For the new installation of System Manager, 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.
60 days after the System Manager CLI password expires, Geographic Redundancy becomes nonoperational. You must set a new password on primary and secondary System Manager servers for Geographic Redundancy to become operational again.
Ensure that the two System Manager servers meet the requirements that are defined in Prerequisites for the Geographic Redundancy setup.
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.
After the Geographic Redundancy configuration is complete, the credentials used for logging in to the secondary System Manager becomes identical to the login credentials of the primary System Manager.
Procedure
Log on to the System Manager web console of the standalone server that you require to designate as the secondary server and perform the following:
On the System Manager web console, click Services > Geographic Redundancy.
Click Configure.
In the dialog box, provide the details of the primary System Manager server in the following fields:
Primary Server Username
Enter the system administrator user name that you use to log on to the primary System Manager server.
Primary Server Password
Enter the system administrator password that you use to log on to the primary System Manager server.
Primary Server IP
Primary Server FQDN
Click OK.
The configuration process takes about 30 minutes. However, the duration might vary depending on the size of the data on the primary System Manager server.
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.
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:
On the System Manager web console, click Services > Geographic Redundancy.
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:
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 web console of the primary System Manager server, enable the Geographic Redundancy replication.
