Hi,
I am running Exchange 2000 and have recently been having lots of errors due to running out of space (the physical disk size is fine but am hitting Exchange limits).
I have purchased a third party archiving tool but have not had a chance to properly implement it and Exchange has hit the limit:-
---------------------------------------------------------------------
Source: ESE
Event ID: 445
Information Store (2624) The database D:\Exchsrvr\mdbdata\priv1.edb has reached its maximum size of 16384 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.
For more information, click ---------------------------------------------------------------------
This morning it dismounted and could not get it to mount again.
I decided to try an offline defrag and ran the ESEUTIL /D command against the Private Information Store.
This seemed to work OK and as I know that the space problems are within this database (plus this is a production server which has been down all morning) I then did a backup and didn't run the utility against the Public information store.
This seemed to free up space and I was able to get Exchange running, however now I have a system which seems to be slow and event log entries :-
---------------------------------------------------------------------
Source: ESE
Event ID: 602
Information Store (884) Database 'D:\Exchsrvr\mdbdata\priv1.edb': Background clean-up skipped pages. The database may benefit from widening the online maintenance window during off-peak hours. If this message persists, offline defragmentation may be run to remove all skipped pages from the database.
For more information, click
---------------------------------------------------------------------
I am a bit confused as it is telling me that the solution is to run a defragmentation whereas this is actually what has caused the message in the first place.
Do I need to run another pass of the defragmentation ?? Should I have also ran something else at the same time as I did the original defrag ??
What will happen if I just leave this till tonight's online maintenance ?? Will it resolve the problem or am I better pulling it again and doing something right now......
Any advice would be gratefully received.....
Jon Scriven
I am running Exchange 2000 and have recently been having lots of errors due to running out of space (the physical disk size is fine but am hitting Exchange limits).
I have purchased a third party archiving tool but have not had a chance to properly implement it and Exchange has hit the limit:-
---------------------------------------------------------------------
Source: ESE
Event ID: 445
Information Store (2624) The database D:\Exchsrvr\mdbdata\priv1.edb has reached its maximum size of 16384 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.
For more information, click ---------------------------------------------------------------------
This morning it dismounted and could not get it to mount again.
I decided to try an offline defrag and ran the ESEUTIL /D command against the Private Information Store.
This seemed to work OK and as I know that the space problems are within this database (plus this is a production server which has been down all morning) I then did a backup and didn't run the utility against the Public information store.
This seemed to free up space and I was able to get Exchange running, however now I have a system which seems to be slow and event log entries :-
---------------------------------------------------------------------
Source: ESE
Event ID: 602
Information Store (884) Database 'D:\Exchsrvr\mdbdata\priv1.edb': Background clean-up skipped pages. The database may benefit from widening the online maintenance window during off-peak hours. If this message persists, offline defragmentation may be run to remove all skipped pages from the database.
For more information, click
---------------------------------------------------------------------
I am a bit confused as it is telling me that the solution is to run a defragmentation whereas this is actually what has caused the message in the first place.
Do I need to run another pass of the defragmentation ?? Should I have also ran something else at the same time as I did the original defrag ??
What will happen if I just leave this till tonight's online maintenance ?? Will it resolve the problem or am I better pulling it again and doing something right now......
Any advice would be gratefully received.....
Jon Scriven