6.1 Overview

You must take database backup and restore it either on the same or a different cluster. It uses the NEF database to run any command or follow instructions.

Note:

This chapter describes the scenario-based procedures to restore NEF database only. To restore all the databases that are part of cnDBTier, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide available on My Oracle Support.

Database Model of NEF

NEF database consists of configuration data and state data. The details are as follows:

• Configuration Data: The configuration data is exclusive for a given site. Thus, an exclusive logical database is created and used by the site to store its configuration data. An operator can perform configuration operations of NEF data in respective cnDBTier using the Configuration Management service.
• State Data: The state data is the NEF application data, which is required for service operations.

NEF has the following databases created:

• NEF application database: This database consists of tables used by the application to perform the functionality of the NEF network function.
• NEF network database: This database consists of tables used by NEF to store the network details like system details and database backups.
• NEF common configuration database: This database consists of tables used by common configuration.

Performing cnDBTier Fault Recovery procedures to restore cnDBTier (through automated backup file or on-demand backup from mate site), brings back configuration along with the state data captured during backup. Thus policies and other configuration will get restored, along with state data.

Note:

If an older backup file is used to restore a site, then the stale sessions cleanup is performed automatically.