Geographic Redundancy Replication and data restoration

Last Updated : Nov 18, 2021 |

Geographic Redundancy Replication

The Geographic Redundancy feature provides the following replication mechanisms to ensure consistency of data between the primary and the secondary System Manager servers:

  • Database replication

  • File replication

  • LDAP (Directory) replication

The primary System Manager server continuously replicates the data with the secondary System Manager server. If the system does not replicate the data for a specific period of time that is configured in Services > Configurations > Settings > SMGR > HealthMonitor, the primary and the secondary System Manager servers raise alarms.

For more information on replication, see Administering Avaya Aura® System Manager.

Data restoration

In a Geographic Redundancy set up you must restore data when the primary System Manager server or the site fails. Restore the data from an old primary server or from the secondary server. In addition you may perform data restoration while replacing the primary or the secondary server, or while recovering the primary server from disaster. For more information on data restoration, see Administering Avaya Aura® System Manager.

Note:

When the primary server comes up after the server returns to the sunny day scenario, the alarms raised by the secondary server persist. You must manually clear the alarms raised by the secondary server in the rainy day scenario.