Meeting system requirements

CloudPoint host requirements

The host on which you install CloudPoint must meet the following requirements.

Table: Operating system and processor requirements for CloudPoint host

Category	Requirement
Operating system	Ubuntu 16.04 and 18.04 Server LTS Red Hat Enterprise Linux (RHEL) 7.x
Processor architecture	x86_64 / AMD64 / 64-bit processors

Table: System requirements for the CloudPoint host

Host on which CloudPoint is installed	Requirements
Amazon Web Services (AWS) instance	Elastic Compute Cloud (EC2) instance type: t3.large vCPUs: 2 RAM: 16 GB Root disk: 64 GB with a solid-state drive (GP2) Data volume: 50 GB Elastic Block Store (EBS) volume of type GP2 with encryption for the snapshot asset database; use this as a starting value and expand your storage as needed.
Microsoft Azure VM	Virtual machine type: D2s_V3 Standard CPU cores: 2 RAM: 16 GB Root disk: 64 GB SSD Data volume: 50 GB Premium SSD for the snapshot asset database; storage account type Premium_LRS; set Host Caching to Read/Write. Ensure that do the following before you deploy CloudPoint on an RHEL instance in the Azure cloud: Register the RHEL instance with Red Hat using Red Hat Subscription Manager Extend the default LVM partitions on the RHEL instance so that they fulfil the minimum disk space requirement
Google Cloud Platform (GCP) VM	Virtual machine type: n1-standard-2 vCPUs: 2 RAM: 16 GB Boot disk: 64 GB standard persistent disk, Ubuntu 16.04 Server LTS Data volume: 50 GB SSD persistent disk for the snapshot asset database with automatic encryption
VMware VM	Virtual machine type: 64-bit with a CloudPoint supported operating system vCPUs: 8 RAM: 16 GB or more Root disk: 64 GB with a standard persistent disk Data volume: 50 GB for the snapshot asset database
Physical host (x86_64 / AMD64)	Operating system: A 64-bit CloudPoint supported operating system CPUs: x86_64 (64-bit), single-socket, multi-core, with at least 8 CPU count RAM: 16 GB or more Boot disk: 64 GB Data volume: 50 GB for the snapshot asset database

Disk space requirements

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 Docker containers	10 GB
CloudPoint agents and plug-ins	350 MB 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
`/cloudpoint`	50 GB or more

Applications, operating systems, cloud, and storage platforms supported by CloudPoint agents and plug-ins

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	File systems Linux native file systems: ext3, ext4, and XFS Microsoft Windows: NTFS Microsoft SQL 2014, SQL 2016, SQL 2017 See Microsoft SQL plug-in configuration notes. MongoDB Enterprise Edition 3.6 See MongoDB plug-in configuration notes. Oracle 12c, Oracle 12c R1, Oracle 18c Single node configurations are supported. See Oracle plug-in configuration notes. Notes: Oracle database applications are not supported in a Google Cloud Platform (GCP) cloud environment. This is a limitation imposed by the companies owning these products and services, and is currently outside the scope of CloudPoint. CloudPoint does not support application-consistent snapshots on ext2 file systems. CloudPoint does not support Microsoft SQL Server workloads in a GCP cloud environment.
Operating systems on supported assets	Red Hat Enterprise Linux (RHEL) 7.x Windows Server 2012, 2012 R2, and Windows Server 2016 Note: CloudPoint agents are not supported on non-English operating systems.
Cloud platforms	Amazon Web Services (AWS) If you wish to protect applications, the applications must be hosted on a t2.large or a higher specification AWS instance type. CloudPoint currently does not support applications that are running on t2.medium or a lower instance type. For protecting Microsoft Windows-based applications, use t2.xlarge or t3.xlarge or a higher specification instance type. Microsoft Azure If you wish to protect applications, the applications must be hosted on a D2s_V3 Standard or a higher specification Azure virtual machine type. For protecting Microsoft Windows-based applications, use B4ms or D4s_V3 or a higher specification virtual machine. Note: The CloudPoint Azure plug-in supports disks of type Premium_LRS, Standard_LRS, and StandardSSD_LRS. All other disk types are defaulted to Standard_LRS during snapshot restore operations. Google Cloud Platform (GCP) If you wish to protect applications, the applications must be hosted on a n1-standard-2 or a higher specification GCP virtual machine type.
Storage platforms	NetApp storage arrays See NetApp plug-in configuration notes. Dell EMC Unity arrays See Dell EMC Unity array plug-in configuration parameters. HPE storage arrays See HPE RMC plug-in configuration notes. Pure Storage FlashArray See Pure Storage FlashArray plug-in configuration notes. Hitachi storage arrays See Hitachi plug-in configuration notes. InfiniBox enterprise arrays See InfiniBox plug-in configuration notes.

Note:

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:

%PROGRAMDATA%\Amazon\Tools
This is the default location for most AWS instances.
%PROGRAMFILES%\Veritas\Cloudpoint
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!"
```

CloudPoint time zone

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.

Proxy server requirements

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, `"http://proxy.mycompany.com:8080/"`.
VX_HTTPS_PROXY	Contains the HTTPS proxy value to be used for all connections. For example, `"https://proxy.mycompany.com:8080/"`.
VX_NO_PROXY	Contains the hosts that are allowed to bypass the proxy server. For example, `"localhost,mycompany.com,192.168.0.10:80"`.

CloudPoint services that need to communicate externally via a proxy server use these predefined environment variables that are set during the CloudPoint installation.

Meeting system requirements

Feedback

Feedback