How do I monitor the streaming backup process?

874 views
Skip to first unread message

Dipanjan Das

unread,
Jun 14, 2021, 1:29:39 PM6/14/21
to Barman, Backup and Recovery Manager for PostgreSQL

Hello,

I am using streaming backup feature of barman. I can see the WAL data getting fetched from the psql server to my barman server. To monitor if the fetch is happening right, I am manually watching the `pg_wal` directory of the psql server, and also the "streaming" and "wal" directories of the barman servers. I am sure this is not what people do. I am aware of the barman status" and "barman replication-status" commands. But, I failed to find (did I miss it?) the information that says until what time the backup has been done, including the WALs. I think the "Last available backup" in "barman status" command's output actually shows the time when the last full backup was taken, disregarding the WALs. How do I find that information?

Abhijit Menon-Sen

unread,
Jul 29, 2021, 10:56:00 AM7/29/21
to pgba...@googlegroups.com
On Mon, Jun 14, 2021 at 10:59 PM Dipanjan Das
<mail.dip...@gmail.com> wrote:
>
>
> I am using streaming backup feature of barman. I can see the WAL data getting fetched from the psql server to my barman server. To monitor if the fetch is happening right, I am manually watching the `pg_wal` directory of the psql server, and also the "streaming" and "wal" directories of the barman servers. I am sure this is not what people do. I am aware of the barman status" and "barman replication-status" commands. But, I failed to find (did I miss it?) the information that says until what time the backup has been done, including the WALs. I think the "Last available backup" in "barman status" command's output actually shows the time when the last full backup was taken, disregarding the WALs. How do I find that information?

Two answers: (a) `barman check` will tell you if there's something
wrong; (b) `barman show-backup servername latest` will give you
information about the latest backup (or you can pass a different
backup id).

Here's a random example of the output:

barman@unarmed:~$ barman show-backup uptight latest
Backup 20210723T070008:
Server Name : uptight
System Id : 6985025709346482144
Status : DONE
PostgreSQL Version : 110012
PGDATA directory : /opt/postgres/data
Tablespaces:
example: /opt/postgres/ts (oid: 16588)

Base backup information:
Disk usage : 178.7 MiB (178.7 MiB with WALs)
Incremental size : 151.6 MiB (-15.14%)
Timeline : 1
Begin WAL : 000000010000000000000045
End WAL : 000000010000000000000045
WAL number : 1
WAL compression ratio: 99.89%
Begin time : 2021-07-23 07:00:08.082259+00:00
End time : 2021-07-23 07:00:13.028611+00:00
Copy time : 4 seconds
Estimated throughput : 37.7 MiB/s
Begin Offset : 40
End Offset : 248
Begin LSN : 0/45000028
End LSN : 0/450000F8

WAL information:
No of files : 31
Disk usage : 13.6 MiB
WAL rate : 0.21/hour
Compression ratio : 97.25%
Last available : 000000010000000000000064

Catalog information:
Retention Policy : VALID
Previous Backup : 20210715T064112
Next Backup : - (this is the latest base backup)

-- Abhijit
Reply all
Reply to author
Forward
0 new messages