If you are using MS Exchange Server 2003 Service Pack 1 in your organization, then you should be mindful about its size and keep archiving the data. Because if you fail to do so, then the EDB (Exchange Database) file may soon cross its 16 GB limit, thereby making it unmountable and, also, corrupt. The Messaging Database (MDB) automatically stops functioning, and becomes unable to mount, when the mailbox reaches this 16 GB limit. But you need not worry as there are several methods that you can perform for Exchange recovery. But when these do not work, then you should surely use a third-party Exchange recovery software.
Consider a scenario in which you are unable to mount MS Exchange Server SP 1. When you check the event log, the following event IDs are logged in it:
“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.”
Cause:
The most probable cause of this issue is that the size of the mailbox has increased 16 GB.
Resolution:
To resolve this issue, there are following methods that you can use to perform Exchange Server recovery and get the Exchange Server back on track:
You should try to upgrade to MS Exchange Server 2003 Service Pack 2 by downloading and installing the Service Pack 2. Restart the system after installing it.
If you are the system administrator in your organization, then you can employ the following steps:
i.Increase the size limit of the database by 1 GB although temporarily.
ii.Remove the content that you do not need or take a backup of such items.
iii.Then, defragment the database to compact it to such an extent that it is under the specified limits of the database size.
You can use the Recovery Storage Group feature to mount the database in the recovery storage group. After that, use the Exmerge.exe tool to retrieve the inaccessible user mailboxes from the database.
If you are still unable to mount the system, then you ought to take desperate measures to recover the Exchange Server. For such cases, a third-party Microsoft Exchange recovery software proves to be the most handy resolution. Such Exchange recovery tools are so efficient and reliable that the databases remain untouched during the Exchange Server recovery.
The most trusted and recommended tool in this respect is Stellar Phoenix Exchange Server Recovery that extracts user mailboxes in the form of separate PST files from damaged EDB files. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Exchange recovery software works on EDB files created for MS Exchange Server 5.5, 2000, 2003, and 2007.
For more visit at: http://www.ms-exchange-server-recovery.com/
Consider a scenario in which you are unable to mount MS Exchange Server SP 1. When you check the event log, the following event IDs are logged in it:
“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.”
Cause:
The most probable cause of this issue is that the size of the mailbox has increased 16 GB.
Resolution:
To resolve this issue, there are following methods that you can use to perform Exchange Server recovery and get the Exchange Server back on track:
You should try to upgrade to MS Exchange Server 2003 Service Pack 2 by downloading and installing the Service Pack 2. Restart the system after installing it.
If you are the system administrator in your organization, then you can employ the following steps:
i.Increase the size limit of the database by 1 GB although temporarily.
ii.Remove the content that you do not need or take a backup of such items.
iii.Then, defragment the database to compact it to such an extent that it is under the specified limits of the database size.
You can use the Recovery Storage Group feature to mount the database in the recovery storage group. After that, use the Exmerge.exe tool to retrieve the inaccessible user mailboxes from the database.
If you are still unable to mount the system, then you ought to take desperate measures to recover the Exchange Server. For such cases, a third-party Microsoft Exchange recovery software proves to be the most handy resolution. Such Exchange recovery tools are so efficient and reliable that the databases remain untouched during the Exchange Server recovery.
The most trusted and recommended tool in this respect is Stellar Phoenix Exchange Server Recovery that extracts user mailboxes in the form of separate PST files from damaged EDB files. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Exchange recovery software works on EDB files created for MS Exchange Server 5.5, 2000, 2003, and 2007.
For more visit at: http://www.ms-exchange-server-recovery.com/
0 comments:
Post a Comment