Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

VVR Rlink connect fail state

Created: 10 Nov 2013 • Updated: 28 Jan 2014 | 2 comments
Prithvi's picture
This issue has been solved. See solution.

Hi,

Looking a solution to fix VVR rlink connect fail state at primary location while secondary status is in connect active.

why this happened?

There was abrupt power outage at secondary location and now when all servers at secondary are up, replication is showing in inconsistent state and Rlink is in connect fail state.

 

Operating Systems:

Comments 2 CommentsJump to latest comment

kjbss's picture

On the primary, try to recover the rlink to the secondary:

# vxrlink -g <diskGroup> recover <to_secondary_rlk>

If that does not work, again on the primary host, detach and then again attach the rlink:

# vxrlink -g <diskGroup> -f det <to_secondary_rlk>
# vxrlink -g <diskGroup> -a att <to_secondary_rlk>

If these still do not work, please provide the following, run from both the primary host, and then from the secondary host:

# vxprint -Pl
# vxprint -qhtg <diskGroup> | egrep '^rv|^rl'
# vradmin -g <diskGroup> -l printrvg <rvgName>
# vradmin -g <diskGroup> -l repstatus <rvgName>

 

SOLUTION
stinsong's picture

Also, restart VVR processes maybe help after all of above not work:

/usr/sbin/vxstart_vvr stop
/usr/sbin/vxstart_vvr