Cisco Prime Collaboration Provisioning Install and Upgrade Guide, 12.4

Perform Backup and Restore

Cisco Prime Collaboration Provisioning allows you to backup your data and restore it. You can schedule periodic backups using the Provisioning UI (Schedule Backup Using the Provisioning User Interface).

Note

In Cisco Prime Collaboration Provisioning 12.4, backup and restore requires mandatory password for enhanced security. Hence, after the upgrade to 12.4, all scheduled backup jobs from 12.x will fail. Once upgrade from 12.x to 12.4 is complete, you can cancel all the previously scheduled and saved jobs. The admin has to either reset the password and schedule the backup again or delete the scheduled backup job and reschedule it on 12.4. You can view the upgrade logs for the appropriate message.

There are two backup and restore scenarios; select the set of procedures that matches your scenario:

Backup and restore on a single machine, with the same installation or a new installation. For this scenario, see Schedule Backup Using the Provisioning User Interface.

Note

When backing up files, you should place the files on a different file server. Also, you should burn the backup data onto a CD.

Cisco Prime Collaboration Provisioning allows you to back up system data and restore it on a different system in the event of total system failure. To restore the backup from another system, the following prerequisites must be met:

Ensure that the server to which data is restored has the same MAC address as that of the system that was backed up (the IP address and the hostname can be different).
If you are unable to assign the MAC address of the original system (the one that was backed up) to another system, contact the Engineering Team for information on a new license file (for a new MAC address).
The procedure to backup and restore data on a different system is the same as the procedure to backup and restore data on the same system.

Back Up the Single-Machine Provisioning Database

This procedure requires that you have administrator level access to the Provisioning database (the PostgreSQL database).

Step 1	Login as troubleshooting user using SSH with port 22
Step 2	Navigate to the /opt/cupm folder and enter the following command: sudo ./cupm-app-service.sh stop
Step 3	Stop Apache, JBoss, and NICE Services using the following commands: ps -aef \| grep startcupm ps -aef \| grep nice kill -9 <startcupm process ID> kill -9 <nice process ID>
Step 4	Go to the directory using the command: cd /opt/postgres/pghome/bin
Step 5	Run the following command: sudo ./pg_dumpall -o -Upmadmin > /<backup_directory_name>/<backup_file_name> where, pmadmin—postgres user id backup_directory_name— For sudo user, the directory name is /home/<sudo User directory>. For Example: If sudo user is 'testuser' , directory name will be /home/testuser/ backup_file_name—Backup will be created with this file name.
Step 6	In a backup folder, make copies of the following files and directories: /opt/cupm/sep/dfc.properties /opt/cupm/sep/ipt.properties /opt/cupm/sep/dfc.keystore /opt/cupm/jboss/server/cupm/conf/login-config.xml /opt/cupm/jboss/server/cupm/deploy/dfc-ds.xml /opt/cupm/sep/ipt/.system/.pcprandom.key
Step 7	Start Apache, JBoss, and NICE Services using the following commands: cd /opt/cupm sudo ./cupm-app-service.sh start

Restore the Single-Machine Provisioning Database

Before You Begin

If you are restoring to a new installation, have the system with the new installation up and running before beginning this procedure. This procedure requires that you have administrator level access to the Provisioning database (the PostgreSQL database).

If you are restoring the database on a new system, you must verifying that the following ports are not being used by another application:

dfc.jboss.port=46008
dfc.postgres.port=5432
dfc.nice.rmi.registry.internal.port=46001
dfc.webport=80

If a port is being used by another application, you must change the port number to a vacant port. These settings are defined in the /opt/cupm/sep/dfc.properties file. If you accepted the default location during installation, the installation directory is /opt/cupm.

Step 1

Login as troubleshooting user using SSH with port 22.

Step 2

Navigate to the /opt/cupm folder and enter the following command to stop the application services like Apache, JBoss and NICE:

sudo ./cupm-app-service.sh stop

Step 3

Ensure whether the application services are stopped by using the following command:


ps -aef | grep startcupm
ps -aef | grep nice
kill -9 <startcupm process-id>
kill -9 <nice process-id>

To check whether the nice process is still holding on the postgres connection, enter the following command:
```
ps -aef
```
Look for the process: /opt/cupm/jvm/bin/java -server -classpath /opt/cupm/sep/lib/dom.jar:/opt/cupm/sep/lib/jaxbapi.jar:/opt/cupm/sep/lib/jaxb-impl.jar
If the process is running then enter the following command:
```
kill -9 <Process-Id found earlier>
```

Step 4

If you are restoring to the same installation, then proceed to the next step, if you are restoring to a new installation, paste the backed-up file (bak) into /mnt folder

Step 5

Go to the directory using the command:

cd /opt/postgres/pghome/bin

Step 6

Run the following command to restore the database:


sudo ./CUPM-restore.sh <username> <password> <backup_file_name with Absolute Path>

where, username is the username of the PostgreSQL administrator. The default administrator username is pmadmin; the password is same as you entered for globaladmin.

If you are getting the following error:

"dropdb: database removal failed: ERROR:  database "cupm" is being accessed by other users"

Do the following:

Check whether the nice process is still holding on the postgres connection by using the following command:
```
ps -aef
```
Look for the process: /opt/cupm/jvm/bin/java -server -classpath /opt/cupm/sep/lib/dom.jar:/opt/cupm/sep/lib/jaxbapi.jar:/opt/cupm/sep/lib/jaxb-impl.jar
If the process is running then enter the following command:
```
kill -9 <Process-Id found earlier>
```
Run the restore command again (./CUPM-restore.sh <username> <password> /mnt/<backup_file_name>).

