Considerations for cloud intelligent groups

Consider the following before creating cloud intelligent groups:

The values that you specify for the intelligent group filters are case-sensitive.
The Status attribute is derived from State. To add a condition filter on the Status attribute, select State from the Filter drop-down.
Account ID option in intelligent groups:
- The All Accounts option in the Account ID list is available to NetBackup's Default Cloud Administrator role.
- The All Accounts option in the Account ID list is available to NetBackup's custom roles with the All cloud assets permission for one or multiple cloud service providers.
- Any custom role with explicit asset access permission of account(s) or subscription(s) cannot use the All Accounts option.

Considerations for PaaS intelligent groups

You can subscribe the assets to different protection plans based on the backup types that are supported for the assets. However, you cannot subscribe the intelligent groups containing AWS RDS Oracle assets to the protection plans that contain incremental schedules.
Intelligent groups are not supported for AWS DocumentDB and AWS Neptune workloads.
The Service type drop-down shows the service types available for the provider, irrespective of the discovered assets.
Intelligent groups for PaaS assets support protection of the Azure, AWS, and GCP assets.
Intelligent groups are not supported on Redshift clusters. However, intelligent groups for Redshift database assets are supported.
For Azure MySQL assets, you cannot create intelligent groups with a mix of database and server assets. An intelligent group can either contain a group of databases or servers. When creating an intelligent group for Azure MySQL, you must specify the entityType filter as either server or database.
Tag handling for Azure SQL server and Azure Managed Instance:
- For SQL server, the "Server" keyword is added as a prefix to tags, when the tag is copied at the database level.
- For Azure Managed Instance, the "Instance" keyword is added as a prefix to the tags, when the tag is copied at the database level.
- No prefix is added for tags in other workloads.

Considerations for Application intelligent groups

While creating an intelligent group for applications, only RDS assets are supported in AWS.