Supported platforms

• 1: Vertica server and Management Console
• 2: Client drivers support
• 2.1: Perl driver requirements
• 2.2: Python driver requirements
• 3: Vertica SDKs
• 4: FIPS 140-2 supported platforms
• 5: Eon on-premises storage
• 6: Vertica on Amazon Web Services
• 7: Containerized environments
• 8: Virtualized environments
• 9: Hadoop integrations
• 10: Apache Kafka integrations
• 11: Apache Spark integrations
• 12: Linux volume manager (LVM)
• 13: End-of-support notices

1 - Vertica server and Management Console

Operating systems and versions

OpenText supports the Vertica Analytic Database 23.4.x running on the following 64-bit operating systems and versions on x86_x64 architecture.

In general, OpenText provides support for the Vertica Analytic Database, not its host operating system, hardware, or other environmental elements. However, OpenText makes an effort to ensure the success of its customers on recent versions of the following popular operating systems for the x86_64 architecture.

When there are multiple minor versions supported for a major operating system release, OpenText recommends that you run Vertica on the latest minor version listed in the supported versions list. For example, if you run Vertica on a Red Hat Enterprise Linux 8.x release, OpenText recommends you upgrade to or be running the latest supported RHEL 8.x release.

Recommended storage format types

Choose the storage format type based on deployment requirements. Vertica recommends the following storage format types where applicable:

• ext3

• ext4

• NFS for backup

• XFS

• Amazon S3 Standard, Azure Blob Storage, or Google Cloud Storage for communal storage and related backup tasks when running in Eon Mode

The storage format type at your backup and temporary directory locations must support fcntl lockf (POSIX) file locking.

You can view the file systems in use on your nodes by querying the system table STORAGE_USAGE.

Vertica users have successfully deployed other file systems, Vertica cannot guarantee or desired outcomes on all storage format types. In certain support situations, you may be asked to migrate to a recommended storage format type to help with troubleshooting or to fix an issue.

Vertica Analytic Database supports Linux Volume Manager (LVM) on all supported operating systems. Your LVM version must be 2.02.66 or later, and must include device-mapper version 1.02.48 or later. For information on requirements and restrictions, see the section, Vertica Support for LVM.

Network address family support

Vertica server supports IPv4 and IPv6 network addresses for both internal and external communications. The database cluster uses IPv4 by for internal communications by default. You can choose to have the cluster use IPv6 for its internal communications when you install Vertica and create the cluster.

Vertica supports using IPv6 to identify nodes in the database cluster. However, AWS DNS resolution does not support IPv6. To have a cluster in AWS that uses IPv6, use the IPv6 IP addresses instead of using host names when installing Vertica and forming the cluster.

Currently, Vertica does not support using IPv6 on Google Cloud Platform or Microsoft Azure.

The MC currently does not support IPv6. If your Vertica database uses IPv6 for internal communications, the MC will not be able to connect to or manage the database. The MC must communicate with the database cluster using its own internal network addresses.

Supported browsers for Management Console

Vertica Analytic Database 23.4.x Management Console is supported on the following web browsers:

• Chrome
• Firefox
• Microsoft Edge

Vertica server and Management Console compatibility

Management Console (MC) 23.4.x is compatible with all supported Vertica server versions.

2 - Client drivers support

Vertica provides JDBC, ODBC, OLE DB, Python, vsql, and ADO.NET client drivers. Download the latest drivers from Vertica Client Drivers. Choose from drivers for the following platforms:

To view a list of driver and server version compatibility, see Client driver and server version compatibility.

ADO.NET Driver

The ADO.NET and OLE DB drivers are supported on the following platforms:

OLE DB Driver

The ADO.NET and OLE DB drivers are supported on the following platforms:

JDBC driver

All non-FIPS JDBC drivers are supported on any Java 8-compliant platform or later (Java 8 is the minimum).

ODBC driver

Vertica Analytic Database provides both 32-bit and 64-bit ODBC drivers. Vertica 23.4.x ODBC drivers are supported on the following platforms:

vsql client

The Vertica vsql client is included in all client packages. It is not available as a separate download. The vsql client is supported on the following platforms:

2.1 - Perl driver requirements

To use Perl with Vertica, you must install the Perl driver modules (DBI and DBD::ODBC) and a Vertica ODBC driver on the machine where Perl is installed. The following table lists the Perl versions supported with Vertica 23.4.x.

Later versions of Perl (5.10 and above), DBI, and DBD::ODBC might also work.

2.2 - Python driver requirements

To use Python with Vertica, you must install either:

• The vertica-python client.

• The pyodbc module.

For details, see Installing Python client drivers.

The following table lists compatible versions of Python, the Python drivers, and ODBC.

3 - Vertica SDKs

