Demystifying Exchange 2010 database availability group (DAG)

re: Demystifying Exchange 2010 database availability group (DAG)

EricM — Mon, 16 May 2011 10:48:31 GMT

Is it possible to prevent the replication traffic failing over to the MAPI network? We push Replication over an intersite WAN implemented on different technology (point-point fiber) to the user (MAPI) traffic (MPLS), and couldn't tolerate the replication bandwidth on the MPLS.

We'd rather recover the link and let the replication catch up. Can this be done?

re: Demystifying Exchange 2010 database availability group (DAG)

Dan — Fri, 04 Feb 2011 14:58:34 GMT

Looks like Exchange 2007 used SMB for the replication (log shipping), but all I see for 2010 is that is now using TCP (www.howexchangeworks.com/.../log-shipping-in-exchange-2010-dag.html). Surely there is some sort of file transfer protocol involved?

re: Demystifying Exchange 2010 database availability group (DAG)

Dan — Thu, 03 Feb 2011 14:56:28 GMT

So what kind of traffic is the DAG actually sending? Based on what is here, I see MAPI traffic is a part of it, but what is the "Replication" traffic - is that SMTP, or something else?