CPM may mark a successful RDS DR as failed

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

• Cross-Account and Cross-Region DR of an encrypted RDS database may fail

  If cross-region and cross-account backup of an encrypted RDS database is successful, but fails in the cross-region cross-account DR copy, you may see the following error in the cpm logs: ERROR: start_copy_region(dr_rds.py:381) RDS DR copy_snapshot ...

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

• RDS DR may fail in v2.6.x with the "cannot be copied because it does not exist in your account" error

  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 error "Option group whateveroptiongroupgoeshere does not exist."

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