With todays great hypervisor management tools and the paradigm shift from Client/Server to Cloud networking the old need to backup “Host” servers has really gone away.

A couple of years ago it became readily apparent that the Client/Server networking model had outlived its usable lifespan and needed to be updated to something better. The NIST defined the new model as a “Cloud.” Broad Network Access, Rapid Elasticity, Resource Pools, On Demand Self Service, and Measured Service are the 5 critical components.This is the new model that will be used going forward for networking. Microsoft releases its Cloud operating system in a matter of weeks.

Virtualization is the gateway technology to the Cloud. Whether that cloud is Private, Public, or some Hybrid of the two there is little question that virtualization is the method driving the move from the old way, Client/Server, to the new way, Cloud!

In the new “Cloud” model Virtual machines are the base components (not hardware). Hardware is grouped into resource pools and allocated to VM’s on an as needed basis. When we take the previous fact into consideration we have to adjust the way we think and act regarding our backup, recovery, replication, migration and disaster recovery strategies. If you approach a virtual environment with the old DR strategies of Client/Server those strategies will suffer from bloated backups and disorganized recovery. The new strategy focuses on the VM and ignores the resource pool since the resource pool is technically an evolving and elastic resource, while the VM is the stable unit of service. Backups are done on a per VM basis and stored in the local or remote resource pool. In the case of a service, application, or entire VM failure these backup files are available to restore to the original host resource, or elsewhere in the resource pool, at the administrators preference. If a host server resource should happen to fail the VM’s could easily and seamlessly be restored, or possibly even moved while running, to another host without service interruption. The VM backups are stored on disk using compression and deduplication strategies to minimize bloat and maximize recovery potential.

Both VMware and Microsoft have included great provisioning and management tools for with their hypervisors to minimize the impact of Host server operations.

At Veeam we clearly understand virtualization, and we make the best backup tools! Next time someone tells you that you need to backup your VM hosts ask them “Why?”

If you haven’t used Veeam Backup & Replication try it today!

GD Star Rating
Hypervisor Host Server Backup Doesn’t Matter!, 3.1 out of 5 based on 8 ratings

Veeam Availability Suite — Download free 30-day trial