Hosting Operations
Deletes or truncates filesVerify Restored File Checksums
You need to run the checksum manifest inside the restored sandbox and confirm each restored file is OK.
Command
BACKUP_ROOT=/srv/backups/site RESTORE_SANDBOX=/tmp/linuxoneliners-restore/full && rm -rf "$RESTORE_SANDBOX" && mkdir -p "$RESTORE_SANDBOX" && tar -xf "$BACKUP_ROOT/2026-06-25/site.tar" -C "$RESTORE_SANDBOX" && (cd "$RESTORE_SANDBOX" && sha256sum -c CHECKSUMS.sha256)
Before you run this
System impact: Deletes, truncates, or overwrites data. Requires backup, preview, and exact path review before production use.
When not to use it: Do not validate against a checksum file from an untrusted or unrelated backup.
Expected output
One OK line per restored file in the checksum manifest.
System impact
Deletes or truncates files. The existing restore-sandbox/full directory is removed and recreated, then checksum validation reads restored files.
When to use it
Use during restore drills when byte-level validation matters.
When not to use it
Do not validate against a checksum file from an untrusted or unrelated backup.
Recovery / rollback
Remove the restore-dr/restore-sandbox/full directory from the example copy. Never point the rm -rf path at production data.
next steps
Related commands
Extract a Backup Into a Restore Sandbox
A restore drill should write to a sandbox, not production.
BACKUP_ROOT=/srv/backups/site RESTORE_SANDBOX=/tmp/linuxoneliners-restore/full && rm -rf "$RESTORE_SANDBOX" && mkdir -p "$RESTORE_SANDBOX" && tar -xf "$BACKUP_ROOT/2026-06-25/site.tar" -C "$RESTORE_SANDBOX"
Check Required Files After Restore
A successful extraction still needs a required-file check.
BACKUP_ROOT=/srv/backups/site REQUIRED=/srv/backups/site/required-files.txt RESTORE_SANDBOX=/tmp/linuxoneliners-restore/full && rm -rf "$RESTORE_SANDBOX" && mkdir -p "$RESTORE_SANDBOX" && tar -xf "$BACKUP_ROOT/2026-06-25/site.tar" -C "$RESTORE_SANDBOX" && find "$RESTORE_SANDBOX" -type f | sed "s#^$RESTORE_SANDBOX/##" | sort | comm -23 "$REQUIRED" -
Diff Restored Config Against Expected
A restored config can exist and still be the wrong config.
BACKUP_ROOT=/srv/backups/site EXPECTED_CONFIG=/srv/backups/site/expected/app/config.yml RESTORE_SANDBOX=/tmp/linuxoneliners-restore/full && rm -rf "$RESTORE_SANDBOX" && mkdir -p "$RESTORE_SANDBOX" && tar -xf "$BACKUP_ROOT/2026-06-25/site.tar" -C "$RESTORE_SANDBOX" && diff -u "$EXPECTED_CONFIG" "$RESTORE_SANDBOX/app/config.yml"
Review Critical File Modes in the Archive
Permissions are part of the restore, not decoration.
BACKUP_ROOT=/srv/backups/site && tar -tvf "$BACKUP_ROOT/2026-06-25/site.tar" | awk '/secrets.env|deploy.sh/ {print $1, $6}'
List Archive Contents Before Extracting
You can inspect a tar backup before it writes a single file.
BACKUP_ROOT=/srv/backups/site && tar -tf "$BACKUP_ROOT/2026-06-25/site.tar" | sed 's#^./##' | sort
Study mapping
Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.