NetWorker Module for Microsoft SQL AlwaysOn Availability Group Client Wizard Does Not Configure Listener or Cluster Name When VMs are in Azure

Summary: NMM SQL AlwaysOn Availability Group (AAG) Cluster with two nodes - Client Wizard fails to configure listener or cluster name. The dispatcher timed out. Backup also fails with a manually configured client. The SQL hosts are Vitruam machines (VMs) in Azure. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

NetWorker Module for Microsoft (NMM) SQL ALlwaysOn Availability Group (AAG) Cluster with two nodes - Azure - Client Wizard fails to configure listener or cluster name.

Wizard fails with Dispatcher timed out message displayed.
Backup also fails with manually configured client, exit code 1.

In this case, the NetWorker Server 

  • Can ping the name and IP of the SQL hosts - the nodes in AAG
  • Cannot ping - listener name or IP - destination unreachable
  • Cannot ping - cluster name or IP - stops responding

Cause

Since NetWorker server is on same subnet as the two SQL clients, networking or firewalls are not the issue. For example, all IP addresses are in the same subnet n.n.n.0.

The SQL AAG LISTENER NAME and IP are in some way LOAD BALANCED in AZURE.

VMs in Azure load balancer or balancing are unsupported.

Resolution

Supported
  • VMs in Azure - that are stand-alone hosts.
  • VMs in Azure that are cluster names, or instances
Unsupported
  • VMs in Azure load balancer or balancing are not supported.
Article Properties
Article Number: 000218283
Article Type: Solution
Last Modified: 13 Oct 2023
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.