How do I stop WAL streaming in BARMAN cron?
0
votes
1
answer
4506
views
I am having an issue "resetting" or fixing a backup server I have in BARMAN:
-bash-4.2$ barman check *server-name*
Server *server-name*:
PostgreSQL: OK
superuser or standard user with backup privileges: 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
systemid coherence: OK
archive_mode: OK
archive_command: OK
continuous archiving: FAILED
archiver errors: FAILED (duplicates: 1, unknown: 1)
Looking at the BARMAN documentation, it gives a procedure to stop WAL logging.
>The cron command ensures that WAL streaming is started for those servers that have requested it, by transparently executing the receive-wal command.
>In order to stop the operations started by the cron command, comment out the cron entry and execute:
>receive-wal --stop SERVER_NAME
>You might want to check barman list-server to make sure you get all of your servers.
How do we "comment out the cron entry"? I don't see it in the barman user crontab if I do a -l
. I assume we use some form of cron
but I dont see any options?
Currently I am not backing up this server, but the WAL logs are still getting copied.
Any ideas or help would be very appreciated! Thanks!
Asked by Troy Meyerink
(1 rep)
Jul 30, 2021, 06:37 PM
Last activity: Feb 9, 2025, 01:03 AM
Last activity: Feb 9, 2025, 01:03 AM