This section details software requirements for running User Defined Extensions (UDxs) developed using the Vertica SDKs.

C++ SDK

The Vertica cluster does not have any special requirements for running UDxs written in C++.

Java SDK

Your Vertica cluster must have a Java runtime installed to run UDxs developed using the Vertica Java SDK. Vertica has tested the following Java Runtime Environments (JREs) with this version of the Vertica Java SDK:

• Oracle Java Platform Standard Edition 6 (version number 1.6)

• Oracle Java Platform Standard Edition 7 (version number 1.7)

• Oracle Java Platform Standard Edition 8 (version number 1.8)

• OpenJDK 6 (version number 1.6)

• OpenJDK 7 (version number 1.7)

• OpenJDK 8 (version number 1.8)

Python SDK

The Vertica Python SDK does not require any additional configuration or header files.

R language pack

The Vertica R Language Pack provides version 3.5 of the R runtime and associated libraries for interfacing with Vertica. You install the R Language Pack on the Vertica server.

4 - FIPS 140-2 supported platforms

Vertica uses a certified OpenSSL FIPS 140-2 cryptographic module to meet the security standards set by the National Institute of Standards and Technology (NIST) for Federal Agencies in the United States or other countries. Vertica links with the version of OpenSSL on the system to perform cryptographic operations at run time. When operating in FIPS mode, Vertica relies on the operating system's FIPS configuration to ensure a FIPS-certified version of OpenSSL is present in the environment.

OpenText can support Vertica in FIPS mode on Red Hat Enterprise Linux (RHEL) versions 9.2 and higher with FIPS-compliant versions of OpenSSL 3.0. OpenSSL version 1.1.1k is not supported. For information on downloading FIPS-compliant libraries, see the OpenSSL documentation.

FIPS-enabled Vertica requires the following:

• A user-generated certificate signed by an approved Certificate Authority.

• TLS 1.2 to support the server-client connection for a FIPS-enabled system.

Supported drivers

Vertica supports the following client drivers for FIPS-compliance:

• vsql

• ODBC

• JDBC

For more information see Federal information processing standard.

5 - Eon on-premises storage

Vertica supports the following storage platforms for Vertica Eon Mode running on-premises.

Pure Storage FlashBlade

Vertica supports communal storage on Pure Storage FlashBlade version 3.0.0 and later. See Create an Eon Mode database on-premises with FlashBlade for more information.

Vertica does not support the use of Vertica Management Console or admintools to administer data located on Pure Storage hardware.

For information on configuring Pure Storage, refer to support.purestorage.com.

MinIO

Vertica supports communal storage on MinIO version 2018-12-27T18:33:08Z and later. See Create an Eon Mode database on-premises with MinIO for more information.

Vertica does not support the use of Vertica Management Console or admintools to administer data located on MinIO.

See the MinIO website for more information about MinIO.

HDFS

Vertica supports communal storage on HDFS when accessed through WebHDFS. See Create an Eon Mode database on-premises with HDFS for more information.

For HDFS, Vertica does not support the following:

• The MapR distribution of HDFS, which is accessed through an NFS mount point and not through WebHDFS.

• Using Vertica Management Console or admintools to administer data located on HDFS.

• Cloudera (CDH) versions 5.x in Eon Mode.

• The copycluster vbr backup and restore utility for communal storage on HDFS.

Other validated object storage

The preceding sections detail storage platforms and versions that Vertica engineering tests under specific performance and load thresholds. In addition to these storage platforms, the Vertica Partner Engineering team validates object storage platforms that meet strict performance requirements.

For details, see On-Premises.

6 - Vertica on Amazon Web Services

For information about deploying Vertica on Amazon Web Services (AWS), see Vertica on Amazon Web Services.

AWS instance types

Vertica supports a range of AWS instance types to deploy cluster hosts or MC hosts on AWS. See Supported AWS instance types for a complete list of supported instance types.

Amazon machine images

Vertica provides tested and pre-configured Amazon Machine Images (AMIs) to deploy cluster hosts or MC hosts on AWS. The Vertica AMI allows users to configure their own storage using the officially supported version of Vertica Analytic Database for AWS.

See Choose a Vertica AMI Operating Systems for a list of operating systems currently available in Vertica AMIs.

Consider the following when using the Vertica AMI:

• Vertica develops AMIs on a slightly different schedule than the product release schedule. The AMIs for Vertica releases are available sometime following the initial release of Vertica software.

• Each Vertica AMI comes pre-configured with default resource limit settings.

• Amazon does not support using 32-bit binaries on Amazon Linux 2.0 AMIs. Therefore, you cannot use the Vertica 32-bit client libraries on these AMIs.

IPv6 support

