I'm struggling to work out how to restart barman after recovering the attached database server with a VM snapshot and data reload.
When I run barman check db I get
Server db: PostgreSQL: OK superuser or standard user with backup privileges: OK PostgreSQL streaming: 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 3 backups, expected at least 0) ssh: OK (PostgreSQL server) systemid coherence: OK pg_receivexlog: OK pg_receivexlog compatible: OK receive-wal running: FAILED (See the Barman log file for more details) archive_mode: OK archive_command: OK continuous archiving: OK archiver errors: FAILED (duplicates: 283)
Barman is correctly grumpy about having WAL files chopped off and resent and I'm happy to just blow away the current backups and WALS and start again from now (if that makes sense), but I can't for the life of me work out how.
I have tried rebuilding the xlogdb, tried to move the data directory, but couldn't because its in use.
Ive tried barman switch-wal --force --archive db but got a bunch of lines
Error: 000000010000009D0000009F is already present in server db. File moved to errors directory. 000000010000009D000000A0 Error: 000000010000009D000000A0 is already present in server db. File moved to errors directory. 000000010000009D000000A1 Error: 000000010000009D000000A1 is already present in server db. File moved to errors directory. 000000010000009D000000A2 Error: 000000010000009D000000A2 is already present in server db. File moved to errors directory. 000000010000009D000000A3 Error: 000000010000009D000000A3 is already present in server db. File moved to errors directory.
I'm really at a loss here. There are a bunch of files in Error, but as I said, I'm not trying to get the current backups working, just want to start again. How do you do that?