db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-14 10:13:05 +02:00
Code Issues Releases Activity
eff7b46eb1
pgbackrest/test/expect/backup-full-010.log

116 lines
4.2 KiB
Plaintext
Raw Normal View History

More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
run 010 - bkp 1, sby 0, dst backup, asy 1, cmp 1
================================================
full backup - update during backup (backup host)
> [CONTAINER-EXEC] backup [BACKREST-BIN] --config=[TEST_PATH]/backup/pgbackrest.conf --type=full --stanza=db backup --test --test-delay=1 --test-point=manifest-build=y
------------------------------------------------------------------------------------------------------------------------------------
+ supplemental file: [TEST_PATH]/db-master/pgbackrest.conf
----------------------------------------------------------
[db]
db-path=[TEST_PATH]/db-master/db/base
db-port=[PORT-1]
db-socket-path=[TEST_PATH]/db-master/db
[global]
backup-cmd=[BACKREST-BIN]
backup-config=[TEST_PATH]/backup/pgbackrest.conf
backup-host=backup
Regression tests can now be run as any properly-configured user, not just vagrant.
2016-10-01 19:39:44 +02:00
backup-user=[USER-1]
More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
lock-path=[TEST_PATH]/db-master/spool/lock
log-level-console=debug
log-level-file=trace
Added the log-level-stderr option. Controls whether console log messages are sent to stderr or stdout. By default this is set to warn which represents a change in behavior from previous versions, even though it may be more intuitive. Setting log-level-stderr=off will preserve the old behavior. Suggested by Sascha Biberhofer.
2016-10-05 15:09:30 +02:00
log-level-stderr=off
More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
log-path=[TEST_PATH]/db-master/spool/log
repo-path=[TEST_PATH]/backup/repo
spool-path=[TEST_PATH]/db-master/spool
[global:archive-push]
archive-async=y
+ supplemental file: [TEST_PATH]/backup/pgbackrest.conf
-------------------------------------------------------
[db]
db-cmd=[BACKREST-BIN]
db-config=[TEST_PATH]/db-master/pgbackrest.conf
db-host=db-master
db-path=[TEST_PATH]/db-master/db/base
Regression tests can now be run as any properly-configured user, not just vagrant.
2016-10-01 19:39:44 +02:00
db-user=[USER-2]
More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
[global]
lock-path=[TEST_PATH]/backup/repo/lock
log-level-console=debug
log-level-file=trace
Added the log-level-stderr option. Controls whether console log messages are sent to stderr or stdout. By default this is set to warn which represents a change in behavior from previous versions, even though it may be more intuitive. Setting log-level-stderr=off will preserve the old behavior. Suggested by Sascha Biberhofer.
2016-10-05 15:09:30 +02:00
log-level-stderr=off
More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
log-path=[TEST_PATH]/backup/repo/log
repo-path=[TEST_PATH]/backup/repo
[global:backup]
archive-copy=y
start-fast=y
incr backup - update during backup (backup host)
> [CONTAINER-EXEC] backup [BACKREST-BIN] --config=[TEST_PATH]/backup/pgbackrest.conf --stop-auto --no-archive-check --stanza=db backup --test --test-delay=1 --test-point=manifest-build=y
------------------------------------------------------------------------------------------------------------------------------------
+ supplemental file: [TEST_PATH]/db-master/pgbackrest.conf
----------------------------------------------------------
[db]
db-path=[TEST_PATH]/db-master/db/base
db-port=[PORT-1]
db-socket-path=[TEST_PATH]/db-master/db
[global]
backup-cmd=[BACKREST-BIN]
backup-config=[TEST_PATH]/backup/pgbackrest.conf
backup-host=backup
Regression tests can now be run as any properly-configured user, not just vagrant.
2016-10-01 19:39:44 +02:00
backup-user=[USER-1]
More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
lock-path=[TEST_PATH]/db-master/spool/lock
log-level-console=debug
log-level-file=trace
Added the log-level-stderr option. Controls whether console log messages are sent to stderr or stdout. By default this is set to warn which represents a change in behavior from previous versions, even though it may be more intuitive. Setting log-level-stderr=off will preserve the old behavior. Suggested by Sascha Biberhofer.
2016-10-05 15:09:30 +02:00
log-level-stderr=off
More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
log-path=[TEST_PATH]/db-master/spool/log
repo-path=[TEST_PATH]/backup/repo
spool-path=[TEST_PATH]/db-master/spool
[global:archive-push]
archive-async=y
+ supplemental file: [TEST_PATH]/backup/pgbackrest.conf
-------------------------------------------------------
[db]
db-cmd=[BACKREST-BIN]
db-config=[TEST_PATH]/db-master/pgbackrest.conf
db-host=db-master
db-path=[TEST_PATH]/db-master/db/base
Regression tests can now be run as any properly-configured user, not just vagrant.
2016-10-01 19:39:44 +02:00
db-user=[USER-2]
More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
[global]
lock-path=[TEST_PATH]/backup/repo/lock
log-level-console=debug
log-level-file=trace
Added the log-level-stderr option. Controls whether console log messages are sent to stderr or stdout. By default this is set to warn which represents a change in behavior from previous versions, even though it may be more intuitive. Setting log-level-stderr=off will preserve the old behavior. Suggested by Sascha Biberhofer.
2016-10-05 15:09:30 +02:00
log-level-stderr=off
More flexible configuration for databases Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
2016-08-24 18:39:27 +02:00
log-path=[TEST_PATH]/backup/repo/log
repo-path=[TEST_PATH]/backup/repo
[global:backup]
archive-copy=y
start-fast=y
restore, type 'default' (db-master host)
> [CONTAINER-EXEC] db-master [BACKREST-BIN] --config=[TEST_PATH]/db-master/pgbackrest.conf --db-include=test1 --link-all --stanza=db restore
------------------------------------------------------------------------------------------------------------------------------------
+ supplemental file: [TEST_PATH]/db-master/db/base/recovery.conf
----------------------------------------------------------------
restore_command = '[BACKREST-BIN] --config=[TEST_PATH]/db-master/pgbackrest.conf --stanza=db archive-get %f "%p"'
restore delta, backup '[BACKUP-FULL-1]', type 'time', target '[TIMESTAMP-TARGET-1]' (db-master host)
> [CONTAINER-EXEC] db-master [BACKREST-BIN] --config=[TEST_PATH]/db-master/pgbackrest.conf --delta --set=[BACKUP-FULL-1] --type=time --target="[TIMESTAMP-TARGET-1]" --link-all --stanza=db restore
------------------------------------------------------------------------------------------------------------------------------------
+ supplemental file: [TEST_PATH]/db-master/db/base/recovery.conf
----------------------------------------------------------------
restore_command = '[BACKREST-BIN] --config=[TEST_PATH]/db-master/pgbackrest.conf --stanza=db archive-get %f "%p"'
recovery_target_time = '[TIMESTAMP-TARGET-1]'
Reference in New Issue Copy Permalink