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

280 of 739
Note:
While generic SCSI device mappings in virtual machines are supported by
Storage Mirroring Recover for Virtual Infrastructure, the generic SCSI device
will not be created on the target virtual machine. This is necessary because the
target virtual machine will fail to start if the SCSI device hardware does not exist
on the target ESX host. Upon failback, the generic SCSI device will be mapped
back to the original source.
If a source virtual machine with a generic SCSI device mapping is replicated to
target and the entire protection job is removed, then re-created in the reverse
direction, the SCSI device will not be mapped back to the original source.
Enter the following information for the source server:
1. If your source virtual machine is administered by VirtualCenter, select the
VirtualCenter server in the Source VirtualCenter server field. The VirtualCenter
server is where the VMware VirtualCenter service is running. The VMware
VirtualCenter service manages all the VMware ESX servers in the environment.
Selecting a VirtualCenter server provides the following benefits:
● Storage Mirroring Recover for Virtual Infrastructure will be able to accept a
non-root user account.
● Storage Mirroring Recover for Virtual Infrastructure will be able to use
VMotion technology to move the virtual machine.
To add additional VirtualCenter servers or to update credentials, see Managing
VirtualCenter servers.
If you want to create a connection directly from one ESX server to another without
using VirtualCenter, select (None).
2. In the Virtual machine to protect field, enter the name of the virtual machine you
want to protect.
Note:
● Each protection that you configure will apply to a single virtual
machine.
● Special or unique characters in the virtual machine name will cause
the Storage Mirroring service to unload. In order to avoid this issue, do
not use any special or unique characters in the virtual machine name,
including the following: # / \ : * ? ‘ " < > |
● Even if the selected virtual machine is configured to use “thin” (sparse)
disks, the replica .vmdk file on the target (and, in the case of a reverse
protection, the restored source .vmdk disk) will not be created as thin.
This creates the potential for disk space issues. Make sure that there is
adequate disk space available on the source virtual machine and the
target for failover and reverse protection scenarios.