Administrator Guide

Resuming I/O after rollback
About this task
Without that data, the winning cluster's data image is inconsistent. Resuming I/O at the winner requires rolling back the
winner's data image to the last point where the clusters agreed.
This can cause a sudden change in the data image.
Many applications cannot tolerate sudden data changes, so the roll-back and resumption of I/O requires manual intervention.
The delay gives the administrator the chance to halt applications before changing the data image. The data image is rolled back
as soon as a winner is chosen (either manually or automatically using a detach rule).
The resume-after-rollback command acknowledges that the application is ready for recovery (this may involve application failure
and/or restarting the host).
NOTE: It is recommended to restart the hosts of affected applications.
Steps
1. Use the ls command to display the consistency group on the winning cluster during an inter-cluster link outage.
VPlexcli:/clusters/cluster-1/consistency-groups/cg1> ls
Attributes:
Name Value
-------------------- -------------------------------------------
active-clusters []
cache-mode synchronous
detach-rule -
operational-status [suspended, requires-resume-after-rollback]
passive-clusters [cluster-1, cluster-2]
recoverpoint-enabled false
storage-at-clusters [cluster-1, cluster-2]
virtual-volumes [dd1_vol]
visibility [cluster-1, cluster-2
Contexts:
advanced recoverpoint
2. Use the resume-after-rollback command to acknowledge that the application is ready for recovery.
VPlexcli:/clusters/cluster-1/consistency-groups/cg1> resume-after-rollback --
consistency-group cg1
This will change the view of data at cluster cluster-1, so you should ensure
applications are stopped at that cluster. Continue? (Yes/No) Yes
3. Use the ls command to display the change in operational status.
VPlexcli:/clusters/cluster-1/consistency-groups/cg1> ls
Attributes:
Name Value
-------------------- ----------------------
active-clusters [cluster-1]
cache-mode synchronous
detach-rule -
operational-status [ok]
passive-clusters [cluster-2]
recoverpoint-enabled false
storage-at-clusters [cluster-1, cluster-2]
virtual-volumes [dd1_vol]
visibility [cluster-1, cluster-2]
Contexts:
advanced recoverpoint
78
Consistency Groups