NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- AWS and Azure government cloud support
- Configure Snapshot Manager in NetBackup
- Managing intelligent groups for cloud assets
- Protecting cloud assets or intelligent groups for cloud assets
- Managing policies for cloud assets
- Limitations and considerations
- Add an SLP and cloud policy
- Operations on cloud policy
- PaaS and IaaS policy SLP configurations
- Scan for malware
- Protecting Microsoft Azure resources using resource groups
- NetBackup Accelerator for cloud workloads
- Configuring backup schedules for cloud workloads using protection plan
- Backup options for cloud workloads
- AWS Snapshot 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
- Prerequisites for protecting Amazon RDS SQL Server database assets
- Configuring storage for different deployments
- About incremental backup for PaaS workloads
- Configuring incremental backups for Azure MySQL server
- About archive redo log backup for PaaS workloads
- About Auto Image Replication 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
- Protecting AWS or Azure VMs for recovering to VMware
- Cloud asset cleanup
- Cloud asset filtering
- Recovering cloud assets
- Recovering cloud assets
- About the pre-recovery check for VMs
- Supported parameters for restoring cloud assets
- Restoring to a different cloud provider
- Recovering virtual machines
- Recovering applications and volumes to their original location
- Recovering applications and volumes to an alternate location
- Additional steps required after restoring an AWS RDS database instance
- Recovery scenarios for GCP VMs with read-only volumes
- (GCP only) Restoring virtual machines and volumes using the autoDelete disk support
- Perform rollback recovery of cloud assets
- Restore to a different cloud provider
- Recovering AWS or Azure VMs to VMware
- Recovering PaaS assets
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
- Troubleshoot cloud workload protection issues
- Error Code 9855: Error occurred while exporting snapshot for the asset: <asset_name>
- Backup from snapshot jobs take longer time than expected
- Backup from snapshot job fails due to connectivity issues when Snapshot Manager is deployed on an Ubuntu host
- Error disambiguation in NetBackup UI
- Status Code 150: Termination requested by administrator
- Troubleshoot PaaS workload protection and recovery issues
About incremental backup for PaaS workloads
NetBackup supports differential incremental backup for Azure SQL Server, Azure SQL Managed Instance, AWS RDS Oracle, and GCP SQL Server workloads. Incremental backups reduce the backup window significantly in NetBackup. In this method, NetBackup backs up only the data that has been changed since the subsequent full backup.
Differential incremental backup is only supported for those workloads, where the Change Data Capture feature on the Azure SQL Server, GCP SQL Server, AWS RDS Oracle, and Azure SQL Managed Instance are enabled.
Guidelines for working with incremental backups for PaaS workloads:
Assign a longer retention period to full backups than to incremental backups within a policy. A complete restore requires the previous full backup plus all subsequent incremental backups. It may not be possible to restore all the files if the full backup expires before the incremental backups.
Use one storage for full and incremental backups.
Do not create long-term copy for incremental backups.
Do not expire random incremental backup images. Expiring them may cause application inconsistency due to data loss. NetBackup relies on the previous full backup and all the subsequent incremental backups.
While duplicating, ensure that the full and the incremental backup copies are duplicated to the target storage. Any of the previous full or incremental images missing may result in data loss.
While importing, ensure that the full and all the incremental backup copies are imported together. If any of the previous dependent full or incremental images are missing, it may result in failure.
Differential incremental backup is supported on AWS RDS Oracle, only if schema changes are managed by the RDS.