Checklist

Backup restore checklist: questions that show if you can recover.

Use it for servers, apps, NAS, files, and SaaS exports. The goal is restore proof, not a pretty backup checkbox.

RTO exemplu38 minRestore testOKDovezi lunareIncluseSLA uptime99.98%

An untested backup is an assumption. During an incident, assumptions become downtime, missing data, and decisions made under pressure. Nobody needs that kind of creativity.

This checklist is for managers and operators. No deep jargon. It only asks for a concrete answer: what can we restore, how fast, and with what accepted data loss?

Checklist

Things to check

Inventory

  • Which servers, VMs, apps, databases, and files are critical?
  • Who owns each workload?
  • Which data changes daily and which data can be recreated?

Backup policy

  • How often does backup run?
  • How long are copies kept?
  • Is there an offsite or isolated copy?

Restore proof

  • When was the last restore test?
  • How long did it take?
  • What data was missing or which steps were unclear?

Incident

  • Who decides recovery priority?
  • Where is the runbook?
  • How do you communicate if the main systems are down?

FAQ

Useful clarifications before the technical call

How often should restore be tested?

For critical systems, monthly or quarterly. The right rhythm depends on data change and downtime impact.

Does this checklist replace backup architecture?

No. It finds gaps fast. The architecture still needs to be designed and tested for each important workload.

Restore proof

A backup is useful only after restore works.

We test one restore, document the gap, and give you a readable RTO/RPO note. Not a scary report. A useful one.