CPM may fail to add more than one Aurora cluster to a policy using “cpm backup” tags

• Related Articles

• “cpm backup” tag values may not be updated for instances already included in a policy

  When updating “cpm backup” tags on an instance which is already added to a policy, CPM may not add the tag to this policy during “Scan Tag” action. If you update the “cpm backup” tag of an instance that already exists in a policy but the change isn’t ...

• CPM may fail to add an instance using "Scan Resources”, if policy is created from a template and the "#app-aware" option is added to the tag

  When trying to add an instance to a new policy, which is created from a template using the cpm backup tag and value of new policy:existing policy#app-aware, tag scanning may fail with the following error: “Resource tag scan failed". The new policy is ...

• Cross-account DR backup of encrypted snapshots of Aurora cluster (RDS) may fail with the “No matching KMS alias” error

  DR of encrypted snapshots of AuroraDB cluster (DRS) may fail with the “No matching KMS alias” error in the Backup log: Error - Aurora DR copy snapshot failed (in Backup account). No matching KMS alias on target region (source <source_region>, target ...

• Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into CPM server log during the tag scanning operation

  The following may be printed into the CPM server log during the tag scanning operation: ERROR: manage_account_tagged_resources(.\cpmserver\cpm\backup_tag.py:336) Policy_Name doesn't exist/attached to account To resolve: Find error in CPM server logs, ...

• Instance may be removed from the policy once a tag scan is performed

  An instance may be removed from the policy once a tag scan is performed Issue: When there is an instance which is added to two policies - by tag and via web-console, an instance will be removed from the policy in which it was added via GUI. In logs ...