Files and paths · Lesson 21 of 36 · 8 minutes

Backup manifest review

Read a backup manifest before touching archive files.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read manifest
Run cat backups/manifest.txt.
Hint & worked example
Read one or more files to standard output without editing their contents.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cat backups/manifest.txt
```
Remember: Reading a source file should precede changing it; avoid printing real secrets.
2
Find restore guidance
Run grep restore backups/manifest.txt.
Hint & worked example
Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
grep restore backups/manifest.txt
```
Remember: No matches is exit status 1, which is different from a malformed invocation.
3
Inspect manifest
Run stat backups/manifest.txt.
Hint & worked example
Inspect a file or directory metadata record, including ownership, permissions, and size.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
stat backups/manifest.txt
```
Remember: Metadata and file contents answer different questions.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

cat: Read one or more files to standard output without editing their contents.
Reading a source file should precede changing it; avoid printing real secrets.
grep: Select input lines that match a pattern; -i ignores case, -n adds line numbers, and -v inverts selection.
No matches is exit status 1, which is different from a malformed invocation.
stat: Inspect a file or directory metadata record, including ownership, permissions, and size.
Metadata and file contents answer different questions.

Worked example and expected result

$ cat backups/manifest.txt

backup-2026-05-26.tar includes README.txt and /srv/www/index.html
verify checksum before restore
restore into /home/learner/restore first

Exit status: 0. The command completed successfully in the training fixture.

$ grep restore backups/manifest.txt

verify checksum before restore
restore into /home/learner/restore first

Exit status: 0. The command completed successfully in the training fixture.

$ stat backups/manifest.txt

Path: /home/learner/backups/manifest.txt
Type: file
Mode: -rw-r-----
Owner: learner
Group: learners
Size: 137 bytes

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Backup manifest review”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.No matches is exit status 1, which is different from a malformed invocation.

Apply it elsewhere

Before adapting the grep workflow from “Backup manifest review” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Backup archive create Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual