The latest patch can be found at https://n2ws.com/wp-content/uploads/2018/02/2.2.0a_Upgrade_PATCH_20180218.zip  (please unzip it before using) 

Upgrading to v2.2.x using patch is supported only from versions 2.1.3x and up.

In order to upgrade from earlier versions, please

1) Upgrade to v2.1.3b first using patch available at https://support.n2ws.com/portal/kb/articles/release-notes-for-the-latest-v2-1-x-cpm-patch and then apply the v2.2.x patch available above

2) Use the upgrade instructions in chapter 1.3.5 "Upgrading the CPM Server Instance" at https://n2ws.com/support/documentation/introduction-to-cpm#13

The patch can be applied by using the "CPM patches" link at the bottom of the GUI:

Applying the same patch twice by mistake is perfectly safe.

Once the latest patch/version is installed, please upgrade the Agents too (if you are using them).

If you still have some v1.8.0 agents, please upgrade the policies as well - according to chapter 6.2.2 "Support for old 1.8.0 agents" in our User Guide 

N2WS-570 - CLI recover request may fail when "root-device-source" parameter is set to "image"

N2WS-908 - CPM may mark a successful RDS snapshot as failed

N2WS-1029 - The "Users" panel may become non-functional after upgrade to v2.2.x

N2WS-1040 - Downloading from explore session with delegate user may result in "There are no active explore sessions..."

N2WS-1054 - (AMI only) Provided OS updated against Meltdown (CVE-2017-5754) and one Spectre variant (CVE-2017-5753) Vulnerabilities

N2WS-739 – Improved the look and arrangement of the "General Settings" page

N2WS-740 - Added an option to use custom CPM DNS/IP for IDP

N2WS-767 - Added an option to select NameID format for IDP

N2WS-435 - Cross-account instance recovery with CPM CLI may not retain instance’s attached volumes

N2WS-503 - CPM may accidentally remove an instance from a policy

N2WS-404 - CPM may mark a successful RDS DR as failed

N2WS-619 - RDS cross-account snapshots may not get deleted

83ec3dd251 - Exception may occur when trying to recover an instance using CPM CLI

01cca27a55 - Cross-account and cross-region policy with instances in multiple regions may not replicate snapshots to some regions

1568e9cd0f - Cross-region replicated RDS snapshots may not get deleted during Cleanup

1c32873738 - CPM may fail to add an instance using "Scan Resources", if policy is created from a template and the "#app-aware" option is added to the "cpm backup" tag

96dea730c7 - Unexpected issues may occur when editing an account created by CPM CLI

d7f45e2233 -  Cleanup process may abort due to timeout

fac2f88e7a - VSS Shadow copies may not get deleted if remote Agent’s VSS script crashes

a858114182 - Unexpected CPM/Agent behavior due to performing VSS for two different policies on the same Agent simultaneously

N2WS-585 - Simplified initial configuration of CPM, especially for new free trials

N2WS-505 - Added instance and CPM tags to volumes of AMIs created by CPM

N2WS-568 - Proxy password is now obfuscated in UI

N2WS-662 - Reject access and secret keys belonging to an AWS root account

N2WS-612 - Added support for new regions:  Paris (France) & Ningxia (China)

ea89a118c6 - Added support for SAML-base IDP providers.

6cae32989c - Added support for new instance types: x1e.32xlarge, P3 family, C5 family, xe1 family, m5 family, H1 family.

58b86bbfc6 - Added support for new Redshift node types: dc2.large & dc2.8xlarge, added support for the Aurora db.r4 family, added support for RDS R4 and M4 families

e8772c3f31 - More data for the Snapshot View report - Added start time, account, policy and status

2d61283f34 - Added support for Windows 2016 Server Core (previously CPM Agent service failed to start on Windows 2016 Server Core)

6a50d9e6f7 - Added support for Aurora Clusters using PostGreSQL engine

e5de964f41 - CPM now adds tags to snapshots and AMIs using a single API call