Hello,
I configured a 2019 SQL Always on with 3 nodes, 1 DR node and a FSW. For whatever reason either randomly or during failover to other secondary nodes the DR IP is adding itself to DSN automatically. Why is this happening?
Hello,
I configured a 2019 SQL Always on with 3 nodes, 1 DR node and a FSW. For whatever reason either randomly or during failover to other secondary nodes the DR IP is adding itself to DSN automatically. Why is this happening?
Hi @SushmaPeddi-7734,
We have not received a response from you. Did any update for this thread?
Hi @SushmaPeddi-7734,
during failover to other secondary nodes the DR IP is adding itself to DSN automatically.
I could not fully understood this situation. Did you mean the virtual IP for the AG name flips to the DR site? Could you share us some screenshot about DR IP is added to DSN? Please mask the sensitive information for security.
If I misunderstood, please let me know.
Please check if the thread Multi-Subnet AG - DNS flips to secondary IP could give you some idea.
If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar queries.
13 people are following this question.
SSMS Object Explorer Showing Blue Question Mark for SQL Server & SQL Server Agent - SQL FCI Setup
sql 2017 avalibilty group cluster failover powershell
Some or all Cluster resources are not discovered by the OpsMgr agent
SCOM 2019 OperationManagerDB, server cluster service, asynchronous synchronous setup