Datacenter Switchover - Evicting members of a DAG

Background:
We have two AD sites (A and B), each with their own datacenter with internet access.
We have three multi-rolled Exchange servers (2x in site A, 1x in site B). We'll call them Aex1,Aex2,Bex1
We have a DAG configured spanning sites A and B consisting Aex1,Aex2,Bex1.
We have three copies of every database. Bex1 hosts only passive copies. Aex1 and Aex2 host both active and passive copies.
Aex1 and Aex2 need to be powered off for 2-3 days while they are physically relocated.
Prior to shutting down Aex1/Aex2, we plan to activate all databases on Bex1 (in Secondary site) and update DNS as necessary to point clients to the CAS in the secondary site.
I'm familiar with the online Exchange Server 2010 Datacenter Switchover guided walkthrough and plan to use it.
http://support.microsoft.com/common/survey.aspx?scid=sw;en;3510&showpage=1
Question -
When I run Restore-DatabaseAvailabilityGroup -Identity DAG -ActiveDirectorySite <Recovery_Site B>, DAG members on the StoppedMailboxServers list are EVICTED from the DAG's cluster.
When I go through the datacenter switchback procedure to re-add the evicted DAG members, will Exchange synchronize the database copies on Aex1/Aex2 from Bex2 or will it have to perform a FULL reseed? Total downtime for Aex1/Aex2 will
be 1-2 days MAX.
My concern is that full database seeds takes a very long time between the two sites (they are in different geographical locations, connected via a WAN connection with a latency of ~150ms). I want to avoid having to perform a FULL reseed.
I appreciate any and all input. Thanks!

