EditShare System Upgrade Paths

Before upgrading an EditShare system, confirm three things: The upgrade path from your current version, that your hardware can run the target release, and how much downtime to plan. 

Upgrade paths

How you upgrade depends on the version you're running now. You can confirm the current version at the bottom of the master server's EditShare home page.

You can only install releases that came out before your support end date. To check that date, go to EFS Control > System > License > "Support and Updates until".

If the updater says your support has expired but your contract is current, contact support with your serial number(s) or dongle ID(s) so they can verify the contract and issue a new license if appropriate

Is my hardware eligible?

The 2025.1.0 release implemented some hardware requirements which didn't exist on previous releases.  If you're not running 2025.1.0 or later, check your hardware before downloading anything. One system in the cluster which doesn't meet hardware requirements will result in the entire cluster being unable to upgrade. Pay particular attention to non-SSD boot drives or LSI/3ware RAID cards.

If your system is older, or you're not sure, send support the following before you upgrade:

• Model and capacity (for example, EFS 200 96TB)
• Serial number and dongle ID for each server
• Current software version
• A cluster-wide diagnostics file 

Planning downtime

Plan a maintenance window for any upgrade. Each server restarts as it's upgraded, so connected workstations lose access while that server is down.

• Single server: all users are offline for the whole upgrade. Schedule it outside production hours.
• HA and multi-server clusters: the upgrader works through the servers one at a time. On larger XOR-configured clusters, turn on the option to wait for EFS chunk replication before each storage server upgrades. That will avoid downtime when upgrading storage nodes but may considerably longer.
• Larger jumps and older hardware takes longer Underlying OS upgrades always take longest

After the server upgrade, check that workstations run a compatible EditShare Connect version. 

Offline upgrades

Use the offline updater for systems without internet access, when the online updater says no updates are available or for systems which can't reach artifacts.editshare.com.

1. Go to updates.editshare.com and sign in with your my.editshare.com account.
2. Find your target release and select Downloads. The offline updater (.esu file) is at the bottom of the page.
3. Check that the file's MD5 or SHA checksum matches the one listed.
4. In EFS Control, open the Upgrader Tool, choose the offline updater option, select the .esu file and select Start Upgrade.

Servers with no internet access fail the automatic update check. This shows as a warning in the daily status report.

Before you start

• Run a health report: on the server's home page, go to Status > Server Status, sign in, select every box and submit or review that morning's Daily Status Report email.  Resolve any offline or missing drives, offline nodes, broken OS drive mirrors or other critical errors first.
• Make sure every server in the cluster is booted and working.
• In EFS Status, check the Info page shows no unavailable regular files.
• If you run FLOW, check Flow Control > Systems for red lights or crashed services.
• Check the License End Date is later than the release you're planning to install.
• Confirm your hardware is eligible (see above).
• Plan the maintenance window and tell users.

For more details on the EFS Control System Upgrade, see this article.

Post upgrade, you can open the "Previous Upgrades" tab in EFS Control > System > Upgrades and select "Show Detail"s to see the result for each server.

Contact support before you start if you're upgrading from earlier than 2024.2 and are unsure of the age or specifications of your hardware.