Protecting cloud assets or intelligent groups for cloud assets
You can create cloud provider-specific protection plans for your cloud workloads. Then you can subscribe the assets that are associated with the cloud provider to a provider-specific protection plan.
Note:
If you previously had a protection plan that was applied to assets from different cloud providers, it is automatically converted to the new provider-specific format. This conversion happens after an upgrade to NetBackup 9.1. For example, if you had the assets from Google Cloud and AWS Cloud that are subscribed to one protection plan, then the protection plan is split. The protection plan is split into two separate protection plans for each provider.
section.
Use the following procedure to subscribe a cloud VM, application, volume, or an intelligent group to a protection plan. When you subscribe an asset to a protection plan, you assign predefined backup settings to the asset.
Note:
The RBAC role that is assigned to you must give you access to the assets that you want to manage and to the protection plans that you want to use.
To protect a cloud asset or an intelligent group
- On the left, click Workloads > Cloud.
- On the Virtual machines tab, or Applications tab, or Volumes tab or Intelligent groups tab, click the box for the asset or the asset group and click Add protection.
- Select a protection plan and click Next.
- You can adjust the following settings:
Schedules and retention
Storage options
For more information about storage options in the web UI, review the Configuring storage section in the NetBackup Web UI Administrator's Guide.
Backup options
- Click Protect.
Apart from the scheduled protection plans, you can also use the option to backup an asset immediately, to safeguard against any unplanned circumstances.
Select a cloud asset or an intelligent group and click .
Then select a protection plan to apply. Only the protection plans relevant to a specific cloud provider of the asset are displayed as options.
Click .
A backup job is triggered, which can be tracked on the Activity monitor page.
For more information, see NetBackup Web UI Administrator's Guide.
Note the following points concerning the automatic conversion of older protection plans to the new format.
Protection plan conversion starts when the asset migration is completed after the upgrade of NetBackup to 9.1 and later.
Old protection plans with no assets subscribed are not converted to the new format. You can manually delete them.
Before or during conversion
All the assets are unsubscribed from the old protection plan and subscribed to the converted protection plan.
No new assets can be subscribed to the old protection plan.
The Backup now operation fails for the old plan.
Customizing or editing the old protection plan is prevented.
After successful conversion
If the old protection plan was used to protect the assets from only one cloud provider, then the new plan retains the same name and asset subscription upon conversion.
If the old protection plan was used to protect the assets from multiple cloud providers, then the name of the old protection plan is retained as before. The protection plan name is updated to retain the asset subscription for any one cloud provider upon conversion.
For the other cloud providers that were part of the old plan, new protection plans are created upon conversion, and only the assets of respective providers are subscribed to them. New plans are named in the following format
<old_plan_name>_<cloud_provider>.Hence you may see more number of plans in your Protection Plans menu on the web UI than before.
Success messages are shown in the notifications as follows:
The protection plan <protectionPlanName> created during conversion to new format.
Successfully converted the protection plan <protectionPlanName> to the new format.
Then you can start managing and applying the converted protection plans as normal.
Failure scenarios
Refer to the following to know how the failure scenarios are handled during or after the conversion of protection plans. Also check the notifications for any failure alerts and take the necessary action.
Some of the assets might fail to get unsubscribed from the old protection plan. In that case, the conversion continues with the assets that are successfully unsubscribed. The conversion process for the assets that failed, is retried every 4 hours.
After the conversion, some of the assets might fail to get automatically re-subscribed to the new plan. In that case, you need to manually subscribe those assets to the converted protection plan.
Failure might be encountered when the required access permissions are assigned to the new, converted protection plan. In that case, you need to manually assign the access permissions.