Arctera

Upgrades to 8.0.2 may cause configuration errors in VVR replication (4115707)

This issue is observed when you upgrade to InfoScale 8.0.2 release. After the upgrade on the secondary site is complete, the RVG replication status shows that the RLINK is disassociated and the secondary SRL volume is missing.

This issue typically happens in cases where the SRL volume size is large (30 GB or more) and if the auto_recover tunable is enabled. The SRL resync (recovery) process may take some time depending on the size of the SRL volume. The SRL volume remains unavailable during this time and any attempts to associate the SRL volume with the RVG fail.

The following errors are displayed in the replication status:

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.

VxVM vxvol ERROR V-5-1-3681 Volume <volumename> state is not ACTIVE

<!--NeedCopy-->

Workaround:

Wait for the SRL volume resync (recovery) process to complete.

Check the progress using the following command:

# vxtask list

Once the recovery process is complete, the SRL volume status appears as enabled.

Compete the post-upgrade VVR replication configuration

  1. Identify the logowner node using the following command:

    # vxprint -VI

  2. Configure the replication IP on the logowner node, if it is not already configured, and then verify using the following command:

    # vxprint -PI

  3. Associate the SRL volume with the RVG:

    # vxvol -g diskgroupname aslog rvgname srlname

  4. Recover the RLINK:

    # vxrlink -g diskgroupname recover rlinkname

  5. Attach the RLINK on the secondary for the respective RVG:

    # vxrlink -g diskgroupname -f att rlinkname

  6. Start the RVG:

    # vxrvg -g diskgroupname start rvgname

  7. Restart the Veritas Volume Replicator Daemon ( vradmind) on all nodes on both the primary and the secondary site:

    # /sbin/vxstart_vvr stop

    # /sbin/vxstart_vvr start

  8. Check the replication status on the primary:

    # vradmin -g diskgroupname -repstatus rvgname

  9. If the replication status shows as paused, then resume the replication:

    # vradmin -g diskgroupname resumerep rvgname

  10. If the replication status shows as “logging to DCM “œ OR “DCM requires recovery”, then resync the RVG:

    # vradmin -g diskgroupname resync rvgname

Upgrades to 8.0.2 may cause configuration errors in VVR replication (4115707)

In this article