This repository was archived by the owner on May 1, 2025. It is now read-only.
  
  
  
  
    
    
    
      
    
  
  
    
File tree Expand file tree Collapse file tree 3 files changed +13
-11
lines changed Expand file tree Collapse file tree 3 files changed +13
-11
lines changed Original file line number Diff line number Diff line change 1+ To reverse sync, the user must be assigned the :authrole: `restore `
2+ role for both source and destination and the ``enableUserWriteBlocking ``
3+ field must be set to ``sourceAndDestination ``.
Original file line number Diff line number Diff line change 11The user specified in the ``mongosync `` connection string must have the
2- required permissions on the source  and destination clusters. The 
3- permissions vary depending on your environment and if you want to  
4- modify write-blocking settings or use reverse sync. 
5- 
2+ required :ref: ` user  permissions < c2c-permissions- and-roles >` on the 
3+ source and destination clusters. The permissions vary depending on your 
4+ environment and if you want to  modify write-blocking settings or use
5+ reverse sync. 
Original file line number Diff line number Diff line change @@ -141,10 +141,10 @@ Request Body Parameters
141141         cluster while migration is in progress, and unblocks writes right
142142         before ``canWrite`` is ``true``.
143143
144-        To reverse  sync, the ``enableUserWriteBlocking`` field must be set 
145-        to ``"sourceAndDestination"``. To allow the source cluster  
146-        to accept writes again, for example after running migration tests,  
147-        run the following command: 
144+        .. include:: /includes/api/facts/reverse- sync-requirements.rst 
145+        
146+        To allow the source cluster  to accept writes again, for example
147+        after running migration tests,  run the following command: 
148148
149149       .. code-block:: shell 
150150
@@ -175,9 +175,8 @@ Request Body Parameters
175175     - Optional
176176     - If set to ``true``, enables the sync operation to be
177177       reversed.
178- 
179-        To reverse sync, the ``enableUserWriteBlocking`` field must be set
180-        to ``sourceAndDestination``.
178+        
179+        .. include:: /includes/api/facts/reverse-sync-requirements.rst
181180
182181       This option is not supported for the following configurations:
183182
 
 
   
 
     
   
   
          
    
    
     
    
      
     
     
    You can’t perform that action at this time.
  
 
    
  
    
      
        
     
       
      
     
   
 
    
    
  
 
  
 
     
    
0 commit comments