Transaction log replay: The foundation for DAG replication
Within a DAG, the transaction logs that are generated on the active server are pushed by the Replication Service to each of the servers that maintain passive mailbox database copies, where the logs are then validated and then replayed to update the passive copies. The DAG is the boundary of data replication for transaction logs. In other words, you cannot replicate logs to a server in a different DAG and have Exchange replay the logs into a database replica there. It then follows that before you can create a copy of a database, it must reside in a DAG and the target server must be part of the same DAG. The DAG is also the boundary for failover insofar as failovers only occur within the ...
Get Microsoft® Exchange Server 2010 Inside Out 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.
