Managing failover of a TrueCopy or Universal Replicator copy group

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

In a planned failover, you can run the applications from the secondary site.

From the secondary site, change the status of replication group CR to perform the swap-split operation. This triggers Replication Plug-in for Containers to failover all the TrueCopy or the Universal Replicator pairs in the copy group managed by the parent replication group to the secondary site.

The data copy process from the primary site to the secondary site is stopped and the applications can write data to the secondary volume.

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.

Edit the ReplicationGroup CR. Enter:

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

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

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

# KUBECONFIG=${KUBECONFIG_S} kubectl get replicationgroup
NAME                     STATUS DESIREDSTATE  OPERATION AGE
replicationgroup-sample  Split  swap-split     none    17m

Verify that the replication CR status is Failover. Enter:
```
# KUBECONFIG=${KUBECONFIG_S} kubectl get replication
NAME                 STATUS    DESIREDSTATE OPERATION AGE
replication-sample   Failover  none         none      6d20h
```
Note:
- The replication CR status at primary site is Split and the replication CR status at the secondary site is failover.
- The applications can now write data to the secondary volume (S-Vol).