"Danger's platform was unique, and the migration would have to be done without disrupting the current user base," Enderle explained. Danger may have stopped doing full backups before Microsoft acquired it and perhaps did not reinstitute the practice.
That could have caused the delay in restoring data. "When the problem occurred, the redundant backup was not initially available, and Microsoft had to rebuild the database," Enderle said.
"Generally, unless the storage medium has been destroyed, there are a number of ways, all expensive, to recover from something like this, and it appears they were successful," he explained.
"The problem was the result of bad practices meeting bad circumstances," Charles King, principal analyst at Pund-IT, "but it does call into question what consumers can and should expect from a hosted services provider."
Microsoft had probably not fully audited Danger's IT procedures, according to Enderle.
"That's not an uncommon mistake in an acquisition, but one that can be avoided if the acquisition team doing the review is experienced," he said. "Mistakes can happen, and this was a big one."
0 comments:
Post a Comment