Skip to main content
Question

DNN listener within Azure for IaaS AlwaysOn Availability Group

  • July 2, 2026
  • 2 comments
  • 11 views

Forum|alt.badge.img+1

We are looking to upgrade and migrate our Veeam database from SQL Server 2016 to 2025 from on-prem to Azure IaaS solution. Our current environment is on-prem with AlwaysOn Availability Group that uses a VNN Listener. We are looking to use the DNN listener now that we are going to be within Azure.

Does Veeam support the DNN listener within Azure for IaaS AlwaysOn Availability Group?


Also, within the connection string to use the DNN listener within the Availability Group, the connection parameter MultiSubnetFailover=True is mandatory.

Where would we set this configuration parameter within the Veeam for this connection property? 

 

 

Please advise.

2 comments

Chris.Childerhose
Forum|alt.badge.img+22

I cannot find anything on DNN when searching.  This might be a need to open a support ticket just as an inquiry to get the right answer.  Unless someone who uses this knows.


Link State
Forum|alt.badge.img+12
  • Veeam Legend
  • July 6, 2026

Hi ​@Nikks 

Check this KB2301: How to Deploy Veeam Configuration Database in SQL AlwaysOn Availability Group

Reading the referenced KB, it does not appear to provide explicit confirmation of full DNN support. What is clearly stated is that multi-subnet SQL Always On clusters are not supported for Veeam configuration databases.

Therefore, the most accurate interpretation is that the documented support is limited to supported single-subnet configurations, while no clear statement can be found regarding support for multi-subnet deployments using DNN. In other words, the KB does not validate DNN as a fully supported option in all scenarios; it only confirms support within the single-subnet architecture described.

System Requirements - Veeam Backup & Replication User Guide

 

As ​@Chris.Childerhose said, open a support ticket to get more information

Please let us know what the support team says – I’m interested. Thanks