Backups may fail with "CPM Server identified this backup as orphaned: marking as failed" after upgrade to v2.3.x

Backups may fail with "CPM Server identified this backup as orphaned: marking as failed” error after upgrading to 2.3.0X and logs may show the below prints:

update_request(agentapi_requests.py:<line_number>) failed calling url https://127.0.0.1:443/agentapi/update/. Exception: ('The read operation timed out',)
2018-04-04 23:27:57,020:[140387708561152] ERROR: update_request(agentapi_requests.py: <line_number>) Failed calling url https://127.0.0.1:443/agentapi/update/. Will sleep a little and try again. Retry count: 4
2018-04-04 23:28:02,028:[140387708561152] WARNING: backup_function_internal(agent.py: <line_number>) policy: <policy_name>. Failed to send update after snapshots started ,

ERROR: update_request(agentapi_requests.py:<line_number>) failed calling url https://127.0.0.1/agentapi/update/. Exception: HTTP Error 400: Bad Request, data: <h1>Bad Request (400)</h1>

If you encounter this issue, please upgrade to latest 2.X.X version

Reference defect number – N2WS-1681, fixed in v2.3.0e

Link to Release Notes and the latest patch – https://support.n2ws.com/portal/kb/articles/release-notes-for-the-latest-v2-3-x-cpm-release

Related Articles
RDS backups may fail with "CPM Server identified this backup as orphaned: marking as failed"
The problem may happen if 2 policies are using the same schedule/target RDS, And therefore are trying to backup the same RDS databases at the same time. The following errors may be logged in the Backup Log: Info - Backup is agentless, managed by CPM ...
CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors
CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors: The reason for this failure is using wrong AWS Access Key and Secret Key - maybe they belong to the wrong account.
Release notes for the latest v2.7.x CPM release
In order to upgrade to v2.7.x from any previous version, please see the instructions here: https://support.n2ws.com/portal/kb/articles/upgrade-instructions-for-v2-7-0 In order to upgrade to v2.7.x from v2.7.0 or newer only, you can use the patch file ...
Backups may fail without being retried
If a Backup policy has failed and the following conditions are met: Number of retries defined in the policy is not zero. Start time of the backup is the original scheduled start time. Retry Interval (“Wait between Retries (in minutes)”) has passed ...
Backup may fail after approximately 30 minutes
If backup fails after approximately 30 minutes, please check the Backup Log for the following prints: ERROR: check_keep_alive_delinquents(.\cpmagent\record_management.py:<line_number>) Found stuck backup of policy <policy_name>, has not responded for ...

Backups may fail with CPM Server identified this backup as orphaned marking as failed after upgrade to v2.3.x

Backups may fail with "CPM Server identified this backup as orphaned: marking as failed" after upgrade to v2.3.x

Related Articles

RDS backups may fail with "CPM Server identified this backup as orphaned: marking as failed"

CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors

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

Backups may fail without being retried

Backup may fail after approximately 30 minutes