Table of Contents
- Title and Copyright Information
- What's New in this Guide
- 1 Introduction
-
2
Recovery Scenarios
- 2.1 Complete Server Outage (All Servers)
- 2.2 Partial Server Outage with One NOAM Server Intact and both SOAMs Failed
- 2.3 Partial Server Outage with both NOAM Servers Failed and One SOAM Server Intact
- 2.4 Partial Server Outage with NOAM and one SOAM Server Intact
- 2.5 Partial Server Outage with both NOAM Servers Failed with DR-NOAM Available
- 2.6 Partial Service Outage with Corrupt Database
- 3 Procedure Overview
-
4
Disaster Recovery
Procedure
-
4.1
Recovering and Restoring System
Configuration
- 4.1.1 Recovery Scenario 1 (Complete Server Outage)
- 4.1.2 Recovery Scenario 2 Partial Server Outage with One NOAM Server Intact and Both SOAMs Failed
- 4.1.3 Recovery Scenario 3 (Partial Server Outage with all NOAM servers failed and one SOAM server intact)
- 4.1.4 Recovery Scenario 4 (Partial Server Outage with one NOAM server and one SOAM server intact)
- 4.1.5 Recovery Scenario 5 (Partial server outage with both NOAM servers failed with DR-NOAM Available)
- 4.1.6 Recovery Scenario 6 (Database Recovery)
-
4.1
Recovering and Restoring System
Configuration
- 5 Resolving User Credential Issues after Database Restore
- 6 IDIH Disaster Recovery
- A.1 DSR Database Backup
- A.2 Inhibit A and B Level Replication on C-Level Servers
- A.3 Un-Inhibit A and B Level Replication on C-Level Servers
- A.4 Inhibit A and B Level Replication on C-Level Servers (When Active, Standby and Spare SOAMs are lost)
- A.5 Un-Inhibit A and B Level Replication on C-Level Servers (When Active, Standby and Spare SOAMs are lost)
- A.6 Workarounds for Issues not fixed in this Release