Upgrade instructions

Upgrade instructions

This guide outlines the steps required to upgrade N2WS Backup & Recovery.
We strongly recommend that you follow every step contained within this guide to ensure is done correctly and no data loss occurs.

in addition to this article, we recommend that you watch this Video Tutorial: Upgrading N2WS AWS instance

Version specific

  1. For v2.4 --> v2.6 versions with S3, Please also read this KB or consult support. Upgrade from v2.4/2.5/2.6
  2. For v3.0.0/v3.0.0a versions, Please also read this KB and implement after upgrade.  S3 backups may be stored for X days instead of X months

Sizing consideration

  1. In 4.2 onward we changed minimum server size to t3.medium
    You can see sizing guide here: Recommended instance sizes and volume types for CPM Server instances

Permissions

Due to the new functionality, you may need to update your permission policies.
Please see the JSON templates attached to this KB:  
  1. AWS Minimal Permissions
  2. Azure Minimal Permissions  
If you have more than one AWS Account added in the N2WS console, you will have to update the IAM Policies for each of them.
Also, if you upgrade via AMI - make sure to attach the IAM role when launching the new instance.

Before starting

We recommend to keep the following info
  1. Check if you are using a proxy in the N2WS settings and write down the details
  2. Take a screen shot of the N2WS EC2 instance network settings: IP, VPC, Subnet, Security Groups and also IAM Role and Keypair name.
  3. Additionally you might want to take a screen shot of the Tags if you have more than just a few
  4. Make sure you know the username and password for the root/admin user
  5. If you are using RestAPI, check RestAPI newest guide for changes in the API's you are using
  6. If you are using LB, Best to set the timeout for at least 800 seconds
  7. Connect to N2WS Server and make sure cpmdata volume has enough free space

Read documentation

  1. Read Chapter 2 of the User Guide
  2. Watch Video Tutorial on how to upgrade
  3. Raise ticket with support for any question you might have

Start upgrade

  1. Follow the steps to upgrade in the user guide

After Upgrade

  1. If you were using Agents to perform app-consistent backups, you might have to download and install latest version of the thin backup agent on your Windows EC2 instances. latest agent can be downloaded from the N2WS server UI.
  2. If after upgrade public IP changed, the VSS agents configuration(cpmagent.cfg) will need to be updated
  3. If you were using backup scripts that utilize SSH, you may need to log in to the N2WS Server once and run the scripts manually so that the use of the private key will be approved
  4. If you are using CLI, then you will need to download new version of the CLI tool.
  5. If you are using RestAPI, you might need to update some commands post upgrade, for example updating the 'version=' if it is included in any command.

Upgrade Diagram

The following diagram shows the major steps and considerations in an N2WS upgrade.


    • Related Articles

    • How to upgrade CPM using a patch

      Please note: upgrading using patch does not upgrade Apache/OS Upgrade Diagram 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. ...

    • 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 v2.7.0

      This guide outlines the steps required to upgrade to N2WS Backup & Recovery version 2.7. We strongly recommend that you follow every step contained within this guide to ensure version 2.7 is configured correctly and no data loss occurs. Customers ...

    • N2WS-21963 - Copy to S3 fails with Failed to stop processor(s)

      Issue: Copy to S3 is failing with following error ERROR: add_error(segment_handler.py:322) copy of md table of segment 1 of volume vol-12345678, instance i-0987654321, backup 123 fail : Failed to stop processor(s): not all blocks were processed ...

    • 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 ...