Unconfigured Ad Widget

Collapse

Cloud computing snafu deletes Microsoft Sidekick T-Mobile data

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Steyr_223
    Calguns Addict
    • Sep 2002
    • 9480

    Cloud computing snafu deletes Microsoft Sidekick T-Mobile data

    LOL! Luv it!




    Cloud computing snafu deletes Microsoft Sidekick T-Mobile data
    Eight hundred thousand T-Mobile subscribers who use Microsoft's Danger Sidekick smart phones suffered the worst possible failure that can occur to anyone's personal data. All the customers' data - address books, calendars, to-do lists and photos was wiped out... kaput... gone... destroyed... forever and ever.

    This computing nightmare affects not only Sidekick owners but everyone who owns a smart phone who now have to question the integrity of their own devices.

    T-Mobile, the operator of the Sidekick's data service and Microsoft fumble to explain how this massive clusterfoot happened.

    T-Mobile's web site explains:

    Regrettably, based on Microsoft/Danger's latest recovery assessment of their systems, we must now inform you that personal information stored on your device -- such as contacts, calendar entries, to-do lists or photos -- that is no longer on your Sidekick almost certainly has been lost as a result of a server failure at Microsoft/Danger. That said, our teams continue to work around-the-clock in hopes of discovering some way to recover this information. However, the likelihood of a successful outcome is extremely low... Sidekick users "NOT reset their device by removing the battery or letting their battery drain completely, as any personal content that currently resides on your device will be lost."


    T-Mobile subscribers who use the Microsoft Sidekick smart phones loose all their data permanently in the Microsoft cloud
    The implication of the statement is Microsoft servers suffered a catastrophic failure and that there was no backup. How the f&^% is it possible there was no single backup on an enterprise so critical to the personal lives of tens of thousands of T-Mobile/Microsoft Sidekick users?

    This isn't the first time a Web service has crashed and left its users without access to data stored "in the cloud." Google's Gmail has had multiple outages but it has very quickly recovered with no data loss.

    This is the FIRST TIME a MAJOR cloud-computing vendor didn't have any backups. It is a total failure of systems from Microsoft's server operating systems, storage systems, processes, procedures and everything that shoulda, woulda, coulda happened.

    Folks, this is Microsoft we're talking about here. It's the same company who wants us to upgrade to Windows 7. It's the company who wants to be your cloud computing company of choice. It's the same company who sells server operating systems.

    The blame is also being shared with Hitachi Data Systems who provided the failed backup systems. It is being reported Microsoft contracted Hitachi Data Systems (HDS) to do remedial work on the server infrastructure and that, during the work, the server infrastructure failed. There were no backups or replicated data sets and so the data was lost forever.

    Further this involves a major telecommunications company - T-Mobile, not some small rural mobile phone provider. We need to understand so consumers know what to avoid in the future.

    In every company I have ever worked in or consulted for, backing up is part of Information Technology 101. I always advocate not only one backup but sometimes double and triple backups and minimum 30-day archives. How can Microsoft, Hitachi and T-Mobile allow this massive failure?

    Microsoft, Hitachi and T-Mobile must come clean and explain where and how the failures occurred lest they suffer the consequence of loosing the public and corporate enterprises' trust. For now till they explain their names are all in the mud.

    This is a complete failure. It would be a tough day to sell Microsoft server operating systems software today and even harder to sell Hitachi Data's backup systems... unless Microsoft, Hitachi and T-Mobile comes clean and explains how this massive failure can happen. If I were a company chief information officer or chief information security officer, I would have to do a complete double-take before I commit to a server operating system or backup solution that can suffer such catastrophic failure.

    The worst part of this (having owned a Sidekick) is there is NO EASY WAY to backup your Sidekick. It's supposed to do it for you. This absolutely sucks for T-Mobile subscribers who use the Microsoft Sidekick dumb phone.

    It's small comfort that T-Mobile suspended the further sales of Microsoft's Sidekick smart phone.



    Read more: http://www.sfgate.com/cgi-bin/blogs/...#ixzz0U2VNOVSQ
  • #2
    lazyworm
    Senior Member
    • Jan 2006
    • 1639

    I have some limited insider info on this event, which I can't post on a public
    forum. However, I can say it's not as simple as the article stated.
    At any rate, the subscribers are f'd, at least for the near term.

    Comment

    • #3
      Steyr_223
      Calguns Addict
      • Sep 2002
      • 9480

      Thanks! Do you know if it's true HDS was to blame or was it more complex?

      Comment

      • #4
        ilbob
        Senior Member
        • Jul 2008
        • 1777

        Originally posted by lazyworm
        I have some limited insider info on this event, which I can't post on a public
        forum. However, I can say it's not as simple as the article stated.
        At any rate, the subscribers are f'd, at least for the near term.
        seems pretty simple.

        data loss. no backup.

        why in the world would anyone create a utility of this kind that does not have a way to back it up locally? what moron came up with that idea?
        bob

        Disclaimers: I am not a lawyer, cop, soldier, gunsmith, politician, plumber, electrician, or a professional practitioner of many of the other things I comment on in this forum.

        Comment

        • #5
          NSR500
          Banned
          • Aug 2006
          • 19530

          Another reason not to trust "The Cloud".

          Comment

          • #6
            lazyworm
            Senior Member
            • Jan 2006
            • 1639

            Originally posted by Steyr_223
            Thanks! Do you know if it's true HDS was to blame or was it more complex?
            Generally speaking...
            There are multiple places where a problem like this could have happened.
            When there are multiple vendors involved, there will be finger pointing.
            So who's truly at fault may never be public, at least not for a long while.

            Comment

            • #7
              razorx
              CGN/CGSSA Contributor - Lifetime
              CGN Contributor - Lifetime
              • Jan 2008
              • 703

              This is not an indictment against technology or cloud computing. This is a completely an issue about people and process when this catastrophic.

              After all, making a backup(s) doesn't mean you can restore it.

              Procedures have to be in place to continually validate integrity of systems and data. Quite evident, this was the definitive failure.

              Comment

              • #8
                NSR500
                Banned
                • Aug 2006
                • 19530

                Originally posted by razorx
                This is not an indictment against technology or cloud computing. This is a completely an issue about people and process when this catastrophic.
                Technology and the Cloud are created and run by people and because of that they can be suspect.

                Comment

                • #9
                  artherd
                  Calguns Addict
                  • Oct 2005
                  • 5038

                  Honestly, I wouldn't trust Microsoft to feed my cat.
                  - Ben Cannon.
                  Chairman, CEO -
                  CoFounder - Postings are my own, and are not formal positions of any other entity, or legal advice.

                  Comment

                  • #10
                    JDay
                    I need a LIFE!!
                    • Nov 2008
                    • 19393

                    This is old news and the data has already been restored.
                    Oppressors can tyrannize only when they achieve a standing army, an enslaved press, and a disarmed populace. -- James Madison

                    The Constitution shall never be construed to authorize Congress to prevent the people of the United States, who are peaceable citizens, from keeping their own arms. -- Samuel Adams, Debates and Proceedings in the Convention of the Commonwealth of Massachusetts, 86-87 (Pearce and Hale, eds., Boston, 1850)

                    Comment

                    • #11
                      lazyworm
                      Senior Member
                      • Jan 2006
                      • 1639

                      Originally posted by JDay
                      This is old news and some of the data has already been restored.
                      Fixed it for you.

                      Comment

                      • #12
                        doughboy334
                        Senior Member
                        • Mar 2008
                        • 2019

                        sabatoge?

                        This past week's Sidekick data disaster was so extraordinary, you would think that either T-mobile or Microsoft would issue an explanation. There's one
                        sigpic

                        Originally posted by Jpach
                        Just do what M Sage and others have said to do, they know what theyr talkin about. Just dont urinate in your barrel and expect ur rifle to be ok. My buddy and I recently went shooting and he shot corrosive yugo ammo through his Mosin and figured he could just piss in the barrel and call it a day. Several days later the bolt was rusted shut but I guess the fouling wasnt TOO bad.

                        Comment

                        Working...
                        UA-8071174-1