HP 3PAR Operating System Software - Manual (Page 106)

modified. To create target volumes automatically, use the admitrcopyvv -createvv
command. See:
Automatically Creating Target Volumes on the Secondary System
HP 3PAR Command Line Interface Administrator’s Manual
•
Virtual volumes used with HP 3PAR Remote Copy must be one of the following types:
Thinly-provisioned virtual volumes (TPVVs) with snapshot space drawn from a CPG. TPVVs
require the use of HP 3PAR Thin Provisioning Software. ◦
◦ Fully provisioned virtual volumes (FPVV). For more details about virtual volumes, see the
HP 3PAR StoreServ Storage Concepts Guide.
◦ Read and write snapshots of existing TPVVs or FPVVs can also be used as new base
virtual volumes within HP 3PAR Remote Copy. Individual remote-copy replication groups
are prevented from containing multiple virtual volumes from the same volume tree.
•
The primary and secondary virtual volumes to be linked (for example, vv1 and vv1_remote)
must be the same size.
•
Volumes can have different RAID levels and availability levels (Cage, Magazine, and so on).
•
Virtual volume limits are as follows:
◦ The maximum number of system-wide mirrored volumes for the HP 3PAR 10000 StoreServ
Storage is as follows:
– 2,400 in synchronous mode
– 6,000 in asynchronous periodic mode (when only asynchronous periodic mode is
used)
◦ The maximum number of volumes per remote-copy group in synchronous or asynchronous
periodic mode is 300.
◦ The maximum size of a mirrored volume is 16 TB.
•
If you configure a TPVV as a primary virtual volume in a remote-copy volume group, the
secondary volume should either:
◦ Have no data written to it before you add it to the remote-copy volume group, or
◦ Match the size of the primary volume exactly, so that the entire secondary volume gets
written during initial synchronization.
•
You can save read/write (RW) snapshots to remote-copy volume groups.
For more information, see “Rules for Adding Snapshots to Volume Groups” (page 112) .
For additional information, see “Linking Virtual Volumes in Volume Groups” (page 113) .
Converting Standard Virtual Volumes
1. Ensure that the virtual volume you use with remote copy does not share snapshot administrative
space or snapshot data space with any other virtual volume.
If the virtual volume shares these resources with other volumes, the conversion will fail.
106 Working with Virtual Volumes