Veritas NetBackup™ CloudPoint Install and Upgrade Guide
- Section I. CloudPoint installation and configuration
- Preparing for CloudPoint installation
- About the deployment approach
 - Deciding where to run CloudPoint
 - About deploying CloudPoint in the cloud
 - Meeting system requirements
 - CloudPoint host sizing recommendations
 - Creating an instance or preparing the physical host to install CloudPoint
 - Installing Docker
 - Creating and mounting a volume to store CloudPoint data
 - Verifying that specific ports are open on the instance or physical host
 
 - Deploying CloudPoint using the Docker image
 - CloudPoint cloud plug-ins
 - CloudPoint storage array plug-ins
- NetApp plug-in configuration notes
 - Nutanix Files plug-in configuration notes
 - Dell EMC Unity array plug-in configuration parameters
 - Pure Storage FlashArray plug-in configuration notes
 - HPE RMC plug-in configuration notes
 - Hitachi plug-in configuration notes
 - InfiniBox plug-in configuration notes
 - How to configure the CloudPoint storage array plug-ins?
 
 - CloudPoint application agents and plug-ins
- Microsoft SQL plug-in configuration notes
 - Oracle plug-in configuration notes
 - MongoDB plug-in configuration notes
 - About the installation and configuration process
 - Preparing to install the Linux-based agent
 - Preparing to install the Windows-based agent
 - Downloading and installing the CloudPoint agent
 - Registering the Linux-based agent
 - Registering the Windows-based agent
 - Configuring the CloudPoint application plug-in
 - Configuring VSS to store shadow copies on the originating drive
 - Creating a NetBackup protection plan for cloud assets
 - Subscribing cloud assets to a NetBackup protection plan
 - About snapshot restore
 - Restore requirements and limitations for Microsoft SQL Server
 - Restore requirements and limitations for Oracle
 - Restore requirements and limitations for MongoDB
 - Steps required before restoring SQL AG databases
 - Recovering a SQL database to the same location
 - Recovering a SQL database to an alternate location
 - Additional steps required after a SQL Server snapshot restore
 - Additional steps required after restoring SQL AG databases
 - SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the CloudPoint host
 - Disk-level snapshot restore fails if the original disk is detached from the instance
 - Additional steps required after a MongoDB snapshot restore
 - Additional steps required after an Oracle snapshot restore
 - Additional steps required after restoring an AWS RDS database instance
 
 - Protecting assets with CloudPoint's agentless feature
 
 - Preparing for CloudPoint installation
 - Section II. CloudPoint maintenance
 
Microsoft Azure plug-in configuration notes
The Microsoft Azure plug-in lets you create, delete, and restore snapshots at the virtual machine level and the managed disk level.
Before you configure the Azure plug-in, complete the following preparatory steps:
Use the Microsoft Azure Portal to create an Azure Active Directory (AAD) application for the Azure plug-in.
Assign the service principal to a role to access resources.
For more details, follow the steps in the following Azure documentation:
Table: Microsoft Azure plug-in configuration parameters
CloudPoint configuration parameter  | Microsoft equivalent term and description  | 
|---|---|
Tenant ID  | The ID of the AAD directory in which you created the application.  | 
Client ID  | The application ID.  | 
Secret Key  | The secret key of the application.  | 
Regions  | One or more regions in which to discover cloud assets. Note: If you configure a government cloud, select US Gov Arizona, US Gov Texas US, or Gov Virginia.  | 
Resource Group prefix  | The string with which you want to append all the resources in a resource group.  | 
Protect assets even if prefixed Resource Groups are not found  | The check box determines whether the assets are protected if they are not associated to any resource groups  | 
Consider the following before you configure the Azure plug-in:
The current release of the plug-in does not support snapshots of blobs.
CloudPoint currently only supports creating and restoring snapshots of Azure-managed disks and the virtual machines that are backed up by managed disks.
CloudPoint does not support disk-based protection for applications that store data on virtual disks or storage spaces that are created from a storage pool. While taking snapshots of such applications, the disk-based option is not available.
CloudPoint does not support snapshot tagging for assets in the Azure cloud environment. Even though Azure supports a maximum of up to 15 tags per snapshot, you cannot assign tags to snapshots, either manually using the APIs or via a protection policy, using CloudPoint.
CloudPoint does not support snapshot operations for Ultra SSD disk types in an Azure environment. Even though CloudPoint discovers the ultra disks successfully, any snapshot operation that is triggered on such disk assets fails with the following error:
Snapshots of UltraSSD_LRS disks are not supported.
If you are creating multiple configurations for the same plug-in, ensure that they manage assets from different Tenant IDs. Two or more plug-in configurations should not manage the same set of cloud assets simultaneously.
CloudPoint currently does not block you from creating such a configuration. If there is an overlap of cloud assets between plug-in configurations, you may have to resolve the configuration issue by deleting such plug-in configurations and adding them again, ensuring that there are no overlapping assets.
However, CloudPoint does not allow you to delete a plug-in configuration if there are any snapshots associated with the assets in that configuration.
When you create snapshots, the Azure plug-in creates an Azure-specific lock object on each of the snapshots. The snapshots are locked to prevent unintended deletion either from the Azure console or from an Azure CLI or API call. The lock object has the same name as that of the snapshot. The lock object also includes a field named "
notes" that contains the ID of the corresponding VM or asset that the snapshot belongs to.You must ensure that the "
notes" field in the snapshot lock objects is not modified or deleted. Doing so will disassociate the snapshot from its corresponding original asset. It will also disable the Overwrite existing restore option for the snapshots that are created in CloudPoint 2.2.1 or later.The Azure plug-in uses the ID from the "
notes" fields of the lock objects to associate the snapshots with the instances whose source disks are either replaced or deleted, for example, as part of a in-place restore operation. Therefore, if you have upgraded to NetBackup 2.2.1 release, then the Overwrite existing restore option will not be available for the snapshots that are created using an older version of CloudPoint.Azure plug-in supports the following GovCloud (US) regions:
US Gov Arizona
US Gov Texas
US Gov Virginia
CloudPoint Azure plug-in does not support the following Azure regions:
Location
Region
US
US DoD Central
US DoD East
US Sec West
China
CloudPoint does not support any regions in China.
China East
China East 2
China North
China North 2
Germany
Germany Central (Sovereign)
Germany Northeast (Sovereign)