Barman base backup process locks up

149 views
Skip to first unread message

Fábio Peruchi

unread,
Apr 29, 2016, 5:38:46 PM4/29/16
to Barman, Backup and Recovery Manager for PostgreSQL, Infra Operações
Hi!

I'm trying to do a base backup with Barman 1.6.0 of the folowing database server bmw-test that have only 25.2 MB and it locks up:

barman -v
1.6.0

/etc/barman.conf

; Main configuration file

[barman]
; Main directory
barman_home = /tecsinapse/data/barman

; System user
barman_user = jenkins

; Log location
log_file = /var/log/barman/barman.log

; Default compression level: possible values are None (default), bzip2, gzip or custom
compression = gzip

; Pre/post backup hook scripts
;pre_backup_script = export PGUSER=postgres;export PGPASSWORD="!ts@psql!";
;post_backup_script = env | grep ^BARMAN

; Directory of configuration files. Place your sections in separate files with .conf extension
; For example place the 'main' server section in /etc/barman.d/main.conf
configuration_files_directory = /etc/barman.d

; Minimum number of required backups (redundancy)
minimum_redundancy = 0

; Global retention policy (REDUNDANCY or RECOVERY WINDOW) - default empty
retention_policy = 

; Global bandwidth limit in KBPS - default 0 (meaning no limit)
bandwidth_limit = 0

; 'main' PostgreSQL Server configuration
[bmw-test]
description =  "BMW Test PostgreSQL Database"
; SSH options
; PostgreSQL connection string
conninfo = host=bmwtest.portaltecsinapse.com.br user=postgres password=*******


barman status bmw-test
Server bmw-test:
Description: BMW Test PostgreSQL Database
Active: True
Disabled: False
PostgreSQL version: 9.3.12
pgespresso extension: Not available
Current data size: 25.2 MiB
PostgreSQL Data directory: /tecsinapse/data/postgresql
PostgreSQL 'archive_command' setting: rsync -a %p jen...@52.67.27.76:/tecsinapse/data/barman/bmw_test/incoming/%f
Last archived WAL: No WAL segment shipped yet
Current WAL segment: 00000001000000010000004C
Retention policies: not enforced
No. of available backups: 0
First available backup: None
Last available backup: None
Minimum redundancy requirements: satisfied (0/0)

barman check bmw-test
Server bmw-test:
PostgreSQL: OK
wal_level: OK
directories: OK
retention policy settings: OK
backup maximum age: OK (no last_backup_maximum_age provided)
compression settings: OK
failed backups: OK (there are 0 failed backups)
minimum redundancy requirements: OK (have 0 backups, expected at least 0)
ssh: OK (PostgreSQL server)
not in recovery: OK
archive_mode: OK
archive_command: OK
archiver errors: OK

See the log below. The process stops on the last line:

barman backup bmw-test
2016-04-29 18:23:08,174 [1864] barman.backup INFO: Starting backup for server bmw-test in /tecsinapse/data/barman/bmw-test/base/20160429T182308
2016-04-29 18:23:08,294 [1864] barman.backup_executor INFO: Backup start at xlog location: 1/4B000028 (00000001000000010000004B, 00000028)
2016-04-29 18:23:08,294 [1864] barman.backup_executor INFO: This is the first backup for server bmw-test
2016-04-29 18:23:08,305 [1864] barman.backup_executor INFO: Copying files.
2016-04-29 18:23:08,306 [1864] barman.command_wrappers INFO: Smart copy: ':/tecsinapse/data/postgresql/' -> '/tecsinapse/data/barman/bmw-test/base/20160429T182308/data' (ref: None, safe before None)
2016-04-29 18:23:08,306 [1864] barman.command_wrappers INFO: Smart copy step 1/4: preparation
2016-04-29 18:23:08,797 [1864] barman.command_wrappers INFO: Smart copy finished: :/tecsinapse/data/postgresql/ -> /tecsinapse/data/barman/bmw-test/base/20160429T182308/data (safe before None)
2016-04-29 18:25:14,558 [1905] barman.backup INFO: Starting backup for server bmw-test in /tecsinapse/data/barman/bmw-test/base/20160429T182514
2016-04-29 18:25:15,070 [1905] barman.backup_executor INFO: Backup start at xlog location: 1/4C000028 (00000001000000010000004C, 00000028)
2016-04-29 18:25:15,071 [1905] barman.backup_executor INFO: This is the first backup for server bmw-test
2016-04-29 18:25:15,084 [1905] barman.backup_executor INFO: Copying files.
2016-04-29 18:25:15,085 [1905] barman.command_wrappers INFO: Smart copy: ':/tecsinapse/data/postgresql/' -> '/tecsinapse/data/barman/bmw-test/base/20160429T182514/data' (ref: None, safe before None)
2016-04-29 18:25:15,085 [1905] barman.command_wrappers INFO: Smart copy step 1/4: preparation
2016-04-29 18:25:15,538 [1905] barman.command_wrappers INFO: Smart copy finished: :/tecsinapse/data/postgresql/ -> /tecsinapse/data/barman/bmw-test/base/20160429T182514/data (safe before None)

Please, can you help me?

Thanks in advance.
Fábio Peruchi

Gabriele Bartolini

unread,
Apr 29, 2016, 9:15:08 PM4/29/16
to pgba...@googlegroups.com, Infra Operações
Hi Fabio,

 Thanks for using Barman!

 Are you sure that WAL archiving is correctly working?

Regards
Gabriele 
Inviato da iPhone
--
--
You received this message because you are subscribed to the "Barman for PostgreSQL" group.
To post to this group, send email to pgba...@googlegroups.com
To unsubscribe from this group, send email to
pgbarman+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/pgbarman?hl=en?hl=en-GB

---
You received this message because you are subscribed to the Google Groups "Barman, Backup and Recovery Manager for PostgreSQL" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pgbarman+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fábio Peruchi

unread,
May 2, 2016, 1:43:34 PM5/2/16
to Gabriele Bartolini, pgba...@googlegroups.com, Infra Operações
Thanks Gabriele.

I fixed WAL archiving and now it's working correctly.

Regards,
Fabio


logo tecsinapse
Fábio Peruchi
DevOps / Operações
ícone email fabio.peruchi​@​​tecsinapse​​.​com​​.​​br​
ícone phone (19) 98205-4446
ícone skype fabio_peruchi

Esta mensagem, incluindo seus anexos, tem caráter confidencial e seu conteúdo é restrito ao destinatário da mensagem. Caso você a tenha recebido por engano, queira, por favor, retorná-la ao destinatário e apagá-la de seus arquivos. Qualquer uso não autorizado, replicação ou disseminação desta mensagem ou parte dela é expressamente proibido. A TecSinapse não se responsabilizará pelo conteúdo ou pela veracidade desta informação.

Reply all
Reply to author
Forward
0 new messages