Exchange Recovery

Discussion in 'Windows Small Business Server' started by AndrewS, Aug 5, 2006.

  1. AndrewS

    AndrewS Guest

    Hows this for a problem...
    I have a friend that is running SBS2k3, it died and no back ups. I have
    managed to get the *.edb, *.stm and log files from the old drives but thats
    it. How do I mount them on to the new server?
    AndrewS, Aug 5, 2006
    1. Advertisements

  2. Kevin Weilbacher [SBS-MVP], Aug 5, 2006
    1. Advertisements

  3. In
    If you don't have a good backup (tsk tsk) and can't mount the stores in your
    rebuilt environment, you might see - it's an
    invaluable tool for an Exchange admin.
    Lanwench [MVP - Exchange], Aug 5, 2006
  4. You don't.

    If the original AD is not available, I don't think there's any way to
    directly use the stores.

    You probably need something like Recovery Manager for Exchange from (formerly Aelita).
    Steve Foster [SBS MVP], Aug 5, 2006
  5. AndrewS

    Anna Clark Guest

    Hi Andrew:

    Any chance that the client worksations were keeping .ost files, and that
    they have not left the old domain yet?

    In that case you might be able to open Outlook on the .ost files, export to
    ..pst and import back to the new domain.

    Anna Clark
    Anna Clark, Aug 5, 2006
  6. Hi Andrew,

    You are only as good as your last fully good and validated backup. What you
    will need to do first is back up what you do have. Go to the folder that
    contains your database files - delete those. Restore the database that you
    have from the old drives. If your log files are toast then you will have to
    copy the old log files from the previous old drive to the current log log
    file folder. Ideally, you want to use as much of the old log files as
    possible. If your current log files are ok make sure that you also have a
    copy of the checkpoint file available. This will tell Exchange what's the
    last committed log file it can use for restoration purposes. If you restore
    from your old drive you can sometimes merge the log files together - but if
    you do this you will need to delete the old checkpoint file.

    I would look at the whitepaper on the site on Exchange
    Disaster Recovery. It will provide you with the necessary background as well
    as information about how to use ESEUTIL to verify the integrity of the
    various Exchange files.

    Does this help?
    Deepak Shenoy, Aug 5, 2006
  7. AndrewS

    Anna Clark Guest

    Hi Deepak:

    The user seems to be saying that they have rebuilt the SBS from scratch, in
    which case the SID will be different and the store will probably not mount.
    In some cases, if the did everything exactly the same they may get it to
    mount, but unless one has tested this on a backup server in the closet it is
    fraught with errors.

    I would be more likely to get the production server up, but before joining
    the workstations to the new domain, verify if there are no ost's. Then
    after getting the users back in operation, try restoring the exchange data
    bases files from the old drives to a test unit. Once running on the test
    SBS, they can use xmerge or export to recover the individual mailboxes.

    Anna Clark, Aug 5, 2006
  8. AndrewS

    AndrewS Guest

    This is so true....I had been looking at the box for the first 3-4 weeks just
    to make sure that everything was working OK, but then left him to it. Turns
    out that for the past 6-8 weeks he has had an anoying beep coming from the
    server. Looks like it was telling him that he had a failed drive in hte raid
    5 set.I may have to take his server off him!
    It just gets worse. The files that I have from the old drives are not what
    you would cll "In Good Condition" ESEUTIL /p , ISINTEG just don want to know
    about it. Quest can see the files and folders but only fragments of mail.
    Will have a look for the .OST on the local cilents, see if I can do anything
    from them.

    Thanks for your help but it may be a lost cause

    AndrewS, Aug 6, 2006
  9. AndrewS

    bibomaria Guest

    Exchange Server errors, accidental deletion of important files may lead to Exchange Database file corruption. In order to recover EDB files, one needsto use Lepide Exchange manager that is user friendly, professional and easy to use software. This software makes EDB to PST conversion accurate and quick. In case of corrupt EDB files, users need to launch LEM software, point to the corrupt EDB file, extract user mailbox, convert EDB to PST and save to the desired location.
    For more information -
    bibomaria, Jul 9, 2012
    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.