1. Oracle Communications Diameter Signaling Router Cloud Disaster Recovery Guide
  2. 4.0 Procedure Preparation

16 4.0 Procedure Preparation

Disaster recovery procedure execution is dependent on the failure conditions in the network. The severity of the failure determines the recovery scenario for the network. Use Table 4: Recovery Scenarios below to evaluate the correct recovery scenario and follow the procedure(s) listed to restore operations.

Note:

A failed server in disaster recovery context refers to a server that has suffered partial or complete software failure to the extent that it cannot restart or be returned to normal operation and requires intrusive activities to re-deploy base software.

Table 16-1 Procedure Preparation

Recovery Scenario Failure Condition Section
1
  • All NOAM servers failed.
  • All SOAM servers failed.
  • MP servers may or may not be failed.
 Section 5.1.1 Recovery Scenario 1 (Complete Server Outage).
2
  • At least 1 NOAM server is intact and available.
  • All SOAM servers failed.
  • MP servers may or may not be failed.
 Section 5.1.2 Recovery Scenario 2 (Partial Server Outage with one NOAM server intact and both SOAMs failed).
3
  • All NOAM servers failed.
  • At least 1 SOAM server out of Active, StandBy, and Spare is intact and available.
  • MP servers may or may not be failed.
 Section 5.1.3 Recovery Scenario 3 (Partial Server Outage with all NOAM servers failed and one SOAM server intact).
4
  • At least 1 NOAM server is intact and available.
  • At least 1 SOAM server out of Active, StandBy, and Spare is intact and available.
  • 1 or more MP servers have failed.
 Section 5.1.4 Recovery Scenario 4 (Partial Server Outage with one NOAM server and one SOAM server intact).
5
  • Both NOAM servers failed in Primary site.
  • At least 1 SOAM server out of Active, StandBy, and Spare is intact and available.
  • DR-NOAM is available
 Section 5.1.5 Recovery Scenario 5 (Partial Server Outage with all NOAM servers failed with DR-NOAM available).
6
  • Server is intact.
  • Database gets corrupted on the server.
  • Replication is occurring to the server with corrupted database.
 Section 5.1.6.1 Recovery Scenario 6: Case 1.
6.1
  • Server is intact.
  • Database gets corrupted on the server.
  • Latest Database backup of the corrupt server is NOT present.
  • Replication is inhibited (either manually or because of comcol upgrade barrier).
 Section 5.1.6.2 Recovery Scenario 6: Case 2.