Comments on: That fragile thing we call the Internet http://aralbalkan.com/1281 Passionate geekisms. Sun, 12 Feb 2012 17:52:56 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Ms. Jen http://aralbalkan.com/1281/comment-page-1#comment-131011 Ms. Jen Sat, 29 Mar 2008 22:41:26 +0000 http://aralbalkan.com/1281#comment-131011 I use Movable Type, which means I have static files, but I also once a month back up the whole of the database as a sql file and I do I "export" text back up of my posts. I am pretty covered. smiles, jen ;o) I use Movable Type, which means I have static files, but I also once a month back up the whole of the database as a sql file and I do I “export” text back up of my posts. I am pretty covered.

smiles, jen ;o)

]]> By: James Aylett http://aralbalkan.com/1281/comment-page-1#comment-130906 James Aylett Sat, 29 Mar 2008 15:53:59 +0000 http://aralbalkan.com/1281#comment-130906 The problem isn't backups - it's knowing whether your backups are useful (which is what happened with Coolz0r: they weren't). So I'd recommend (assuming you for some reason cannot put in place something more frequent) backing up your blog (and any other bits of your website) once a month, and *at least once a year* rebuilding them onto another site. (These days that other site could quite happily just be running on your laptop.) It demonstrates that you actually have all the useful ducks lined up properly. You also have to be able to notice within the schedule of your backup cycle when something has gone wrong; with a large site and very old data, this is harder than it sounds. Keeping periodic backups forever avoids this problem (although it might still be a huge amount of work to recover to the last known good state if only part of your site gets corrupted). (Better yet is to do say db dumps and incremental backups every day, full backups every month, and test restore some stuff at random out of everything you back up on a regular schedule. I'll admit that last bit is something I'm not strictly doing...) The problem isn’t backups – it’s knowing whether your backups are useful (which is what happened with Coolz0r: they weren’t). So I’d recommend (assuming you for some reason cannot put in place something more frequent) backing up your blog (and any other bits of your website) once a month, and *at least once a year* rebuilding them onto another site. (These days that other site could quite happily just be running on your laptop.) It demonstrates that you actually have all the useful ducks lined up properly.

You also have to be able to notice within the schedule of your backup cycle when something has gone wrong; with a large site and very old data, this is harder than it sounds. Keeping periodic backups forever avoids this problem (although it might still be a huge amount of work to recover to the last known good state if only part of your site gets corrupted).

(Better yet is to do say db dumps and incremental backups every day, full backups every month, and test restore some stuff at random out of everything you back up on a regular schedule. I’ll admit that last bit is something I’m not strictly doing…)

]]> By: Rob http://aralbalkan.com/1281/comment-page-1#comment-130846 Rob Sat, 29 Mar 2008 12:09:26 +0000 http://aralbalkan.com/1281#comment-130846 Having just got a TimeCapsule, I'm in a backup mood! Think it's a great idea! Having just got a TimeCapsule, I’m in a backup mood! Think it’s a great idea!

]]>