Cloud-computing : "Micro$oft/Danger. Enough Said."

Story: Jolicloud to usher return of thin clientTotal Replies: 20
Author Content
henke54

Oct 12, 2009
4:32 AM EDT
Quoting:In the canon of Microsoft cock-ups, this may be the most humiliating: A server failure at the company’s Danger subsidiary has wiped out the personal data of a large number of T-Mobile Sidekick users and despite its best efforts, Microsoft cannot seem to get the information back.
http://digitaldaily.allthingsd.com/20091012/sidekick/
TxtEdMacs

Oct 12, 2009
9:54 AM EDT
I think you people are being too hard on MS.

Really, even the FTC will not bring a case against them, because right in the name their customers are fore warned.

See it's so easy to defend my favorite vendor of quality software and services.

YBT

PS I await my check with strong anticipation, don't stint on the amount.
bigg

Oct 12, 2009
10:06 AM EDT
> despite its best efforts, Microsoft cannot seem to get the information back

Did they try a FOSS tool? There's probably something on Sourceforge that could do the job.
tuxchick

Oct 12, 2009
10:16 AM EDT
Nice idea, bigg, but they're probably command-line.

Just think, if it weren't for MS we would have no one worthy to mock.
jdixon

Oct 12, 2009
10:22 AM EDT
> ...but they're probably command-line.

Actually, since the filesystems involved were undoubtedly NTFS, I don't think there are too many FOSS tools for dealing with them. We can do basic reads, writes, and size changes; but filesystem checks and repairs are probably beyond anything we have.

> ...if it weren't for MS we would have no one worthy to mock.

Oh how I wish that were true, TC. But demonstrating a disproof would get me into TOS violation territory rather quickly. :)
TxtEdMacs

Oct 12, 2009
1:35 PM EDT
To all you foolish people, who think this was an accident: at least one site has speculated that this failure of the cloud enhances or at least lengthens the cash flow of MS's desktop offerings.

MS screw up? Never!

Watch MS crying while running to the nearest off shore bank to money launder their cash flow excess. So berate them, but it is too foolish to under rate them.

YBT
montezuma

Oct 12, 2009
9:11 PM EDT
Um this might be a touch naive but how often did MS/Danger do backups? Weird old M$
azerthoth

Oct 12, 2009
9:14 PM EDT
ooh nice touch ybt.
caitlyn

Oct 13, 2009
1:16 AM EDT
I like Txt's conspiracy theory. I could almost believe that Microsoft would want to sabotage cloud computing and bring us all back to our nice, comfortable, Windows desktops. Remember, nobody actually runs Linux so we all must run Windows. I know this because Microsoft and their supporters keep publishing "market share" numbers that have to be true. Microsoft would never lie, would they?
jacog

Oct 13, 2009
4:43 AM EDT
The internet is nothing but a fad, anyway... innit?
TxtEdMacs

Oct 13, 2009
11:03 AM EDT
Folks, please you forget my actual role on LXer, i.e. "resident shill / astroturfer" with some weak humor thrown in the mix. So do not put my income at risk with compliments. Remember even a completely broken clock / watch tells time twice a day albeit only once for the military versions.

So one has to reflect, whose interests are served best by the reported fiasco? MS gets a black eye, hardly - all is forgiven too soon or simply forgotten, but their long term interests seem to be well served by letting the cloud be the culprit. MS wins by playing up the damage on a program where they would be only a "me too ... " bit market player.

YBT
gus3

Oct 13, 2009
11:11 AM EDT
Quoting:Remember even a completely broken clock / watch tells time twice a day albeit only once for the military versions.
A stopped clock is no more useful than a smashed clock.

A clock that is consistently three minutes behind may always tell the wrong time, but it's still more useful than a stopped clock.
jdixon

Oct 13, 2009
11:16 AM EDT
> A clock that is consistently three minutes behind may always tell the wrong time, but it's still more useful than a stopped clock.

And what use is a clock which tells you whatever time best suits its purposes at the moment? :)
bigg

Oct 13, 2009
11:31 AM EDT
> A clock that is consistently three minutes behind may always tell the wrong time

It always tells you the right time. You just have to read it correctly. In some places, the "time" is whatever is on the clock in the room you're working. Different rooms have different times, hence you have to read your watch correctly depending on where you will be working so you're not late.

> MS gets a black eye, hardly

It was obviously a hardware problem. It's so obvious that nobody bothered to collect evidence showing that it was a hardware problem.
Steven_Rosenber

Oct 13, 2009
2:54 PM EDT
I hadn't heard what kind of hardware and OS this "Danger" company was using, but I did read that the fail took out the backup along with it.

Also disturbing is that these Sidekick devices don't store their contact information in NVRAM on the phone. It's all with the provider, or was at any rate.
jdixon

Oct 13, 2009
3:07 PM EDT
> ...but I did read that the fail took out the backup along with it.

They were probably just running a RAID array without any other backup. If the controller fried, it may have corrupted the entire array beyond repair. Now, why they didn't have tape backup is another matter.
bigg

Oct 13, 2009
3:28 PM EDT
> I did read that the fail took out the backup along with it

Then they didn't really do a backup. Similarly, I know a lot of users who copy their data to a CD and stick it in their desk. If there's a fire, the backup is gone. Plus there's a copy of your data readily available to thieves.
Steven_Rosenber

Oct 13, 2009
3:31 PM EDT
The various rumors about Sidekick/Danger/Microsoft are:

-- They were upgrading the Storage Area Network and didn't do a backup, after which the upgrade failed

-- Sabotage

-- "dogfooding" ... and I did not make up that word, which means "eating their own dogfood," e.g. Microsoft replacing non-MS technologies with their own.

I did a bit of a roundup on Sidekick today but didn't post it to LXer because I feel it's more than a little OT (and will be so unless further details change that assessment).

But if you want the latest rumors, I do have 'em:

http://insidesocal.com/click/2009/10/sources-microsoft-forgo...
bigg

Oct 13, 2009
3:33 PM EDT
According to SJVN, they did an upgrade without doing a backup:

http://www.itworld.com/security/80819/sidekick-microsofts-bi...

Quoting:while neither Microsoft nor T-Mobile is saying exactly what happened, it appears that Danger didn't back-up its servers before launching into a major, and failed, SAN upgrade.

I don't know about you, but any where I've ever worked, not running a backup before any major upgrade is a firing offense. And, not just any firing, this is a "don't let your feet touch the floor as the security cops run you out of the building" crime.

This isn't just a tech problem though. This is an organizational problem. This is a case where firing them all, from the top down, and letting unemployment sort them out is appropriate. There is simply no way on Earth that Microsoft should have tried this 'upgrade' without knowing that a backup was set, checked, and ready-to-go.
montezuma

Oct 13, 2009
6:05 PM EDT
LOL. So they didn't backup before an upgrade huh! What a bunch of morans.

Maybe if we are really lucky the same thing will happen to the source code for Windows 7

This is what happens if you are a monopoly. Standards fall.
gus3

Oct 13, 2009
7:05 PM EDT
Quoting:Maybe if we are really lucky the same thing will happen to the source code for Windows 7
"Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)" -- Linus Torvalds

Given the likelihood of Windows 7's code already having leaked, I doubt it will disappear.

Posting in this forum is limited to members of the group: [ForumMods, SITEADMINS, MEMBERS.]

Becoming a member of LXer is easy and free. Join Us!