InvestorsHub Logo
Followers 0
Posts 625
Boards Moderated 0
Alias Born 03/25/2004

Re: jay1000 post# 84478

Wednesday, 01/09/2008 3:48:29 PM

Wednesday, January 09, 2008 3:48:29 PM

Post# of 97722
Jay1000:

It crashed in the middle of December 2006. It corupted the disks so bad, they had to be reloaded from scratch. A complete rebuild to disk was necessary and that took all day. It was in place since April, 2006 or about 8 months. That is a data corruption crash. Not a simple disk, controller, memory or CPU failure, but corruption of data and loss of about half a day of it (from the nightly data backup). The latter two scares any IT department. Since it wasn't a mission critical server, it was allowed another chance. If it dies again the same way, no Conroe based server will be allowed here. Its too much of a chance to allow.

12 hours of data in a mission critical server is worth $12+ million in some shops. A corrupting server just isn't worth any increase in performance against that.

A crash that just needs a reboot, with a loss of a minute of data, at most, is bad, but nowhere near the above. For the crashed server's place, a reboot would cause no loss of data and a short work delay (2 minutes and 31 seconds after last software update). Why do you think Microsoft's Windows 2003 Advanced Server OS would be tolerated otherwise?

Pete
Volume:
Day Range:
Bid:
Ask:
Last Trade Time:
Total Trades:
  • 1D
  • 1M
  • 3M
  • 6M
  • 1Y
  • 5Y
Recent AMD News