{"id":7636,"date":"2020-06-18T08:54:19","date_gmt":"2020-06-18T08:54:19","guid":{"rendered":"https:\/\/rax-stg-wp-aws.com\/blogs\/back-up-and-restore-a-vertica-database\/"},"modified":"2026-11-03T19:28:47","modified_gmt":"2026-11-03T19:28:47","slug":"back-up-and-restore-a-vertica-database","status":"publish","type":"blogs","link":"https:\/\/www.rackspace.com\/en-gb\/blogs\/back-up-and-restore-a-vertica-database\/","title":{"rendered":"Back up and restore a Vertica database"},"content":{"rendered":"<p><strong>Introduction<\/strong><\/p>\n<p>To ensure that you can recover data in the event of data corruption or accidental deletion, make database backups a routine maintenance activity. This post explores&nbsp;Vertica\u00ae database backup and restoration.<\/p>\n<p>Vertica, an analytic database management system, is a columnar-storage platform&nbsp;designed to handle large volumes of data, enabling fast query performance in&nbsp;traditionally resource-intensive scenarios.<\/p>\n<p>Vertica offers the following advantages:<\/p>\n<ul>\n<li>Improves query performance over traditional database relational database management systems.<\/li>\n<li>Provides high availability.<\/li>\n<li>Provides petabyte scalability on commodity enterprise servers.<\/li>\n<\/ul>\n<p>The database backup and recovery mechanism reduces the downtime during maintenance and disaster recovery.<\/p>\n<p><strong>&nbsp;Back up and restore a database<\/strong><\/p>\n<p>With Vertica, you can create hot backups, incremental copies with an indefinite number of restore points, and backups of an entire database or a subset (schemas,&nbsp;tables, and so on) of the database. The following backup levels are available:<\/p>\n<ul>\n<li><strong>Full level<\/strong>: This level ensures that you can back up and restore the full Vertica database.<\/li>\n<li><strong>Incremental level<\/strong>: This level is a subsequent backup that consists of only new or changed data.<\/li>\n<li><strong>Object-level<\/strong>: This level is the backup of an object for restoration.<\/li>\n<\/ul>\n<p>Vertica offers the flexibility and levels of granularity to restore specific&nbsp;objects (such as schemas and tables) from a full backup.<\/p>\n<p><strong>Snapshots<\/strong><br \/>\nDatabase snapshots capture a consistent image of all the objects and data in the database. You can select a subset of database objects to include in an object-level snapshot, which contains associated data in the database at the&nbsp;time of the snapshot and other objects in the dependency graph. You can name&nbsp;your snapshot as you like (for example: snap, objectsnap1, fullsnap, and so on).<\/p>\n<p><strong>Backup location<\/strong><\/p>\n<p>The backup location is the directory on a backup host where you save snapshots&nbsp;and their associated archives. Because the snapshots are compatible, you can use&nbsp;any object snapshot from the same backup location after you restore a database&nbsp;from a full database snapshot. All snapshots in the same backup location share<br \/>\ndata files through hard links.<\/p>\n<p><strong>Hard-link backups<\/strong><br \/>\nVertica provides low cost and space-efficient copies (<em>hard-link local backups<\/em>)&nbsp;of the database backups in the local cluster infrastructure. You can retrieve&nbsp;these backups faster because the system does not copy the user data to an external&nbsp;backup environment. Vertica copies only the catalog data and initiates&nbsp;Linux\u00ae-based hard links within the file system.<\/p>\n<p><img decoding=\"async\" src=\"\/wp-content\/uploads\/2026\/blog_article_images\/26459-body-Picture1_10.png\" alt=\"vertica pic 1\" \/><\/p>\n<p><a href=\"https:\/\/www.vertica.com\/wp-content\/uploads\/2016\/04\/sidestep1.png\">Image Source<\/a>&nbsp;<\/p>\n<p>These backups share the same set of storage blocks, and each backup tracks their&nbsp;point-in-time copy. The system doesn&#8217;t store the same content in multiple&nbsp;locations.<\/p>\n<p><strong>Backup and restoration process flow<\/strong><br \/>\nThe backup and restoration flow consists of the following steps:<\/p>\n<p>1. Select the snapshot type, such as full, incremental, or object-level backup.<br \/>\n2. Create a configuration file by using the Vertica Backup and Recovery tool.<br \/>\n3. Initialize a backup location to store the backup files.<br \/>\n4. Take a backup by using the configuration file.<br \/>\n5. Verify the backups in the backup location.<br \/>\n6. Restore the full database or database objects on similar or different Vertica clusters.<\/p>\n<p><img decoding=\"async\" src=\"\/wp-content\/uploads\/2026\/blog_article_images\/26459-body-Picture2_4.png\" alt=\"vertica pic 2\" \/><\/p>\n<p><a href=\"https:\/\/www.vertica.com\/kb\/Copy-and-Restore-Data-from-a-Vertica-Cluster-to-a-Backup\/Content\/BestPractices\/Copy-and-Restore-Data-from-a-Vertica-Cluster-to-a-Backup.htm\">Image Source<\/a>&nbsp;<\/p>\n<p><strong>Generate a configuration file<\/strong><\/p>\n<p>The <strong>vbr.py<\/strong>&nbsp;utility creates a configuration file with the information Vertica&nbsp;requires to back up and restore full, incremental, or object-level snapshots.&nbsp;You cannot back up or restore databases or objects without a configuration file,&nbsp;and no default file exists.<\/p>\n<p>You can create as many backup configuration files as you need (such as full or&nbsp;incremental, object or schema-specific, or location-specific files).<\/p>\n<p><strong>Full backup configuration file<\/strong><\/p>\n<p>The following steps help in creating a configuration file to take the full database backup.<\/p>\n<p><em>&nbsp;$ vbr.py &#8211;setupconfig<br \/>\n&nbsp; &nbsp; Snapshot name (backup_snapshot): full_bkp_snap<br \/>\n&nbsp; &nbsp; Backup vertica configurations? (n) [y\/n]: y<br \/>\n&nbsp; &nbsp; Number of restore points (1):<br \/>\n&nbsp; &nbsp; Specify objects (no default):<br \/>\n&nbsp; &nbsp; Vertica user name (dbadmin): dbadmin<br \/>\n&nbsp; &nbsp; Save password to avoid runtime prompt? (n) [y\/n]: n<br \/>\n&nbsp; &nbsp; Node v_testdb_node0001<br \/>\n&nbsp; &nbsp; Backup host name (no default): v_testdb_node0001<br \/>\n&nbsp; &nbsp; Backup directory (no default): \/vert_backup\/backup<br \/>\n&nbsp; &nbsp; Node v_testdb_node0002<br \/>\n&nbsp; &nbsp; Backup host name (no default): v_testdb_node0002<br \/>\n&nbsp; &nbsp; Backup directory (no default): \/vert_backup\/backup<br \/>\n&nbsp; &nbsp; Node v_testdb_node0003<br \/>\n&nbsp; &nbsp; Backup host name (no default): v_testdb_node0003<br \/>\n&nbsp; &nbsp; Backup directory (no default): \/vert_backup\/backup<br \/>\n&nbsp; &nbsp; Config file name (full_bkp_snap.ini): \/vert_backup\/backup_conf\/full_bkp_snap.ini<br \/>\n&nbsp; &nbsp; Change advanced settings? (n) [y\/n]: n<br \/>\n&nbsp; &nbsp; Saved vbr configuration to \/vert_backup\/backup_conf\/full_bkp_snap.ini.<\/em><\/p>\n<p><strong>Object-specific backup configuration file<\/strong><\/p>\n<p>Perform the following steps to create an object-specific configuration file:<\/p>\n<p>1. List the objects in the database and choose which ones to use. The following objects are present in our Vertica database:<\/p>\n<p>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;List of tables<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Schema | Name &nbsp;| Kind &nbsp;| &nbsp;Owner &nbsp;| Comment<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &#8212;&#8212;&#8211;+&#8212;&#8212;-+&#8212;&#8212;-+&#8212;&#8212;&#8212;+&#8212;&#8212;&#8212;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab1 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab2 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab3 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(3 rows)<\/p>\n<p>2. Run the following command to create a configuration file to take a backup of the **public.tab1** table:<\/p>\n<p><em>&nbsp; &nbsp; &nbsp; &nbsp; $ vbr.py &#8211;setupconfig<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Snapshot name (backup_snapshot): tab1_bkp_snap<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Backup vertica configurations? (n) [y\/n]: n<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Number of restore points (1):<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Specify objects (no default): public.tab1<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Vertica user name (dbadmin): dbadmin<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Save password to avoid runtime prompt? (n) [y\/n]: n<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Node v_testdb_node0001<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Backup host name (no default): v_testdb_node0001<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Backup directory (no default): \/vert_backup\/backup<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Node v_testdb_node0002<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Backup host name (no default): v_testdb_node0002<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Backup directory (no default): \/vert_backup\/backup<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Node v_testdb_node0003<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Backup host name (no default): v_testdb_node0003<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Backup directory (no default): \/vert_backup\/backup<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Config file name (tab1_bkp_snap.ini): \/vert_backup\/backup_conf\/tab1_bkp_snap.ini<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Change advanced settings? (n) [y\/n]: n<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Saved vbr configuration to \/vert_backup\/backup_conf\/tab1_bkp_snap.ini.<\/em><\/p>\n<p><em>3. <\/em>Run the following commands to list the created backup configuration files:<\/p>\n<p><em>&nbsp; &nbsp; &nbsp; &nbsp; $ cd \/vert_backup\/backup_conf\/<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; $ ls -la<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; total 20<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; drwxr-xr-x. 2 dbadmin dbadmin 4096 Jan 20 14:21 .<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; -rw-rw-r&#8211;. 1 dbadmin dbadmin &nbsp;488 Jan 20 14:21 tab1_bkp_snap.ini<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; -rw-rw-r&#8211;. 1 dbadmin dbadmin &nbsp;475 Jan 20 14:04 full_bkp_snap.ini<\/em><\/p>\n<p><strong>&nbsp;Initialize the backup location<\/strong><\/p>\n<p>To initialize the backup locations for full and object-level backups on the<br \/>\nsource cluster, run the following <em>`init<\/em>` statements:<\/p>\n<p><em>&nbsp; &nbsp; $ \/opt\/vertica\/bin\/vbr.py -t init &#8211;config-file full_bkp_snap.ini<br \/>\n&nbsp; &nbsp; $ \/opt\/vertica\/bin\/vbr.py -t init &#8211;config-file tab1_bkp_snap.ini<\/em><\/p>\n<p><strong>Take a backup<\/strong><br \/>\nTake either a full database or an object-level backup.<\/p>\n<p><strong>Full database backup<\/strong><\/p>\n<p>Take full database backup by using the previously created configuration file,&nbsp;<strong>full\\_bkp\\_snap.ini<\/strong>:<\/p>\n<p><em>&nbsp; &nbsp; $ vbr.py &#8211;task backup &#8211;config-file full_bkp_snap.ini<br \/>\n&nbsp; &nbsp; Please input vertica password:<br \/>\n&nbsp; &nbsp; pparing&#8230;<br \/>\n&nbsp; &nbsp; Found Database port: &nbsp;5433<br \/>\n&nbsp; &nbsp; Copying&#8230;<br \/>\n&nbsp; &nbsp; 348900 out of 348900, 100%<br \/>\n&nbsp; &nbsp; All child processes terminated successfully.<br \/>\n&nbsp; &nbsp; Committing changes on all backup sites&#8230;<\/em><br \/>\n&nbsp; &nbsp; backup done!<br \/>\n&nbsp;<\/p>\n<p><strong>Single object backup<\/strong><br \/>\nUse the configuration file, <strong>tab1\\_bkp\\_snap.ini<\/strong>, to take an object-level backup:<\/p>\n<p><em>&nbsp;$ vbr.py &#8211;task backup &#8211;config-file tab1_bkp_snap.ini<br \/>\n&nbsp; &nbsp; Please input vertica password:<br \/>\n&nbsp; &nbsp; pparing&#8230;<br \/>\n&nbsp; &nbsp; Found Database port: &nbsp;5433<br \/>\n&nbsp; &nbsp; Copying&#8230;<br \/>\n&nbsp; &nbsp; 78920 out of 78920, 100%<br \/>\n&nbsp; &nbsp; All child processes terminated successfully.<br \/>\n&nbsp; &nbsp; Committing changes on all backup sites&#8230;<\/em><br \/>\n&nbsp; &nbsp; backup done!<\/p>\n<p><strong>Verify the backup location<\/strong><\/p>\n<p>Run the following commands to verify the backup location:<\/p>\n<p>&nbsp; &nbsp;<em> $ cd vert_backup\/<br \/>\n&nbsp; &nbsp; $ ls -la<br \/>\n&nbsp; &nbsp; total 16<br \/>\n&nbsp; &nbsp; drwxr-xr-x. &nbsp;4 dbadmin dbadmin 4096 Jan 20 13:40 .<br \/>\n&nbsp; &nbsp; dr-xr-xr-x. 28 root &nbsp; &nbsp;root &nbsp; &nbsp;4096 Jan 20 13:53 ..<br \/>\n&nbsp; &nbsp; drwxr-xr-x. &nbsp;5 dbadmin dbadmin 4096 Jan 20 15:22 backup<br \/>\n&nbsp; &nbsp; drwxr-xr-x. &nbsp;2 dbadmin dbadmin 4096 Jan 20 15:29 backup_conf<br \/>\n&nbsp; &nbsp; $ cd backup\/<br \/>\n&nbsp; &nbsp; $ ll<br \/>\n&nbsp; &nbsp; total 12<br \/>\n&nbsp; &nbsp; drwxrwxr-x. 8 dbadmin dbadmin 4096 Jan 20 15:29 v_testdb_node0001<br \/>\n&nbsp; &nbsp; drwxrwxr-x. 8 dbadmin dbadmin 4096 Jan 20 15:29 v_testdb_node0002<br \/>\n&nbsp; &nbsp; drwxrwxr-x. 8 dbadmin dbadmin 4096 Jan 20 15:29 v_testdb_node0003<br \/>\n&nbsp; &nbsp; $ cd v_testdb_node0001\/<br \/>\n&nbsp; &nbsp; $ ll<br \/>\n&nbsp; &nbsp; total 12<br \/>\n&nbsp; &nbsp; drwx&#8212;&#8212;. 3 dbadmin dbadmin 4096 Jan 20 15:29 tab1_bkp_snap<br \/>\n&nbsp; &nbsp; drwx&#8212;&#8212;. 3 dbadmin dbadmin 4096 Jan 20 15:22 full_bkp_snap<\/em><\/p>\n<p><strong>Restore the backup<\/strong><\/p>\n<p>Restore either the full or object-level backup.<\/p>\n<p><strong>Restore from a full-database backup<\/strong><\/p>\n<p><strong>Note:<\/strong>&nbsp;The database must be down to restore the full backup.<\/p>\n<p>Use the following steps to perform a full-database restore:<\/p>\n<p>1. Drop all the objects in your database and restore them with the recently created backup:<\/p>\n<p>&nbsp; &nbsp; &nbsp; &nbsp; cluster=&amp;gt; dt<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;List of tables<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Schema | Name &nbsp;| Kind &nbsp;| &nbsp;Owner &nbsp;| Comment<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &#8212;&#8212;&#8211;+&#8212;&#8212;-+&#8212;&#8212;-+&#8212;&#8212;&#8212;+&#8212;&#8212;&#8212;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab1 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab2 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab3 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; (3 rows)<\/p>\n<p><em>&nbsp; &nbsp; &nbsp;cluster=&amp;gt; drop table tab1,tab2,tab3;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; DROP TABLE<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; cluster=&amp;gt; dt<\/em><\/p>\n<p>\n<em>2.<\/em> With the database down, restore the database by using the full backup:<\/p>\n<p><em>&nbsp; &nbsp; &nbsp; &nbsp; $ vbr.py &#8211;task restore &#8211;config-file full_bkp_snap.ini<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Please input vertica password:<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Preparing&#8230;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Found Database port: &nbsp;5433<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Copying&#8230;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; 248556 out of 248556, 100%<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; All child processes terminated successfully.<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; restore done!<\/em><\/p>\n<p>\n3. Start the database and check whether the object restoration succeeded. The following example shows that the restoration succeeded:<\/p>\n<p>&nbsp; &nbsp; &nbsp; &nbsp; cluster=&amp;gt; dt<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;List of tables<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Schema | Name &nbsp;| Kind &nbsp;| &nbsp;Owner &nbsp;| Comment<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &#8212;&#8212;&#8211;+&#8212;&#8212;-+&#8212;&#8212;-+&#8212;&#8212;&#8212;+&#8212;&#8212;&#8212;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab1 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab2 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab3 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; (3 rows)<\/p>\n<p><strong>Restore an object-level backup<\/strong><\/p>\n<p><strong>Note<\/strong>: The database must be up and running for an object-level restore.<\/p>\n<p>To restore an object, you need to use an existing object-level backup. The following code drops **tab1** in preparation for restoration:<\/p>\n<p>&nbsp; &nbsp; cluster=&amp;gt; drop table tab1;<br \/>\n&nbsp; &nbsp; DROP TABLE<br \/>\n&nbsp; &nbsp; cluster=&amp;gt; dt<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;List of tables<br \/>\n&nbsp; &nbsp; Schema | Name &nbsp;| Kind &nbsp;| &nbsp;Owner &nbsp;| Comment<br \/>\n&nbsp; &nbsp; &#8212;&#8212;-+&#8212;&#8212;-+&#8212;&#8212;-+&#8212;&#8212;&#8212;+&#8212;&#8212;&#8212;<br \/>\n&nbsp; &nbsp; public | tab2 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; public | tab3 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; (2 rows)<br \/>\n&nbsp;<\/p>\n<p>Perform the following steps to restore an object from an object-level backup:<\/p>\n<p>1. Restore the object:<\/p>\n<p><em>&nbsp; &nbsp; &nbsp; &nbsp; $ vbr.py &#8211;task restore &#8211;config-file tab1_bkp_snap.ini<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Please input vertica password:xxxxxxxx<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Preparing&#8230;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Found Database port: &nbsp;5433<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Copying&#8230;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;out of , 100%<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; All child processes terminated successfully.<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Copying&#8230;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; 2970 out of 2970, 100%<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; All child processes terminated successfully.<\/em><br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; restore done!<\/p>\n<p>2. Check whether the object restoration succeeded. The following example shows a successful restoration of <strong>public.tab1<\/strong>&nbsp;from the object-level backup:<\/p>\n<p>&nbsp; &nbsp; &nbsp; &nbsp; $ vsql<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; Password:xxxxxxx<\/p>\n<p>&nbsp; &nbsp; &nbsp; &nbsp; dbadmin=&amp;gt; dt<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;List of tables<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Schema | Name &nbsp;| Kind &nbsp;| &nbsp;Owner &nbsp;| Comment<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &#8212;&#8212;&#8211;+&#8212;&#8212;-+&#8212;&#8212;-+&#8212;&#8212;&#8212;+&#8212;&#8212;&#8212;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab1 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab2 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab3 &nbsp;| table | dbadmin |<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; (3 rows)<\/p>\n<p>&nbsp; &nbsp; &nbsp; &nbsp; dbadmin=&amp;gt; d tab1 ;<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; List of Fields by Tables<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Schema | Table | Column | &nbsp; &nbsp; Type &nbsp; &nbsp; | Size | Default | Not Null | Primary Key | Foreign Key<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &#8212;&#8212;&#8211;+&#8212;&#8212;-+&#8212;&#8212;&#8211;+&#8212;&#8212;&#8212;&#8212;&#8211;+&#8212;&#8212;+&#8212;&#8212;&#8212;+&#8212;&#8212;&#8212;-+&#8212;&#8212;&#8212;&#8212;-+&#8212;&#8212;&#8212;&#8212;-<br \/>\n&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;public | tab1 &nbsp;| col1 &nbsp; | numeric(3,) &nbsp;| &nbsp; &nbsp;8 | &nbsp; &nbsp; &nbsp; &nbsp; | f &nbsp; &nbsp; &nbsp; &nbsp;| f &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |<\/p>\n<p><strong>Conclusion<\/strong><\/p>\n<p>This post highlights the logic behind the Vertica database backup and recovery&nbsp;process. It also provides the steps to back up and restore a Vertica database at&nbsp;various levels, such as full, incremental, and object-level.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Back up and restore a Vertica database<\/p>\n","protected":false},"author":2,"featured_media":7638,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","format":"standard","meta":{"content-type":"","nid":"26459","content_type":"blog","created_by":"10130","authored_on":"2024-01-08T09:54:19+00:00","field_article_industries":"","tag_category":"Technical","field_blog_author_text":"by Rackspace Technology Staff","seo_description":"Explore QUIC protocol for reducing latency on the internet. Game-changer for content and user experience.\r\n","field_featured_image":"","insights_image":"\/wp-content\/uploads\/2026\/blog_technical_images\/26459-insights_image-database-technical-blog-2-insights.jpg","field_partners":"","rxt_platforms":"Relational Databases","product":"","publisheddate":"2020-06-18T08:54:19","rxt_solutions":"Data, Databases","opengraph_tag":"","x_tag":"","teaser_flag":"Technical Blog","seo_titile":"Back up and Restore Vertica Database | Rackspace Technology","field_topics":"","field_slug":"back-up-and-restore-a-vertica-database","footnotes":""},"categories":[178],"tags":[204],"class_list":["post-7636","blogs","type-blogs","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-technical"],"_links":{"self":[{"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/blogs\/7636","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/blogs"}],"about":[{"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/types\/blogs"}],"author":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/comments?post=7636"}],"version-history":[{"count":3,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/blogs\/7636\/revisions"}],"predecessor-version":[{"id":9576,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/blogs\/7636\/revisions\/9576"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/media\/7638"}],"wp:attachment":[{"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/media?parent=7636"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/categories?post=7636"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rackspace.com\/en-gb\/wp-json\/wp\/v2\/tags?post=7636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}