SQL availability group and file server role answering from the same name

• bill-humphrey

  SSC Rookie

  Points: 32

  More actions

  March 26, 2025 at 8:32 pm

  #4567996

  Hello,

  I'm tasked with setting up a 2 node server cluster that will host a MS SQL availability group. I have the servers setup and the AG looks to be working well. However, there is also a requirement to hang a share off of one of the drives. I'm not crazy about this requirement, but I have to deal with it.

  Since this is a windows cluster, my understanding is that I need to add and configure the file server role and add the share there. I've done this and it's working, with one exception, which is the DNS name.

  For example, let's say these are the various names involved:

  • Cluster Name = ServerCluster
  • Availability Group = SqlAG
  • AG Listener = SqlListener
  • File Server = ServerNameFS

  Since the SQL Listener and the FS roles each need their own DNS names, I'm getting pushback from some people that the SQL instance and file share don’t answer from the same name. They want to be able to access both the SQL instance and the share from the same name, as if this was a singer server solution.

  I've been looking for a way to accommodate this request, but have come up short. The GUI management does not list "File Share" as a resource option for the AG and I haven't found a way to do this in power shell.

  Am I missing something or is this just not possible?

  • OS = Windows Server 2022 Datacenter
  • SQL = SQL 2022 Enterprise
  • All resources are on-prem

  Thanks in advance,

• Site Owners

  SSC Guru

  Points: 80342

  More actions

  March 27, 2025 at 9:10 pm

  #4568731

  Thanks for posting your issue and hopefully someone will answer soon.

  This is an automated bump to increase visibility of your question.

• deubel_m

  SSC-Addicted

  Points: 467

  More actions

  March 28, 2025 at 1:08 pm

  #4569218

  What?? 1. A File Server resource group has nothing to do on an AlwaysOn AG server. 2. The underlying wsfc is controlled by the sql server. So a failover has to be done in SSMS or by T-SQL.

  Is the file share on the same disks as the SQL server located? If so, I hope it's not a production enviroment