How to upgrade CPM using a patch
Please note: upgrading using patch does not upgrade Apache/OS
General:
1. It is recommended to deploy the patch when you have no active backup policies, DR or recovery running - as it will restart Apache and require few min downtime.
2. When using patches to upgrade N2WS instead of the AMI upgrade, be
sure that you check your current version to ensure that the patch you
are using is compatible with your current version of N2WS CPM. If the patch
is not compatible with your current version of CPM you will get a
warning similar to the example below.
3. We recommend that you read both this KB and watch this short 3 min Video Tutorial - How to upgrade N2WS using the patch method
Permissions
1. Due to the new functionality, you may need to update your permission policies. Please see the JSON templates attached to this KB: AWS Minimal Permissions, Azure Minimal Permissions
2. Update the relevant roles with the new permissions files.
Steps:
Before doing any upgrade steps, make sure that you create a snapshot of the CPM data volume and that you know how to recover1. Read all the steps before starting.
2. Download the CPM upgrade patch from the Release Notes of the latest version of CPM found here - CPM Release Notes
3. Go to General Settings, then choose "Patches".
4. Click "choose file" and browse to the patch file and open it.
5. The file name should now appear in the window, then click on "upload and install".
6. You will get a confirmation window like the one below. Click "Upload and Install" and the patch will begin installation. The confirmation window will stay up until the patch completes its install. This will usually only take a few minutes. The window will close itself when complete.
7. Once it completes and the install confirmation window closes, You will get a message that install was successful in the top right and the patch should now be listed with an install date.
Note: please wait at least a minimum of 10 minutes even if UI say successful. Then refresh the browser with "shift +F5" to clear the browser cache.
8. Click on the help link (?) in the top right and choose "about" to verify the patch was applied and CPM is now on the updated version.
9. You should see the updated version from the patch that you just applied similar to my example below.
Related Articles
Patch for cost reduction of copy to S3
Installation of the patch will reduce costs drastically for customers who are using S3 (Between 5 to 20 times less expensive than previous version) The improvements are: For copied volumes which are larger than 512GB, worker’s volume type will be sc1 ...Upgrade instructions for v3.x/4.x
This guide outlines the steps required to upgrade to N2WS Backup & Recovery version 3.x/4.x We strongly recommend that you follow every step contained within this guide to ensure version 3.x/4.x is configured correctly and no data loss occurs. ...Upgrade using AMI to v2.6.0 from earlier versions may fail with the Configuration Wizard timing out and "Could not upgrade mysql"
Upgrade using AMI to v2.6.0 from earlier versions may fail with the Configuration Wizard timing out: The following error may be printed in the "config_shell_commands.log" file: upgrade_mysql_db(:60) Could not run mysql5.6 on docker, error=409 Client ...Release notes for the latest v2.6.x CPM release
In order to upgrade to v2.6.x from any version, please use the AMI upgrade method . The upgrade instructions are in the chapter 1.3.5 "Upgrading the N2WS Server Instance" at https://n2ws.com/support/documentation/introduction-to-cpm#13 In order to ...Release notes for the latest v2.7.x CPM release
In order to upgrade to v2.7.x from any previous version, please see the instructions here: https://support.n2ws.com/portal/kb/articles/upgrade-instructions-for-v2-7-0 In order to upgrade to v2.7.x from v2.7.0 or newer only, you can use the patch file ...