To reverse the direction of a sync operation, use the following procedure to commit your sync and call the reverse
endpoint.
If you want to keep your source cluster updated with new writes from your destination cluster post-cutover, you can use reverse
. For more details, see Mid-sync Considerations.
Before You Begin
Before you can reverse your sync direction, you must configure mongosync
and use the start
endpoint to set the following parameters:
reversible
totrue
enableUserWriteBlocking
to"sourceAndDestination"
.
For more information on limitations and requirements of reversing sync, see reverse
.
Important
If you are migrating from a pre-6.0 source cluster, you cannot reverse sync.
Steps
Use these steps to reverse the direction of your sync:
Finalize your sync.
Follow the Finalize Cutover Process tutorial to enable write blocking and finalize your data migration.
IMPORTANT: mongosync
does not support Filtered Sync during the reverse sync process.
Call the reverse
endpoint.
Call the reverse
endpoint to reverse the direction of your sync operation. Your original source cluster becomes your new destination cluster and your original destination cluster becomes your new source cluster.
mongosync
replicates all writes that you performed on your new source cluster after you unblocked writes (during step 4 of the Finalize Cutover Process) to the new destination cluster.