What Do I Do If the Synchronization Status Is Displayed as Abnormal After the cascadeTool query Command Is Executed on the Active Node of ServiceCenter at the Production Site and the Active Node at the DR Site

5

【Product�?
ManageOne ServiceCenter

【Version�?
3.X

【Question�?
What do I do if the synchronization status is displayed as abnormal after the cascadeTool query command is executed on the active node of ServiceCenter at the production site and the active node at the DR site?

【Answer�?
The active node at the DR site synchronizes data from the active node at the production site. If any of the following situations occurs, the database at the production site cannot be synchronized. The synchronization status is displayed as abnormal after you run the cascadetool query command.
The active and standby nodes of ServiceCenter at the production site or the active node at the DR site are faulty.
The network at the production or DR site is faulty.
Network ports required for DR synchronization are not enabled based on the communication matrix.

----End

Other related questions:
ServiceCenter at the DR Site Is Abnormal
If ServiceCenter at the DR site is abnormal, you need to perform the operations in this section to troubleshoot the fault and quickly restore services. For details,seeServiceCenter at the DR Site Is Abnormal,The applicable version is 3.0.9.

What Do I Do If the Database Status of the Standby Node Is Abnormal in Active/Standby Mode
【Product�? ManageOne OperationCenter 【Version�? 2.3, 3.0, 3.0.5, 3.0.7, 3.0.8, and 3.0.9 【Question�? What do I do if the database status of the standby node is abnormal in active/standby mode? 【Answer�? Perform the following operations on OperationCenter 2.3: Step 1 Use PuTTY and the remote login IP address to log in to the standby node where OperationCenter is deployed as user appuser. Step 2 Run the following command to switch to user root: sudo su �?root Enter the password of user root. Step 3 Run the following command to disable PuTTY logout on timeout: TMOUT=0 Step 4 Run the following commands: su gaussdba gs_ctl build ----End Perform the following operations on OperationCenter 3.X: Step 1 Use PuTTY and the remote login IP address to log in to the standby node where OperationCenter is deployed as user appuser. Step 2 Run the following command to disable PuTTY logout on timeout: TMOUT=0 Step 3 Run the following command: gs_ctl build ----End

ServiceCenter at the DR Site Is Faulty
If one ServiceCenter VM at the DR site is faulty or both the active and standby ServiceCenter VMs at the DR site are faulty, and services cannot be recovered after ServiceCenter is restarted, you can troubleshoot the faults by following the instructions provided in this section to recover the services. For details,seeServiceCenter at the DR Site Is Faulty,The applicable version is 3.0.9.

Query the active node of the OpenStack controller node during eBackup installation
To query the active node of the OpenStack controller node, do as follows: 1. Log in to the OpenStack reverse proxy in SSH mode. 2. Run the su-root command and enter the password of user root as prompted to switch to user root. 3. Run the source set_env command, select openstack environment variable (keystone v3), and enter the password to import environment variables. 4. Run the cps template-instance-list --service cps cps-server command. In the command output, the node whose status is active is the active node of the controller node.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top