NetBackup™ Web UI Cloud Administrator's Guide
- Introducing the NetBackup web user interface
- Monitoring NetBackup
- Managing and protecting cloud assets
- Configure CloudPoint servers in NetBackup
- Managing intelligent cloud groups
- Protecting cloud assets or intelligent cloud groups
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
Recovering cloud assets
You can restore AWS, Azure, and Azure Stack VM assets from snapshot copy, replica copy, backup copy, or duplicate copy.
While restoring VMs, NetBackup gives you the option to change certain parameters of the original backup or snapshot copy. Including options like changing the VM display name, changing power options of the VM, removing tag associations during restore, and restoring to an alternate network. You can also restore VMs to an alternate configuration, to a different region, to a different subscription, and restore VMs or disks to a different resource group.
Pre-recovery check indicates how a restore may fail, before the restore is initiated. The pre-recovery check verifies the following:
Usage of supported characters and the length in the display name.
Existence of destination network
Existence of selected Resource group for VMs and disks
Existence of source VM snapshot(applicable for restore from snapshot)
Existence of the staging location added in the file
/cloudpoint/azurestack.conf
(applicable for restore from backup for Azure stack)Existence of a VM with the same display name.
Connectivity with the CloudPoint server and cloud credential validation.
The pre-recovery check for PaaS assets verifies the following:
A valid Azure SQL database display name. Another database with the same display name should not exist.
Valid restore point in Azure. The restore point must be later than or equal to earliest recovery point and earlier than or equal to the current time.
A valid managed instance in Azure. The specified managed instance must exist. If the managed instance exist then only SQL database display name is validated under it. This is applicable only for Azure SQL Managed database recovery points.
The following table summarizes the different parameters that you can change while restoring assets for different cloud providers.
Table: Supported parameters for Azure and Azure Stack snapshot and backup copies
Parameters | Snapshot copy | Backup copy | |||||||||||||||||
Azure | Azure Stack | Azure | Azure Stack | AWS | |||||||||||||||
Change VM display name | Y | Y | Y | Y | Y | ||||||||||||||
Change power state of the VM | Y | Y | Y | Y | Y | ||||||||||||||
Remove tag associations | Y | Y | Y | Y | Y | ||||||||||||||
Restore to a different network | Y | Y | Y | Y | Y | ||||||||||||||
Subscription ID | Y | Y | |||||||||||||||||
Change resource group | Y | Y | Y | Y | |||||||||||||||
Change region of the VM | Y | Y | Y | ||||||||||||||||
Change provider configuration | Y | Y | Y | ||||||||||||||||
Change resource group for disks | Y | Y | Y | Y |
Table: Parameters supported by AWS and GCP snapshot copies
Parameters | AWS | GCP |
Change VM display name | Y | Y |
Change power state of the VM | Y | Y |
Remove tag associations | Y | Y |
Restore to a different network | Y | Y |
To recover a VM
- On the left, click Cloud.
- Click the Virtual Machines tab.
All the discovered cloud assets for the respective category are displayed.
- Double-click the protected asset that you want recover.
- Click the Recovery points tab.
The available images are listed in rows with the backup timestamp for each image. For AWS workloads you can see replica as well as backup images, if available.
- In the Copies column, click the copy that you want to recover. You can see the backup, snapshot, and replica copy, if available. Click Recover. If you don't select a copy to restore, the primary copy is selected.
- Click Restore Virtual Machine.
- In the Recovery target page, do the following:
If you restore a backup copy, modify the values of these parameters as required:
Configuration: To restore to an alternate configuration, select one from the drop-down.
Region: To restore to an alternate region, select one from the drop-down.
Subscription: To restore to an alternate subscription, select one from the drop-down. For Azure and Azure Stack only.
Resource group: To restore to an alternate resource group, click the search icon, in the Select resource group dialog, select the required resource group. For Azure and Azure Stack only.
Display name: To change the display name, enter the new one in the field. The specified display name is validated during the pre-recovery check.
Note:
Except in AWS workloads, the following special characters are not allowed in the display name: ` ~ ! @ # $ % ^ & * ( ) = + _ [ ] { } \\ | ; : ' \" , < > / ?."
If you restore a snapshot copy, specify only the Resource group and the Display name.
- Click Next.
- In the Recovery options page:
If you restore a backup copy, to restore to a different region, select a Region. To select a network available in that region, click the search icon near Network configuration, and select a target network for recovery.
If you restore a snapshot copy, click the search icon in Network configuration, and select a target network for recovery. The list shows networks available in that region.
In the Advanced section:
To keep the VM powered on after recovery, select Power on after recovery.
To remove the tags associated with the asset at the time of backup or creating snapshot, select Remove tag associations.
Note:
If you do not select the Remove tag associations option, any tag value for assets should not have spaces, before and after a comma. After the restoration of an asset, the spaces before and after a comma in the tag values are removed. For example, the value for the tag name:created_on: Fri, 02-Apr-2021 07:54:59 PM , EDT, is converted to: Fri,02-Apr-2021 07:54:59 PM,EDT. You can manually edit the tag values to reinstate the spaces.
- Click Next. The pre-recovery check begins. This stage validates all the recovery parameters and displays errors, if any. You can fix the errors before starting the recovery.
- Click Start recovery.
The Restore activity tab shows the job progress.
For information on the recovery status codes, see the NetBackup administrator or the NetBackup Status Codes Reference Guide, available here:
http://www.veritas.com/docs/000003214
For GCP, when you restore a snapshot that was created before the upgrade, if the source disk is not present, a default restored disk, pd-standard is created.
To recover applications and volumes to the original location
- On the left, click Cloud.
- Click the Applications or Volumes tab.
All the discovered cloud assets for the respective category are displayed.
- Double-click on the protected asset that you want recover.
- Click the Recovery points tab. In the calendar view, click the date on which the backup occurred.
The available images are listed in rows with the backup timestamp for each image.
- On the top right for the preferred recovery point, select Original location.
- Click Start recovery.
- On the left, click Activity monitor to view the job status.
Considerations
For encrypted VM restore in AWS to an alternate location, the key-pair names must be same on the source and destination region. If not, create a new key-pair in the destination region that is consistent with the key-pair in the source region.
To recover applications and volumes to alternate location
- On the left, click Cloud.
- Click the Applications or Volumes tab.
All the discovered cloud assets for the respective category are displayed.
- Double-click on the protected asset that you want recover.
- Click the Recovery points tab. In the calendar view, click the date on which the backup occurred.
The available images are listed in rows with the backup timestamp for each image.
- On the top right for the preferred recovery point, select Alternate location.
- Select the location where you want to restore the cloud asset.
- Click Start recovery.
- On the left, click Activity monitor to view the job status.
The following table describes how NetBackup handles the restore/recovery of Google Cloud Platform VMs that have Read-only volumes.
Scenario | Handling |
---|---|
Restoring a volume from the snapshot of an attached Read-only disk (from the Volumes tab under Cloud workloads on the NetBackup Web UI) | During restore, the disk will be attached in the 'Read/write' mode to the original or alternate location. |
Restoring a VM (with a Read-only disk) from a crash-consistent snapshot (from the Virtual Machines tab under Cloud workloads on the NetBackup Web UI) | During restore of such a VM to its original or alternate location, a 'Read-only' disk will be restored in a 'Read/write' mode. |
Restoring a VM (with a Read-only disk) from an app-consistent snapshot (from the Virtual Machines tab under Cloud workloads on the NetBackup Web UI) | Even if a 'Read-only' disk can be attached to multiple VMs, it will be discovered under only one VM. For a Windows VM, the snapshot will fail with a VSS error, similar to the following: Failure: flexsnap.GenericError: Failed to take snapshot(error: Failed to create VSS snapshot of the selected volumes.)" For a Linux VM, the snapshot may or may not be successful for a VM under which the disk is discovered, but it will fail for other VMs due to the missing dependencies. Error example: linear_flow.Flow: create snapshot (test-win) of host linux-1(len=4)' requires ['snap_google-gcepd-us-west2-b-7534340043132122994'] but no other entity produces said requirements\n MissingDependencies In the above case, if a snapshot is successful for a Linux VM, a 'Read-only' disk will be restored in a 'Read/write' mode. |