Server operations · Lesson 29 of 36 · 8 minutes

Backup service note

Inspect an inactive backup service and write a review marker.

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 active
Run systemctl is-active 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 is-active 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
Write backup marker
Run printf backup-reviewed > lab/backup-service.txt.
Hint & worked example
Format data deliberately, including separators and final newlines.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
printf backup-reviewed > lab/backup-service.txt
```
Remember: A format string controls output; a newline is data, not an automatic guarantee.

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.
printf: Format data deliberately, including separators and final newlines.
A format string controls output; a newline is data, not an automatic guarantee.

Worked example and expected result

$ systemctl is-active backup

inactive

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.

$ printf backup-reviewed > lab/backup-service.txt

(no output; exit 0)

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

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Service failure notes 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