May 6, 2016 at 6:44 am
I am getting the error "Availability Group is not ready for automatic failover" even though all databases are showing as synchronized..what else can I look at?
May 6, 2016 at 4:04 pm
Just a guess but is the secondary replica set to asynchronous and/or manual failover? What do you get when you run the following:
SELECT
ag.name,
r.replica_server_name,
r.availability_mode_desc,
r.failover_mode_desc
FROM
sys.availability_replicas r
INNER JOIN sys.availability_groups ag
ON r.group_id = ag.group_id
ORDER BY
ag.name,
r.replica_server_name;
Joie Andrew
"Since 1982"
May 6, 2016 at 11:16 pm
•Verify that at least one secondary replica is configured as automatic failover. If there is not a secondary replica configured as automatic failover, update the configuration of a secondary replica to be the automatic failover target with synchronous commit.
•Use the policy to verify that the data is in a synchronization state and the automatic failover target is SYNCHRONIZED, and then resolve the issue at the availability replica.
May 8, 2016 at 11:10 am
They all return SYNCHRONOUS_COMMIT
May 8, 2016 at 11:22 am
I added 2 attachments, ( I couldn't figure out how to paste them in my post)
Pic1 is from the secondary server showing the replica states...it shows the same server name for the first 2 rows
Pic2 is from the primary server showing replica states..it shows on the first row that the secondary is healthy but the state is NULL. and then it shows row3 that same server as row2 with row3 as NOT HEALTHY but it is online. Row 1 should be the secondary for this server, not row3...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply