NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- Configure Snapshot Manager in NetBackup
- Managing intelligent groups for cloud assets
- Protecting cloud assets or intelligent groups for cloud assets
- Managing policies for cloud assets
- Add an SLP and cloud policy
- Scan for malware
- Protecting Microsoft Azure resources using resource groups
- NetBackup Accelerator for cloud workloads
- AWS Snapshot replication
- Protecting PaaS assets
- Installing the native client utilities
- Configuring storage for different deployments
- Add credentials to a database
- Recovering cloud assets
- Recovering cloud assets
- Restore to a different cloud provider
- Recovering AWS or Azure VMs to VMware
- Recovering PaaS assets
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
- Troubleshoot PaaS workload protection and recovery issues
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
attribute is derived from . To add a condition filter on the attribute, select from the drop-down.Account ID option in intelligent groups:
The
option in the list is available to NetBackup's Default Cloud Administrator role.The
option in the list is available to NetBackup's custom roles with the 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
option.
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.
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.
While creating an intelligent group for applications, only RDS assets are supported in AWS.