From f3dbf47547e659f1797495b65a623382435805c0 Mon Sep 17 00:00:00 2001 From: Quentin Dufour Date: Fri, 28 Jan 2022 19:11:58 +0100 Subject: [PATCH] Ajout de pg_verifybackup --- op_guide/stolon/manual_backup.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/op_guide/stolon/manual_backup.md b/op_guide/stolon/manual_backup.md index 1e02ac4..fa7e13f 100644 --- a/op_guide/stolon/manual_backup.md +++ b/op_guide/stolon/manual_backup.md @@ -99,6 +99,18 @@ You should have something like that: 00000003000014AF000000C9 00000003000014AF000000CA 00000003.history archive_status ``` +Before restoring our backup, we want to check it: + +```bash +cd /tmp/sql/pg_data +cp ../backup_manifest . +# On ne vérifie pas le WAL car il semblerait que ça marche pas trop +# Cf ma référence en bas capdata.fr +# pg_verifybackup -w ../wal . +pg_verifybackup -n . + +``` + Now, We must edit/read some files before launching our ephemeral server: - Set `listen_addresses = '0.0.0.0'` in `postgresql.conf` - Add `restore_command = 'cp /mnt/wal/%f %p' ` in `postgresql.conf` @@ -290,3 +302,4 @@ https://www.cybertec-postgresql.com/en/pg_basebackup-creating-self-sufficient-ba https://www.postgresql.org/docs/14/continuous-archiving.html https://www.postgresql.org/docs/14/backup-dump.html#BACKUP-DUMP-RESTORE https://dba.stackexchange.com/questions/75033/how-to-restore-everything-including-postgres-role-from-pg-dumpall-backup +https://blog.capdata.fr/index.php/postgresql-13-les-nouveautes-interessantes/