HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

37 of 739
The Application Manager can be used to configure Storage Mirroring Recover to provide
high availability for BlackBerry Enterprise Server using a Microsoft SQL Server database
back end. This allows a secondary server to assume the identity and role of a failed
server while maintaining the availability of BlackBerry Enterprise Server and/or SQL
Server services with minimal disruption or data loss.
Configuration All versions
Consolidated to consolidated Supported
Distributed to distributed Not supported
Distributed to consolidated Not supported
Supported Hyper-V configurations
To protect Hyper-V virtual machines, your 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 the 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.
The following host configurations are supported for protecting Hyper-V virtual machines: