myVertica  

Upgrading Vertica

Vertica adds new features and enhances existing features with every release. To access the new and improved features, upgrade to the latest release of Vertica.

Prerequisites

Before you upgrade, perform the following:

  • Perform a full database backup. If upgrade is unsuccessful, a full back up allows you to roll back to your current version. You can consider creating a hard link backup. Note that a disk failure causes corruption of the backup.
  • However, a disk failure will affect the backup and copy.
  • Verify the platform requirements for the new version.
  • Check the catalog storage space.
  • Uninstall the HDFS connector (required only if you are upgrading from versions earlier than Vertica 7.2.x).


  • Vertica recommends you to upgrade to the immediate next version for best performance results. For example: Upgrade to the next incremental version of Vertica. For example, upgrade from 7.1 to 7.2 or 8.0 to 8.1. For more information, see Upgrade Paths in the Vertica documentation.

    After you complete these tasks, shut down the database and follow these steps:

    Step Task Result
    1 Perform a full local backup of your existing database and stop the database. $ /opt/vertica/bin/admintools -t stop_db -d db-name If the backup is successful, proceed to Step 2.

    If the backup is not successful, see Creating Full Backups in the Vertica documentation.
    2 Uninstall any additional packages that you installed on each host. rpm -e vertica-package-name

    If you omit this step and do not uninstall additional packages, the Vertica server package fails to install in the next step.
    If the uninstall is successful, proceed to Step 3.

    If the uninstall is not successful, examine the error and contact Vertica technical support.
    3 Install the new Vertica Server package on any host as root or sudo. # rpm -Uvh pathname $ sudo rpm -Uvh pathname

    You can install on one node or all the nodes. If you install one node at a time, the install_vertica script installs in other nodes sequentially. If you install all the nodes at the same time, the install_vertica script is faster as the script does not have to copy the rpm.
    If the install is successful, proceed to Step 4.

    If the install is not successful, examine the error and contact Vertica technical support.
    4 Run the update_vertica script as root or sudo, as shown in the following sample command: # /opt/vertica/sbin/update_vertica --rpm /home/dbadmin/vertica_x.1.x.x86_64.RHELx.rpm --dba-user mydba If the update is successful, proceed to Step 5.
    5 Start the database. => # /opt/vertica/bin/admintools -t start_db -d db-name When the database starts, proceed to Step 6.
    6 After upgrading the Vertica server package on your cluster, upgrade the client authentication.
    • a. Review the client authentication methods that Vertica created during the upgrade by querying the CLIENT_AUTH, CLIENT_AUTH_PARAMS and the USER_CLIENT_AUTH system tables.
    • b. Review the vertica.log file.
    • c. Create the required records as needed with CREATE AUTHENTICATION.
    • d. After the upgrade, enable all defined authentication methods.
    • e. Create an authentication method (LOCAL TRUST or LOCAL PASSWORD) with a very high priority such as 10,000. Grant this method to the DBADMIN user, and set the priority using ALTER AUTHENTICATION.
    If the upgrade is successful, proceed to Step 7.

    If the upgrade is unsuccessful, contact Vertica Technical Support.
    7 Reinstall the packages that you uninstalled before upgrading. For each package, see its install or upgrade instructions. If the upgrade was unable to install one or more packages, reinstall them with admintools.

    Learn More

    For more information, see Upgrade Vertica in the Vertica documentation.