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.
Last updated: October 10, 2019
Note Setting up a backup server is part of the initial configuration process. If you have not already done this, see Setting Backup Parameters.
Cisco Unified SIP Proxy backup and restore functions use an FTP server to store and retrieve data. The backup function copies the files from the Cisco Unified SIP Proxy module to the FTP server and the restore function copies the files from the FTP server to the Cisco Unified SIP Proxy application. The FTP server can reside anywhere in the network as long as the backup and restore functions can access it with an IP address or hostname.
We recommend that you back up your configuration files whenever you make changes to the system or application files. Do backups regularly to preserve configuration data.
– Scheduled backup and restore operations. The backup and restore procedures begin when the appropriate command is entered.
– Centralized message storage arrangement. Cisco Unified SIP Proxy backup files cannot be used or integrated with other message stores.
– Selective backup and restore. Only full backup and restore functions are available. Individual messages or other specific data can be neither stored nor retrieved.
Cisco Unified SIP Proxy automatically assigns a backup ID to each backup. Although there are the three different types of backups, the system does not take into account the type of backup when generating the backup ID. Therefore, you will never have two backups with the same backup ID, even if one is a configuration file and the other a data file.
To determine the backup ID of the file you want to restore, use the show backup server or show backup history commands in either EXEC or offline mode. Those commands list all available backup copies on the remote backup server and their respective backup IDs.
The following examples display the output from the show backup history and show backup server commands:
After you create the backup files, you can restore them when needed. Restoring is done in offline mode, which terminates all calls. You should therefore consider restoring files when call traffic is least impacted.
To determine the backup ID of the file you want to restore, use the show backup server or show backup history commands in either EXEC or offline mode.
3. restore id backup_ID category { all | configuration | data }