About SoftNAS SNAPReplicate™ and SNAP HATM

Setting up SNAPReplicate™ provides replication of data between SoftNAS Cloud® instances for greater redundancy. SNAP HATM, on the other hand, adds an additional layer of protection by providing load balancing between SoftNAS Cloud® instances.

For in-depth information on SoftNAS High Availability functions, consult the SoftNAS High Availability Guide.


The following are required for a successful SNAPReplicate™ and SNAP HATM setup.

If setting up SNAPReplicate™ using Elastic IP addresses:

If setting up SNAPReplicate™ using Virtual IP addresses:

Launching SoftNAS Cloud® Platforms

Setting Up For SnapReplicate™

The following is required for a standard SoftNAS SNAPReplicate™ and SNAP HATM implementation:

If setting up SNAPReplicate™ using Elastic IP addresses:

If setting up SNAPReplicate™ using Virtual IP addresses:

Configuring StorageCenter

Once the StorageCenter interface has been accessed, set up the Disk DevicesStorage Pools, and Volumes that will be required for HA.

Note: When setting up storage pools for replication, they have to have the same name. Otherwise, replication will not work properly. Also, create a volume on the source-side node.

Note: For any high-availability solution involving the transition and synchronization of data between two nodes, there is some risk of limited data-loss at the moment of failure. This potential loss is mitigated by caching and synchronization options made available by the underlying system in use, or added by the vendor. SoftNAS' implementation of ZFS is no exception to this general rule. ZFS offers inherent options to either prevent data loss or improve performance with increased risk. If using the default settings upon creation of your pools and volumes, SoftNAS' implementation balances the concerns of data loss and performance. If data retention is your primary concern, we recommend changing the Sync mode setting when creating your pools to 'always'. For more information about sync mode settings and the options available, see Working with Storage Pools.

Note: When selecting storage for replication, remember that for throughput to be as consistent and reliable as possible, a like to like storage configuration is optimal. Replicating data from a high performance EBS storage volume to a lesser performance object storage volume, for example, can create bottlenecks that can lead to potential data loss.