BACKUP v2.6

The BACKUP subcommand is used to create a full backup or an incremental backup.

Syntax for full backup:

bart BACKUP –s { <server_name> | all } [ -F { p | t } ]
  [ -z ] [ –c <compression_level> ]
  [ --backup-name <backup_name> ]
  [ --thread-count <number_of_threads> ]
  [ { --with-pg_basebackup | --no-pg_basebackup } ]

Syntax for incremental Backup:

bart BACKUP –s { <server_name> | all } [ -F p]
 [ --parent { <backup_id> | <backup_name> } ]
  [ --backup-name <backup_name> ]
  [ --thread-count <number_of_threads> ]
  [ --check ]
  [--checksum-algorithm ]

Please Note:

• While a BACKUP subcommand is in progress, no other subcommands must be invoked. Any subcommands invoked while a backup is in progress will skip and ignore the backups.

• For full backup, the target default format is a tar file, whereas for incremental backup, only plain format must be specified.

• The backup is saved in the <backup_path>/<server_name>/<backup_id> directory, where <backup_path> is the value assigned to the <backup_path> parameter in the BART configuration file, <server_name> is the lowercase name of the database server as listed in the configuration file, and <backup_id> is a backup identifier assigned by BART to the particular backup.

• MD5 checksums of the full backup and any user-defined tablespaces are saved as well for tar backups.

• Before performing the backup, BART checks to ensure if there is enough disk space to completely store the backup in the BART backup catalog.

• In the postgresql.conf file, ensure the wal_keep_segments configuration parameter is set to a sufficiently large value. A low setting of the wal_keep_segments configuration parameter may result in the deletion of some WAL files before the BART BACKUP subcommand saves them to the archive_path. For information about the wal_keep_segments parameter, see the PostgreSQL Core Documentation.

• In the BART configuration file, setting xlog_method=stream will instruct the server to stream the transaction log in parallel with creation of the backup for a specific database server; otherwise the transaction log files are collected upon completion of the backup. See the EDB Backup and Recovery Installation and Upgrade Guide available at the EDB website for details about database server setting.

  Note

  If the transaction log streaming method is used, the -Fp option for a plain text backup format must be specified with the BACKUP subcommand.

• When you use BART to take a backup of PostgreSQL server, multiple backups can be taken simultaneously and if a backup is interrupted, the backup mode is terminated automatically without the need to run pg_stop_backup() command manually to terminate the backup.

Options

Along with the BACKUP subcommand, specify the following option:

Specify the following options as required. If you do not specify any of the following options, the backup is created using default settings.

Backup Name Examples

The following examples demonstrate using the --backup-name clause:

./bart backup -s ppas12 -Ft --backup-name "YEAR = %year
MONTH = %month DAY = %day"
./bart backup -s ppas12 -Ft --backup-name "YEAR = %year
MONTH = %month DAY = %day %%"
./bart show-backups -s ppas12 -i "test backup"

Error messages

The following table lists the error messages that may be encountered when using the BACKUP subcommand: