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
- 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 PostgreSQL
Restoring security privileges is not supported.
During restore, you can use the - no-owner and - no-privileges options. After restore, the metadata captured at the time of backup is shown as the owner/ACL in the progress log restore activity on the web UI.
Restore does not fail if the owner or role does not exist on the destination.
Post restore, the database has the role associated with it, according to the credentials provided in NetBackup against the destination instance.
Users need to modify the ownership of databases post-restore.
Azure Postgres database restore from a single to a flexible server or vice versa is not supported because of the cloud provider's limitations.
The following characters are not supported in the database name in the restore workflow: `, @, \, [, ], !, #, %, ^, ., ,, &, *, (, ), <, >, ?, /, |, }, {, ~, :, ', ", ;, +, = and -.
Uppercase username is not supported for new users added after PostgreSQL server creation.
(RDS and Azure PostgreSQL only) SCRAM authentication configured on a database instance is not supported.
If full or differential incremental backups fail with temporary objects, then delete the temporary objects manually and run backup again.