HELP EXCHANGE IS DOWN

Discussion in 'Windows Small Business Server' started by Mike, Jun 9, 2008.

  1. Mike

    Mike Guest

    Ok,

    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
     
    Mike, Jun 9, 2008
    #1
    1. Advertisements

  2. Mike

    Mike Guest

    Ok, 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 much.
     
    Mike, Jun 9, 2008
    #2
    1. Advertisements

  3. 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, here's how:

    How to recover the information store on Exchange 2000 Server or Exchange
    Server 2003 in a single site
    http://support.microsoft.com/kb/313184
     
    Dave Nickason [SBS MVP], Jun 9, 2008
    #3
  4. Mike

    Al Williams Guest

    Verify your RAID (I hope?) disk array - exchange (or any DB for that matter)
    needs good reliable disk hardware. Make sure it is solid before attempting
    to recover or it could happen again. A hard reset should not corrupt
    things.

    Have a look at the logs before the unable to login issue to see if you can
    see why you were unable to login. Verify your anti-virus is "exchange
    aware" and is setup not to scan the exchange DB files - this can corrupt the
    DB's. Perhaps when you moved it to another drive you did not add those
    exceptions. See http://support.microsoft.com/kb/823166
     
    Al Williams, Jun 9, 2008
    #4
  5. Mike

    Mike Guest

    I don't have an AV issue Al. I wish that was the culprit. I'll check the
    logs for hardware problems. Thanks for the response.
    -mike
     
    Mike, Jun 9, 2008
    #5
  6. Mike

    Mike Guest

    I'm not sure what to do Dave. What would you do if you were in my situation?
    I have a pst backup for everyone. do you know the cost for ms support? per
    instance? hourly?
    thanks....
    -mike
     
    Mike, Jun 9, 2008
    #6
  7. Mike

    Mike Guest

    I 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...
     
    Mike, Jun 9, 2008
    #7
  8. Mike

    SteveB Guest

    I agree with Dave. In this case calling CSS is probably best. The charge
    should be per incident although this looks like a server down scenario.
     
    SteveB, Jun 9, 2008
    #8
  9. 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.
     
    Dave Nickason [SBS MVP], Jun 9, 2008
    #9
  10. Mike

    Mike Guest

    Thanks Dave. There is nothing in the event log that shows a faulty raid. I'm
    on the phone with MS support right now. thanks for the advise.
     
    Mike, Jun 9, 2008
    #10
  11. Mike

    Mike Guest

    Hi Dave,

    Thanks for your advise. I watched an ms support rep go through the same
    instructions as in the link you sent and we are back up and 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
     
    Mike, Jun 10, 2008
    #11
  12. Glad to hear you sorted it out. I was thinking about this later, and I
    think calling PSS was the right move rather than restoring to a new database
    from the PSTs. If you'd had an unrepaired issue that caused the database
    corruption, you might have restored the PST files, only to find yourself
    right back in the same place.
     
    Dave Nickason [SBS MVP], Jun 10, 2008
    #12
  13. Mike

    kj [SBS MVP] Guest

    Lessons learned:

    - Have a verified good backup.(now is always a good time to start)
     
    kj [SBS MVP], Jun 10, 2008
    #13
  14. Mike

    Al Williams Guest

    Good to hear but I'm wondering if you know what the cause of the issue was.
    Exchange is usually pretty good about recovering from hard resets.
     
    Al Williams, Jun 10, 2008
    #14
  15. Mike

    bobmaria57 Guest

    Lepide Exchange Manager is an exceptional software that helps in extractingand restoring only selected items from the available backup without requiring brick-level backup. The software offers efficient Exchange disaster recovery using which a user can recover Exchange database.
    For more information - http://www.exchangedatabaserecovery.co.uk
     
    bobmaria57, Jul 13, 2012
    #15
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.