Note
There may be preparatory steps that you would like to take before performing failover or while your cluster is operating normally in order to be prepared to switch client applications over to the replication peer. See Deploying a Failed-Over Replication Peer as a Working Cluster.
The following recover scenarios are supported for a protected path (on' Cluster A') that has a sync replication destination (on 'Cluster B') and an async replication destination (on 'Cluster C'), per the configuration described in Combining Synchronous and Asynchronous Replication:
Turnover from 'Cluster A' to 'Cluster B', so that 'Cluster B' can become the primary cluster.
Ungraceful failover to 'Cluster C' in the event that 'Cluster A' and 'Cluster B' both become unreachable.
After 'Cluster A' and/or 'Cluster B' become reachable, to restore data written to 'Cluster C' while they were down, establish async replication with 'Cluster C' as the source.
Subsequently, failback to 'Cluster A'.
Graceful Turnover to the Secondary Sync Replication Peer (VAST Web UI)
On the secondary sync peer, open the Protected Paths tab of the Data Protection page.
Right-click the protected path, select Replications and then Modify Replication State.
The Modify replication state dialog shows that the expected state change after fail over.
Click Turn Over.
The secondary sync rep cluster becomes the source and starts to replicate to the async destination.
Ungraceful Failover to the Async Replication Destination Peer
On the async destination peer, cluster C, open the Protected Paths tab of the Data Protection page.
Right-click the protected path, select Replications and then Modify Replication State.
The Modify replication state dialog shows that the expected state change after fail over.
Click Fail Over.
While the failover is in progress, the protected path role on 'Cluster C' appears as Becoming Standalone. When failover is complete, the role on Cluster C becomes Stand alone. Cluster C is now writeable and is not replicating to any of the other peers.
Replicate from Cluster C after Failover
Once again, on the now standalone 'cluster C', right-click the protected path, select Replications and then Modify Replication State.
In the Modify replication state dialog, click Become Source.
When the process is complete, the role of the protected path on 'Cluster C' shows as Source, and Cluster C begins replicating to the available destination(s).
Fail Back to Cluster A after Ungraceful Failover
On the async destination peer, cluster C, open the Protected Paths tab of the Data Protection page.
Right-click the protected path, select Replications and then Modify Replication State.
The Modify replication state dialog shows that the expected state change after fail over.
Click Fail Over.
While the failover is in progress, the protected path role on 'Cluster C' appears as Becoming Source. When failover is complete, the role on Cluster C becomes Source. Cluster C is now the writeable source of async replication. Any other peers in the replication group that are reachable become destinations.