A backup with a green tick can still leave you nervous.
That sounds strange until you need to restore something.
The backup job passing is good. It means the process ran. But it does not answer every question that matters during a real problem.
Can we restore it?
How long will it take?
Who knows the steps?
Where do we restore to?
What access is needed?
Has anyone tested this recently?
Those questions matter because recovery is different from configuration. It is possible to have backups enabled and still be unsure what would happen under pressure.
I have learned to respect restore testing.
Not because every environment needs a huge exercise every week. That would not be realistic. But some kind of evidence is needed. A backup strategy that nobody has tested is partly a hope.
The same applies to documentation.
A restore process should be readable by someone tired, busy and under pressure. It should not depend on one person remembering the magic steps. If it does, the system is more fragile than it looks.
Backups also need ownership. Someone has to know what is protected, how often, where it is stored and what the recovery expectation is.
Not every system needs the same recovery target. A test box and a business critical database are not the same thing. But the decision should be clear, not accidental.
I like simple recovery questions:
- What are we protecting?
- What failure are we preparing for?
- How quickly do we need it back?
- Have we tested the restore?
- Where is the evidence?
These are not exciting questions.
But when something breaks, they become very important very quickly.
A green tick is a start. Recovery confidence needs more than that.