Exchange Server 2016 Management Series Courseware 53. Dag managed settings lagged database copy

1) Why to use a lagged database copy

To avoid database logical corruption and storage logic corruption.
Typically, a lagged database copy is generally not required because the organization has multiple non-lagged copies of the mailbox database, combined with the application of single recovery and retention policies. The benefits of lagged database replicas are only in very few environments, such as when an organization encounters logical corruption, especially storage logic corruption.
A large amount of data corruption or a specific addition, deletion, or modification that occurs outside of the user's expectation can lead to storage logic corruption. Storage logic corruption is typically caused by a third-party server or client application performing MAPI operations on the database, and can result in data corruption or large data loss. While individual restores can provide protection against most logical corruptions, in rare cases, recovering data through a lagged database copy is more meaningful than using a single recovery feature.

2) How to set up a lagged database copy

A lagged mailbox database copy is a mailbox database copy that has a replay delay time value configured to be greater than 0. Activating and recovering a lagged mailbox database copy is a straightforward process if you want the database to replay all log files and keep the database copy up to date.

Set-mailboxdatabasecopy https://technet.microsoft.com/zh-cn/library/dd298104 (v=exchg.160). aspx

For warning information, please refer to the following introduction to SafetyNet.
https://technet.microsoft.com/zh-cn/library/jj657495 (v=exchg.160). aspx
You can view or configure the SafetyNet in the location.

By default, the value of the secure network is as shown.

For more It information, you can also follow the public number below:

Zeng Hung Xin's online classroom, has hung Xin da Lecture hall-51CTO College

Http://edu.51cto.com/lecturer/639838.html

Exchange Server 2016 Management Series Courseware 53. Dag managed settings lagged database copy