N2W Software

            Release notes for the latest v2.5.x CPM release

            In order to upgrade to v2.5.x from v2.4.x and earlier, please use one of the following methods:

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


            2) Patch upgrade method. Please read the following:
            - Notice! this patch may only be used to upgrade from CPM v2.3.0c/d/e or v2.4.0 to v2.5.0
            1. If running an older version of CPM, please use upgrade method 1) above.
            2. If patch is installed to an incorrect version, the CPM instance will stop functioning (error 500) and must be rebuilt using method 1) above.

            - Using this patch requires outbound internet connectivity from the CPM Server.
            • If using a proxy or limiting internet connectivity, please use the AMI upgrade method in 1) shown above.
            • Without internet connectivity patch upgrade may appear successful, however CPM Server may respond slowly and malfunction.
            • Without internet connectivity OS and applications will not be updated, leaving the system open to vulnerabilities.
            • If you have patched without internet connectivity by accident, please rerun the upgrade using the AMI upgrade method in 1) shown above.

            - No backups, DR or S3 copies should be running or scheduled to run while installing the patch
            • Please take steps such as disabling schedules to ensure policies will not try to run until the upgrade is complete.

            - Please wait 10 minutes after installing then reboot the CPM Instance from the AWS console.
            • Failure to do so will prevent the changes on OS level from being being implemented, functionality may be compromised.

            - Patch can be applied by using the "CPM patches" link at the bottom of the GUI:

            - Note it may take a few minutes for the CPM GUI to become responsive after installation.

            For both upgrade methods, please give attention to these details:
            1. Due to the new functionality, you may need to update your permission policies. Please see the JSON templates attached to this KB: https://support.n2ws.com/portal/kb/articles/what-are-the-required-minimal-aws-permissions-roles-for-cpm-operation

            2. it is now a requirement to attach an IAM role to the CPM server instance.

            3. After the latest version is installed, please manually upgrade VSS Agents by downloading the thin backup agent from the upgraded CPM server and reinstalling within the instance OS.

            Additional patches for v2.5.0:

            CPM CLI and RESTful API have been updated to v1.2:

            CPM CLI v1.2: https://support.n2ws.com/portal/kb/articles/cli-guide-and-software-download-for-cpm-v2-5-0

            Change log:

            February 28, 2019  (CRC-32 8958D061) - version 2.5.0 (Patch should only be applied to v2.3.0c/d/e or v2.4.0 and later - see note above about "error 500")

            Issues Fixed:

            N2WS-5580    Stockholm region missing after patch upgrade
            N2WS-5113      HTTP error 500 generating the unprotected resources report
            N2WS-4989    HTTP error 500 using custom DNS/IP for IDP in CPM
            N2WS-4985    Backup Monitor view slow to refresh
            N2WS-4771     CPM may try to run a S3 backup of an instance exceeding the 8TB limit
            N2WS-4762    User column not filled in S3 repositories table after adding a new user
            N2WS-4710     ERROR: task failed: std::bad_alloc Failed to upload s3 object.
            N2WS-4703    Update UI to reflect no support for Transit Gateways in Capture VPC
            N2WS-4575    Cannot utilize Idp login when domain or user name has dash/hyphen character
            N2WS-4515     AWS permissions check passes but job fails on DescribeVpcAttribute
            N2WS-4419     Missing permissions for the permissions.json file
            N2WS-4409    Instances with multiple NICs cannot be restored
            N2WS-4092    Changed "All snapshots deleted" to "moved to S3 Storage'" when S3 copies still exist.
            N2WS-4073    Script execution timeout results in agent failure
            N2WS-3889    Download of CPM logs and reports may fail due to a timeout
            N2WS-3782    Daily summary notification is 'All OK' but there is a scan error.
            N2WS-3768    Backup where no snapshots ran may be marked "partially successful"
            N2WS-3753    Removed DR account from showing in independent account resource report
            N2WS-3750    Removed "By Availability Zone" placement option during restore
            N2WS-3702    CPM unable to run powershell scripts
            N2WS-3658    Instance Restore UI doesn't show the root volume as able to be restored
            N2WS-3502    CPM may use default encryption keys during DR
            N2WS-3176     DR recovery exception: get_proxy_data ValueError: invalid literal for int() with base 10: 
            N2WS-3165     Alerts show partially successful backups as failed

            New Features:

            N2WS-4674     Enhanced S3 Copy logging
            N2WS-4610     Added feature to allow AWS keys for notifications to be updated by API
            N2WS-4580    Added new region - Stockholm
            N2WS-4307    Added ability to perform cross-region DR with 2nd GovCloud
            N2WS-4297    Added support for new AWS GovCloud (US-East)
            N2WS-4244     Improved cross-account DR to make all snapshots "incremental forever"
            N2WS-2475    Added "S3 Cleanup log" button to general settings

            Help us to make this article better
            0 0