Promoting Avaya Analytics on DC2 as primary and configuring Avaya Analytics on DC1 as standby

Last Updated : Apr 08, 2026 |

About this task

Important:

Perform this procedure when you are upgrading from Avaya Analytics™ version 4.2 and above.

Before you begin

Install Avaya Analytics™ version 4.3.1.1 at DC1.

Procedure

  1. If you are upgrading from Avaya Analytics™ version 4.2 and above, on the DC2, which is currently the primary site, do the following on the Cluster Control Manager (CCM) console:
    1. To run the Analytics Administration script as root user, use the following command:

      ccm release orca analytics

    2. To select the Geo/High Availability option, enter the corresponding number.
    3. To select the Geo options option, enter the corresponding number.
    4. To configure DC2 to start replicating data back to DC1, select the Configure Primary Geo cluster option by entering the corresponding number.
    5. Enter CCM IP address of the Geo Standby cluster (DC1).
    6. Enter the username to login to CCM of the Geo Standby cluster (DC1).
    7. Enter the password to login to CCM of the Geo Standby cluster (DC1) and click Enter.
    8. Note the IP address and PV names that you receive at the end of this process.
      Note:

      The script takes a few minutes to run, meanwhile it returns IP address and PV name.

      You must use this IP address and PV name for configuring the standby data center.

      After completing the above procedure, a backup job is triggered. You have to wait for backup job to complete and then proceed with the next step.

  2. On the DC1 to make it a standby, do the following on the Cluster Control Manager (CCM) console:
    1. Log in to the Cluster Control Manager (CCM) console in the DC1 cluster as the cust user.
    2. To switch to the root user, enter su.
    3. To disable firewall on DC1(standby), do the following:
    4. Run cluster_ssh.

      It displays the available nodes on the system. For example;

      1. node164182.puneccq.avaya.com

      2. node164183.puneccq.avaya.com

      3. node164184.puneccq.avaya.com

    5. Run the firewall config command for each node and exit.
      Note:

      The IP Address argument is the same IP provided as output from Geo Primary config.

    6. For example; Select [1]. 
      Last login: Tue May 31 21:10:27 2022 from 135.27.164.178
DeployType=Cluster Node
[ccmuser@node164182 ~]$ sudo firewall-cmd --permanent --direct --add-rule ipv4 filter OUTPUT 0 -o eth0 -d IP_Address -j ACCEPT
[ccmuser@node164182 ~]$ sudo systemctl restart firewalld
[ccmuser@node164182 ~]$ exit
  3. To run the Analytics Administration script as root user, use the following command:

    ccm release orca analytics

  4. To select the Geo/High Availability option, enter the corresponding number.
  5. To select the Geo options option, enter the corresponding number.
  6. To configure the standby cluster, select the Configure Standby Geo cluster option by entering the corresponding number.
  7. In the Proceed to Standby Geo cluster config field, enter y.
  8. At the prompt for IP address, enter the IP address and PV names that you noted from the DC2. See step 1h.
    Note:

    The script takes a few minutes to run.

    At this point, DC2 is primary and data is now replicating from DC2 to DC1.

  9. Return to the previous page by entering b.
  10. Quit the current page by entering q.
  11. To return to the main menu, type m and press Enter.
    Note:

    Once the above steps are completed successfully the Analytics database and MicroStrategy database will start to sync.

    The MSTR will not be accessible for standby data center.

    For more information, see Avaya Oceana® and Avaya Analytics™ Disaster Recovery document.