Please enter search query.
Search <book_title>...
NetBackup™ Web UI Cloud Administrator's Guide
Last Published:
2023-01-12
Product(s):
NetBackup (10.1.1)
- 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
Recovering PaaS assets
PaaS assets are listed under the workload. You can restore AWS RDS PostgreSQL, RDS MySQL, and RDS SQL Server assets from the tab, and all other PaaS assets, from the tab. Recovery flows for Azure assets are different based on whether they are NetBackup protected or Azure protected.
PaaS assets support Instant access during recovery. Instant access enables faster access to data and reduces overall recovery time.
Before performing Instant access recovery ensure to add the key: MEDIA_SERVER_POD_CIDR in the bp.conf file of the primary server. For NetBackup deployed in AKS or EKS environment, set its value to the subnets of the media server pod, as comma-separated values. For example: MEDIA_SERVER_POD_CIDR=10.0.0.0/8, 10.0.0.0/16