Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4532

AG- not failing to another node

$
0
0

Hello Everyone,

  Hope everyone is safe and doing well in SQL World. 

   Like to see if anyone has came around this type of issue and has workaround. 

   I am working on SQL server 2016 and did set up MULTI SUBNET AG. Created Availability Group name 'DBA'. Fail over works fine from SSMS & T- SQL command  'ALTER AVAILABILITY GROUP DBA FAILOVER;  '

*********************

FAIL OVER PROBLEM ONLY FROM FAIL OVER CLUSTER MANAGER.

Now from Failover Cluster Manager --> ROLES when i am trying to fail over to DR node two thing happens.

1) Fail over does not happen fully. I see IP for the DR is coming back online and it doesn't stay on DR it fail back to Primary. 

2) I get below error

Error: 

Cluster resource 'DBA_xxx.xxx.xxx.xxx' of type 'IP Address' in clustered role 'DBA' 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.

************************

Also Strange thing i noticed , before Fail over I CHECK MARKED Preferred owner for DBA role is both Primary and DR . when I do FAIL OVER TO DR and it fails, AND I Check Preferred owner only PRIMARY is Check Marked & DR node is unchecked (Screen shot 2)SC1- Both node Check Marked.After Failover- DR Unchecked from Preferred Owner.  

Any thoughts and workaround would be great help. 

Thank you and be safe, Healthy & Protected. 


Thank you very much for your time and effort to answer this post. Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach Best -Ankit


Viewing all articles
Browse latest Browse all 4532

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>