Lab 24: Backing Up Configs and IOS to TFTP
The habit that separates professionals: configs backed up OFF the device. Copy running-config to a TFTP server, break something on purpose, then restore like it never happened. Difficulty: Beginner+ · Time: ~20 min.
Lab objectives
- Back up running-config to TFTP
- Verify the file landed on the server
- Damage the config deliberately
- Restore from the backup
Topology & addressing
Router (192.168.1.1) + PT Server (192.168.1.5) with the TFTP service enabled, same subnet.
Step-by-step configuration
copy running-config tftp:→ address 192.168.1.5, filename R1-backup | Push the config off-box |
| Break it: change the hostname, remove an IP | Simulated bad day |
copy tftp: running-config | Pull the backup over the damage (merge into RAM) |
Verification
The server's TFTP file list shows R1-backup after step 1. After "restoring", the hostname and settings return. Two real-world notes: copying INTO running-config merges (it doesn't erase extras — full disaster recovery restores into startup-config + reload), and this same mechanism backs up IOS images before upgrades.
Next lab: labs hub · test yourself: CCNA practice test.
Frequently asked questions
Why back up to TFTP instead of just saving?
copy run start protects against reboots, not against bad changes, hardware death or fat fingers — off-device copies survive everything.
Does restoring to running-config wipe my current config?
No — it merges. Lines not present in the backup remain; a truly clean restore goes to startup-config followed by a reload.
When should backups happen?
Before every change window, after every verified change — and automatically on schedule in production networks.
Related articles
Want hands-on training?
Learn this on real Cisco lab devices with placement support at Attila Technologies, Ahmedabad.