Resynchronizing a TrueCopy pair or Universal Replicator pair after a failover

Replication Plug-in for Containers Installation and User Guide

Version

3.18.x

Audience

anonymous

Part Number

MK-92ADPTR155-10

ft:lastEdition

2026-07-07

After a planned failover is completed and applications are running from the secondary site, the data can be synchronized back to the primary volume.

From the secondary site, change the status of the Replication CR to perform swap-resync operation site. This triggers Replication Plug-in for Containers to swap the replication storage volumes and resync the TrueCopy pair or the Universal Replicator pair.

The data copy process is resumed from the secondary site to the primary site.

Note: These operations enable the secondary site to act as the new primary site. The direction of the replication, that is the data copy and journal is now reversed from the secondary site to the primary site.

Verify that the Replication CR status is failover and the operation value is none.

From the secondary cluster, edit the Replication CR. Enter:

# KUBECONFIG=${KUBECONFIG_S} kubectl edit replication <Replication-name>

Modify the desiredPairState parameter to swap-resync.
For example:
```
spec:
  desiredPairState: <swap-resync>
```

Verify that the Replication CR status is Pair. Enter:

# KUBECONFIG=${KUBECONFIG_S} kubectl get replication 
NAME                 STATUS   DESIREDSTATE   OPERATION   AGE
sample-replication   Pair    swap-resync    none        19m