[mapping]

Specifies all database nodes to include in an Enterprise Mode database backup.

Enterprise Mode only

Specifies all database nodes to include in an Enterprise Mode database backup. This section also specifies the backup host and directory of each node. If objects are replicated to an alternative database, the [Mapping] section maps target database nodes to the corresponding source database backup locations.

Note

[CloudStorage] and [Mapping] configuration sections are mutually exclusive. If you include both, the backup fails.

Unlike other configuration file sections, the [Mapping] section does not use named parameters. Instead, it contains entries of the following format:

dbNode = backupHost:backupDir

Element Description

Element	Description
`dbNode`	Name of the database node as recognized by Vertica. This value is not the node's host name; rather, it is the name Vertica uses internally to identify the node, typically in this format: `v_``dbname``_node000``int` To find database node names in your cluster, query the `node_name` column of the NODES system table.
`backupHost`	The target host name or IP address on which to store this node's backup. `backupHost` is different from `dbNode`. The `copycluster` command uses this value to identify the target database node host name. IPv6 addresses must be enclosed by square brackets `[]`. For example: `v_backup_restore_node0001 = [fdfb:dbfa:0:2000::112]:/backupdir/backup_restore.2021-06-01T16:17:57 v_backup_restore_node0002 = [fdfb:dbfa:0:2000::113]:/backupdir/backup_restore.2021-06-01T16:17:57 v_backup_restore_node0003 = [fdfb:dbfa:0:2000::114]:/backupdir/backup_restore.2021-06-01T16:17:57` Important Although supported, backups to an NFS host might perform poorly, particularly on networks shared with rsync operations.
`backupDir`	The full path to the directory on the backup host or node where the backup will be stored. The following requirements apply this directory: Already exists when you run `vbr` with `--task backup` Writable by the user account used to run `vbr`. Unique to the database you are backing up. Multiple databases cannot share the same backup directory. File system at this location supports `fcntl lockf` file locking.

dbNode

Name of the database node as recognized by Vertica. This value is not the node's host name; rather, it is the name Vertica uses internally to identify the node, typically in this format:

v_dbname_node000int

To find database node names in your cluster, query the node_name column of the NODES system table.

backupHost

The target host name or IP address on which to store this node's backup. backupHost is different from dbNode. The copycluster command uses this value to identify the target database node host name.

IPv6 addresses must be enclosed by square brackets []. For example:


v_backup_restore_node0001 = [fdfb:dbfa:0:2000::112]:/backupdir/backup_restore.2021-06-01T16:17:57
v_backup_restore_node0002 = [fdfb:dbfa:0:2000::113]:/backupdir/backup_restore.2021-06-01T16:17:57
v_backup_restore_node0003 = [fdfb:dbfa:0:2000::114]:/backupdir/backup_restore.2021-06-01T16:17:57

Important

Although supported, backups to an NFS host might perform poorly, particularly on networks shared with rsync operations.

backupDir

The full path to the directory on the backup host or node where the backup will be stored. The following requirements apply this directory:

Already exists when you run vbr with --task backup
Writable by the user account used to run vbr.
Unique to the database you are backing up. Multiple databases cannot share the same backup directory.
File system at this location supports fcntl lockf file locking.

For example:

[Mapping]
v_sec_node0001 = pri_bsrv01:/archive/backup
v_sec_node0002 = pri_bsrv02:/archive/backup
v_sec_node0003 = pri_bsrv03:/archive/backup

Mapping to the local host

vbr does not support using localhost to specify a backup host. To back up a database node to its own disk, specify the host name with empty square brackets. For example:

[Mapping]
NodeName = []:/backup/path

Mapping to the same database

The following example shows a [Mapping] section that specifies a single node to back up: v_vmart_node0001. The node is assigned to backup host srv01 and backup directory /home/dbadmin/backups. Although a single-node cluster is backed up, and the backup host and the database node are the same system, they are specified differently.

Specify the backup host and directory using a colon (:) as a separator:

[Mapping]
v_vmart_node0001 = srv01:/home/dbadmin/backups

Mapping to an alternative database

Note

Replicating objects to an alternative database requires the vbr configuration file to include a [NodeMapping] section. This section points source nodes to their target database nodes.

To restore an alternative database, add mapping information as follows:

[Mapping]
targetNode = backupHost:backupDir

For example:

[Mapping]
v_sec_node0001 = pri_bsrv01:/archive/backup
v_sec_node0002 = pri_bsrv02:/archive/backup
v_sec_node0003 = pri_bsrv03:/archive/backup