On 7/11/22 08:34, Eric Bollengier via Bacula-devel wrote:
Hello Andrea,
Hello and thanks for answering.
It is quite simple, when we upload a part and if that the "same" part is
already
present, we create a copy to avoid data loss.
Hmm...
This volume was recycled, otherwise it would not be reused, so no
left-over data should be worth anything.
I can't imagine a workflow where "saving" it would be needed, but
probably it's my lack of imagination.
When doing the (re)label process,
the SD should delete the parts already present in the volume.
Are you saying that, when the (cloud) volume is recycled, all the parts
in the S3 bucket should be deleted?
This is not happening.
Should I enable any option for this?
Do I need to issue a truncate command?
It's quite possible that something went wrong during this process
(connection,
permission, bug, etc..).
I would suggest to open an issue at bugs.bacula.org where we can discuss
details.
If the above is correct, I will do.
Only, I'm still on 11.0.6.
Should I try and upgrade to 13, before?
bye & Thanks
av.
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
