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...
- To create a lagged database copy, specify a replay lag time value when adding ...
Get Microsoft Exchange Server 2013 PowerShell Cookbook - Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
