No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Replication between both BMS servers is up-to-date in veritas however it is down in watchman

Publication Date:  2012-07-24 Views:  28 Downloads:  0
Issue Description
The replication between Active and standby BMS servers is down  in watchamn (red). however, in veritas, it is "consistant" & "up-to-date".
Alarm Information
The replication status is down in watchman "RED"
Handling Process
The simple solution is to rename the rlinks like that ones involved by watchman scripts and "repconf.conf" file.
Also, we can change unify the rlink name between vea and watchman config files ("repconf.conf" and watchman scripts under "/etc/wmscripts"). but this solution is a little bit hard dangerous and may become hard to control after. aslo, it needs watchman reboot in both servers.
I suggest to follow the fist method.
Root Cause
* veritas:
when building the replication using vea, the default rlink names will follow this template:
"rlk_ip@_rvgname"
ex: rvg anme : wm_rvg
      primary 10.0.0.10         rlink name:  "rlk_10.0.0.20_wm_rvg"
      secondary 10.0.0.20    rlink name:  "rlk_10.0.0.10_wm_rvg"
* watchman:
- When checking replication status, the used scripts under "\etc\wmscript" invloves "a_to_b_rlk" and "b_to_a_rlk" by default. So, it will receive an error msg telling him that these rlinks dont't exist. thus  it will display the replication as down "red".
Suggestions
 Null

END