Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
cloudappliance/patches [2018_02_22 10:18] – dan | cloudappliance:patches [2023_11_16 18:50] – steven | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | # How To Apply a Patch |
- | * Copy the patch file PATCH_FILE.tgz to the appliance using scp or any other tool | + | #### Last updated on Nov. 16, 2023 |
- | * ssh into the appliance as smeconfiguser | + | |
- | - su to root | + | |
- | '' | + | ===== About Access Anywhere Server Patches ===== |
- | * cd to var/ | + | |
- | '' | + | Patches are small changes that are confined to one or a few pieces of the Access Anywhere Server code. They are almost always issued for the purpose of resolving an issue that is affecting one or a small number of customers. |
- | * move the copied | + | |
- | '' | + | Nasuni seldom issues patches, preferring to combine sets of changes into service packs which we release frequently. On those occasions when we do see fit to issue a patch, |
- | * change | + | |
- | '' | + | ### How Patches are Provided |
- | * su to smestorage | + | |
- | '' | + | If a patch is appropriate then Nasuni will provide you with a link to a compressed tar file //< |
- | * cd to patches | + | |
- | '' | + | ### Prerequsites |
- | * Apply the patch | + | |
- | '' | + | * Check the applicability of the patch. Patches are only provided for specific releases. |
- | * Run any required | + | * Test first on a non-production system if you have one available. |
+ | * Patches should be applied to production systems during a service window. | ||
+ | * A backup of the server should be made during the service window and prior to applying the patch. | ||
+ | * If the database is external to the appliance then the database should also be backed up. | ||
+ | * A confidence test of the patched system should be conducted within the service window. If the confidence test exposes an issue and a rollback is required, the appliance backup should be restored. If the database is external, the database backup should be restored. | ||
- | '' | + | ### Patching Steps |
+ | |||
+ | Note that these steps should be completed for each appliance in a multi-node (HA) system. | ||
+ | |||
+ | Copy the patch file PATCH_FILE.tgz to the appliance using scp or any other tool | ||
+ | |||
+ | Login into the appliance as smeconfiguser | ||
+ | |||
+ | Become root | ||
+ | |||
+ | su - root | ||
+ | |||
+ | cd to var/www/smestorage/ | ||
+ | |||
+ | cd / | ||
+ | |||
+ | move the copied patch file to / | ||
+ | |||
+ | mv / | ||
+ | |||
+ | change the owner of the file to smestorage | ||
+ | |||
+ | chown smestorage: | ||
+ | |||
+ | su to smestorage | ||
+ | |||
+ | su - smestorage | ||
+ | |||
+ | cd to patches | ||
+ | |||
+ | cd patches | ||
+ | |||
+ | Apply the patch | ||
+ | |||
+ | ./patch -patch PATCH_FILE.tgz | ||
If you encounter any issues during these steps, please contact Support. | If you encounter any issues during these steps, please contact Support. | ||
- | ===== To Roll Back a Patch ===== | + | ### To Roll Back a Patch |
+ | |||
+ | Change to the smestorage user by first logging in as smeconfiguser and becoming root | ||
- | * su to root | + | |
+ | su - smestorage | ||
- | '' | + | cd to patches |
- | * su to smestorage | + | |
- | '' | + | |
- | * cd to patches | + | |
- | '' | + | Roll back the patch |
- | * Roll back the patch | + | |
- | '' | + | |