Cisco Prime Collaboration Administration Guide, 9.5
Backup and Restore
Downloads: This chapterpdf (PDF - 217.0KB) The complete bookPDF (PDF - 876.0KB) | Feedback

Table Of Contents

Performing Backup and Restore

Overview of Backup and Restore

Scheduling a Backup Using the Prime Collaboration User Interface

Scheduling a Backup Using the CLI

Backup and Restore Assurance Data

Creating a Repository on an FTP, SFTP, or TFTP Server

Backing Up Data

Restoring Data on the Same System

Restoring Data on a Different System

Listing the Repository Data

Checking the Backup History


Performing Backup and Restore


Prime Collaboration allows you to back up and restore your data. You can schedule periodic backups using the Prime Collaboration user interface, 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.


NoteCLI is supported only through SSH; Telnet is not supported. The port used for Prime Collaboration Assurance is 26; for Prime Collaboration Provisioning it is 22.

The application stop cpcm command takes 10 minutes to complete execution and application start cpcm command takes 10 to15 minutes to complete execution.


Overview of Backup and Restore

Although the Prime Collaboration Assurance and Prime Collaboration Provisioning applications'UIs are converged, you must perform backups on the respective Assurance and Provisioning servers.

Prime Collaboration Assurance backup and restore are covered in this guide. For information about Prime Collaboration Provisioning backup and restore, see `Provisioning Database Backup and Restore' in Cisco Prime Collaboration 9.5 Provisioning Guide.

Prime Collaboration Assurance uses the following purge policy:

All session and endpoint statistics data older than one day are purged. For more details, see "Monitoring Sessions" in Cisco Prime Collaboration 9.5 Assurance Guide.

All session and troubleshooting details older than 14 days are purged every hour. For more details, see "Video Endpoints" in Cisco Prime Collaboration 9.5 Assurance Guide.

Call quality event history and audio/video phone audit report data older than 30 days are purged. For more details, see "Voice Reports" inCisco Prime Collaboration 9.5 Assurance Guide.

Cleared alarms and events that are older than 14 days are purged every hour. If an alarm is purged, all associated events are also purged. Active events and alarms are not purged. For more details, see Cisco Prime Collaboration 9.5 Assurance Guide.

Jobs that are older than 14 days and have a status of completed, failed, or cancelled are purged every hour.

The backup and restore service allows you back up the database, configuration files, and log files to either a remote location or a local disk. Files in the following folders are backed up by the backup service:

Folder Name
Type of Data

emms database

Database

cpcm/conf

Configuration files

cpcm/export

Troubleshooting and endpoint utilization reports

cpcm/logs and tomcat/logs

Assurance application and Tomcat log files

jre/lib/security

Keystore files



Note The data backup may take a long time (up to12 hours), depending on the number of managed devices in the Prime Collaboration Assurance server. It is recommended that you schedule backups during the non-business hours, because, this operation will severely slow down the Prime Collaboration Assurance UI performance.


Scheduling a Backup Using the Prime Collaboration User Interface

You can schedule and run backup for both Assurance and Provisioning from the user interface. You can use SFTP, FTP, or a local connection to create the backup.

You must be logged in as an administrator to perform backup.

To create a new backup job:


Step 1 Choose Administration > Backup Management.

Step 2 In the Backup Management page, click New.

Step 3 Enter a name for the backup job.

If you do not specify a backup name, the Backup Title field is defaulted with a date stamp.

Step 4 Select a backup category and enter the connection settings. (You can use SFTP, FTP, or local connection to create the backup.)

Step 5 Do one of the following:

If you are using a local connection, specify the location at which to save the backup files on your local machine. (You can specify up to nine backup files to be saved using the Backup History drop-down list; the default is two.)

If you selected SFTP or FTP, provide the required information and click Test to test the connection using the credentials.

Step 6 Specify the backup start time and recurrence interval. (The time displayed in the date picker is the client browser time.)

Step 7 (Optional) Enter the e-mail IDs to which the backup status notification are to be sent. You must separate the e-mail IDs using a comma.

Step 8 Click Save.

The scheduled backup job is listed in the Backup Management page.

You can click Run Now to run the backup immediately.



Note You cannot take a backup of Analytics from the Backup management UI. Use CLI to take backup of Analytics.


Scheduling a Backup Using the CLI

Backup and Restore using the CLI can be performed in the following ways:

Make a backup of data in a system and restore it on the same system. For more information, see Backup and Restore Assurance Data.

Make a backup of data in a system and restore it on a different system. For more information, see Restoring Data on a Different System.

Backup and Restore Assurance Data

Creating a Repository on an FTP, SFTP, or TFTP Server

You must create a repository before backing up the data. By default, the backup service creates a *.tar.gpg file under the configured repository. The backed-up file is in a compressed format. The repository can be on CD-ROM, disk, HTTP, FTP, SFTP, or TFTP.

To create a repository:


Step 1 Log in to the Prime Collaboration Assurance server with the account that you created during installation. The default login is admin.

Step 2 Enter the following commands to create a repository on a disk:

admin# config t
admin(config)# repository RepositoryName
admin(config-Repository)# url ftp://ftpserver/directory
admin(config-Repository)# user UserName password {plain | hash} Password
admin(config-Repository)# exit
admin(config)# exit

Where:

RepositoryName is the location to which files should be backed up. This name can contain a maximum of 30 alphanumeric characters.

ftp://ftpserver/directory is the FTP server and the directory on the server to which the file is transferred. You can also use SFTP, HTTP, disk, or TFTP instead of FTP.

UserName and {plain | hash} Password are the username and password for the FTP, SFTP, or TFTP server. hash specifies an encrypted password, and plain specifies an unencrypted plain text password.

For example:

admin# config t
admin(config)# repository tmp
admin(config-Repository)# url ftp://ftp.cisco.com/incoming
admin(config-Repository)# user john password plain john!23
admin(config-Repository)# exit
admin(config)# exit


Backing Up Data

After creating the repository, log in to the Prime Collaboration Assurance server as admin and run the following command to back up the data:

admin# backup Backupfilename repository RepositoryName application cpcm

 
 

Where:

Backupfilename—Name of the backup file (without the extension-.tar.gpg). This name can contain a maximum of 100 alphanumeric characters.

RepositoryName—Location to which the files are be backed up. This name can contain a maximum of 30 alphanumeric characters.

The following message appears after the backup is complete:

% Creating backup with timestamped filename: Backupfilename-Timestamp.tar.gpg

 
 

The backup file is suffixed with the time stamp (YYMMDD-HHMM) and file extension .tar.gpg and saved in the repository. For example:

admin# backup cmbackup repository tmp application cpcm
 
 

The following message appears after the backup is complete:

% Creating backup with timestamped filename: cmbackup-110218-0954.tar.gpg 

Restoring Data on the Same System

To restore the data, log in to the Prime Collaboration Assurance server as admin and run the following command:

admin# restore Backupfilename repository RepositoryName application cpcm

 
 

Where Backupfilename is the name of the backup file suffixed with the timestamp (YYMMDD-HHMM) and file extension .tar.gpg.

For example:

admin# restore cmbackup-110218-0954.tar.gpg repository tmp application cpcm
 
 

Restoring Data on a Different System

Prime Collaboration 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 system 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.


Note To perform backup and restore for a single machine or distributed database setup in Provisioning, see "Performing Backup and Restore" chapter in Cisco Prime Collaboration 9.5 Provisioning guide.



Note You must rediscover all the devices post restore.


Listing the Repository Data

You can list the data within a repository. Log in to the Prime Collaboration Assurance server as admin and run the following command:

admin# show repository RepositoryName

For example:

admin# show repository tmp
cmbackup-110218-0954.tar.gpg
admin#
 
 

Checking the Backup History

You can check the backup history. Log in to the Prime Collaboration Assurance server as admin and run the following command:

admin# show backup history

For example:

admin# show backup history
Fri Feb 18 09:54:39 UTC 2011: backup cmbackup-110218-0954.tar.gpg to repository 
temp: success
Fri Feb 18 18:29:48 UTC 2011: backup cmbackup-110218-1829.tar.gpg to repository 
tmp: success
admin#