How to delete original seed of a single backup job

Support
#1

Hi all,

Apologies if this has been posted before; I’ve had a look and couldn’t find the precise answer to my question.

So, I have Duplicacy running in a Docker container on my Synology NAS. It snapshots certain folders and uploads them to a BitBucket B2 account.
Everything works perfectly, but here’s the problem:

When I first set up the backup, I targeted three folders on my NAS; ‘Video’, ‘Docs’, and ‘General’.
The ‘Video’ folder is huge (1.5TB) and the other two are much, much smaller.

The backup had been running fine for a few months, but I about two months ago I decided I really don’t need the ‘Video’ folder in my Backblaze bucket (it’s too big and pushes costs up).

I tweaked my ‘Prune’ job in the Duplicacy schedule page so it read:

-keep 0:180 -keep 0:30 -keep 1:7 -a -threads 20 -exhaustive

Fast forward to now and I’ve checked my Duplicacy, hoping to see a significant drop in storage by the loss of the ‘Video’ folder. But no loss has taken place.

If I look at the ‘Restore’ option and select the ‘Video’ backup job, Backblaze reports a single image to restore from that reads: “revision 69 created at 2026-02-22 04:00”.

So, clearly the pruning job has done what it was meant to, and keep all the jobs neat and tidy, but I think that I still has the initial snapshot/seed of my ‘Video’ file on Backblaze.
How do I ensure that that snapshot, and only that one, is deleted from the cloud storage?

I don’t want to touch either of the other jobs; they are running fine and need to remain.
I have deleted the job in the ‘Schedule’ tab that used to run those ‘Video’ backups, but I have not removed the actual job from the ‘Backup’ tab; do I need to do that?

Any help greatly appreciated!

#2

For safety, Duplicacy won’t remove the last revision for a snapshot / backup ID, so you’ll have to remove it manually.

The easiest way is to just delete the /snapshots/videos/69 file (or whatever ID you used for videos) in the B2 bucket and then run Prune with options -all -exhaustive -exclusive (making very sure you don’t have any other backup or other jobs running at the same time).

You can technically do it with a targeted prune in the web UI, but you need to be careful to use the right options, as the web UI automatically adds flags like -a and -keep, which isn’t what you want, but you can edit after. You also need to add a ‘temporary’ schedule for this manual task…

  1. Click the green plus icon in the bottom left of the Schedule page
  2. Enter a name, like ‘Cleanup’, untick all the days (Mon-Sun), Save
  3. Add a Prune job, select the right destination, and just accept the default retention policy for now
  4. Click the ‘-keep 0:1800 -keep 7:30 -keep 1:7 -a’ link under Options to edit
  5. Replace these options entirely, with:
-id videos -r 69 -exclusive

Replacing ‘videos’ with whatever ID you used. You can now manually run the schedule by pressing the green play icon. Again, make sure no other jobs are running when using -exclusive.

You can delete the cleanup schedule when you’re finished - i.e. click the clock icon and then Delete this schedule. You can also remove the job from the Backup tab whenever you like.

(As you can see, this process is a bit of a faff when you only need to do it once, which is why it’s generally easier to manually delete the revision file directly off the storage, then cleanup with a generic Prune job with -all -exhaustive -exclusive.)

1 Like
#3

Thanks so much for your help.

Your first suggestion - wiping the actual file in BB and then running a Prune cleanup - worked like a charm and I’ve now removed the offending backup and saved the space I need.