/
Azure Getting Started - Configuring High Availability

Azure Getting Started - Configuring High Availability

Apr 13, 2023

Configuring SnapReplicate™

Having prepared the environment on both Azure SoftNAS instances, we can now set up high availability. The first step towards high availability in SoftNAS is to establish replication. SnapReplicate™ makes this as simple as completing a quick wizard.

On your primary instance (source controller) navigate to SnapReplicate/SNAP HA.


Click the Add Replication button in the Replication Control Panel.
From the Add Replication wizard, read the Instructions and then click the Next button.
Enter the IP address of your secondary instance (Target) in the IP address text box.  This step is specifying the network path that SnapReplicate™ traffic will take.


Once done, click the Next button.

The source node must be able to connect via HTTPS to the target node (similar to how the browser user logs into StorageCenter using HTTPS). HTTPS is used to create the initial SnapReplicate configuration.

Next, several SSH sessions are established to ensure two-way communications between the nodes is possible. When connecting two Azure nodes, it is best to use the internal instance IP addresses, as traffic is routed internally by default between instances. 

If you have not yet done so, the Security Group on each instance should be configured with the internal IP addresses of the paired instance (the source instance should recognize traffic from the target instance, and the target instance should recognize traffic from the source) to ensure both HTTPS and SSH traffic between instances is recognized.

Enter the username for the secondary instance (target) in the Remote admin user ID text box.



Enter the password you set during creation for the secondary instance (target) and verify in the appropriate text boxes.


Once done, click the Next button.
Read the Finish Replication Setup instructions and click the Finish button.
The SnapReplicate relationship between the two SoftNAS controller nodes will be established. The corresponding SyncImage of the SnapReplicate will be displayed.


After data from the volumes on the source node is mirrored to the target, once per minute SnapReplicate transfers keep the target node hot with data block changes from the source volumes.


The tasks and an event log will be displayed in the Replication Control Panel section. This indicates that a SnapReplicate relationship is established and that replication should be taking place.

Configuring SNAP HA™

SnapReplicate™ establishes a replication relationship, one that can be manually triggered or scheduled, but is not automated. For true high availability in a failover situation, SNAP HA™ must be configured as well.

While still on the SnapReplicate/SNAP HA page, click the Add SNAP HA button in the Replication Control Panel.


Configuration of SnapReplicate™ is a prerequisite to setup of SNAP HA™.  If SnapReplicate™ is not configured, the Add SNAP HA™ button will be grayed out.

If you have not yet configured a notification email, you will need to provide one prior to continuing SNAP HA™.

Enter your e-mail into the Email text box.


Once done, click the OK button.
From the Add High Availability wizard, read the Instructions and then click the Next button.
Provide your Username or Service Principal into the Username/Service Principal text box.


Enter and confirm you Password into the appropriate text boxes.

Once done, click the Next button.
In the Virtual IP text box, enter an IP address that is within the same CIDR block as the instances you have created.
FOR EXAMPLE: If the IP Address for our primary instance here is 10.0.1.4 and the IP Address for our secondary instance is 10.0.2.4.  We will give the Virtual IP an address of 10.0.3.x.


Update All Subnets

This is an advanced option that can be useful if you do not have a large number of subnets.

If hundreds of subnets are in use, it is recommended to NOT select this option.

Virtual IP on same Subnet

This is an advanced option that should only be checked if using VNET peering.

  1. In the HA Num of retries text box, enter the max number of retries before your virtual machine fails over.


  2. In the Storage timeout text box, enter the max time (in seconds) that storage can be unavailable before a failover is triggered.


  3. In the Max. hoping request time (ms) text box, enter the default time for max ioping requests, to ensure that a failover is triggered more quickly in event of failure.


  4. From the HA node recovery mode section, select the behavior of the failed node during a failover. 

  1. Reboot - this is the default option, allowing for quicker recovery and re-establishment of high availability, as the failed node will reboot, and SNAP HA will be reactivated, with the original node set as secondary.

  2. Shutdown - The failed node will remain shut down. You will need to reboot the instance manually to re-establish high availability. 

  3. None (No action taken) - This option is only for debug or support use. The failed node will remain in its current state. 

Once done, click the Next button.
Read the Finish HA Setup instructions and click the Finish button.


It will display a Loading... image while HA pairing is being created.