0
J
u
n
e
2
0
0
6
Backups matter
I read today that CouchSurfing has closed. CouchSurfing was a site that allowed people to offer their homes for free accommodation to travellers. It was three years old and had some 90,000 members.
It closed due to catastrophic failures in some of the operational aspects of the site:
- a hard drive crash that was avoidable
- incorrectly executed incremental backups
I used to work for a company that didn’t have proper backup procedures – not only for itself, but also for its major product. In both cases, checks weren’t performed to ensure that it was possible to recover from backup.
Backups are rarely seen as a necessity in small businesses and few organisations are committed to the time and effort necessary to ensure that its complete and correct. It’s essential and critical. Because, as the CouchSurfing experience demonstrates, if something goes wrong it can close your business.
We’re unlike most businesses. We have an implicit advantage in that we develop locally and deploy to remote servers. In a sense that’s an automatic backup, although that doesn’t give us the ability to rollback. And we rely on the owners of those servers to back them up in accordance with their terms of service. Service availability and backups are less than ideal, but commensurate with the expectations of our customers. Even so, the more we use other companies, the more we are coming to realise that one day we will need to do it all ourselves.
We use Subversion to commit and manage changes to our work, on our local servers. Thus, our servers have the entire lifetime of each project, with individual employee’s computers retaining just the local ongoing work.
But that’s not all. We also backup our servers. A custom-developed automated process uses the internet not only to ensure that we have both an incremental backup, but that we also have an off-site backup. This gives us, in total, three or four distinct places that our work is stored.
Yes, it’s been tested, and yes, it’s saved our business.

