Vertica Back Up

It is strongly recommended that you back up the following resources that may be used if one of the above scenarios occurs.

Vertica database:

1. Log on to the Vertica database server and make sure the Vertica database is running

2. Create a backup configuration file by running the following command:
   /opt/vertica/bin/vbr.py --setupconfig

   Example:

   [dbadmin@xs10 tmp]$ /opt/vertica/bin/vbr.py --setupconfig

   The resulting parameters are:

   Snapshot name (backup_snapshot): backup

   Number of restore points (1):

   Specify objects (no default):

   Vertica user name (dbadmin): dbadmin

   Save password to avoid runtime prompt? (n) [y/n]: y

   Database user password to save in vbr password config file (no default):

   Node v_xsdb_node0001

   Backup host name (no default): localhost #enter all hostname for cluster

   Backup directory (no default): /tmp/vertica_backup #need to create the folder in advance

   Config file name (backup.ini):

   Password file name (no default value) (no default): /tmp/pw.ini

   Change advanced settings? (n) [y/n]:

   Saved vbr configuration to backup.ini.

   Saved vbr configuration to /tmp/pw.ini.

3. Backup the Vertica database by running /opt/vertica/bin/vbr.py --task backup --config-file <file name created at previous step>

   For details on backing up a Vertica database, seehttp://my.vertica.com/docs/7.1.x/PDF/HP_Vertica_7.1.x_AdministratorsGuide.pdf

It is recommended that you use the following backup and restore guidelines:

• A best practice for data warehouse administrators is to back up critical data on a regular basis.

• Database backups should consist of a weekly full database backups, and daily differential backups.

• Backups should be periodically verified by restoring a copy onto a test system.

• Start scheduled backups before running the daily ETLs.

• Perform full backups in off-peak times.