Working with lagged database copies

The concept of a lagged database copy is based on functionality introduced with Exchange 2007 that was included with Standby Continuous Replication (SCR). Using lagged database copies, we can configure a replay lag time in which logfiles that are replicated to database copies are not played 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.

How to do it...

1. To create a lagged database copy, specify a replay lag time value when adding a mailbox database copy:

   Add-MailboxDatabaseCopy -Identity DB03 `
   -MailboxServer mbx2 `
   -ReplayLagTime 3.00:00:00
   

   In this example, a new lagged database copy is added to the MBX2 mailbox server with a 3 day replay lag time.

2. You can also change a regular...