NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- Configure Snapshot Manager 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 assets
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Configuring the storage server for instant access
- Configuring storage for different deployments
- About incremental backup 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
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
Installing the native client utilities
If you use a build-your-own (BYO) setup, you must install the native client utilities in your NetBackup environment for your PaaS workload to work.
For NetBackup deployments in Azure Kubernetes Services (AKS) or Elastic Kubernetes Services (EKS), the native client utilities are packaged as part of NetBackup media server, primary server, and data mover container image. Manual installation is not required for them.
Ensure that the network settings like firewall, security group, and DNS configuration are configured appropriately to access databases within the cloud provider.
Note:
If any of these packages are already installed in the media server(s), remove the packages to avoid conflict with the newer versions of the packages that you install.