Now that we have our static IP chosen, let’s run the following command:
Set-DatabaseAvailabilityGroup -Identity ShudnowDAG -DatabaseAvailabilityGroupIPAddresses 10.204.4.178（我的DAG虚拟IP）
We now see that our DAG has the following static IP configured.
Well, let’s go ahead and add our first node to the DAG. Go into the EMC > Organization Configuration > Mailbox > Database Availability Group > Right-Click our DAG > Manage Database availability Group Membership.
But… what exactly was done during this behind the scenes when this first node was added to the DAG? The following occurs (from Technet documentation):
?The Windows Failover Clustering component is installed, if it is not already installed.
?A failover cluster is created using the name of the DAG.
?A cluster network object (CNO) is created in default computers container.
?The name and IP address of the DAG is registered as a Host (A) record in DNS.
?The server is added to DAG object in Active Directory.
?The cluster database is updated with information on the databases that are mounted on the added server.
First of all,we can see the DAG has been registered in DNS.
Second of all, we can see the DAG’s Cluster Network Object (CNO) has been created in AD.
Third of all, we can see the cluster has been formed. As you can see, there’s no CMS/Virtual Server in the Services and applications. This is because Exchange 2010 is not a cluster aware application. Exchange 2010 only utilizes Windows Failover Clustering Services for heartbeat information and cluster networks.
Finally, we can see that the cluster is currently set to Node Majority. When we add our second node, the cluster will be switched to Node Majority with File Share Witness since we’ll have an even number of Exchange Nodes and will need a 3rd node/share to act as our witness. Because of this, we won’t see any FSW data inside of FSW share until our second node is added to the DAG.
本文转自xury 51CTO博客，原文链接：http://blog.51cto.com/xury007/270056，如需转载请自行联系原作者
