On Tue, Mar 8, 2022 at 11:51 AM dulhaver via Barman, Backup and
Recovery Manager for PostgreSQL <pgba...@googlegroups.com
> I guess this may be what the manual calls streaming-only which "does not require any SSH connection for backup and archiving operations. This is particularly suitable and extremely practical for Docker environments." I seem not being able to extract the right breadcrumbs applying for such a scenario from the manual to get this going. Definitely nothing works without ssh in the state I am in right now.
Streaming happens on a request basis: barman (via barman cron, that in
turns starts a pg_walreceiver) asks for wals to PostgreSQL.
On the other hand, archiving happens on a push basis: PostgreSQL
pushes wals thru the archive_command.
You need archive_mode = off (in PostgreSQL), or archive_command =
/bin/true (in PostgreSQL) and archiver = off in barman.
> On the other hand I am at a point where I do not care any longer about what exactly is happening or how it is called as long as I can make it work. Or if anybody recommends other modes then streaming only I am all open)
Backup is the easy part, recovery is the hardest one. If you don't
know what you are doing, you probably will not be able to recover.
> archive_command: FAILED (please set it accordingly to documentation)
I suspect because you have archiver = on in barman.
> that actually seems to work with the archive_commmand mentioned above. I am not understanding the different though.
> Is there anything that would be recommended?
Yes, read again this thread, we explained it quite clearly.
> So again ... my goal was to got the streaming only path, but I seem unable to find that.
Starting from scratch with barman configuration could help.
> My problem is that I am writing a paper for my exam on a comparison barman/pgBackRest and and struggling really hard an the barman side. I admin not to be super experienced with postgres (which is my personal weakness) and may have chosen the wrong topic for such a paper due to that. But there is not way back now any longer and I need to get something going, so I can at least take Barman into the comparison (beyond stating that I could not make Barman work).
In my experience, barman has been simpler to configure than
pgbackrest. Also, as you probably already discovered, pgbackrest
requires ssh to work properly always.