Restore

Restore writes a backup file back into the space you are in.

Fields

Field	Description
Passphrase	The passphrase used when the backup was taken — required
File	Only a .zip produced by the Backup screen is accepted

The file’s integrity is verified before anything is written back. A modified or corrupted backup is refused; a wrong passphrase fails the same way, because both come up against the same check.

Whatever is in the file is what is loaded

Restore offers no type selection and reads no list out of the backup — it imports whatever the .zip actually contains. That is the other half of the “no selection” decision on the backup side.

Deleted records come back — and that is deliberate

A restore revives the deleted records the file names. A record comes back under its own old identity, not as a new record with the same name.

The difference matters: a variable’s logged values, its fired-alarm history, its row-access anchor and its audit trail are all written under that identity. Had a same-named new record been created, none of them would attach to it — you would have a namesake with no history.

Bulk edit does not behave this way: there, re-adding a deleted row creates a new one.

The version warning

If a backup taken on one version is restored onto another, the restore warns — but does not stop.

Case	Behaviour
The versions match	Silent
The versions differ	A warning; the restore continues
The backup names no version	A neutral line, not a fault

Every difference warns; there is no major/minor reading. A comparison that decided which differences are safe would become the thing this deliberately is not — a compatibility layer.

Take the warning seriously

The warning comes from a fault measured in the field: an animation/SLD project backed up on one version and restored onto another comes back with some bindings evaluated differently — colours resolve to transparent, Move and positioning stop working. Nothing fails, the restore reports success, and the operator has no reason to connect what they are looking at with the move they just made; they find out by re-drawing the object and seeing the old one come back.

The rule is: bring both installations to the same version. This warning is that rule’s watchman, not a compatibility layer.

Not stopping is deliberate too: an archive is a whole installation, and this is the one operation an operator reaches for when something has already gone wrong.

The audit record

A restore is written to the audit trail, and the record names the person who asked for it, even though the work itself ran in the background as the system user.

Related

• Backup — producing the file
• Backup (operations) — the secret bundle, the master key, and what to check after a restore