<div>
<div class="content wysiwyg-content">
<br />
<br />
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.<br />
<br />
<a href="http://technet.microsoft.com/en-us/library/dd979786.aspx" rel="ugc">http://technet.microsoft.com/en-us/library/dd979786.aspx</a>&nbsp;<br />
I had some questions:<br />
<br />
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?<br />
<br />
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?<br />
<br />
3. What is the difference between taking a VSS copy of the lag DB and simply copy and pasting to another location?<br />
<br />

</div>
</div>




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?



Exchange 2010 Lagged copy of DB

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.