Configuring Geographic Redundancy

Last Updated : Sep 21, 2023 |
Prolog information
Metadata
Keywords:
For resiliency, you can configure Geographic Redundancy from the pair of standalone System Manager servers.
Important:
  • During Geographic Redundancy configuration, the primary System Manager replicates data between primary and secondary System Manager servers. Therefore, ensure that the system maintenance activities such as backup, restore, and shutdown are not in progress.
  • After the Geographic Redundancy configuration is complete, the login credentials for the secondary System Manager becomes identical to the login credentials of the primary System Manager.
Before you begin
  • For the new System Manager installation, ensure that you change the default password for the system administrator user.
  • Ensure that you change CLI passwords on primary and secondary System Manager servers.
    Geographic Redundancy becomes nonoperational 60 days after the System Manager CLI password expires. You must set a new password on primary and secondary System Manager servers to make Geographic Redundancy operational again.
  • Ensure that the two System Manager servers meet the requirements that are defined in prerequisites for servers in the Geographic Redundancy setup.
  1. Log on to the standalone server's System Manager web console that you require to designate as the secondary server, and perform the following:
    1. On the System Manager web console, click ServicesGeographic RedundancyConfigure.
      ADDITIONAL INFORMATION:
      The Configure/Reconfigure connection with primary server window is displayed.
    2. Enter the primary System Manager server details in the fields.
    3. Click OK.
      ADDITIONAL INFORMATION:
      The configuration process takes about 30 minutes. However, the duration can vary depending on the size of the data on the primary System Manager server.
      ADDITIONAL INFORMATION:
      Note:
      You cannot access the web console as the server becomes unavailable. 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.
  2. Perform one of the following actions to view the status of Geographic Redundancy configuration during the restart of the two application servers:
    1. Log on to the primary System Manager server web console.
    2. Click ServicesGeographic Redundancy.
      ADDITIONAL INFORMATION:
      The GR Health page is displayed.
    3. Refresh the page. If Enable is available, the configuration is complete.
    ADDITIONAL INFORMATION:
    Note:
    Log off and log on to the primary System Manager server to view the updated status of Geographic Redundancy health.
  3. Log in to the secondary System Manager server as system administrator by using the command line interface.
  4. Type tail –f /home/ucmdeploy/quantum/autoReconfig.log.
    ADDITIONAL INFORMATION:
    The system displays the progress during the restart of the two application servers. When the second application server restart completes, the following messages are displayed:
    ADDITIONAL INFORMATION:
    • SMGR :: operationStatus=success
    • SMGR :: Quantum has been successfully configured as a secondary.
Next steps
On the primary System Manager server web console, enable the Geographic Redundancy replication.
Related links
Prerequisites for Geographic Redundancy setup