I have been monitoring the free space on my exchange 2000 server very closely, and determined that I needed to do something now to prevent running out of space in a couple months. Buying additional storage is not an option - so I must rely on other means.
I came up with a list of large mailboxes and began having the users archive their mail to .pst files. This has been going smoothly. I have noticed the downward trend in free space begin to slowly level off.
However - it seems there should be more free space than there is. I have checked my retention settings and event logs - and the event ID 1221 for the mailbox store have reported more and more free space available in the database file - which is expected.
Is there a way to monitor how much free space is available in the priv1 database files? I am more SQL server minded, and was curious if the Exchange DB files behave like an mdf - and don't shrink (unless told to do so). If I can monitor the available free space in the priv1 DB files, without having to look at the ID 1221 event each day, then I would be happy.
I assume doing an offline defrag would reclaim the free space in the DB file.
Thanks
I came up with a list of large mailboxes and began having the users archive their mail to .pst files. This has been going smoothly. I have noticed the downward trend in free space begin to slowly level off.
However - it seems there should be more free space than there is. I have checked my retention settings and event logs - and the event ID 1221 for the mailbox store have reported more and more free space available in the database file - which is expected.
Is there a way to monitor how much free space is available in the priv1 database files? I am more SQL server minded, and was curious if the Exchange DB files behave like an mdf - and don't shrink (unless told to do so). If I can monitor the available free space in the priv1 DB files, without having to look at the ID 1221 event each day, then I would be happy.
I assume doing an offline defrag would reclaim the free space in the DB file.
Thanks