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 ...
RDS encrypted backups failing DR according to backup logs with "cannot be copied because it does not exist in your account" error You may see the following in the logs Info - RDS DR, found matching KMS alias alias/BMS-Standard-Key (source US East (N. ...
RDS DR may fail with the following error printed in the log: Fri 04/26/2019 09:34:52 AM - Error - RDS DR copy snapshot failed for region Anyregion (region), snapshot cpm-policy-40-db7-2019-4-26-12-30. Reason: Option group whateveroptiongroupgoeshere ...
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 ...
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) ...