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
- How to configure the 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
- Dell EMC PowerScale (Isilon) plug-in configuration notes
- Qumulo plug-in configuration notes
- 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
- Volume Encryption in NetBackup
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
- CloudPoint logging
- Troubleshooting CloudPoint
- Restarting CloudPoint
- Troubleshooting CloudPoint logging
- CloudPoint agent fails to connect to the CloudPoint server if the agent host is restarted abruptly
- CloudPoint agent registration on Windows hosts may time out or fail
- Disaster recovery when DR package is lost or passphrase is lost
- Agentless log file name changed
- Upgrading CloudPoint
- Uninstalling CloudPoint
Supported CloudPoint operations on Dell EMC PowerScale (Isilon) plug-in
CloudPoint performs the following management operations on the Dell EMC PowerScale (Isilon):
Table: CloudPoint operations on Dell EMC PowerScale (Isilon) plug-in
CloudPoint operation | Description |
|---|---|
Discover assets | CloudPoint discovers all the NFS exports and their snapshots along with some of their metadata. Note: CloudPoint only discovers assets with depth as 2. For example, if on NFS exports you have: ["/ifs", "/ifs/test_fs1", "/ifs/test_fs2", "/ifs/test_fs1/test_data", "/ifs/smb_03/test_data/dir01"] so NFS exports discovered in cloudpoint are ["/ifs/test_fs1", "/ifs/test_fs2"]. |
Create snapshot | To create a snapshot, CloudPoint triggers a POST REST API call on the nfs_export with the required information and the snapshot name. The API returns the details of the snapshot. A typical snapshot created by CloudPoint has the following naming convention: NB<unique_21digit_number> |
Delete snapshot | To delete a snapshot, CloudPoint triggers a DELETE REST API call with the required snapshot details and confirms that the snapshot has been deleted successfully on the Cluster. |
Restore snapshot | CloudPoint is uses the JobAPI to revert a snapshot. To revert a snapshot that contains a directory, it is recommended that you create a SnapRevert domain for a directory. To revert a snapshot, perform the following steps:
|
Export snapshot | When a snapshot export operation is triggered, a new NFS export is created over the snapshot path ("/ifs/test_fs/.snapshot/NB15985918570166499611/") and the backup host is added as a Root Client with the read-only permission. |
Deport snapshot | When a snapshot deport operation is triggered, CloudPoint deletes the NFS export created over the snapshot path at the time of the export operation. |
Create snapshot diff | CloudPoint use the JobAPI to create a changelist between snapshots. To create a changelist, perform the following steps:
Note: The following important points:
|