The @recycle folder is the network bin on Qnap systems, so all those files has been deleted.
I have two questions:
As Backuping_SERVERNAME_Volumes (2) folder is quite heavy (several TB), I would like a confirmation that I can permanently delete all those files without taking any risks for my backup integrity.
The main .vbk file in Backuping_SERVERNAME_Volumes (1) is several TB heavier than the total amont of my data. I have archived several projects less than seven days ago, so I assume this is the reason why. Is there moments when this is relevant to start again from a clean and new backup (for exemple after deleting a large amount of data several times)? I assume that this is not the case, and that after the retention period, the main .vbk will sheds weight, but i'm quite new to how Veeam works.
FrancoisG wrote:As Backuping_SERVERNAME_Volumes (2) folder is quite heavy (several TB), I would like a confirmation that I can permanently delete all those files without taking any risks for my backup integrity.
Assuming that these files residing in the QNAP recycle bin have nothing to do with the current backup chain as our agent considers these files as deleted (not present), then you can remove these files.
FrancoisG wrote:The main .vbk file in Backuping_SERVERNAME_Volumes (1) is several TB heavier than the total amont of my data. I have archived several projects less than seven days ago, so I assume this is the reason why. Is there moments when this is relevant to start again from a clean and new backup (for exemple after deleting a large amount of data several times)? I assume that this is not the case, and that after the retention period, the main .vbk will sheds weight, but i'm quite new to how Veeam works.
Depending on your job configuration, whether you're running active fulls or not, you might want to enable this option to wipe out the unused blocks from the backup file.