Vertica Server and Vertica Management Console

Supported Operating Systems and Operating System Versions

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

In general, Micro Focus provides support for the Vertica Analytic Database, not its host operating system, hardware, or other environmental elements. However, Micro Focus 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 7.x release, OpenText recommends you upgrade to or be running the latest supported RHEL 7.x release.

Platform Processor Supported Versions Known Issues

Red Hat Enterprise Linux / CentOS

Vertica does not support or recommend in-place upgrades from one major version to another major version. For example, you cannot perform in-place upgrades from RHEL/CentOS 7.x to RHEL/CentOS 8.x.

For information on how to upgrade to Red Hat Enterprise Linux 7, see Upgrading Your Operating System on Nodes in Your Vertica Cluster. For information on changes to the operating system for Red Hat Enterprise Linux 7, see the Red Hat Enterprise Linux 7 documentation.

Vertica support for CentOS is based on testing done on Red Hat Enterprise Linux. Vertica continues to support CentOS, but testing and troubleshooting will be performed with the associated RedHat version.


7.x: all with known issues

8.x: all with known issues


There are some circumstances where you cannot create a cluster from Management Console due to an issue with the private key file.

To create R extensions, manually install the libgfortran4 package. Download the applicable package from the CentOS Linux and Stream releases page.

SUSE Linux Enterprise Server x86_64

12 SP2 and higher

15.x: all

openSUSE x86_64 42.3
Amazon Linux x86_64 2.0 on Amazon Machine Instances (AMIs)
Oracle Enterprise Linux (Red Hat compatible kernels only) x86_64

6.x: all

7.x: all

Debian Linux x86_64

8.5, 8.9

10.x: with known issues


On Vertica 9.3 and higher, you cannot restart the Management Console using the MC Interface in your browser. To restart the Management Console, enter one of the following commands:

  • systemctl restart vertica-consoled
Ubuntu x86_64

14.04 LTS and higher with known issues


On Vertica 9.3 and higher, you cannot restart the Management Console using the MC Interface in your browser. To restart the Management Console, enter one of the following commands:

  • systemctl restart vertica-consoled
  • /etc/init.d/vertica-consoled restart

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 for communal storage and related backup tasks when running in Eon Mode

For the Vertica I/O profile, the ext4 file system is considerably faster than ext3.

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 Vertica Management Console

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

  • Chrome

  • Firefox

  • Microsoft Edge

  • Internet Explorer 11

Vertica Server and Management Console Compatibility

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