Back to lessons

Hosting Operations

Read the Backup Manifest

You need to confirm the backup id, timestamp, archive name, and completion status before drilling a restore.

Command

cd restore-dr && cat backups/2026-06-25/MANIFEST.txt

What changed

Nothing changes. The command prints the manifest.

Danger

safe

When to use it

Use before extracting an archive so the selected restore point is explicit.

When not to use it

Do not rely on a manifest alone; validate the archive and restored files afterward.

Undo or recovery

No undo needed because this command is read-only.

Expected output

Manifest keys including backup_id, created_at, archive, status, and total_files.

demo script

Disposable terminal steps

  1. cd restore-dr && cat backups/2026-06-25/MANIFEST.txt
  2. cd restore-dr && grep -E 'backup_id=|created_at=|status=' backups/2026-06-25/MANIFEST.txt

simulated output

What it looks like

disposable vessel
::fixture-ready::
$ cd restore-dr && cat backups/2026-06-25/MANIFEST.txt
backup_id=2026-06-25
created_at=2026-06-25T12:00:00Z
archive=site.tar
status=complete
total_files=7
::exit-code::0
$ cd restore-dr && grep -E 'backup_id=|created_at=|status=' backups/2026-06-25/MANIFEST.txt
backup_id=2026-06-25
created_at=2026-06-25T12:00:00Z
status=complete
::exit-code::0

YouTube Short

Read the manifest.

Before extracting a backup, read the manifest. The status and timestamp are your first sanity check.

LinkedIn hook

The manifest should say what backup you are about to trust.

Question: What fields do you require in a backup manifest?

experiments

A/B tests to run

Metric: completion_rate

A: Read the manifest before restore.

B: Do not restore a mystery archive.