frevere
asked on
Exchange Offline Maintenance
Background Information: running Exchange 2003 SP2 on Windows Server 2003 SP2. All clients are Windows XP.
Issue: I have a storage group that the edb is up to 92GB in size on a 100GB LUN. If, and this has been done once before, move all the recipients from the storage group to another empty storage group, the edb grows to 80GB. After doing this, I left the recipients here. The storage group grew again to 92GB in size over time. Obviously this is white space, because most of the users have been cleaning their mailboxes out per a new policy. I took the storage group offline and ran defrag against this storage group hoping to compress the edb back to 80GB or so. After compressing the edb, and yes, before anyone asks, I used another drive for the temp edb which was copied over when the compress was complete, we only gained back a few GB, roughly 2.5GB. Any ideas why we are not reclaiming this lost space or did I fail to do something? Below is the command I used.
"c:\program files\exchsrvr\bin\eseutil " /d "<drive letter>:\<edb name>" /t "<drive letter:\temp edb>"
Issue: I have a storage group that the edb is up to 92GB in size on a 100GB LUN. If, and this has been done once before, move all the recipients from the storage group to another empty storage group, the edb grows to 80GB. After doing this, I left the recipients here. The storage group grew again to 92GB in size over time. Obviously this is white space, because most of the users have been cleaning their mailboxes out per a new policy. I took the storage group offline and ran defrag against this storage group hoping to compress the edb back to 80GB or so. After compressing the edb, and yes, before anyone asks, I used another drive for the temp edb which was copied over when the compress was complete, we only gained back a few GB, roughly 2.5GB. Any ideas why we are not reclaiming this lost space or did I fail to do something? Below is the command I used.
"c:\program files\exchsrvr\bin\eseutil
Check your application event logs for event ID 1221. That will tell you how much white space is in the database.
Hi,
I have answered this in detail earlier
Nitin Gupta
I have answered this in detail earlier
- https://www.experts-exchange.com/questions/23677038/MS-Exchange-2003-database-size.html
- https://www.experts-exchange.com/questions/23644176/Determing-Size-of-exchange-Database.html
Nitin Gupta
ASKER
Hi qupnit,
These are great references. Thank you, but it still doesn't explain the why, when I move all the users from storage group A to storage group B, the database shrinks to 80GB, and if I run a defrag when the database reaches 95GB, it only shrinks to 92GB instead of 80GB like a move. I know that moving users is the safer (preferred) method, rather than running eseutil, but we cannot continue to move users around. This takes a considerable amount of time.
These are great references. Thank you, but it still doesn't explain the why, when I move all the users from storage group A to storage group B, the database shrinks to 80GB, and if I run a defrag when the database reaches 95GB, it only shrinks to 92GB instead of 80GB like a move. I know that moving users is the safer (preferred) method, rather than running eseutil, but we cannot continue to move users around. This takes a considerable amount of time.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sembee's article really explains this in great detail. Thanks.