i just performed a backup as a test and later i did
duplicacy prune -exclusive -r 1
The revision is removed but in the chunks dir on the storage i still see some empty chunk dirs.
Is this intended? If yes, why?
This Empty folders after prune partially answer my question. “I’d definitely not tinker with the /chunks directory if I were you - if you still have any backup data in the storage, that is.” . But here i do not have any backup data in the storage, it should be “empty” because i pruned the only 1 revision present on it at all.
And also, when i perform the backup again, like if i do it for the first time, i see this before any Uploaded chunk:
Skipped chunk 3 size 1048576, 1024KB/s 00:02:13 0.7% Skipped chunk 4 size 1048576, 2.00MB/s 00:01:06 1.4% Skipped chunk 13 size 1048576, 3.00MB/s 00:00:44 2.2% Skipped chunk 14 size 1048576, 4.00MB/s 00:00:33 2.9%
This was true also for the first time i performed the backup (maybe because a file was in use and it was not possible to backup it?).
From my first backup:
Loaded 0 include/exclude pattern(s) Use 10 uploading threads Skipped chunk 3 size 1048576, 1024KB/s 00:02:16 0.7% Skipped chunk 4 size 1048576, 2.00MB/s 00:01:08 1.4% Failed to open file for reading: open \\?\C:\Users\xxx: The process cannot access the file because it is being used by another process. Skipped chunk 13 size 1048576, 3.00MB/s 00:00:45 2.1% Skipped chunk 14 size 1048576, 4.00MB/s 00:00:34 2.9%
Why these firsts chunks are skipped?
Thanks in advance!