One way to address these kind of problems is to use cloudHQ to synchronize your Google Docs with SugarSync (clickable: http://cloudHQ.net/sugarsync). (We are releasing dropbox this weekend).
Here is our idea: there are many different cloud storage services and each of them is very good for a particular use case but not so good for other use cases. For example, Google Docs service is excellent for collaboration but not so good for storage. On the other hand, Dropbox or Sugarsync service is excellent for storage but not so for collaboration.
So if data is continuously synchronized between Google Docs and lets say SugarSync storage, then you can always fall back to SugarSync when Google Docs becomes unavailable and vice versa. In order words, you can use other service as a standby site in case of service unavailability, malicious or accidental deletion of files, etc.
He talked me through all the design considerations they had to do for their backup system for the datacenter here. It's a lot of work, but there is a lot of business value in having a working backup system.
But Google Apps is a pain in the butt to backup, since we don't have direct file access to things. The best strategy I can see, if you want to stick with it, is to email yourself every file, every edit. That's pretty insanely tedious.
Automatic daily Google Apps backups -- all of it, even Google Sites -- for just $3 per user per month. Unlimited storage. One-click restore for Google Docs and Gmail messages. And we're soon rolling out full-domain search, so you can query all your Gmail, Docs and Calendar accounts simultaneously.
We also backup your Twitter Feed, your Facebook Pages and your Flickr or Picasa photo albums, should the need arise.
Also, for the record, we have a 1-800 number that we actually answer, so in the event you have trouble with our service, we'll pick up the phone and talk you through the fix. We can't repair your Apps account, but we can darn well make sure you get to the data that's in it. We wouldn't charge you, otherwise.
Do you have any integration (or plans for integration) with Dropbox? I'd love to sign up to a service that simply dumps a copy of all my backed up files to a Dropbox folder somewhere, once a week.
Our Pro 500 plan is $19.99 per month and includes 10 Google Apps users and unlimited storage. That actually breaks down to less than $2 per user per month. Beyond that first ten, additional users are $3 per user per month. I usually just quote the $3 figure for simplicity's sake, especially since most admins using a paid Google Apps domain (Google Apps Premium) have more than 10 users anyway.
[1] http://code.google.com/googleapps/appsscript/service_docslis...
But he's an operations guy like me, and he probably wears both a belt and suspenders just in case the belt breaks. So in response to the complaint that emailing yourself files to insure you have copies is a pain, I suggested he script the moral equivalent using Google's provided APIs to the docs service.
I know you can use pop (and maybe imap) to pull email out of GMail. but can you recommend a product that can handle slurping and backing up all the mail for your domain?
You can also do it direct from the web UI. Just select all your documents from the Google Docs homescreen, click on the "Download..." link in the righthand column, and it will ask you what formats you want then generate a zip file to download.
I don't know of a command line script that uses OAuth (GDocsBackup has a command line mode but uses password auth.) Anyone?
There are plenty of apps on the marketplace. I assume they're all automated.
There is probably a business idea here.
Shameless plug: This is why I wrote my app, CloudPull. CloudPull backs up your Google Docs, Calendars, and Contacts to your Mac. If for any reason you are unable to access your Google account, CloudPull ensures that you have backups of your Google data on your Mac.
More information about CloudPull is available at: http://www.goldenhillsoftware.com/
The real story here is that a paying customer was unable to get anything better than a free user.
FWIW, I must be lazy or something, but I don't think the user of a VERSIONED online document storage service should be reasonably be expected to also have his/her own backups. What the hell am I paying for then?
Why can't there be two stories?
If I park my car and don't lock the doors, and come back to find it gone, is the story that I'm an idiot for leaving a car unlocked, or is the story that the neighborhood is unsafe?
They're both problems, but I can actually solve one of them myself. That doesn't excuse the $BAD_THING that happened, but it does offer me options for when it inevitably does.
So in your analogy: You park your car at a garage with a guard, pay them to keep it safe and leave your car unlocked. And when you come back it's gone.
Yes he could have done something to make it less likely it, but he also explicitly paid someone else to handle it for him.
Because it seems to be a foreign concept in this day and age, I will repeat it again.
You always backup.
I entirely agree- When things are mission critical to you, you need them in an environment where you can control it, back it up properly, and ensure it stays up.
We're not a priority to Google (Understandably.)
For things that really matter to your company, you should bring them in-house, so you can ENSURE they're backed up, and available when necessary. At least that way when things do fail, you can make fixing it a top priority, rather than a nice-to-have.
The reality is that Google is much less likely to damage or lose your data than you are, but it's always good to keep extra copies around locally. This is important for many reasons, like access when either Google or your whole net connection is unavailable, and more flexibility with the data.
In-house IT fails plenty of the time also, and plenty of organization cannot afford to fix some failures. One must consider the probabilities in all cases.
Personally, I think this applies to yourself, too. As much as possible, make it difficult for you to overwrite your own backups before they expire. If possible, encrypt and outsource.