High-Availability (HA) with Syncplify.me Server! v4

Syncplify.me Server! version: 4.0.17+

Version 4.x of Syncplify.me Server! introduced a remarkable amount of new features, and improved some of the existing ones greatly. The latter is the case of high availability deployments, which have been rendered much easier and a lot more powerful.

This article explains one way (not the only possible one) to install and deploy a highly available multi-node Syncplify.me Server! in your network.

First of all, let’s prepare 3 virtual machines:

  • 1 VM for the DB and HTTP/REST server
  • 2 VMs for the SFTP server nodes

All 3 of these machines will need to have private IP addresses (LAN) and no public IP address. Keep in mind, the only public IP address is the one you will configure later on your Load Balancer.

Installing the DB and HTTP/REST Server

The first step is the installation of the DB and HTTP/REST server. This one is pretty standard: just download the installer from our website and run it. After the installation of the pre-requisites and the software itself, the HTTP/REST Configuration Wizard will automatically be executed.

Make sure you choose the Advanced Setup configuration option.

The only non-obvious step is the configuration of the HTTP/REST Server Bindings. In fact the Wizard will try to identify your public IP address (if you have one) but you will need to manually change it and make sure to configure it to your VM’s LAN IP address.

For example, if your VM’s LAN IP address is, then the configuration will be as shown in the following picture:


After this, simply follow the rest of the Wizard as you would normally do in any typical installation.

Installing the two SFTP server nodes

The installation of each SFTP server node, instead, requires one extra step versus the DB/REST server VM here above.

On both VMs, please, make sure you choose the Advanced Setup configuration option, and on both of them make sure to specify the LAN IP address of the DB/REST server you have previously installed, when requested to do so, just like in the picture here below:


Now you can proceed, and when you get to the HTTP/REST Server Bindings, the Wizard will try to identify your public IP address (if you have one). On both nodes you will need to manually change it and make sure to configure it to each VM’s LAN IP address.

For the sake on this example, this could be your first SFTP node:


And this could be your second node:


Obviously all LAN IP addresses in this article are totally made up, and you will have to use/specify the ones that are configured on each one of your three VMs.

Once all of the above is done, you can log into any of the three nodes’ HTTPS Web Management Interface (ex: and start creating your multi-node Virtual Server. During the creation phase you will see all 3 nodes, but you will have to use only the 2 nodes that are meant to be SFTP servers and leave the DB server alone.

Last step: the Load Balancer

The last step is configuring your Load Balancer’s VIP (Virtual IP) public address and set it to balance the traffic between the 2 LAN IP addresses assigned to the 2 SFTP nodes. Once again, please, make sure there is no route/NAT that would make the DB server reachable from the Internet, only the 2 SFTP nodes must be reachable from the Internet.

Thank you!

Print Friendly
Bookmark the permalink.

Comments are closed