July 2017
Intermediate to advanced
648 pages
31h 9m
English
Lagged database copies can invoke automatic log replay to play down the log files in the following scenarios:
Play down based on health copy status requires ReplayLagManager to be enabled. From Exchange 2016 CU1 onwards, ReplayLagManager is enabled by default. This can be changed by running the following cmdlet:
Set-DatabaseAvailabilityGroup DAG -ReplayLagManagerEnabled $False
Also starting in Exchange 2016 CU1, playing down logs is subject to the health of the disk, more precisely, the disk's I/O latency. If a disk's read ...
Read now
Unlock full access