Hyper-V R2 Can Give You Backup / Recovery Options You Never Had Before!

Times are tough, and belts are tight.  Many companies have looked to server virtualization to reduce costs through hardware consolidation.  Cutting costs by combining server instances onto fewer physical systems can reduce costs, but could you do more?  Are you squeezing the right cost without putting your organization at risk? 

Could you actually save more with less?

I speak with lots of customers about cost cutting and virtualization.  I’m always interested in how they manage their virtual environment, and often dig into their operational procedures and practices. Yes you’ve heard that Hyper-V in Windows Server 2008 R2 includes Live Migration - providing continuous application availability during planned failovers for virtual machines. Live Migration and Quick Migration are fantastic availability features of Windows Server 2008 R2 and Hyper-V, but not all servers or applications require this level of availability.

If you’ve purchased VMware, you likely know about VMotion, a similar capability to Live Migration.  Do you use VMotion for all (or any) of your systems?  For all the hype of these marquee availability features, organizations simply do not use them for many (if any) VMs.  Perhaps the cost of shared storage is too high to facilitate failover clustering, or the level of complexity is too much for administrators in remote branch offices.  Added expense and complexity are at odds with the cost drivers pushing consolidation through virtualization. 

Most individual production servers require some ability to be recovered from a failure.  Regardless of your virtualization method (VMware, Hyper-V, or other) or your use of planned failover tools (Live Migration, VMotion, or other), you still likely need to backup and recover the VMs and the data they serve / process. 

How do you backup and restore your VMs?  Are you doing it the most efficient way?

Do you leverage the same agents inside VMs you use on physical systems?  Lots of companies charged down the “virtualize to consolidate” path without altering their backup and recover processes.  Many companies still backup VMs using agents inside the virtual machines.  There’s nothing wrong with this approach, and it may even be unavoidable in some situations.  The problem is that backing up the same old way means these companies are still buying the same expensive backup agents for each VM.  It also means they need to rebuild a VM to recover (it in much the same way as an old physical server).   Savings realized through server consolidation can be substantial, but without adjusting your operational methods, benefits are limited! 

Why not take advantage of the encapsulation of server instances to improve disaster recovery?  VMs live in files, why not backup and restore the few number of files that represent a VM, rather than be forced to reconstruct VMs to recover them?

Consolidated Backup and Recovery of VMs is Part of Windows!

Did you know that everything you need to do a Hyper-V backup is included in Windows Server?  There are at least two ways to make complete, consistent backups of VMs on Hyper-V that can be quickly and easily restored without purchasing additional backup software.  Because VM files exist on top of a Windows file system, they can be accessed by all the same backup and recovery tools you already know and use, leveraging the integrated snapshot capability of the Volume Shadow Copy Service .  If you don’t want to use an external backup and recovery product you can use the integrated Windows Server Backup utility (WSB) or write your own custom process to make snapshots using diskshadow and xcopy.  For an even better backup and recovery solution, you can checkout System Center Data Protection Manager which enables you to snapshot and backup your VMs (for example) ever 15 minutes efficiently over the network. 

VMware Backup Costs Extra, and You Still Need 3rd Party Tools!

Yes, you could do something similar with VMware – they offer VMware Consolidated Backup to backup a VMware host and the hosted / encapsulated virtual machines, but just like VMotion, it is by no means a low cost backup solution.  It still requires a VMware 3rd party backup solution as well as the extra cost of  VMware’s tools.  Even with all that, it’s not a simple process to get it working. 

Simplify Your Linux / UNIX Backups with Windows?

What sort of support do you have for some of the vintage UNIX systems or those few (perhaps) mysterious Linux systems in the corner of your computer room?  If you are primarily a Windows administrator, how long might it take you to rebuild those systems and reload / reconfigure the applications they host?  What if the “Y2K Compliant” hardware on which those dinosaurs run were to fail?  Could you even find the install floppies or a drive to load them?  Microsoft doesn’t provide much in the way of support for Linux or UNIX operating systems – it’s not our business.  Even with that, because they can be virtualized on Hyper-V, you can make reliable backups of these non-Windows operating systems using the same integrated, low cost tools and capabilities.  I walked through the details of how this all works on my personal blog here using an instance of Hannah Montana Linux for fun.  This distribution is of course not supported by Microsoft on Hyper-V, but the process works perfectly.  Microsoft does have support arrangements with two of the large commercial Linux distribution vendors (Red Hat and Novell), but there are hundreds of Linux distributions and lots of other non-Microsoft operating systems out in the world.   While Microsoft doesn’t provide support for UNIX on Hyper-V (just like with all those unsupported Linux distributions), there are versions that work, including Open Solaris, SCO UNIX, and every Linux distribution I’ve tried:

image

      Open Solaris 5.11 

 image 

