Skip to main content

Go back to an earlier snapshot

Something has been wrong since an activation, and you do not know yet what. Then the way back helps: it makes the previous snapshot the active one again, immediately; what caused it, you clarify afterwards.

Going back buys you time; the cause remains. You can search for it afterwards, calmly, with a system that works again — the way to do that is under It ran for months and stopped working yesterday.

What you need​

  • The Activation permission, Full level. With only Configuration, you see the archive and can compare in it; the button appears only with Activation. See Permissions.
  • The go-ahead to do this now. The step takes effect immediately and without notice: from the click on, every route works according to the old snapshot. Running jobs are not affected — they finish under the snapshot they started under.
  • The entry point: Configuration Snapshots, section Archived configurations.

It goes back exactly one step​

The archive lists all earlier snapshots; exactly one of them can be brought back. The Restore button is on exactly one row: the highest archived version below the active one. All other rows are there to view and compare.

Archive list in which only the top row carries a button to restore.

In the example: version 7 is active, and versions 1 to 6 are in the archive. Only version 6 can be brought back.

Expect gaps in the numbering. The archive is trimmed from the bottom over time, so the next row below version 12 may well be version 9. And the top row can be the wrong one, too: after a step back, the snapshot that was just archived sits at the very top with its higher number, while the button sits further down. Rely on the button alone.

What the step does​

The confirmation prompt says it verbatim: Version 6 becomes the active configuration snapshot again. The currently active snapshot is archived. So two movements — version 6 comes to the front, version 7 goes into the archive and can be brought back from there just as version 6 could a moment ago.

If a draft is open, a third sentence appears: The existing draft is preserved and can still be activated.

The draft survives the step, and that is the trap​

A draft is a copy of the snapshot that was active when it was first edited, plus your changes. In the example, draft version 8 is therefore "version 7 and one additional row". Going back leaves it as it is: it stays, stays Validated, stays activatable.

If you activate it now, you bring version 7 back with it — the whole snapshot it was copied from, including the one new row. The step back would be undone.

Therefore:

  • Tell the person who is working on the draft. There is only one draft, and the person who created it learns about the step back only through you.
  • The draft is activated only once the cause is known. It may keep growing; it goes into operation only once you know why you went back.
  • Once the cause is known, the repair belongs in the same draft. It already contains the snapshot in which the error lies — that is where the change is to be made. How that works is described under Change a running configuration.

The Validated on the draft also deserves mistrust afterwards: it was computed against the snapshot that was active before the step. Validate again before anyone activates.

When one step is not enough​

Then take another one. After the return to version 6, version 5 carries the button, and so on, down to the oldest snapshot the archive still holds. Each step archives the snapshot that was active at that moment.

Look beforehand instead of clicking your way through. With Compare, you can put any two snapshots side by side, including version 7 against version 4. That way, you see at a glance what three steps back would mean before you take the first. The screen for this is in the reference under Configuration Snapshots.

What it is not​

  • Importing is a separate path. A configuration from another system comes as a file and lands in the draft — see Bring a configuration into the production system.
  • Discarding is a separate path. Discard affects the draft alone, and it is final. What is already active can only be superseded.
  • The button in the Parked drafts section does something else. It is also called Restore and brings back a parked draft. Pay attention to which section you click in.
  • A snapshot comes back as a whole. Setting a single route to the old snapshot and leaving the rest is not supported.

What comes next​

See also​