Azure - Error "Policy "Policy_Name" doesn't exist/attached to account" may be printed into 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, then scroll up to see account looking for policy.
Once Azure account name is
obtained, search in that account in the Azure console VM "Tags"
section for the key and value field. Key field is "cpm backup" and
value field will be the policy name. The Azure account name is found in a
statement like below example, printed before the error above. To easily find Azure account
name do a search before the above error for "Scan Tags for account".
INFO: manage_account_tagged_resources(.\cpmserver\cpm\backup_tag.py:107) Scan tags for account Account_name (user: User_Name)
Option
1 - If volume/instance is mistakenly tagged to an
incorrect policy name, please re-tag to a correct policy name that belongs to
this Azure account.
Option 3 - If you have multiple accounts seeing the same resources please see chapter 13.4.1 "Pitfalls" in our CPM User Guide:https://docs.n2ws.com/user-guide/14-tag-based-backup-management#14-4-pitfalls-and-troubleshooting
Please note, Tags are case sensitive.Tools you can use to locate tags in Azure to alleviate the message above:
1. Open VM Console in Azure and browse to VM in left hand pane.
2. In the Filter section please enter the name of the Policy that your received the error. This should return the VM that have the tag you searched for.
When the search returns, click on the VM name to open its details, on the left pan of the VM select the Tags tab, the right pan will open.
3. Remove or edit the tag that caused the error as in the screenshot below.
4. You can delete or edit the tags as needed.
5. Then open CPM Manager
and select General
Settings at
the top of the screen and select the Tag Scan section.
6. Please run a Scan Now Job. When
completed open the "Show Log" to verify the error is gone.
Note: You may need to repeat this process if the error persists in the scan log and instead of VM machines search the Disks or Snapshots etc. Then rerun the Scan and verify the errors are not present.
Related Articles
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 ...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 ...N2WS-22672 - Tag scan fails with error "list index out of range"
Issue: Tag scan fails with the following error in cpm_scan.log log Traceback (most recent call last): File "./cpmserver/cpm/backup_tag.py", line 358, in scan_for_aws_resources File "./cpmserver/cpm/aws_utils.py", line 3100, in ...How to configure tag scan module by regions and by Scan Resource Types in CPM 3.0 and above
Background: This document describes how to filter Resource scanning by regions or by Resource Types which is new to new to CPM 3.0, This allows you to limit not only the regions that a tag scanning will scan but adds the ability to scan by specific ...