Best Practice for Remote Copy volumes

Consider the following best practices for virtual volumes used in Remote Copy.

• Source and target virtual volumes must be the same size.

• Virtual volumes must have a user CPG and a snapshot CPG.

• A snapshot CPG for virtual volumes being replicated must have the same tier of storage as the source; not a lower tier of storage.

• To provide the best granularity of Remote Copy failover, allow a failover of only one host or application. Therefore, add all virtual volumes belonging to the same application to the same Remote Copy group. Do not add virtual volumes that have no host or application (logical link) to the same Remote Copy group.

  Virtual volumes that have logical links include:

  • Virtual volumes used by the same application (data and log volumes, for example)

  • Virtual volumes used by a Logical Volume Manager (LVM) volume group

  • Virtual volumes that contain virtual disks of the same VM

• Consider performance before mixing different types of disks/RAID levels on the source and target systems. You can only write as fast as your slowest drive.

• When using Remote Copy in combination with virtual domains, the source and target virtual volumes must be in domains of the same name on the source and target systems. However, they do not need to be of the same type (type of provisioning, RAID, or disk).