This document describes the basics and the required setup for Backup and Restore features in Cisco Unified Communications Manager (CUCM) from the Graphic User Interface (GUI).
Cisco recommends that you have knowledge of these topics:
Cisco Unified Communications Manager
Secure File Transfer Protocol (SFTP)
The information in this document is based on these software versions:
Cisco Unified Communications Manager version 10.5.2.15900-8
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
The Disaster Recovery System (DRS), which can be invoked from CUCM Administration, provides full data backup and restore capabilities for all servers in the cluster. The DRS allows you to perform regularly scheduled automatic or user-invoked data backups.
DRS restores its own settings (backup device and schedule settings) as part of the platform backup/restore. DRS backs up and restores the drfDevice.xml and drfSchedule.xml files. When the server is restored with these files, you do not need to reconfigure DRS backup device and schedule.
The Disaster Recovery System includes these capabilities:
A user interface in order to perform backup and restore tasks
A distributed system architecture with backup and restore functions
Archive backups to a physical tape drive or remote SFTP server
The Disaster Recovery System contains two key functions, Master Agent (MA) and Local Agent (LA). The Master Agent coordinates backup and restore activity with Local Agents. The system automatically activates both the Master Agent and the Local Agent on all nodes in the cluster.
CUCM cluster (this involves the CUCM nodes and the Cisco Instant Messaging & Presence (IM&P) servers) must fulfil these requirements:
Port 22 open in order to establish the communication with SFTP server
Validated that the IPsec and Tomcat certificates are not expired.
In order to verify the validity of the certificates, navigate to Cisco Unified OS Administration > Security > Certificate Management
Ensure that the Database Replication is setup completed and does not show any errors or mismatches from the CUCM Publisher and the IM&P Publisher servers.
SFTP server settings must cover these requirements:
Login credentials are available
It must be reachable from the CUCM server
Files are included in the path selected when a restore is performed
The Disaster Recovery System performs a cluster-level backup, which means that it collects backups for all servers in a CUCM cluster to a central location and archives the backup data to physical storage device.
Step 1. In order to create backup devices on which data is saved; navigate to Disaster Recovery System > Backup > Backup Device.
Step 2. Select Add New; define a Backup Device Name and enter the SFTP values as shown in the image. Select Save.
Step 3. Create and edit backup schedules in order to back up data. Navigate to Backup > Scheduler.
Step 4. Define a Schedule Name. Select the Device Name and check the Features based on your scenario as shown in the image.
Step 5. Configure a scheduled backup based on your scenario as shown in the image.
Step 6. Select Save and notice the warning as shown in the image. Select OK in order to move forward.
Step 7. Once that a Backup Schedule is created, select Enable Schedule as shown in the image.
Step 8. Wait until the status is changed to Enabled as shown in the image.
Step 9. If a Manual backup is required, navigate to Backup > Manual Backup.
Step 10. Select the Device Name and check the Features based on your scenario as shown in the image.
Step 11. Select Start Backup and operation is displayed in progress as shown in the image.
Step 12. Once the manual backup is completed, the completion message is displayed as shown in the image.
Step 13. In order to estimate the size of backup tar file that SFTP device uses, select Estimate Size as shown in the image.
Step 14. Estimate size is displayed as shown in the image
Note: Estimate Size function is calculated based on previous successful backups and can vary in case configuration has been changed since the last backup.
Step 15. In order to check the Status of the Backup while a backup runs, navigate to Backup > Backup Status as shown in the image.
Step 16. In order to consult the backup procedures performed in the system, navigate to Backup > History as shown in the image.
DRS restores mainly drfDevice.xml and drfSchedule.xml files. However, when a system data restoration is performed, you can choose which nodes in the cluster require to get restored.
Note: Backup Device (SFTP server) must be already configured in order to retrieve the tar files from it and restore the system with these files.
Step 1. Navigate to Disaster Recovery System > Restore > Restore Wizard.
Step 2. As shown in the image, select the Device Name which stores the backup file you want to use for the restore. Select Next.
Step 3. Select the Backup File from the displayed list of available files as shown in the image. Selected backup file must include the information that you want to restore.
Step 4. From the list of available features, select the feature you need to restore as shown in the image.
Step 5. Select the nodes in which you desire to apply the restore as shown in the image.
Note: One-Step Restore allows the restoration of the entire cluster if the Publisher has already been rebuilt or fresh installed. This option is visible ONLY if the backup file selected for restore is the backup file of the cluster and the features chosen for restore includes the feature(s) that is registered with both publisher and subscriber nodes.
Step 6. Select Restore in order to start the process and Restore status is updated as shown in the image.
Step 7. In order to verify the status of the restore, navigate to Restore > Current Status as shown in the image
Step 8. Restore Status changes to SUCCESS once it is completed as shown in the image.
Step 9. In order for the changes to take effect, system must be restarted as shown in the image: