Theme
Updating and upgrading: general rules
The process to update or upgrade your Syncplify Server! falls into one of the following scenarios. Read the one that applies to your current situation.
WARNING
Every update and upgrade requires an active maintenance and support plan. The installer warns you if the plan of your license has expired, to give you a chance to renew it first.
Updating within the same major version (for example from v8.x.y to v8.w.z)
If the major version stays the same, updating to the most recent release is straightforward: download the installer from syncplify.com/download and run it. Your virtual sites, users, VFSs and configuration are kept and upgraded automatically, so this is truly an automatic and hassle free procedure.
From version 8.4.0 the server can also update itself. Each node checks Syncplify's signed release channel once a day and shows what it found on the Updates page of the SuperAdmin UI; an update is installed on request, or automatically when the node is idle, according to the update policy you set. Either way, whether you run the installer or the server updates itself, the same sequence runs on the node: a backup of the configuration database is taken, the previous version is kept in a rollback slot, and the node is health checked afterwards. In a cluster, nodes are updated one at a time, never together. The manual explains it all in Keeping the server current.
Upgrading from v6 or v7 to v8 (standalone server)
Whether you are upgrading from v6 or from v7, the procedure is identical. Since v6, Syncplify Server! has been built on the same architectural foundation, so the upgrade process is the same from every version from v6 onward: download the v8 installer and run it. Your configuration, virtual sites, users and VFSs are preserved automatically. The step by step instructions are in Upgrading from v6 or v7 to v8 on Windows and on Linux; the rare case where the v6 or v7 database cannot be exported has its own page, Upgrading from v6 or v7 to v8 when everything else fails.
Upgrading from v6 or v7 to v8 (HA cluster)
High availability was redesigned and reimplemented from scratch in v8, so a v6 or v7 HA cluster is not upgraded in place: in place upgrades of HA clusters are strongly discouraged. The sanctioned procedure is:
- take a full configuration backup from the SuperAdmin UI of any one of the v6 or v7 nodes
- install a fresh standalone v8 node and restore that backup onto it
- add more fresh v8 nodes to it to recreate the cluster, then move your licenses over
The complete procedure is in Upgrading a v6 or v7 HA cluster to v8.
Upgrading from an older version (v4 or v5 to v8)
You can upgrade from an old v4 or v5 installation of our software. These upgrades are relatively easy, but they do require a few manual steps, and the implications deserve a thorough explanation, so they have a dedicated page: Upgrading from v4 or v5 to v8.
WARNING
You need a v8 license: your old v4 or v5 license does not work with v8. If you have an active maintenance and support plan, you can request a v8 license code for free; see Licensing and license codes.
Upgrading from v1, v2 or v3
Upgrading from any version older than v4 is not possible. Versions 1 through 3 were based on a totally different, and now discontinued, technology, so their configuration cannot be exported and therefore cannot be imported into v8.
If you are running any version between v1 and v3, your only option is to deploy a brand new v8 and configure it from scratch. Sorry about that; we had no other option.