Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
Yesterday I disabled about 40 Gig worth of mailboxes that have been moved off my server. Knowing that my Deletion settings were 30/30, I set them to 0 and unchecked the "Do not delete.." box. I set the schedule to run for 4 hrs completeing at 7am this morning.
When I came in, I checked the DB size and I've gained nothing. What does a guy have to do to force Exchange to give me back some space?
Also what exactly does the Maintenance run? Does it defrag during this time? Are there manual Powershell commands I can run during working hours?
I'm actually trying to avoid that due to the size - 460Gig. I'm moving mailboxes to 5 new storage groups so they'll be more managable. I read that moving to new SG's with new DB's actually eliminates the step for a defrag. True?
if you check your event log, you will see that the edb now has "whitespace" - google exchange whitespace for more info.
If you insist on reducing the physical space consumed by the edb, you are going to have to dismount the database/store - you are running multiple databases yes? - and eseutil /mh, and /g, and /d.
google exchange eseutil defrag.
If I was you, I would not do it - I would make sure that my exchange, a business critical application, is getting the drive space it needs.
Thanks guys. Yes, we're in the middle of this discussion. I do need to run offline defrag to get my space back. Now it's just finding the time to do it. Anyone have an idea how long a defrag to get whitespace back will take on a 460 Gig db? I KNOW I'm going to be asked this and when I say "Unknown" I'll be sent back to the drawing board. Around here they want hard numbers not guesses.
I've read that backing up an Exchange db at the same time as running Maint, causes the online defrag to be suspended until after the backups have completed.
Does this rule apply when you're runing a doc level backup as well?
487 mailboxes
< Message edited by catzodellamarina -- 4.Feb.2009 4:41:16 PM >
If I was you, I would create new storagegroups/databases and move the users. Be a lot faster and down time would be limited to those users who are actively moving.
Be a bit of a hit on storage.
eseutil time varies based on hardware speed - primarily (assuming good server host) on your drive/array performance.
Yes, I'm moving small users to new SG's. I will not have enough space remaining to finish the move. We've basically painted ourselves into a corner when we made 1 SG, 1 DB, and a mob rules for 400 people. Looks like 3 days of downtime is the sacrifice needed to get this corrected.
Did you find out how much of white space does this DB has ? If its gona take downtime of 3 days i would just move all the users from this DB, Just delete this DB. Create a new DB and move back the user.
It sounds unanimous that I must run an offline defrag. I met with mgmt. on this and we're prepared to run next weekend. We'd all like to avoid ever having to run an Offline again. Is this realistic? Explain to me - does everyone have to perform an offline from time to time to get back their whitespace? OR.. will a small DB, with properly scheduled Online Maint finishing every night, keep a tidy DB and you may never need to run an OFFLINE?
If we had an emergency cleanup of mailboxes, and set "keep deleted to 0 days" would this free space with ONLINE maint?
Does the Offline run until it stops or can it be canceled? If cancelled will it pickup where it left off or is all your defrag now a mess or changes are disgarded?
When you run OFFLINE maint, do you need equal amount of space available to complete? If so, can this space be on a different volume?
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Hiya chap,
An offline defrag should not be part of a regular maintenance schedule for Exchange - it is difficult to say that you will "never" have to run it again - that will of course depend on what you do from now on. You can set don't keep deleted mailboxes - but that will not have an effect on the overall size of the store as the mailbox once existed - the space that it occupies will only be reclaimed within the internals of the database (the on-line defrag that has been mentioned) - from the data that you have supplied it looks like that your data store will shrink by 133GB - if might be an idea after the defrag to split the mailboxes up in to a couple of Databases - really a good target size for an Exchange DB is < 200GB.
You can cancel the offline defrag by pressing CTRL-C - however if you restart, it will go from the beginning again (it reads the DB page by page) - typically you need 110% of the size of the DB free on the Defrag drive and you can redirect the defrag to another volume - this should be a local disk.
Yes, Microsoft recommends 100 GB DB without CR and 200 GB with CR as the maximum database sizes for Exchange 2007.
And as Grogan said you cannot rule out the possibility of defrag in future. But still you can avoid it for a long time by the monitoring the online maintenance and allow the full pass to complete.
Smaller the database less time it takes for the online maintenance to complete the full pass.
I want to thank all for assiting me. It's been a long road and we're finally getting arms around our Exchange situation. I think I've found a work around for the lengthy Offline defrag, which has everyone worried in regards to downtime. How does this sound: I'm going to attach my CCR servers to the SAN with a f/c cards. Carve out space on the SAN for all of my mailboxes x 2 (room for future ESEUTIL) Move ALL mailboxes to SAN, seperated into 5 storage groups - setup with quotas. Delete the old db.
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Sounds like a good move - however be mindful of the following:
1. If the SAN is shared with other data (e.g. SQL, File Share) make sure that you have enough IO capacity to handle Exchange.
2. Make sure that you take into account the logs and DB best practice rec's when placing the new SG's (RAID 10 for DB - or RAID 5 if you are working to a budget with RAID 1 for the logs - both on separate LUNS).
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> Management >> Scheduled Maintenance 
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
Scheduled Maintenance - 
New Databases - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
