NET Backup Vault / Atomic Safety Protocol
Restore Safety

Atomic Safety Protocol.

A restore should not leave your network half-changed. Atomic Safety Protocol is how NET Backup Vault runs an atomic restore: it validates first, takes a snapshot of your live configuration, applies and checks each change, and reverts the changed settings if a step fails.

The Idea

What "atomic" means for a restore

In computing, an operation is atomic when it cannot be partially done. It happens completely, or it does not happen at all. There is no observable middle state.

Recovery is exactly where that property matters most. A restore that fails halfway, after writing some VLANs but not the firewall rules that depend on them, can leave a network in a state that never existed before and is worse than the problem you were fixing.

Atomic Safety Protocol removes that risk. A restore is one transaction with a clear contract: succeed entirely, or revert entirely.

Restore Safety

Snapshot first.
Revert on failure.

An atomic restore takes a snapshot of your live configuration first. If the Meraki API returns an error midway, NET Backup Vault reverts the changed settings to their pre-restore state.

Core Principles

Four principles
behind every atomic restore

Revert on failure

If a step fails, the changed settings are reverted

An atomic restore applies and checks one feature at a time. If a feature fails to apply, NET Backup Vault reverts the settings it already changed to their pre-restore state, newest first. If a revert itself fails, you are alerted straight away.

Validate first

Nothing is written until the request checks out

Pre-flight validation and an optional dry-run preview confirm the target is reachable and the backup is compatible before any live setting is touched. You see what would change before you commit to changing it.

Snapshot

Your live state is captured before the first write

The current configuration is recorded as a rollback checkpoint at the start of every restore. That checkpoint is what makes a clean, automatic reversal possible.

Rollback

Failure reverts you, automatically

Power loss, an API timeout, or a rejected change mid-restore all trigger the same response: the engine reapplies the checkpoint and your network returns to its exact pre-restore state.

How NET Backup Vault Does It

One safety sequence,
every single time

Whether you restore one firewall rule or an entire organization, the same four steps run underneath. The protocol is not optional, and it is not something you have to configure.

01

Pre-flight validation

Before a single setting is written, NET Backup Vault checks that the target organization and networks exist, are reachable, and are compatible with the backup. Nothing is applied during this phase.

Reachability · feature compatibility
02

Snapshot first

NET Backup Vault captures your current live configuration as a rollback checkpoint. This is the exact state your network will return to if anything goes wrong.

Pre-restore checkpoint
03

Apply

Each selected setting is pushed back to the Meraki Dashboard in sequence. Long-running restores report live progress so you always know which step is executing.

Tracked, step-by-step
04

Verify, or roll back

Every change is confirmed against live state. If any step fails midway, the engine reverts the changed settings to their pre-restore state.

Automatic rollback on failure

Rollback checkpoints are retained for a limited window after a restore completes, so you can also reverse a successful restore after the fact while the checkpoint is still available.

An Honest Boundary

What we can protect, and what no tool can

Atomic Safety Protocol protects what is restored. It does not, and cannot, expand what is possible to capture in the first place. Every Meraki backup tool, including NET Backup Vault, can only read and write what the Meraki Dashboard API exposes.

We think you deserve to know where that line is. A truly complete Meraki backup remains challenging even on the latest API, for reasons that sit with the platform, not the backup tool:

01

Meraki's Dashboard API still does not have full feature parity with the Dashboard UI.

02

Some Dashboard settings remain UI-only and have no API endpoint to read or write them.

03

Beta endpoints frequently appear before they stabilize, so coverage shifts over time.

04

Newer product families (MV cameras, MT sensors, MG cellular) are still expanding their API coverage.

NET Backup Vault tracks new endpoints as Meraki ships them. Anything Meraki keeps UI-only sits outside the API and therefore outside any automated backup. We would rather state that plainly than imply a coverage we cannot honestly deliver, so we list what we can and cannot restore, item by item.

Restore without the held breath.

See how atomic restores and automatic rollback work against your own Meraki organization.