?
Solved

Merge corrupt database to clean database

Posted on 2012-04-04
4
Medium Priority
?
404 Views
Last Modified: 2012-04-11
Hello Experts, recently we have had some corruption issues in our exchange database. After running a defrag and isinteg we still have not been able to shake the corruption. We have devised the plan bellow to merge to a clean database. Please review and hopefully you will concur that this will successfully clean the database or if you foresee any issues with this plan please reply.

1.      Copy the FSG database from our active (online) exchange server to a temporary (offline) exchange server
2.      Create a new database on that temporary exchange server and mount that new database to the FSG on the temporary server
3.      Mount the database copied from the active server to the recovery group on the temporary server
4.      Merge/Export all mail from the database mounted in the RG to the database mounted in the FSG on the temporary server
5.      Once step 4 is complete, dismount the database in the FSG on the temporary server and copy it off to the active server
6.      Dismount the database in the FSG on the active server and mount that database to the recovery group
7.      Stop all SMTP services on the active exchange server to avoid new mail from flowing
8.      Mount the copied database to the FSG on the active exchange server
9.      Merge all mail from the database in the RG to the database in the FSG on the active server
10.      Restart all SMTP services

This theoretically leaves us with a new un-corrupt database. The idea here to is reduce the exposure to the users and to reduce downtime.
If we don’t follow the procedure we will have users without their old mail for however many days it takes to merge the mail from the old database to a new one on the active server. All while mail is flowing into the new database we create.

The question left remaining for us:
Since the majority of the mail in the database mounted to the RG is already in the database mounted to the FSG, will that mail be duplicated when we merge those two databases?
Or will only the new mail that has been added to that database be merged?

If this is not clear enough feel free to post with any questions.

Thank you...
0
Comment
Question by:CKabs
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 15

Accepted Solution

by:
Rajkumar-MCITP earned 1000 total points
ID: 37809186
Instead of doing all the above work. If you have enough disk space for new database creation, and enough disk space on the current log file directory ( moving the mailbox will create new logs) then create a new mailbox database on the same live server and move the mailbox to new database. While moving you will have an option to skip the corrupted items.. set some value to remove the corrupted emails

Inform if there is no space and option for new database on the current server...
0
 
LVL 1

Author Comment

by:CKabs
ID: 37810739
Rajkumar, the current drive is full but we have another drive installed in which we can copy the database to then modify exchange config to point to that location.
There are 2 problems with using your method,
1. We do not have Exchange Enterprise
2. Even if we stood up a Enterprise server elsewhere or upgraded, we would benleft with the issue that while we are copying users loose access to their old mail

Even utilizing cached exchange mode would present the issue of, if thee users close outlook they will only have access to their old mail in offline mode.

Correct me if im wrong here.

P.S. Our database is already past the 75GB limit for Standard.
0
 
LVL 1

Author Closing Comment

by:CKabs
ID: 37832673
No response was given to my follow up question...
0
 
LVL 15

Expert Comment

by:Rajkumar-MCITP
ID: 37833162
Sorry Ckabs for not answering your follow up question. I missed this..

As you mentioned, if you move the mailbox to different server, users may lose connection. To avoid this you have to schedule to mailbox move on off business hours and also reconfiguring the outlook profile in needed.

what you planned? appears you have fixed it.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses
Course of the Month13 days, 1 hour left to enroll

777 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