Backup may fail after approximately 30 minutes

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

• DR may fail due to the "snap-0123456789abcdef failed, has status error" error

  If Cross-Region DR fails with the following error in the Backup Log: Error - Volume DR copy snapshot failed for region <Region Name>, snapshot snap-<snapshot_ID>e (status: error).” Please download the logs from CPM GUI and search for the following: ...

• Cross-account DR may fail with the "RequestLimitExceeded" error

  The Cross-Account DR may fail with the following error in the Backup Log:  Error,"Volume DR copy snapshot failed for region <Region Name>, snapshot snap-<Snapshot Number> (to DR account). Reason:       Failed adding share permission to snapshot ...

• Backup scripts may fail after upgrading to CPM 2.3.0

  If you have partially successful backups after upgrading your CPM to v2.3.x or newer, please open the backup log and search for the below: Error - Could not find script "before_<Policy Name>", will continue without backup scripts If you have found ...

• Cross-Region DR RDS backup may fail with "Copy failed due to an AWS limitation regarding default encryption key” error

  RDS DR backup of encrypted snapshots between different regions may fail with the following error in the Backup log: Error - RDS DR, copy snapshot failed (to DR account) due to an AWS limitation regarding default encryption key (source US East (Ohio), ...