Skip to content

Configuration Backup

How backups run

vConfig logs into each device over SSH (falling back to Telnet if enabled), runs the vendor's show/display commands, and stores the configuration with a full version history. Backups are multi-threaded; concurrency, timeouts and per-device ports are configurable under Settings → Backup.

  • Scheduled: typically daily, set once in Settings.
  • On demand: per device, per selection, or full network.
  • Credentials: two levels — global defaults plus per-device overrides.

Diffs and change alerts

Every new backup is compared with the previous version:

  • Config changes shows a network-wide feed of added/removed lines per device after each run.
  • Per-device history lets you diff any two versions side by side.
  • Webhook alerts (Slack/Teams/WeCom/DingTalk/Feishu) fire when a device's config drifts or a backup fails.

Search and the resource index

  • Config search: full-text search across every stored configuration.
  • Resource index: vConfig parses the newest config of each device and extracts interfaces, VLANs, VRFs, interconnect addresses, BGP AS numbers and customer references into a filterable, CSV-exportable index — your network's de-facto source of truth, reverse-engineered from reality.

Custom vendors and drivers

Built-in drivers cover Cisco IOS/IOS-XR, Juniper Junos, Huawei VRP, H3C Comware, MikroTik RouterOS and Arista EOS. For anything else, define a custom brand with its own login procedure and command set — one vendor = login procedure + command sets + format family.

Compliance with backups

Backed-up configs feed the compliance module and drift detection — no additional device access needed.