Hi!
I'm currently running Exchange 2010 SP3 UR5 and have set up three Exchange 2013 SP1 CU10 servers in preparation for migration.
The three Exchange 2013 servers are set up in a DAG without an AAP, witness server is a non Exchange server. The DAG appears to be working without issue (no failovers, manual failover works fine) but I am getting errors both on the Windows Server side and application side (reported via SCOM 2012 R2).
On each server I get the following error in Server Manager: Exchange2013DAG Target name resolution error.
Additionally, the following error keeps getting generated by SCOM for each server:
Alert: Cluster resource failed
Source: Cluster Service
Path: VEXCH002.DOMAIN.LOCAL
Last modified by: System
Last modified time: 12/28/2015 12:32:17 PM Alert description: Cluster resource 'Cluster IP Address' of type 'IP Address' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Running a Test-ReplicationHealth returns this:
PSComputerName : vexch002.domain.localRunspaceId : b89a5678-dc6e-44bb-8e5b-9438e2bedaa6
PSShowComputerName : False
Server : VEXCH002
Check : QuorumGroup
CheckDescription : Checks that the quorum and witness for the database availability group is healthy.
Result : *FAILED*
Error : Quorum resource 'Cluster Group' is not online on server 'vexch001'. Database availability group
'Exchange2013DAG' might not be reachable or may have lost redundancy. Error:
Cluster IP Address: Failed
Cluster Name: Offline
is offline. Please verify that the Cluster service is running on the server.
Identity :
IsValid : True
ObjectState : New
Again, the DAG appears to be functioning as it should. I've tried researching the error and have attempted a couple things such as manually bringing the cluster group online, which actually caused a failover and didn't seem to help.
Any help is much appreciated! Things seem to be working but I don't feel comfortable moving forward with our migration with these kind of errors.