Backup may fail with the "The snapshot 'snap-01234567890abcdef' does not exist" error.

• Related Articles

• A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error

  A backup may be marked "Partially Successful" due to the "Instance probably doesn't exist anymore" error: Error - (instance: i-1234567890abcdef) could not get object from aws. Instance probably doesn't exist anymore ... Warning - Finished kicking off ...

• 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 of RDS may fail with the error “can not take snapshot, db is in stopped state" error

  Backup of RDS may fail with the below error: "(database: >DB  name>) can not take snapshot, db is in stopped state" This is due to an AWS limitation. AWS automatically backs up a stopped RDS, so there is no need for manual backups: ...

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