Over the past several years, alternatives to traditional backup software products have been developed for backing up virtual machines. These image backup solutions leverage the fact that VMs encapsulate the entire application, OS and server configuration state in a single file — like a VMDK for VMware. This allows the entire server backup process to be reduced to a single (large) file backup and removes the complexity involved with traditional backups, which usually had to understand file structure, application data objects, etc.
But, even with image-based backups, returning applications to operational status requires several steps.
New technologies in image-based backup solutions now enable hosts to run VMs directly from the backup area, without first restoring these files to primary storage. By allowing a VMDK file to be accessed and run while it’s still a “backup file” eliminates the entire recovery transfer step and shortens the time to data significantly. Another feature of these new image backup solutions is recovering application-specific data objects without agents or special backup steps.
The ability to run VMs from the backup area also enables another key improvement to image-based backups: recovery verification. These solutions can, as part of the backup process, run a recovery verification step, to make sure the VM can be restarted. Instead of simply confirming that data can be returned in one piece, this process can assure that the application, or the entire application stack across several VMs, can be recovered.
For storage VARs, server virtualization is a fact of their customers’ lives. And, like their physical server predecessors, the topic of backing up virtual machines comes up often. For customers already using image-based backup solutions, features like backup verification and in-place recovery of VMs can support some compelling discussions. For those still using traditional backup solutions, this may be the tipping point to making the switch to image backups.
Follow me on Twitter: EricSSwiss