Hi all. I’ve been using Duplicacy to backup to Backblaze for… maybe a year now? A while anyway. Generally it works great and is very reliable. However, my Backblaze usage keeps growing and growing and growing… It’s up to 3.6 Tb now because I had never set up a prune job or limited the number of revisions(?). (I’m not entirely sure about the correct terminology here.)
My backup job log looks likes this:
Options: [-log backup -storage Backblaze-B2 -threads 4 -limit-rate 3000 -stats -stats] 2023-09-03 03:00:01.642 INFO REPOSITORY_SET Repository set to /backuproot 2023-09-03 03:00:01.642 INFO STORAGE_SET Storage set to b2://grigsby-citadel-duplicacy 2023-09-03 03:00:01.765 INFO BACKBLAZE_URL download URL is: https://f000.backblazeb2.com 2023-09-03 03:00:03.159 INFO BACKUP_START Last backup at revision 287 found 2023-09-03 03:00:04.262 INFO BACKUP_INDEXING Indexing /backuproot
So there are roughly 287 revisions, which is way more than I need. I’d like to reduce my Backblaze usage to about a month’s worth of backups.
A few weeks ago I added a prune job to run once a week with the following arguments:
-log prune -storage Backblaze-B2 -keep 0:30
The log says
2023-08-30 06:00:01.306 INFO STORAGE_SET Storage set to b2://grigsby-citadel-duplicacy 2023-08-30 06:00:01.449 INFO BACKBLAZE_URL download URL is: https://f000.backblazeb2.com 2023-08-30 06:00:02.948 INFO RETENTION_POLICY Keep no snapshots older than 30 days 2023-08-30 06:00:12.045 INFO SNAPSHOT_NONE No snapshot to delete
So my Backblaze usage hasn’t gone down, and duplicacy seems to think there’s nothing to delete. What am I doing wrong? How do I run a prune command to delete everything older than 30 days?
Thank you very much!