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
RPO is how much data you can bear to lose, measured in time. RTO is how long you can bear to be down. The calculator uses numbers you type. It does not measure your backups and it is not a legal SLA.
A short RPO with a nightly backup is a contradiction you write down. Do not pick zero because the form allowed it unless you can say how the copies work. The SLA page is a different percentage.
This does not authorize a failover test on production during the reading.
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.
- Write the RPO.
- Write the RTO.
- Name the backup that is supposed to meet them.
- Mark a contradiction if the backup is slower than the RPO.
- Do not start a failover.
- Stop.
Mistakes that outlive the command
RPO vs RTO Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Zero typed with no copy to match.
- The result filed as a contract.
- A production failover during the reading.
- RPO and RTO swapped and left swapped.
Decisions to write down
One decision for RPO vs RTO Explained: Both durations are written. The backup frequency is named. A contradiction is marked if there is one. No failover was started. And this is not a contract.
Checks before you call it done
Confirm this before you call the change done: RPO is written. RTO is written. The backup is named. No failover was started. And the note says this is not an SLA. If one of those fails, stop.
| Term | Question | Not |
|---|---|---|
| RPO | How old can the restored data be? | A legal SLA |
| RTO | How long until the service is back? | A wish with no backup |
| Backup | Does the copy meet that age? | A calculator measurement |
# RPO is data loss in time. RTO is downtime.
# Not a contract.
# Do not fail over production from this page.Before you leave the host
RPO vs RTO Explained 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.