This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
A backup you have not restored is a hope. The checklist generator drafts questions from answers you type. It does not connect and it does not restore anything.
The target is a spare host or a spare folder, not the live data. Write what you will compare: a file count, a checksum, or a login. Do not delete production to prove the backup. One dataset.
If the spare is missing, the test waits. That is the result.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Name the dataset and the spare target.
- Draft the checklist.
- Write the comparison you will make.
- Do not restore over production.
- Do not delete the live copy.
- Stop.
Mistakes that outlive the command
Testing Your Backups goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A restore over production.
- The live copy deleted as the test.
- No spare named.
- The checklist treated as a remote job.
- Someone else's backup used as the sample.
Decisions to write down
One decision for Testing Your Backups: The target is a spare. The live copy stays. The comparison is one sentence. Nothing was restored yet. And the data is yours.
Checks before you call it done
Confirm this before you call the change done: The dataset is written. The spare is written. The comparison is written. No restore was started. And production was not the target. If one of those fails, stop.
# Restore to a spare.
# Do not restore over production.
# Do not delete the live copy to test.Before you leave the host
Testing Your Backups ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.