Recovering the primary System Manager server from disaster

Last Updated : Nov 21, 2021 |

Perform the system recovery process when the primary System Manager server becomes unavailable and when you do not have a backup to restore on the new System Manager server.

About this task

Important:

During the system recovery of Geographic Redundancy, the active secondary System Manager server copies the data from the secondary System Manager server to the primary System Manager server. Therefore, ensure that the system maintenance activities, such as, backup, restore, and shutdown are not in progress.

Before you begin

For fresh installation of System Manager, change the default password for the system administrator user.
Ensure that the two System Manager servers meet the requirements that are defined in Prerequisites for the Geographic Redundancy setup.

Procedure

Activate the secondary System Manager server.
Create a backup of the secondary System Manager server.
View and verify the virtual FQDN that is configured on the secondary System Manager server by using one of the following:
- From the virtual FQDN configured in the System Manager certificate, do one of the following:
  - On Firefox, click the icon on the address bar of the browser. Click More Information > View Certificate > Details. In the Certificate Details area, click Certificate > Extensions > Certificate Subject Alt Name. The system displays two values for DNS Name. The first entry is the virtual FQDN.
  - On Chrome, click Not secure on the address bar, and then click Certificate > Details > Subject Alternative Name. The first entry for DNS Name is the virtual FQDN.
  - On Edge, click Not secure on the address bar, and then click Show certificate symbol > Details > Subject Alternative Name. The first entry for DNS Name is the virtual FQDN.
- From the command line interface, log in to the secondary System Manager server, and check the virtualFQDN property value in the $MGMT_HOME/infra/conf/smgr-properties.properties file.
On the new server, install the System Manager template that you later designate as primary server with the same virtual FQDN that you obtained in Step 3.
Log on to the web console of the new System Manager server to change the default password.
For Release 7.1 and later, perform the steps provided in the Disaster recovery prerequisites section.
Log in to the command line interface of the newly created primary System Manager with administrator privilege CLI user credentials, and perform the following:
1. Perform one of the following:
  - For Releases 6.3.1 and 6.3.0, type sh $MGMT_HOME/geo/bin/rundisasterrecovery.sh <peer fqdn> <peer ip> <peerNodesmgrUserId> <peerNodesmgrPassword>.
  - For Release 6.3.2 and later, type sh $MGMT_HOME/geo/bin/rundisasterrecovery.sh —FQDN <secondary fqdn> —IP <secondary IP> —ID <secondary System Manager web console system admin user name> —PASS <secondary System Manager web console system admin password>.
  - For Release 7.1 and later, type sudo -u admin $MGMT_HOME/geo/bin/rundisasterrecovery.sh -FQDN <SECONDARY_FQDN> -IP <Secondary_Host_IPAddress> -ID admin -PASS <UIPassword>
  Release 6.3.x example: $MGMT_HOME/geo/bin/rundisasterrecovery.sh –FQDN psvdbf24.dr.sdr.com –IP 144.235.244.244 –ID systemadmin –PASS System$567.
  
  Release 7.1.x example: sudo -u admin $MGMT_HOME/geo/bin/rundisasterrecovery.sh -FQDN sit2.smgrdev.avaya.com -IP 2a07:2a42:adc0:1d::87 -ID admin -PASS System$675
  
  The recovery process starts and takes about 40 minutes. The command runs in the background and the system creates nohup logs in the directory from where you run the rundisasterrecovery.sh command, which you can tail.
2. Type one of the following:
  - tail -f $AVAYA_LOG/mgmt/geo/disasterRecoveryScript.log
  - tail -f nohup.out
To quit the tail command, press Control+C.

When the recovery process is complete, the system displays the message Disaster Recovery has completed JBoss will be restarted, may take up to 15 minutes. The system configures System Manager servers as a Geographic Redundancy pair with the secondary data on the primary System Manager server.
Deactivate the secondary System Manager server.
Restore the data from the primary System Manager server.
Enable the Geographic Redundancy replication.

The system starts working in the normal operational mode.

Send Feedback

AVAYA DOCUMENTATION CENTER

No results found