N2W Software

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

            ================================================================================================
            Release notes for v2.2x are here:
            https://support.n2ws.com/portal/kb/articles/release-notes-for-the-latest-v2-2-x-cpm-release
            ================================================================================================

            This procedure can also be used to upgrade from v2.0.2 - but not earlier (please see instructions for older versions further below).
            If you are upgrading from v2.0.2, you must apply this v2.0.2 patch "patch_2.0.2_required_for_2.1.0_upgrade.tar" (attached to this article at the bottom of the page) first, before applying the latest patch.
            Its extension is "*.tar" instead of "*.patch" - that's OK, there is no need to rename it.

            The latest patch for v2.1.x is the "patch_2.1.3b.patch" (attached to this article at the bottom of the page).
            The patch is cumulative and can be applied to any 2.1.x version.

            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.
            Please apply the patch when no backups/DR is running.

            ==========================================================================================================================
            If you are running version earlier than 2.0.2, please use the upgrade instructions in chapter 1.5.5 "Upgrading the CPM Server Instance"
            ==========================================================================================================================

            Once the latest patch/version is installed, please upgrade the Agents too (if you are using them) - latest Agent version is 2.1.3.
            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 at http://www.n2ws.com/images/PDF/CPMUserGuide.pdf

            Change log:

            November 3, 2017 - version 2.1.3c (AMI Only, no patch. Install via AWS Marketplace and use CPM User Guide Chapter 1.5.5 "Upgrading the CPM Server Instance")
            This version is meant to address the "debian-sys-maint" vulnerability for new installations

            August 17, 2017 (CRC 6D3629F8) - version 2.1.3b

            August 10, 2017 (CRC 6575515E) - version 2.1.3a
            If you have used this patch or installed the v2.1.3a AMI - please install the latest patch ASAP

            1b47a156e7 - Downloaded csv log's name contains log download time instead of a more informative time
            572c4d8e57 - Wrong version is displayed in SSH prompt

            August 8, 2017 (CRC A422F5EA) - version 2.1.3
            If you have used this patch, the patch from August 1st 2017 (CRC  2D2D8122) or installed the v2.1.3 AMI - please install the latest patch ASAP

            982e480909 - Remote agents should restart after local agent restart

            new features:

            aa871b39c6 - Aurora - added support for 'db.t2.small' type
            6cae32989c - Added support for new instance types: g3 family


            June 12, 2017 (CRC  2032E883) - version 2.1.2

            f887a2fb9e - Move the "delete" button to the top of the snapshots list
            24392b27f6 - Fail gracefully if the remote agent does not support VSS
            692cef9882 - "No matching KMS alias on target region" error may happen with a newly created KMS alias
            86a4b5e807 - Adding internal keepalives during the run-Snapshot stage


            new features:

            6cae32989c - Added support for new instance types: f1 family


            March 1, 2017 (CRC  6A524506) - version 2.1.1

            baa25a13ed   - Fixed display clock for backup targets and patches pages.
            d8f5a39ccc    - backup tag - don't add terminated/shutting down instances to policies
            4ca2fa2b0d   - Fixed the  redshift 'node type' field length
            9c60a5ff8f    - Additional performance improvement for large scale backups
            83bdc5961c   - Run ASAP now starts the backup immediately
            a56aa827de - Snapshot and Backup reports do not contain the managed users' data


            new features:

            6cae32989c – Added support for the new i3 instance types


            February 7, 2017 (CRC  156A3AB4)

            16a86dd6a1   - Assume role fails in agent if assuming account from another user
            dfc02fec0c    - Increasing the system-wide timeout for VSS and scripts from 300 to 900 seconds (requires the Agents to be updated to this version)
            2da742439d - Remote Agent – Disable proxy when connecting to internal addresses
            196a00ef22  - Failed backups may not be retried if schedule is limited to certain days of the week
            6676511295  - Recovery of encrypted volumes across accounts may fail
            d1074555ba - Improved LVM  volume exploring

            new features:

            baa25a13ed – Display CPM Server time in console


            January 23, 2017 (CRC  440C3E83)

            1d8ad48487   - Explore of entire volume/logical drive may not work
            d27d5fe7f3    - Single AMI backup may fail, if root device name is not equal to the mapped device name
            2694b2d820 - "Request Limit Exceeded" may fail backups
            d22412090a  - During volume recovery, instance id in 'attach to instance' column may stretch over 2 lines
            882874dd47 - Incorrect error message about reaching the edition's limit

            new features:


            ebfa7f7c48   - Add support for new region EU (London), eu-west-2
            5121742511   - 'script timeout'  is now used across the system as timeout for remote agent operations - requires the Agents to be upgraded to this version first.
            d1074555ba - File Level Restore ("Explore") now supports LVM
            19ef824a94  - Add support copying encrypted snapshots of RDS across regions
            6676511295  - implement cross account recovery of encrypted volumes (snapshots are copied as part of the recovery process)

            December 11, 2016 (CRC  E30D72D6)

            ce24d493d8 - Increase the default timeout on remote agent operation

            88db9f5175 - Wrong credentials may be used during File Level Recovery ("Explore")

            98d18ddef6 - Single AMI may be marked as orphan and deleted by mistake

            603ee18a1b - Remote agent crashes every 10 hours
            721c726d8b - Single AMI creation may fail


            new features:


            6cae32989c - Added support for new instance types: t2.xlarge, t2.2xlarge, r4 family

            3df18ef9a9 - Added support for new the region "Canada (Central)" - ca-central-1
            f4b052f82c - Added support for T2.Medium Aurora instances
            049379b03c - Added the "scan now" operation to CLI

            November 17, 2016 (CRC  99E26F8A)

            6ccf7f6779   - Adjusting API and CLI call to support new 2.1 accounts 
            fe4e1a181    - Explore - show all error messages before closing explore tab
            6a6ab919cd - Volume recovery - filter AWS special tags (don't try to add them to volume/instance)
            882dbdd315 - Reducing amount of data used by remote agent to reduce strain on the web server
            eafa452e2b - GUI Improvements: Added “num records in page” for schedules, policies, agents, freezer, accounts and users
            Added free search text will also catch schedule name and description in policies and vice versa
            Limited number of policies in schedule tab
            7d49598eb7 - Fixed assume role issue when account name contains spaces


            November 7, 2016 (CRC  97B6D8B6)

            fdea85d37a - Recover instance now catches all exception types
            b7ea470fbd - Backing up Aurora Cluster - Backup is aborted due to an internal agent error
            aa01cc8cfe  - Windows instance recovery can crash if instance launch does not succeed
            e230b8515f - DR keeps failing due to checking status too quickly
            f3e74eaf35 -  DR fails after network disconnection 

            October 30, 2016 (CRC 54234006)

            9227e37d66 - AMI is selected automatically during cross account instance recovery from the wrong account, AMI wasn't copied to the DR account
            623fe723fa   - RDS DR may fail if exceeded number of concurrent copies

            October 23, 2016 (CRC 7286957B)

            ae435e11e1    - DR fails on AMIs with ephemeral storage
            e2d2fc1278   - Fixing params in API for CLI access (userdata + others)
            82b41c2957  - Fix dr volume/rds/ami, when encryption key is from another account (alias not available)
            eb9068cfcb  - Boto3 fails to connect with proxy+IAM role (assume role to other account failed)
            83eccce5b3  - "Cpmdata" policy stops working after patch update

            new features:

            6cae32989c  - Added support for new instance types: p2.xlarge - p2.8xlarge - p2.16xlarge - m4.16xlarge
            de4d2c031f    - Added support for new Ohio region (us-east-2)
            469b0d5d96 - Allow assuming from accounts of the root user
            xyz                  - Minor changes to Explore – some cosmetic + make the search case insensitive






            -      


            Updated: 20 Jan 2019 10:26 PM
            Helpful?  
            Help us to make this article better
            0 0