Syncplify.me Server! v4: simplicity and power

Syncplify.me Server! version: 4.0.0+

Designing software for a large customer base is not an easy task. Some users want simplicity, very few and easy “clicks” to get their server up and running, no distractions, not too many things to look at, and that often sacrifices power. Other users (usually Enterprise customers) need to be able to perform complex deployments, integrated into complicated existing environments, they need to be able to configure every single tiny detail of the solution to fit into a much bigger architecture, and all that power often sacrifices simplicity.

When we designed Syncplify.me Server! v4 we have kept all of this in mind, and we have accomplished a design that “adapts” to the user’s needs and desires. In fact, v4 features simplified, wizard-driven configuration for those users who require simplicity, and yet advanced users can plan and execute their deployments down to the tiniest detail by configuring every single aspect, even when the architecture is very complicated. Continue reading

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