Issue Cloning Standby Node with repmgr in PostgreSQL 17 + Barman 3.14 Setup

[sudha]

Hi everyone,

I’m in the process of setting up a PostgreSQL 17 three-node streaming replication cluster using repmgr for high availability and Barman (version 3.14) for backups and WAL archiving.

On the primary node, backups are running successfully via Barman, and WAL archiving is working as expected. I’m now trying to clone a standby node using repmgr with Barman as the backup source.

When I run the following dry-run command, everything seems fine, But when I execute the actual clone command without --dry-run, I get this error:

I’m not sure why backup.info is being looked for under repmgr/ inside the data directory. Any guidance or suggestions would be greatly appreciated.

Thanks in advance!

[Martin Marques]

Hello,

Have a look at the following issues from the Barman and Repmgr github spaces (the Barman one was closed as it's not a barman problem)

https://github.com/EnterpriseDB/barman/issues/1091

https://github.com/EnterpriseDB/repmgr/issues/896

--
--
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.
To view this discussion, visit https://groups.google.com/d/msgid/pgbarman/e1452902-4a8c-4554-bbe6-18182c97efeen%40googlegroups.com.