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
- CloudPoint extension sizing recommendations
- Creating an instance or preparing the host to install CloudPoint
- Installing container platform (Docker, Podman)
- Creating and mounting a volume to store CloudPoint data
- Verifying that specific ports are open on the instance or physical host
- Preparing CloudPoint for backup from snapshot jobs
- Deploying CloudPoint using container images
- Deploying CloudPoint extensions
- Before you begin installing CloudPoint extensions
- Downloading the CloudPoint extension
- Preparing to install the extension on a VM
- Installing the CloudPoint extension on a VM
- Preparing to install the extension on a managed Kubernetes cluster (AKS) in Azure
- Preparing to install the extension on a managed Kubernetes cluster (EKS) in AWS
- Install extension using the Kustomize and CR YAMLs
- Installing the CloudPoint extension on Azure (AKS)
- Installing the CloudPoint extension on AWS (EKS)
- Managing the extensions
- CloudPoint cloud plug-ins
- CloudPoint storage array plug-ins
- How to configure the CloudPoint storage array plug-ins?
- NetApp plug-in configuration notes
- ACL configuration on NetApp array
- Nutanix Files plug-in configuration notes
- Configuring ACL for Nutanix array
- Dell EMC Unity array plug-in configuration notes
- FUJITSU AF/DX plug-in configuration notes
- NetApp NAS plug-in configuration notes
- Dell EMC PowerStore plug-in configuration notes
- Dell EMC PowerStore NAS plug-in configuration notes
- Dell EMC PowerFlex plug-in configuration notes
- Dell EMC XtremIO SAN plug-in configuration notes
- Pure Storage FlashArray plug-in configuration notes
- Pure Storage FlashBlade plug-in configuration notes
- IBM Storwize plug-in configuration notes
- HPE RMC plug-in configuration notes
- HPE XP plug-in configuration notes
- Hitachi plug-in configuration notes
- Hitachi (HDS VSP 5000) plug-in configuration notes
- InfiniBox plug-in configuration notes
- Dell EMC PowerScale (Isilon) plug-in configuration notes
- Dell EMC PowerMax and VMax 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
- 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
- Restore requirements and limitations for Microsoft SQL Server
- Restore requirements and limitations for Oracle
- Additional steps required after an Oracle snapshot restore
- 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 restoring an AWS RDS database instance
- Protecting assets with CloudPoint's agentless feature
- Volume Encryption in NetBackup CloudPoint
- CloudPoint security
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
- CloudPoint logging
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Preparing to uninstall CloudPoint
- Backing up CloudPoint
- Unconfiguring CloudPoint plug-ins
- Unconfiguring CloudPoint agents
- Removing the CloudPoint agents
- Removing CloudPoint from a standalone Docker host environment
- Removing CloudPoint extensions - VM-based or managed Kubernetes cluster-based
- Restoring CloudPoint
- Troubleshooting CloudPoint
Dell EMC XtremIO SAN plug-in configuration parameters
Specify the following parameters when you configure the Dell EMC XtremIO SAN plug-in:
Table: Dell EMC XtremIO SAN plug-in configuration parameters
CloudPoint configuration parameter | Description |
|---|---|
Plugin ID | Provide a name for the plugin. |
FQDN/ IP Address | The array's IP address, in IPV4 / FQDN format. |
User name | A user account that has permissions to perform snapshot operations on the Dell EMC XtremIO SAN array. |
Password | Provide a password to the user account. |
The following screen is displayed when you configure the plug-in using the NetBackup Administration Console:
The following considerations and limitations are applicable:
All the snapshot which are taken for any volume are read-only mode. There is a new re-purpose copy cloned from the volume which is used for data backup.
The re-purpose clone copy is only done in the export operation not in the create snapshot directly.
The repurpose clone copy is deleted based on the scheduled deport from NetBackup or manually triggering the expire operation. This is a thin provisioned type copy.
The limit for any volume name is 128 characters on the array. So, a user can have the maximum length of volume name is 128 - (23 (NB<unique_21digit_number>) - 9 (Repurpose) - 2 (Dot notations)) = 94. It is a strict requirement to limit the volume name to 94 characters for a successful snapshot creation.
It is strictly advised, not to write the data to repurpose copy created by NetBackup through manual mapping it on to the host server. User created re-purpose copies are considered as an individual volume in NetBackup. But changing the copies starting with volume_name.NB<unique_21digit_number>.repurpose is strictly not recommended.
Don't refresh the repurpose copy, as it changes the data from the parent volume and backup, and restore operations.
For example: If you have a volume V1 and a snapshot is triggered for the same then the protection copy occurs with the V1.NB<unique_21digit_number> format and in the export operation, a repurpose copy occurs with the name V1.NB<unique_21digit_number>.repurpose.