Vertica supports using IPv6 to identify nodes in the database cluster. However, AWS DNS resolution does not support IPv6. To have a cluster in AWS that uses IPv6, use the IPv6 IP addresses instead of using host names when installing Vertica and forming the cluster.

7 - Containerized environments

Vertica supports running in any containerized environment that conforms to the performance requirements for vioperf, vnetperf, and vcpuperf.

As Vertica extends our support and deployment in containerized environments including Kubernetes, we cannot test and certify all possible configurations. However, OpenText makes an effort to ensure the success of its customers on recent versions of supported operating systems for the x86_64 architecture.

Vertica tests containers running on Docker. When the underlying hardware, OS, and container are configured correctly, the database system performs well. In some circumstances, there is a minor performance difference for queries made against a cold- or partially-populated depot when accessing communal storage.

Because your Vertica support contract covers Vertica products only, if you choose to run Vertica on a container configuration and you experience an issue that might not be caused by Vertica products, the Vertica Support team might ask you to reproduce the issue in a different environment, or engage with the support resources for your containerization technology.

For guidelines on how to provision and size your Kubernetes resources for Vertica deployments, see Recommendations for Sizing Vertica Nodes and Clusters in the Vertica Knowledge Base.

VerticaDB operator and Vertica server version support

The VerticaDB operator supports Vertica server versions 11.0.0 and higher.

Container orchestration version support

Communal storage support

Containerized Vertica on Kubernetes supports the following public and private cloud providers:

• Amazon Web Services S3

• S3-compatible storage, such as MinIO

• Google Cloud Storage

• Azure Blob Storage

• Hadoop File Storage

Managed Kubernetes services support

Vertica supports the following managed Kubernetes services:

• Amazon Elastic Kubernetes Service (EKS)

• Google Kubernetes Engine (GKE)

• Azure Kubernetes Service (AKS)

Cluster management platform support

Vertica supports the Vertica DB operator and Vertica on Kubernetes environment on Red Hat OpenShift versions 4.8 and higher.

8 - Virtualized environments

Vertica supports running in any virtualized environment that conforms to the performance requirements for vioperf, vnetperf, and vcpuperf.

Vertica does not support VM Snapshot.

Vertica has tested VMware, and when the underlying hardware is configured correctly, VMWare performs well. Customers have also deployed other virtualization configurations successfully. If you choose to run Vertica on a different virtualization configuration and you experience an issue, the Vertica Support team may ask you to reproduce the issue using a bare-metal environment to aid in troubleshooting. Depending on the details of the case, the Support team may also ask you to enter a support ticket with your virtualization vendor.

Guidelines for hypervisor and virtual machine configuration

There are many enterprise-grade hypervisors available on the market today, most of which support Linux-based virtual machines (VMs) in support of Vertica. When selecting and configuring your virtual environment, refer to the following guidelines.

• Do not over-subscribe the physical resources (CPU, memory, and network) of the hosting hardware. Many hypervisors allow you to take advantage of scaling out solutions by over-subscribing resources, for example, deploying more virtual CPUs than are physically installed in the host hardware. However, this type of deployment has a negative performance effect on a Vertica cluster.

• Configure the hypervisor to run low-latency, high-performance applications. This means that you should disable power-saving features and CPU frequency scaling on the hypervisor hardware because these technologies contribute to latency in the applications.

• Choose an operating system for the Vertica VMs that is supported by Vertica and by the hypervisor you are using. For some hypervisors, different operating systems may perform better than others. Vertica recommends that you investigate the options with your hypervisor vendor.

• Configure attached storage for high I/O performance. A virtualized Vertica node requires the same amount of disk I/O performance as a non-virtualized one. Vertica recommends that customers use the vioperf utility to validate the actual performance throughput being achieved on each VM.

• If you are providing storage using a shared storage device, make sure to validate disk I/O performance on the cluster as a whole to ensure that the shared resource(s) do not create a bottleneck. To achieve this validation, run the vioperf utility on all the cluster nodes simultaneously to determine the maximum disk I/O performance that can be achieved on each VM during times of heavy I/O load.

• Memory recommendations for Vertica running in a virtualized environment are no different than running in a non-virtualized environment. Vertica recommends that you allocate 8 GB of memory per virtual core. Again, do not over-subscribe the memory available in the hypervisor, because this creates contention for the physical resources, causes negative performance impacts, and possibly crashes the VMs.

• Networking requirements for a virtualized Vertica cluster are the same as for a non-virtualized cluster. Each node in the cluster must be able to communicate with all the other nodes, and latency in those communications can have a negative effect on cluster performance. When you are running multiple virtual machines on a single host server, the network communication is very fast. This occurs because the network traffic is virtualized in the memory space of the hypervisor and never leaves the physical server. However, if the cluster expands beyond a single host, the physical networking of that host can become a bottleneck for the cluster. If you are deploying in a virtual environment, that environment has a robust networking infrastructure that can provide the necessary connection speeds between physical hosts. In most cases, there will be multiple 10 GBE networking connections. Use the vnetperf utility to validate actual network performance speeds between nodes in your Vertica cluster.

