MSSQL.hsphere.cc down

[Craig_Smith]

MSSQL.hsphere.cc will be down for repair.

We will post here when we have more information on when it will be back up.

We still have it in the office. Making the best of the outage by giving it a serious upgrade since we're working on it anyway.

[Brangwyn]

Super thanks, any rough eta ?

[aliensx]

???

We've upgraded the box to a dual xeon 2.4Ghz like the other latest machines. We're also upgrading the OS to 2003 so that it conforms with the rest of the MSSQL boxes.

[Brangwyn]

Thats super Matt, but how about that ETA ? we are already in the realm of what 5+ hours outage ? which means there will be people requesting credits for this one.

[Vixen]

I know they are still working on the server as Brad has gone back to the office (twice tonight) to assist in repairing the server. I spoke to him a few minutes ago and he said it should be done shortly.

[Brangwyn]

Thanks Vixen.

Brad and Matt are pretty much finished and the machine will be back in place within the next 90 minutes.

The new mssql.hsphere.cc was brought up 20-30 minutes ago. May it live as long as its predecessor and retire with less downtime.

[Brangwyn]

Thanks Alex, looks like around 8 hours total downtime then ?, first email I got that it was down was around 6pm EST

[admin]

Something went worng in windows 2000 and would not longer fully boot. It would load to the screen where it says windows 2000 with the blue line then just stop. So we had to find how to fix that. Once we got that fixed we went ahead and upgraded to 2003 and put it in all new hardware as well.

That server had been online for 3 years and running dual PIII 1000 with 2GB of 133MHz ram, so the upgrade should help a lot for users on that box as well and should be a bit more stable as well now.

[aliensx]

I understand the problem but believe me our customers didn't understand very well why we haven't been notified earlier.

[mresell]

Wouldn't it be easier to swap out a drive and use a standby server than to take a server offline so long w/ no replacement? 8hrs was long enough if something had happened that delayed it further... seems like it could have been much worse.

[admin]

We did put it a new case just to rule out hardware. But moving mssql is not all that easy if you have to do it with a system that does not boot. It would of taken a little bit longer if that had happended.