Thanks for your advise. I watched an ms support rep go through the
running. We had to delete some log files to remount the DB in the
end. I'm witnessing a backup of the exchange store as we speak..lol
thanks again for you help. -mike
Post by Dave Nickason [SBS MVP]AFAIK MS Support in the US is $259 per incident, no matter how long
it takes to get it resolved. After hours support is a lot more -
maybe twice as much - and that's after 6 PM Pacific time last I
knew. I haven't had a major Exchange issue in a few years now, but
when I have, my primary consideration has been whatever will take
the least time to get us back in business, regardless of cost.
As long as you have PSTs that you're certain you can recover the
data from, you could just create new stores. I don't see much risk
in that, other than that you'll lose single instance storage. IMO
that's a negligible consideration anyway. If you're going to do
that, rename the existing directory with the existing databases, to
preserve them in case you run into an unexpected problem the other
way. Create a new directory for the new databases, and keep the
old until you're sure all is well. That way, there's no risk I can
see. The other thing is, if you're willing to create new stores anyway,
you could just try the procedure in the KB first to see if that
solves it for you. Some of the processes are a little time
consuming depending on database size and server specs, but the
process is not difficult if you follow the KB carefully.
The other thing is, don't disregard Al's points - if something like
a problem with your RAID controller caused this, you're going to
run into it again fairly rapidly.
Post by MikeI have a question Dave,
Since I have a pst backup for everyone, would it be easier to just
create a new mail box store? Will I have to do anything with the
connector if I do this? What are your thoughts?
thanks...
Post by Dave Nickason [SBS MVP]My first recommendation is that unless you're 100% sure you are
not at risk of losing data, I would call PSS (Microsoft support)
and let them walk you through this. Even people who are
comfortable with Exchange database recovery can benefit from
having a calm third party behind them while they're trying to
recover this much important data. If you're determined to go it alone,
How to recover the information store on Exchange 2000 Server or
Exchange Server 2003 in a single site
http://support.microsoft.com/kb/313184
Post by MikeOk, it gets worse. I now have no good backup to restore from.
Thankfully, I have a pst file for everyone. My only other option
is to repair the database. If anyone can point me to a good
procedure on doing this, I would be very appreciative. Please
note, I've already started to backup the corrupted database
since I read somewhere you should do that before running
eseutil.exe. Thank you all for taking the time to read this and for
anyone's
help. I'm in a pretty good jam, please help anyone. Thanks so
Post by MikeOk,
Running SBS 2003 SP2 with exchange SP2
I couldn't log into the server locally or remotely and did a
hard shut down. Now the exchange is down.
Getting the following event id's : 9518, 454, 515 & 465
From what it looks like the logging/recovery failed and I guess
its time to restore from backup. Yes, I have a backup. Can
someone point me to a good solid procedure to restore the
exchange correctly? First thing I'm doing is creating a pst and
savig it locally to
everlyones computer.
Just so its known, I had to move the exchange database friday
night due to lack of space on the OS partition where it was
installed (I didn't setup this server, someone before me did).
But everything was fine, everyone was getting email up until I
did a hard reset this morning.
thanks in advance for anyones help