Most organizations are still relying on traditional data backup and recovery software for virtual machine (VM) backup, but there are downsides to that approach. In Jacob Gsoedl's latest Storage magazine article, learn about the best way of backing up VMs, whether it's with traditional virtual machine backup options or new virtual machine backup software.
In most IT shops, virtual servers are backed up just like physical servers at first, but as the number of virtual servers increases traditional backup methods start breaking down. The fact that a single physical machine can host many VMs poses challenges that simply don't exist when backing up dedicated physical servers.
With multiple VMs competing for processing, storage and networking resources, contention for those resources is the No. 1 challenge of virtual server backup. Concurrent backup jobs on multiple VMs can seriously impact the performance of applications hosted on those VMs. And when traditional backup methods are used to protect virtual servers, some key capabilities are sacrificed, such as application-consistent data protection and the ability to restore sub-VM-level objects such as files without having to restore the whole virtual machine. As virtual servers proliferate in the data center, there's a clear call to storage managers to rethink backing up VMs and the applications they host.
VM backup options
Lauren Whitehouseanalyst, ESG
Contemporary virtual server environments can be protected using one of the following backup methods:
- Backup agents on VMs
- Continuous data protection (CDP)
- VM image backup on the hypervisor using a backup proxy server
Backup agents on VMs. Backing up VMs by placing backup agents on each VM extends the most popular backup method of physical servers into the virtual server realm. Instead of having one backup agent per physical server, each VM gets its own agent and backup jobs run independently for each virtual machine. This approach is workable as long as the number of VMs is small; as the number of VMs per hypervisor grows, resource contention will create performance problems. Besides being able to leverage an existing backup product and approach, a backup agent can be the most straightforward way of ensuring application consistency. For many apps, especially non-Windows applications and applications that aren't integrated with Microsoft Volume Shadow Copy Service (VSS), backup agents may be the only way of ensuring application consistency of backup data.
Continuous data protection. A CDP product that runs on each VM is one step up from backup agents running traditional full and incremental backups. A CDP product captures changes on an ongoing basis and puts a much smaller burden on the host machine than traditional backups do. CDP products work either at the file or block level, and usually provide integration with mainstream applications to enable restoring to consistent points in time. In addition to large backup application vendors that have added continuous data protection to their suites, CDP products are offered by a list of smaller vendors such as FalconStor Software Inc., InMage Systems Inc., Vision Solutions (acquired Double-Take Software) and others.
VM image backup on the hypervisor using a backup proxy server. Backing up VM images on the hypervisor, rather than backing up virtual machines via agents within each VM, is appealing for many reasons: it enables efficient backups with little processing overhead; eliminates the need to install and manage backup agents on each VM; and by centralizing the backup of all VMs at the host, the backup of multiple VMs can be orchestrated to minimize performance problems and resource contention. To offload the backup task from the hypervisor machine, VM snapshots are usually replicated or mounted to a backup host or proxy server, minimizing the performance impact while backups are performed.
Host-side VM image backup, however, is usually only acceptable if VMs can be backed up in a consistent state; all major hypervisor vendors have added the ability to quiesce a VM while a snapshot of the VM image is taken. Another challenge with VM image backup is restoring granularity. While some backup products are only able to restore virtual machines, others are able to restore sub-VM objects such as files. Consistent data protection of apps within each VM is more challenging with VM image backup than it is with backup agents within virtual machines. Application-consistent data protection is usually limited to applications that are integrated with VSS. For apps that aren't integrated with VSS, crash-consistent backups may be the only option; but if application consistency is required, backup agents on VMs are the way to go.
Without question, the trend is toward VM image backup at the hypervisor level and offloading the backup task to a proxy backup server—and as the number of virtual servers grows it becomes even more relevant. Mechanisms to enable efficient VM image backup and capabilities vary significantly between Citrix XenServer, Microsoft Hyper-V and VMware vSphere.
VMware vStorage APIs for Data Protection
Data protection has been a sore spot for VMware and it took VMware until vSphere 4 to get it right. Prior to vSphere 4, VMware provided VMware Consolidated Backup (VCB) to offload backups from hypervisors to a proxy server, but it wasn't widely adopted due to some grave shortcomings. With VCB, snapshots of virtual machine disk (VMDK) images were taken and copied in full to a proxy server from which backups were run. Offloading the backup to a proxy server minimized the impact of backups on VMs, but it required additional storage for the snapshots.
"VCB was clumsy and the biggest problem with it was how to size the proxy server to where all snapshots needed to be copied," said Lauren Whitehouse, a senior analyst at Milford, Mass.-based Enterprise Strategy Group (ESG).
The vSphere 4 vStorage APIs for Data Protection (VADP), the successor to VCB, addresses the shortcomings of VCB. To start with, VADP no longer requires copying data to a proxy server; instead, snapshots can now be mounted to a proxy server where they're backed up to disk or tape. While VCB only supported taking full snapshots of a VMDK, regardless of how much it changed, VADP supports efficient snapshots via its change block tracking (CBT) feature. CBT keeps track of changes within a VMDK at a block level and enables efficient snapshots of changes only.
vSphere 4 is fully integrated with VSS to enable application-consistent snapshots of VSS-enabled applications running on virtual machines. To be able to take advantage of VSS, however, VMware Tools needs to be installed on the virtual machine. vSphere communicates with VSS via VMware Tools.
To back up a VM via VADP, a "quiesce" command is sent to vSphere to instruct the VM to flush data in memory to disk and no longer accept writes. If VMware Tools is installed on the VM, VMware Tools can pass on the "quiesce" to VSS-enabled applications on the virtual machine to also "freeze" applications within the VM. A snapshot is then taken; on completion of the snapshot, the "freeze" is removed from the VM and VSS-enabled applications. Finally, the snapshot is mounted to the backup proxy from where it's backed up to disk or tape.
VADP is widely supported by third-party backup applications. In addition to major backup application vendors (Arkeia Software, CA, CommVault Systems Inc., EMC Corp., IBM, Quest Software Inc./BakBone Software Inc. and Symantec Corp.), smaller vendors such as PHD Virtual Technologies and Veeam Software offer virtual server backup applications with VADP support. Additionally, vSphere provides its own backup tool called VMware Data Recovery (VDR). VDR is delivered as a virtual appliance to perform snapshots and deduplication to a backup disk target. VMware has positioned VDR as a lower end backup product.
Microsoft Hyper-V and VSS
Thanks to Microsoft VSS, Microsoft got data protection for Hyper-V right from the get-go. In many ways, a VMware VADP backup cycle resembles backing up Hyper-V. A backup app dispatches a "quiesce" command to a Hyper-V VM via VSS to flush data in memory to disk; VSS then takes a snapshot and removes the freeze from the VM. Similar to VADP, the snapshot can then be replicated or mapped to a dedicated backup proxy server. The "quiesce" can be extended to VSS-enabled applications within VMs, but requires the so-called backup integration service installed on the VM, akin to VADP requiring VMware Tools.
VSS depends on several main components (click here for more information on Microsoft Volume Shadow Copy components) VSS-enabled applications need to implement a so-called VSS-writer that coordinates various components to create consistent shadow copies of one or more volumes. Applications, such as a backup application, need to implement a VSS-requestor to request a volume shadow copy. The key component, though, is the VSS-provider, which creates and maintains shadow copies (snapshots). While VSS-providers are included with the latest Windows OSes, software and storage hardware vendors can provide their own VSS-providers. Noticeably, hardware-based VSS-providers of arrays enable high performance and highly scalable data protection of Hyper-V environments. While it took VMware to implement change block tracking to get to efficient snapshots, in VSS it's a capability of the VSS-provider. For instance, the VSS-provider that's part of Microsoft's operating systems does incremental snapshots via a copy-on-write method; that is, when a change to the original volume occurs but before it's written to disk, the block to be modified is read and stored away.
The support for VM image-level backup of Hyper-V isn't as extensive among third-party backup applications as is support for VADP. For instance, IBM Tivoli Storage Manager (TSM) and PHD Virtual Backup don't have support for it at present. Similar to VMware, Microsoft provides its own backup solution for Hyper-V environments with System Center Data Protection Manager (DPM). DPM provides near-continuous data protection for virtual machines hosted on servers running Hyper-V. With advanced features like disk-to-disk and disk-to-tape support, the ability to recover sub-VM objects like files, protection of virtual machines while live migration is in progress, integration into Microsoft System Center, and support for clustered and standalone Hyper-V systems, DPM provides a state-of-the-art product rather than the entry-level product VMware provides with VDR.
Citrix XenServer backup
Third-party backup applications can initiate full or incremental disk image snapshots of Citrix XenServer VMs through XenAPI (XAPI). These snapshots are usually crash-consistent and depend on applications to regain a consistent state after a restore. Recovering after restoring a crash-consistent backup is analogous to powering up a virtual machine after a power failure.
With XenServer 5.6, Citrix added live memory snapshots to capture the state of a virtual machine when a snapshot is taken and allows reverting to a previous state on restore. Citrix memory snapshot leverages Microsoft VSS, so it's available for VSS-enabled VMs (Microsoft operating systems) but not for Linux virtual machines.
In addition to XenServer snapshots, XenServer supports shared storage snapshots for arrays supported by XenServer. Leveraging snapshot capabilities of arrays is the fastest and most scalable method to protect a XenServer environment, but it's only an option if the storage infrastructure is supported by XenServer.
Like vSphere and Hyper-V, Citrix provides its own VM image backup application with VM Protection and Recovery (VMPR). A scaled-down version of VMPR that lacks features like scheduling is included with all versions of XenServer. A more advanced version that supports scheduling and automation is available as a paid option. Third-party backup application support for XenServer image-level backup is more tenuous than for vSphere and Hyper-V. Among the backup application vendors that support it are Arkeia Software, CommVault, PHD Virtual Technologies and Veeam Software.
Backing up VMs: The bottom line
Block-based VM image backup on the hypervisor host, ideally via a backup proxy server, is becoming the preferred way of backing up virtual servers. Maturing backup APIs in vSphere, Hyper-V and XenServer, as well as increasing support by backup applications for these APIs combined with performance and scalability merits, are among the main reasons for its adoption. Because most organizations run more than a single hypervisor (more than 70% of companies according to ESG's Whitehouse) and a mix of physical and virtual servers, multi-hypervisor support and the ability to support both physical and virtual server backups are important considerations when choosing virtual machine backup software.
About this author:
Jacob Gsoedl is a freelance writer and a corporate director for business systems.
This article was previously published in Storage magazine.
Download a free guide on backing up VMs
Read a tip about VM backup strategies
Study our tutorial on VMware backup software