Recovery

A dataset history line branches from a snapshot to a clone, while a separate lock marks a user hold on another snapshot.

ZFS snapshots give the filesystem a rewind button

A ZFS snapshot preserves a point-in-time dataset view through copy-on-write references instead of a full duplicate of its data. Existing blocks remain available while references need them. Creation still has metadata and synchronization work; neither zero allocation nor completion before a shell redraw is a measured guarantee. This review did not run ZFS or recover the earlier claimed fixture’s raw output. ...

The same checksummed archive first fails in a fresh cluster because a role is missing, then restores after that role is supplied. The recovered two orders total 6075 cents.

Backups are untested hope without proof

A completed backup job establishes that the backup process produced an artifact. A restore rehearsal establishes whether that artifact, the available tooling, and the required environment can produce a usable system. These are different claims. Recovery evidence should identify the backup used, the state recovered, the dependencies supplied, and the time needed to make the result useful to the application. ...

Retrieve an archive and checksum from storage, verify the retrieved copy before use, and restore into an isolated disposable test target. Check files, permissions and elapsed restore time. A stored file alone is not proof of recovery.

Backups are only useful after a restore rehearsal

Choose a small recovery unit, verify it, and practice restoring it somewhere disposable.