Thursday, April 28
Exchange 2000 16GB Message Store Size Limit
Exchange 2000 is causing multiple, repeated events in the log because the information store has gotten too large. They are not all identical to the one below, but the only variance is the Event ID or Imbedded Error Code:
Event Type: Warning
Event Source: ESE
Event Category: Space Management
Event ID: 445
Date: 4/27/2005
Time: 6:01:36 PM
User: N/A
Computer: billgatesisevil
Description:
Information Store (3788) The database D:\Program Files\Exchsrvr\mdbdata\priv1.edb has reached its maximum size of 16382 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.
For more information, click http://www.microsoft.com/contentredirect.asp.
We attempted to perform an temporary increase of the Database by 1GB as per Microsoft TechNet KB article 813051. This did not work and the errors continued.
Called Microsoft Support. The tech laughed and said that KB 813051 hardly ever works.
First we verified that there was a good tape backup of Exchagne from the previous evening.
Second we disabled Virus Scan.
Next we dismounted the Message Store in Exchange System Manager.
From the command line, we then checked the integrity of the Public and Private databases:
d:\\exeutil /mh "\path\priv1.edb"
d:\\exeutil /mh "\path\pub1.edb"
Note the file names are the defaults for Exchange 2000.
After the integrity was verified, we made a flat file backup of the databases by copying the .edb and .stm files to another drive.
Next, from the command line, we ran the Database Derfagment utility on both the Public and Private databases. According to Microsoft this can take 4-5 hours to compelete on 16GB of data. It took us about 2.5 hours.
d:\\exeutil /d "\path\priv1.edb"
d:\\exeutil /d "\path\pub1.edb"
While the defrag was running, we copied all the current log files into a "Backup Logs" directory.
Once the defragmentation was completed we remounted the store and tested. Everything was working fine. The compression appears to have gained us about 1GB of free space.
The next step is to begin removing unnecessary e-mails and archiving e-mails that are old but need to be retained.
Event Type: Warning
Event Source: ESE
Event Category: Space Management
Event ID: 445
Date: 4/27/2005
Time: 6:01:36 PM
User: N/A
Computer: billgatesisevil
Description:
Information Store (3788) The database D:\Program Files\Exchsrvr\mdbdata\priv1.edb has reached its maximum size of 16382 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.
For more information, click http://www.microsoft.com/contentredirect.asp.
We attempted to perform an temporary increase of the Database by 1GB as per Microsoft TechNet KB article 813051. This did not work and the errors continued.
Called Microsoft Support. The tech laughed and said that KB 813051 hardly ever works.
First we verified that there was a good tape backup of Exchagne from the previous evening.
Second we disabled Virus Scan.
Next we dismounted the Message Store in Exchange System Manager.
From the command line, we then checked the integrity of the Public and Private databases:
d:\
d:\
Note the file names are the defaults for Exchange 2000.
After the integrity was verified, we made a flat file backup of the databases by copying the .edb and .stm files to another drive.
Next, from the command line, we ran the Database Derfagment utility on both the Public and Private databases. According to Microsoft this can take 4-5 hours to compelete on 16GB of data. It took us about 2.5 hours.
d:\
d:\
While the defrag was running, we copied all the current log files into a "Backup Logs" directory.
Once the defragmentation was completed we remounted the store and tested. Everything was working fine. The compression appears to have gained us about 1GB of free space.
The next step is to begin removing unnecessary e-mails and archiving e-mails that are old but need to be retained.
Number of people who will never get their time back from reading this page:
