Upgrading Vertica

The process of upgrading your database with a new Vertica version includes:

1. Completing upgrade prerequisites

2. Upgrading Vertica

3. Performing post-upgrade tasks

Upgrade paths

Vertica upgrades are generally incremental: you must upgrade to each intermediate major and minor release. For example, in order to upgrade from Vertica 9.0 to 10.1, you would upgrade incrementally as follows:

1. Vertica 9.0 to 9.1

2. Vertica 9.1 to 9.2

3. Vertica 9.2 to 9.3

4. Vertica 9.3 to 10.0

5. Vertica 10.0 to 10.1

As new versions are released, you must continue upgrading incrementally (from 10.1 to 11.0, then 11.0 to 11.1, and so on).

If you're upgrading from a FIPS-enabled Vertica 9.2.x database to 10.1.1 and want to maintain your FIPS certification, you must perform a direct upgrade. For instructions, see Nonsequential FIPS database upgrades.

Be sure to read the Release Notes and New Features for each version in your path. Documentation and release notes for the current Vertica version are available in the RPM and at https://docs.vertica.com/latest, which also provides access to documentation for earlier versions.

If you want to test out a new version of Vertica for an Eon Mode database without upgrading your entire cluster, you can sandbox a secondary subcluster and then upgrade the subcluster within the sandbox. By sandboxing the subcluster, you can try out the new version of Vertica stress-free and continue to use your main cluster as usual. After confirming that the upgrade works, you can downgrade the sandboxed subcluster, remove the sandbox, and proceed to upgrade the entire cluster.

For guidance on upgrading from unsupported versions, contact Vertica Technical Support.