Backing Up with Server Shutdown

Use this task to do a backup the application database (Core DB), Oracle reporting database, and OCSDMDW reporting database on the shut down SDM server (cold backup) to a local directory path.

If you are using Oracle Communications Report Manager, you must shut down the Oracle BI Publisher database instance and Oracle Report Manager database instance (OCSDMDW) before you do the cold backup of the database. See the Report Manager Administrator Operations chapter in the Oracle Communications Report Manager Installation Guide for more information about stopping these database instances.
Login to the server as the nncentral user.
Change to the bin directory. For example:
```
cd /home/nncentral/AcmePacket/NNC8x/bin/
```
Enter the backupdbcold.sh script.

Note:
The backupdbcold.sh -- help script provides all of the arguments that you can use.
```
./backupdbcold.sh
```
- You can use the following arguments with this script:
  - -d —Use this argument to select a local directory that you want to store backup archives. For example:
```
./backupdbcold.sh -d/home/nncentral/AcmePacket/<Directory>/NNC8x_ColdBackup_yyyy_mm_dd_<number>_all.tar
```
  - -a, --all — Use this argument to run all backups and store them as a single archive.
```
./backupdbcold.sh --all
```
  - -c --core — Use this argument to backup the core application database and store it as an individual archive.
```
./backupdbcold.sh --core
```
  - -r --report — Use this argument to backup the reporting Oracle database and repository and store as an individual archive.
```
./backupdbcold.sh --report
```
  - -o --ocsdmdw — Use this argument to backup the (Oracle Communications Session Delivery Manager Data Warehouse (OCSDMDW) database and store as an individual archive.
```
./backupdbcold.sh --ocsdmdw
```
  - -ep, --excludePlugins —Use this argument to exclude archived plugin zip files from the resulting backup file. By default, the resulting backup file contains all product plugin installation zip files which were previously uploaded to SDM. You can override this behavior by entering this command.
```
./backupdbcold.sh --excludePlugins
```
After the script runs, the output displays a section called Backup Results. The output shows if the core SDM application database and reporting databases are successfully backed up to the default DatabaseBackup directory. The following example shows the directory on which the application database file was backed up:
```
/home/nncentral/AcmePacket/DatabaseBackup/NNC8x_ColdBackup_yyyy_mm_dd_<number>_all.tar
```
Note:
If you do not have reporting configured on the SDM server, the output shows that the reporting databases failed to be backed up.
Execute the startnnc.sh script.

Note:
With the introduction of Oracle Communications Session Delivery Manager, Release 8.0, you must select one server to start in the cluster only. Once this server is started and operational, you can start the other server(s) in the cluster.
```
./startnnc.sh
```
The console displays the number of services started. After all services have started, the system is ready for use. Do not attempt to log in until the console has indicated that the web servers are up.
If you are using Oracle Communications Report Manager and have shut down the Oracle BI Publisher database instance and Oracle Report Manager database instance (OCSDMDW), you must start them again. See the Report Manager Administrator Operations chapter in the Oracle Communications Report Manager Installation Guide for more information about starting these database instances.

The SDM plugin service always tries to synchronize itself with other cluster nodes when the server starts. This allows a node that was previously down, become current if it missed an upload, or an uninstall event.

Next Steps

Select Tools > Health Monitor and view the Heartbeat Summary table to check SDM cluster member node processes.
Begin using SDM. Use your web browser to navigate to the server login page by entering the host name or IP address, and port number in the web browser navigation bar. For example:
```
http://example.com:8080
```
In the login page, enter the administrator login name and password that you configured in the Configure User Account Passwords section.