what you do when an Exchange Database taken offline automatically
Hi,
recently I have attended an interview, one of the quetion i think i couln't answer properly
The question (scenario) was
you are administring Exchange server, suddenly you realised that one Exchange Databse is taken offline automatically without your intervention.
why it might be happend ?
what do you do next ?
could you please help me to answer this question perfectly in future interviews and i need to know for real time situation as well
recently I have attended an interview, one of the quetion i think i couln't answer properly
The question (scenario) was
you are administring Exchange server, suddenly you realised that one Exchange Databse is taken offline automatically without your intervention.
why it might be happend ?
what do you do next ?
could you please help me to answer this question perfectly in future interviews and i need to know for real time situation as well
Last Comment
Michael Knight
the database most likely is in a dirty shutdown state. You need to run eseutil against it first to verify integrity
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Also, for Exchange 2003 SP2 you may have to increase the size limit in the registry. If it is set to below 75 GB you can increase the amount. If it is at the 75GB max size already then there is a registry key hack to enable 1 GB of Temp extra store size limit. That can give you enough time to empty out the database.
The first thing you need to do is check the event log on the Exchange server, Exchange is pretty good for logging errors telling you what the problem is. As @chakko stated, it is usually because you've exceeded the limit configured in the registry so the easy fix is just to increase the limit. It's also possible it was due to another issue so the event log is where you need to start.
In the event that you're not able to keep your mailbox database below the limit (e.g. you're running Exchange 2003 SP2 and your mailbox database is greater than 75gb), our solution was to have a VB Script scheduled to restart the Exchange Store service every morning at 5.30am as the mailbox or public folder stores are automatically dismounted at 5am every day if they are over the limits configured in the registry. If that's happening there'll be an event log entry. Restarting the service automatically every day kept us going while I planned and performed the migration to Exchange 2010.
You'd also want to make sure your Exchange backup finishes by 5am every day.
In the event that you're not able to keep your mailbox database below the limit (e.g. you're running Exchange 2003 SP2 and your mailbox database is greater than 75gb), our solution was to have a VB Script scheduled to restart the Exchange Store service every morning at 5.30am as the mailbox or public folder stores are automatically dismounted at 5am every day if they are over the limits configured in the registry. If that's happening there'll be an event log entry. Restarting the service automatically every day kept us going while I planned and performed the migration to Exchange 2010.
You'd also want to make sure your Exchange backup finishes by 5am every day.
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
