A configuration backup is useful only if it is recent, stored safely and tested. Most failures are discovered when a replacement device arrives and the backup turns out to be six months old.
What to back up
- Running and startup configuration of routers, switches and firewalls
- Wireless controller configuration
- Firmware version and licence details
- Certificates and keys where the device allows export
How often
Back up on a schedule, daily for most networks, and after any change. A good tool also detects a change and stores a new version at once.
Store versions, not just the latest
Keeping every version lets you compare two dates and see exactly which lines changed, which answers "what did someone change before the outage?" quickly.
Detect drift with a golden template
Define the expected configuration for a device type, such as the access-switch standard. Any device that no longer matches is flagged, so temporary fixes do not become permanent differences.
Protect the backups
- Restrict who can read them, because they contain secrets
- Store copies off the monitoring server
- Encrypt backups at rest where possible
- Rotate credentials used for backup access
Test a restore
Once a quarter, restore a backup onto a spare device and confirm it works. An untested backup is a hope, not a plan.
NexoraUNMS backs up configuration over SSH, keeps versions, shows diffs and checks drift and policy. See configuration backup in NexoraUNMS.
Related guides: NexoraUNMS – Unified Network Management Software
Network Configuration Backup & ComplianceWhat Is a UNMS? Unified Network Management System ExplainedNexoraUNMS – Unified Network Management Software
See NexoraUNMS on a Live Demo Network
Watch monitoring, topology, alerts and configuration backup working together on sample data. Free demo from NexoraSoft; no obligation.
Book a Free Demo +91 98115 51004