NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- Configure Snapshot Manager's in NetBackup
- Managing intelligent cloud groups
- Protecting cloud assets or intelligent cloud groups
- Cloud asset cleanup
- Cloud asset filtering
- AWS and Azure government cloud support
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Configuring backup schedule for cloud workloads
- Backup options for cloud workloads
- Snapshot replication
- Configure AWS snapshot replication
- Using AWS snapshot replication
- Support matrix for account replication
- Protect applications in-cloud with application consistent snapshots
- Protecting PaaS objects
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Configuring the storage server for instant access
- 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
- 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, Flexscale, Appliance, Azure Kubernetes Services (AKS) or Elastic Kubernetes Services (EKS) do not support PaaS workloads. As a possible workaround for using AKS or EKS environments, mount the ushare path on the media server with path same as the ushare's export path.
For example:
If the ushare is created with name 'usharedbpaas', run these two commands on the media server:
mkdir -p /mnt/vpfs_shares/usha/usharedbpaas
mount -t nfs4 <storage server fqdn>:/usha/usharedbpaas /mnt/vpfs_shares/usha/usharedbpaas
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 primary server running on Windows OS.
You can duplicate the PaaS backup image to a supported storage server. But before starting the a restore, you need to duplicate the image, back to an MSDP server with universal share enabled. See Recovering duplicated 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.
Alternates restore for region and account is not supported.
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.
If you create the MSDP STU on cloud storage, then universal shares from such storage servers are not listed in the PaaS protection plan. Because the backups of universal shares from cloud storage units are not supported by the universal share backup mechanisms