Oh how i love exchange 2003!

Currently sat here watching eseutil tick its way thru a couple of mailstores after iscsi spazzed out and dropped the disks which corrupted the stores.

have been working on this since 7 yesterday eve

Mmm nice! I feel your pain having worked a 36-hour day a few weeks back after the SAN failed and removed the Exchange server's disks.

its a race against time now lol.. users start logging on in under 2 hours and we are still 2 mailstores down :eek:

Well my snooze alarm has gone of twice now. Might get out of bed.

Well my snooze alarm has gone of twice now. Might get out of bed.

:P (im still here)

I feel your pain. I've had a similat experience with some dodgy SCSI firmware corrupting a store.

Oh how i love exchange 2003!

Currently sat here watching eseutil tick its way thru a couple of mailstores after iscsi spazzed out and dropped the disks which corrupted the stores.

have been working on this since 7 yesterday eve

Don't use iSCSI for a large system such as this? :P

HTH

Been a while since I've had to do anything with MS products. Thank fully my backend local user base support days are behind... thank god !!!

I remember having to pull close to 30 hours one time when a collegue decided to add more storage to an SQL cluster... and totally fooked it.

Hope you get it sorted Col.

Don't use iSCSI for a large system such as this? :P

HTH

Yes we know that now.... being that our entire Netapp/VMware plan was based on using Iscsi LUNS mounted in-guest with i-scsi initiators.. due to alot of our db workloads isnt fast enough (our olap enviroments are needing high sequential throughput that we cant get through GBe and VMware doesnt support 10gigE properly yet.

so we are moving to FC going forward.

Oh.. finally got home to bed at 10 thismorning. all this hassle because of a fecking exchange logfile!. (we speculated that the fault happened as exchange was re-naming the most current log so for one storage group it was insistant there were logs missing so wouldnt verify the databases.. had to use a eseutil /p in the end as our tape-DR-company fecked up.. we ordered the backup tapes back as an emergency, and their emergency phone number was down so couldnt confirm it to get them sent out

You would have hoped that MS would have heard of transactions wouldn't you

All the places I worked at that had mail issues with 2003, was down to users exceeding the max user mailbox size 2003 could handle and it then creates a stupidly large log file which causes the crash.

Any, or multiple, mailboxes over 750mb?