1.0 Introduction

This document provides a comprehensive technical guide for performing a backup of the Trivial File Transfer Protocol (TFTP) files within a Cisco Unified Communications Manager (CUCM) environment. The analysis addresses an initial query regarding the use of CLI commands for this purpose and expands upon it to deliver a robust, Cisco-recommended best practice solution suitable for production environments, ensuring data integrity and system recoverability.

2.0 Problem Analysis and Initial Approach

The core technical objective is to create a reliable backup of the files managed by the CUCM TFTP service. These files are critical for endpoint operation and include phone configuration files (e.g., SEP<MAC>.cnf.xml), firmware loads, ring lists, locale files, and other device-specific resources.

An initial approach identified involves utilizing the CUCM Command Line Interface (CLI) on the Publisher node. The proposed command is:

file get tftp /*

This command instructs the CUCM appliance to transfer all files located in the root of the TFTP directory to a pre-configured SFTP server.

Evaluation of the Initial Approach:
While the file get tftp command is a valid and useful utility for ad-hoc retrieval of specific files, it is fundamentally insufficient and not recommended as a formal backup strategy for the following reasons:

• Incompleteness: This method only copies the static files present in the TFTP directory at that moment. It does not back up the underlying CUCM database (CCMDB), which is responsible for dynamically generating the phone configuration files. Without the database, a system restore is impossible.
• Lack of Cluster Awareness: The command executes only on the node to which the engineer is connected (typically the Publisher). It does not account for TFTP files that may be served by, or are specific to, Subscriber nodes in a large cluster.
• No Integrity Validation: This is a simple file copy operation. It lacks the built-in validation, logging, and error-handling mechanisms of a dedicated backup system, making it unreliable for disaster recovery purposes.
• Unsupported for System Restoration: A backup created using this method is not a valid source for a system restore. The official CUCM restore process requires a backup set created by the Disaster Recovery System (DRS).

3.0 Recommended Solution: Cisco Disaster Recovery System (DRS)

The only Cisco-sanctioned and fully supported method for backing up a CUCM cluster, including all TFTP components, is the Disaster Recovery System (DRS). DRS is an integrated tool accessed via the CUCM web interface that provides a robust, cluster-wide backup and restore capability.

DRS ensures a consistent snapshot of all critical components. When performing a backup, DRS includes the following, among others:

• CUCM (CCMDB): The core configuration database for the entire cluster. This is the source of truth that generates TFTP configuration files.
• TFTP Files: The complete set of static and dynamically generated files required by endpoints.
• Music On Hold (MOH) Audio Files: All audio sources for MOH.
• Platform Configuration: Essential system-level settings.

4.0 Detailed Procedure for a Comprehensive DRS Backup

To execute a proper backup that includes all TFTP data, follow the procedure below. This requires access to the CUCM Administration GUI and a functional SFTP server accessible from the CUCM cluster nodes.

Step 1: Configure the Backup Device

Before a backup can be performed, DRS must be configured with the details of a remote SFTP server where the backup archives will be stored.

1. Log in to the Cisco Unified CM Administration page of your CUCM Publisher.
2. Navigate to Disaster Recovery System in the top-right navigation dropdown and click Go. You will be redirected to the DRS interface.
3. Log in with appropriate administrator credentials.
4. Navigate to Backup > Backup Device.
5. Click Add New.
6. Configure the following fields:
   • Device Name: A descriptive name (e.g., Primary_SFTP_Backup_Server).
   • Server Name / IP Address: The hostname or IP address of your SFTP server.
   • Path Name: The absolute or relative path on the SFTP server where backups will be stored (e.g., /backups/cucm/). Ensure the specified user has write permissions to this directory.
   • User Name: The username for authenticating to the SFTP server.
   • Password: The corresponding password for the user.
   • Protocol: Select SFTP.
7. Click Save. The system will test connectivity to the SFTP server.

Step 2: Execute a Manual Backup

1. In the DRS interface, navigate to Backup > Manual Backup.
2. From the Device Name dropdown, select the backup device you configured in Step 1.
3. Under Select Features, ensure you select at least the CUCM feature. The TFTP Server Files are backed up as part of the CUCM component itself. You do not need to select a separate “TFTP” feature unless it is explicitly listed for a specific version. Backing up the CUCM feature set ensures both the database and the resulting TFTP files are captured.
4. Click Start Backup. The process will begin, and its progress can be monitored from the Backup > Backup Status page.

Upon completion, a .tar archive containing the complete backup set will be located on your SFTP server.

5.0 Conclusion

For ensuring business continuity and system recoverability, the use of the Cisco Disaster Recovery System (DRS) is mandatory. The CLI command file get tftp should be reserved for specific troubleshooting tasks, such as manually retrieving a single phone’s configuration file for analysis. A formal backup strategy must exclusively rely on DRS to create a consistent, validated, and restorable snapshot of the entire CUCM cluster, thereby safeguarding all critical TFTP data and the underlying database that populates it. Regular, automated DRS backups are a cornerstone of a well-maintained Cisco Unified Communications environment.