Configuration Backup

Equipment burned out at 2 AM. Do you have its config? Which version? Was it ever tested? A backup nobody tests is just a false sense of security.

What configuration backup is

Configuration backup for an ISP covers routers, OLTs, switches, servers, and VMs. It is not just copying a file — it means versioning, comparing with the previous version, storing off-device, and having the config ready when you need to restore.

What RASYS does

  • Automated config collection — Mikrotik, Huawei, Cisco, Juniper, Datacom, ZTE, FiberHome — via SSH/SNMP/NETCONF.
  • Tools — Oxidized, RANCID, custom scripts when the vendor requires it.
  • Internal Git versioning with history of who changed what and when.
  • Diff between versions for incident investigation ("what changed in the last 24 hours?").
  • Server backup (XCP-ng/Linux) — VMs, configs, databases, and critical scripts via custom in-house scripts. Continuous status monitoring in Rasys's internal system (the client does not have direct access).
  • Off-site storage — not in the same PoP as the production network.

Equipment we work with

Mikrotik, Huawei, Cisco, Juniper, Datacom routers and switches; OLTs (MA5800, AN5516, C320, DM4xxx); Linux/XCP-ng servers.

When it makes sense to talk to us

You have never tested a backup restoration; equipment burned and you lost the config; a production change left you unclear about what changed; auditing/compliance requires a configuration history; you want to reduce MTTR after hardware failure.

Talk to us — initial conversation, no commitment. See also: Infrastructure Documentation, Virtualization.

FREQUENTLY ASKED QUESTIONS

Where does the backup storage live?

It depends on what is being backed up. Network configuration backups (router, OLT, switch) live in Rasys's infrastructure — you do not need to provide storage. Server and VM backups are too large for that, so they live on-site at the ISP plus an off-site copy in the cloud.

How often is the collection run?

Default: once per day plus on-change (every time we detect a change via SNMP trap or syslog). Configurable.

How do you restore equipment that burned out?

We take the most recent backup of the mirror unit (or the failed unit), apply it to the new equipment via serial console, adjust anything that is unit-specific (serial, MAC-dependent config), and validate session by session.

Is the backup encrypted?

Yes, in transit (SSH/HTTPS) and at rest (LUKS/age). Decryption key is segregated per customer.