Restore points are only supported in PostgreSQL >= 9.1 so for older versions the check command may fail if there has been no write activity since the last log rotation, therefore it is recommended that activity be generated by the user if there have been no writes since the last WAL switch before running the check command.
#2 different version ubuntu installed parallels 13 archive#
Note that pg_create_restore_point('pgBackRest Archive Check') and pg_switch_xlog()/ pg_switch_wal() are called to force PostgreSQL to archive a WAL segment. The command may also be run on the standby host, however, since pg_switch_xlog()/ pg_switch_wal() cannot be performed on the standby, the command will only test the repository configuration. The command can be run on the PostgreSQL or repository host. It detects misconfigurations, particularly in archiving, that result in incomplete backups because required WAL segments did not reach the archive. It will attempt to check all repositories and databases that are configured for the host on which the command is run. The check command validates that pgBackRest and the archive_command setting are configured correctly for archiving and backups for the specified stanza.
config-include-path is specified: *.conf files in the config include path will be loaded and the path is required to exist.config option is specified: only the specified config file will be loaded and is expected to exist.config and config-include-path are default: the default config file will be loaded, if it exists, and *.conf files in the default config include path will be appended, if they exist.
There are multiple ways the pgBackRest configuration files can be loaded:
0 kommentar(er)
