Exchange 2010 DB corruption options

Hi all

We're seeing some minor database corruption on one of our Exchange 2010 DBs. The only issue we have (had) is a problem with calendar auto-accepts not working consistently which MS put down to DB issues. Moving the calendars to a new DB solved the issue so I going with it for now.

The DB is too big to fix during the small window we have - we are very nearly 24/7.

My plan is to move all the mailboxes in that DB to a new DB and then remove the old DB.

Does anyone have any comments on doing it this way?

I appreciate that I might lose a few a records here and there doing it this way but it's a risk that we're willing to take given the lack of options.

Any comments?

Olly
LVL 1
stonnewayAsked:
Who is Participating?
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.

Mohammed TahirMicrosoft Exchange and O365 AdministratorCommented:
To avoid downtime its a better way to move the mailboxes to new Database instead of repair.

Refer:
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/moving-mailboxes-exchange-2010-part1.html


Tahir
0
Mohd_ShaikhCommented:
Hi,

Before moving from old DB to new DB, you can try below step for current calendar auto-accepts issue.


The solution would be to change the mailbox type:
Set-Mailbox -Identity <Name> -Type <Regular,Room,Equipment,Shared>
-Confirm:$False

Once this is done then the Set-CalendarProcessing (Exchange 2010 only command)
can be use to set the calendar to Autoaccept

Thank You!
0
Raj-GTSystems EngineerCommented:
I have done what you are planning to do a few times and can confirm it works well to eradicate mailbox corruption.

Hope this helps.
0

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
JohnGarterCommented:
Hi Stonneway,

I would like to tell you that as you are saying that your Exchange Server 2010 database is big and you are moving the mailbox from one DB to another. I think that this procedure before repairing you corrupt database will make the data after migration to a new DB also corrupt. This thing will further create redundancy and will make the mailboxes at the destination DB corrupt. So, from my side it will be beneficial first of all to repair the DB through any 3rd party tools and then perform the move operation.

Thanks
0
stonnewayAuthor Commented:
Thanks all
0
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
Exchange

From novice to tech pro — start learning today.