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).
| 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.
|
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.About the Author
Soniya Shah
Information Developer
Currently, a first year law student with a background in science and technology. Experienced technical writer, with specializations in software documentation, big data, blog development, and website development. I build user-centered content to communicate complex and technical information more easily.
I used to work for Vertica full time for about 3 years. I still work at Vertica part time while going to law school.
Update: Soniya is now doing her law internship, and no longer working at Vertica. Good luck, Soniya!
