Today we are getting hammered with about half a foot of snow, so it is a good time to curl up in my office with some concentrated time to do my backups.
Earlier in the week, when it was still above freezing, I was working with some friends who have a small development shop here in town. I was helping them figure out their own backup strategy. They are smart folks, doing some cool things with computers, and have plenty of technical expertise when it comes to writing code and understanding how PCs work. What was surprising was how long our conversation took to understand their requirements, figure out what products they wanted to continue to use, and chart a course that would cover their data assets with enough redundancy but still be something that they would actually use on a regular basis.
When you think about it, backups are still far too hard. You need basic anti-virus/anti-spyware/personal firewall protection on each machine. You have to create bootable images, in case your drive goes south or gets corrupted with something that that collection of products doesn’t catch. You want a shared network data repository and backups offside of this information, in case a meteor hits your office (or a tornado, more likely around these parts). You want a spare laptop in case someone’s tanks or gets stolen. When you add up all these elements, backups could be a full-time job.
I have a rather complex backup routine that I use for my own data protection, and there isn’t anyone else in my office (most of the time) and most of my data resides on one computer. So I fully anticipated that it would be a lot more complex for my friends who have multiple computers. The hard part is to make it easy enough so that they could be motivated to follow through on a regular basis.
I will admit that my own backups are a chore that I don’t enjoy doing and only motivate myself to do it because I recall the consequences of an office fire many years (in my building, luckily both I and my office were untouched) or a stolen laptop from the trunk of my car in a Seattle shopping center. And as I was describing my own processes to my friends, I realized that there is still one place that I don’t have adequate backups. Actually, two places, and both because I use Web resources for creating some of my corporate mission-critical content: my WordPress blog and my Gmail address book. In the very unlikely situation that either of these companies go out of business or remove my data accidentally, I am totally toast.
Actually, part of my Gmail contacts did disappear for a little while last summer while the Google Guys were working on some update or something. For a day or so, I lost the use of the contact groups to organize my peeps. I could still see the individual contacts, but none of the group membership structure.
I realized then (and now) that there is no easy way to replicate this group structure, even if I do an export to a CSV of my entire contact list: all I get from doing that is just the contacts without any group memberships. After the disappearing group lists, I spent a few hours taking screenshots of each group list, realizing that I probably would never do that again and it was far too painful to be useful, but I did feel that I did something to prevent it from happening again. I was right: those screenshots were a one-time deal. I still don’t have a solution. Google, please get this fixed soon.
But the Strominator.com WordPress blog is more troubling, because there are lots of links and lots of content that I have created over the years and if that goes away, I don’t have much recourse and don’t even want to think about re-creating that stuff. So what to do?
One thought I had was to cross-post all my blog entries on another free blogging service, such as on Blogger or LiveJournal. It would be nice if one of them would be able to import an XML file or RSS feed and replicate the entire Strominator blog automatically, but alas that isn’t possible. None of the services will import the comments on my WordPress site – which could be a benefit for those of you that want to start with a clean slate. None of them will import the static pages of content that I have created, which are essentially links to my published archive. I guess I could cut and paste the HTML and save it as a local file on my desktop, but that seems so 1990s.
Multiply.com does have the ability to import blog entries from a bunch of different blogging services (including Blogger and LiveJournal), but not WordPress. Too bad.
Sigh. So I will have to go back and copy and paste my posts, which is a tedious process considering that I have several hundred posts on the darn thing. I did replicate last year’s just to see what it took, and I guess from now going forward I will cross-post for backup’s sake. But which service should I use?
One thought I had was to cross-post my old content on sites that have some social-networking patina so I can get some leverage and readership out of the effort. Scribd.com is one such site, but they are more geared towards uploading documents rather than straight HTML – I not only lose the comments but the embedded links with this service. Google’s Blogger is probably not going away, but do I want to trust Yet Another Googlicious Service for my content? Not sure about that. And LiveJournal has an extra step to get posts to be dated properly.
So nothing is perfect. I welcome your thoughts as always. At least my words are preserved on a few places around the Internet.
David,
WordPress is stored in MySQL. Zmanda backs up MySQL. I’m sure Dmitri could help with this.
…Bruce…
We back up our blogs (personal blogs, client blogs, business blogs) because it would be just too painful to lose years of effort. But backing them up is no big deal. First, all of our websites are backed up nightly to a separate dedicated backup computer. Came in mighty handy last week when the disk drive died on our webserver. Second, I periodically, like once a month or so, get a backup directly from the mysql database via using myphpadmin. I figure it’s less painful to lose a month’s worth of data than all of it. I save the current versions of each directly to a local backup drive. Most of our blogs are ExpressionEngine-driven, so we’ve gotten pretty comfortable with the tools provided with this application.
If you run your own WordPress server, several readers mentioned this plug in that will allow you to export backups of your blog database files:
http://www.ilfilosofo.com/blog/wp-db-backup/
It is called the WordPress Database Backup plugin. Configure it to backup
your database (including any additional tables you need). Set the option
to run a backup weekly (or daily, if you think that’s necessary), and
email the backup to a Gmail account you’ve set up.
Note that this doesn’t backup the files from your web site, just the
database. Most web hosts have some kind of automatic backup system you
can use for the files, and again, you can download them to your PC
occasionally (I just download the last backup each time I upgrade
Wordpress).
Also, the most awesome web site for explaining backup concepts is The
Tao Of Backup:
http://www.taobackup.com/
Another reader suggests ecto, which while designed for posting to blogs from your local drive, can work as a backup:
http://infinite-sushi.com/software/ecto/
(21 day free, $18 to purchase, both Mac and Win versions)
And I should mention that WordPress allows you to import an entire blog from various formats, as well as export the entire blog into a single XML file.
One more suggestion:
Another backup possibility is creating an offline
copy with a tool like HTTrack (www.httrack.com). This is not a solution
tuned for backups, but it would beat cut and paste. I have used this for
the purpose of keeping a historical record of what my blog has looked
like at various times in the past. A database table backup will only
keep the current state of the presentation theme, not the history.
Pingback: Sunday night links | clock — watching time, the only true currency
I lost a months work of blog posts and all of my pages on my wordpress.com blog this past weekend. As soon as customer service opened Monday morning I emailed then, but I am a bit worried that my blog has not yet been restored to the state it was in Friday or Saturday night. (Yes I guess I am a worry wart). I have been emailing them daily to ask for status — Has anyone had to have their WordPress.com blog restored using their backup? And if so how could you share with me how long does it generally take?
Thanks for your time.