Exchange 2010 Site Resilience, Multiple DAG IPs, and Cluster Resources
Exchange 2010 allows us to have Database Availability Group (DAG) members in several AD Sites. For every subnet a DAG member’s MAPI NIC is in, we must obtain a DAG IP. This DAG IP is a separate IP than is located on the MAPI NICs themselves. We take this DAG IP to the DAG using the Set-DatabaseAvailabilityGroup command.
Let’s take a look at an example of how the architecture may look.
Taking a look at the above Visio diagram, we have two sites, Primary Site and DR Site, with one node in each. The MAPI NIC in the Primary Site has an IP Address of 172.17.24.200. That means that we’ll need to have a DAG IP that lives in this same subnet. We choose a DAG IP of 172.17.24.120. The MAPI NIC in the DR Site has an IP Address of 172.16.24.200. That means that we’ll need to have a DAG IP that lives in this same subnet. We choose a DAG IP of 172.16.24.120.
In order to add these MAPI IP Addresses, we’ll need to run the following the command.
Note: IPs on Replication NIC’s subnet do not get added to the Database AvailabilityGroupIPAddresses. Only MAPI NIC Subnets get added.
--> The rest is on the blog :