EDB Corruption If It Exceeds 16 GB Size Limit Article

	1888 Articles Home \| Computer Articles \| Data Recovery Articles \| Windows Articles	Data Recovery RSS
EDB Corruption If It Exceeds 16 GB Size Limit

Mailbox Store is a critical part of Microsoft Exchange Server. It contains all of the user mailbox and related data. A separate mailbox is created for every user in Exchange Server, which is accessible through the user profile in Outlook.

Author: Bob Luis

Article Tools:

But in some situations, the mailbox store doesn’t mount when it reaches 16 GB size limit. In such situations, you can not access data from the Exchange Server database and thus critical data loss situations occur. At this point, you are required to opt for Exchange Repair solutions to get your business critical and precious data back.

In a practical scenario, when you attempt to mount the Exchange Server mailbox store, the following Event ID might be logged into the Application Event Log of Exchange Server:

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.
Event Type: Warning
Event Source: ESE
Event Category: Space Management
Event ID: 445
Description: Information Store

(3160) The database D:\Program Files\Exchsrvr\MDBDATA\priv1.edb has reached its maximum size of 16383 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.

In such cases, to gain access of your critical data, you are required to repair and restore your corrupted Exchange Server database by carrying out Exchange Server Repair.

Cause

This behavior of Exchange Server might take place when the Exchange Server database exceeds its size limit, which is 16 GB in Exchange Server 2003 SP1 and earlier. Due to the exceeded size limit, EDB file (Exchange Server Database) gets damaged and thus it can not be accessed. Increased size of EDB file causes MDB (Messaging Database) to shut down automatically.

Resolution

To prevent this problem from being occurred in future, you are recommended to migrate to latest version of Microsoft Exchange Server. In order to resolve database corruption issue, go for Exchange Server Recovery solutions. Recovery is potential through third party applications, known as Exchange Server Repair software. These applications are powerful enough to methodically scan entire database and extract all of its inaccessible objects. These tools allow you to easily repair and restore damaged database as they come equipped with interactive graphical user interface. With read only demeanor, these programs are totally safe to use.

Stellar Phoenix Mailbox Exchange Recovery is the best every made and the most robust recovery tool for Microsoft Exchange Server 2003, 2000 and 5.5. It recovers all of the EDB file objects and is designed for Microsoft Windows 2003, XP and 2000.

About Author

Bob Luis has passion for writing Technical article. He is right now writing articles related to Product like Exchange Repair software and Exchange Recovery. He is also a professional writer.
For more information, visit: MS Exchange Repair.

Article Source: http://www.1888articles.com/author-bob-luis-22336.html