The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You can schedule periodic backups using the Cisco 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 through VM console using the vSphere client. We recommend you not to trigger the restore from SSH/Putty prompt.
Cisco Prime Collaboration uses the following purge policy:
All conference and endpoint statistics data older than one day are purged.
All conference details older than 14 days are purged every hour.
Call quality event history and audio/video phone audit report data older than 30 days are purged.
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.
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 following folders are backed up by the backup service:
Depending on the number of managed devices in the Cisco Prime Collaboration Assurance server, the data backup should take:
Upto 150,000 endpoints - 4 hours
Upto 80,000 endpoints - 3 to 2.5 hours
Upto 20,000 endpoints - 2 hours
Upto 3,000 endpoints - 1 hour
Note | To achieve the preceding time periods, the network latency should not be more than 20 ms. |
We recommend you to schedule backups during the non-business hours, because, this operation can slow down the Cisco Prime Collaboration Assurance user interface performance.
You must create a repository before backing up the Cisco Prime Collaboration 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.
You can list the data within a repository. Log in to the Cisco Prime Collaboration server as admin and run the following command:
admin# show repository RepositoryName
admin# show repository myftp assurance_Sun_Feb_09_14_20_30_CST_2014.tar.gpg
You can schedule and run backup from the Cisco Prime Collaboration user interface.
You must be logged in as an administrator to perform backup.
CLI is supported only through SSH; telnet is not supported. The port used for Cisco Prime Collaboration server is 26. After creating the repository, log in to the Cisco Prime Collaboration server as admin and run the following command to back up the data:
admin# backup Backupfilename repository RepositoryName application cpcm
Backupfilename—Name of the backup file (without the extension-.tar.gpg). This name can be 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 is displayed 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, in case of backup on the ftp server:
admin# backup assurance repository myftp application cpcmwhere, myftp is a repository name.
You can check the backup history.
Log in to the Cisco Prime Collaboration server as admin and run the following command:
The following sections describe the process of restoring the data on the same system.
To restore the data, log in to the Cisco Prime Collaboration application server as admin through VM console using vSphere client. we recommend you to not to trigger the restore from SSH/Putty prompt.
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, to restore on the ftp server:
admin# restore assurance_Sun_Feb_09_14_20_30_CST_2014.tar.gpg repository myftp application cpcm
Cisco Prime Collaboration allows you to back up the data of a system and restore the data in another system in the event of total system failure.
To restore the backup from another system:
Ensure that the system to which data is restored must have the same MAC address as that of the system that was backed up (IP address and the hostname can be different).
In the case you are unable to assign the MAC address of the original system (that was backed up) to another system, contact Cisco TAC for information on a new license file (for a new MAC address).
To restore the backup from another system, log in as administrator and perform restore as described in Restore Data on Same System. See also, Create a Repository.
Note | As a post requirement, you must rediscover all the devices after restoring the data. |