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
- About storage lifecycle policies
- Managing policies for cloud assets
- Limitations and considerations
- Planning for policies
- Creating policies for cloud assets
- Setting up attributes for PaaS assets
- Setting up attributes for IaaS assets
- Creating schedules
- About backup frequency
- About assigning retention periods
- Configuring the Start window
- Configuring the include dates
- Configuring the exclude dates
- Configuring the cloud assets for PaaS
- Configuring the cloud assets for IaaS
- Configuring backup options for IaaS
- Managing cloud policies
- 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 AWS or Azure VMs for recovering to VMware
- Cloud asset cleanup
- Cloud asset filtering
- Protecting PaaS assets
- Protecting PaaS assets
- Prerequisites for protecting PaaS assets
- Enabling binary logging for MySQL and MariaDB databases
- Enabling backup and restore in Kubernetes
- Prerequisites for protecting Amazon RDS SQL Server database assets
- Protecting RDS Custom instances
- Protecting Azure Managed Instance databases
- Limitation and considerations
- For all databases
- For PostgreSQL
- For incremental backups for Azure PostgreSQL
- For AWS RDS PostgreSQL and AWS Aurora PostgreSQL
- For AWS DynamoDB
- For AWS DocumentDB
- For AWS Neptune
- For AWS RDS SQL
- For Azure, AWS RDS, and Aurora MySQL
- For incremental backups using Azure MySQL server
- For incremental backups using the GCP SQL Server
- For Azure SQL and SQL Managed Instance
- For Azure SQL and SQL Managed Instance (without temp. database)
- For Azure SQL Server and SQL Managed Instance incremental backup
- For Azure Cosmos DB for MongoDB
- For Azure Cosmos DB for NoSQL
- For Amazon RDS for Oracle
- For Amazon Redshift databases
- For Amazon Redshift clusters
- For GCP SQL Server
- For GCP BigQuery
- Installing the native client utilities
- Configuring storage for different deployments
- Configuring the storage server for instant access
- 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
- Discovering PaaS assets
- Viewing PaaS assets
- Managing PaaS credentials
- Add protection to PaaS assets
- Recovering cloud assets
- Recovering cloud assets
- About the pre-recovery check for VMs
- Supported parameters for restoring cloud assets
- Recovering virtual machines
- Recovering applications and volumes to their original location
- Recovering applications and volumes to an alternate location
- 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
- 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>
- VMs and other OCI assets with CMK-encrypted disks are marked as deleted in NetBackup UI.
- 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
Using AWS snapshot replication
This section describes how to create snapshot replicas using the AWS snapshot replication feature, and restore the replicated snapshots whenever required. Refer to the NetBackup Snapshot Manager Install and Upgrade Guide and the NetBackup Web UI Administrator's Guide for details about these steps, otherwise indicated.
This section describes how to configure the Source region to create snapshot replicas in the Target region.
To create replicas
- Add Snapshot Manager (CP1) in web UI.
- Add AWS plug-in for Source and Target region for replication.
- Create a protection plan and select Region and Account.
- Connect and configure an application consistent guest VM using the OnHost agent.
- Start the snapshot-based backup and replicate the snapshots using the protection plan.
- Verify the recovery points for snapshot and replica copy.
If the Source region fails, you can restore the VMs belonging to this region, from the Target region, where you have taken the snapshot replicas. As the Source region is down, you initially need to restore the VMs in the Target region.
Note:
You cannot restore single files or folders from a replica that was discovered by an alternate Snapshot Manager in a failed over region.
Restoring in the target region
- Disable server CP1 in the Source region from web UI.
- Register a new Snapshot Manager (CP2) in the target region, from web UI.
- Add AWS plug-in for only the Target region and account. Let the discovery complete.
- To restore VMs:
Sign in to the NetBackup Web UI.
On the left, click Workloads > Cloud. On the Virtual machines tab, click the computer that you want to recover.
Click the Recovery points tab. In the list of images, click Restore in front of the required Replica image, and click Restore virtual machine.
To change the Display name for the VM, enter a new name.
Select a subnet (subnet path having VPC).
- Add the appropriate security group to the restored VMs to enable remote access.
- Uninstall and reinstall the Snapshot Manager agent from the restored VMs, and then register the Snapshot Manager agents with the new CP2 server.
- Run a deep discovery from the AWS provider console.
- Create new protection plan to protect the restored VMs. Start a snapshot-based backup.
You can restore the VMs from the Target region to the Source region, once the source region is back online.
Restoring to the source region
- Edit the AWS plug-in for CP2 and add the Source region.
- Create a new protection plan to create a snapshot replica in the Source region.
- Start a snapshot-based backup and replicate.
- Disable the CP2 server in web UI. Enable or disable a Snapshot Manager
- Enable the CP1 server and start a deep discovery from the AWS provider console.
- Perform full restore of the VMs from the Target region.
- Add the appropriate security group to enable remote access to the restored VMs.
- Uninstall and reinstall the Snapshot Manager agents from the restored VMs. Then register Snapshot Manager agents with the CP1 server.
- Run a deep discovery from the AWS console.
- Use the existing protection plan to protect newly restored VMs.