"The system identified issues and will stop backing up" error during an upgrade
Customers may receive the following error during a CPM upgrade:
The system identified issues and will stop backing up. This could be due to a downgrade of an existing server or expiration of license.
CPM Server is in recovery mode and will not perform backup
If the problem doesnt disappear after refreshing the CPM GUI 15 minutes later, this problem is usually caused by one of the following reasons:
1) CPM Server not having the required internet access.
You may see the following error in the CPM Server logs:
ERROR: directory_service_settings(.\cpmserver\cpm\utils.py:582) Failed getting CPM public host name. Exception: HTTP Error 404: Not Found
2) Not following the upgrade instructions in the "2.2.4 Terminating the Old Instance and Launching the New Instance" in our User Guide at https://docs.n2ws.com/user-guide/2-configuring-n2ws#id-2.2-upgrading-n2ws
The old instance likely wasn't terminated before launching the new one.
Please terminate the old CPM instance and wait until it is in terminated state, then click on the link "perform failover" at the bottom of the console page.
If it succeeds you will be asked to reboot the instance.
If it does not, please terminate all CPM instances, and then launch and configure a fresh one.
The system identified issues and will stop backing up. This could be due to a downgrade of an existing server or expiration of license.
CPM Server is in recovery mode and will not perform backup
If the problem doesnt disappear after refreshing the CPM GUI 15 minutes later, this problem is usually caused by one of the following reasons:
1) CPM Server not having the required internet access.
You may see the following error in the CPM Server logs:
ERROR: directory_service_settings(.\cpmserver\cpm\utils.py:582) Failed getting CPM public host name. Exception: HTTP Error 404: Not Found
ERROR: directory_service_settings(.\cpmserver\cpm\utils.py:591) Failed also getting CPM public IP. Exception: HTTP Error 404: Not
Please see this KB: https://support.n2ws.com/portal/kb/articles/internet-access-required-for-cpm-operations2) Not following the upgrade instructions in the "2.2.4 Terminating the Old Instance and Launching the New Instance" in our User Guide at https://docs.n2ws.com/user-guide/2-configuring-n2ws#id-2.2-upgrading-n2ws
The old instance likely wasn't terminated before launching the new one.
Please terminate the old CPM instance and wait until it is in terminated state, then click on the link "perform failover" at the bottom of the console page.
If it succeeds you will be asked to reboot the instance.
If it does not, please terminate all CPM instances, and then launch and configure a fresh one.
Related Articles
CPM stops working with the "Lost connection to license server" error
Background: When running CPM "Free Trial & BYOL Edition", It needs to connect to our license server and you may experience the below error: The system identified issues and will stop backing up. This could be due to a downgrade of an existing server ...How to upgrade an N2WS server from Ubuntu 22.04 to Ubuntu Pro
Before starting, make sure you know how to redeploy the server in case of issues during OS upgrade. In addition, Linux knowledge is Required. There are additional costs charged by AWS when using Ubuntu Pro. Warning: Do not cut and paste commands out ..."Cannot attach volume 'vol-xxxx' with Marketplace codes" error may be displayed during CPM upgrade
The following error message may be displayed when trying to upgrade the CPM instance using a new AMI: Could not attach volume vol-1234567890abcdef to instance i-abcdef0123456789. Reason: Cannot attach volume 'vol-1234567890abcdef' with Marketplace ...Upgrade fails with error "Could not mount the new volume, returned: 8192"
If you get this error message during an upgrade, it is very likely that the filesystem is corrupted on the CPMData Volume. Please perform these steps: 1) Connect to N2WS EC2 instance where the upgrade failed using user "cpmuser" and your Key 2) ...Error Message "Only 1 instances of CPM Enterprise Edition are allowed to perform backup in one account." when performing upgrade or installation of CPM server.
Symptom: When upgrading or installing your CPM server by installing a new instance, you could get the following error: Only 1 instances of CPM Enterprise Edition are allowed to perform backup in one account. the following instances belong to this ...