HP Storageworks Storage Mirroring Console user's guide (T2558-96330, April 2009)

5 - 1
Storage Mirroring for
Hyper-V:
Protecting a Hyper-V
Virtual Machine
With Storage Mirroring for Hyper-V, you can use the Storage Mirroring Console to protect virtual
machines running on the Microsoft Hyper-V platform. Storage Mirroring replicates all of the files
associated with the virtual machine for one Microsoft Hyper-V host to another.
Storage Mirroring for Hyper-V can be used to:
 Automate the discovery and protection of virtual machines.
 Map the source virtual switches for a virtual machine to the available virtual switches on the target
Hyper-V host.
 Monitor IP addresses and perform a manual failover when a failover condition is met.
 Bring the replica virtual machine online with the network adapters disabled, allowing you to test
the replica virtual machine while the source is still online.
Supported configurations
Your Storage Mirroring for Hyper-V environment must conform to the following requirements.
 The source virtual machine be in its own home folder that is not shared by any other virtual
machines.
 The source virtual machine cannot be created in the Hyper-V system default folder.
 The source virtual machine cannot be replicated into to Hyper-V system default folder on the
target host.
 The replica virtual machine folder on the target must be unique to the replica virtual machine.
 The source virtual machine snapshot folder must be unique to the virtual machine, and it cannot
be in the Hyper-V system default folder.
 The replica virtual machine snapshot folder cannot be the Hyper-V system default folder.
 The replica virtual machine cannot share a snapshot folder with any other virtual machines.
 After protection has been configured for a virtual machine, the location of the snapshot folder for
that virtual machine cannot be changed. If the snapshot folder is changed, the protection job must
be removed and re-created.
 If a protected virtual machine is renamed in the Hyper-V manager, the replica virtual machine will
not be renamed. In order to pick up the name change, the protection job must be removed and
re-created.
 Virtual machines cannot use raw, pass-through, or differencing disks.
 Clustered Hyper-V source and target environments are not supported.
Storage Mirroring for Hyper-V supports the following host protection configurations when protecting
Hyper-V virtual machines:
 Many to One—Virtual machines from multiple Hyper-V hosts can be protected on a single
Hyper-V target host.
 One to One—Virtual machines from a single Hyper-V host can be protected on a single Hyper-V
target host.