Exchange 5.5 SP3 performance post eseutil /d /ispriv usage

[HuntsvilleALGuy]

Did a eseutil /d /ispriv the other day


readable via:

http://elvis.rowan.edu/~west

Server meached capacity, made mail come offline, users shaved mail data, reclaimed roughly 6gigs.


However before that, we did an initial offline defrag which free'd only like 800 megs. is exchange not happy after a capped out DB limit reach, and then data / white space is reclaimed to 15.2gigs roughly, and it's just not happy w/ that, even 800megs free when it just previously capped out?


We had constant problems, mail services shutting down, primarily Internet Mail Service. However, the following day was the day of reckoning, made users offload a lot, and did another eseutil /d /ispriv, and it seems to be stable?


Are there read/write/service issues when db is that high, even if shaving off some space from the 16gb limit. All is good now until we get win2k3 enterprise/exchange 2k3 enterprise.


p.s - i inherited this job that had no email/no quota policy so everything snowballed on us in 1 week. Initial db crash seemed to make alot of other things fail, but the 6gig reclaim seemed to help out alot.





respond if u like any input.

 

[HuntsvilleALGuy]

Better worded.

when a 5.5 DB is maxed out at 16gb, and a reclaim brings it to 15.2gb, is exchange still not happy with only 800megs free after just capping out at 16before eseutil brought it down 800megs? Seems so to me, lowlevel read/write issues?


the huge 6gig cap seemed to hold us over without hitches for now.

 

[KPMIS]

Remember that there might a message retention period on the database and if you compact before that period expires then you will not shrink the database. Bacause the MTP keeps deleted data and it is not officially Tombstoned from compaction standpoint.

If you do a Mailbox only backup then you can gauge the actual size of the data not the database

FYE when my exchange 5.5 Standard shut down it was just under the 15 gig limit