Hello there.
I'm making backup doc_mng3 server, but it takes forever (not a joke, tested for 3 days)
Database is rly small it's about 15 Gb. (Wanna backup 0,5Tb in future)
[root@asu-dev-db-pm-01 /]# barman -d backup doc_mng3
Starting backup using rsync-concurrent method for server doc_mng3 in /asudevzfs/backups/doc_mng3/base/20250307T152712
DEBUG: detecting data directory
DEBUG: detecting tablespaces
I can fix it by using:
barman switch-xlog --force doc_mng3
After fix it makes.
[root@asu-dev-db-pm-01 /]# barman -d backup doc_mng3
Starting backup using rsync-concurrent method for server doc_mng3 in /asudevzfs/backups/doc_mng3/base/20250307T152712
DEBUG: detecting data directory
DEBUG: detecting tablespaces
Backup start at LSN: 30/4F016FB0 (00000013000000300000004F, 00016FB0)
Starting backup copy via rsync/SSH for 20250307T152712 (4 jobs)
Copy done (time: 2 minutes, 20 seconds)
Asking PostgreSQL server to finalize the backup.
DEBUG: Writing backup label: /asudevzfs/backups/doc_mng3/base/20250307T152712/data/backup_label
Backup size: 14.7 GiB
Backup end at LSN: 30/63B57B98 (000000130000003000000063, 00B57B98)
Backup completed (start time: 2025-03-07 15:37:17.002718, elapsed time: 2 minutes, 23 seconds)
DEBUG: Starting archive-wal for server doc_mng3
Processing xlog segments from streaming for doc_mng3
000000130000003000000063
000000130000003000000064
Processing xlog segments from file archival for doc_mng3
00000013000000300000004F.00016FB0.backup
000000130000003000000063
DEBUG: Checking backup 20250307T152712 of server doc_mng3
DEBUG: Check finished: the status of backup 20250307T152712 of server doc_mng3 changed from WAITING_FOR_WALS to DONE
barman check is here:
[root@asu-dev-db-pm-01 /]# barman check doc_mng3 o
Server doc_mng3:
PostgreSQL: OK
superuser or standard user with backup privileges: OK
PostgreSQL streaming: OK
wal_level: OK
replication slot: OK
directories: OK
retention policy settings: OK
backup maximum age: OK (no last_backup_maximum_age provided)
backup minimum size: OK (14.7 GiB)
wal maximum age: OK (no last_wal_maximum_age provided)
wal size: OK (32.0 MiB)
compression settings: OK
failed backups: FAILED (there are 1 failed backups)
minimum redundancy requirements: OK (have 2 backups, expected at least 0)
ssh: OK (PostgreSQL server)
systemid coherence: OK
pg_receivexlog: OK
pg_receivexlog compatible: OK
receive-wal running: OK
archive_mode: OK
archive_command: OK
continuous archiving: OK
archiver errors: OK
doc_mng3.conf here:
[doc_mng3]
description = "patroni doc_mng3"
ssh_command = ssh postgres@XXX
conninfo = host=10.102.101.52 port=5003 user=postgres dbname=postgres password=RXXX
streaming_conninfo = host=10.102.101.52 port=5003 user=barman password=XXX
backup_method = rsync
reuse_backup = link
backup_options = concurrent_backup
parallel_jobs = 4
backup_directory = /asudevzfs/backups/doc_mng3
archiver = on
retention_policy = RECOVERY WINDOW OF 7 DAYS
slot_name = barman
create_slot = auto
streaming_archiver = on
incoming_wals_directory = /asudevzfs/backups/doc_mng3/incoming
What can I do to fix this?
(just 1 base of 3 have this problem)
barman version:
[root@asu-dev-db-pm-01 /]# barman -v
3.12.1 Barman by EnterpriseDB (
www.enterprisedb.com)