Operating System Software User Manual

where -removevv <VV_name> <group_name> automatically removes the corresponding
secondary volume of the specified volume in the specified volume group.
When removing an entire remote-copy group using the removercopygroup command, you can
also indicate that all volumes on the secondary system should also be removed by using the
-removevv option, as follows:
# removercopygroup -removevv <group_name>
where -removevv <group_name> removes the volumes on the secondary system that are
associated with the specified volume group to be removed.
Coordinated Manual Grow over Remote Copy
The size of a remote-copy volume can be increased by using the growvv command. The growth
of a volume is coordinated across primary and secondary targets. A coordinated grow can be
started from either the primary or secondary target. If the volume to be grown is in a remote-copy
group, the group must be stopped before the grow operation is permitted.
Volumes on remote targets are grown to the intended size of the local volume. If a target cannot
be contacted or remote copy is not started, only the local volume will be grown. A check is first
made to see if the local and remote volumes can be grown by the requested amount. If this succeeds,
all volumes are grown; however, if other volumes are grown during this process, it is possible that
volumes on the local array or remote array may not grow. If this occurs, the volumes that didn't
grow must be grown manually before the group can be started.
Configuring ESX Host Personas
All host personas function with HP 3PAR Remote Copy, but care should be taken when using ESX
hosts that the correct host persona is selected.
For host configurations that have independent ESX hosts attached to the primary and secondary
arrays, host persona 6 (Generic-Legacy) should be configured. This persona does not support
ALUA path management.
For host configurations that have ESX hosts connected to both the primary and the secondary array,
using HP 3PAR OS 3.1.2 or later, host persona 11 (VMware) should be configured. This persona
supports ALUA path management.
The use of persona 11 (VMware) with remote-copy volumes supports non-disruptive failover. For
more information, see “Using Peer Persistence for Non-disruptive Failover in 1-to-1 Remote Copy
in Geocluster Environments” (page 163)
Coordinated Manual Grow over Remote Copy 155