Entrar
 
HomeBibliotecaWikiAprenderGaleriaDownloadsSuporte ComunidadeFóruns
Recursos para Profissionais de TI >
> 
> 
Unable to add second Exchange server to DAG or Failover Cluster

Răspuns Unable to add second Exchange server to DAG or Failover Cluster

  • segunda-feira, 28 de maio de 2012 01:21
     
     
    Entrar para Votar
    0

    I have two Exchange 2010 servers running on Server 2008 R2 at two different sites. The sites are connected through a SonicWall site to site VPN. Exchange works perfectly fine on both servers, but I am not able to get the failover working. DAG is configured on MAIL01. On MAIL02, I open EMS and run the following command.

    “Add-DatabaseAvailabilityGroupServer –identity DAG –MailboxServer MAIL02”

    It always fails when trying to add MAIL02 to the cluster. Here is the error message.

    Summary: 1 item(s). 0 succeeded, 1 failed.

    Elapsed time: 09:17:11

    NJ

    Failed

    Error:

    A source-side operation failed. Error The Microsoft Exchange Replication service may not be running on server MAIL02.DOMAIN.LOCAL. Error: Error 0x6ba (The RPC server is unavailable) from cli_RpccGetDbSeedStatus.

    Error 0x6ba (The RPC server is unavailable) from cli_RpccGetDbSeedStatus

    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.355.1&t=exchgf1&e=ms.exch.err.Ex4543D9

    Exchange Management Shell command attempted:

    update-MailboxDatabaseCopy -Identity ‘NJ\MAIL02' -SourceServer 'MAIL01' -Network 'DAG\DAGNetwork01' -DeleteExistingFiles

    Elapsed Time: 09:17:11

    Node 'mail02' failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. Please run the Validate a Configuration wizard to ensure network settings. Also verify the Windows Firewall 'Failover Clusters' rules.

    If I look at the cluster log files, it is always the same error.

    Event 1572: Node 'MAIL02' failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. Please run the Validate a Configuration wizard to ensure network settings. Also verify the Windows Firewall 'Failover Clusters' rules.

    I ran the Cluster Validation to check networking between the two nodes and this is what I get.

    The HostRecordTTL property for network name 'Name: DAG' is set to 300 ( 5 minutes). For local clusters the suggested value is 1200 (20 minutes).

    For this, I run the following command. “cluster res "cluster network 1" /priv HostRecordTTL=1200” but I keep getting error 5007, the cluster resource could not be found. Not sure why I am getting that error since “cluster network 1” is definitely the correct name.

    I am also getting this message in the validation.

    Node MAIL01.DOMAIN.LOCAL is reachable from Node mail02.domain.local by only one pair of interfaces. It is possible that this network path is a single point of failure for communication within the cluster. Please verify that this single path is highly available or consider adding additional networks to the cluster. The following are all pings attempted from network interfaces on node mail02.domain.local to network interfaces on node MAIL01.DOMAIN.LOCAL.

    Result  Source Network Interface  Destination Network Interface  Same Cluster Network  Maximum Allowed Round-Trip Latency 

    Success  mail02.domain.local - MAIL02 Team  MAIL01.DOMAIN.LOCAL - MAIL01 Team  False  2000 

    Result  Source IP Address  Destination IP Address 

    Success  192.168.50.15  192.168.150.15

    It seems obvious that the issue is related to the network, but I can’t figure out what. Windows Firewall is turned off on both servers. I created a Service Object for UDP 3343 in both SonicWall routers. The IP address of MAIL01 is 192.168.150.15 and MAIL02 is 192.168.50.15. What am I missing?

    • Editado KapsZ28 segunda-feira, 28 de maio de 2012 01:22
    •  
     

