CPM may accidently remove an instance from a policy

• Related Articles

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

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

• Error "Account AccountName can't define the cpmdata policy, as it's not the owner of the CPM Server" may be displayed when creating the "cpmdata" policy

  Error "Account AccountName can't define the cpmdata policy, as it's not the owner of the CPM Server" may be displayed when creating the "cpmdata" policy. This means that you are trying to create the "cpmdata" policy using an account that isn't the ...

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

• Empty tag value may result in the error "Instance (or Volume) <ID> wasn't scanned properly"

  The error "Instance (or Volume) <ID> wasn't scanned properly" may appear in resource scan log and CPM server log if an instance, or volume is configured with the cpm backup tag key, and the tag value is empty. This message will appear only if the tag ...