DR copy may fail with "Failed looking for source KMS. Error: Request limit exceeded” error

• Related Articles

• DR may fail due to the “Volume DR Failed getting volumes info” and “RequestLimitExceeded” errors

  If DR fails with the below errors in Backup log ERROR: check_region_copy_state(.\cpmserver\cpm\dr_volume.py:<line_number>) Volume DR Failed getting volumes info in region <Region name> (policy <Policy Name>,in Backup account), Exception: ...

• Cross-account DR may fail with the "RequestLimitExceeded" error

  The Cross-Account DR may fail with the following error in the Backup Log:  Error,"Volume DR copy snapshot failed for region <Region Name>, snapshot snap-<Snapshot Number> (to DR account). Reason:       Failed adding share permission to snapshot ...

• DR of encrypted snapshots may fail with the “No matching KMS alias” error

  DR of encrypted snapshots may fail with the following error in the Backup log: ERROR: start_copy_region(.\cpmserver\cpm\dr_volume.py:<line number>) Volume DR copy snapshot failed (in Backup account). No matching KMS alias on target region (source ...

• DR may fail with "Error: No KMS info for region" and "failed getting kms aliases"

  The following error may appear in the Backup Log: Error - Failed looking for source KMS (region US West (Oregon), snapshot snap-xxxxxxxx). Error: No KMS info for region us-west-2 (No KMS) This error may appear in cpm_server.log: ERROR: ...

• Cross-region DR copy of encrypted snapshot may fail with "Copy failed due to an AWS limitation regarding default encryption key” error

  DR of encrypted snapshots may fail with the following error in the Backup log: Error - <DR Policy>, copy snapshot failed (in Backup account) due to an AWS limitation regarding default encryption key source <source region>, target <target region>, ...