Home » Cisco Certification Courses » CUCM Basics » Serviceability, Backup and Restore » CUCM Backup and Restoration

Backing up and Restoring Cisco Unified Communications Manager

The Disaster Recovery System (DRS), which can be invoked from the Cisco Unified Communications Manager Administration, provides full data CUCM backup and restore capabilities for all servers in a Cisco Unified Communications Manager cluster. Moreover, it also allows you to perform regularly scheduled automatic or user-invoked data backups.

The Disaster Recovery System performs a cluster-level backup, which basically means that it collects backups for all servers in a Cisco Unified Communications Manager cluster to a central location and also archives the backup data to a physical storage device.

Additionally, DRS restores its own settings (backup device settings and schedule settings) as part of the platform backup/restore. DRS backs up and restores drfDevice.xml and drfSchedule.xml files. So when the server is restored with these files, you do not need to reconfigure DRS backup device and schedule.

CUCM Backup DRS Menu

The DRS manages the following components:

The Cisco Unified Communications Manager database (CCMDB) includes the Cisco Unified Communications Manager, Call Detail Records Analysis and Reporting, and also the Call Detail Records.

  • Platform
  • Music On Hold (MOH) Audio Files
  • BAT Bulk Provisioning Service (BPS)
  • CCM Preference Files (CCMPREFS)
  • TFTP Phone device files (TFTP)
  • SNMP Syslog Component (SYSLOGAGT SNMP)
  • SNMP CDP Subagent (CDPAGT SNMP)
  • Trace Collection Tool (TCT)
  • Cluster Manager (CLM)
  • Cisco Extended Functions (CEF)
  • Reporter

 

In addition, the Disaster Recovery System backs up and restores the following components of the IM and Presence Service if you have IM and Presence nodes installed in the cluster:

  • Trace Collection Tool (TCT)
  • IM and Presence Preference Files (PREFS)
  • IM and Presence Database (DB)
  • XMPP Configuration Files (XCP)
  • Syslog Component (SYSLOGAGT)
  • Platform
  • Cluster Manager (CLM)
  • IM and Presence Configuration Files (CUP)

 

Before starting with the activities, you must have access to an SFTP server, which will be used to configure a network storage location. The SFTP path must exist before you create the backup, and the account that is used to access the SFTP server must have write permission for the selected path.

Also, the SFTP protocol is the SSH file transfer protocol, and this is the only option that is supported as a destination device in DRS. There are third-party applications that can provide you with this feature, but probably the easiest way is to bring up a Linux box and enable SSH on it.

 

Task 1: Cisco Unified Communications Manager (CUCM) Backup

In this lab, you will configure CUCM backup on Cisco Unified Communications Manager and then manually back them up to a network share.

Activity Procedure

Complete the following steps:

  1. Login to the CUCM with your credentials.
  2. Start your Linux box.
  3. From the Communications Manager Administration page, go to Navigation> Disaster Recovery System page and click the Go button. You will need to log in again because the disaster recovery site is separate from the administration site.
  4. From the menu, select Backup > Backup Device.
  5. Click Add New.
  6. Type in a name Share in the Backup Device Name field
  7. Type in the IP address 10.1.1.90 into the Host name/IPAddress field.
  8. Type into the Path Name field “/home/admin/”.
  9. Type in the username (admin) and the password used in the Linux box. By default, direct login with the root user is disabled in the SSH configuration file.
  10. Click Save and the system will test the connection to the SFTP server. Once everything is fine, there should be a message on the top “Update successful“.
  11. From the menu, select Backup > Scheduler.
  12. Click Add New.
  13. Type in a name for Weekly in the Schedule Name field.
  14. Select the backup device created in the earlier steps.
  15. Select UCM as the feature to back up.
  16. Configure the scheduler to back up the system every Sunday at 3.00 am beginning tomorrow.
  17. Click the Save button and then the Ok button on the warning screen.
  18. Click Enable Schedule at the bottom of the screen.
  19. Click the Save button and then the Ok button on the warning screen.
  20. From the menu, select Backup > Manual Backup.
  21. Select the Backup Device created in the previous steps.
  22. Select UCM as the feature to back up.
  23. Click the Start backup button, and then click the Ok button on the warning screen.
  24. The manual backup process will take some time to finish.
  25. To check the status of the backup process, from the menu select Backup > Current Status. The web page displays the backup status and refreshes automatically, or you can use the refresh button.
  26. Once the backup process completes, access the Linux box and list the contents of the /home/admin folder. All the backup files are stored here.
  27. Go back to the administration page by using the navigation pane. You will need to log in again.
  28. On the Cisco Unified Communications Manager administration page, select Call Routing > Translation Pattern to change your Communications Manager configuration.
  29. Click Аdd New button.
  30. On the Translation Pattern page, use the following parameters:
    – Translation pattern: 234XXXX
    – Provide Outside Dial tone: unchecked
    – Called Party Transformation mask: 3XXX
  31. Click Save
  32. You can add more translation patterns using different patterns.
  33. To verify that the translation pattern has been inserted, from the menu select Call Routing > Route Plan Report.
  34. On the Route Plan Report page, click the Find button.
  35. The page should list the configured translation patterns as a result.

 

