Misleading log message from CLI

Support
#1

I have a very old duplicacy datastore from an old Mac which did not change for a very long time, and it only gets pruned from time to time.

me@Tuchka:/volume1/Backups/duplicacy/snapshots/me-imac$ ls -alt
total 20
drwxrwxrwx+ 1 me users   36 Oct 23  2019 .
drwxrwxrwx+ 1 me users   88 Jan  3  2019 ..
-rwxrwxrwx+ 1 me users 2072 Jul 12  2018 2094
-rwxrwxrwx+ 1 me users 2476 Jun 17  2018 1803
-rwxrwxrwx+ 1 me users 2342 May 12  2018 1257
-rwxrwxrwx+ 1 me users 2476 Apr  5  2018 860
-rwxrwxrwx+ 1 me users 1674 Feb 28  2018 146

This is what I see when I run prune over sftp:

me@obsidian ~ % duplicacy prune -keep 31:360 -keep 7:90 -keep 1:14 -a
Storage set to sftp://me@synology.nas//Backups/duplicacy
Keep 1 snapshot every 31 day(s) if older than 360 day(s)
Keep 1 snapshot every 7 day(s) if older than 90 day(s)
Keep 1 snapshot every 1 day(s) if older than 14 day(s)
Fossil collection 1 found
Ignore snapshot me-imac whose last revision was created 7 days ago
Ignore snapshot users-imac whose last revision was created 7 days ago
Fossils from collection 1 can't be deleted because deletion criteria aren't met
No snapshot to delete

I don’t understand what does Ignore snapshot me-imac whose last revision was created 7 days ago mean since its literal meaning does not reconcile with reality.

Duplicacy version 2.5.1 (51CBF7)

#2

For a fossil to be permanently deletable, a new backup is expected from each snapshot id (in order to make sure that the fossil to be deleted is not referenced by any ongoing backup). However, those two snapshot ids haven’t done any backup in the last 7 days, so Duplicacy viewed them as becoming dormant and excluded them when evaluating fossils for deletion (otherwise Duplicacy would not be able to prune any chunk once a snapshot id stops running backups).

The message Fossils from collection 1 can't be deleted means a new backup is expected from at least one other snapshot id. It has nothing to do with those two ids.

1 Like
#3

Ah, got it, so the message was supposed to read “Ignore snapshot me-imac whose last revision was created over 7 days ago”. Then it would be correct.

To clarify — I’m not questioning backup/prune correctness, just the wording of the message.

3 Likes
#4

Right, it is so obvious now that you pointed it out. I’ll fix it.

3 Likes