Administrator Guide

}),
(cluster-2,{ summary:: suspended, details:: [cluster-departure]
})]
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
● The ls command shows consistency group cg1 as suspended, requires-resume-at-loser on cluster-2 after cluster-2
is declared the losing cluster during an inter-cluster link outage.
● The resume-at-loser command restarts I/O on cluster-2.
● The ls command displays 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:: suspended, details:: [requires-resume-at-
loser] })]
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
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
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
Table 11. Consistency group field descriptions
Property Description
Standard properties
cache mode
synchronous (default) - Writes are done synchronously. Writes are not
acknowledged to a host unless they have been sent to back-end storage at all
clusters.
detach-rule
Policy for automatically picking a winning cluster when there is an inter-cluster
link outage. A winning cluster is intended to resume I/O operations when the link
fails.
● no-automatic-winner - The consistency group does not select a winning
cluster.
74 Consistency Groups