Reconfiguring Geographic Redundancy

Last Updated : Jun 09, 2023 |

Before you begin

  • Ensure that the two System Manager servers meet the requirements that are defined in Prerequisites for the Geographic Redundancy setup.

  • Create the snapshot of the primary and secondary System Manager servers.

    Note:

    Delete the snapshot after the configuration of Geographic Redundancy.

  • Log on to System Manager web console of the secondary server.

About this task

For resiliency, from the pair of standalone System Manager servers, you can configure Geographic Redundancy.

Important:

During the configuration of Geographic Redundancy, the primary System Manager replicates the data between the primary and the secondary System Manager servers. Therefore, ensure that the system maintenance activities such as backup, restore, and shutdown are not in progress.

Procedure

  1. On the System Manager web console, click Services > Geographic Redundancy.
  2. Click Reconfigure.
  3. In the dialog box, provide the details of the primary System Manager server in the following fields:

    • Primary Server Username

      Type the admin user name that you use to log on to the primary System Manager web console.

    • Primary Server Password

      Type the admin password that you use to log on to the primary System Manager web console.

    • Primary Server IP

    • Primary Server FQDN

  4. Click OK.
    Note:

    Because the server becomes unavailable, you cannot gain access to the web console. Wait until the process is complete before you continue with the next step.

    The server that you configured becomes the secondary server and the other standalone server becomes the primary System Manager server.

  5. To view the status of the Geographic Redundancy configuration during the restart of the two application servers, perform one of the following:

    • Log on to the web console of the primary System Manager server and perform the following:

      1. On the System Manager web console, click Services > Geographic Redundancy.

      2. Refresh the GR Health page.

        If Enable is available, the configuration is complete.

        Note:

        Log off and log on to the primary System Manager server to view the updated status of Geographic Redundancy health.

    • Log in to the secondary System Manager server as system administrator by using the command line interface and perform the following:

      1. Type tail –f /home/ucmdeploy/quantum/autoReconfig.log.

        The system displays the progress during the restart of the two application servers. When the second application server restart completes, the system displays the following messages: 
                   SMGR  ::  operationStatus=success

           SMGR  ::  Quantum has been successfully configured as a secondary.

Next Steps

On the primary System Manager web console, enable the Geographic Redundancy replication.