Last year I wrote about my backup strategy. Here are some new developments.
I'm still using rsnapshot for local backups, and duplicity for encrypted remote backups. I switched to the S3 backend for duplicity. (My meager data costs less than $0.10 per month to upload and store there.)
Things got a little more complicated when Sarah and I each got our own laptops. (Before that we shared a desktop computer.) I still use a git repository for my own home directory, but I wanted something simpler for files we share. And I want those files backed up even when we're away from our home network and storage server. Dropbox is the perfect solution. It syncs folders over the network, integrates perfectly into the Mac/Windows/Gnome desktop, and can share files publicly over the web or privately between Dropbox users. Most importantly, it has a simple way to view and restore previous versions of files that change. And (for my meager needs again) it's free!
The one part of my system that wasn't automated before was backing up data from various online apps. I wrote, "There's a business opportunity here for someone who can make this easier." In fact, I was seriously thinking about creating that business myself, but Backupify did it for me. They back up my data from Flickr, Twitter, Google Docs, Delicious, and GMail to my own S3 account. (They'll handle the S3 stuff if you don't have an account, but you can save money by registering your own.)
The reason I'm writing this now is that it's the last day of their blogging contest, so I can get some free stuff for telling them the feature or service I wish they'd support. Well, my number one service is LiveJournal (where I'm publishing this post). But more importantly, my number one feature would potentially allow them to support many services, even ones they've never seen.
Right now, each major web app has a different custom API for getting access to data. This means that Backupify doesn't support brand new or obscure services, because they need to write different code for each one. What I'd like to see is a standard for how services can use standard protocols like OAuth and the Atom Publishing Protocol to support export and backup of users' data. Then, as a web developer, I could support that spec and know that my users could employ existing software like Backupify to keep their data safe. There's an obvious chicken-and-egg problem here, but if Backupify could partner with a group like Google's Data Liberation Front to champion a new standard, then they could get some real momentum. (Google is a good candidate since they already support OAuth, and their GData API is based on APP.)