Please enter search query.
Search <book_title>...
NetBackup™ Web UI Cloud Administrator's Guide
Last Published:
2025-03-18
Product(s):
NetBackup & Alta Data Protection (11.0)
- 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
- About storage lifecycle policies
- Managing policies for cloud assets
- Configuring the Start window
- Managing cloud policies
- Scan for malware
- Protecting Microsoft Azure resources using resource groups
- NetBackup Accelerator for cloud workloads
- AWS Snapshot replication
- Protecting PaaS assets
- Protecting RDS Custom instances
- Protecting Azure Managed Instance databases
- Limitation and considerations
- Installing the native client utilities
- Configuring storage for different deployments
- Managing PaaS credentials
- Add protection to PaaS assets
- Recovering cloud assets
- Recovering cloud assets
- 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
For AWS RDS PostgreSQL and AWS Aurora PostgreSQL
Backup and restore need a media server with NetBackup version 10.4 or above and a local LSU.
If a backup image contains a materialized view, after the restore, you need to manually refresh the materialized view. See this article to refresh materialized views:
If the user credentials used to restore are those of an IAM user, then the database object gets restored with the same ownership as in the source database.
Ownership and privileges on an object are not restored. The user that you use for the restore, becomes the owner of all the restored database objects in the following scenarios:
If the restored user credentials are username and password.
If the backup image is taken by a version before NetBackup version 10.4.