Meaning behind "snapshot foo at revision 123 is encoded in an old version format"?

Support
#1

Hi, after updating to duplicacy 3, I started seeing these lines when backing up, listing backups, etc:

snapshot foo at revision 123 is encoded in an old version format

What is the meaning of this message - is it trying to convey a future deprecation, a call to action to fix it, or is it purely information and can be ignored? In which case, do we really need to see it all the time?

Thanks.

#2

This means revision 123 was created in an old snapshot format used by by CLI 2.7.2 or earlier. Version 3.0.1 switched to a new snapshot format but for backward compatibility it can read the old one. You can simply ignore these messages.

#3

Alright, but is there a future where this earlier format is going to be phased out and duplicacy will no longer work with it?

If not, can we get a flag to suppress this warning or turn it off by default since it is of no consequence? Maybe move it to a more verbose level?

1 Like
#4

Doesn’t v3.x update the snapshot format for subsequent revisions, or does it keep the snapshot format the same for the entire snapshot ID?

I assumed, since it could read but not write(?) the older format, subsequent revisions would be upgraded and these messages would simply go away.

Or do we have to create a new snapshot ID with v3.x?

#5

Subsequent revisions might be upgraded, but the message in the OP refers to a specific revision… If :d: doesn’t convert existing revisions, and there are no issues with supporting v2 revisions, I’d prefer not to see these messages either (unless under debug perhaps?). Or perhaps convert all v2 into v3 when running with a specific flag(s)?

1 Like
#6

Makes sense.

Though backups usually don’t look at snapshot files beyond the latest revision, so they should only show up repeatedly with other operations. The message could easily be made debug-only or verbose mode in such cases.

1 Like