Restore Exchange 5.5 and Renaming MDBDATA

Posted on 2007-08-12
Last Modified: 2013-12-01
Hi everyone,

I have Exchange 5.5 on a Win2K server and during a bad shutdown the IS became corrupted.  I am using Backup Exec and have the selections "Microsoft Exchange Public Folders" and "Microsoft Exchange Mailboxes" checked for my backups.  I have good backups of those.  I did not backup the IS though (I know).

I've ran a repair using eseutil and recovered a lot of data but with a lot of errors.  I also have tried running a restore and now people have duplicate emails and some users show having 4 billion unread emails in their inbox.

I've tried creating a recovery server and restoring it to the new install of Exchange but Backup Exec is giving me errors.

On my production server can I rename the MDBDATA folder to OLD, create a new priv.edb and pub.edb and run my restore back to the prod server?  Or is it a bit more complicated than that?

Thanks for any help!
Question by:r_talkington
    LVL 27

    Accepted Solution

    After you ran the repair (eseutil /p), did you run ISINTEG -FIX -PRI -TEST ALLTESTS

    But to answer your question:
    Yes you can rename the MDBDATA folder on ALL drives to MDBDATA.OLD.
    Create a new MDBDATA folder wherever you renamed one.
    Start the Information Store service.
    This will then create empty databases.


    Author Comment

    No I don't think I did run ISINTEG.  I did run the integrity mode using eseutil, though.  

    Should I go ahead and run it to see if the problems get fixed or just make sure and do it after the restore?
    LVL 27

    Expert Comment

    "Should I go ahead and run it to see if the problems get fixed or just make sure and do it after the restore?"
    I'm not sure how to answer that.
    When ESEUTIL /P is run against a database, ESEUTIL examines each 4KB page in the database. If there are errors it will try to correct them. If they cannot be corrected then the page is discarded from the database.
    ISINTEG works on the links between the different tables in the database. So if a page has been deleted by ESEUTIL /P then this needs to be run.

    What I have seen alot of the time is that users will have messages showing in their mailbox but they cannot open some of these. After running ISINTEG -FIX the messages that cannot be opened will be removed because the links between the tables have been corrected.

    Hope this helps.


    Author Comment

    Yes it did help tremendously.  Got everything back up and running.  Thanks for your help!

    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Join & Write a Comment

    We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
    "Migrate" an SMTP relay receive connector to a new server using info from an old server.
    This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
    This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

    755 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    22 Experts available now in Live!

    Get 1:1 Help Now