CPM may mark a backup as successful although not all snapshots succeeded

• Related Articles

• CPM may mark a successful RDS snapshot as failed

  CPM may mark a successful RDS snapshot as failed. In the backup log you may see the following error: Error - snapshot of database <DBname> failed. There may also be a "rate exceeded" error in the CPM server logs: ERROR: get_list(connection.py:1180) ...

• Snapshot and backup records may not be deleted during cleanup - although snapshots are deleted in EC2 and backups are hidden in GUI

  If you have CPM Server v2.1.3a, snapshot and backup records may not be deleted during cleanup from CPM's internal database - although snapshots are deleted in EC2 and backups are hidden in GUI If you have v2.1.3a, please upgrade to the latest 2.1.X ...

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

• CPM may mark a successful RDS DR as failed

  On rare occasions, CPM may mark a successful RDS DR as failed in Backup Monitor. When this happens, you can see the following messages in the backup log: Error - RDS DR copy snapshot failed for region “RegionName”….Reason: Cannot create the snapshot ...

• Backup and snapshot view csv reports may not show managed users’ data when retrieved by CPM root user

  When retrieving the “backup view csv report” or “snapshot view csv report” with CPM root user, the reports may contain data related to the logged in root user and not the managed users as well. To resolve this issue, please upgrade to the latest ...