Continuous replication failover and failback
Typically, the source cluster drives a replication session. However, in some situations, it may be useful for the destination cluster to drive the replication session. Access Appliance supports a failover and a failback feature for continuous replication. This feature enables control of replication to be temporarily relocated from the source cluster to the destination (target) cluster.
Continuous replication failover and failback is useful for:
Planned failover
In cases where the source cluster is taken down for routine maintenance or for moving applications to another cluster, a planned failover procedure is available for moving replication from the source cluster to the destination cluster.
Unplanned failover or Disaster recovery
In cases where the source cluster fails unexpectedly, an unplanned failover procedure is availble for moving replication to the destination cluster.
With failover and failback, you can use the replication continuous failover command to move control from the source cluster to the destination cluster. You use the replication continuous failback to restore control to the source cluster.
Continuous replication failover does not automatically move the NFS or the CIFS share information that is associated with file system from the source cluster to the destination cluster. Share information has to be done manually.
CIFS shares should be removed before failover and failback operations. After failover and failback operation are complete, add the CIFS shares again.