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.
Version specific
- For v2.4 --> v2.6 versions with S3, Please also read this KB or consult support. Upgrade from v2.4/2.5/2.6
- 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
- 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:
- AWS Minimal Permissions
- 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
- Check if you are using a proxy in the N2WS settings and write down the details
- Take a screen shot of the N2WS EC2 instance network settings: IP, VPC, Subnet, Security Groups and also IAM Role and Keypair name.
- Additionally you might want to take a screen shot of the Tags if you have more than just a few
- Make sure you know the username and password for the root/admin user
- If you are using RestAPI, check RestAPI newest guide for changes in the API's you are using
- If you are using LB, Best to set the timeout for at least 800 seconds
- Connect to N2WS Server and make sure cpmdata volume has enough free space
Read documentation
- Read Chapter 2 of the User Guide
- Watch Video Tutorial on how to upgrade
- Raise ticket with support for any question you might have
Start upgrade
- Follow the steps to upgrade in the user guide
After Upgrade
- 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.
- If after upgrade public IP changed, the VSS agents configuration(cpmagent.cfg) will need to be updated
- 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
- If you are using CLI, then you will need to download new version of the CLI tool.
- 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.