• When deploying multiple Vertica VMs per physical host, the fewer the better. The goal of virtualization is to consolidate workloads to reduce overall hardware footprints. However, running multiple Vertica VMs on the same host can place the Vertica cluster in a situation where a single hardware failure can take down multiple nodes in a cluster, and perhaps even the cluster itself. Vertica recommends that when you virtualize a Vertica cluster, spread the VMs across as many physical hosts as possible, with an ideal goal of having one Vertica VM per physical host.

• While virtual networking can be very robust, Vertica has found that UDP broadcast traffic that is used in the spread daemon can be unreliable in most virtual environments, especially when those environments are spread across more than one physical host. In order for Vertica to function effectively in a virtualized environment, use the --point-to-point flag when you execute the /opt/vertica/sbin/install_vertica script. This flag configures the spread daemons to communicate directly with one another.

9 - Hadoop integrations

OpenText supports Vertica 23.4.x with the following Hadoop distributions. OpenText expects Vertica to work with subsequent Hadoop distributions, and tests these later distributions as soon as practical.

* Vertica is phasing out support for this platform. See End-of-support notices for more information.

You must apply patches for the following issues: HDFS-8855 and HDFS-8696. See your Hadoop vendor documentation for further instructions.

MapR versions 5.2 and later are expected to work. You cannot use MapR in Eon Mode.

10 - Apache Kafka integrations

You can use Vertica with the Apache Kafka message broker. For more information on Kafka integration, refer to Apache Kafka integration.

Kafka versions

Vertica has been tested with different versions of Apache Kafka. The following table lists the Kafka versions that each Vertica version supports:

Avro schema registry versions

The Vertica integration for Apache Kafka has been tested with the Avro schema registry distributed with Confluent 3.3.1 and 4.0.0. For more information about Confluent, see the Confluent website.

Java versions

The data streaming job scheduler uses the Vertica JDBC library to connect to the target database, and requires Java 8 or later.

11 - Apache Spark integrations

You can use the Vertica Connector for Apache Spark to transfer data between Vertica and Apache Spark. The following table shows the versions Apache Spark and Scala the Connector supports as well as the name of the Spark Connector JAR file to use for each combination:

* Vertica is phasing out support for this Apache Spark version. See End-of-support notices for more information.

Notes

• A Spark Connector JAR file can support multiple versions of Spark. For example, vertica-spark2.1_scala2.11.jar supports Spark 2.1, 2.2, 2.3, and 2.4.1.

• Vertica recommends you always use the version of the Spark Connector shipped with your version of the Vertica server. When you upgrade your Vertica server, you should also upgrade your version of the Spark Connector.

For more information on Apache Spark integration, refer to Apache Spark integration.

12 - Linux volume manager (LVM)

Vertica 23.4.x supports Linux Volume Manager (LVM) on all supported operating systems.

LVM version supported

Vertica supports LVM version 2.02.66 or later, and must include device-mapper version 1.02.48 or later.

LVM configuration notes

In configuring LVM:

• When you create logical volumes with the lvcreate command, use the readahead option to set the read ahead sector count to greater than 2048 KB.

• You can use the default settings for all other LVM options.

LVM restrictions

The following limitations apply to LVM support:

• You cannot have physical drives shared across several nodes.

• Vertica supports linear logical volumes only. Vertica does not support striped or mirrored logical volumes.

• Vertica supports extending logical volumes (lvextend), but not reducing the size of a logical volume.

• Vertica recommends frequent backups.

• Vertica does not support LVM backup and restore, such as LVM snapshot and merge. Use the Vertica backup utility, vbr.

• Vertica does not support LVM space reclamation because space reclamation is duplicated when reducing the size of a logical volume.

• Vertica does not support LVM migration. Use Vertica Copy operations.

• Vertica does not support LVM high availability. Use Vertica high availability capabilities.

• Vertica does not support LVM RAID. Configure RAID at the disk controller level.

13 - End-of-support notices

These end-of-support notices apply to specific client, Linux, Hadoop, and Kafka distributions.

End-of-support notices

Vertica no longer supports the following client platforms and server distributions:

• AIX (all releases)

• Amazon Linux 2017.09

• Debian 7.6, 7.7

• HP-UX (all releases)

• macOS 10.10

• Red Hat Enterprise Linux/CentOS 6.x

• SUSE 11SP3

• Ubuntu 12.04