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
Meeting system requirements
The host on which you install CloudPoint must meet the following requirements.
See CloudPoint host sizing recommendations.
Table: Operating system and processor requirements for CloudPoint host
Category | Requirement |
|---|---|
Operating system |
|
Processor architecture | x86_64 /64-bit processors |
Table: System requirements for the CloudPoint host
Host on which CloudPoint is installed | Requirements |
|---|---|
Amazon Web Services (AWS) instance |
|
Microsoft Azure VM |
Ensure that do the following before you deploy CloudPoint on an RHEL instance in the Azure cloud:
|
Microsoft Azure Stack Hub VM |
Ensure that do the following before you deploy CloudPoint on an RHEL instance in the Azure Stack Hub cloud:
|
Google Cloud Platform (GCP) VM |
|
VMware VM |
|
Physical host (x86_64 / AMD64) |
|
Note:
NetBackup CloudPoint is not fully FIPS compliant.
CloudPoint uses the following file systems on the host to store all the container images and files during installation:
/(root file system)/var
The /var file system is further used for container runtimes. Ensure that the host on which you install or upgrade CloudPoint has sufficient space for the following components.
Table: Space considerations for CloudPoint components
Component | Space requirements |
|---|---|
CloudPoint containers | 30 GB free space |
CloudPoint agents and plug-ins | 350 MB free space, for every CloudPoint plug-in and agent configured |
Additionally, CloudPoint also requires a separate volume for storing CloudPoint data. Ensure that you create and mount this volume to /cloudpoint on the CloudPoint host.
Table: Space consideration for CloudPoint data volume
Volume mount path | Size |
|---|---|
| 50 GB or more |
See CloudPoint host sizing recommendations.
CloudPoint supports the following applications, operating systems, cloud, and storage platforms.
These assets are supported irrespective of how you configure CloudPoint, whether using the CloudPoint cloud or storage agents and plug-ins (earlier known as off-host plug-ins), or using the CloudPoint application configuration plug-ins (earlier known as on-host plug-ins), or using the CloudPoint agentless feature.
Table: Supported applications, operating systems, cloud, and storage platforms
Category | Support |
|---|---|
Applications |
Notes:
|
Operating systems on supported assets |
Note: CloudPoint agents are not supported on non-English operating systems. |
Cloud platforms |
|
Storage platforms |
|
Ensure that the time zone settings on the host where you wish to deploy CloudPoint are as per your requirement and synchronized with a public NTP server.
By default, CloudPoint uses the time zone that is set on the host where you install CloudPoint. The timestamp for all the entries in the logs are as per the clock settings of the host machine.
If the instance on which you are deploying CloudPoint is behind a proxy server, that is, if the CloudPoint instance connects to the internet using a proxy server, you must specify the proxy server details during the CloudPoint installation. The CloudPoint installer stores the proxy server information in a set of environment variables that are specific for the CloudPoint containers.
The following table displays the environment variables and the proxy server information that you must provide to the CloudPoint installer. Make sure you keep this information ready; you are required to provide these details during CloudPoint installation.
Table: Proxy server details required by CloudPoint
Environment variables created by CloudPoint installer | Description |
|---|---|
VX_HTTP_PROXY | Contains the HTTP proxy value to be used for all connections. For example, |
VX_HTTPS_PROXY | Contains the HTTPS proxy value to be used for all connections. For example, |
VX_NO_PROXY | Contains the hosts that are allowed to bypass the proxy server. For example, |
CloudPoint services that need to communicate externally via a proxy server use these predefined environment variables that are set during the CloudPoint installation.