Exchange 2010 database Availability Groups and Offline Defrag
Posted on 2009-12-18
Having recently run an offline defrag of our store and finding it took 7 hours for a 50GB database on our Exchange 2003 server I was wondering how this has changed in Exchange 2010.
Given that Single Instance Storage is growing and the use of Archiving in the same database will make databases huge running an offline defrag (or indeed any ESEUTIL repairs) are going to have a significant impact on uptime.
My first question is if I need to run an offline defrag on a database that is part of a database availability group will it take all databases offline and replicate the changes once the defrag has completed or will I be able to run the defrag on copy at a time?
My second question is are offline defrags still necessary or is there now some magic tool that does the equivalent without taking the database offline to recover precious disk space?
My final question is if a corruption occurs in a database will it be replicated to the other databases? I suspect not if all is being replicated is the log files but it would be nice to get a definitive answer so I know what I am potentially letting myself in for with Exchange 2010.
Thanks in advance for any help given.