Cisco Configuration Backup to TFTP: Practical IOS Guide

Cisco configuration backup to TFTP is a simple way to keep router or switch configs available for recovery. This updated note preserves the original archive/kron example and adds practical checks for safer operations.

What this backup configuration does

The example below sends the running configuration to a TFTP server every night at 1:00. It also triggers a backup when an engineer saves the configuration with write memory.

X Follow @ipexptobe

IOS archive and kron example

If you would like in easy way to  backup your configuration each day on tftp server, below you can follow ready solution.

In this case every night at 1:00 config will be sent to your tftp.
Also when you "wr mem" your configuration on a cisco device, it will be send as well to tftp.

archive
 path tftp://10.0.0.1/Backup/$h-config
 write-memory
!
!
kron occurrence daily-config-backup at 1:00 recurring
 policy-list backup-config
!
!
kron policy-list backup-config
 cli write memory

It's very usefull and cheap solution.
You can download free TFTP Server, e.g :  PumpKIN

Step 1: Download a TFTP Server

1. Download client from the link : PumpKIN and install it on your pc.

Step 2: Configuring pumpkin as your new TFTP server

 

 Launch PumpKIN.

1. From the PumpKIN menu follow to “Options” > “Server” > “TFTP file system root”. Point PumpKIN to the provisioning folder of your 3CX Phone System – by default:  C:\ProgramData\3CX\Data\Http\Interface\provisioning\%%provdir%%. Where %%provdir%% is the randomly generated provisioning folder name. This folder will be used to place files you need to upload via TFTP or download.
2. Other options can be set as needed. For example: “Read and Write Request Behavior” if you want a prompt before files are uploaded? or downloaded?  Change network ports, timeout etc.
3. Now you have a TFTP server installed you can begin updating your phones, gateways, routers as needed.  There are also other free TFTP clients out there.  TFTPD32/64 or Solarwinds just to name a few others.

Operational checks before using TFTP backup

• Confirm the device can reach the TFTP server over the management network.
• Use a predictable file name pattern such as $h-config so each device is easy to identify.
• Remember that TFTP is not encrypted; keep it on a trusted lab or management segment and restrict access where possible.
• Periodically test restore procedures, not only backup creation.

Related reading

• Start Here: Networking Topics
• Automation label hub
• Network Security label hub
• Cisco IOS Aliases: Faster CLI Troubleshooting Shortcuts

Discussion

If you run automated config backups in a lab or production network, share what transport, retention policy, and restore test process worked best for you.

Follow Network freak for more networking notes, diagrams and troubleshooting tips.

X @ipexptobe on X