DR may remain stuck in "In Progress" state forever

• Related Articles

• DR snapshots may get encrypted with default encryption key on target region instead of custom key

  This issue may occur if Encryption Keys list contains over a hundred of encryption keys. The below warning may appear in the backup log: Warning - Volume snapshot <snapshot_id> is encrypted with key from another account. Using default encryption on ...

• RDS Cross Region DR fails with Exception: Cannot copy more than 5 snapshots across regions

  You may see the following errors in the CPM logs when cross region RDS DR copies fail to successfully copy to the DR region. ERROR:  cpm_copy_dbsnapshot(aws_rds_utils.py:217)  Exception: Cannot copy more than 5 snapshots across regions ...

• Cross-account and cross-region policy with instances in multiple regions may not replicate snapshots to all regions

  If DR is enabled on a policy with both Cross-account and Cross-region DR, and the policy backs up instances in multiple regions, snapshots may be missing in the target account's target region. For example: If you have 1 instance in N.Virginia and 1 ...

• Cross region copy of RDS snapshots may fail with error: RDS DR copy snapshot failed (in Backup account). No matching KMS alias in target region

  Issue: The Following error may appear in the CPM Server logs: ERROR: start_copy_region(dr_rds.py:301) RDS DR copy snapshot failed (in Backup account). No matching KMS alias on target region (source EU (Frankfurt), target Asia Pacific (Singapore), RDS ...

• DR process may time out due to exceeding the snapshot limit per region

  In case Backup finished successfully but DR failed after 24 hours due to timeout as seen in the “Backup Log” example below: Error - DR process failed: Timed out after 24 hours Please download logs and search the CPM logs for: RDS DR We reached the ...