Similar to the original issue #227 after completing a major upgrade I have updated the old server to be inactive.
Not being able to run barman list-backups on the old server was an unpleasant surprise.
I can see there was a pull request #722 opened to support this but both the issue and the pull request appear to have been closed as part of a widespread issue reset.
Can this be reconsidered?
At the very least I would like to be able to run list-backups and show-backup.
A nice to have would also be recover but I could understand if that is not considered acceptable.
Maybe there should be some kind of alternative status beyond just active=true/false to identify an old server that is no longer backing up and is in the process of aging out. A server in this state could be handled by barman cron to enforcing it's retention policies.