Performing a failback of a TrueCopy or Universal Replicator pair using the DR Operator

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

Failing back a TrueCopy or Universal Replicator pair using the DR Operator restores the original replication direction after a failover, making the recovered site the secondary and reestablishing normal data synchronization between the two storage systems.

Perform the following steps on the primary site:

Apply the DR policy with desiredState set to failback. Enter:

kubectl patch drpolicy <drpolicy-cr-name> --type=merge -p '{"spec":{"desiredState":"failback"}}'

Verify if the DR policy is applied on both the primary and secondary sites. Enter:

 kubectl get drpolicy

Sample output:

kubectl get drpolicy
NAME                  SOURCE_CLUSTER   TARGET_CLUSTER   REPLICATION_TYPE   DESIRED_STATE   STATUS    CTG_ID   AGE
sample-app-drpolicy   site-61          site-62          sync               failback        Healthy   21       35m

Verify the replication status of the PVCs. Enter:

kubectl get replication -A

Sample output:

NAMESPACE   NAME                                                 STATUS   DESIREDSTATE   OPERATION   AGE
         demo-app    replication--apps-1-drpolicy-sync--demo-server-pvc     Pair    failover        none        42m
         demo-app    replication--apps-1-drpolicy-sync--demo-ui-pvc         Pair    failover        none        42m
         demo-db     replication--apps-1-drpolicy-sync--demo-db-pvc         Pair    failover        none        42m

You must also verify the replication status on the secondary site.