Goody, a hate thread. I hate: Harleys. Buicks. Yellow Jackets. Jelly Fish at the beach (in aquaria is fine). Liver. Vomiting.
Sounds like you've been there. 200 GB of data stranded. Gonna be a long weekend, most of it watching status bars....
Yes, but it was only 2GB worth of data thankfully. The bad thing about it was it was classified data we needed right away post (military) operation. I hope you can remote in! Sunny
This is part what got me out of the computer industry: MS Win2000 boxes kept crashing in-flight. Too bad they were our 'video recorders' and every time it happened the test-flights were basically a waste of time and fuel and we came back empty handed. Cost about $50k or so per OS crash. Must have happened 25 times minimum. I suggested going to SGIs (again). Wouldda cost about $85k. Was shot down (again) because it was 'too expensive.' Sigh.
It's all well under control, but thanks for the offer. And to be fair to MS, at the root this was a hardware issue -- the drive array decided (incorrectly) that three drives from a RAID 5 array were bad at the same moment. The machine could have survived 2 (online spare), but not 3. So my log files went away, and the databases were confused.
I've only had one (****ty 3ware 9500) raid controller decide a drive was bad incorrectly. And it was only 1 thank god. What RAID manufactuar, so we can stay far the f--- away?!
Not being able to go back to work until I hear from my Doctor about my x-rays. I don't think it's that bad but I still can't lift anything heavy without a little pain. This is so boring & I need to make $$$$ ASAP!! AAAUUUGGGHHH!!!
Wait until the x-rays don't show any damage after you break your back, then you're told the pain is all in your head and you're going back to work the next day.
We have made the switch from GroupWise (Novell) to Microsoft Exchange and MS has Novell beaten hands down. How would you like to spend your time running GW checks against mailboxes with Novell? Since switching over to MS Exchange we have had not 1 problem in a muti-domain forest connected to other forests and all sharing a common address book and in a SAN cluster to boot. With all of this complexity we have not had any problems that has been caused by Exchange itself.
Same here, we'll have ~18,000 mailboxes on Exchange come November. That said, it was nice to be able to design and build this thing from the ground up w/ Windows/Exchange 2003 native. We're at basically 100% uptime since we went live. But yeah, corrupted t-logs do suck.
