The concept of a lagged database copy is based on functionality introduced in Exchange 2007 that was included with standby continuous replication (SCR). Using lagged database copies, we can configure a replay lag time in which log files that are replicated to database copies are not committed into the database file, therefore lagging behind the active database, for a given period of time. The benefit of this is that it gives you the ability to recover point-in-time data in the event of a logical database corruption. In this recipe, you'll learn how to use the Exchange Management Shell to work with lagged database copies.
Working with lagged database copies
How to do it...
Let's see how to work with lagged database...