Network configuration backup, and restoring from it
A switch dies on Friday evening, its replacement lands on Monday morning. What decides how long that weekend feels is not having a backup somewhere, it is being able to put it back on a new device without reading it line by line. Same story the day thirty switches have to come back to a reference configuration.
Request a trialBackup that covers the whole estate
Avalon backs up the configuration of every supported device on a defined schedule, whatever the brand. There is no per-vendor script, no file server to maintain and no naming convention to enforce.
- Scheduling per site, per group or across the whole estate
- Versioned history of successive configurations
- Comparison between two dates, on the configuration or on a captured state
- Restoring the configuration of a replaced device
Comparing to understand what changed
The value of a history is not storage, it is reading. Comparing two versions of the same configuration turns an evening of investigation into a few minutes. The comparison works on a captured operational state just as well as on the configuration itself.
Replaying a configuration, not just reading it
A backup earns its keep the day it goes back onto the device. Avalon tags a backup as a Config Set, then replays the whole tag across a set of devices: a batch is aligned on a reference configuration in one operation instead of one intervention per device.
The replay leans as much as possible on each platform own restore mechanisms, rather than replaying a configuration line by line. Where the device can arm a safety net before writing, Avalon arms it. Where it cannot, the transaction says so before acting, not after.
A prerequisite for any automation
Reliable backup is what makes deployment calm, because it provides the way out. It is also the basis of compliance checking, since a rule is evaluated against the configuration actually in place.
Frequently asked questions
- Which vendors are supported?
- Cisco IOS, IOS-XE, NX-OS and IE1000, Aruba CX including VSX and VSF, HP Comware including IRF, HP ProCurve and Huawei VRP. Stacks and virtual chassis are recognised as such. Adding a vendor usually takes five to ten days.
- Where are configurations stored?
- In the virtual appliance deployed at the customer site. No configuration leaves their network.
- Can a backup be pushed back as it is?
- Yes, that is what Config Sets are for. A configuration captured from a device that was really running it gets tagged, then replayed onto the devices of your choice, using the platform own configuration replacement mechanisms.
- Can a backup be triggered from another tool?
- Yes, every feature is available through the API, so a backup can be triggered from a scheduler or from an Ansible pipeline.
Offers
Avalon is available under a transparent yearly subscription, based on the number of managed IP devices alone.
- Yearly subscription, no hidden fees
- One license per device (switch stacks count as a single license)
- Decreasing cost per device as your network scales
- Guaranteed price stability, with no unexpected increases year over year
- Every feature included, no add-on modules
Designed with network engineers
Benefit from a platform shaped through real-world deployments and continuous collaboration with network teams.
Real customers!
University Hospital of Limoges
“We have deployed all the required configurations for our WiFi infrastructure migration across the entire Hospital, achieving a time savings of more than tenfold, and without any errors.”
Airbus Atlantic
“We use Avalon in a global automation process to ensure our maps are always up to date, streamlining workflows and enhancing the efficiency of our operational teams.”
See what centralised backup looks like on your estate
Thirty days of trial, up to 500 devices, on your own site, and nobody to ask first. Run a discovery, then a first backup of everything it finds.
Request a trial