Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-11 Thread Adrian Klaver
On 8/11/21 1:18 PM, Matthias Apitz wrote: El día jueves, agosto 12, 2021 a las 12:47:32a. m. +0530, Vijaykumar Jain escribió: Could some kind sol acknowledge me that this is the correct procedure to use pg_verifybackup? Thanks in advance ... postgres@db:~/playground/demo/basebackup$

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-11 Thread Vijaykumar Jain
On Thu, 12 Aug 2021 at 01:48, Matthias Apitz wrote: > This is exactly the point of my question (and I figured it out too): > Where is this explained that «pg_wal.tar.gz file has to uncompressed in > pg_wal dir»? > > indeed, I am not able to find or search relative reference in docs (i never used

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-11 Thread Matthias Apitz
El día jueves, agosto 12, 2021 a las 12:47:32a. m. +0530, Vijaykumar Jain escribió: > > > > > > Could some kind sol acknowledge me that this is the correct procedure to > > use pg_verifybackup? Thanks in advance > > > > > ... > >postgres@db:~/playground/demo/basebackup$ tar xzf base.tar.gz >

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-11 Thread Vijaykumar Jain
btw, you can also use pgbackrest for backups. i'll let docs do the talking, pgBackRest - Reliable PostgreSQL Backup & Restore but it can help you manage incremental and differential and full backups along with parallel support. (so fast and less bandwidth) also a quick on

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-11 Thread Vijaykumar Jain
> > > Could some kind sol acknowledge me that this is the correct procedure to > use pg_verifybackup? Thanks in advance > > postgres@db:~/playground/demo$ initdb -D db 2>/dev/null 1>&2 postgres@db:~/playground/demo$ pg_ctl -D db -l logfile start 2>/dev/null 1>&2 postgres@db:~/playground/demo$ psql

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-11 Thread Matthias Apitz
El día martes, agosto 10, 2021 a las 11:38:57a. m. +0200, Matthias Apitz escribió: > I think, I sorted it out by doing this: > > I moved away the tar-archives: > > $ cd /data/postgresql133/backup-20210810-1 > $ mkdir ../saved > $ mv *.tar.gz ../saved > > I unpacked 'base.tar.gz' the usual way:

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-10 Thread Matthias Apitz
El día martes, agosto 10, 2021 a las 09:23:34a. m. +0200, Matthias Apitz escribió: > I've studied now the fine docs again and have some additional questions. The > backup was done fine to the directory /data/postgresql133/backup-20210810-1 > which contains now: > > $ ls -l > total 717252 > -rw--

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-10 Thread Matthias Apitz
El día lunes, agosto 09, 2021 a las 01:32:58p. m. -0700, Adrian Klaver escribió: > https://www.postgresql.org/docs/13/app-pgverifybackup.html > > "pg_verifybackup is used to check the integrity of a database cluster backup > taken using pg_basebackup against a backup_manifest generated by the ser

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-09 Thread Matthias Apitz
El día lunes, agosto 09, 2021 a las 01:32:58p. m. -0700, Adrian Klaver escribió: > > > > What we do wrong here with pg_verifybackup? > > Not read the docs?: > > https://www.postgresql.org/docs/13/app-pgverifybackup.html > > "pg_verifybackup is used to check the integrity of a database cluster

Re: (13.1) pg_basebackups ./. pg_verifybackup

2021-08-09 Thread Adrian Klaver
On 8/9/21 1:15 PM, Matthias Apitz wrote: Hello, We do backups with something like: $ pg_basebackup -U ${DBSUSER} -Ft -z -D ${BACKUPDIR}-${DATE}-${NUM} and they seems to work fine: $ ls -l backup-20210809-1/ total 7656108 -rw--- 1 postgres postgres4191873 Aug 9 14:19 backup_manifest -