Cisco Prime Collaboration Provisioning Guide, 9.5
Performing Backup and Restore
Downloads: This chapterpdf (PDF - 225.0KB) The complete bookPDF (PDF - 4.05MB) | Feedback

Table Of Contents

Performing Backup and Restore

Backing Up the Single-Machine Provisioning Database

Restoring the Single-Machine Provisioning Database

Backing Up Provisioning for a Distributed Database

Restoring Provisioning for a Distributed Database

Scheduling Backup Using the Provisioning User Interface

Editing and Deleting a Backup Job

Canceling a Backup Job


Performing Backup and Restore


Prime Collaboration allows you to make a backup of your data and restore it. You can schedule periodic backups using the Prime Collaboration Provisioning UI, or run backup commands manually by logging in to the system as an admin user (CLI user). However, you must manually run restore commands by logging in to the system as an admin user (CLI user).

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 Backing Up the Single-Machine Provisioning Database and Restoring the Single-Machine Provisioning Database.

Backup and restore for a distributed database scenario, for the same installation, a new installation with the same IP address, or a new installation with a new IP address. For this scenario, see Backing Up Provisioning for a Distributed Database and Restoring Provisioning for a Distributed Database.


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.


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 that the application server to which data is restored has the same MAC adddress 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 Cisco TAC 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.

Backing Up the Single-Machine Provisioning Database

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


Step 1 Stop Apache, JBoss and NICE Services by using the following commands:

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

Step 2 Go to the directory:

/opt/postgres/9.0/bin.

Step 3 Run the following command:

./pg_dumpall -o -Upmadmin > /<backup_directory_name>/<backup_file_name>
 
 

where,

pmadmin—postgres user id

backup_directory_name—Name of the directory where you want to place the backup file

backup_file_name—Backup will be created with this file name.

Step 4 Backup the following files:

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

Step 5 To restart Apache, JBoss and NICE Services:

a. Go to /opt/cupm folder.

b. Execute ./cupm-app-service.sh start


Restoring the Single-Machine Provisioning 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).

Before You Begin

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 Stop Apache, JBoss and NICE Services, 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 2 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 into /mnt folder

Step 3 Go to the directory:

cd /opt/postgres/9.0/bin

Step 4 Run the following command:

./CUPM-restore.sh <username> <password> /mnt/<backup_file_name>
 
 

Where username is the username of the PostgreSQL administrator. The default administrator username is pmadmin.

Where password is the password provided for globaladmin.

Step 5 If you are restoring to the same installation, proceed to the next step. If you are restoring to a new installation, copy back the following backed-up files:

/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

Step 6 To restart Apache, JBoss and NICE Services:

a. Go to /opt/cupm folder.

b. Execute ./cupm-app-service.sh start.


Backing Up Provisioning for a Distributed Database

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


Step 1 In the application server, stop Apache, JBoss and NICE Services by using the following commands:

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

Step 2 In the database server, go to the directory:

cd /opt/postgres/9.0/bin.

Step 3 Run the following command:

./pg_dumpall -o -Upmadmin > /<backup_directory_name>/<backup_file_name>
 
 

where,

pmadmin—postgres user id

backup_directory_name—Name of the directory where you want to place the backup file

backup_file_name—Backup will be created with this file name.

Step 4 In the application server, backup the following files:

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

Step 5 To restart Apache, JBoss and NICE Services:

a. Go to /opt/cupm folder.

b. Execute ./cupm-app-service.sh start.


Restoring Provisioning for a Distributed Database

If you are restoring to a new installation, either with the same or a new IP address, 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).


Note 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 /sep/dfc.properties file. (If you accepted the default location during installation, the installation directory is /opt/cupm.)

Also, you will need to change the system name in one of the following settings:

dfc.postgres.host=<system name> (If the database is on one system.)

dfc.postgres.hostlist=<system names> (If the database is on multiple systems.)


Restoring Database in the database server


Step 1 In the application server, stop Apache, JBoss and NICE Provisioning Services, 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 2 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 into /mnt folder

Step 3 Go to the directory:

cd /opt/postgres/9.0/bin

Step 4 Run the following command:

./CUPM-restore.sh <username> <password> /mnt/<backup_file_name>

Where

username is the username of the PostgreSQL administrator. The default administrator username is pmadmin.

password is the password provided for globaladmin.

Step 5 If you are restoring to the same installation, proceed to the next step. If you are restoring to a new installation, copy back the following backed-up files:

/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

Step 6 To restart Apache, JBoss and NICE Services:

a. Go to /opt/cupm folder.

b. Execute ./cupm-app-service.sh start.


Restoring Database in the application server


Step 1 If you are restoring to the same installation, proceed to the next step. If you are restoring to a new installation, copy back the following backed-up files:

/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

Step 2 Update the IP address of the database server (postgres host) in opt/cupm/sep/dfc.properties

Step 3 Update the IP address of database server (postgres host) in opt/cupm/jboss/server/cupm/deploy/dfc-ds.xml

Step 4 To restart Apache, JBoss and NICE Services:

a. Go to /opt/cupm folder.

b. Execute ./cupm-app-service.sh start.


Scheduling Backup Using the Provisioning User Interface

You can create periodic backups of the Provisioning database using the Prime Collaboration Provisioning user interface. You must be logged in as an administrator to perform a backup.

To create a backup of the Provisioning database:


Step 1 Choose Administration > System Maintenance > 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.

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

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

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

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

b. If you select local, provide only the location where you want to save the backup files on your local machine.

Step 5 For a local backup, choose the number of backup files you want to save on your local machine from the Backup History drop-down list. You can save up to nine recent backup files. The default is two.

Step 6 Enter the scheduling details to schedule a backup:

a. Start Time—Click to enter the start date and time in the yyyy/MM/dd and hh:mm AM/PM formats, respectively.

b. Click the date picker if you want to select the start date and time from the calendar. The time displayed is the client browser time. The scheduled periodic backup runs at this specified time.

c. Recurrence—Click None, Daily, Weekly, or Monthly to specify the backup period.

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 one or more comma-separated email addresses to receive a status notification for the scheduled backup.

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

Step 9 To run a backup immediately, click Run Now.


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

The backups 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.


Note Deleting run history logs will not delete the backed up files.


Editing and Deleting a Backup Job

You can edit and delete the backup schedules you have created.


Note The Edit and Delete options are disabled for Scheduled and In Progress states, and you cannot delete a backup job at those times.



Step 1 Choose Administration > System Maintenance > Backup Management.

Step 2 Select any scheduled backup from the Backups table. You can edit only one backup job at a time.

Step 3 Click Edit.

Step 4 In the Edit Backup window, make the necessary changes and click Save.


To delete a backup:


Step 1 Select any scheduled backup job from the Backups table.

Step 2 Click Delete. The backup job is deleted.


Canceling a Backup Job

You can cancel a running backup job which is in Scheduled or In Progress state only.


Step 1 Choose Administration > System Maintenance > Backup Management.

Step 2 Select any scheduled backup from the Backups table.

Step 3 Click Cancel.