Arctera

Replication status on the secondary may display stale information after a reboot or a change in logowner node (4113138)

This issue is observed in a Cluster Volume Replication (CVR) environment. When you reboot the secondary or change the logowner node, the replication status on the secondary displays stale data and is out of sync with the primary. When you verify the status of the replication using the vradmin repstatus command, you may see the following message in the output:

VxVM VVR vradmin INFO V-5-52-1205 Primary is unreachable or RDS has 
configuration error.
Displayed status information is from Secondary and can be out-of-date.
<!--NeedCopy-->

This issue may occur because the secondary logowner is unable to communicate with the primary after the change. This may lead to failures in replication operations such as pauserep, stoprep, and migrate. However, this issue does not impact the actual VVR replication functionality.

Workaround: To synchronize the replication status between the primary and secondary, perform one or both of the following steps:

  • Restart the Veritas Volume Replicator daemon ( vras-vradmind) on the secondary logowner for the impacted RVG.
  • Restart the vras-vradmind on the primary logowner node.
Replication status on the secondary may display stale information after a reboot or a change in logowner node (4113138)

In this article