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

297 of 739
5. Using an external tool, copy each source .vmdk file to its corresponding target
location shown in the replica virtual machine disk mapping file. Be sure to copy the
files to the exact locations shown; otherwise, Storage Mirroring Recover for Virtual
Infrastructure will not be able to find them. Also, note that in the mapping, the .vmdk
filenames may be different on the target than the source. If this is the case, you
must use the target .vmdk filenames shown in the mapping file when you are
creating the copies.
Note:
Some copy utilities have been found to create copies of .vmdk files that are a
different size than the original source .vmdk file. Storage Mirroring Recover for
Virtual Infrastructure requires the source and target .vmdk files to be of identical
size in order to perform a file difference mirror. Before moving forward, you
should verify that the .vmdk file sizes match from source to target.
6. If you have created a snapshot before copying the .vmdk files, you may remove it
now.
7. Modify the scheduled protection start time to start the protection job immediately.
The file difference synchronization will begin.
Protect a server to a virtual target machine on VMware ESX
Storage Mirroring Recover Virtual Recovery Assistant for ESX is used to protect entire
physical and/or virtual source machines to virtual target machines running on VMware
ESX Server.
1. Before you set up protection for your source, verify that the required ports are
enabled.
2. Launch the Storage Mirroring Recover Virtual Recovery Assistant console.
3. Connect to the VirtualCenter server.
4. Set up protection for the virtual machine.
Firewall configuration
If your source and target are on opposite sides of a NAT or firewall, you will need to
configure your hardware to accommodate Storage Mirroring Recover Virtual Recovery
Assistant communications. You must have the hardware already in place and know how
to configure the hardware ports. If you do not, see the reference manual for your
hardware.
In a NAT or firewall environment, you must have a static mapping where a single,
internal IP address is always mapped in a one-to-one correlation to a single, external IP
address. Virtual Recovery Assistant cannot handle dynamic mappings where a single,