Backing Up the Weakest 2.0 Link
by Ewan Spence
Where is your data’s weakest link? In the rush to return to mainframe like applications and dumb terminals accessing them… sorry I mean rich Web 2.0 sites running powerful applications on any platform via the web browser… it’s worth considering your worst case scenarios. While these services are run by large companies, with bundles of cash and servers, problems will happen…
Apple’s MobileMe service has had a rough launch, including loss of emails and access to many of its users.
Google’s Gmail service went down recently for a few hours not because of problems with the mail server, but because the Contacts app section was broken.
Amazon’s S3 storage had some server issues, which resulted in a number of sites loosing access to their files, Wordpress.com being one of them.
I’m not deliberately picking on these specific issues, but to use them to illustrate that… er… stuff happens. And if your strategy relies on these services, you’re passing over a vital part of your infrastructure to these third parties. Some form of back-up or second level that defaults back to your site or a reserve archive makes business sense.
So consider that, and ask yourself if you’re comfortable with the emerging way of mobile phone applications being built around the client/server model. Even though the power, capability and storage of modern handsets are in excess of the PC’s we were using a few years ago, there are more and more applications keeping the data on an external site.
Is this what you want for your personal data? For it to be held somewhere else, where anything could happen to it? And that’s not just loss of access or loss of data, but Amazon S3 comes under the jurisdiction of the US government – for UK users who are comfortable with something like the Data Protection act, those restrictions just aren’t in place in the US. Overtly paranoid maybe, but it’s one consideration. And there is always the nightmare of what happens if the company you are using goes bust (and that should be a primary concern with web 2.0 style start-ups!)
The solution, for me at least, is two fold,. The first is to only use applications that allow me local storage on my phone (and this they become part of my backup strategy for my phone); the second is if this isn’t possible, the web part of the app must allow me to ‘dump’ the data out to an archive file in some form, or let me get to the data.
It’s not perfect, but if I know I can reconstruct my data when the server of ‘cool idea’ goes boom, I’m happy. Can you say the same for your information?














