Backup of cpmdata may fail after migration/upgrade with the "The volume '....' does not exist" error

• Related Articles

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

• Upgrade may fail with the "Failed labeling and mounting after 10 retries, giving up" and "Could not mount the new volume, returned: 256" errors

  Upgrade using AMI may fail with the following error in the file config_shell_commands.log: 2021-02-08 18:07:06,610: perform_shell_commands(:339)  Could not mount the new volume, returned: 256 2021-02-08 18:07:06,610: perform_shell_commands(:349)  ...

• DR may fail due to the “Volume DR Failed getting volumes info” and “RequestLimitExceeded” errors

  If DR fails with the below errors in Backup log ERROR: check_region_copy_state(.\cpmserver\cpm\dr_volume.py:<line_number>) Volume DR Failed getting volumes info in region <Region name> (policy <Policy Name>,in Backup account), Exception: ...

• Error "Account AccountName can't define the cpmdata policy, as it's not the owner of the CPM Server" may be displayed when creating the "cpmdata" policy

  Error "Account AccountName can't define the cpmdata policy, as it's not the owner of the CPM Server" may be displayed when creating the "cpmdata" policy. This means that you are trying to create the "cpmdata" policy using an account that isn't the ...

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