Cisco "copy running-config startup-config" Command Explained
copy running-config startup-config — saves the active configuration to NVRAM so it survives reboots — the command that makes changes permanent. Runs in privileged EXEC mode.
Syntax and common variants
| Variant | Purpose |
|---|---|
copy running-config startup-config | Save RAM config to NVRAM |
write memory (or wr) | The classic shortcut, same effect |
copy running-config tftp: | Back the config up to a TFTP server |
show startup-config | Inspect what's currently saved |
Reading the output
| Output / element | Meaning |
|---|---|
Destination filename [startup-config]? | Press Enter to confirm |
Building configuration… [OK] | Saved successfully |
When to use it
The difference between a fixed network and a time bomb: unsaved changes vanish at the next power cycle. Professional habit — verify, then save; and before risky work, copy the config off-box (TFTP) so rollback is trivial. Browse more in the command reference or practise in the free labs.
Frequently asked questions
What happens if I forget to save?
The device boots its last saved startup-config — every unsaved change silently disappears at reload.
Is write memory the same thing?
Yes — the legacy shortcut performs the same save; wr is its abbreviation.
How do I discard unsaved changes instead?
Reload without saving — the device returns to startup-config as of the last save.
Related articles
Want hands-on training?
Learn this on real Cisco lab devices with placement support at Attila Technologies, Ahmedabad.