# Using tags to automate resource group membership

You can use tags from your virtualization or cloud provider to automatically manage resource group membership in Commvault.

By combining provider tags with rule-based selection, you can create groups that update dynamically as your environment changes.

## Why use tags for group membership

Tags provide a scalable way to organize resources based on business or operational criteria.

Using tags:

- Reduces manual effort when managing large or dynamic environments

- Helps maintain consistent grouping across teams and workloads

- Automatically updates group membership as resources are added or modified

## Tag types in Commvault

Commvault uses two types of tags for different purposes.

- Provider tags: Tags defined in platforms such as VMware vCenter, Amazon Web Services (AWS), or Microsoft Azure. You can use these tags in rule-based selection to dynamically include resources in groups.

- Commvault tags: Tags created in Commvault to organize and label resources. These tags are not used for rule-based resource selection.

## How tag-based rules work

You assign tags to resources in your provider platform, and then create rules in a group that include resources with specific tags.

For example:

- Assign the tag `Environment=Production` to resources in your provider

- Create a group that includes all resources with that tag

As new resources are tagged, they’re automatically included in the group.

## Create a group using tag-based rules

To include resources based on provider tags, define a rule that matches the tag.

1. Go to the group that you want to manage.

2. On the Content tab, click Edit.

3. Click Add, and then select Rule.

4. Click Add rule.

5. For Rule, select Tag or Tag category.

6. In the operator list, select how the value is evaluated, such as Equals.

7. In Value, select or enter the tag.

8. Optional: Add more rules and select whether resources must match all or any conditions.

## Common tagging patterns

Group by | Example tags | How to use
--- | --- | ---
Environment | `Environment=Production`, `Environment=Test`, `Environment=Development` | Create groups based on lifecycle stage.
Application or service | `Application=Finance`, `Application=HR` | Apply protection settings per application.
Ownership | `Owner=TeamA`, `Owner=TeamB` | Identify ownership and manage responsibility.

## Combine tags with other rules

You can combine tag-based rules with other criteria to refine group membership.

For example:

- Include resources with the tag `Environment=Production`

- And where the resource name starts with `prod-`

This approach provides more precise control over which resources are included.

## When to use tag-based grouping

Use tags in the following scenarios:

- Managing large or dynamic environments

- Standardizing how resources are grouped across teams

- Automating group membership

- Applying protection settings consistently across changing resources

×

Loading...