5 Disaster Recovery Scenarios
This chapter describes the disaster recovery procedures for different recovery scenarios.
Scenario 1: Deployment Failure
This section describes how to recover OCNADD when the OCNADD deployment corrupts.
For more information, see Restoring OCNADD.
Scenario 2: cnDBTier Corruption
This section describes how to recover the cnDBTier corruption. For more information, see Oracle Communication Cloud Native Core DBTier Disaster Recovery Guide. After the cnDBTier recovery, restore the OCNADD database from the previous backup.
To restore the OCNADD database, execute the procedure Create OCNADD Restore Job by setting BACKUP_ARG to DB.
Scenario 3: Database Corruption
This section describes how to recover from the corrupted OCNADD database.
Perform the following steps to recover the OCNADD configuration database (DB) from the corrupted database:
- Retain the working ocnadd backup by following Obtain the OCNADD Backup files procedure.
- Drop the existing Databases by accessing the MySql DB.
- Perform the Copy and Restore the OCNADD backup procedure to restore the backup.
Scenario 4: Site Failure
This section describes how to perform disaster recovery when the OCNADD site has software failure.
Perform the following steps in case of a complete site failure:
- Run the Cloud Native Environment (CNE) installation procedure to install a new Kubernetes cluster. For more information, see Oracle Communications Cloud Native Environment Installation Guide.
- Run the cnDBTier installation procedure. For more information, see Oracle Communications Cloud Native Core DBTier Installation and Upgrade Guide.
- For cnDBTier disaster recovery, take a data backup from an older site and restore it to a new site. For more information about cnDBTier backup, see "Create On-demand Database Backup" and to restore the database to a new site, see "Restore DB with Backup" in Oracle Communications Cloud Native Core DBTier Disaster Recovery Guide.
- Restore OCNADD. For more information, see Restoring OCNADD.