Data Domain: Replication Initialization is in Progress, and Upgrade Cannot Proceed

Symptom:
DD OS upgrade precheck fails with the following error:

Error: Replication initialization is in progress, and upgrade cannot proceed.

Resolution:

1. Check if the Data Domain is configured for replication and if the replication is in an initializing state.

#replication show config      ------> (To check if the replication pair has configured)

#replication watch rctx://  ------> (Provide the context number to check the replication status)
 
     #replication watch rctx://1
     Use Control-C to stop monitoring.
     (0:00:00) Replication initialize started...
     (0:00:10) 1%: initializing 3/3^C

2. As the replication initialization is in a third phase, check the replication status. The user must wait until the replication initializations complete.

# replication status rctx://1
 
     CTX: 1
     Mode: source
     Destination: mtree://ddve3010.dd.lab/data/col1/oracle-se2
     Enabled: yes
     Low bandwidth optimization: disabled
     Replication encryption: disabled
     Replication propagate-retention-lock: enabled
     Local filesystem status: enabled
     Connection: connected since Fri Oct 12 12:37:24
     State: initializing 3/3 1%       ---->  (Check how much the initialization completed)
     Error: no error
     Sync'ed-as-of time: -
     Current throttle: 8192K bps
     Max-repl-streams: 8 (default)

3. If the user wants to upgrade the Data Domain first, then replication must be broken on both sides.

On source:
# replication break rctx://<ctx_num>        ------> (Provide the context number to break the replication pair)

On target:
# replication break rctx://<ctx_num>        ------> (Provide the context number to break the replication pair)

4. After the replication is broken, upgrade the DD OS.
5. You will now need to reconfigure the replication but need to determine which path to go down
   • Scenario A: If repl init was getting close to finishing, you will probably want to fastcopy the destination mtree to a temp mtree and redo the repl
   • Scenario B: If repl init wasn't very far along and you just want to start over from scratch, we delete the destination mtree and then redo the repl

Scenario A

1. You want to save the progress from the init before it was broken.
   On the destination DD, fastcopy the repl mtree to a temp mtree and then delete the orig mtree and run cleaning for 1 min to clear it out:

# mtree create /data/col1/<temp_mtree>
# filesys fastcopy source <repl_mtree> destination <temp_mtree>
# mtree delete /data/col1/<repl_mtree>
# filesys clean start        -------> only needs to run for 1 min to clear out deleted mtree

2. Now we will remake the replication on the source and destination and init it on source:
   

   On target:
   # replication add source mtree://<dd_src_hostname>/data/col1/<source_mtree> destination mtree://<dd_dst_hostname>/data/col1/<dest_mtree>
   
   On source:
   # replication add source mtree://<dd_src_hostname>/data/col1/<source_mtree> destination mtree://<dd_dst_hostname>/data/col1/<dest_mtree>
   # replication init rctx://<ctx_num>

3. Once the initialization is done for the repl ctx, we delete the temp mtree off the destination:
   

   # mtree delete /data/col1/<temp_mtree>

Scenario B

1. You want to start over from scratch. On destination DD, we delete the repl mtree, run cleaning and then redo the repl

# mtree delete /data/col1/<repl_mtree>
# filesys clean start        -------> only needs to run for 1 min to clear out deleted mtree

2. Redo the repl on the source and dest and init it:
   

   On target:
   # replication add source mtree://<dd_src_hostname>/data/col1/<source_mtree> destination mtree://<dd_dst_hostname>/data/col1/<dest_mtree>
   
   On source:
   # replication add source mtree://<dd_src_hostname>/data/col1/<source_mtree> destination mtree://<dd_dst_hostname>/data/col1/<dest_mtree>
   # replication init rctx://<ctx_num>