Verifying the status of Replication CR

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

When a Replication CR is created, its status transitions to Pair once the initial replication is established and data protection begins. The time required for this transition depends on the size of the data in the target PVC.

Verify the Replication CR status at the primary site. Enter:

KUBECONFIG=${KUBECONFIG_P} kubectl get replication

Sample output:

NAME      STATUS    DESIREDSTATE   OPERATION  AGE
replication-sample  Pair      none           none       12m

Verify the Replication CR status at the secondary site. Enter:
```
KUBECONFIG=${KUBECONFIG_S} kubectl get replication
```
Sample output:
```
NAME      STATUS    DESIREDSTATE   OPERATION  AGE
replication-sample  Pair      none           none       12m
```
If the Replication CR was created incorrectly, do the following:
1. Delete the Replication CR from the primary site: Enter:
```
KUBECONFIG=${KUBECONFIG_P} kubectl delete -f hspc_v1_replication.yaml
```
2. Verify whether a PVC with the specified name exists in the secondary cluster. If it exists, delete it. Enter:
```
KUBECONFIG=${KUBECONFIG_S} kubectl delete pvc <PVC-name>
```