Step 7

If you are restoring to the same installation, proceed to next step. If you are restoring to a new installation, copy back the following backed-up files. To copy the file using ssh, copy the files at /home/<sudo user directory> , and then copy using sudo cp <file_name> <Absoulte_Patch_file_name_to _ be_copied>. For example: If sudo user id is 'testuser', and file to be copied is 'dfc.properties' file at /home/testuser/, Using ssh, copy dfc.properties file at /home/testuser/ and then, copy the file again to mentioned directory using the command sudo cp /home/testuser/dfc.properties /opt/cupm/sep/dfc.properties

/opt/cupm/sep/dfc.properties
/opt/cupm/sep/ipt.properties
/opt/cupm/sep/dfc.keystore
/opt/cupm/jboss/server/cupm/conf/login-config.xml
/opt/cupm/jboss/server/cupm/deploy/dfc-ds.xml
/opt/cupm/sep/custom.properties
/opt/cupm/sep/passwordpolicy.properties

Note

To restore the random key, refer Restoring Random Key.

Step 8

Start Apache, JBoss, and NICE Services using the following commands:

cd /opt/cupm
sudo ./cupm-app-service.sh start

Restoring Random Key

The backup compressed file created by Backup Management (Administration > Backup Management) includes a copy of random key file.

Step 1	Copy the backed up directory to the server. Navigate to /opt/cupm/sep/ipt/.
Step 2	Create a directory .system (if it does not exist) using the mkdir command, else move to step 3.
Step 3	Navigate to /opt/cupm/sep/ipt/.system.
Step 4	Copy the following from backed up directory: cp <BACK UP DIR>/pcprandom.key .pcprandom.key cp .pcprandom.key .pcprandom.key.bkp touch .pcprandomconfigured

Schedule Backup Using the Provisioning User Interface

You can create periodic backups of Provisioning database using the Provisioning User Interface. You must be logged in as an administrator to perform backup. To create a backup of the Provisioning database:

Step 1

Choose Administration > Backup Management.

Step 2

In the Backup Management page, click New.

Step 3

Enter a backup title in the Create New Backup page.

Step 4

From the Backup Connection drop-down list, select SFTP, FTP, or Local to save your backup files.

If you select SFTP or FTP, provide the following details:

IP address of the server where the backup files need to be saved.

Path to the backup location and port details (for SFTP only).

Note

The backup location is relative to the specified SSH user home directory. The relative path must contain directory details(for example DIRNAME or DIRNAME 1 / DIRNAME 2), to avoid backup in root directory.

Username and password information. Testing the SFTP or FTP password is optional.

Note

Taking backup through SFTP on another PCP server in FIPS mode is not supported.

If you select Local, the backup files are saved to the CUPM local directory.

Note

Ensure that the destination path for SFTP, FTP, or Local is not given as “opt/backup”

Step 5

For a local backup, select the number of backup files you want to save on your local machine from the Backup History drop-down list.

The default value is 2. By default, you can save two recent backup files. You can save up to 9 recent backup files.

Step 6

Enter the scheduling details to schedule a backup.

The time displayed is the server browser time. The default recurrence type for a new backup job is None. After a backup job is created with default settings, the backup will start immediately.

Step 7

Enter email address to receive status notification for the scheduled backup. You can enter multiple email addresses separated with a comma.

Step 8

Click Save. The scheduled backup appears in the Backups table on the Backup Management page.

Step 9

Click Run Now, to run a backup immediately.

Prime Collaboration Provisioning enters maintenance mode before backup starts. A notification will be displayed for all logged-in users stating that the users will be logged out of Prime Collaboration Provisioning 10 minutes before the scheduled backup starts. Users must save their work and log out before the backup starts, else they will be logged out automatically, and will not be able to access Prime Collaboration Provisioning.

The backup table provides information on the status and history of each backup job. The Next Run Time option provides details on the next periodic schedule.

The Last Run Status column shows the status of the last run backup job. The status of a backup job can be Scheduled, In Progress, Success or Failed.

When a backup job reaches the scheduled time, the last run status changes to Scheduled. After entering into maintenance mode, that is after 10 minutes, the status will change from Scheduled to In Progress.

After the backup job is complete, the status is either Success or Failure.

To know about the history of any backup job, click Run History Count, and open the dialog box. You can view the start time, end time, status and file size of the backup. You can delete the run history logs. The backed up files are not deleted when the backup logs are deleted.

Managing Backup Jobs

With the scheduled jobs, you can:

Edit and Delete: The Edit and Delete options are disabled during Scheduled and In Progress states. You cannot edit or delete a backup job when the backup is in Scheduled or In Progress state. You can edit only one backup job at a time.
Cancel: You can cancel a running backup job which is in Scheduled or In Progress state only.

Book Title

Chapter Title

Results

Chapter: Backup and Restore Cisco Prime Collaboration Provisioning

Backup and Restore Cisco Prime Collaboration Provisioning

Perform Backup and Restore

Back Up the Single-Machine Provisioning Database

Restore the Single-Machine Provisioning Database

Restoring Random Key

Schedule Backup Using the Provisioning User Interface

Managing Backup Jobs

Was this Document Helpful?

Contact Cisco

Related Cisco Community Discussions