Use this procedure to promote the secondary DC2 to the primary role after a DC1 failure.
Note:
If testing, you must only perform this process during a maintenance window.
The entire data center must fail over in this case. For example, it is not supported to run Avaya Oceana® on DC1 against Avaya Analytics™ on DC2.
Before you begin
Check that the secondary DC2 data center is in standby mode.
Procedure
Log in to the Cluster Control Manager (CCM) console as the customer user.
Switch to being the root user by entering the command su.
To run the Analytics Administration script, use the following command:
ccm release orca analytics
Select Geo/High Availability by pressing the corresponding number.
Select Geo options by pressing the corresponding number.
Select Switch over: Promote secondary data center database to primary by pressing the corresponding number.
In the Proceed to Geo switchover field, enter y. Entering n cancels the operation.
In the Continuing will switch over this data center to Primary data center field, enter y.
Return to the previous page by entering b.
Quit the current page by entering q.
Return to the main menu by entering m.
Restart the following services using post install scripts, do the following:
Run Analytics Administration script, use the following command:
ccm release orca analytics.
Select Troubleshooting > General > Restart Measure Processors and wait until all the measure processors are up.
Restart orca-scheduler and orca-admin-data-service.
Restart pod orca-database-rest.
Return to the previous page by entering b.
Quit the current page by entering q.
Return to the main menu by entering m.
Next Steps
Once the cause of the DC1 failure has been resolved and fixed, you can switch back from DC2 as the primary to DC1. To start that process, DC1 first needs to receive data replication from DC2. See Reversing data replication when the DC2 is the primary.
