A. Failover using GUI / SQL Management Studio
1. Capture always on before Failover
2. Execute
3. Cafture Always on after failover
B. Failover using T SQL/ Query
run commmand failover on standby/secondary
To do a manual failover, you may execute the code below:
USE master;
GO
ALTER AVAILABILITY GROUP 'lab_ag' FAILOVER
GO
Alternatively, to force the failover with possible data loss, based on your checking for data loss from step 1, you can execute the following code:
USE master;
GO
ALTER AVAILABILITY GROUP 'lab_ag' FORCE_FAILOVER_ALLOW_DATA_LOSS
GO
C. Log Failover 1 Change Primary SQL01 to SQL02
1. from sql01 (Original Primary)
2021-10-07 14:19:46.52 spid53 The state of the local availability replica in availability group 'lab_ag' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:20:29.82 spid55 AlwaysOn: The local replica of availability group 'lab_ag' is preparing to transition to the primary 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.
2021-10-07 14:20:29.83 spid55 The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:20:31.03 Server The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:20:34.21 spid55 AlwaysOn: The local replica of availability group 'lab_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.
2021-10-07 14:20:34.21 spid55 The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:20:34.26 spid26s The availability group database "teguhth" 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.
2021-10-07 14:20:36.10 spid26s Nonqualified transactions are being rolled back in database teguhth for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
2021-10-07 14:20:36.28 spid55 AlwaysOn: The local replica of availability group 'lab_ag' is preparing to transition to the primary 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.
2021-10-07 14:20:36.29 spid55 The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:20:36.34 Server The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:20:36.34 spid26s The availability group database "teguhth" is changing roles from "RESOLVING" to "PRIMARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.
2021-10-07 14:20:36.34 spid26s Nonqualified transactions are being rolled back in database teguhth for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
2021-10-07 14:25:56.64 Server The Service Broker endpoint is in disabled or stopped state.
2021-10-07 14:25:56.65 Server Started listening on virtual network name 'lab_list'. No user action is required.
2021-10-07 14:26:06.67 Logon Database Mirroring login attempt by user 'SQL01\Administrator.' failed with error: 'Connection handshake failed. The login 'SQL01\Administrator' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: 10.10.10.4]
.........................
2021-10-07 14:26:15.22 Backup Database backed up. Database: teguhth, creation date(time): 2021/10/06(19:13:06), pages dumped: 298, first LSN: 31:194:37, last LSN: 31:212:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\10.10.10.3\tmp\teguhth.bak'}). This is an informational message only. No user action is required.
.........................
2021-10-07 14:37:15.55 spid63 AlwaysOn: The local replica of availability group 'lab_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.
2021-10-07 14:37:15.56 spid63 The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:37:15.58 spid27s The availability group database "teguhth" 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.
2021-10-07 14:37:15.89 spid27s Nonqualified transactions are being rolled back in database teguhth for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
2021-10-07 14:37:15.90 Server Stopped listening on virtual network name 'lab_list'. No user action is required.
2021-10-07 14:37:24.36 Logon Database Mirroring login attempt by user 'SQL01\Administrator.' failed with error: 'Connection handshake failed. The login 'SQL01\Administrator' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: 10.10.10.4]
2021-10-07 14:37:46.11 spid30s The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:37:52.29 spid28s The availability group database "teguhth" is changing roles from "RESOLVING" to "SECONDARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.
2021-10-07 14:37:52.30 spid28s Nonqualified transactions are being rolled back in database teguhth for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
2021-10-07 14:37:53.32 spid28s AlwaysOn Availability Groups connection with primary database terminated for secondary database 'teguhth' on the availability replica with Replica ID: {6715fd76-2094-4380-989f-c8ecbaea6350}. This is an informational message only. No user action is required.
2021-10-07 14:37:56.39 spid35s Starting up database 'teguhth'.
2021-10-07 14:37:59.29 spid28s A connection timeout has occurred while attempting to establish a connection to availability replica 'SQL02' with id [6715FD76-2094-4380-989F-C8ECBAEA6350]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.
2021-10-07 14:38:23.78 spid35s 1 transactions rolled forward in database 'teguhth' (5:0). This is an informational message only. No user action is required.
2021-10-07 14:38:24.18 spid35s Recovery completed for database teguhth (database ID 5) in 27 second(s) (analysis 23 ms, redo 33 ms, undo 0 ms.) This is an informational message only. No user action is required.
2. from sql02 (Original SECONDARY)
2021-10-07 14:23:54.55 spid55 The state of the local availability replica in availability group 'lab_ag' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:23:55.35 spid35s The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:24:07.82 spid38s A connection timeout has occurred while attempting to establish a connection to availability replica 'SQL01' with id [53F37BA3-4AA7-4E40-B174-EB44F804F62F]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.
2021-10-07 14:24:16.96 spid55 Starting up database 'teguhth'.
2021-10-07 14:24:17.26 spid55 The database 'teguhth' is marked RESTORING and is in a state that does not allow recovery to be run.
2021-10-07 14:24:17.50 Backup Database was restored: Database: teguhth, creation date(time): 2021/10/06(19:13:06), first LSN: 31:194:37, last LSN: 31:212:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\10.10.10.3\tmp\teguhth.bak'}). Informational message. No user action required.
2021-10-07 14:24:23.74 Backup Log was restored. Database: teguhth, creation date(time): 2021/10/06(19:13:06), first LSN: 31:135:1, last LSN: 31:212:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\10.10.10.3\tmp\teguhth.trn'}). This is an informational message. No user action is required.
2021-10-07 14:35:05.65 spid56 The state of the local availability replica in availability group 'lab_ag' has changed from 'SECONDARY_NORMAL' to 'RESOLVING_PENDING_FAILOVER'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:35:32.10 spid58 ALTER DB teguhth with AGNAME:lab_ag
2021-10-07 14:35:32.13 spid58 ALTER DB param option: SET
2021-10-07 14:35:43.35 spid61 AlwaysOn: The local replica of availability group 'lab_ag' is preparing to transition to the primary 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.
2021-10-07 14:35:43.62 spid61 The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_PENDING_FAILOVER' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:35:43.74 spid61 The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:35:43.93 Server The Service Broker endpoint is in disabled or stopped state.
2021-10-07 14:35:43.94 Server Started listening on virtual network name 'lab_list'. No user action is required.
2021-10-07 14:35:43.96 Server The Service Broker endpoint is in disabled or stopped state.
2021-10-07 14:35:45.32 spid59 ALTER DB teguhth with AGNAME:lab_ag
2021-10-07 14:35:45.32 spid59 ALTER DB param option: SET
2021-10-07 14:35:49.44 Server The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:35:49.48 Server The Service Broker endpoint is in disabled or stopped state.
2021-10-07 14:35:59.13 Logon Database Mirroring login attempt by user 'SQL02\Administrator.' failed with error: 'Connection handshake failed. The login 'SQL02\Administrator' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: 10.10.10.3]
2021-10-07 14:44:23.36 Server AlwaysOn Availability Groups: Local Windows Server Failover Clustering node is no longer online. This is an informational message only. No user action is required.
2021-10-07 14:44:27.31 Server Error: 19407, Severity: 16, State: 1.
2021-10-07 14:44:27.31 Server The lease between availability group 'lab_ag' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
2021-10-07 14:44:33.07 Server AlwaysOn: The local replica of availability group 'lab_ag' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required.
2021-10-07 14:44:33.12 Server The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:44:38.03 spid35s Error: 41005, Severity: 16, State: 2.
2021-10-07 14:44:38.03 spid35s Failed to obtain the Windows Server Failover Clustering (WSFC) resource handle for cluster resource with name or ID '5d6d37f1-9a56-4494-b793-caca88d3ba52' (Error code 1722). The WSFC service may not be running or may not be accessible in its current state, or the specified cluster resource name or ID is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
2021-10-07 14:44:41.55 spid35s Error: 41144, Severity: 16, State: 1.
2021-10-07 14:44:41.55 spid35s The local availability replica of availability group 'lab_ag' is in a failed state. The replica failed to read or update the persisted configuration data (SQL Server error: 41005). To recover from this failure, either restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.
2021-10-07 14:44:46.56 Server Stopped listening on virtual network name 'lab_list'. No user action is required.
2021-10-07 14:44:46.12 spid35s AlwaysOn: The local replica of availability group 'lab_ag' is restarting, because it failed to read the persisted configuration. This is an informational message only. No user action is required.
2021-10-07 14:44:49.11 spid39s AlwaysOn: The availability replica manager is going offline because the local Windows Server Failover Clustering (WSFC) node has lost quorum. This is an informational message only. No user action is required.
2021-10-07 14:44:51.82 spid35s Error: 41005, Severity: 16, State: 2.
2021-10-07 14:44:51.82 spid35s Failed to obtain the Windows Server Failover Clustering (WSFC) resource handle for cluster resource with name or ID '5d6d37f1-9a56-4494-b793-caca88d3ba52' (Error code 1722). The WSFC service may not be running or may not be accessible in its current state, or the specified cluster resource name or ID is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
2021-10-07 14:44:51.82 spid35s Error: 41144, Severity: 16, State: 1.
2021-10-07 14:44:51.82 spid35s The local availability replica of availability group 'lab_ag' is in a failed state. The replica failed to read or update the persisted configuration data (SQL Server error: 41005). To recover from this failure, either restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.
2021-10-07 14:44:51.83 spid35s AlwaysOn: The local replica of availability group 'lab_ag' is restarting, because it failed to read the persisted configuration. This is an informational message only. No user action is required.
2021-10-07 14:44:52.94 spid39s AlwaysOn: The local replica of availability group 'lab_ag' is stopping. This is an informational message only. No user action is required.
2021-10-07 14:44:58.07 spid39s AlwaysOn: The availability replica manager is starting. This is an informational message only. No user action is required.
2021-10-07 14:44:58.07 spid39s AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user action is required.
2021-10-07 14:46:18.54 Logon Database Mirroring login attempt by user 'SQL02\Administrator.' failed with error: 'Connection handshake failed. The login 'SQL02\Administrator' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: 10.10.10.3]
2021-10-07 14:46:22.71 spid39s AlwaysOn Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
2021-10-07 14:46:22.71 spid39s AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational message only. No user action is required.
2021-10-07 14:46:22.71 spid39s AlwaysOn Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
2021-10-07 14:46:22.71 spid39s AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering node to come online. This is an informational message only. No user action is required.
2021-10-07 14:47:51.20 spid39s AlwaysOn Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
2021-10-07 14:47:56.93 spid39s AlwaysOn: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2021-10-07 14:47:58.17 spid39s AlwaysOn: The local replica of availability group 'lab_ag' is starting. This is an informational message only. No user action is required.
2021-10-07 14:48:00.59 spid39s The state of the local availability replica in availability group 'lab_ag' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:48:31.02 spid61 AlwaysOn: The local replica of availability group 'lab_ag' is preparing to transition to the primary 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.
2021-10-07 14:48:31.13 spid61 The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:48:31.13 Server The Service Broker endpoint is in disabled or stopped state.
2021-10-07 14:48:31.14 Server Started listening on virtual network name 'lab_list'. No user action is required.
2021-10-07 14:48:31.22 Server The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
D. Failover 2 Change Primary from SQL02 to SQL01
1. from sql02 (New Primary)
2021-10-07 15:11:21.12 spid69 AlwaysOn: The local replica of availability group 'lab_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.
2021-10-07 15:11:21.33 spid69 The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 15:11:21.33 Server Stopped listening on virtual network name 'lab_list'. No user action is required.
2021-10-07 15:11:38.68 Logon Database Mirroring login attempt by user 'SQL02\Administrator.' failed with error: 'Connection handshake failed. The login 'SQL02\Administrator' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: 10.10.10.3]
2021-10-07 15:11:53.97 spid30s The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 15:12:05.10 spid35s A connection timeout has occurred while attempting to establish a connection to availability replica 'SQL01' with id [53F37BA3-4AA7-4E40-B174-EB44F804F62F]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.
2. from sql01 (New secondary)
2021-10-07 14:43:12.02 spid30s AlwaysOn: The local replica of availability group 'lab_ag' is going offline because the corresponding resource in the Windows Server Failover Clustering (WSFC) cluster is no longer online. This is an informational message only. No user action is required.
2021-10-07 14:43:12.33 spid30s The state of the local availability replica in availability group 'lab_ag' has changed from 'SECONDARY_NORMAL' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:43:12.34 spid28s AlwaysOn Availability Groups connection with primary database terminated for secondary database 'teguhth' on the availability replica with Replica ID: {6715fd76-2094-4380-989f-c8ecbaea6350}. This is an informational message only. No user action is required.
2021-10-07 14:43:12.45 spid37s The availability group database "teguhth" is changing roles from "SECONDARY" 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.
2021-10-07 14:43:12.45 spid37s Nonqualified transactions are being rolled back in database teguhth for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
2021-10-07 14:44:44.56 spid55 AlwaysOn: The local replica of availability group 'lab_ag' is preparing to transition to the primary 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.
2021-10-07 14:44:44.62 spid55 The availability replica for availability group 'lab_ag' on this instance of SQL Server cannot become the primary replica. One or more databases are not synchronized or have not joined the availability group, or the WSFC cluster was started in Force Quorum mode. If the cluster was started in Force Quorum mode or the availability replica uses the asynchronous-commit mode, consider performing a forced manual failover (with possible data loss). Otherwise, once all local secondary databases are joined and synchronized, you can perform a planned manual failover to this secondary replica (without data loss). For more information, see SQL Server Books Online.
2021-10-07 14:44:58.07 spid55 AlwaysOn: The local replica of availability group 'lab_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.
2021-10-07 14:46:26.36 spid30s The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 14:46:26.85 spid26s The availability group database "teguhth" is changing roles from "RESOLVING" to "SECONDARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.
2021-10-07 14:46:26.85 spid26s Nonqualified transactions are being rolled back in database teguhth for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
2021-10-07 14:46:26.89 spid28s Nonqualified transactions are being rolled back in database teguhth for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
2021-10-07 14:46:27.26 spid26s AlwaysOn Availability Groups connection with primary database terminated for secondary database 'teguhth' on the availability replica with Replica ID: {6715fd76-2094-4380-989f-c8ecbaea6350}. This is an informational message only. No user action is required.
2021-10-07 14:46:28.18 spid28s Starting up database 'teguhth'.
2021-10-07 14:46:39.09 spid26s A connection timeout has occurred while attempting to establish a connection to availability replica 'SQL02' with id [6715FD76-2094-4380-989F-C8ECBAEA6350]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint of the host server instance.
2021-10-07 14:47:00.28 spid28s 1 transactions rolled forward in database 'teguhth' (5:0). This is an informational message only. No user action is required.
2021-10-07 14:47:00.37 spid28s Recovery completed for database teguhth (database ID 5) in 25 second(s) (analysis 2 ms, redo 69 ms, undo 0 ms.) This is an informational message only. No user action is required.
2021-10-07 15:10:32.62 spid56 The state of the local availability replica in availability group 'lab_ag' has changed from 'SECONDARY_NORMAL' to 'RESOLVING_PENDING_FAILOVER'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 15:11:05.79 spid58 AlwaysOn: The local replica of availability group 'lab_ag' is preparing to transition to the primary 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.
2021-10-07 15:11:05.81 spid58 The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_PENDING_FAILOVER' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 15:11:06.18 spid29s AlwaysOn Availability Groups connection with primary database terminated for secondary database 'teguhth' on the availability replica with Replica ID: {6715fd76-2094-4380-989f-c8ecbaea6350}. This is an informational message only. No user action is required.
2021-10-07 15:11:07.42 spid58 The state of the local availability replica in availability group 'lab_ag' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 15:11:07.65 spid33s The availability group database "teguhth" is changing roles from "SECONDARY" 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.
2021-10-07 15:11:07.68 Server The Service Broker endpoint is in disabled or stopped state.
2021-10-07 15:11:07.94 Server Started listening on virtual network name 'lab_list'. No user action is required.
2021-10-07 15:11:08.29 spid33s Nonqualified transactions are being rolled back in database teguhth for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
2021-10-07 15:11:08.37 Server The Service Broker endpoint is in disabled or stopped state.
2021-10-07 15:11:10.92 Server The state of the local availability replica in availability group 'lab_ag' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
2021-10-07 15:11:10.95 spid33s The availability group database "teguhth" is changing roles from "RESOLVING" to "PRIMARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.
No comments:
Post a Comment