During an inter-cluster link outage, you might permit I/O to resume at one of the two clusters, the
winning cluster.
About this task
I/O remains suspended on the
losing cluster.
When the inter-cluster link restores, the winning and losing clusters re-connect, and the losing cluster discovers that the winning cluster has resumed I/O without it.
Unless explicitly configured, I/O remains suspended on the losing cluster. This prevents applications at the losing cluster from experiencing a spontaneous data change.
The delay allows you to shut down applications.
After stopping the applications, use the
consistency-group resume-at-loser command to:
Resynchronize the data image on the losing cluster with the data image on the winning cluster.
Resume servicing I/O operations.
You can then safely restart the applications at the losing cluster.
To restart I/O on the losing cluster:
Steps
Use the
ls command to display the operational status of the target consistency group.
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
Use the
ls command to verify the change in operational status: