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
cd restore-dr && rm -rf restore-sandbox/full && mkdir -p restore-sandbox/full && tar -xf backups/2026-06-25/site.tar -C restore-sandbox/full && (cd restore-sandbox/full && 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 fixture copy. Never point the rm -rf path at production data.
Watch this command run
Example output from a temporary Linux lab
This example uses disposable sample files and sanitized output so you can inspect the shape of the result before touching a real system.
$ cd restore-dr && rm -rf restore-sandbox/full && mkdir -p restore-sandbox/full && tar -xf backups/2026-06-25/site.tar -C restore-sandbox/full
$ cd restore-dr && (cd restore-sandbox/full && sha256sum -c CHECKSUMS.sha256)
app/config.yml: OK
app/secrets.env: OK
public/index.html: OK
app/orders.csv: OK
uploads/avatar.txt: OK
bin/deploy.sh: OKView reproducible demo details
These commands recreate the temporary example before running the command under review.
Reproduce this demo
cd restore-dr && rm -rf restore-sandbox/full && mkdir -p restore-sandbox/full && tar -xf backups/2026-06-25/site.tar -C restore-sandbox/fullcd restore-dr && (cd restore-sandbox/full && sha256sum -c CHECKSUMS.sha256)
next steps
Related commands
Extract a Backup Into a Restore Sandbox
A restore drill should write to a sandbox, not production.
cd restore-dr && rm -rf restore-sandbox/full && mkdir -p restore-sandbox/full && tar -xf backups/2026-06-25/site.tar -C restore-sandbox/full
Check Required Files After Restore
A successful extraction still needs a required-file check.
cd restore-dr && rm -rf restore-sandbox/full && mkdir -p restore-sandbox/full && tar -xf backups/2026-06-25/site.tar -C restore-sandbox/full && find restore-sandbox/full -type f | sed 's#^restore-sandbox/full/##' | sort | comm -23 required-files.txt -
Diff Restored Config Against Expected
A restored config can exist and still be the wrong config.
cd restore-dr && rm -rf restore-sandbox/full && mkdir -p restore-sandbox/full && tar -xf backups/2026-06-25/site.tar -C restore-sandbox/full && diff -u expected/app/config.yml restore-sandbox/full/app/config.yml
Review Critical File Modes in the Archive
Permissions are part of the restore, not decoration.
cd restore-dr && tar -tvf backups/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.
cd restore-dr && tar -tf backups/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.
Useful for
- LPIC-1 style command-line practice
- LFCS style performance tasks
- Linux+ style troubleshooting review
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.