Apply a File Director patch
File Director software can be updated by applying a patch, supplied by Ivanti, which can be uploaded through your appliance.
In this section:
Before applying any update to File Director you are advised to take a backup or snapshot of your virtual machine(s), your database, and the appliance configuration. See Backup and restore
We recommend appliances are forced offline via the Maintenance mode flag (or manually via the load balancer) and brought back online following the patching process. This is to stop any traffic from the load balancer.
See also Note: 2021.1 patch below.
Maintenance mode status is recommended for appliances before starting the patching process as a database schema upgrade may be required. This is performed by the first node to be upgraded. From this point on, all older nodes are blocked from communicating with the database, which causes their health monitors to fail and be marked as offline by the load balancer.
Client device session tokens (log on states) are held in appliance memory. When the cluster is patched, these are lost, which means that the clients need to reauthenticate on their next connection with the appliance (generally within 30 seconds unless notification checks are disabled). Because all this traffic will be directed at the first single updated appliance that shows as online to the load balancer, the resultant traffic could saturate this appliance and result in an unbalanced configuration.
The 2021.1 patch file applies only to File Director 2019.3 and above.
File Director 2021.1 includes a new base image and administrators are advised to deploy the new image and apply the patch only the recommended approach is not possible. Refer to 2021.1 upgrade for guidance.
Estates using VMware upgrading by applying the patch will need to manually update the VM hardware level and change to the VMXNET3 adapter to take advantage of the 10GB NIC. Refer to VM Network Adapter for further information.
Note: 2018.3 patch
Periodically, large patches are issued containing multiple component updates and upgrades to the OS. The 2018.3 patch is an example.
Before installing the 2018.3 patch be aware it will require a system reboot several times during the update process. In addition, it is essential you perform recommended backups, as in some circumstances you will need to re-import the appliance snapshot after the update process has completed.
- Refer to the Important information above.
- Log in to the File Director Admin console.
Select Home > Version.
In the Status section, details of the current patch version are displayed.
Click Choose File and navigate to a File Director patch file.
The screen updates to list the components that the patch is updating and their version numbers. Click a patch to view further details.
- Select the required patch and click Deploy Update file.
To complete the patch install, the server automatically reboots. Connected devices are unable to communicate with the server for few minutes whilst the reboot completes.
This process explains how to apply a patch to all nodes in a cluster. Note that if clustering is enabled and a patch server has been set, patches are applied via the Cluster tab.
You can apply a patch to a cluster using any nodes as long as one of the nodes in the cluster is the patch server. To make the current node the patch server, select Cluster > Status and click Promote to Patch Server.
1.Refer to the Important information above.
2.Log in to the web Admin console on any node in the cluster.
3.Select Cluster > Update.
5.Click Choose File and navigate to a File Director patch file.
The patch is displayed in the Updates section of the screen along with all patches that have been previously uploaded.
Select a patch and click Delete to remove it from the list and from the patch server.
7.Select the row in the table of the required patch and click Deploy Update.
To see the components and release notes for a patch, click the patch name.
Applying updates - additional information
•Updates are applied in parallel to all components across the cluster that are not the same version as the patch.
•Nodes may require a reboot following an update - follow the instructions displayed.
•Nodes that are offline are not updated and display with a warning icon in the Status screen. Reapply the patch when the node is online to update its components. This does not affect any nodes that have already been updated.
•The progress of the update is displayed and you are informed when the update is complete.
•Depending upon the File Director version you are upgrading from, you may be required to restore your appliance configuration from the pre-upgrade backup. See Backup and restore.
•Disable maintenance mode on each appliance and test client connections to File Director.