File Director upgrades
In this section:
Depending upon your needs there are different approaches to applying a File Director upgrade:
In-place upgrades are the most straightforward and ensure that all File Director appliances are of the same version.
The disadvantages of in-place updates is that your system will remain offline during part of the upgrade. See Apply a File Director patch for further information.
If you want to evaluate or test a major version upgrade before applying it to your production environment you may want to perform a side-by-side upgrade. This approach allows you maintain continuity and keep your existing File Director appliance(s) running, whilst creating a new set of appliances using the newer version. The approach requires additional infrastructure and resources.
To ensure that your clients continue to synchronize with configured map points after the upgrade it is vital to perform the following steps:
1.Back up your current appliance configuration (see Backup and restore).
2.Restore the configuration to your new appliance or cluster.
If you do not restore the configuration on your new installation, each client will perform full conflict resolution. Under these conditions, the client attempts to download the server copy of every file in order to recreate the local metadata. If you have a large number of files and users, this can dramatically increase the load on your network.
The 2021.1 release of File Director delivers many important changes that simplify both its infrastructure requirements and configuration.
Existing users of File Director are recommended to upgrade to the 2021.1 release by installing a new base image. This approach provides the most simple path to deployment. Where this is not possible, a 2021.1 patch is also available and can be applied.
An existing File Director appliance must be updated to 2019.3 or later the upgrade to 2021.1 is applied.
Upgrading from 2019.1 or previous
You can only directly upgrade your File Director appliance(s) to 2021.1 from version 2019.3 and above.
•If you are currently running 2019.1 or earlier, follow the steps below.
•If you are running 2019.3 or later skip the following steps and refer to Removal of SQL dependency below.
Applying the File Director 2019.3 Appliance Patch:
1.Enable maintenance mode on each node.
2.From within the File Director admin console, create a configuration snapshot.
3.When upgrading to 2019.3 the database settings will be wiped as the new schema is applied. It is vital that a configuration snapshot is downloaded before upgrading. This configuration snapshot can then be restored post-upgrade.
4.Apply the File Director 2019.3 patch.
5.Apply your configuration snapshot.
6.Validate all settings by connecting directly to the appliance.
7.Disable maintenance mode on each node.
A key feature of File Director 2021.1 is that it has no requirement for an external SQL database, the previous dependency has been removed. On upgrade, there are no additional steps required to benefit from this change, the transition is seamless with no impact to clustering or client connectivity. Following upgrade all SQL software is removed from your appliance (including the SQL driver), and the tab within the web admin user interface.
The following section applies only to VMware deployments, it does not apply to Hyper-V. The recommended virtual hardware level for VMware is version 14 or later.
The base image for File Director 2021.1 includes the VMXNET3 network adapter for virtual machines. This adapter supports a 10GB network capability. Installing the new base image will automatically update the required VM configuration file to enable the increased capacity.
If you upgrade to 2021.1 by applying the patch, you will need to manually update the network adapter from E1000 to VMXNET3 in order to take advantage of the 10GB NIC.
If you upgrade to 2021.1 by installing the patch the network adapter must be updated to take advantage of the 10GB NIC. The change can be made via the VMWare user interface or manually in the configuration file:
•After applying the patch, locate and open the VMware configuration file (.vmx)
•In the ethernet0.virtualDev field enter:
Note, in previous releases of File Director (2020.3 and earlier), the value required was
As of File Director 2020.2, by default the server will accept only TLS1.3 and TLS.1.2 secure connections. Refer to Advanced configuration help.
Upgrade to File Director from any technical preview installation is not supported.