Whoopity-doo! Shook
From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, June 01, 2010 11:57 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Replied offline with lab workbook. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 11:51 AM To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed Thanks! Sounds promising. I'm assigning the IP address using "Set-DatabaseAvailabilityGroup -DatabaseAvailabilityGroupIPv4Address <blah>" cmdlet, AFTER the two servers have been added as members. I should probably add the IP address immediately after creating the DAG, I presume? I'll do this now, you will hear me shout from the rooftops or crying into my coffee within 20 minutes. Cheers Richard From: bounce-8946464-8066...@lyris.sunbelt-software.com [mailto:bounce-8946464-8066...@lyris.sunbelt-software.com] On Behalf Of Michael B. Smith Sent: 01 June 2010 16:14 To: MS-Exchange Admin Issues Subject: RE: DAG setup and configuration help needed If you are running the DAG wizard/cmdlets on one of your exchange mailbox servers that will be in the DAG - then add the REMOTE ONE FIRST (there is a bug about the permissions associated with the CNO if you don't do it that way - alternately, run the wizard elsewhere). You don't say how/when you are allocating IP addresses to the DAG, which is an important consideration in this scenario. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Tuesday, June 01, 2010 6:29 AM To: MS-Exchange Admin Issues Subject: DAG setup and configuration help needed Good morning everyone For those who have had experience so far in setting up a DAG - whether it was for testing or production - I wonder if you could help me? I've been following the excellent instructions over at www.msexchange.org<http://www.msexchange.org>, beginning with part 1: http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part1.html My environment for this purpose is: * Physical Windows Server 2008 Enterprise for the witness. * Virtual Windows Server 2008 R2 Standard domain controller. * 2 x virtual Windows Server 2008 R2 Enterprise Exchange 2010 RU2 servers. * I am using ESXi as my virtualisation platform. * My DC is a brand new build, dcpromod to Windows Server 2008 R2 forest functional level. For the purpose of my testing, it's running DNS. * The two Exchange servers have two virtual NICs installed and configured as replication and MAPI networks. My problem is related to DAGs, and perhaps clustering. The DAG itself is created normally. It is when I come to add my two Exchange servers to the DAG that the problem(s) begin: 1. The first server is added to the DAG with no errors. 2. Upon configuration of the second server, an IP address conflict is reported. The IP conflicting is that of the first server. To me this makes no sense! Both interfaces on both servers have hardcoded IP information. 3. The DAG will then not come online, even after assigning an IP address to it. 4. This error is reported in the cluster event log on both servers: Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'domain'. The error code was 'Unable to find computer account on DC where it was created'. The cluster identity 'DAG1$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain. If you've made it this far, could you share your experience with the process and offer any tips as to why this isn't going as smoothly as I told myself it would be?! Thanks Richard
