Reprotecting original disaster recovery reverses the direction of replication. Once the production site has been restored, the original source pod should be demoted. To reprotect the MongoDB instance now running at the target site (disaster recovery site):
-
Original production site: demote the pod on restored FlashArray. Whether the demotion operation is performed using FlashArray GUI or command line, the ‘--skip-quiesce’ option should be selected so that stale data on the failed source array is not unnecessarily replicated prior to completing the demote.
From command line:
purepod demote --skip-quiesce <pod_name>
From FlashArray GUI select (see Figure 7):
Storage Pods ➤ <pod> ➤ '⋮' (vertical ellipsis) ➤ Demote ➤ Skip Quiesce➤ Demote
Figure 7.
Following the completed demotion of the original source pod, ActiveDR will automatically reverse the direction of replication. The new content created by MongoDB running at the recovery site is now replicated back to the original production site.