Backup
A copy of important files, settings, exports, or systems that can be used if the original is lost, damaged, or changed by mistake.
Backup Terms
A plain-English glossary for backup and recovery terms used across KITPro resources, checklists, and readiness conversations.
A practical glossary for backup-readiness conversations.
These definitions are intentionally simple. They are meant to help you understand the Backup Readiness Checklist, Restore Test Notes, and the Backup & Recovery Readiness preview lane.
Backup terms in plain English
Use these terms as a starting point when writing notes or preparing a manual KITPro conversation.
Restore
The act of bringing files, settings, or a system back from a backup copy. A backup is only useful if a restore path is realistic enough to follow.
Snapshot
A point-in-time capture of a system, disk, folder, or service. Snapshots can be useful, but they still need clear notes and a tested recovery path.
Versioning
Keeping earlier versions of files so a bad change, overwrite, or accidental edit does not leave only the latest copy.
Offsite backup
A backup copy stored away from the main location. This can help if the original device, room, building, or local setup has a problem.
Local backup
A backup stored nearby, such as on an external drive, NAS, or local server. Local copies can be fast to use but should not be the only plan.
Cloud backup
A backup stored with an online provider. It can help with separation, but access, cost, sync behavior, and restore steps still need review.
3-2-1 backup idea
A common rule of thumb: keep three copies, on two types of storage, with one copy away from the main location. Treat it as a starting point, not a complete review.
Recovery point
How far back the restored data may be. If the latest useful copy is two days old, the recovery point is roughly two days before the failure.
Recovery time
How long it may take to get useful access back. This includes finding the backup, restoring it, checking it, and getting back to work.
Restore test
A planned check where you try restoring a file, folder, export, or system sample so you can see what works and what needs better notes.
Backup retention
How long backup copies are kept before they expire or are replaced. Retention affects how far back you can go if a problem is discovered late.
Access control
Who can reach the backup, restore it, change it, or remove it. Access should be clear enough to review before it is needed.
Documentation / restore notes
Written steps, locations, owners, assumptions, and gaps that help someone understand what to do during a restore test or recovery review.
Why these terms matter
Backup planning is easier to review when the words are clear and tied to real systems.
- The same words can mean different things across tools and teams.
- Clear terms make it easier to ask useful questions about backup readiness.
- A simple glossary helps turn vague backup confidence into something easier to review.
Use the glossary with the checklist.
Read the terms, then use the Backup Readiness Checklist to write down what is protected, where copies live, whether a restore has been tested, and what still needs review.
Need help turning the terms into a review?
Start a KITPro conversation. Keep the first note manual and focused on what you run, what matters, and what backup or restore questions you want reviewed.
Related resources
Keep going through the backup readiness resources.
Use these nearby resources if you want more context before starting a manual KITPro conversation.
Backup Readiness Checklist
Start here to see what is clear and what is missing.
Open resourceBackup Review Prep
Organize a useful first email before contacting KITPro.
Open resourceRestore Test Notes
Document what worked, what failed, and what needs attention.
Open resource