NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- AWS and Azure government cloud support
- 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
- Limitations and considerations
- Add an SLP and cloud policy
- Operations on cloud policy
- PaaS and IaaS policy SLP configurations
- Scan for malware
- Protecting Microsoft Azure resources using resource groups
- NetBackup Accelerator for cloud workloads
- Configuring backup schedules for cloud workloads using protection plan
- Backup options for cloud workloads
- AWS Snapshot replication
- Protect applications in-cloud with application-consistent snapshots
- Protecting PaaS assets
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Configuring the storage server for instant access
- Prerequisites for protecting Amazon RDS SQL Server database assets
- Configuring storage for different deployments
- About incremental backup for PaaS workloads
- Configuring incremental backups for Azure MySQL server
- About archive redo log backup for PaaS workloads
- About Auto Image Replication for PaaS workloads
- Limitations and considerations
- Discovering PaaS assets
- Viewing PaaS assets
- Managing PaaS credentials
- View the credential name that is applied to a database
- Add credentials to a database
- Add protection to PaaS assets
- Perform backup now
- Protecting AWS or Azure VMs for recovering to VMware
- Cloud asset cleanup
- Cloud asset filtering
- Recovering cloud assets
- Recovering cloud assets
- About the pre-recovery check for VMs
- Supported parameters for restoring cloud assets
- Restoring to a different cloud provider
- Recovering virtual machines
- Recovering applications and volumes to their original location
- Recovering applications and volumes to an alternate location
- Additional steps required after restoring an AWS RDS database instance
- Recovery scenarios for GCP VMs with read-only volumes
- (GCP only) Restoring virtual machines and volumes using the autoDelete disk support
- Perform rollback recovery of 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 cloud workload protection issues
- Error Code 9855: Error occurred while exporting snapshot for the asset: <asset_name>
- Backup from snapshot jobs take longer time than expected
- Backup from snapshot job fails due to connectivity issues when Snapshot Manager is deployed on an Ubuntu host
- Error disambiguation in NetBackup UI
- Status Code 150: Termination requested by administrator
- 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.