Microsoft says it had Sidekick data backup, but it was hit, too
techflash.com
techflash.com
A few months ago Google had a large multi-hour App Engine outage. Afterwards (within 24 hours?) they posted a detailed technical explanation/postmortem online for anyone interested to read, with a play-by-play that even went minute-by-minute.
Microsoft/Danger owe their customers more of a real explanation.
That's got to be the best non-answer answer I've read in a long time. And no - redundancy and stability of the service have nothing to do with the backup policy.
It was them. Those bastards we bought. I mean, sure that was almost a year ago, and most of the original employees are gone, but do keep in mind when we're talking about this that it's not a proper MS offering.
Unless you like it. Then yay us.
The very reason to have a legitimate backup is that it cannot be damaged by the same mechanisms that can damage your primary data. It should be inert, if possible, or at least to some extent immutable, and it should be offsite.
RAID is not a backup. SAN is not a backup. Mirroring to a redundant storage array is also not a true backup.
Backups are hard to get right, and expensive. But the cost of getting it wrong can be monumental.
It goes even farther than that:
Real backups mean that at some level you can recover that data
The smart thing would be for Microsoft to think of the employees: what management decision is likely to make working in that group least likely to suck over the next few months? If it were me, I would invest in technology and hires/transfers, not in bureaucracy. I would give that group everything it needs to build and rebuild that system twice. After all, doesn't Microsoft have the money for that?
Friend: Sir, my hard disk partition crashed and the project files are all gone.
Lecturer: Don't you have a back up?
Friend: The backup was on the same partition.
It might even kill off some of the smaller cloud-based players...