In this video, we demonstrate the process to fail over to a disaster recovery or Dr fluid FS NAS cluster once failed over we'll add new data and then fail back to the primary cluster. First, select the secondary fluid FS cluster in enterprise manager and expand the list of NAS volumes. Select the NAS volume. You want to promote to a production volume and take note of the recovery point which is the time of last successful replication.
Next expand the list of replication actions and choose the option to promote destination after promotion, we must restore the configuration of the NAS volume by right clicking on the volume itself. This will recreate share schedule and quota settings on the newly promoted volume. The promoted NAS volume is now accessible by going to the public virtual IP address for the secondary fluid FS cluster. In this example, note that both the primary and secondary clusters contain the exact same data to highlight the fail back replication activity.
We will create a new text file on the secondary cluster. Once the primary site has been recovered and is operational, we remove the previous replication policy from the NAS volume in the event that the primary site was recovered. We must also remove its replication policy as well by first promoting the replica from the primary side and then deleting the policy. This is not necessary in the event that the primary side is redeployed from scratch. Next configure replication from the secondary site back to the primary site for the promoted NAS volume. In this case, since the primary site was recovered, we will replicate back to the original NAS volume.
If the primary site had been redeployed, we would need to have created a new volume to replicate too. Once the policy has been created, start the process via the replication actions drop down menu after replication is completed and we're ready to cut over back to the production site. Promote the replica volume on the primary site via the replication actions menu on the secondary FS cluster. As before we must apply the volume configuration to the promoted NAS volumes on the primary side.
This will also apply any changes that occur to the configuration while live on the secondary cluster. We can now verify that the new data written while the secondary volume was promoted has made it back to the primary cluster. Now we follow the same processes before to delete the replication policy. First delete the policy on the secondary site to remove the fail back replication configuration. Finally create a new replication policy for the NAS volume. From the primary cluster to the secondary cluster.
