RVG goes into secondary log error state after secondary site reboot in CVR environments (4046182)

Last published : Sep 18, 2026
In a CVR environment, after the system at the secondary site reboots, the RVG goes into the secondary log error state.
Workaround: Perform the following tasks to recover from the issue.
  1. Stop the replication.
# vradmin -g <diskgroup_name> stoprep <RVG_name>
  1. Disassociate the SRL at the secondary site.
# vxvol -g <diskgroup_name> dis <SRL_name>
  1. Re-associate the SRL at the secondary site.
# vxvol -g <diskgroup_name> aslog <RVG_name> <SRL_name>
  1. Restart the replication.
# vradmin -g <diskgroup_name> -a startrep <RVG_name>
Related information