Meraki has no undo button
Cisco Meraki Dashboard has no native backup, no rollback, and no version history. Here is what that means for your network and what you can do about it.
Cloud-managed does not mean backed up.
Cisco Meraki Dashboard stores your configuration in the cloud. It syncs across devices. It provides a clean web interface for managing your network. But it does not back up your configuration. There is no restore button. There is no version history. There is no undo.
This surprises people. Meraki is a premium product. It costs real money per device, per year. The assumption is that a cloud-managed platform would protect your configuration the way a cloud database protects your data. It does not.
What “no backup” actually means
When a technician accidentally deletes a firewall rule, it is gone. When someone misconfigures a VLAN and breaks VoIP for an entire office, the previous configuration is gone. When a Meraki device fails and the RMA replacement arrives, it arrives blank.
Meraki has a Change Log. It shows that a change happened. It does not show the full before-and-after state. It cannot restore the previous configuration. It has limited retention. And it does not include sensitive fields like pre-shared keys.
Cisco support has confirmed this directly. On the Meraki community forums, a Cisco employee stated: “There is no way we can restore the account.” This is not a bug. This is how the product works.
The real cost of no backup
The cost is invisible until it is not. Most MSPs and network admins discover this gap the same way: an incident happens, they look for an undo button, and it is not there.
The typical recovery looks like this:
- Discover the problem (often at an inconvenient time)
- Try to remember what the configuration looked like before
- Search for screenshots, notes, exported configs, old documentation
- Manually rebuild the affected configuration
- Hope nothing was missed
This process takes 2-6 hours for a single network. For an MSP managing 30+ client organizations, the risk compounds.
What you can do about it
There are four approaches:
Manual exports. You can export configurations from the Meraki API and store them somewhere. This works until you forget, until the export script breaks, or until you need to restore and realize the export does not cover all 19 configuration types.
Custom scripts. You can write Python scripts using the Meraki Dashboard API. Many network admins have done this. These scripts typically cover about 75% of configuration types, have no scheduling, no UI, no rollback capability, and break when the API changes. They also leave when the person who wrote them leaves.
Enterprise NCM tools. Platforms like Auvik, SolarWinds NCM, or ManageEngine NCM provide multi-vendor configuration management. Most of them use SSH/SNMP, which Meraki does not expose. The ones that do support Meraki often treat it as a secondary integration, not a primary focus.
Purpose-built Meraki backup. Tools designed specifically for the Meraki Dashboard API that provide automated scheduling, granular feature-level restore, version control, and rollback. This is what NET Backup Vault does.
The bottom line
If you manage Cisco Meraki networks, your configurations are not backed up unless you have explicitly set up a backup system. The Meraki Dashboard does not do this for you. The longer you operate without backup, the more you are betting that nothing will go wrong.
That is not a bet most network professionals would take if they knew they were making it.