Troubleshooting Replication CR issues

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

Make sure you have read through this document and understood how Replication CRs are created. See Understanding Replication CR Workflow for more details.

Creating a Replication CR triggers Replication Plug-in for Containers to create a LocalVolume and a RemoteVolume CR. These CRs are used to gather information about the primary and secondary sites storage volumes.

When the status of Replication CR does not change to an expected status, then run the kubectl describe command for the event log.

If an error message is shown in the newest event log, follow the instructions of the error message to fix the problem. Also, check the event logs for the LocalVolume and RemoteVolume CRs in the primary and secondary sites.

Note: Operations performed on a replication group CR or replication CR may not immediately reflect the status at the sites. The status is updated only after reconciliation is completed among sites and custom resources, which can take 5–10 minutes. You can monitor the status by using the watch command on the replication/replicationgroup or by checking the logs.