SCO OpenServer 5.0.7

    image

    Unsupported (by Microsoft) Linux

Even without support from Microsoft, I can snapshot, backup, and recover single processor versions of these operating systems on Hyper-V simply and efficiently, just like I can my supported Windows VMs.  Can you do that with physical instances of all your servers?  Can you do it as cheaply and efficiently on other virtualization platform?

Don’t Just Consolidate with Virtualization – Modernize With Hyper-V

Backup is just one example of how you can save using the virtualization capabilities integrated in Windows Server to make your operations more efficient.  Take a look at the efficiency of your entire IT infrastructure as you approach your virtualization projects.  Review your investments in hardware, software, management tools, personnel, training and understand the impact of your move to virtualize and where you can drive out the most cost and get the most benefit.  For more details on the integrated backup and recovery capabilities Windows Server 2008 R2 and Hyper-V, check out my personal blog.

-John

Published 30 November 09 08:16 by John Kelbley

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# tonyr said on November 30, 2009 7:05 PM:

did not bother to read your entire post but I suspect that you failed to explain that a vss based backup of csv based volumes is not currently possible.

# John Kelbley said on November 30, 2009 7:43 PM:

Tony - thank you for your comment.

You really should read the whole post, it's not about planned availability, it is focused on cost and simplicity.

The post discusses the value of the backup features integrated into Windows Server 2008 R2 for Hyper-V.  As I explain, I believe that backup and recovery is a more fundamentally important capability than costly, complex planned availability solutions like VMware's VMotion.

Remember that CSV is not a requirement for Hyper-V Live Migration, so Live Migration and VSS backups are not mutually exclusive.  Yes many current commercial backup products do not at this time support backup of VMs homed on the recently introduced CSV, but that support is coming.  

