Backup and restore procedures

[mack]

We all have rock solid backups... right?

But in the event, you lost a disk or had a serious hardware malfunction would you be prepared for recovering data. I had the chance of trying this out today when I finished building a new system. and had to "recover" data from my backup server.

My suggestion is to have a document written in advance with a clearly defined list of steps that need to be followed. You should also print this off because you may or may not have access to a system.
When doing a recovery, everyone's situation will be different. but you may well find your situation requires things to happen in a certain order. There may be files that need to be brought over first, there may be software that needs to be installed and configured using files within your data.

Having a properly written list will help speed up the process, and being able to write in whilst not in the midst of a data disaster will help you think the process through clearly.

Mack.

[phranque]

a couple of previous threads with some good information:
Beyond backup: preserving your web data [webmasterworld.com]
Backup Strategies [webmasterworld.com]

[LifeinAsia]

You should also print this off because you may or may not have access to a system.

I would recommend keeping an updated copy in a cloud storage account (like Box) in case you forget where you put the paper copy. Also, that way you don't have to print another copy each time you make a major change to the procedure.

[Lexur]

I have four documents saved in a pendrive (always in my keyring) and printed:
- core business strategy (just to know what I'm doing and why, and some metrics for my success or -lately most frequent- failure)
- passwords
- backup and restore procedures
- expiry dates (domains, trademarks, online services, insurance and so on)

[graeme_p]

Its good practice (but a huge nuisance) to occasionally test that you can restore.

Its also good to have scripted reproducible setup for things like really critical servers.

[mack]

Its good practice (but a huge nuisance) to occasionally test that you can restore.

I hear you, ashamed to say but yesterday was the first attempt I had made at a recovery. I had just been assuming I knew how it would work. Turns out even for my fairly simple solution, there were a few things I had to change during the process.

Scary to think many people simply have no backup solution. That to me would be terrifying!

Mack.

[graeme_p]

Just because I say its good practice does not mean I actually do it.

Mostly I recommend it and do it if the client is willing to pay for it.