NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- Configure Snapshot Manager's in NetBackup
- Managing intelligent cloud groups
- Protecting cloud assets or intelligent cloud groups
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Protecting PaaS objects
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Add credentials to a database
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
Limitations and considerations
Consider the following when protecting cloud workloads.
NetBackup deployments in Flex Appliance and Flex Scale do not support PaaS workloads.
Supports only default the ports for the databases across providers. Workload instances configured with the custom ports are not supported.
Database names containing the characters '#' and '/' are not supported for backup and restore operations. Also, the database name should adhere to naming conventions suggested by the cloud vendors.
Backup and restore of a database with multi-byte or non-English characters are not supported for a primary server running Windows and having back level media server with a version less than 10.1.1.
You can duplicate the PaaS backup image to a supported storage server. But before starting a restore, you need to duplicate the image, back to an MSDP server with universal share enabled. See Recovering duplicate images from AdvancedDisk.
Restore of security privileges is not supported.
During restore we use - no-owner and - no-privileges option and in post-restore phase we show metadata details which were captured at time of backup as owner/ACL in the progress log restore activity on web UI.
Restore does not fail, if the owner/role does not exist on the destination.
Post restore, the database has the role associated according to the credentials provided in NetBackup against the destination instance.
Users need to modify the ownership of databases post restore.
Backup and restore are not supported if the only SSL (Secure Sockets Layer) connection is enforced at the server level for GCP PostgreSQL workload.
Azure Postgres database restore from single to flexible server or vice versa is not supported because of the cloud provider limitations.
Following characters are not supported in database name in restore workflow: &, (, ), <, >, \, |, /, ;, `, ', and ".
Uppercase username is not supported for new users added after PostgreSQL server creation.
For AWS DynamoDB, you must create an S3 bucket with the name
netbackup-<accountid>
. NetBackup uses this bucket as staging location for the backup operations.Alternates restore for region and account is not supported.
Restore from imported images from a different primary server is only supported using NetBackup REST API.
Only Express and Web editions for AWS RDS SQL are supported.
For credential validation, IAM is not supported for AWS RDS SQL. You can use the username and password method.
Only
data management type is supported. The data management type is not supported for AWS RDS SQL instance editions.
Restore operation require superuser privileges if the dump file contains CREATE DEFINER statement.
Backup and restore are not supported if the only SSL connection is enforced at the server level for GCP MySQL workload.
The Azure VM which is used as a media server, should be in the same Vnet as that of an Azure-managed instance. Alternatively, if the media server and SQL managed instance are in different Vnet, then both the Vnets must be peered to access the database instance.
Backup fails when Readlock is placed on the database or resource group.
Backup is partially successful when Deletelock is placed on the database or resource group. The tempdb stale entry does not get deleted from the Azure cloud portal. You need to manually delete it.