Guides
Backups you have actually restored
Demo Author
Published: 1 min read
Most teams have backups. Far fewer have restored one recently. Until you do, you do not know whether they work, or how long a recovery takes.
Three copies, two kinds of storage, one far away
Keep three copies of your data, on two kinds of storage, with one copy in another place. A fire, a failed disk or a deleted account then cannot take everything at once.
Restore on a schedule
Every month, restore a recent backup to a separate machine and check that the application starts and the data is complete. Write down how long it took.
How much data you can afford to lose, and how long you can be offline. They decide how often to back up and how fast a restore must be.
Practise the bad day
Once a year, walk through a full recovery with the whole team, so the first real one is not the first time. Talk to us about your recovery targets.
Related posts
Handing over the night shift and the patching
TechnologyAlerts at 3am and patches nobody has time for wear a team down. Here is what changes when someone watches the systems around the clock.
Moving an old system to the cloud, one step at a time
GuidesA big-bang migration bets the business on one night. Moving system by system, with a way back at every step, keeps the work running.
