an attempt to failover or create availability group failed. the operation is not supported when always on availability group is running under a remote windows server failover clustering (WSFC) context. under a remote cluster context failing over or creati

Shuvajit Roy 166 Reputation points
2023-05-08T04:11:51.7866667+00:00

I cannot add the secondary DB to "Always On Basic Availability Groups". While I attempt to add the node, I get the error in the screenshot. My architecture diagram can help u understand my environment. Can anybody provide please?

Action plan taken so far:

  • Always On Basic Availability Groups does not contain WSFC. Its simple replication over to the other node, however the error contains WSFC error.
  • Checked to see if DNS and computer object is associated to WSFC. Observed, there are no such objects.

Error screenshot:

MicrosoftTeams-image

My architecture:

2023-05-08_9-57-52

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,107 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. AniyaTang-MSFT 12,341 Reputation points Microsoft Vendor
    2023-05-08T07:49:00+00:00

    Hi @Shuvajit Roy

    Based on your architecture, are you adding your domain controllers to an availability group? Depending on the requirements of the availability group, availability groups are not supported on domain controllers.

    You can review this document for prerequisites, limitations, and recommendations for AlwaysOn Availability Groups: https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability?view=sql-server-ver15.

    If this is not the issue, please provide more detailed information.

    Best regards,

    Aniya