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

Continue reading

Syncplify.me Server! v4.0.11 released

We have just released version 4.0.11 of our Syncplify.me Server! software. This version features the following improvements:

  • Improved support for Active Directory Groups
  • Fixed few glitches in the Web Configuration Manager
  • Fixed a bug in the “Zero Configuration” setting of the HTTP/REST Configuration Wizard

As usual you can download this new release from our website.

Syncplify.me Server! v4: new Configuration Manager preview

Syncplify.me Server! version: 4.0.0+

After a lot of anticipation we are happy to share with our users the very first screenshot (preview) of the new v4 Configuration Manager dashboard. Hope you all will like it! In the picture here below you can see the dashboard for a multi-node (active-active HA) Syncplify.me Server! v4 virtual server.

v4confman

Maintenance release: Syncplify.me Server! v3.1.18.58

We have just released version 3.1.18.58 of our Syncplify.me Server!

This new maintenance release only features a “cosmetic” change: there is now a button to run the Configuration Manager directly from within the Instance Controller.

As usual you can download the latest version from our web site. Thank you!

Syncplify.me Server!: the path from v3 to v4 (teaser)

After less than a month from the release of v3, our team is already at work on v4.

While v3 has been our “back-end release” (the version that introduced a whole lot of new functional features, from speed limits to new scripting capabilities, from multiple instances to actual impersonation, and more…), v4 will be our “front-end release” and will deliver a greatly improved interface for… well… everything.

And thanks to the whole new configuration API implemented as REST web service to be consumed over a secure HTTPS channel, the GUI will also be fully cross-platform. Ever dreamed to be able to configure your Syncplify.me Server! from your iPhone or Android device? V4 will make it possible!

SMSv4onPhone

The above is not a mock-up, it is an actual screenshot taken from one of our Android phones in the lab. More to come… soon!

How-to: configure Syncplify.me Server! HA instances

Note: this article refers to Syncplify.me Server! v3.x; As of Syncplify.me Server! v4.0 support for high-availability (HA) has become even better; you can read more about v4.0 HA features here.

One of the main new features in Syncplify.me Server! v3.0 is the ability to run in high availability (HA) configurations.

A highly available configuration is a deployment in which 2 or more servers share the same storage and configuration/user database. A network balancer is then used to decide whether to operate such servers in an active/active mode (where all nodes accept incoming client connections simultaneously) or in an active/passive mode (where some nodes accept client connections, and some other nodes kick in to substitute one of the active nodes that has stopped working).

This article explains how to configure Syncplify.me Server! (with HA licenses) in order to operate in a highly available configuration. Please, read on… Continue reading

Syncplify.me Server!: why so many “ports” to configure?

Some of our users have been asking why there are so many “ports” to configure in Syncplify.me Server! and if configuring them is really necessary.

First of all, let’s say that Syncplify.me Server! is designed to work out-of-the-box, without the need for any special reconfiguration. In fact, by default, it uses the ports defined in each protocol standard (21 and 20 for FTP, 990 and 989 for FTPS, and 22 for SFTP) plus the widest possible port-range for passive FTP(S) connections.

Continue reading