Hi We are running Exchange 2010 SP1 in a pre-prod environment. We have 20 DB's in the DAG, each with 5 copies - one of which is a lag copy of that DB. I am looking to perform a restore using the lagged copy. http://technet.microsoft.com/en-us/library/dd979786.aspx I had some questions: 1. Is there a Powershell command I can run to find out what the lagged copy for a particular DB is and where it is located? 2. In the Technet article we are taking a VSS copy of the DB. Do we then run the commands on the VSS copy version of the actual lagged copy? 3. What is the difference between taking a VSS copy of the lag DB and simply copy and pasting to another location?

To identify the lagged copy and the lag time period configured, Use the below script. Get-MailboxDatabase |Select-Object name, ReplayLagTimes-Cheers Shaba

Hi, Database logical corruption is taken care of by the the lost flush detection mechanism, which is a new ESE database improvement in Exchange 2010. We can use lagged database copy to recover. I understand that if we have serveral database copy, then we can take backup of database copy only. Eliminating Traditional Backups using native Exchange 2010 Functionality (Part 3) http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/eliminating-traditional-backups-using-native-exchange-2010-functionality-part3.htmlXiu Zhang TechNet Community Support

Hi, Database logical corruption is taken care of by the the lost flush detection mechanism, which is a new ESE database improvement in Exchange 2010. We can use lagged database copy to recover. I understand that if we have serveral database copy, then we can take backup of database copy only. Eliminating Traditional Backups using native Exchange 2010 Functionality (Part 3) http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/eliminating-traditional-backups-using-native-exchange-2010-functionality-part3.htmlXiu Zhang TechNet Community Support