Hello, everyone!
In this post, I would like to share with you how to manually switchover between active and standby sites.
This topic
describes how to manually switch over the U2000 applications from the active
site to the standby site and then from the standby site to the active site. In
this way, you can check the system reliability and maintain the system.
Prerequisites
Ensure that the following prerequisites
are met before performing the operation.
· The heartbeat
connection between the active site and the standby site is normal.
· The data
replication between the active site and the standby site is normal.
· The active site
and the standby site are normal and no fault occurs. If there is a fault tag,
clear it by running the following command:
hares -clear <resource_name> [-sys hostname]
Command example:
hares -clear NMSServer
Context
After the active site is switched over to
the standby site, the original standby site in the cluster changes to the
active site. In addition, the replication relation between the active site and
the standby site is repaired and the replication direction is specified again.
NOTICE:
· After the
switching, the U2000 may not receive alarms. It is recommended that the client
be reconnected and the primary site be configured on the U2000 again based on
the the primary site's IP address after switching.
· After the
switching, the FTP account may be unavailable. You are advised to reconnect the
client and server. To reconfigure the FTP account, including the sever IP
address, user name, and password, choose Administrator > Settings> FTP Account Information Management from the main menu.
Procedure
1. Check the
replication status.
a. Log in to the active site as the root user.
NOTE:
If security hardening is enabled, log in to the OS as the ossuser user. Then run the su - root command and enter the root user password to switch to the root user.
b. Run the following command to check the data replication status of the active sites.
In the Solaris or SUSE Linux OS:
# vradmin -g<diskgroupname> repstatus <rvgname>
Command example:
# vradmin -g datadg repstatus datarvg
The following information appears.
Replicated Data Set: datarvg
Primary:
Host name: 10.71.210.78
RVG name: datarvg
DG name: datadg
RVG state: enabled for I/O
Data volumes: 4
VSets: 0
SRL name: lv_srl
SRL size: 3.00 G
Total secondaries: 1
Secondary:
Host name: 10.71.210.76
RVG name: datarvg
DG name: datadg
Data status: consistent, up-to-date
Replication status: replicating (connected)
Current mode: asynchronous
Logging to: SRL
Timestamp Information: behind by 0h 0m 0s
NOTE:
You can perform the active/standby replication switchover only when Data status is consistent, up-to-date.
2. To perform manual switchover between the primary and secondary sites.
U******mands:
· To switch over the U2000 and database applications from the primary site to the secondary site, run the following command on the secondary site as the root user:
# hagrp -switch AppService -any -clus localclus
· To switch over the U2000 and database applications from the secondary site to the primary site, run the following command on the primary site as the root user:
# hagrp -switch AppService -any -clus localclus
NOTE:
Run the hastatus -sum command as the root user to check the service status and service group status.
Use GUI:
c. Log in to the MSuite client. For details, see Logging In to the MSuite Client.
d. Choose Deploy> Monitor HA Status from the main menu. The Monitor the Statusdialog box is displayed.
e. Optional: Click View to view the historical records of the primary and secondary sites.
NOTE:
The status of each HA system indicator is displayed. You can click detail info to view details or restoration suggestions.
f. Click check nowto view the current information about the primary and secondary sites.
NOTE:
· It takes three to five minutes to check the HA system status.
· After the check, you can view the check results, details, and suggestions in the HA Statusdialog box.
· The check results are saved as .xml files in /opt/oss/engr/engineering/ha_review/result. The name of the latest check result file contains the word new. For example, ha_review_result_20150421165146.xml. In this example, 20150421165146indicates the time when the HA system status is checked. You can run the following commands to check the file information:
· # cd /opt/oss/engr/engineering/ha_review/result
# cat ha_review_result_20150421165146.xml
g. Click Switch to Secondary to switch to the secondary site.
That's all, I hope you like it.
Thank you!
