Resynchronizing a TrueCopy or Universal Replicator copy group 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 replication group CR to perform the swap-resync operation. This triggers Replication Plug-in for Containers to pair all the TrueCopy or Universal Replicator pairs in the copy group managed by the parent replication group.

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

Note: This operation enables the secondary site to act as the new primary site. The direction of the replication, that is the data copy and journal are now reversed from the secondary site to the primary site.

Verify the desiredState of all the replication CRs is in none state at both the sites.
Verify the desiredState of all the replication group CRs is in none state at the primary site and in swap-split state at the secondary site.

Edit the ReplicationGroup CR. Enter:

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

Update the value for the desiredPairState parameter to swap-resync.
For example:
```
spec:
  desiredPairState: swap-resync
```

Verify that the ReplicationGroup CR status is Pair and the operation value is none. Enter:

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

Verify that the replication CR status is Pair. Enter:

# KUBECONFIG=${KUBECONFIG_S} kubectl get replication
NAME                 STATUS  DESIREDSTATE OPERATION AGE
replication-sample   Pair    none         none      6d20h