2011 (Windows)

Table Of Contents
http://technet.microsoft.com/en-us/library/dd440865(WS.10).aspx
Find information about backing up and restoring Microsoft Hyper-V virtual
machines:
See About backing up and restoring Microsoft Hyper-V virtual machines
on page 292.
About backing up and restoring Microsoft Hyper-V
virtual machines
To create a backup of a Microsoft Hyper-V virtual machine, you must back up the
volumes of the computer where the virtual machine is hosted. Create either a live
backup or a system state backup of the host machine.You cannot back up or restore
a specific virtual machine. A live backup is created while the virtual machine is
running (hot backup).
A system state backup is created in any of the following conditions:
The guest operating system on the virtual machine is not running (cold backup).
The Hyper-V VSS integration component is not installed in the virtual machine.
Note: Symantec System Recovery is unable to back up cluster shared volumes.
Because volumes in such a configuration are accessible to each of the clustered
Hyper-V host computers, a given volume cannot be locked for backup . However,
clustered disks can be backed up by Symantec System Recovery because one host
has exclusive access to the disk.
To create a backup of a running virtual machine, the following conditions must
be met:
The guest operating system must be running.
The guest machine must be running Windows Server 2003 or later.
If the guest machine is running Winows 2000, Windows XP 32- or 64-bit, you
can only create a system state backup (cold backup).
The Hyper-V VSS integration component must be installed on each virtual
machine to be backed up.
If you move a virtual machine from Virtual Server 2005 to Hyper-V, first
uninstall the Virtual Server 2005 integration component from the virtual
machine. After you Virtual Server 2005 integration component, you can install
the Hyper-V VSS integration component.
Backing up Microsoft virtual environments
About backing up and restoring Microsoft Hyper-V virtual machines
292