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

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. Virginia), target US East (Ohio), snapshot cpm-policy-35-db0)
Error - RDS DR copy snapshot failed for region US East (Ohio), snapshot cpm-policy-35-db0 (to DR account). Reason: Encrypted source snapshot: arn:aws:rds:us-east-1:23456788:snapshot:cpm-policy-35-db0 cannot be copied because it does not exist in your account
Info - RDS DR, found matching KMS alias alias/BMS-Standard-Key (source US East (N. Virginia), target US East (Ohio), snapshot cpm-policy-35-db1)
Error - RDS DR copy snapshot failed for region US East (Ohio), snapshot cpm-policy-35-db1 (to DR account). Reason: Encrypted source snapshot: arn:aws:rds:us-east-1:23456788:snapshot:cpm-policy-35-db1 cannot be copied because it does not exist in your account
Info - DR completed for region US East (Ohio)
Error - DR RDS process failed

If you encounter this errors, please upgrade to the latest  2.X.X version.

Reference defect number – N2WS-8786
Link to Release Notes – release notes for the latest v2-6-x cpm release

    • Related Articles

    • Cross-region and cross-account DR of an encrypted RDS cluster may fail in v2.6

      Encrypted cluster RDS backups (Cross-region & cross-account) DR might fail. You may see the following in the logs Error - RDS DR copy snapshot failed for region US East (Ohio), snapshot Snapshotname (to DR account). Reason: Encrypted source snapshot: ...

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

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

    • EBS/RDS DR & Recovery with KMS key

      When copying cross account an EBS/RDS Volume encrypted with custom KMS, a KMS key should also be available in the other account. There are 2 ways that CPM uses for checking KMS key - Alias & Tag KMS Tag When using custom tag, you are telling CPM to ...

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