retivo Docs
  1. Docs
  2. Concepts

Config versions

When Retivo saves a new version, what it ignores, and how comparing and restoring work.

When a version is saved

Retivo reads the running configuration over SSH every day at 02:00 server time, when you press Back up now or Back up selected, before every push, and before a firmware upgrade.

A new version is saved only when the configuration really changed. Lines that change by themselves are ignored, for example:

  • Cisco: ! Last configuration change, ! NVRAM config last updated, ntp clock-period
  • FortiOS: #conf_file_ver, encrypted password strings that differ on every read

So the list of versions is a list of real changes.

What is stored with a version

  • the full configuration text,
  • the time and how it was made (scheduled, manual, push, restore),
  • for pushes and restores, who did it and their description,
  • whether a copy reached the remote destination, if one is set.

Comparing

Any two versions of a device can be compared side by side: removed lines in red on the left, added lines in green on the right.

Restoring

Restore is built from the difference between the live configuration and the version you choose. Retivo proposes the commands, you review them, and they go through the same preview and typed "yes" as any push. Afterwards Retivo says whether the device now matches the chosen version.

Caution

Restore is a proposal, not a rollback. Banners, certificates and order-sensitive lists such as ACLs may need manual correction. FortiOS restore re-applies changed blocks only. RouterOS restore is not supported.

What's next

Last modified October 15, 2026