ts678
March 17, 2025, 2:43pm
5
Hi, I’m running Duplicati 2.1.0.2_beta_2024-11-29.
I changed the remote volume size of a backup task, which caused deleting unwanted files to have a lot of work to do. I noticed that deleting unwanted files only performs put and get operations on remote volumes but does not actually delete them. As a result, the backup backend requires significantly more free space than the backup itself actually needs.
My question is: Why doesn’t it delete already processed volumes immediately after successfu…
was the same early conclusion that was solved after hearing deletes are at end.
opened 04:11PM - 27 Jan 25 UTC
bug
- [x] I have searched open and closed issues for duplicates.
- [x] I have search… ed the [forum](https://forum.duplicati.com) for related topics.
----------------------------------------
## Environment info
- **Duplicati version**: 2.1.0.2
- **Operating system**: N/A
- **Backend**: N/A
## Description
> tl;dr: It will delete the files at then end of the compact step.
per [forum](https://forum.duplicati.com/t/deleting-unwanted-files-does-not-delete-only-get-and-put/19831/12?u=ts678), worst case is free space need equal to backup size.
I suppose `quota-warning-threshold` default of 10 to ensure some early warning should become 110.
As mentioned in forum, this new design makes recovery from a filled fixed-size destination very hard.
[What to do when disk space is full?](https://forum.duplicati.com/t/what-to-do-when-disk-space-is-full/19965) is a possible case. What procedure is likely to work with new way?
is my concern about what that means. This hits super hard if remote volume size change causes compact. Dealing with full destination was tough even before this. Previously if one could free up a tiny space, compact could make more. No more.