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
Troubleshooting Amazon Redshift issues
Explanation:
This is a known limitation of AWS. The maximum query statement size is 100 KB. See the AWS documentation for the details:
https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html
Workaround:
Do the following:
- Mount the Instant Access (IA) path using the following API:
netbackup/recovery/workloads/cloud/paas/instant-access-mounts - Navigate to the mount path in the media server.
- Ensure that the mount path directory hierarchy is as follows:
ClusterDirectory/DatabaseDirectory/DatabaseDirectory/SchemaDirectory/TableDirectory - In the
SchemaDirectory, locate the filesStoredProcedures.json, Views.json,andFunctions.json. Each file contains one or more SQL statements which you can run in Amazon Redshift Query Editor-2.Manually run these SQL statements.
Explanation:
If the system time where you run the AWS Redshift APIs is not correct, you get this error. This message appears in the logs:
Signature expired: 20230226T181919Z is now earlier than 20230226T181921Z (20230226T182421Z - 5 min.)"
Workaround:
Run the ntpdate command to fix the system time.
Explanation:
This error appears when the region is not specified. You can see the following error in the dbagentsutil logs. You can find the dbagentsutil logs at the following location:
/usr/openv/netbackup/logs/
Workaround:
Do the following:
- Download AWS CLI on the media server where the
dbagentis running. - Run the command:
aws configure
- Enter the region name for EC2 when prompted. Do not specify the values for the other parameters.
Explanation:
This error appears when the NetBackup Snapshot Manager that runs the discovery does not have access to the Redshift cluster. You can see the following error in the flexsnap logs:
Connect timeout on endpoint URL: "https://redshift.us-east-2.amazonaws.com/
Workaround:
Without access permission, the Snapshot Manager requires the inbound rules to be configured for the snapshot manager in the security group of the 'VPC endpoint of the Redshift service'.
On the AWS portal, select a cluster. Click Properties > click Network and security settings > click the virtual private cloud object > click Endpoints. Search for "redshift-endpoint" in the search field > click the VPC endpoint ID > click the Security Groups tab. Click the Security Group ID > click Edit Inbound rules, and add the following for media servers.
Type : HTTPS Protocol : TCP Port range : 443 Source : 10.177.77.210/32
* Here, the source refers to the media server instance.
Run discovery from NetBackup web UI again.