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
Additional steps required after restoring an AWS RDS database instance
The following steps are required after you restore an AWS RDS database instance snapshot. Even though the restore operation is successful, these manual steps are required so that the instance is available for normal use.
After restoring an AWS RDS database instance successfully, you have to manually check and reassign certain properties of the restored instance. This is required because even though the restore operation itself is successful, one or more instance properties are not restored completely. In some cases, NetBackup resets the property values to their default settings.
The following RDS database instance or cluster properties are not restored completely and needs modification:
VPC security groups value (AWS Management Console > RDS Database instance > Connectivity & security tab)
Deletion protection setting (AWS Management Console > RDS Database instance > Configuration tab)
Copy tags to snapshots setting (AWS Management Console > RDS Database instance > Maintenance & backups tab)
Perform the following steps:
- Verify that the RDS database instance snapshot restore is successful.
- Sign in to the AWS Management Console and from the top-right corner, select the region in which you have restored the RDS instance.
- From the Services menu, under Database, click RDS.
- From the Dashboard menu on the left, click Databases.
- In the Databases panel, select the restored RDS database instance and then click Modify from the menu bar on the top right.
- On the Modify DB panel, check for the following properties and ensure that the attribute values match with those of the original instance:
Under Network & Security, verify that the Security group attribute has the correct security group name assigned.
Under Backup, verify that the Copy tags to snapshots option is set as per the original instance.
Under Deletion protection, verify that the Enable deletion protection option is set as per the original instance.
If required, verify all the other parameter values and set them as per your preference.
- Once you have modified the desired RDS instance properties, click Continue.
- Under Scheduling of modifications, choose an appropriate option depending on when you want to apply the modifications to the instance and then click Modify DB instance.
- Verify the RDS instance properties and ensure that the changes have taken effect.