Skip to main content

MSFT: We've Got Most of the Sidekick Data Back

Earlier this week Microsoft/Danger and T-Mobile announced that all Sidekick data stored on Danger's servers was gone and the likelihood that they'd get any of it back was "extremely low." Up until now, T-Mobile has been the one making statements and offering compensation. Today, Microsoft released a statement detailing what happened that the company lost customer's data in the first place and informing users that most of the data had been retrieved.

"We are pleased to report that we have recovered most customer data for those Sidekick customers whose data was affected by the recent outage," said Roz Ho, Corporate Vice President of Premium Mobile Experiences at Microsoft.  Ho went on to say that Microsoft would begin restoring users' personal data as soon as possible, starting with personal contacts and added that Microsoft now believes the data loss only affected "a minority of Sidekick users."

Now on to the juicier topic of how it all happened in the first place.  Despite reports during the week that say it could only have been an attempt at sabotage from a vexed employee, Microsoft is still pointing the finger of blame at a server failure, claiming it had to rebuild the system piece by piece to retrieve all the data.

"We have determined that the outage was caused by a system failure that created data loss in the core database and the back-up," said Ho. "We rebuilt the system component by component, recovering data along the way. This careful process has taken a significant amount of time, but was necessary to preserve the integrity of the data."

Which do you think is more likely, sabotage or server failure? Let us know in the comments below!

Check out the full letter below (via CNet):

Dear T-Mobile Sidekick customers, On behalf of Microsoft, I want to apologize for the recent problems with the Sidekick service and give you an update on the steps we have taken to resolve these problems. We are pleased to report that we have recovered most customer data for those Sidekick customers whose data was affected by the recent outage. We plan to begin restoring users' personal data as soon as possible, starting with personal contacts, after we have validated the data and our restoration plan. We will then continue to work around the clock to restore data to all affected users, including calendar, notes, tasks, photographs and high scores, as quickly as possible. We now believe that data loss affected a minority of Sidekick users. If your Sidekick account was among those affected, please continue to log into the T-Mobile Sidekick forum at http://www.t-mobile.com/sidekick for the latest updates about when data restoration will begin, and any steps you may need to take. We will work with T-Mobile to post the next update on data restoration timing no later than Saturday. We have determined that the outage was caused by a system failure that created data loss in the core database and the back-up. We rebuilt the system component by component, recovering data along the way. This careful process has taken a significant amount of time, but was necessary to preserve the integrity of the data. We will continue working closely with T-Mobile to restore user data as quickly as possible. We are eager to deliver the level of reliable service that our incredibly loyal customers have become accustomed to, and we are taking immediate steps to help ensure this does not happen again. Specifically, we have made changes to improve the overall stability of the Sidekick Service and initiated a more resilient backup process to ensure that the integrity of our database backups is maintained. Once again, we apologize for this situation and the inconvenience that it has created. Please know that we are working all-out to resolve this situation and restore the reliability of the service. Sincerely, Roz Ho Corporate Vice President Premium Mobile Experiences, Microsoft Corporation

  • curnel_D
    Sabatage! No one cares about server malfunctions. It's much more fun to think it was someone on a revenge induced rampage.
    Reply
  • the_krasno
    Still this doesn not explain the failure in the back up servers.
    Reply
  • magicandy
    Server failure. The sabotage thing was most likely a scapegoat created just in case they couldn't recover the data.
    Reply
  • JMcEntegart
    Curnel_DSabatage! No one cares about server malfunctions. It's much more fun to think it was someone on a revenge induced rampage.
    Agreed. Who's says life at Microsoft can't be sexy?
    Reply
  • zak_mckraken
    MS is still screwed in the lawsuit. Even if they do manage to recover all lost data, the fact that they stated they recovered "most" of the user data is the perfect opportunity for people to claim they are still lacking data, even though they don't. People are just that greedy.
    Reply
  • warezme
    Sabotage derived from the Netherlands when workers would throw their wooden shoes or sabots into the textile mills to break them as explained in a star trek movie.
    Reply
  • bydesign
    Got to love cloud computing... This is just the tip of iceberg with this technology. The real destater will be the modern day equivalent of the destruction of the great library of Alexandria.
    Reply
  • ssalim
    Server outage and the backup too? Yea right. For a small newbie company maybe but for Microsoft/Danger? No way in hell.

    S-A-B-O-T-A-G-E
    Reply
  • ravewulf
    bydesignGot to love cloud computing... This is just the tip of iceberg with this technology. The real destater will be the modern day equivalent of the destruction of the great library of Alexandria.I think one of the better ways we could implement cloud computing is if data is stored locally as well as in the cloud. They both can act as data redundencey and the cloud can be used to sync changes between all connected computers. There should also be a safety mechanism for when data is deleted on a device. Windows Live Mesh seems to do this fairly well, even if it is still in beta.
    Reply
  • dextermat
    Once again, that well known company put themselves; "sucks" in Microsucks lol
    Reply