Hi mlawpa,
They will need some time to sync the database copies after the Mailbox servers have been incorporated into the DAG.
However, accoding to some specific conditions during the outage, it may require reseeding the database copies.
For example, if during the outage, you remove the database copies from the failed primary datacenter to allow log file truncation to occur for the surviving active copies in the second datacenter, reseeding will be required.
More details in the following article:
Datacenter Switchovers
http://technet.microsoft.com/en-us/library/dd351049(v=exchg.141).aspx
Please notice the "Mailbox Server Role Switchback" session.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

  • Silly Doubt in Exchange 2010 - Datacenter SwitchOver

    Hi Team
    i have a very silly doubt in my exchnage 2010 environment with two sites
     two mailbox servers (Site A )  and another two mailbox servers in site B  .All the four mailbox servers is same DAG 
    site A mailbox database copies are available in site B and Vice Versa.
    in site A , if two mailbox servers is down / not reachable, automatically the database are moved from site A to Site B and mounted over there. and normal mailflow is happening with interruption of few sec / minutes
    then why we need Datacenter SwitchOver  and what is is purpose of doing Datacenter SwitchOver and Datacenter SwitchBack, as the mailflow is functioning without any issue
    it may be silly , but i would like to be very clear from  top of my head
    thanks team

    Hi Li, 
    Correct , that is not a problem for me now. The problem is below as mentioned 
    i just started the datacenter switch over  from one site to another site and unfortunately i have been halted in the initial stage itself in my test environment
    Site: Main-Office
    One Domain Controller: Indlabbitesdc01.labbites.co.in  - Hosting
    DNS Services
    One Hub Server: Indlbht01.labbites.co.in  - Witness Server 
    2 CAS server (CAS ARRAY) - casarray1.labbites.co.in and casarray2.labbites.co.in
    Casarray IP: 172.29.137.50
    2 Mailbox Servers – Indlbmb01.labbites.co.in and indlbmb02.labbites.co.in
    Dag Name: DAG1
    DAG IP: 172.29.137.140
    Site: GUINDY-OFFICE
            - No WIteness server in this SIte
    One Additional Controller: Labdeldc01.labbites.con.in
    One HUB and CAS Server: indlbguex01.labbites.co.in
    2 Mailbox servers – indlbgumbx01.labbites.co.in and indlbmb03.labbites.co.in
    Both mailbox servers are members in DAG1
    As per Plan , DAC is enabled in DAG1 
    Next step i shutdown all the servers Site:
    Main-Office and trying to open the powershell from one of the mailbox from Site: GUINDY-OFFICE  for issuing the command Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell  and i got
    the below error
             VERBOSE:
    Connecting to indlbgumbx01.labbites.co.in
    [indlbgumbx01.labbites.co.in]
    Connecting to remote server failed with the following error message : WinRM cannot proces
    s
    the request. The following error occured while using Kerberos authentication: There are currently no logon servers available to service the logon request.
     Possible causes are:
      -The user name or
    password specified are invalid.
      -Kerberos is used
    when no authentication method and no user name are specified.
      -Kerberos accepts
    domain user names, but not local user names.
      -The Service Principal
    Name (SPN) for the remote computer name and port does not exist.
      -The client and
    remote computers are in different domains and there is no trust between the two domains.
     After checking for
    the above issues, try the following:
      -Check the Event
    Viewer for events related to authentication.
      -Change the authentication
    method; add the destination computer to the WinRM TrustedHosts configuration setting or us
    e HTTPS transport.
     Note that computers
    in the TrustedHosts list might not be authenticated.
       -For more
    information about WinRM configuration, run the following command: winrm help config. For more information,
     see the about_Remote_Troubleshooting
    Help topic.
        + CategoryInfo
             : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
       eption
        + FullyQualifiedErrorId
    : PSSessionOpenFailed
    Exception calling "GetComputerDomain"
    with "0" argument(s): "The local computer is not joined to a domain or the domain
     cannot be contacted."
    At C:\Program Files\Microsoft\Exchange
    Server\V14\bin\ConnectFunctions.ps1:204 char:70
    +     [System.DirectoryServices.ActiveDirectory.Domain]::GetComputerDomain
    <<<< ().Forest.Name
        + CategoryInfo
             : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId
    : DotNetMethodException
    Exception calling "GetComputerSite"
    with "0" argument(s): "The specified domain either does not exist or could not be c
    ontacted.
    At C:\Program Files\Microsoft\Exchange
    Server\V14\bin\ConnectFunctions.ps1:164 char:92
    +     $localSite=[System.DirectoryServices.ActiveDirectory.ActiveDirectorySite]::GetComputerSite
    <<<< ()
        + CategoryInfo
             : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId
    : DotNetMethodException
    Exception calling "FindAll"
    with "0" argument(s): "Unknown error (0x80005000)"
    At C:\Program Files\Microsoft\Exchange
    Server\V14\bin\ConnectFunctions.ps1:253 char:17
    +     $search.FindAll
    <<<< ()
        + CategoryInfo
             : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId
    : DotNetMethodException
    You cannot call a method
    on a null-valued expression.
    At C:\Program Files\Microsoft\Exchange
    Server\V14\bin\ConnectFunctions.ps1:146 char:33
    +      
              $siteName = $siteDN.ToString <<<< ().SubString(3).Split(",")[0]
        + CategoryInfo
             : InvalidOperation: (ToString:String) [], RuntimeException
        + FullyQualifiedErrorId
    : InvokeMethodOnNull
    WARNING:
    No Exchange servers are available in the Active Directory site . Connecting to an Exchange server in another
    Active Directory site.
    Failed to connect to an
    Exchange server in the current site.
    Enter
    the server FQDN where you want to connect.: lbdeldc01.labbites.co.in
    VERBOSE: Connecting to
    lbdeldc01.labbites.co.in
    [lbdeldc01.labbites.co.in]
    Connecting to remote server failed with the following error message : WinRM cannot process t
    he request. The following
    error occured while using Kerberos authentication: There are currently no logon servers avail
    able to service the logon
    request.
     Possible causes are:
      -The user name or
    password specified are invalid.
      -Kerberos is used
    when no authentication method and no user name are specified.
      -Kerberos accepts
    domain user names, but not local user names.
      -The Service Principal
    Name (SPN) for the remote computer name and port does not exist.
      -The client and
    remote computers are in different domains and there is no trust between the two domains.
     After checking for
    the above issues, try the following:
      -Check the Event
    Viewer for events related to authentication.
      -Change the authentication
    method; add the destination computer to the WinRM TrustedHosts configuration setting or us
    e HTTPS transport.
     Note that computers
    in the TrustedHosts list might not be authenticated.
       -For more
    information about WinRM configuration, run the following command: winrm help config. For more information,
     see the about_Remote_Troubleshooting
    Help topic.
        + CategoryInfo
             : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
       eption
        + FullyQualifiedErrorId
    : PSSessionOpenFailed
    [PS] C:\Windows\system32>

  • Proper way to install windows update on Exchange 2010 DAG with one mailbox server in Head Office and 1 mailbox server in DR site both are members of 1 DAG

    Hi Guyz,
    I have this setup in my exchange environment.
    1 DAG with 2 members
    - One member is located in Head Office and the other member is located in DR site. All of the mailbox databases are located only in HO (Plan to add additional second member in HO soon). Now what is the proper way to install windows patches on the
    member in HO? I don't want to move the databases to DR site as much as possible.
    Appreciate your feedback and Many thanks in advance guyz..
    More power to all!
    Regards,

    Hi,
    To update the DAG members with new patches, the update process should be managed to prevent all of the DAG members from being offline at the same time.
    To do this, I recommend you move the active mailbox databases off a particular server so that it can be patched, and if necessary rebooted, without causing any downtime for mailbox users on that database.
    For detailed steps, here is an article for your reference.
    How to Install Updates on Exchange Server 2010 Database Availability Groups
    http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-database-availability-groups/
    Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Mailbox move and dag members

    Hello,
    Exchange 2010 sp3 ru6
    windows 2008R2 enterprise
    I have 2 servers in HQ and 1 servers in DR site - all members of DAG
    MailboxServer1
    MB1 5 databases - Active node - HQ
    db1 950GB
    db2 200GB
    db3 100GB
    MailboxServer2
    MB2 5 databases - passive node - HQ
    db1 950GB
    db2 200GB
    db3 100GB
    DRMailboxServer1
    MB3 5 databases - passive node - DR site
    db1 950GB
    db2 200GB
    db3 100GB
    db1 is 950GB large and contains 800 mailboxes.  I am planning to move users from db1 to db2 and db3,  to keep db1 from growing beyong 1TB.
    When I start moving users,  I understand it will generate transactions logs on the active node, and  the same transaction logs also gets transfeered
    to db2 and db3 depending on where the mailboxes are being moved to. Is my understanding correct ?
    What other impacts will this have on other members of the dag ?
    What are some best practices and gotchas, I should be looking for ?
    Thanks!
    JOe

    Hi,
    Agree with Willard. Although the source server logs the record deletions, which are small, the target server must write all transferred data first to transaction logs. If you generate 10 GB of log files in one day, and keep a three-day buffer of 30 GB,
    moving 50 2-GB mailboxes (100 GB) would fill your target log LUN and cause downtime. In cases such as these, you may have to allocate additional capacity for the log LUNs to accommodate your move mailbox practices.
    I recommend you move a percentage of user mailboxes on a nightly or weekly basis to different databases.
    Here is a related article for your reference.
    http://technet.microsoft.com/en-gb/library/ee832796(v=exchg.141).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2010: Virtualized Exchange 2010 Datacenter Migration

    We have a virtualized Exchange 2010 production implementation that needs to be relocated to a new datacenter. We will be leveraging SAN based replication and VMWare to cutover.
    Some background info:
    3 CAS/HUB servers
    4 Node DAG across 2 sites (3 production Mailbox servers in the site to be migrated, 1 mailbox server will not move and be left in DR)
    Since I need to shutdown 3 mailbox servers in a 4 node DAG, the cluster will go offline and the databases will dismount. I could run a datacenter switchover to preserve service, but I have the OK to take Exchange completely down. 
    Knowing that:
    1) What are the best practices to shutdown and start up all the CAS servers and Mailbox servers (both in prod and DR)?
    2) Should I suspend replication or dismount the databases in advance and prevent them from automatically mounting on boot up?  Is the StartDagServerMaintenance script relevant in this situation?
    Any suggestions on the proper way to go about this is much appreciated.  Thanks for reading.

    -->1) During the shutdown...would it make sense to turn off the 4th mailbox server in the DAG which is located in our DR site? I'm thinking that leaving the DR mailbox server powered off and powering it up last among the DAG members would prevent
    any database copies from being activated in DR. 
    You already have a planned outage. I suggest you shut down the server in DR and start that after starting
    all the 3.
    2) To be able to mount a database in a 4 node DAG, I need to have the file share witness and two mailbox servers available first...correct?  
    Your fileshare witness should be online first otherwise none of your databases will get mounted.
    If your DAG contains odd number of members filesharewitness will be ignored, (even number of DAG members will use filesharewitness)http://blog.credera.com/technology-insights/microsoft-solutions/when-do-dags-need-a-file-share-witness/
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • DAG Design

    I've got 3 database servers in a DAG, 2 of them at my main site, and 1 of them at my DR site.  We also have 2 file share witnesses configured, the primary being at the main site, and the alternate at the DR site.  We recently had a scenario where
    the main site went down completely and that caused the cluster to go down, leaving only the db server and FSW at the DR site up.  Since the cluster was down, the databases dismounted on the DR site server and would not mount.  It appears that the
    servers at the main site going down caused the DR site to think that it was the site that was offline and therefore things didn't fail over properly.
    My question is - What can we change to make it so that the DR site will become the active site in the event of an unexpected outage at the main site?  I understand that since we have 3 database servers, we're not actually using the FSW at either location
    unless we happen to lose one of those 3 servers.  Would putting the primary FSW at the DR site remedy this problem?

    Failovers are not automatic in your scenario.
    You need to implement DAC Mode and do a datacenter switchover:
    http://technet.microsoft.com/en-us/library/dd351049(v=exchg.150).aspx
    If you want automatic failover, you would need a 3rd datacenter for the File Share Witness and an even amount of DAG members in each data center.
    http://blogs.technet.com/b/scottschnoll/archive/2012/11/01/storage-high-availability-and-site-resilience-in-exchange-server-2013-part-3.aspx
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • CAS Array and DAG Site Resiliency (2 Remote Sites via Point to Point Protocol)

    Hi, we are planning to deploy Exchange HA and Site Resiliency but i had some troubles understanding some concepts.
    Out current configurations settings:
    Datacenter A:
    1 MB/CAS/HT (MB01)
    1 CAS (CAS01)
    1 Point to Point link between Datacenter A and Datacenter B (We create a VLAN in the remote datacenter pointing to the Active Directory site where our Exchange server is).
    1 Active Directory Site with 2 Domain controllers (with VLAN 192.1.3.x in Datacenter A and VLAN 192.1.20.x in Datacenter B)
    Datacenter B:
    We want to install a new Exchange CAS Server (CAS02) in VLAN 192.1.20.x, is it posible to create a CAS Array with this configuration considering the replication network for the cluster in the MS Windows Server NLB, so that our Virtual IP of the cluster points
    to 192.1.3.x VLAN? What are the network considerations to the replication and MAPI network between VLANs? Does we need some third party NLB or this could be achieved with MWS2008R2?
    Same configuration for the DAG, with a new server (MB02) just for the MB role. The idea is to remove the CAS role from MB01 and have 2 Exchange Mailbox servers members of the DAG and 2 Exchange CAS Servers members of the CAS Array, so in case of a disaster
    in Datacenter A our clients automatically failover to Datacenter B in this case all of our clients will be pointing to the CAS Array in their Outlook.
    Hope you can help me with this, i don't know if this is possible with our actual infraestructure.
    Best Regards,
    Gerardo

    Thanks Ed, 
    So in that case we will need at least 4 servers in Datacenter A (2 MB members of DAG and 2 CAS/HUB members of the CAS Array) to get a decent HA solution, Am I correct?
    What about the other server in Datacenter B for DR, it will be a passive node or just another multirole server. So in case of DR (Let's say our Datacenter A is totally wrecked) I will need to switchover manually with my DB backups and switchover the user
    mailbox and outlook clients to point to the DR server? I didn´t get the point of the DR server in Datacenter B, can you explain a little bit more?
    I'm totally agree with you about the false positive failovers because our network doesn't meet that requeriments at all.
    Hope you can help me to clear my mind.
    Best Regards,
    Gerardo

  • Dag failed the wrong way??

    Thanks for reading my question. We have a main site and a DR site. I'm running a single exchange server in the main site for ~120 users. I created an exchange server in our DR site, removed the default database from that site and created a DAG failover
    with the main site primary. I also had a file witness in the main site thinking that if the link between sites failed the two parts at the main site would keep those up, only if the primary server failed would it fail to the DR.
    Long story short, we lost the MPLS link due to a fiber cut.  Instead of keeping the primary active, the DR site kicked in and the primary failed to stay online.  We had to scramble to foreceably remove the DAG to get back up and working at the
    main site. 
    I now need to rebuild this in a way that works as I want:  With the primary and file witness in the main site, did I do something wrong to make this fail in what I thought was the improbable way?  Is there a better architecture to accomplish this?
    Thanks!
    Jim
    Jim Tall

    For a stretched DAG across a WAN, you should implement DAC mode and disable the DR server from automatic db activation. If needed, use a datacenter switchover technique which requires you to manually bring the DR server online.
    http://technet.microsoft.com/en-us/library/dd979790(v=exchg.150).aspx
    Datacenter Activation Coordination mode
    http://technet.microsoft.com/en-us/library/dd351049(v=exchg.150).aspx
    Datacenter Switchovers
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Node Majority DAG, How to recover when quorum is lost

    Hi
    I have EXchange 2013 SP1 DAG, Node Majority where 2 MBX servers in the primary site and 1 MBX server in the DR Site. If there is a simultaneous loss of the 2 MBX servers in the primary site as in a power failure, then quorum will be lost. 
    How can I recover operations using the MBX Server in DR?????
    jk

    Hi ,
    Agree with Pavan.
    Datacenter switchover is the only option.If there is simultaneous failure happened on all the nodes in the primary site or else an primary datacenter failure then there wouldn't be an enough time for the cluster to recalculate and adjust the quorum.So the only
    way is to do an datacenter switchover.
    Reference link for datacenter Switchover :
    http://smtpport25.wordpress.com/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/
    Above mentioned article is for exchange 2010 even though the steps defined on that article is same for exchange 2013.
    Reference kink for Dynamic quorum : 
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/exchange-2013-dag-dynamic-quorum-part2.html
    Please reply me if anything is not clear.
    Thanks & Regards S.Nithyanandham

  • Exchange 2010 SP3 DAG Witness/Quorom Server Placement with 3 Datacenters

    Hi we have 2 Exchange 2010 SP3 Server in the same Organization in a DAG
    First one in Datacenter 1 in Germany
    Second one in Datacenter 2 in Austria
    There is a Third Datacenter available in Switzerland
    Where should we place the Witness Server?
    Our major concern is not a WAN Link will go down, most time a Datacenter will loose Power for some hours due
    maintenance work or other things.
    Is it a good idea to place the Witness Server in the third Datacenter!?
    We found a Document which some missconception which talks about placing the witness always in
    the primary Datacenter. But the Datacenter Switchover Document for Exchange 2013 says use a third Datacenter.
    Is that also okay for Exchange 2010 or are they totally different?
    Thank you in advance
    Troga

    Hi,
    It is a new configuration option in Exchange 2013 that we use a third location for hosting the witness server.
    Placing FSW in the third location will privide the ability automatically failover databases to the other datacenter in response to a datacenter-level failure event.
    For more details, you can look at the "Witness server placement considerations" section in the following article.
    http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Unable to send to external email recipients - Multi Tenant Exchange 2013 - MultiRole servers in DAG

    Greetings all, I hope someone can help.
    I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
    Internal mail flow is fine (external email addresses can send to the domain).
    External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
    There are two multi-role Exchange servers that are members of the DAG.
    I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
    No SSL certificates have been purchased or installed yet.
    Exchange URLs have not been changed since default configuration at install.
    OWA and ECP works both internal and external.
    External DNS works with SPF and PTR records correctly configured
    Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
    Send Connectors are the default ones created during install. Receive connector is standard configuration with  - * - 
    When sending email to an external address, I receive a failure notice
    ServerName.test.corp.int gave this error:
    Unable to relay 
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
    More Info - 
    ServerName.test.corp.int
    Remote Server returned '550 5.7.1 Unable to relay'
    I have been troubleshooting this for many hours with no progress.
    I have created new Send Connectors for the server that is advising that it is unable to relay, but they have all failed.
    I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
    I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
    I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
    I am at a loss as to why I can't send out with the default configuration. I would assume that email would flow out without any changes, but this does not happen.
    Can someone please assist before I lose my sanity.
    Thanks in advance,
    Terry

    Greetings all, I hope someone can help.
    I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
    Internal mail flow is fine.
    Incoming mail from external senders is also fine. - 
    external email addresses can send to the domain).
    External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
    There are two multi-role Exchange servers that are members of the DAG.
    I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
    No SSL certificates have been purchased or installed yet.
    Exchange URLs have not been changed since default configuration at install.
    OWA and ECP works both internal and external.
    External DNS works with SPF and PTR records correctly configured
    Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
    Receive Connectors are the default ones created during install. Send connector is standard configuration with  - * - 
    When sending email to an external address, I receive a failure notice
    ServerName.test.corp.int gave this error:
    Unable to relay 
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
    More Info - 
    ServerName.test.corp.int
    Remote Server returned '550 5.7.1 Unable to relay'
    I have been troubleshooting this for several days with no progress.
    I have created new Receive Connectors for the server that is advising that it is unable to relay, but they have all failed.
    I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
    I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
    I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
    Even more info - Further troubleshooting -
    I found my one of my Exchange servers had an extra NIC. I have since added a second NIC to the other server, so now both Exchange servers have dual NICs. I removed the DAG cleanly and recreated the DAG from scratch, using this link -
    hxxp://careexchange.in/how-to-create-a-database-availability-group-in-exchange-2013/ 
    The issue still exists, even with a newly created DAG. I also found that the Tenant Address Books were not 'applied'. I applied them but still no resolution
    I think the issue is related to multi-tenant configuration even though the error says that it can't relay. The unable to relay message can appear when sending from a domain that the Organization does not support. Like trying to email as [email protected]
    when you domain name is apple.com - But through extensive research I still can't resolve the issue.
    Can someone please assist before I lose my sanity.
    Thanks in advance,
    Terry

  • Exchange 2010 SP3 - Can DAG member be on OS 2012 R2 STD?

    Hi guys.
    We have Exchange 2010 SP3 on 2008 r2 enterprise.
    now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
    with best regards,
    bostjanc

    Hi guys.
    We have Exchange 2010 SP3 on 2008 r2 enterprise.
    now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
    with best regards,
    bostjanc
    No. It wont let you do that. 
    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx
    DAGs are available in both Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition. In addition, a DAG can contain a mix of servers running Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition.
    Each member of the DAG must also be running the same operating system. Exchange 2010 is supported on both the Windows Server 2008 and Windows Server 2008 R2 operating systems. All members of a DAG must run either Windows Server 2008 or Windows Server 2008
    R2. They can't contain a combination of both Windows Server 2008 and Windows Server 2008 R2.
    In addition to meeting the prerequisites for installing Exchange 2010, there are operating system requirements that must be met. DAGs use Windows Failover Clustering technology, and as a result, they require the Enterprise version of Windows.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Mailbox Databases - 1500 users Exchange 2010 DAG

    I have the following setup for a 5 server DAG setup and would like to know the recommended setup for high availability for all user databases. I would like the databases copied to several DAG members servers, but am unsure as to how i should stagger the
    database replication. Please see the drive sizes below and send me feedback/recommendations.
    Each of my DAG member servers (mailbox servers) has the following storage space available:
    C:\60GB(O/S), D:\1TB(Mailboxes), E:\1TB(Mailboxes) F:\(logs)
    How many databases should i create to maximize efficiency and give best user performance/experience?
    To how many DAG member servers should i copy the database in order to achieve a reasonable amount of High Availability?
    Again, I have 1500 users and 2TB per server to accommodate mailbox databases.
    Users average 500MB mailbox quotas.
    Can i create the DAG replicas on the second drive (E:\) or should i just use both terabyte volumes exclusively for users mailboxes?

    Hi,
    5 members in a DAG and one database created for every member, I suggest you create three copys for a database like the following figure. Any two servers corruption couldn't interrupt any client connection.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Sean Xiao
    TechNet Community Support

  • Can't add server to DAG cluster.

    I have two servers in a cluster, but when I add our main mail server I get the following error. 
    All of the servers have two NIC's which the same configuration with two networks.
    I can create a DAG with this server alone, but when I add another one, I get this message. 
    All three servers have the same DNS settings.
    add-databaseavailabiltygroupserver started on machine EXCHANGE.
    [2009-12-25T01:52:25] add-dagserver started
    [2009-12-25T01:52:25] commandline:         $scriptCmd = {& $wrappedCmd @PSBoundParameters }
    [2009-12-25T01:52:25] Option 'Identity' = 'dage'.
    [2009-12-25T01:52:25] Option 'MailboxServer' = 'exchange'.
    [2009-12-25T01:52:25] Option 'DatabaseAvailabilityGroupIpAddresses' = ''.
    [2009-12-25T01:52:25] Option 'WhatIf' = ''.
    [2009-12-25T01:52:25] Process: w3wp w3wp.exe:1368.
    [2009-12-25T01:52:25] User context = 'NT AUTHORITY\SYSTEM'.
    [2009-12-25T01:52:25]   Member of group 'Everyone'.
    [2009-12-25T01:52:25]   Member of group 'BUILTIN\Users'.
    [2009-12-25T01:52:25]   Member of group 'NT AUTHORITY\SERVICE'.
    [2009-12-25T01:52:25]   Member of group 'CONSOLE LOGON'.
    [2009-12-25T01:52:25]   Member of group 'NT AUTHORITY\Authenticated Users'.
    [2009-12-25T01:52:25]   Member of group 'NT AUTHORITY\This Organization'.
    [2009-12-25T01:52:25]   Member of group 'BUILTIN\IIS_IUSRS'.
    [2009-12-25T01:52:25]   Member of group 'LOCAL'.
    [2009-12-25T01:52:25]   Member of group 'IIS APPPOOL\MSExchangePowerShellAppPool'.
    [2009-12-25T01:52:25]   Member of group 'BUILTIN\Administrators'.
    [2009-12-25T01:52:25] Updated Progress 'Validating the parameters.' 2%.
    [2009-12-25T01:52:25] Working
    [2009-12-25T01:52:25] Mailbox server: value passed in = exchange, mailboxServer.Name = EXCHANGE, mailboxServer.Fqdn = EXCHANGE.acsi.com
    [2009-12-25T01:52:25] LogClussvcState: clussvc is Stopped on EXCHANGE.acsi.com. Exception (if any) = none
    [2009-12-25T01:52:25] The IP addresses for the DAG are (blank means DHCP): 
    [2009-12-25T01:52:25] Looking up IP addresses for DAGE.
    [2009-12-25T01:52:28] Failure while trying to resolve DAGE: threw a SocketException: The requested name is valid, but no data of the requested type was found.
    [2009-12-25T01:52:28] Looking up IP addresses for exchange.
    [2009-12-25T01:52:28]   exchange = [ fe80::1898:2778:f04d:d646%11, fe80::4984:510e:1fea:fb92%12, 2002:c701:63d2::c701:63d2, 199.1.99.210, 10.10.1.210 ].
    [2009-12-25T01:52:28] Looking up IP addresses for EXCHANGE.acsi.com.
    [2009-12-25T01:52:28]   EXCHANGE.acsi.com = [ fe80::1898:2778:f04d:d646%11, fe80::4984:510e:1fea:fb92%12, 2002:c701:63d2::c701:63d2, 199.1.99.210, 10.10.1.210 ].
    [2009-12-25T01:52:28] DAG DAGE has 2 servers:
    [2009-12-25T01:52:28] DAG DAGE contains server EXCHANGE2.
    [2009-12-25T01:52:28] DAG DAGE contains server EXCHANGE3.
    [2009-12-25T01:52:28] Updated Progress 'Checking if Mailbox server 'EXCHANGE' is in a database availability group.' 4%.
    [2009-12-25T01:52:28] Working
    [2009-12-25T01:52:28] GetRemoteCluster() for the mailbox server failed with exception = An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"OpenCluster(EXCHANGE.acsi.com) failed with 0x6d9. Error: There are no more endpoints available from the endpoint mapper"' failed.. This is OK.
    [2009-12-25T01:52:28] Ignoring previous error, as it is acceptable if the cluster does not exist yet.
    [2009-12-25T01:52:28] DumpClusterTopology: Opening remote cluster DAGE.
    [2009-12-25T01:52:28] DumpClusterTopology: Failed opening with Microsoft.Exchange.Cluster.Replay.AmGetFqdnFailedNotFoundException: An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database availability group topology. Error: The fully qualified domain name for node 'DAGE' could not be found.
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.<>c__DisplayClass1.<ResolveFqdn>b__0(Object , EventArgs )
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmHelper.RunADOperationEx(EventHandler ev)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.ResolveFqdn(String shortNodeName)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.GetFqdn(String shortNodeName)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerName..ctor(String serverName)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.DumpClusterTopology..ctor(String nameCluster, ITaskOutputHelper output)
    [2009-12-25T01:52:28] Dumping the cluster by connecting to: DAGE.
    [2009-12-25T01:52:28] DumpClusterTopology: Not dumping, since the cluster could not be contacted.
    [2009-12-25T01:52:28] Opening the cluster on nodes [exchange2, exchange3].
    [2009-12-25T01:52:28] Other mailbox servers in the DAG are already members of cluster 'DAGE'
    [2009-12-25T01:52:28] The server EXCHANGE does not belong to a cluster, and the other servers belong to DAGE.
    [2009-12-25T01:52:29] Successfully resolved servers based on the AD configuration.
    [2009-12-25T01:52:29] The following servers are in the StartedServers list:
    [2009-12-25T01:52:29] The following servers are in the StoppedServers list:
    [2009-12-25T01:52:29] Verifiying that the members of database availability group 'DAGE' are also members of the cluster.
    [2009-12-25T01:52:29] Verifying that the members of cluster 'DAGE' are also members of the database availability group.
    [2009-12-25T01:52:29] According to GetNodeClusterState(), the server EXCHANGE is NotConfigured.
    [2009-12-25T01:52:29] The CNO is currently Offline.
    [2009-12-25T01:52:29] The network name 'DAGE' is not online. Please check that the IP address configuration of the Database Availability Group is correct.
    [2009-12-25T01:52:29] InternalValidate() done.
    [2009-12-25T01:52:29] Updated Progress 'Adding server 'EXCHANGE' to database availability group 'DAGE'.' 6%.
    [2009-12-25T01:52:29] Working
    [2009-12-25T01:52:29] Updated Progress 'Adding server 'EXCHANGE' to the cluster.' 8%.
    [2009-12-25T01:52:29] Working
    [2009-12-25T01:53:12] The following log entry comes from a different process, run on machine 'exchange3.acsi.com'. BEGIN
    [2009-12-25T01:53:12] [2009-12-25T01:52:29] Opening a local AmCluster handle.
    [2009-12-25T01:52:29] Updated Progress 'Adding server 'exchange' to database availability group 'DAGE'.' 2%.
    [2009-12-25T01:52:29] Working
    [2009-12-25T01:52:29] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 12, szObjectName = EXCHANGE, dwStatus = 0x0 )
    [2009-12-25T01:53:11] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 12, szObjectName = EXCHANGE, dwStatus = 0x800713bb )
    [2009-12-25T01:53:11] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 12, szObjectName = EXCHANGE, dwStatus = 0x800713bb )
    [2009-12-25T01:53:11] Found a matching exception: Microsoft.Exchange.Cluster.Replay.DagTaskValidateNodeTimedOutException: A server-side database availability group administrative operation failed. Error: Windows Failover Clustering timed out while trying to validate server 'EXCHANGE'. If this is in a disjoint DNS namespace, the DNS suffixes for all servers in the database availability group must be present on every server.
    [2009-12-25T01:53:11] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 12, szObjectName = EXCHANGE, dwStatus = 0x0 )
    [2009-12-25T01:53:11] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 12, szObjectName = , dwStatus = 0x0 )
    [2009-12-25T01:53:12] The preceding log entry comes from a different process, run on machine 'exchange3.acsi.com'. END
    [2009-12-25T01:53:12] The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2009-12-25_01-52-25.205_add-databaseavailabiltygroupserver.log".
    [2009-12-25T01:53:12] WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A server-side database availability group administrative operation failed. Error: The operation failed with message: Windows Failover Clustering timed out while trying to validate server 'EXCHANGE'. If this is in a disjoint DNS namespace, the DNS suffixes for all servers in the database availability group must be present on every server. ---> Microsoft.Exchange.Cluster.Replay.DagTaskValidateNodeTimedOutException: A server-side database availability group administrative operation failed. Error: Windows Failover Clustering timed out while trying to validate server 'EXCHANGE'. If this is in a disjoint DNS namespace, the DNS suffixes for all servers in the database availability group must be present on every server.
       at Microsoft.Exchange.Cluster.ClusApi.AmCluster.AddNodeToCluster(AmServerName nodeName, IClusterSetupProgress setupProgress, IntPtr context, Exception& errorException, Boolean throwExceptionOnFailure)
       at Microsoft.Exchange.Cluster.Replay.DagHelper.AddDagClusterNode(AmServerName mailboxServerName, String& verboseLog)
       --- End of inner exception stack trace (Microsoft.Exchange.Cluster.Replay.DagTaskValidateNodeTimedOutException) ---
       at Microsoft.Exchange.Cluster.Replay.DagHelper.ThrowDagTaskOperationWrapper(Exception exception)
       at Microsoft.Exchange.Cluster.Replay.DagHelper.AddDagClusterNode(AmServerName mailboxServerName, String& verboseLog)
       at Microsoft.Exchange.Cluster.ReplayService.ReplayRpcServer.<>c__DisplayClass34.<RpcsAddNodeToCluster>b__33()
       at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String databaseName, RpcServerOperation rpcOperation)
       --- End of stack trace on server (exchange3.acsi.com) ---
       at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String databaseName, String serverName, RpcErrorExceptionInfo errorInfo)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunRpcOperationDbName(String serverName, String databaseName, Int32 timeoutMs, ReplayRpcClient& rpcClient, IHaRpcExceptionWrapper rpcExceptionWrapperInstance, InternalRpcOperation rpcOperation)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunRpcOperation(String serverName, Nullable`1 dbGuid, Int32 timeoutMs, ReplayRpcClient& rpcClient, IHaRpcExceptionWrapper rpcExceptionWrapperInstance, InternalRpcOperation rpcOperation)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunAddNodeToCluster(AmServerName serverName, AmServerName newNode, String& verboseLog)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityGroupServer.JoinNodeToCluster()
    [2009-12-25T01:53:12] Updated Progress 'Done!' 100%.
    [2009-12-25T01:53:12] COMPLETED
    add-databaseavailabiltygroupserver explicitly called CloseTempLogFile().

    1. I don't think I have a disjoint. There is only one domain and every server has the same primary dns suffix.
    2. This is the server that cannot be added. Can only be added to a group itself:
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : EXCHANGE
       Primary Dns Suffix  . . . . . . . : acsi.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : acsi.com
    Ethernet adapter Local Area Connection* 9:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
       Physical Address. . . . . . . . . : 02-1E-C9-45-A7-EA
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter Local Area Connection 2:
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
       Physical Address. . . . . . . . . : 00-1E-C9-45-A7-EB
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.10.1.210(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.10.1.1
       DNS Servers . . . . . . . . . . . : 199.1.99.30
                                           199.1.99.10
                                           199.1.99.20
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Local Area Connection:
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
       Physical Address. . . . . . . . . : 00-1E-C9-45-A7-EA
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 199.1.99.210(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 
       DNS Servers . . . . . . . . . . . : 199.1.99.30
                                           199.1.99.10
                                           199.1.99.20
       NetBIOS over Tcpip. . . . . . . . : Enabled
    This is one of the two that is in a functional group:
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : exchange2
       Primary Dns Suffix  . . . . . . . : acsi.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : acsi.com
    Ethernet adapter Local Area Connection* 9:
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
       Physical Address. . . . . . . . . : 02-11-43-04-82-5C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 169.254.1.39(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Local Area Connection:
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Connection
       Physical Address. . . . . . . . . : 00-11-43-04-82-5C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 199.1.99.212(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 199.1.99.154(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 
       DNS Servers . . . . . . . . . . . : 199.1.99.30
                                           199.1.99.10
                                           199.1.99.20
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Local Area Connection 2:
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
       Physical Address. . . . . . . . . : 00-10-18-5A-7D-38
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.10.1.212(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.10.1.1
       DNS Servers . . . . . . . . . . . : 199.1.99.30
                                           199.1.99.20
                                           199.1.99.10
       NetBIOS over Tcpip. . . . . . . . : Enabled
    And the other one that's part of the group that's working:
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : exchange3
       Primary Dns Suffix  . . . . . . . : acsi.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : acsi.com
    Ethernet adapter Local Area Connection* 10:
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
       Physical Address. . . . . . . . . : 02-0C-29-95-A5-BD
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 169.254.2.159(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Local Area Connection 2:
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
       Physical Address. . . . . . . . . : 00-0C-29-95-A5-C7
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.10.1.214(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.10.1.1
       DNS Servers . . . . . . . . . . . : 199.1.99.30
                                           199.1.99.10
                                           199.1.99.20
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Local Area Connection:
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
       Physical Address. . . . . . . . . : 00-0C-29-95-A5-BD
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 199.1.99.214(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 
       DNS Servers . . . . . . . . . . . : 199.1.99.30
                                           199.1.99.10
                                           199.1.99.20
       NetBIOS over Tcpip. . . . . . . . : Enabled
    3.  I have both networks setup as the replication network. Is this a problem?
    4. Every server can ping every other network address of these three servers.
    5. Here's the log:
    add-databaseavailabiltygroupserver started on machine EXCHANGE.
    [2009-12-25T01:52:25] add-dagserver started
    [2009-12-25T01:52:25] commandline:         $scriptCmd = {& $wrappedCmd @PSBoundParameters }
    [2009-12-25T01:52:25] Option 'Identity' = 'dage'.
    [2009-12-25T01:52:25] Option 'MailboxServer' = 'exchange'.
    [2009-12-25T01:52:25] Option 'DatabaseAvailabilityGroupIpAddresses' = ''.
    [2009-12-25T01:52:25] Option 'WhatIf' = ''.
    [2009-12-25T01:52:25] Process: w3wp w3wp.exe:1368.
    [2009-12-25T01:52:25] User context = 'NT AUTHORITY\SYSTEM'.
    [2009-12-25T01:52:25]   Member of group 'Everyone'.
    [2009-12-25T01:52:25]   Member of group 'BUILTIN\Users'.
    [2009-12-25T01:52:25]   Member of group 'NT AUTHORITY\SERVICE'.
    [2009-12-25T01:52:25]   Member of group 'CONSOLE LOGON'.
    [2009-12-25T01:52:25]   Member of group 'NT AUTHORITY\Authenticated Users'.
    [2009-12-25T01:52:25]   Member of group 'NT AUTHORITY\This Organization'.
    [2009-12-25T01:52:25]   Member of group 'BUILTIN\IIS_IUSRS'.
    [2009-12-25T01:52:25]   Member of group 'LOCAL'.
    [2009-12-25T01:52:25]   Member of group 'IIS APPPOOL\MSExchangePowerShellAppPool'.
    [2009-12-25T01:52:25]   Member of group 'BUILTIN\Administrators'.
    [2009-12-25T01:52:25] Updated Progress 'Validating the parameters.' 2%.
    [2009-12-25T01:52:25] Working
    [2009-12-25T01:52:25] Mailbox server: value passed in = exchange, mailboxServer.Name = EXCHANGE, mailboxServer.Fqdn = EXCHANGE.acsi.com
    [2009-12-25T01:52:25] LogClussvcState: clussvc is Stopped on EXCHANGE.acsi.com. Exception (if any) = none
    [2009-12-25T01:52:25] The IP addresses for the DAG are (blank means DHCP): 
    [2009-12-25T01:52:25] Looking up IP addresses for DAGE.
    [2009-12-25T01:52:28] Failure while trying to resolve DAGE: threw a SocketException: The requested name is valid, but no data of the requested type was found.
    [2009-12-25T01:52:28] Looking up IP addresses for exchange.
    [2009-12-25T01:52:28]   exchange = [ fe80::1898:2778:f04d:d646%11, fe80::4984:510e:1fea:fb92%12, 2002:c701:63d2::c701:63d2, 199.1.99.210, 10.10.1.210 ].
    [2009-12-25T01:52:28] Looking up IP addresses for EXCHANGE.acsi.com.
    [2009-12-25T01:52:28]   EXCHANGE.acsi.com = [ fe80::1898:2778:f04d:d646%11, fe80::4984:510e:1fea:fb92%12, 2002:c701:63d2::c701:63d2, 199.1.99.210, 10.10.1.210 ].
    [2009-12-25T01:52:28] DAG DAGE has 2 servers:
    [2009-12-25T01:52:28] DAG DAGE contains server EXCHANGE2.
    [2009-12-25T01:52:28] DAG DAGE contains server EXCHANGE3.
    [2009-12-25T01:52:28] Updated Progress 'Checking if Mailbox server 'EXCHANGE' is in a database availability group.' 4%.
    [2009-12-25T01:52:28] Working
    [2009-12-25T01:52:28] GetRemoteCluster() for the mailbox server failed with exception = An Active Manager operation failed. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"OpenCluster(EXCHANGE.acsi.com) failed with 0x6d9. Error: There are no more endpoints available from the endpoint mapper"' failed.. This is OK.
    [2009-12-25T01:52:28] Ignoring previous error, as it is acceptable if the cluster does not exist yet.
    [2009-12-25T01:52:28] DumpClusterTopology: Opening remote cluster DAGE.
    [2009-12-25T01:52:28] DumpClusterTopology: Failed opening with Microsoft.Exchange.Cluster.Replay.AmGetFqdnFailedNotFoundException: An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database availability group topology. Error: The fully qualified domain name for node 'DAGE' could not be found.
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.<>c__DisplayClass1.<ResolveFqdn>b__0(Object , EventArgs )
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmHelper.RunADOperationEx(EventHandler ev)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.ResolveFqdn(String shortNodeName)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerNameCache.GetFqdn(String shortNodeName)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmServerName..ctor(String serverName)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.DumpClusterTopology..ctor(String nameCluster, ITaskOutputHelper output)
    [2009-12-25T01:52:28] Dumping the cluster by connecting to: DAGE.
    [2009-12-25T01:52:28] DumpClusterTopology: Not dumping, since the cluster could not be contacted.
    [2009-12-25T01:52:28] Opening the cluster on nodes [exchange2, exchange3].
    [2009-12-25T01:52:28] Other mailbox servers in the DAG are already members of cluster 'DAGE'
    [2009-12-25T01:52:28] The server EXCHANGE does not belong to a cluster, and the other servers belong to DAGE.
    [2009-12-25T01:52:29] Successfully resolved servers based on the AD configuration.
    [2009-12-25T01:52:29] The following servers are in the StartedServers list:
    [2009-12-25T01:52:29] The following servers are in the StoppedServers list:
    [2009-12-25T01:52:29] Verifiying that the members of database availability group 'DAGE' are also members of the cluster.
    [2009-12-25T01:52:29] Verifying that the members of cluster 'DAGE' are also members of the database availability group.
    [2009-12-25T01:52:29] According to GetNodeClusterState(), the server EXCHANGE is NotConfigured.
    [2009-12-25T01:52:29] The CNO is currently Offline.
    [2009-12-25T01:52:29] The network name 'DAGE' is not online. Please check that the IP address configuration of the Database Availability Group is correct.
    [2009-12-25T01:52:29] InternalValidate() done.
    [2009-12-25T01:52:29] Updated Progress 'Adding server 'EXCHANGE' to database availability group 'DAGE'.' 6%.
    [2009-12-25T01:52:29] Working
    [2009-12-25T01:52:29] Updated Progress 'Adding server 'EXCHANGE' to the cluster.' 8%.
    [2009-12-25T01:52:29] Working
    [2009-12-25T01:53:12] The following log entry comes from a different process, run on machine 'exchange3.acsi.com'. BEGIN
    [2009-12-25T01:53:12] [2009-12-25T01:52:29] Opening a local AmCluster handle.
    [2009-12-25T01:52:29] Updated Progress 'Adding server 'exchange' to database availability group 'DAGE'.' 2%.
    [2009-12-25T01:52:29] Working
    [2009-12-25T01:52:29] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 12, szObjectName = EXCHANGE, dwStatus = 0x0 )
    [2009-12-25T01:53:11] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 12, szObjectName = EXCHANGE, dwStatus = 0x800713bb )
    [2009-12-25T01:53:11] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 12, szObjectName = EXCHANGE, dwStatus = 0x800713bb )
    [2009-12-25T01:53:11] Found a matching exception: Microsoft.Exchange.Cluster.Replay.DagTaskValidateNodeTimedOutException: A server-side database availability group administrative operation failed. Error: Windows Failover Clustering timed out while trying to validate server 'EXCHANGE'. If this is in a disjoint DNS namespace, the DNS suffixes for all servers in the database availability group must be present on every server.
    [2009-12-25T01:53:11] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 12, szObjectName = EXCHANGE, dwStatus = 0x0 )
    [2009-12-25T01:53:11] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 12, szObjectName = , dwStatus = 0x0 )
    [2009-12-25T01:53:12] The preceding log entry comes from a different process, run on machine 'exchange3.acsi.com'. END
    [2009-12-25T01:53:12] The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2009-12-25_01-52-25.205_add-databaseavailabiltygroupserver.log".
    [2009-12-25T01:53:12] WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A server-side database availability group administrative operation failed. Error: The operation failed with message: Windows Failover Clustering timed out while trying to validate server 'EXCHANGE'. If this is in a disjoint DNS namespace, the DNS suffixes for all servers in the database availability group must be present on every server. ---> Microsoft.Exchange.Cluster.Replay.DagTaskValidateNodeTimedOutException: A server-side database availability group administrative operation failed. Error: Windows Failover Clustering timed out while trying to validate server 'EXCHANGE'. If this is in a disjoint DNS namespace, the DNS suffixes for all servers in the database availability group must be present on every server.
       at Microsoft.Exchange.Cluster.ClusApi.AmCluster.AddNodeToCluster(AmServerName nodeName, IClusterSetupProgress setupProgress, IntPtr context, Exception& errorException, Boolean throwExceptionOnFailure)
       at Microsoft.Exchange.Cluster.Replay.DagHelper.AddDagClusterNode(AmServerName mailboxServerName, String& verboseLog)
       --- End of inner exception stack trace (Microsoft.Exchange.Cluster.Replay.DagTaskValidateNodeTimedOutException) ---
       at Microsoft.Exchange.Cluster.Replay.DagHelper.ThrowDagTaskOperationWrapper(Exception exception)
       at Microsoft.Exchange.Cluster.Replay.DagHelper.AddDagClusterNode(AmServerName mailboxServerName, String& verboseLog)
       at Microsoft.Exchange.Cluster.ReplayService.ReplayRpcServer.<>c__DisplayClass34.<RpcsAddNodeToCluster>b__33()
       at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String databaseName, RpcServerOperation rpcOperation)
       --- End of stack trace on server (exchange3.acsi.com) ---
       at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String databaseName, String serverName, RpcErrorExceptionInfo errorInfo)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunRpcOperationDbName(String serverName, String databaseName, Int32 timeoutMs, ReplayRpcClient& rpcClient, IHaRpcExceptionWrapper rpcExceptionWrapperInstance, InternalRpcOperation rpcOperation)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunRpcOperation(String serverName, Nullable`1 dbGuid, Int32 timeoutMs, ReplayRpcClient& rpcClient, IHaRpcExceptionWrapper rpcExceptionWrapperInstance, InternalRpcOperation rpcOperation)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunAddNodeToCluster(AmServerName serverName, AmServerName newNode, String& verboseLog)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityGroupServer.JoinNodeToCluster()
    [2009-12-25T01:53:12] Updated Progress 'Done!' 100%.
    [2009-12-25T01:53:12] COMPLETED
    add-databaseavailabiltygroupserver explicitly called CloseTempLogFile().

  • Exchange 2013 Windows Server 2012 NLB and DAG on the same server

    Hi all, I am installing Exchange 2013 infrastructure with two servers. 
    Both servers have the CAS and Mailbox roles. 
    For mounting on High Availability, will create a DAG. 
    Client Access I have no external Network Load Balancer. 
    I thought about installing the NLB servers in the DAG members, this could not be done before. 
    I do not know if in Windows Server 2012 and Exchange 2013 
    Can I install NLB on members of a DAG? 
    regards
    Microsoft Certified IT Professional Server Administrator

    Hi,
    I’m afraid that WNLB and DAG cannot coexist in the same server. Because WNLB is incompatible with Windows failover clustering. If we're using an Exchange 2010 DAG and we want to use WNLB, we need to have the Client Access server role and the Mailbox server
    role running on separate servers.
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/ff625247(v=exchg.141).aspx
    Thanks,
    Angela Shi
    TechNet Community Support

Maybe you are looking for

  • Location Service set me in the wrong place

    I recently moved from from LA to Las Vegas, and when I installed my network (3 Airport Express) then my MBP (retina 2012) OS 10.10.2 are keep on telling me that my location is in LA (my previous address). Interesting though is when I am Safari and ot

  • Will Not Start New Library.

    LightRoom just will not start a new library. Now matter what.  It will not start a new library. John

  • Quicktime UI doesn't "catch"

    Since upgrading to Lion (and later on to ML) Quicktime has stopped reacting to mouse input. Well, almost. Basically, I can only access the playhead/timeline – the rest of the UI acts as if it doesn't exist. It shows up just fine, the problem is that

  • Unserialized for inventory management?

    Hi, why unserialized update for inventory management, why not direct update and delta queue. regards anitha.

  • Hi guys, I hope someone can help me with a technical question

    a couple of days I recharge the battery of my iphone with the original usb adapter to the electrical plug and then in the right moment when I plugged the phone it came a little spark from the electrical plug and my iphone  was shut down by itself the