Exchange lagged database copy
Posted on 2014-07-28
I have done some readings on Microsoft website about Lagged database copy, but still not clear.
I want to know what s the purpose of it. I know the lagging is applied only on the passive database copy not on the active and the lagging delays the replay of the logs for a specified time.
However I believe if something happen to active copy, the passive will become the active and the logs will be replayed...anyway
in Some articles, they say that the lagging comes in handy when the active database is corrupted, and when the corrupted data is copied to the passive copy, it will not replayed until it reach the specified time in Lagging...if we realize that there is corruption within that time frame, then we can just initiate the replay of the logs generated before the corruption happened, and delete the logs generated after the corruption happened. .....Too complicated...
I could be wrong...I need Exchange expert to shade some lights on this topic.