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
 
Supported CloudPoint operations on Hitachi arrays
You can perform the following CloudPoint operations on the supported Hitachi storage arrays that are registered with Hitachi Configuration Manager (HCM):
Table: Supported CloudPoint operations on Hitachi arrays
CloudPoint operation  | Description  | 
|---|---|
Discover assets  | CloudPoint discovers all the Logical Devices (LDEV) created on the storage array. The primary LDEV objects appear as disk assets. The secondary LDEV objects that are part of a Thin Image (TI) pair appear under snapshots. One or more LDEV objects are grouped in a logical entity called as a pool. For the CloudPoint Hitachi plug-in to work, you must create a pool named   | 
Create snapshot  | NetBackup takes a snapshot of all the LDEV objects that are attached to a hostgroup. When CloudPoint takes a snapshot, it performs the following actions: 
  | 
Delete snapshot  | When CloudPoint deletes a snapshot, it performs the following actions: 
  | 
Restore snapshot  | CloudPoint performs a restore operation on a thin image snapshot of an LDEV. All the data in the primary LDEV is overwritten by the data from the secondary LDEV.  | 
Export snapshot  | When a snapshot export operation is triggered, CloudPoint searches for the target host based on the world wide name (WWN) or the iSCSI Qualified Name (IQN) specified in the export request. After the host is identified on the storage array, CloudPoint updates the path attribute of the secondary LDEV with the target host where the snapshot is to be exported. Once the target host is added to the secondary LDEV host ports, the exported snapshot is immediately visible on the target host.  | 
Deport snapshot  | When a snapshot deport operation is triggered, CloudPoint removes the target host from the secondary LDEV path attribute. Once the target host entry is removed from the secondary LDEV host ports, the exported snapshot is no longer visible on the target host and the deport operation is complete.  | 
Consider the following when you configure the Hitachi plug-in:
When you delete snapshots using CloudPoint, only the snapshots that are managed by CloudPoint are available for deletion. You cannot use CloudPoint to delete snapshots that are not created using CloudPoint.
The export operation is supported using the following protocols:
Fibre Channel (FC)
Internet Small Computer Systems Interface (iSCSI)