Troubleshooting · Lesson 19 of 26 · 8 minutes

Incident backup inactive

Triage inactive backup state and manifest context.

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
Check backup
Run systemctl status backup.
Hint & worked example
Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
Observe the inactive backup unit and its exit status 3.
```
systemctl status backup
```
Remember: A service can be active while an application endpoint is unhealthy; verify both layers.
2
Read backup journal
Run journalctl -u backup.
Hint & worked example
Read the training journal by unit or a bounded line window.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
journalctl -u backup
```
Remember: A relevant unit and time range are more useful than an unfiltered wall of logs.
3
Read backup 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.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

systemctl: Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
A service can be active while an application endpoint is unhealthy; verify both layers.
journalctl: Read the training journal by unit or a bounded line window.
A relevant unit and time range are more useful than an unfiltered wall of logs.
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.

Worked example and expected result

$ systemctl status backup

backup.service - simulated backup
   Loaded: loaded
   Active: inactive
   Notes: waiting for a configured backup target

Exit status: 3. This nonzero result is an expected part of this exercise.

$ journalctl -u backup

May 26 08:05:00 clairos-learn backup[88]: skipped, no fake target configured
May 26 08:20:00 clairos-learn backup[88]: inactive by policy

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

$ 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.

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 “Incident backup inactive”, which interpretation is safe?A successful first check guarantees that every dependent service is healthy.A relevant unit and time range are more useful than an unfiltered wall of logs.A command appearing in history proves it completed successfully.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Incident nginx config mismatch 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