Reversing data replication when the DC2 is the primary

Last Updated : Aug 09, 2023 |

About this task

Once the cause of the DC1 failure has been resolved and fixed, you can switch back from DC2 as the primary to DC1. However, before doing that, DC1 first needs to receive data replication from DC2.

Note:
  • If testing, you must only perform this process during a maintenance window.

Procedure

  1. On the DC2, do the following on the Cluster Control Manager (CCM) console:
    1. Run the Analytics Administration script as root user, use the following command:

      ccm release orca analytics

    2. Select Geo/High Availability by pressing the corresponding number.
    3. Select Geo options by pressing the corresponding number.
    4. Select Configure Primary Geo cluster by pressing the corresponding number.
    5. Make a note of the IP address and PV name that you receive at the end of this process. You need these values later in this process. The script takes a few minutes to run.
  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 of the DC1 cluster as the cust user.
    2. Switch to the root user by entering su.
    3. Run cluster_ssh. This displays the available nodes, for example:
      1. node164182.puneccq.avaya.com

      2. node164183.puneccq.avaya.com

      3. node164184.puneccq.avaya.com

    4. Run the firewall config command for each node and exit. For example; Select [1].
      Note:

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

      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. Quit the current page by entering q.
  4. To run the Analytics Administration script as root user, use the following command:
  5. Select Geo/High Availability by pressing the corresponding number.
  6. Select Geo options by pressing the corresponding number.
  7. Select Configure Standby Geo cluster by pressing the corresponding number.
  8. In the Proceed to Standby Geo cluster config field, enter y.
  9. At the prompt for IP address, enter the IP address and PV names that you noted from the secondary data center.
    Note:

    The script will take few minutes to run.

  10. Return to the previous page by entering b.
  11. Quit the current page by entering q.
  12. Return to the main menu by entering m.
    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 the standby data center.

Next Steps

  • At this stage, DC2 is still the primary but now with data being replicated to DC1. To return the DC1 to the primary role, repeat the switch over process (Switching over from the primary to the secondary data center) but with the data centers reversed. That is, promote DC1 to be the primary and configure DC2 to be the Standby Geo for DC1.