This chapter describes the requirements and procedures for backing up and restoring the critical data that ensures that Oracle Communications Evolved Communications Application Server (OCECAS) can successfully recover from server failure or other disaster.
OCECAS incorporates Oracle WebLogic application server and Oracle Communications Converged Application Server (OCCAS) and uses the following data repositories:
Oracle Database Standard and Enterprise Editions
NoSQL database
The requirements for backing up and restoring OCECAS, therefore, generally follow the guidelines and best practices that are recommended for Oracle WebLogic Server, Oracle Communications Converged Application Server, and Oracle Database, to be able to successfully recover from server failure or other disaster.
For information on properly configuring WebLogic Server to avoid failures and to recover, if necessary, see "Avoiding and Recovering From Server Failures" in Fusion Middleware Manager Startup and Shutdown for Oracle WebLogic Server.
For information on properly configuring Oracle Communications Converged Application Server to avoid failure and recover, if necessary, see the following chapters in Oracle Communications Converged Application Server Administrator's Guide:
For information about backing up and restoring Oracle database, see the section on backup and recovery in the Oracle Database Documentation Library.
For Oracle Enterprise Database 12c, see "Backup and Recovery User's Guide":
http://docs.oracle.com/cd/E16655_01/nav/portal_4.htm#backup_and_recovery
See also, "Backup and Recovery Reference":
http://docs.oracle.com/cd/E16655_01/backup.121/e17631/toc.htm
Backing up and restoring OCECAS data consists of backing up the following data sources and restoring them following a system failure:
NoSQL database, if you are using it store subscriber data
The Ocecas_home directory, including its subdirectories, in each of your OCECAS domains. The Ocecas_home directory is created during installation and serves as a repository for system files.
EDRs
You use the administration console to specify the location of EDRs in the SDC management domain under Evolved Communications -> Archive directory location.
Subscriber definitions that are maintained by Oracle Platform Security Services
If you choose to use an external LDAP system, such as Oracle Internet Directory that is part of Oracle Identity Manager, you will need backup this data and restore it in the event of failure.
If you have chosen to store subscriber definitions in the database, they will be backed up and restored as part of the database backup and restore processes.
For information on backing up and recovering the NoSQL database, as well as other NoSQL administrative tasks, see NoSQL Database Administrator's Guide.
For information on backing up the Ocecas_home directory, see "Creating a Backup of Your Current OCECAS Installation" in Oracle CommunicationsEvolved Communications Application Server Installation Guide.
Store your backup data in a location that will not be compromised by an OCECAS system failure.