El catálogo con prefacio de Michel Tapié

The process of upgrading HP Vertica is similar to installing it.

Important! When upgrading from 5.x to 6.0, due to a change in how transaction catalog

storage works in HP Vertica 6.0 and later, the amount of space that the transaction catalog takes up can increase significantly during and after the upgrade. Verify that you have a at least 4x the size of the Catalog folder in the catalog free (in addition to normal free space

requirements) on your nodes prior to upgrading.

To determine the amount of space the Catalog folder is using, run du -h on the Catalog folder.

Note: do not run du -h on the entire catalog. Run it specifically on the Catalog folder in the

catalog. For example:

[dbadmin@localhost ~]$ du -h

/home/dbadmin/db/v_db_node0001_catalog/Catalog/

Upgrading HP Vertica

Follow these steps to upgrade your database. Note that upgrades are an incremental and must follow one of the following upgrade paths:

 HP Vertica 3.5 to 4.0  HP Vertica 4.0 to 4.1  HP Vertica 4.1 to 5.0  HP Vertica 4.1 to 5.1  HP Vertica 5.0 to 5.1  HP Vertica 5.0 to 6.0  HP Vertica 5.1 to 6.0  HP Vertica 6.0 to 6.1

IMPORTANT NOTE: HP strongly recommends that you follow the upgrade paths. Be sure to read

the New Features and New Features for each version you skip. The HP Vertica documentation is available in the rpm, as well as at http://www.vertica.com/documentation

(http://www.vertica.com/documentation) (which also provides access to previous versions of the documentation).

1 Back up your existing database. This is a precautionary measure so that you can restore from

the backup if the upgrade is unsuccessful.

Note: Release 5.1 introduced a new backup utility, vbr.py. This utility replaced both the

backup.sh and restore.sh scripts, making both obsolete. Any backups created with backup.sh are incompatible with backups created with vbr.py. HP Vertica recommends that you use the current utility vbr.py as soon as possible after successfully upgrading to Release 5.1 or later. Documentation for the 5.0 scripts remained in the 5.1 documentation. However, the topics were marked Obsolete in that version and subsequently removed from the documentation.

-74-

2 If you are using Ganglia to monitor your database, disable any crontab entry you created for it.

Otherwise, it could run during the upgrade and interfere with the installer. See Monitoring HP Vertica Using Ganglia for more information about Ganglia, and Add a cron job for instructions on editing the crontab.

3 Stop the database using admintools if it is not already stopped.

4 On each host that you have an additional package installed, such as the R Language Pack,

uninstall the package. For example: rpm -e vertica-R-lang.

5 On the administration host, install the new HP Vertica package. See Download and install

the HP Vertica install package (page 34). For example: rpm syntax:

# rpm -Uvh /home/dbadmin/vertica-x86_64.RHEL5.rpm deb syntax:

# dpkg -i /home/dbadmin/vertica-x86_64.RHEL5.rpm

Note: If you fail to install the rpm or deb prior to running the next step, then update_vertica fails

with an error due to the conflict between the version of the update_vertica script and the version of the rpm argument.

6 As root or sudo, run update_vertica. Use the same options that you used when you last installed or upgraded the database, except for the -s host_list parameter. Use

the -S default parameter if spread is running on the same subnet as HP Vertica (default behavior). Otherwise use the -S parameter with the same options you originally used when installing HP Vertica. If you forgot the options that were last used, open

/opt/vertica/config/admintools.conf in a text editor and find the line that starts with install_opts. This line details each option.

For example:

# /opt/vertica/sbin/update_vertica -S default -r /home/dbadmin/vertica-x86_64.RHEL5.rpm

Note: the rpm file must be readable by the dbadmin user when upgrading. Some upgrade

scripts are run as the dbadmin user, and that user must be able to read the rpm file. Stop all databases before you use the -S parameter. If the databases are not stopped then the -S parameter causes the database to restart.

7 Start the database. The startup scripts analyze the database and perform any necessary data

and catalog updates for the new version.

8 Stop the database and perform another backup. Note that you can use incremental backups

as you upgrade, but when moving from Version 5.0 and earlier version to Version 5.1 and later versions the backup process changes from using backup.sh to using vbr.py. You cannot use an incremental backup with different version of the backup script. Create a full backup the first time you move to using vbr.py.

9 Continue along the upgrade path and perform these same steps for each version in your

upgrade path.

10 After you have upgraded to the latest version of the server, install any additional packs you had

previously installed. See the pack install/upgrade instructions for details on upgrading the packs. For R, see Installing/Upgrading the R Language Pack for HP Vertica.

-75-

Upgrading HP Vertica

Additional notes

 Downgrade installations are not supported.

 HP Vertica includes a DBA UNIX group for tighter control over filesystem access in the /opt/vertica/ directories.

During upgrade, a verticadba group is created, and existing users are added to the group with permissions set to 775. This setting grants full privileges to the DBA group and

read/execute privileges to all other users. The /opt/vertica/log and

/opt/vertica/config directories are the folders with the modified permissions.

See also

-76-