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
24
Set data transmission options
You can modify the data transmission options in order to make them more suitable for your
environment.
Click the Change
button in the Data Transmission area. The Set data transmission options
window will appear.
You can change the snapshot data compression settings in the Compression area. The following
options are available:
z Never—(Default) No compression will be applied to the data.
z Only during the initial synchronization—Data will be compressed only during the initial
transmission of the flat virtual disk files.
z Always—All transmissions associated with the protection set will be compressed.
In the Frequency area, select the time and file size thresholds that will trigger data transmission.
z Transmit when the snapshot data reaches this size (MB)—(Default = 32 MB x the number
of snapshot-capable virtual disks) Enter the size of snapshot file (in MB) that will trigger a
transmission from the source to the target. When multiple virtual disks are used, any combination
of writes across all virtual disks that accumulate to this size will trigger replication. The minimum
size allowed is 32 MB.
NOTE: Enabling compression requires that additional CPU cycles be used on both the source and
target servers.