CPM may mark a successful RDS snapshot as failed

• Related Articles

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

• Volume Snapshot may fail with error "The maximum per volume CreateSnapshot request rate has been exceeded"

  Volume Snapshots may fail with the following errors in the log files. backup log 02-12-20 11:07:22 - Error - create snapshot of instance volume vol-xxxxxxxxxxxxx failed. 02-12-19 11:07:22 - Error - snapshot of instance ec2-xxxxxxxxx-xxxx-xx, volume ...

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

  In case CPM marks a backup as successful but not all snapshots succeed, please upgrade to the latest 2.X.X version Reference defect number – N2WS-3578, fixed in v2.4.0 Link to Release Notes and the latest patch – ...

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

• Snapshots may fail with "Reason: Maximum allowed active snapshot limit exceeded."

  Snapshots may fail with "Reason: Maximum allowed active snapshot limit exceeded." This means that you have exceeded Amazon's limit of snapshots per account (10000 by default). ...