Your router's config should outlive your router

14 July 2026

Ask an ISP operator where their router backups live and the honest answer is usually "on the router." A scheduler runs /export file=backup at 2 AM, the file sits in the router's flash, and everyone feels responsible.

That backup protects against exactly one thing: a configuration change you want to roll back. It protects against nothing that actually takes routers out of service:

• Hardware failure — the backup dies with the flash it lives on
• Lightning — common on tower sites, and it doesn't spare storage
• Theft — the config walks away with the device
• Factory reset — a well-meaning technician holding the reset button erases the backup along with the problem
• Flash wear — small boards have small flash, and log-heavy configs wear it out

Off the router, or it isn't a backup

ConnectR takes a different position: the configuration is business data, so it belongs with the rest of your business data. Every night, the platform connects to each router, runs a full /export show-sensitive, and stores the result server-side — tagged with the RouterOS version and board model it came from.

A few design details matter in practice:

• Deduplication. RouterOS stamps every export with a timestamp, so naive backups look "changed" every night. ConnectR hashes the configuration body itself — a night where nothing changed stores nothing, which means your backup list reads as a history of actual changes.
• Retention. The last 30 distinct configurations are kept per router. Enough to answer "what changed this month?", bounded enough to never think about storage.
• On-demand. A "Back up now" button captures state before you attempt something ambitious, and every entry downloads as a plain .rsc you can read, diff, or paste into a replacement router.

The replacement-router scenario

This is the payoff. A router dies on a Saturday. With on-router backups, you're rebuilding from memory. With off-router backups, the procedure is: unbox replacement, run the two onboarding commands, then apply the last known-good export on top. The new hardware inherits the old identity — PPPoE secrets, firewall rules, queue configuration — and your customers mostly never know.

Backups you can't restore after a total loss aren't backups; they're comfort. Put the config where the failure can't reach it.