Having prepared the environment on both SoftNAS Cloud AWS 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.
To establish the secure SnapReplicate relationship between two SoftNAS Cloud® nodes, simply follow the steps given below:
The SnapReplicate/SNAP HA page will be displayed.
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. This connection is established by providing the IP address.
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.
Note: 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, the opportunity to provide one will be presented prior to continuing SNAP HA™. Provide an email address for support reports and logs to be sent to, and click OK.
The next screen depends upon whether your storage pool has made use of MSFT disks added from within the SoftNAS UI (as explained in Adding Block Storage via the SoftNAS UI), or if you added Azure Blob Storage disks, or added your block storage disks through the Azure Portal.
If you added Azure Blob Storage or used the Azure Portal to add your disks, then you would first have to provide Azure account credentials before being prompted to enter your Virtual IP Address.
If (as directed in this guide) you added Microsoft disks using the SoftNAS UI, you will have supplied Azure credentials already. In this case, the wizard will skip ahead to the Virtual IP screen. This is because your credentials are cached in order to speed up the process.
Click Finish on the Finish HA Setup screen.
To test, shut down one of the instances. The other will become primary after a few moments. Alternatively, select Actions, and Takeover to simulate a failover.