Network Load Balancing and Application Request Routing options for high availability

Network Load Balancing (NLB) and Application Request Routing (ARR) are Microsoft features that together provide a unified high-availability and load-balancing configuration. You must install ARR and its required modules before you install SnapCenter, and then enable SnapCenter to configure ARR during installation. To use NLB and ARR in SnapCenter, you must choose the option during installation; you cannot configure this later manually.

If you are using SnapCenter in a production environment and plan to deploy the user interface over multiple SnapCenter Server hosts, you should configure SnapCenter with both ARR and NLB.

SnapCenter does not support other types of load balancing.

To better understand the NLB high-availability capabilities, see the following Microsoft documentation:
To better understand ARR, see the following Microsoft documentation:

The SnapCenter MySQL NSM repository database is installed automatically on the SnapCenter Server host. In a NLB setup, while installing SnapCenter on the second node, you join the NLB of the first node and a copy of the NSM database is created on the second node.

When you implement NLB in a SnapCenter environment, your network adapter and NLB cluster must have the same IP setting and Dynamic Host Configuration Protocol (DHCP) must be disabled on the network adapter. To configure NLB, you must have a dedicated IP address (virtual IP) that will be exposed from all NLB nodes. For example, if you select IPv4 virtual IP, all adapters on all nodes designated for NLB must support IPv4 format. The same applies for IPv6: all adapters and cluster IP must have IPv6 support. Additionally, when you add an SVM to an NLB configuration, each node in the NLB configuration must resolve to the same name or FQDN.

When SnapCenter is installed on an cluster that uses the Microsoft Distributed Transaction Coordinator (MS DTC) service, you must add a firewall exception for the service. If a firewall exception for MS DTC is not added on NLB cluster nodes, resource group creation and host removal operations fail.

Note: When you install NLB, the second node must have access to the first node. The user performing the installation on the second node must be able to access the first node installation directory.

For details about viewing NLB and ARR status in SnapCenter, and configuring secured MySQL connections for NLB configurations, see SnapCenter administration documentation.