Always On not Synchronizing

Ravinder Bahadur 1 Reputation point
2022-10-15T04:26:24.027+00:00

Hi

I have a 2 Node Always On Availability group ( newly created ) using a gMSA account for the SQL Server Engine.
I have created the endpoint and also giving the connect privilege to the gMSA account and altered the AUTHORIZATION to mapped to the gMSA account.

I create the Availability Group and added the replicas. But when I go to the secondary node and issue the command
alter database [x] set hadr availability group = [aggroup]
it fails with "connections to primary principal is not active"

We have checked all ports and other things are ok.

Last Night it worked for sometime but today morning it is back to the same behaviour

Can someone please help me resolve this issue.

Thanks & Regards
Ravi

Azure SQL Database
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Bjoern Peters 8,886 Reputation points
    2022-10-15T12:31:18.12+00:00

    Hi @Ravinder Bahadur

    If that connection is working (at least for some short time), then I would suggest that everything on SQL server side was set up correctly!

    As it seems to be an intermittent problem I would start to investigate deeper into the network part of your environment…

    How are your servers connected to each other?
    Are there any firewalls between those servers?
    Is the local firewall active?
    Are there any other network device that might drop the connection after a specific time?

    We once had an issue with a firewall between two servers that thought the connection was idle for too long and kicked it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.