This section explains the following:
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:
![]() 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. |
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.
This procedure requires that you have administrator level access to the Provisioning database (the PostgreSQL database).
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:
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> | ||
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. "dropdb: database removal failed: ERROR: database "cupm" is being accessed by other users" Do the following: | ||
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
| ||
Step 8 | Start Apache, JBoss, and NICE Services using the following commands:
cd /opt/cupm sudo ./cupm-app-service.sh start |
The backup compressed file created by Backup Management (Administration > Backup Management) includes a copy of random key file.
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:
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.
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.