Barman 3.10.1 can't list backups created by Barman 3.11.1 (due to new "children_backup_ids" attribute)

[Aleksey Tsalolikhin]

Hello,

We deployed a new production database server which was loaded with Barman 3.11.1.

Our other (older) database server has Barman 3.10.1.

I was just doing our regular backups recovery test (testing that we can recover from backups) and I found that our recovery test instance, which has Barman 3.10.1, cannot list the backups created with Barman 3.11.1.

I get messages like this:

WARNING: Unable to open backup.info file for 20241028T040001: 'BackupInfo' object has no attribute 'children_backup_ids'

I see that Barman 3.11 has a new feature where it supports incremental Postgres backups.  I suppose that's where "children_backup_ids" came from.

I updated Barman on my recovery test instance to 3.11.1, and it can list backups from the older database server which is running barman 3.10.1 and the newer database server which is running barman 3.11.1.

You might want to mark the incremental backups support as a breaking change in https://pgbarman.org/barman-3-11-0-released/ and any place else you have the release notes.

Thanks for continuing to improve pgBarman!

Best,

Aleksey

--

www.teramind.co

Aleksey Tsalolikhin Senior DevOps Engineer atsalo...@teramind.co

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

[Giulio Calacoci]

Hi Aleksey,

My personal opinion on this is that your scenario is a bit odd or if you want a corner case.

In general, as far as I can remember, an older version of Barman has never been guaranteed to be able to read the catalogue of a newer one...

In fact Barman is backwards compatible but, as stated multiple times in the past in this very same group, you should always use the latest version of Barman on your server(s).

So updating to the latest one like you did is always the correct course of action.

In any case, we will discuss your suggestion internally, thank you for your feedback.

Ciao,

Giulio

--
--
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/CAJPuHtXa94-VR%3DVmArmvndQSt1Nv%2B7koS6AZ0ys-grpMy36kdQ%40mail.gmail.com.

[Aleksey Tsalolikhin]

Thanks, Giulio, that makes sense. I appreciate your reply.  :)

To view this discussion, visit https://groups.google.com/d/msgid/pgbarman/CAJAbkKV0Z4qX%3DD2kvfAX%3DbwMxvO5vtUyrFoYg_x5HhP%2BBcTf-w%40mail.gmail.com.