Administrator Guide

virtual-volumes [dd1_vol, dd2_vol]
visibility [cluster-1, cluster-2]
Contexts:
advanced recoverpoint
2. Use the consistency-group resume-at-loser to restart I/O on the losing cluster.
VPlexcli:/clusters/cluster-1/consistency-groups/cg1> resume-at-loser -c cluster-2
This may change the view of data presented to applications at cluster cluster-2. You
should first stop applications at that cluster. Continue? (Yes/No) Yes
3. Use the ls command to verify the change in operational status:
VPlexcli:/clusters/cluster-1/consistency-groups/cg1> ls
Attributes:
Name Value
------------------- ----------------------------------------------------------
active-clusters [cluster-1, cluster-2]
cache-mode synchronous
detach-rule no-automatic-winner
operational-status [(cluster-1,{ summary:: ok, details:: [] }),
(cluster-2,{ summary:: ok, details:: [] })]
passive-clusters []
recoverpoint-enabled false
storage-at-clusters [cluster-1, cluster-2]
virtual-volumes [dd1_vol, dd2_vol]
visibility [cluster-1, cluster-2]
Contexts:
advanced recoverpoint
You might notice rebuilding-across-clusters in operational status while devices are rebuilding.
Setting the read-only attribute
SRDF R2 devices (replicas) are an example of an array-managed Business Continuance Volume (BCV). For consistency groups
that contain these volumes, you can use the set command to set the consistency group to read-only.
About this task
If the read-only attribute is true, the system prevents write operations to virtual volumes in the consistency group. Virtual
volumes in a read-only consistency group must be local, and you must map each virtual volume one-to-one to a single storage
volume (for example, local RAID 0 with no slicing).
You cannot add virtual volumes with an invalid topology to a read-only consistency group. The consistency-group add-
virtual-volumes command fails. If you set a consistency group to read-only and that consistency group already contains
virtual volumes with an invalid topology, the set read-only true command fails.
A consistency group cannot be read-only and recoverpoint-enabled at the same time, since the two properties are
incompatible.
Steps
Use the set command to set the consistency group to read-only.
VPlexcli:/> cd/clusters/cluster-1/consistency-groups/test
VPlexcli:/clusters/cluster-1/consistency-groups/test>set read-only true
VPlexcli:/clusters/cluster-1/consistency-groups>ll
Name Operational Active Passive Detach Rule Cache Mode Read
------ Status Clusters Clusters ---------- --------- Only
------- ----------- ------- -------- ---------- --------- ----
DB2_app (Hopkinton,{ winner Hopkinton after 5s synchronous true
summary:: ok,
details:: []
}),
Providence, {
summary:: ok,
Consistency Groups
83