Exchange 2007 mailbox database damaged

I am in the process of recovering a MS Exchange 2007 server from a failed hard drive (one of 5 in a RAID 5 Array).  In the process of failing, the drive actually damaged the array.  I will have to delete the array, recreate it and restore from backup.  

My problem is that in repairing the volume, chkdsk was able to "repair" an unloadable mailbox database by replacing damaged clusters.  This has given me a database that will load and operate, but one that I can't backup.

I am thinking about using the essutil to repair the database, but it is 100Gb in size.  From my estimates, this would require 40+ hours to repair.

I have been told that I should not let the database get that large, and that I should split it into multiple stores.  

My question:
If I create a few new stores, and transfer the mailboxes across those stores until my single store is empty....
1. Can I delete the damaged store?
2. Will the process of moving mailboxes remove the errors and perform the defrag one mailbox at a time?

Thanks
LVL 1
tcampbell_ncAsked:
Who is Participating?
 
Manpreet SIngh KhatraConnect With a Mentor Solutions Architect, Project LeadCommented:
So moving the mailboxes will move the corruption also - moving mailbox between stores\database never will move corruption :)

Would it make sense to go ahead with the moves so the repair/defrag/integrity check could be broken in to smaller time periods? - If you do a move mailbox all this will be taken care of with not huge downtime and also Healthy new database :)

Let me know if you still have any doubts but Move mailbox is the best if you can do ..... remember circular logging if you dont have big enough Log drive or it will cause issue. Also need to have good backups everyday of just the new database.

Remember New database with new StorageGroups :)

- Rancy
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
You will have to follow a process of (Repair, Defrag and Isinteg) to make it a clean and healthy Database.

100 GB database to repair would take approx 24hrs (4-5 GB per hour for Repair and Defrag)
and an additional 10hrs for ISINTEG .... but also very much depends on your server and drive performance :)

I have been told that I should not let the database get that large, and that I should split it into multiple stores 0 Even Exchange 2007 has option of total 5 Database out of which you have default Mailbox and Public folder database so you can still create 3 more Database's and work.

As you say i was going to recommend the same to create 3 more Database move users split the Database to around 40GB as SIS would break ..... once done you can simply remove the corrupted database.

Few points however need to take care is "Move mailbox" process will create many log files on both source and target location so best is to enable "Circular logging"

1. Can I delete the damaged store? - Yes (but you might need to transfer System Mailbox)
2. Will the process of moving mailboxes remove the errors and perform the defrag one mailbox at a time? - The move mailbox would carry any corruption.

- Rancy
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
tcampbell_ncAuthor Commented:
Thanks Rancy.

So moving the mailboxes will move the corruption also.  Would it make sense to go ahead with the moves so the repair/defrag/integrity check could be broken in to smaller time periods?   (Less continuous down time)?  Or will moving the corruption possibly cause additional problems?

Tony
0
 
tcampbell_ncAuthor Commented:
OK Thanks.

I misunderstood your first post:  "The move mailbox would carry any corruption."  I thought you were saying that the move would "carry" the corruption to the new database.  

I have about 500Gb available on that volume, so log files should not be an issue, but I will look at the circular logging.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
My Apologies .... Human after all :)

- Rancy
0
 
tcampbell_ncAuthor Commented:
That's alright, just wanted to make sure I was understanding correctly.

I just remoted into the server and have an additional question....

Do I need to create new storage groups, or simply created new databases under the "First Storage Group" to accomplish my goal?

Thanks

Tony
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
I would always suggest a new DB and new Storage Group

- Rancy
0
 
tcampbell_ncAuthor Commented:
Working fine
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.