Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- About CloudPoint support for AWS IAM roles
- About the CloudPoint AWS CloudFormation template
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Setting up email and adding users
- Assigning roles to users for greater efficiency
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
- Storage array support
- Dell EMC Unity arrays
- Pure Storage FlashArray
- Working with CloudPoint using APIs
- Storage array support
Meeting system requirements
The host on which you install CloudPoint must meet the following requirements.
Table: Operating system and processor requirements for CloudPoint host
The mount state for the root file system (
x86_64 / AMD64 / 64-bit processors
Table: System requirements for the CloudPoint host
Host on which CloudPoint is installed
Amazon Web Services (AWS) instance
Microsoft Azure VM
Google Cloud Platform (GCP) VM
(x86_64 / AMD64)
CloudPoint uses the following file systems on the host to store all the container images and files during installation:
/(root file system)
/var file system is further used for container runtimes. Ensure that the host on which you install CloudPoint has sufficient space for the following components.
Table: Space considerations for CloudPoint components
CloudPoint Docker containers
CloudPoint on-host agent and plug-ins
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
50 GB or more
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 plugins (earlier known as off-host plug-ins), or using the CloudPoint application configuration plugins (earlier known as on-host plug-ins), or using the CloudPoint agentless feature.
Table: Supported applications, operating systems, cloud, and storage platforms
Operating systems on supported assets
CloudPoint agents are not supported on non-English operating systems.
Starting with CloudPoint 2.2 release, the CloudPoint plug-in for HPE 3PAR has been deprecated. Support for this plug-in configuration is no longer available.
To allow CloudPoint to discover and protect AWS Nitro-based Windows instances that use NVMe EBS volumes, ensure that the AWS NVMe tool executable file,
ebsnvme-id.exe, is present in any of the following locations on the AWS Windows instance:
This is the default location for most AWS instances.
Manually download and copy the executable file to this location.
System PATH environment variable
Add or update the executable file path in the system's PATH environment variable.
If the NVMe tool is not present in one of the mentioned locations, CloudPoint may fail to discover the file systems on such instances.
You may see the following error in the logs:
"ebsnvme-id.exe" not found in expected paths!"
For the latest information on features, software, and hardware support, refer to the compatibility lists:
Table: CloudPoint compatibility lists
Cloud Application Compatibility List (ACL)
Hardware Compatibility List (HCL)
CloudPoint supports the following browsers for accessing the CloudPoint user interface.
Table: Supported browsers
75.0.3770.100 or later
52.0.0 or later
CloudPoint only runs on desktop devices. Mobile devices are not supported.
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.
However, the date and time for the operations and tasks in the CloudPoint user interface (UI) might reflect the browser time that corresponds to the local system from where the browser is launched.
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.
Table: Proxy server details required by CloudPoint describes 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
Contains the HTTP proxy value to be used for all connections. For example,
Contains the HTTPS proxy value to be used for all connections. For example,
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. For example, the CloudPoint email service, the CloudPoint notifications service, and the CloudPoint plug-in agent containers.
Proxy server limitations
The following restrictions are applicable:
If CloudPoint is deployed using proxy server settings, email configuration using SendGrid and SMTP are not supported.
However, email configuration using Amazon Simple Email Service (SES) is supported.
CloudPoint deployment using AWS CloudFormation Template (CFT) does not support proxy server configuration.