Use this procedure to switch back to DC1 as primary on Avaya Analytics™.
Note:
Perform this procedure only when upgrading from Avaya Analytics™ 4.2 Patch 2, 4.3 Patch 3, or 4.3.1.0 and above release.
Perform this procedure during maintenance window.
Before you begin
Stop new calls from entering the system.
Wait for the final processing of existing calls which is the main process contributing to the downtime. This depends on the system load during the cut over phase.
Wait for the final Extract, Transform, Load (ETL) process after the last call is processed. After the last call is processed, the final ETL must take place within 15 minutes and takes around five to ten minutes to complete.
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.
Do the following to promote DC1 to Geo Primary:
Run the following command:
ccm release orca analytics
To select Geo/High Availability, enter the corresponding number.
To select Geo Options, enter the corresponding number.
To select Switch over: promote secondary data center database to primary option, enter the corresponding number.
To restart below services using post install scripts, do the following:
Restart Measure Processors.
To run Analytics Administration script, use the following command:
ccm release orca analytics
Select Troubleshooting > General > Restart Measure Processors.
Wait till all the measure processors are up.
Restart orca-scheduler and orca-admin-data-service.
Configure the required connections to communicate with Avaya Oceana® on DC1.
Note:
You can also do this step outside the maintenance window.
Run the reports at DC1 in MicroStrategy to ensure that all the required data is available at the DC1. Ensure that all MicroStrategy configuration is available at DC1.
Result
At the end, DC1 Avaya Analytics™ 4.3.1.1 no longer syncs data from 4.x DC2.
