repmgr standby clone doesn't work with compressed barman backups
Opened this issue · 3 comments
Barman 3.x added compressed backups via pg_basebackup, not available in earlier versions of barman. This adds a complexity that was not taken into account when designing the clone from a barman backup feature, given that compressed backups were not a feature then. This brought up the issue in which the files we recover from a barman backup are not always the uncompressed data files, but rather the base.tar.gz created by pg_basebackup (not to mention that there might also be tablespace tarballs as well).
The easiest solution here is to change the rsync which fetches the files from the backup on the barman server for barman recover which will take care of the decision-making on whether to uncompress, what to uncompress and where to place the files.
I have the same scenario of BARMAN compressed backups. When I am trying to clone a standby using BARMAN. It is not extracting the whole base.tar.gz file and on starting up the Postgres, message says, this is not a cluster directory.
Can you share what changes have been made with rsync to make this work?
Appreciate your help.
Ravi
Thanks, I got your point. Please ignore the above question. I was thinking that there is some parameter that I can enable in repmgr.conf.
We will have a fix for using compressed backups, but it will come in the form of an external rest-API for barman. No ETA yet