Exchange 2003 database corruption

Hi All,

I have had a huge database error recently. The database (.edb) was dismounted and it was suffering from "dirty shutdown"
I was able to fix it using "eseutil /p"  but i read that after a faliure like that it is highly recommended to create a totally clean database on a new harddisk and import the mail back to the mailboxes after.
My question is:
how can i do that? what would be the steps for it, and how is this effecting the outlook users?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
Rather than using ESEUtil /P i would using Exchange Recovery from Kernel Data Recovery.

This software works offline and also does a deep level repair on the Exchange database. From there you will be able to export mailboxes that are within the EBD file.

This software works for all versions of Exchange.

Kernel Data Recovery for Exchange Server

Satya PathakLead Technical ConsultantCommented:
Please have a look below KB It help you to understand how eseutil/P whitch work in Exchange enviroment.
agriboy1980Author Commented:
Alright guys, thx for the quick reply, but i still need to do a fresh database and migrate all the emails back into it.
How would you do that as the fastest and most stable way?

Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Hypercat (Deb)Commented:
Create a new storage group in Exchange System Manager, and then in that storage group create a new mailbox database.  Then you can move the mailboxes from the older mailbox database to the newer one.  In Exchange 2003, the mailboxes will be offline while they're being moved.

If what you're saying is that the recommendation is actually to export the email from the old database and import it into the new one, then you'd need to use the old Exchange 2003 Exmerge utility:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
agriboy1980Author Commented:

The article suggested that if you use "eseutil /p " it is recommended to create a new database and migrate everything into the new database, that is all. Isn'tit enough if i just move mailboxes with ESM from one storage group into the other? (i hate to use exMerge)
How is it gonna effect on users side the outlook, how are they gonna connect to the new storage group after the mailbox has been moved?

Hypercat (Deb)Commented:
I would think that moving the mailboxes would be enough. The mailbox should be discovered automatically by Outlook, I'm pretty sure, given that it's still on the same server just in a different storage group.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.