Todas as Respostas

  • segunda-feira, 28 de maio de 2012 12:28
    Moderador
     
     
    Entrar para Votar
    1

    Hi,

    It is recommend you to get further support in the corresponding community so that you can get the most qualified pool of respondents. Thanks for your understanding.

    For your convenience, I have list the related link as followed.

    Exchange Server 2010
    http://social.technet.microsoft.com/Forums/en-US/category/exchange2010

     
  • segunda-feira, 28 de maio de 2012 17:28
     
     
    Entrar para Votar
    0
    Thanks, but I think the real issue is the failover cluster. If the server would add to the cluster, I probably wouldn't have a problem with DAG.
     
  • terça-feira, 29 de maio de 2012 00:35
    Moderador
     
     
    Entrar para Votar
    1
    Make sure Remote Registry and DHCP Client services are running on the server which you are trying to add on to the Fail-over cluster.

    Press any key... What the ... Where's any key ?

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    About Me ?

     
  • terça-feira, 29 de maio de 2012 01:54
     
     Respondido
    Entrar para Votar
    0
    Wow, that was incredibly easy to do. I removed the DAG and cluster. Then instead of creating the DAG first which automatically creates the cluster, I just created the cluster first. I created the cluster adding both nodes and setting up the quorum as the witness server. When I went to create the DAG, I got an error that the DAG account was already enabled. Easy enough, went into AD and disabled the account. Went back to Exchange and created the DAG. Re-enabled AD account and added both servers to DAG.
    • Marcado como Resposta KapsZ28 terça-feira, 29 de maio de 2012 01:54
    •  
     
  • domingo, 31 de março de 2013 13:04
     
     
    Entrar para Votar
    0

    i have got the same problem cannot add the 2nd server to DAG group. i am facing with the below errors:

    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:16:36


    SAJDDREX01
    Failed

    Error:
    A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: Error 0x71a (The remote procedure call was cancelled) from cli_RpccAddNodeToCluster

    Error 0x71a (The remote procedure call was cancelled) from cli_RpccAddNodeToCluster
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&t=exchgf1&e=ms.exch.err.ExC9C315

    Warning:
    The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2013-03-31_12-28-12.316_add-databaseavailabiltygroupserver.log".


    Exchange Management Shell command attempted:
    Add-DatabaseAvailabilityGroupServer -MailboxServer 'SAJDDREX01' -Identity 'SAEXDAG1'

    Elapsed Time: 00:16:36

    and the log file says :
    ============

    [2013-03-31T12:28:26] Updated Progress 'Adding server 'SAJDDREX01' to database availability group 'SAEXDAG1'.' 6%.
    [2013-03-31T12:28:26] Working
    [2013-03-31T12:28:26] Updated Progress 'Adding server 'SAJDDREX01' to the cluster.' 8%.
    [2013-03-31T12:28:26] Working
    [2013-03-31T12:43:27] The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2013-03-31_12-28-12.316_add-databaseavailabiltygroupserver.log".
    [2013-03-31T12:43:27] WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskOperationFailedException: A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: Error 0x71a (The remote procedure call was cancelled) from cli_RpccAddNodeToCluster ---> Microsoft.Exchange.Rpc.RpcException: Error 0x71a (The remote procedure call was cancelled) from cli_RpccAddNodeToCluster
       at ThrowRpcException(Int32 rpcStatus, String message)
       at Microsoft.Exchange.Rpc.RpcClientBase.ThrowRpcException(Int32 rpcStatus, String routineName)
       at Microsoft.Exchange.Rpc.Cluster.ReplayRpcClient.RpccAddNodeToCluster(String newNode, String& verboseLog)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.<>c__DisplayClass1d.<RunAddNodeToCluster>b__1b(ReplayRpcClient rpcClient)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.<>c__DisplayClass31.<RunRpcOperationDbName>b__30()
       at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRetryableOperation(String serverName, RpcClientOperation rpcOperation)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientHandleRpcException(RpcException ex, String serverName)
       at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRetryableOperation(String serverName, RpcClientOperation rpcOperation)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunRpcOperationDbName(AmServerName serverName, String databaseName, Int32 timeoutMs, IHaRpcExceptionWrapper rpcExceptionWrapperInstance, InternalRpcOperation rpcOperation)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunRpcOperation(AmServerName serverName, Nullable`1 dbGuid, Int32 timeoutMs, IHaRpcExceptionWrapper rpcExceptionWrapperInstance, InternalRpcOperation rpcOperation)
       at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunAddNodeToCluster(AmServerName serverName, AmServerName newNode, String& verboseLog)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityGroupServer.JoinNodeToCluster()
    [2013-03-31T12:44:32] Updated Progress 'Done!' 100%.
    [2013-03-31T12:44:32] COMPLETED
    add-databaseavailabiltygroupserver explicitly called CloseTempLogFile().

    Z.Rather Systems Administrator