Upgrading to v18.x from v16.10

With the release of version 18.x, ExaVault appliances can now update themselves—no manual license uploads, no patching weekends, no surprises.

This upgrade brings three major improvements every customer will benefit from:

Automatic Security Updates: Critical OS and software updates now install automatically on a schedule you control—no need to manually re-image your server or remap disks. This ensures you’re always protected against the latest vulnerabilities, including several patched since the legacy 16.10 release.

License Keys That Just Work: With version 18.x, license key management is completely hands-free. Renewals for paid and Enterprise plans are now processed automatically in the background—no more uploading keys or contacting support to stay current.

SSL Certificates—Now Fully Managed: ExaVault now supports automatic registration and renewal of SSL certificates, reducing administrative overhead and eliminating expiration-related outages. Just turn it on and let it run.

Other Notable Improvements in 18.x

• Branding Consistency: All references to our old brand names Smartfile and Veristack have been replaced with ExaVault.

• Improved Document Viewer: The old PDF/document viewer has been replaced with a higher-quality viewer. It no longer supports annotations or e-signatures—please contact us before upgrading if you rely on those features.

• Streamlined Administration: The deprecated “Django” admin panel is no longer included or supported.

• Simpler User Management: User roles are now expressed as attributes on the User object. Existing users are migrated automatically.

• 2FA Security: SMS-based 2FA now uses and requires your own Twilio credentials.

If you're still on version 16.10, upgrading to 18.x is strongly recommended to maintain a secure, supported deployment. Major OS upgrades are still required approximately every four years—but for everything else, ExaVault will now keep itself up to date.

Performing The Upgrade

This upgrade will require downtime for your current production system. You need to power down your existing installation VM long enough to copy the data to the new VM.

As part of the name change from SmartFile to ExaVault, the upgrade process to v18.x involves renaming several databases and folders on disk. This is to ensure that your appliance will completely match a fresh installation and match the documentation. This part of the upgrade is performed automatically when you start the appliance later in the process.

Firewall Changes

The new version of ExaVault changes the passive port range that is used for FTP transfers. The change was made to align with and match Files.com, our parent company. You will need to update your firewall rules to open ports 40000-49999 for FTP passive ports.

Preparation

Prior to the upgrade, please perform the following steps:

Make a backup first of the entire production VM including primary and secondary disks. While we've never seen anyone experience a failure following these upgrade instructions, taking a backup first provides a safeguard against the unforeseen interrupting a step that can't be recovered.

Save a copy of the network configuration locally. This will be needed to build a new netplan file. This configuration is likely found in the file /etc/network/interfaces

Launching The New VM Instance

Click here to download the ExaVault .ova Image for VMWare.

After obtaining the ExaVault .ova image, follow these steps to configure the VMWare Prerequisites, then continue the next step.

Configuring and Finalizing the Upgrade

Connect to the appliance using your VM console or via SSH. The VM uses a nonstandard port for SSH, so you must specify port 10022 for an SSH connection.

Execute the following commands in a shell to configure and finalize the upgrade to version 18.x. By default, you'll connect using the admin user, so we've added sudo to the commands because they require administrator access to your server.

Create the /data dir:

sudo mkdir -p /data

Remount the existing disk. Replace the device with your device name:

sudo exavaultmount -o remount --destination /data --type xfs --source /dev/sdb1

Start the application:

sudo exavaultctl -o start

Allow a few minutes for your appliance to upgrade all database names.

If anything fails to start, check the logs for errors:

sudo docker logs -n 10 -f exavault_api_1

Once the appliance is started, the exavault-admin-dashboard container should be running. Use a web browser to access the appliance manager on port 9002. Access the configuration page and save your configuration.