Avoid database defragmentation (Event 629) on Exchange 2010

Sometime, we had an issue with database full and we generally get the event 629 to run an offline defrag on the databases. For doing defragmentation, we require a downtime we will get some white space.

In order to avoid the downtime for doing defragmentation, To overcome this action we can move the mailboxes to available databases and delete the problematic database and recreate the same. In this we will get more white space and there is no downtime require. Here is the below step to follow once you have moved the mailboxes to available database.

 Delete the database from DAG and recreate it

 1.       Suspend the healthy database

2.       Delete the Healthy Database and log files under the respective folder (don’t delete the parent folder).
3.       Remove the healthy database from EMC/Shell.
4.       Dismount the active database
5.       Delete the Active Database and log files under the respective folder (don’t delete the parent folder).
6.       Mount the active database, it will to create the fresh DB and log with same location. The initial DB size is 8 MB.

 

7.       Add mailbox database copy (healthy DB).

8.       Example: The server <Active exchange server> is active database node, so we need to point to the healthy DB node <Passive Exchange server>.

 

9.       We need to Finish the configuration and resume the healthy database.

 

 

10.       Once the DB activation completed, we need to enable index catalog as given below cmd.

set-MailboxDatabase -Identity “<database name>” -IndexEnabled $True