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 InfiniBox arrays
CloudPoint supports the following operations on the InfiniBox storage arrays:
Table: Supported CloudPoint operations on InfiniBox arrays
CloudPoint operation | Description |
|---|---|
Discover assets | CloudPoint discovers all the SAN volumes (virtual disks) that are part of storage pools that are created on the InfiniBox storage array. The plug-in sends a request to the array to return a list of all the volumes that have the type set as To discover snapshot objects, the plug-in sends a request to the array to return a list of all the volumes that have the type set as InfiniBox arrays support creating a snapshot of a snapshot. The depth attribute identifies the snapshot type. A snapshot depth value greater than 1 indicates that it is a snapshot of an existing snapshot. CloudPoint does not support discovery and operations on snapshot volumes that have a depth value other than 1. |
Create snapshot | CloudPoint takes a snapshot of all the SAN volumes that are part of a storage pool. When a snapshot is created, CloudPoint plug-in uses InfiniSDK to send a The InifiniBox array creates a snapshot volume, sets the type as |
Delete snapshot | When a snapshot is deleted, CloudPoint plug-in sends a |
Restore snapshot | When a snapshot restore operation is triggered, CloudPoint first gets details about the parent volume that is associated with the snapshot that is being restored. CloudPoint plug-in then sends the The array uses the selected snapshot to perform the restore on the parent volume. All the data in the parent volume is overwritten by the data in the snapshot volume. |
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, CloudPoint plug-in sends a The InfiniBox array returns a LUN ID as a response to the restore request. CloudPoint stores the LUN ID and the target host ID mapping information internally in the CloudPoint database.
The export operation also creates a new virtual asset of type |
Deport snapshot | When a snapshot deport operation is triggered, CloudPoint first gets the target host ID from the database. The CloudPoint plug-in then sends a |
Consider the following when you configure the InfiniBox plug-in:
The InfiniBox plug-in supports discovery and snapshot operations only on volume snapshots that have the depth attribute value set to 1. Volume snapshots that have the depth attribute value other than 1 are not supported.
All parent volume objects and snapshot objects on an InfiniBox array are unique. While creating a snapshot of a volume, if an object with the same name already exists on the array, the create operation fails. You must ensure that the snapshot names are unique.
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 snapshot export operation is supported using the following protocols:
Fibre Channel (FC)
Internet Small Computer Systems Interface (iSCSI)