NetApp recently announced their support for CSV back up (http://blogs.netapp.com/msenviro/2009/11/streamlined-backups-integrated-storage-monitoring-for-hyper-v.html).

-John

# tonyr08 said on December 1, 2009 8:33 AM:

yes given your basic premise that windows backup solution is awesome I do very much agree and vmware does not have a solution like it, sorry about the negativity it was not called for!  

# Alan said on December 9, 2009 5:04 PM:

Hannah Montana Linux an excellent choice.

# Michael said on January 2, 2010 7:02 AM:

Hmmm.....

Nice article but a couple of points:

My customers already have an investment in Backup Exec or Arcserve, why should I shoe in DPM just to backup Hyper-V. They extend these products to backup VMware and it's done!

Free backup of VMware, unsupported but I use GhettoVCB and FastSCP from Veeam, both free.

You don't mentioned DPMand backing up Linux.....hmmm...I smell another gap here!

Glad to see a 3rd party finally mentioned (- Netapp).

I would say live migration is similar in capability to vMotion not the other way around....who has had it shipping in their RTM versions for over 3 years, not in a Beta or CTP.

Keep up the good work!

Mike

# John Kelbley said on January 4, 2010 9:33 AM:

Mike – thanks for your comments!

The point of the post was not to pitch DPM, but to let everyone know that the inclusion of VSS in Windows Server 2008 makes backup and recovery of VMs easier in Hyper-V.

You and your customers can continue to leverage existing investments in 3rd party enterprise backup and recovery tools - they can provide great value and standardizing on a single set of tools simplifies administration.  

The products you mentioned are VSS aware, and they can take advantage of this great capability.

Any VSS aware backup that works with Hyper-V will be able to perform backup and recovery of ANY VM if you backup the host  - Windows, Linux, UNIX – DPM works great for this as do other products!

Some enterprises have realized that their existing tools are not efficient at backing up virtual machines.  Using a traditional backup suite with agents inside a VM does not take advantage of the encapsulation benefits of virtualization.  Agents on the physical host for some backup solutions simply are not efficient - copying ALL VM related files each time a backup is run, plus agents for some of these solutions are EXPENSIVE!

These companies have figured out that they can back up Hyper-V hosts to a DPM Server in a network efficient way to centralize backups of VMs – the agents are much less expensive than other products and DPM only transmits the “deltas” over the wire.

They can then backup the DPM Server using their existing solution to meet compliance goals while saving money on agent!

As for VMotion versus Live Migration I’m not convinced either of them are particularly mainstream.  Yes, they are spoken of frequently  and used in some production environments, but I do not believe  that Live Migration or VMotion are as important as good back and recovery capabilities.  Many scenarios cannot justify the additional cost of shared storage or complexity, but most server production deployments can and do justify a backup and recovery.  The inclusion of VSS in Windows Server 2008 means that Hyper-V has the foundation of industry leading backup and  recovery built in to the product at no additional cost.  I think that’s far more valuable in many scenarios than highly touted “zero down time” capabilities many customers do not implement.

-John

# Dan said on January 20, 2010 11:30 PM:

John, you mention using VSS and Windows Backup to back up VMs. All is good and well, but I was wondering, does this mean that the VMs must be in saved or shut down state to properly back them up? I know that you could enable a HV VSS writer in Win2008 (not R2), and that allowed you to use Windows Backup to back up running VMs. However, nowhere is this mentioned in R2 guides and blogs. Could you clarify this please?

# Dan said on January 20, 2010 11:42 PM:

Another question for you John. You mentioned that "Remember that CSV is not a requirement for Hyper-V Live Migration". That is not correct, and can be clearly seen in this TechNet article:

Hyper-V: Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2:  

http://technet.microsoft.com/en-us/library/dd446679(WS.10).aspx

Can you please clarify this?

# John Kelbley said on January 21, 2010 10:37 AM:

Dan, thanks for the questions and comments!

VSS functions pretty much identically in Windows Server 2008 and Windows Server 2008 R2. When the Integration Services are enabled on a Windows virtual machine and a backup request is made on the Hyper-V host, a VSS backup request is passed into the VM and it can continue to run while a backup image is created.  For non-Windows VMs (or Windows virtual machines with the Integration Services not enabled) a VSS backup request on the host will save the state, create a snapshot, and resume the virtual machine.   I have a pretty detailed blog posts about how it all works here:  http://blogs.technet.com/enterprise_admin/archive/2009/11/18/the-wonder-of-volume-shadow-copy-and-hyper-v.aspx

CSV is not a requirement for Live Migration - Hyper-V failover clustering on R2 can be implemented without CSV and Live Migration still works.  Because CSV and Live migration were both introduced in R2, a lot of the guidance speaks of them both together (and sometimes isn't 100% clear).  Without CSV, each VM should be provisioned on a unique LUN for Live Migration.  I really like using CSV because it simplifies storage provisioning for me.

Let me know if you want to know more or if I’m not being clear.

-John

# Dan said on January 21, 2010 1:34 PM:

Thanks John for your prompt reply. So, if I understand correctly, the above TechNet article and the Hyper-V documentations are all wrong? No one mentions Live Migration without mentioning CSV as a clear requirement for that to work, although that now, while writing this post, I did find a Dell FAQ that says that CSVs are not a must. Interesting. Thanks for clearing that for us.

As for Windows Backup - if I understand correctly, in order to use Windows Backup to back up VMs on Windows Server 2008 Hyper-V R2, all I need to do is to simply back up the volume holding the VMs? And to restore them? Do I simply restore the individual VHDs? What about the registry change that was possible in RTM that enabled application restore feature for individual VMs? Does it also work on R2?

Dan

# John Kelbley said on January 22, 2010 7:07 AM:

Hey Dan, great questions!

Most of the documentation that I’ve seen covers CSV and Live Migration together because they both required increased network bandwidth between cluster nodes.  The guidance I’ve seen isn’t wrong, it’s just incomplete.  Mike Sterling and I are addressing some of this in our upcoming R2 revision to our Hyper-V book (http://www.sybex.com/WileyCDA/SybexTitle/Windows-Server-2008-Hyper-V-Insiders-Guide-to-Microsoft-s-Hypervisor.productCd-0470440961.html).

I’m traveling right now, but when I get back near my lab, I’ll configure up a cluster with Live Migration without CSV and walk through it all in a blog post on my other blog (http://blogs.technet.com/enterprise_admin).

As for using Windows Server Backup (WSB) for Hyper-V – you’ve pretty much got it.  Running a WSB  backup can capture running VMs the way you described using VSS.  You do need to register the Hyper-V writer with WSB on both Windows Server 2008  and Windows Server 2008 R2 (http://support.microsoft.com/kb/958662).  The backup is an application aware (Hyper-V) backup – keep that in mind as you configure the backup and test restore.  The restore puts ALL the VMs back on the target when you use WSB – you cannot do a selective (single VM) restore.  For that I use the diskshadow process I’ve layed out in my other blog (Backup - http://blogs.technet.com/enterprise_admin/archive/2009/11/19/diskshadow-xcopy-backup-of-hyper-v.aspx and Restore - http://blogs.technet.com/enterprise_admin/archive/2009/11/20/diskshadow-xcopy-restore-of-hyper-v.aspx).

WSB does not work for host-based backups of CSV volumes (nor does my diskshadow-based process)  – System Center Data Protection Manager or backup from within the VM is what I typically use.  

Hope that helps, and keep the questions and comments coming!

-John

# John Kelbley said on January 26, 2010 8:04 AM:

Dan (and everyone else!),

I just put up a more detailed walk through / monologue about Live Migration without CSV on my other blog:  http://blogs.technet.com/enterprise_admin/archive/2010/01/26/csv-is-not-required-for-live-migration.aspx.

-John

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required
Page view tracker