The following information will help you stay up to date with latest LiquidFiles version.
About LiquidFiles Updates
A LiquidFiles version number looks like this: v3.1.10 and makes up of:
- v3.1 — Major Release and Feature Release Change.
- 10 — Minor release — Fixes and minor (non-disruptive) changes within the Major Release.
In the v3.1.10 example, the major version is v3.1, and the minor release is .10.
What this means is that you can expect major, and potentially disruptive changes, when moving from version 3.1.x to v3.2.x and so on. And between feature releases there will be minor releases that will deal with any issues within the current major release, but will not add any new features, or change how existing features work.
For organisations that want to use n-1 as their update policy, the recommendation is then to stay one major release behind the current. So if v3.1.10 is the current release, you want to stay on v3.0.xx where xx is the latest fix release within the v3.0 major release.
Once you have updated to a feature release, the recommendation is to always install the latest fix release in that feature release.
LiquidFiles will support the current and previous major release. So if the current release is v3.1.10, any release v3.1.x and v3.0.x is supported. Fixes will typically only be released for the current release though. When a new major release is released, the one two versions back is no longer supported. So if v3.1.10 is the current release. When 3.2.0 is released, version 3.0.x is no longer supported. If you're following the n-1 update strategy, it is now time to schedule an update to v3.1.15 (or whatever is the latest v3.1.xx version) as soon as possible.
To see what's changed between releases, please see the Release Notes. The release notes will outline any major and minor changes to the system.
Getting Notified of new Releases
You can sign up to the Newsletter (at the bottom of this page). Every so often there's a newsletter update alerting of noteworthy new releases.
Performing the Update
There are three ways of updating LiquidFiles:
- Web interface: You can update by browsing to Admin → Update on your LiquidFiles system. This is the simplest way.
- Console: You can login on the console (hitting F1 on the actual console), or through ssh to the system and then type ft update.
- CD/ISO Image: You can boot from the CD/ISO image and select "Upgrade" from the boot prompt.
All methods will update the system to the same status, but there are a few things to be aware of. The web or console way of updating requires Internet access. A lot of other functions in LiquidFiles also requires Internet access but in the event that you have built a closed system with no Internet access, updating through the CD/ISO is your only option.
Upgrading on the console/ssh will give better error messages of things like connection errors. The web interface monitors the update and provide details from what the console applications are doing. But the nature of the web doesn't allow us to run a command like we do on the console through a browser. If you ever run into a problem with DNS or connection timeouts or similar, updating through the console will likely give you better error descriptions.
Updating using the Web Interface
Simply browse to Admin → Update on your LiquidFiles system and select the latest version. It will look something like this:
As you can see in this screenshot, the latest release at this time was v2.3.26. You only ever need to install the latest release. It is not safer, or provide any benefits of stepping through releases beginning with v2.3.15, v2.3.16, ...
Updating using the Console
If you login to the Console, either by hitting F1 Login or logging in with ssh, and typing ft update will look something like this:
Same here, you only ever need to install the latest release.
LiquidFiles does not provide a method for rolling back should an update not work properly. If something happens, we prefer that you open a Support Ticket and we will assist you in fixing whatever problem it is that you're having.
If the system is critical and you need to rollback quickly, please make sure that you take a VMware Snapshot (or similar for your virtual system) before beginning the update.