How to get backups right
This is one of those topics that looks small until it costs you something. The short answer to backups is that it is mostly a sequence of small decisions, not one big one.
Security is a maintenance habit rather than a purchase, which is why it drifts. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
What is actually at stake
An untested backup is a hope, not a backup. Small and consistent beats large and occasional here. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.
The steps
- Establish what you have today before changing anything
- Keep a copy somewhere the main system cannot reach
- Know how long a restore actually takes
- Write down the decision so the next person does not re-litigate it
Know how long a restore actually takes. In practice this is a scheduling problem more than a technical one. It is the sort of thing that looks like polish right up until it costs you an enquiry.
What to do next
The short version
The cheapest security work is the boring kind done on a schedule. Three things worth confirming about backups before you move on:
- Someone can say what the current setup is without going to look
- Keep a copy somewhere the main system cannot reach — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Worth checking on your own setup before it becomes someone else's problem to fix.