Performing Exchange Recovery When Database Exceeds 16 Gb In Ms Exchange Server 2003

MS Exchange Server is the server side of the client-server application from Microsoft

. It extensively supports emailing, managing calendar entries, contacts, tasks, etc. Besides this, it also supports access through mobile and web-based browsers. All such Server information is stored in an EDB file, which sometimes get corrupted making it difficult to mount the Server database. Such corruption scenarios can occur due to various reasons such as database header corruption, hardware issues, abruptly exiting the Exchange Server, etc. In such cases, you should try out appropriate corrective measures. However, if you are not able to sort out the issue then you should use an Exchange recovery software to do the needful for you.

Consider a scenario wherein you are using MS Exchange Server 2003. One day, when you started the Exchange Server you were unable to mount the database. You check the Application event log and find the following event ID that suggests the possible cause of this situation:

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 1112

Description: The database "Mailbox Store (Server Name)" has reached the maximum allowed size. Attempting to unmount the database.

Cause:

The cause of this situation is that the Exchange Server database of Exchange Server 2003 has reached the permitted limit of 16 GB.

Resolution:

To resolve this situation, you should perform the following methods:

1. You should upgrade to Exchange Server 2003 Service Pack 2, as then you would have the option to increase the database size limit to 18 GB.

2. If you have the administrative rights to control the Exchange Server, then you can increase the size of the database by 1 GB for the time being. Then, remove the not-so-necessary content from the database. After this, you should defragment the database to bring it back to the stipulated size limit of the database size.

3. Mount the database using the Recovery Storage Group feature, and then try to extract the EDB from the mailboxes using the Microsoft Exchange Merge Wizard (Exmerge.exe) utility.

Using the aforementioned methods, you can bring the size of the EDB under control and use the Exchange Server as before. However, if you are not able to address the situation then you should use a third-party Microsoft Exchange recovery software to do the needful for you. Such read-only tools are able to perform Exchange Server recovery without overwriting the original contents.

Stellar Phoenix Mailbox Exchange Recovery is an Microsoft Exchange recovery software that repairs corrupted EDB database files. It is supported by Exchange Server 5.5, 2000, 2003, and 2007. This Exchange recovery tool is able to perform Exchange Server recovery by expressing the EDB databases in separated PST files. In addition, this Exchange recovery tool is capable of preserving the formatting of RTF and HTML email messages. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.

by: axel culver

POST COMMENT

INTERNATIONAL DEBT RECOVERY & DEBT ENFORCEMENT - SMCM - SWITZERLAND Good News For Data Loss Victims In India How To: Secure Delete Your Data Acr 2009: Benlysta Outshines Disappointing Rheumatoid Arthritis Data Data Recoverylocate, Recover And Restore Rise of Data Centers in India Debt Collection and Debt Recovery In Dubai Canada's Economic Recovery Slowing TeamLab Portal Backup and Restore: Managing Projects With No Data Loss Ever Primary Stroke Centers Aid Stroke Patient Recovery Studies Show Vitamin B3 Aids Stroke Recovery Data regarding Bangalore Budget Hotels ICICI, HDFC Bank breaks recovery norms: FM