8.3 Prerequisites
Before performing any fault recovery procedure, ensure that the following prerequisites are met:
- cnDBTier must be in a healthy state and available on multiple sites
along with Policy. To check the cnDBTier status, perform the following steps:
- Run the following command to ensure that all the nodes are
connected:
ndb_mgm> show
- Run the following command to check the pod status:
kubectl get pods -n <namespace>
If the pod status is
Running
, then the cnDBTier is in healthy state. - Run the following command to check if the replication is up:
mysql> show slave status\G
In case there is any error, see Fault Recovery chapter in Oracle Communications Cloud Native Core, cnDBTier Installation and Upgrade Guide.
- Run the following command to check which cnDBTier is having
ACTIVE replication to take backup:
select * from replication_info.DBTIER_REPLICATION_CHANNEL_INFO;
- Run the following command to ensure that all the nodes are
connected:
- Automatic backup must be enabled on cnDBTier. Enabling automatic backup
helps in achieving the following:
- Restore stable version of the network function database
- Minimize significant loss of data due to upgrade or roll back failures
- Minimize loss of data due to system failure
- Minimize loss of data due to data corruption or deletion due to external input
- Migrate database information for a network function from one site to another
- The following files must be available for fault recovery:
- Custom values file
(
occnp-custom-values-<release_number>
) - Helm charts
(
occnp-<release_number>.tgz
) - Secrets and Certificates
- RBAC resources
- Custom values file
(
Note:
For details on enabling automatic backup, see Fault Recovery section in Oracle Communications Cloud Native Core, cnDBTier (cnDBTier) Installation Guide.