SQL Server 2022 Always On Secondary Replica cannot connect to Primary

Question

Setting up an Always On Availability group: -Windows Failover Cluster -2 nodes When I set up the group, on the primary replica for that group, I see that both replicas are listed and online and identified as (Primary) or (Secondary). On the Secondary however, I see both replicas listed, but only (Secondary) is identified as such and the primary is listed with a blue question mark. server1:

  AvailGroup1 (Primary)

   Replicas

     server1 (Primary)

     server2 (Secondary)

server2:

  AvailGroup1 (Secondary)

   Replicas

      server1 <- listed with blue question mark

      server2 (Secondary)

Now, if I failover so that server2 is the primary for that group, I get: server1:

AvailabilityGroup1 (Secondary)

  Replicas
     
    server1 (Secondary)      

    server2 <- marked with blue question mark

server2:

AvailabilityGroup1 (Primary)

  Replicas
     
    server1 (Secondary)      

    server2 (Primary)

Does anyone have any idea of why this is doing this? I have verified endpoints and that communication goes both ways. Not sure what else to check. Regards, Keith Clark

Answer 1

Hi @Keith Clark,

It is normal. It's the same in my environment.

Please refer to this similar thread: https://learn.microsoft.com/en-us/answers/questions/87199/availability-replica-server-with-question-status-a

On primary replica you will see all the information.

Best regards,

Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".