NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- Configure Snapshot Manager in NetBackup
- Managing intelligent groups for cloud assets
- Protecting cloud assets or intelligent groups for cloud assets
- About storage lifecycle policies
- Managing policies for cloud assets
- Configuring the Start window
- Managing cloud policies
- Scan for malware
- Protecting Microsoft Azure resources using resource groups
- NetBackup Accelerator for cloud workloads
- AWS Snapshot replication
- Protecting PaaS assets
- Protecting RDS Custom instances
- Protecting Azure Managed Instance databases
- Limitation and considerations
- Installing the native client utilities
- Configuring storage for different deployments
- Managing PaaS credentials
- Add protection to PaaS assets
- Recovering cloud assets
- Recovering cloud assets
- Recovering AWS or Azure VMs to VMware
- Recovering PaaS assets
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
- Troubleshoot PaaS workload protection and recovery issues
For Amazon Redshift clusters
The minium supported version of Primary, Media, and Snapshot management server is NetBackup 10.5.
FIPS is currently not supported for Redshift clusters.
Redshift clusters created with AWS Secrets Manager credentials are not supported.
Redshift cluster restores to alternate regions or alternate accounts are not supported.
Redshift cluster must be in available state before triggering a cluster snapshot.
Cluster restore jobs may appear successful immediately in the Activity monitor, while the job is still in progress. Monitor the cluster restore job in your AWS console for the actual status of the job.
Maximum number of manual snapshots per Redshift cluster is 20.
During restore, the PubliclyAccessible property of the restored cluster is set to False. You can manually change it as required after the restore.
Do not trigger NetBackup image expiry for Redshift cluster snapshot images when a restore is in progress. If automated image expiry jobs run while a restore is ongoing, then the cleanup of the snapshot from the AWS portal fails.
NetBackup Activity monitor does not show values for these snapshot-parameters: Bytes transferred, Files written, Current File, Estimated Files Remaining, and Estimated Files.