Hi All,
I have SQL server 2016 and windows serv er 2016
I created availability group between to two primary and secondary replica
the primary and secondary replica are at two different subnet
I created listener IP with two IP. one IP for every subnet.
I succeeded to created to availability group but failed to failover between nodes
the attached images display the errors.
the following error from cluster event (failover cluster manager)
Cluster resource 'R@W_Cloudcare-AG_10.193.100.28' of type 'IP Address' in clustered role 'R@W_Cloudcare-AG' 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.
No matching network interface found for resource 'R@W_Cloudcare-AG_10.193.100.28' IP address '10.193.100.28' (return code was '5035'). If your cluster nodes span different subnets, this may be normal.
and errors from primary and secondary replica
2017-05-09 13:33:05.22 spid53 Always On: The local replica of availability group 'R@W_Cloudcare-AG' is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC)
cluster. This is an informational message only. No user action is required.
2017-05-09 13:33:05.22 spid53 The state of the local availability replica in availability group 'R@W_Cloudcare-AG' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the availability group
is going offline. The replica is going offline because the associated availability group has been deleted, or the user has taken the associated availability group offline in Windows Server Failover Clustering (WSFC) management console, or the availability
group is failing over to another SQL Server instance. For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
2017-05-09 13:33:05.22 Server The availability group 'R@W_Cloudcare-AG' is being asked to stop the lease renewal because the availability group is going offline. This is an informational message only. No user action is required.
2017-05-09 13:33:05.22 spid67s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: C244F818-AF21-4088-9D70-40CC3FB72465:4
2017-05-09 13:33:05.22 spid68s Always On Availability Groups connection with secondary database terminated for primary database 'R@W_Cloudcare' on the availability replica 'DBSERVER' with Replica ID: {c244f818-af21-4088-9d70-40cc3fb72465}.
This is an informational message only. No user action is required.
2017-05-09 13:33:05.22 Server The Service Broker endpoint is in disabled or stopped state.
2017-05-09 13:33:05.22 spid46s The availability group database "R@W_Cloudcare" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role
synchronization. This is an informational message only. No user action is required.
2017-05-09 13:33:05.22 Server Stopped listening on virtual network name 'RAW_Cloudcare'. No user action is required.
2017-05-09 13:33:05.22 spid46s State information for database 'R@W_Cloudcare' - Hardened Lsn: '(2516:230:1)' Commit LSN: '(2516:228:2)' Commit Time: 'May 9 2017 1:13PM'
2017-05-09 13:33:05.22 spid45s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: C244F818-AF21-4088-9D70-40CC3FB72465:4
2017-05-09 13:33:05.22 spid46s Nonqualified transactions are being rolled back in database R@W_Cloudcare for an Always On Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No
user action is required.
2017-05-09 13:30:52.06 spid36s [INFO] HkHostDbCtxt::Initialize(): Database ID: [5] 'R@W_Cloudcare'. XTP Engine version is 0.0.
2017-05-09 13:30:52.18 spid35s A connection for availability group 'KSH_Cloudcare-AG' from availability replica 'DBSERVER' with id [E3872794-81FD-45B4-8D0E-CC2F93702642] to 'KSHQ-DB' with id [8D4C6153-E437-4401-A426-5C8526A3449C]
has been successfully established. This is an informational message only. No user action is required.
2017-05-09 13:30:52.19 spid35s A connection for availability group 'R@W_Cloudcare-AG' from availability replica 'DBSERVER' with id [C244F818-AF21-4088-9D70-40CC3FB72465] to 'KSHQ-DB' with id [46CFEC67-0B12-4812-9157-BDB3C471D245]
has been successfully established. This is an informational message only. No user action is required.
2017-05-09 13:30:52.50 spid36s [INFO] HkHostDbCtxt::Initialize(): Database ID: [5] 'R@W_Cloudcare'. XTP Engine version is 0.0.
2017-05-09 13:30:52.52 spid36s Always On Availability Groups connection with primary database established for secondary database 'R@W_Cloudcare' on the availability replica 'KSHQ-DB' with Replica ID: {46cfec67-0b12-4812-9157-bdb3c471d245}.
This is an informational message only. No user action is required.
2017-05-09 13:30:52.54 spid36s The recovery LSN (2516:230:1) was identified for the database with ID 5. This is an informational message only. No user action is required.
2017-05-09 13:30:52.54 spid36s 2 transactions rolled forward in database 'R@W_Cloudcare' (5:0). This is an informational message only. No user action is required.
2017-05-09 13:30:54.58 spid35s Always On Availability Groups connection with primary database established for secondary database 'R@W_Cloudcare' on the availability replica 'KSHQ-DB' with Replica ID: {46cfec67-0b12-4812-9157-bdb3c471d245}.
This is an informational message only. No user action is required.
2017-05-09 13:30:56.60 spid35s The recovery LSN (2516:230:1) was identified for the database with ID 5. This is an informational message only. No user action is required.
2017-05-09 13:30:56.74 spid35s Always On Availability Groups connection with primary database established for secondary database 'R@W_Cloudcare' on the availability replica 'KSHQ-DB' with Replica ID: {46cfec67-0b12-4812-9157-bdb3c471d245}.
This is an informational message only. No user action is required.
2017-05-09 13:30:56.76 spid35s The recovery LSN (2516:230:1) was identified for the database with ID 5. This is an informational message only. No user action is required.
2017-05-09 13:33:00.70 spid84 The state of the local availability replica in availability group 'R@W_Cloudcare-AG' has changed from 'SECONDARY_NORMAL' to 'RESOLVING_PENDING_FAILOVER'. The state changed because of a user initiated
failover. For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
2017-05-09 13:33:10.64 spid36s A connection timeout has occurred on a previously established connection to availability replica 'KSHQ-DB' with id [46CFEC67-0B12-4812-9157-BDB3C471D245]. Either a networking or a firewall issue exists
or the availability replica has transitioned to the resolving role.
2017-05-09 13:33:10.64 spid36s Always On Availability Groups connection with primary database terminated for secondary database 'R@W_Cloudcare' on the availability replica 'KSHQ-DB' with Replica ID: {46cfec67-0b12-4812-9157-bdb3c471d245}.
This is an informational message only. No user action is required.
plz help.