Table of Contents Previous Next


2 Overview : 2.2 Block-Level Incremental Backup : 2.2.5 Restoring an Incremental Backup

BART Host. If an incremental backup is to be restored onto the same host where BART has been installed, the restore process is outlined in Section 2.2.5.1.
Remote Host. If an incremental backup is to be restored onto a remote host where BART has not been installed, the restore process still follows the information outlined in Section 2.2.5.1, but in addition the requirements in Section 2.2.5.2 must be established.
The bart program must be available on the remote host because the RESTORE subcommand invocation for an incremental backup results in the execution of the bart program on the remote host to restore the modified blocks to their proper location within the restore directory on the remote host.
The RESTORE subcommand is used to restore an incremental backup by specifying its backup identifier or name with the -i option. All RESTORE options are used in the same manner as when restoring a full backup.
See Section 5.4.8 for information on using the RESTORE subcommand for restoring an incremental backup. Also note the usage of the -w option of the RESTORE subcommand to specify a multiple number of parallel worker processes to stream the modified blocks to the restore host.
Step 1: Install BART on the remote host to which an incremental backup is to be restored. Use the instructions in Section 3.2 to install BART on this remote host.
Note: No editing is needed in the BART configuration file bart.cfg installed on the remote host.
Step 2: Determine the Linux operating system user account on the remote host to be used as the remote user specified by the remote_host parameter in the BART configuration file or by the -r option when using the RESTORE subcommand to restore the incremental backup. This remote user must also be the owner of the directory where the incremental backup is to be restored on the remote host. For example, the user account is typically enterprisedb for Advanced Server or postgres for PostgreSQL.
Step 3: Make sure a password-less SSH/SCP connection has been established from the BART user on the BART host to the remote user on the remote host. See Section 4.2.1 for information on setting up a password-less SSH/SCP connection.
Step 4: When the remote user connects to the remote host, the remote user’s PATH environment variable must include the BART bin directory. For example, modify the user’s ~/.bashrc or ~/.bash_profile file to set the PATH environment variable such as in the following example:

2 Overview : 2.2 Block-Level Incremental Backup : 2.2.5 Restoring an Incremental Backup

Table of Contents Previous Next