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
Configuring backup schedules for cloud workloads using protection plan
You can add a backup schedule in the Attributes tab of the Add backup schedule dialog, while creating a protection plan for the Azure, Azure Stack Hub, AWS, OCI, and GCP cloud workloads.
See the Managing protection plans section of the NetBackup Web UI Administrator's Guide, for details on how to create a protection plan.
To add a backup schedule to a cloud workload
- On the left, click Protection > Protection plans and then click Add.
- In Basic properties, enter a Name, Description, and select Cloud, from the Workload drop-down list.
- Select a Cloud Provider from the drop-down list, and click Next. In Schedules, click Add schedule.
In the Add backup schedule tab, you can configure the options for retaining the backup and the snapshot.
- (For Azure SQL server, GCP SQL Server, and SQL Managed Instance PaaS assets only.) If you have selected Protect PaaS assets only for the protection plan, select Backup type as Incremental backup or Full. For the incremental backup type, NetBackup takes an initial full backup, and all subsequent backups capture only incremental changes in the database. This feature increases backup performance to a great extent. In case of a schema change, goes back to a full backup from an incremental backup, and notifies this activity in the activity monitor.
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. See About incremental backup for PaaS workloads.
- From the Recurrence drop-down, specify the frequency of the backup.
- In the Snapshot and backup options, do any of the following:
Select the Keep snapshot along with backup option to retain both the snapshot and the backup. Specify a retention period for both the snapshot and the backup, using the Keep snapshot for and the Keep backup for drop-downs. Select Full from the Backup type drop-down. Select Initiate backup only when the snapshot is about to expire option, to start the backup job just before the retained snapshot expires.
(For Amazon RDS Oracle assets only) If you have selected the Protect PaaS assets only option for the protection plan, you can select Backup type as Full, Differential incremental, or Archived redo log.
For incremental and Archived redo log backup types, NetBackup takes an initial full backup and captures all the subsequent backups by incremental or archive changes in the database. This feature increases backup performance to a great extent.
Do not use multiple protection plans having incremental schedules. Also, do not use protection plans with a frequency greater than 24 hours in the archived log schedule. For a successful restore NetBackup requires the previous full backup, all subsequent incremental backups, and all subsequent archive backups. If the full backup expires before the incremental or archive backups, it may not be possible to restore all the files.
Select Keep snapshot only option, to retain only the snapshot. Specify the retention period for the snapshot using the Keep snapshot for drop-down.
(Optional) If you have selected the provider as Amazon AWS, and selected to retain the snapshot by selecting any of the above two options, you can configure snapshot replication at this point. For more information about cloud snapshot replication, See Configure AWS snapshot replication.
Select Enable Snapshot replication.
In the table, select Region, AWS Account, and Retention period for the replicated snapshots.
Note:
The number of replication copies that you configure is displayed in the Snapshot replicas column in the Schedules and retention table in the Schedules tab.
Select the Keep backup only option, to retain only the backup. The snapshot expires immediately after the backup. Specify a retention period for the backup using the Keep backup for drop-down. Select Full from the Backup type drop-down.
- Continue creating the schedule in the Start window tab, as described in the Managing protection plans section of the NetBackup Web UI Administrator's Guide.
Availability of the granular recovery for files or folders option depends on the different backup options that you select for the workload.
When you select the , granular recovery is available.
When you select the option, granular recovery is available.
When you select the option, granular recovery is available.
Indexing during backup and snapshot jobs
NetBackup performs VxMS (Veritas Mapping Service) based indexing from snapshot, and inline indexing during the backup from snapshot Jobs. It can index files irrespective of the region and location of the Snapshot Manager. VxMS-based indexing is currently supported for GCP, AWS, Azure, OCI, and Azure Stack Hub clouds.
Indexing is performed during the actual backup or snapshot jobs, but you can perform the recovery of individual files or folders only from the snapshot and backup copy using Enable granular recovery for files and folders option.
Once the snapshot of the VM assets is created, the 'Index from Snapshot' job for each of the assets is triggered. You can check the indexing job details in the Activity Monitor.
The VxMS debug logs and the cloud connector debug logs are available in the /cloudpoint/openv/dm/datamover.<datamover-id>/netbackup/logs folder of the Snapshot Manager.
To index files and folders with the same mount path as mentioned in
/etc/fstab, the/etc/fstabfile on the Linux servers must have entries based on the UUID file system, instead of device paths. The device paths can change depending on the order in which Linux discovers the devices during system boot.
Note:
If the VM is not in a connected state, then the VM backup continues and the backup job is marked as partially successful. In this case, you cannot restore individual files or folders as the indexing is not available when the VM is not connected.