How I handle backups. Or, happy world backup day!

For most of the world, it’s Easter. at least, on the east coast, for the next… we’ll say… less than an hour. But for anyone who maybe doesn’t cellebrate easter, or has maybe more important things on their plate besides that, today is also world backup day. In honour of that, let me tell you how I work.

I’m insanely paranoid about my backups. To the point where at any given time, it can be pretty well guaranteed I know exactly what’s backed up where, and have backups of those in at least two other places. Let me run things down on a basic level. The server hosting this website has 2 hard drives, both of them 2 TB. On the first is everything I’m running–the OS, the software that runs the site, email, you name it. On the second, is every single configuration file, line of code, database, log file, random thing that just doesn’t really have a home in any other category. And on that drive, it’s backed up in 3 different locations–just in case one of them goes on vacation. Or, you know, on the off chance I need to quickly pack up and slingshot my crap from this server to some other in an aweful goddamn hurry. The advantage of also doing it this way is, pretty much on demand, I can grab a copy of that backup, and pull it to any location I choose with enough room to hold it–like, we’ll say, somewhere local if I suspect some fool’s intent on nuking the server. It also allows for a bit more flexibility–let’s say, for instance, I decide to once again fire up a Dropbox instance on the server. Configuring it to serve as a thing to hold backups would be only too easy, and actually be moderately a painless process. The advantage to that of course being I’d have local access to those backups, regardless what my definition of local is, so long as I have access to Dropbox. Kind of makes emergency “Oops I screwed it good” recovery a thing.

What does that mean for the hosted folks? In short, barring a nuclear bombardment that takes out the entire eastern/central region of North America, anything and everything data is relatively breakageproof. Of course if a nuclear bombardment on that scale ever becomes a thing, I suspect “where’s my crap” won’t be the first question on the list. But this also gives me a personal thing I can use later, should I ever manage to stop being bounced around and actually shove my foot in a professional door just enough so that it’s not slammed on my nose. I’ve had absolutely no professional training in this or any other area, and I’m more comfortable with the backup solution I have right now than I would be if I was paying someone else to do it. Largely, I suspect, because I know exactly where everything is and it’s a simple copy/paste if ever I need to unbreak something. But, I think, also because if it does go sideways, I don’t need to worry about holding someone else to account who doesn’t have a dog in this fight. It’s my data. It’s my friends’ websites. It’s another friend’s email. It’s all very good reasons for me to pay the fuck attention. And that, I think, is how I work best. Which reminds me. I think I’m due for a local copy pull…

, ,

One response to “How I handle backups. Or, happy world backup day!”

  1. As one of those friends with the websites and emails and what have you, allow me to say that I very much appreciate those backups.

    And also let me say that it is now April, and since the old deal is up, it’s time to figure out how much money is changing hands so as I can continue having websites and emails and backups. I mention this publicly since private got me nowhere and I feel it necessary to enlist the help of others. So people, let James know that free is not an option even though he says it is. I appreciate the kindness, but he deserves at least a little something for his time.

Have an opinion?

recent Posts

Recent Comments