« Wiki Index
How To Apply a Patch to SME File Fabric Appliance v1705
Patching Best Practices
- If you want to familiarise yourself with the changes introduced by a patch prior to deploying the patch to production, install it first in a non-production environment and test it there.
- Patch your system during a service window when users are not permitted to use the system.
- During the service window and prior to patching the system, backup the appliance itself and, if the database is external, backup the database as well. (If you have a a multi-node (HA) system, it is only necessary to back up one node.)
- Confirm that the system is working correctly after applying the patch and prior to ending the service window.
- If you are unable to confirm that the patched system is working properly, contact SME Support or roll back the patch prior to ending the service window. (Roll-back instructions are provided later in this document.)
To Check Your Current Version
There are two ways to check the version of your appliance:
- Log in to the appliance through the browser as appladmin and click on the hamburger menu in the upper right of the screen. The version number will be displayed.
- SSH into the appliance VM as smeconfiguser and execute the smeversion command. The version number will be displayed.
Release notes describing the contents of version 1705 and its patches can be found here:
Note that these steps should be completed for each appliance in a multi-node (HA) system.
- Open a secure shell on the appliance as smeconfiguser:
- Become the root user:
su - root
- Use the yum command to download and install the patch:
yum update --enablerepo=sme-no-subscription sme-release sme-ff-ftp
The final lines of the output you see should be similar to this:
If you see something different or encounter any issues during these steps please contact SME Support.
Database Update is Automatic
When patching version 10 an extra step was necessary to ensure that any database changes associated with the new code were applied to the appliance's database. With version 1705 database updates are handled automatically by the patching process.
To Roll Back a Patch
- To roll back a patch it is necessary to reverse both the appliance changes made by the patch and any database changes made by the patch.
- If your database is internal to your appliance you can reverse all of the changes by restoring the appliance backup you made prior to applying the patch.
- If your database is external then you need to restore the appliance backup and restore the database backup.