We help IT Professionals succeed at work.
Get Started
Troubleshooting Question

SQL server 2017 AG failover with potential data lost

Last Modified: 2021-03-26

we are going to test the manual AG failover and  I right click on AG console and select failover I saw this:

1)  is the warning matter? it will stop me from doing manual failover?
2) what should I do in order to fix this? we do this as we want to do SQL server 2017 CU22/23 update and the first node to install will be the secondary replica, then primary one.

  but I need to make sure that the failover working well before the patch happens.
3) as from primary and secondary the replication is in Async mode, what should I do before and after the failover and fallback?

the AG daskboard is showing everything is ok .

and from the photo I am not sure why the primary instance is on 02 but 01 is hosted by 03, 03 is the secondary replica! 02 is primary replica.

any thing to check which one is hosting the primary now?

any bugs in the AG dashbard ?

any way to check failover log on when the primary instance is failovered to 03 instead of staying in 02?
Watch Question
Distinguished Expert 2020
This problem has been solved!
Unlock 2 Answers and 31 Comments.
See Answers
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE