Managing failover for TrueCopy or Universal Replicator pairs

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 CR to perform failover operation. This triggers Replication Plug-in for Containers to failover the TrueCopy pair or the Universal Replicator pair.

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

Note: Do not modify the replication in the primary site during this operation.

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

Edit the Replication CR. Enter:

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

Modify the desiredPairState parameter to failover.
For example:
```
spec:
  desiredPairState: failover
```
Confirm that Replication CR status is Failover and the operation value is none.
```
# KUBECONFIG=${KUBECONFIG_S} kubectl get replication
NAME                 STATUS   DESIREDSTATE   OPERATION   AGE
replication-sample   Failover    failover          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).