Activity Verification

You have completed this task when you attain the following results:

  • The CUCM backup history contains the actual manual backup with the result “success”.
  • The translation pattern earlier is added correctly.

CUCM Backup Completed

[root@centos ~]# ls -lh /home/admin/
total 772M
-rw-rw-r– 1 admin admin  26M Jan 12 14:12 2015-01-12-12-18-28_CCM_UCM_CCMDB.tar
-rw-rw-r– 1 admin admin  13M Jan 12 13:53 2015-01-12-12-18-28_CCM_UCM_CCMPREFS.tar
-rw-rw-r– 1 admin admin  21K Jan 12 12:38 2015-01-12-12-18-28_CCM_UCM_CDPAGT.tar
-rw-rw-r– 1 admin admin  11K Jan 12 13:34 2015-01-12-12-18-28_CCM_UCM_CLM.tar
-rw-rw-r– 1 admin admin 871K Jan 12 13:16 2015-01-12-12-18-28_CCM_UCM_PLATFORM.tar
-rw-rw-r– 1 admin admin  11K Jan 12 12:57 2015-01-12-12-18-28_CCM_UCM_SYSLOGAGT.tar
-rw-rw-r– 1 admin admin  11K Jan 12 14:12 2015-01-12-12-18-28_CCM_UCM_TCT.tar
-rw-rw-r– 1 admin admin 733M Jan 12 12:20 2015-01-12-12-18-28_CCM_UCM_TFTP.tar
-rw-rw-r– 1 admin admin  13K Jan 12 14:31 2015-01-12-12-18-28_CCM_drfComponent.xml

CUCM Route Plan Report

 

Task 2: Cisco Unified Communications Manager (CUCM) Restoration

In this task, we will restore the Cisco Unified Communications Manager from the previously created CUCM backup.

Activity Procedure

Complete the following steps:

  1. From the Communications Manager Administration page, go to Navigation>Disaster Recovery System page. You will need to log in again. Then, from the menu, select Restore > Restore Wizard.
  2. Next, select the Device Name.
  3. Click the Next button.
  4. For Step 2 of the Restore page, select the backup file (there should be one backup file from the previous task; if there is no backup file, repeat task 1).
  5. Click the Next button.
  6. For Step 3 of the Restore page, on Select Features select UCM, and click Next.
  7. For Step 4 of the Restore page, on Select the servers to be restored for each feature, select CCM, and click Restore.
  8. Complete the restore process before proceeding.
  9. Reboot the server. You can reboot the server through the Cisco Unified OS Administration web interface or the command line via SSH.
  10. To restart the server through the web interface, use the navigation pane and access the Cisco Unified OS Administration web page. You will need to log in afterwards using your credentials.
  11. From the menu, select Settings > Version.
  12. Click Restart and the Ok.
  13. Another way to restart the server is through CLI. Use the SSH client (PuTTy) and initiate an SSH session to the Cisco Unified Communications Manager Server. Login using your credentials.
  14. Type this command: utils system restart.
  15. Type yes to continue.
  16. Take note of the warning message and then wait for the shutdown message to appear.
  17. Wait until the Communications Manager server is up and running. Try to ping 10.1.1.10 to see when the server will be reachable. The server will take 10 to 15 minutes to come back online, where the web pages are accessible.
  18. Log back into the Cisco Unified Communications Manager administration page, select Call Routing > Route Plan Report, and then click Find to list all dial plan patterns.
  19. Finally, the translation pattern(s) created on the previous task will not be there anymore.

 

Activity Verification

You have completed this task when you attain the following results:

  • Check that the changes made in step one were gone and the previous configuration was restored as well.

CUCM Restore Completed

Route Plan Report - Restored