HP StorageWorks Storage Mirroring Virtual Infrastructure user's guide (T2558-96095, April 2008)
Table Of Contents
- Introducing Storage Mirroring for Virtual Infrastructure
- Install Storage Mirroring for Virtual Infrastructure
- Getting Started with Storage Mirroring for Virtual Infrastructure
- Configure your VMware ESX server to use a root account
- Configure your VMware ESX server to use a non-root account
- Configure the SCP timeout
- Configure the VirtualCenter operation timeout
- Navigate the Storage Mirroring for Virtual Infrastructure interface
- Find out more information about tasks
- Start Storage Mirroring for Virtual Infrastructure
- Connect to the Administrative Servers
- Set up the E-mail Server
- Manage ESX Servers
- Set up Protection for a Virtual Machine
- Monitor your Protected Virtual Machines
- Pre-Staging Data on the Target
21
z Enter the display name—Enter the name you would like to use to identify the replica virtual
machine.
z Map replica virtual network adapters to target VSwitches—If there are multiple target
networks, you can select the network on the target to use.
z Number of processors—Select the number of processors for the replica virtual machine.
z Amount of memory—Enter the amount of memory to use for the replica virtual machine.
When you are finished configuring the replica virtual machine, click Next.
NOTE: Do not use any special or unique characters in the replica virtual machine name,
including the following:
# / \ : * ? ' " < > |
NOTE: The Processors on the source server field displays the number of processors on
the original source virtual machine.
NOTE: The Memory on the source server field displays the amount of memory (in MB) on
the original source virtual machine.
NOTE: The target virtual machine is registered on the first replication loop and will remain
registered. To unregister a machine, you must click the Delete Protection button and
choose the Delete the associated replica virtual machine option.
Even though the target machine appears to be available on the ESX box, the target virtual
machine should never be powered on, removed, or otherwise modified while it is owned
by an active job. Doing so will corrupt the target virtual machine and break the protection
job.