Using tags for tag based protection plans

Examples are provided for the kind of tag names and values that you can use to leverage tagging resources in Cloud Snapshot Manager.

Tag based filtering examples

You can filter cloud resources by their tags. From the Resources page in the portal, you may type a string in the Tag Name field, in the Tag Value field, or in both fields. Resources without the selected tags are filtered out of the response. The following examples show various ways of filtering with tags.

NOTE: For AWS resources, the strings that you type in are treated as case sensitive and a search for resources is based on the exact strings. For Azure resources, the strings that you type in are not treated as case sensitive. For GCP resources, the tag is refereed as label.
Table 1. Tag Rules
Tag Rule Description Example
Tag Name Tag Value Result
Tag Name Resources that contain the tag name. Department All resources that have the 'Department' tag name are displayed.
Tag Value Resources that contain the tag value.
NOTE: No support in GCP.
Sales All resources that have the 'Sales' tag value are displayed.
Tag Name and Tag Value Resources that contain the tag name and the tag value. Env Production All resources that have the 'Env' tag name and the 'Production' tag value are displayed.
  • Tag Name1:Tag Value1
  • Tag Name2: Tag Value2
Resources that contain both the key value pairs.
  • Department
  • Env
  • Sales
  • Production
All resources that have the key pair, 'Department' tag name and the 'Sales' tag value and the key pair, 'Env' tag name and the 'Production' tag value are displayed.
Same Tag Name with multiple Tag Values Resources that contains the tag name that is paired with at least one of the tag values provided.
  • Department
  • Department
  • Department
  • Sales
  • Engineering
  • Finance
All resources that have the 'Department' tag name and the 'Sales' or 'Engineering' or 'Finance' tag value are displayed.
Wildcard for Tag Name or Tag Value Resources that match the wildcard.
NOTE: Wildcards are not supported for Azure and GCP.
  • Purpose
  • Location
  • Prod*
  • Test*
  • *us
  • All resources that have the 'Purpose' tag name and the tag value starting with 'Test', for example, 'Test_manual' or 'Test_automated' are displayed.
  • All resources that have the 'Location' tag name and the tag value ending with 'us', for example, 'eastus' or 'centralus' are displayed.
  • All resources that have the tag name starting with 'Prod' are displayed.
Multiple Tag Names Resources that contain all the tag names specified.
  • Lab
  • Test
All resources that have the 'Lab' and 'Test' tag names are displayed.
Multiple Tag Values Resources that contain all the tag values specified.
NOTE: This is not supported in the GCP.
  • Production
  • Web server
All resources that have the 'Production' and 'Web server' tag values are displayed.
The combination of all the above filters. Resources that match all the filters in combination.
NOTE: 
  • The above rules are applicable for a unique combination of Cloud Account, Resource, and Region (AWS only). For example, CloudAccount1 + VM + us-east-1 + name: (Tag Name) and CloudAccount1 + VM + usa-east-1 + location (Tag Name) are for the tag rule Multiple Tag Names whereas CloudAccount1 + VM + us-west-1 + name: (Tag Name) and CloudAccount1 + VM + usa-east-1 + location (Tag Name) are for the tag rule Tag Name applied on us-west-1 and us-east-1 regions.
  • Tag based protection plan execution first retrieves all the resources available with the provided tag key/value pair. Every resource is again evaluated for the power state.
    • If the power state is Invalid such a resource is skipped during execution of a protection plan
    • If the power state is Valid such a resource is protected during execution of a protection plan

    The following are Invalid states for cloud providers:

    Azure AWS
    PowerState/deallocatinginstance-store
    PowerState/unknown terminated
    ProvisioningState/deleting
    ProvisioningState/creating