When compared to VMware’s virtual server product, market share taken by Microsoft’s Hyper-V is pretty low. Despite that, both have been known to share many similarities. These similarities become even more pronounced when it comes to backup. However, what you have to understand about Hyper-V is that one has to get some of its oddities just right if you want your backups to be consistent and successful.
Keep on reading to find out what are the best strategies and practices you can apply to make you backup successful each and every time.
Basics of Hyper-V Backup Strategy
The basics of virtual server backup dictate that should you back up multiple virtual servers in one physical box, then the chances of your I/O demands will increase significantly. Many users choose to backup Hyper-V at host level instead backing them up at individual virtual servers. The best practice in a physical environment would be to back up with only one agent per server. But this is would be over simplifying things. In this instance the most obvious place to back up would be the host which in fact combines the virtual machines. In this lies the difficulty of multiple virtual machines being handled by the hypervisor. The virtual machines are going to be active at the same time, therefore establishing the need for a way to stop the backup being carried out.
For this very purpose, a built in schema has been introduced by Microsoft called VSS (Volume Shadow Copy Services). VSS stops the virtual machine for a small duration and takes snapshot of its current state. This process is termed quiescence.
The three main components of VSS schema are a requester, a provider and a writer, which as the same suggests, request, write and implement the process in Windows OS and storage array in a larger environment.
When it comes to Hyper-V backup, VSS is an instrumental element. This means that the next time you look for an application for Hyper-V backup, make sure that is works well with VSS.
Main Things to Get Right for Successful Hyper-V Backup
VSS requires a minimum of 300GB of disk space to work. That is 300GB on individual VHD (Virtual Hard Disk). Most of this space is used to write data for quiescence, and from there it is copied by the backup application. The backup will surely fail with this disk space.
To handle quiescence, timekeeping, data exchange between host and guest, Hyper-V has numerous integration components. Without them being right all the time, the backup will either fail or remain inconsistent. To make sure that no such issues arise, make sure that you keep up to date with Microsoft patches.
And finally, a few things about the Hyper-V backup provider. As mentioned before, you need to check to the compatibility of VSS. Also you need to make sure that the backup provider has the capacity incremental forever backups.
The leading cloud backup software, CloudBacko has these abilities and so much more. CloudBacko is the best Hyper-V backup software and requires absolutely no training for you to get started. For more information, you can visit http://www.cloudbacko.com