Is there a process to clear the VEEAM created recycle bin?

[CatSpirent]

recycle bin cleanup.
I spent some time trying to figure out why a directory had 45 GB of data when the subdirectory only had 5GB.
I finally saw a $RECYCLE.BIN in the VEEAM subdirectory.
I can't figure out how to clean it out.
Are there any special instructions for doing that.

It is on my old VEEAM server that I have used to restore older VEEAM backup files when requested to restore older files than my usual restore points have.
In figuring out how to restore what I wanted it also seems old indexes were also restored. I am hoping it is ok for me to just delete those since they are dated with the date of my restore effort.

[HannesK]

Hello,
can you tell us the full path please? There are several veeam subdirectories.

Thanks,
Hannes

[veremin]

Aren't you talking about insider protection feature by any chance? Thanks!

[CatSpirent]

Location is: G:\VEEAM-Backup-repository\VM scheduled backups\$RECYCLE.BIN

So SERVER1 is my main VEEAM server.
SERVER2 is my old VEEAM server which I have added as a backup respository to SERVER1 pointing to SERVER2's G:\VEEAM-Backup-repository

I had seen the protection feature item you mentioned, but it was associated with cloud connect and this isn't a cloud environment.

Updating to add:
My IT person got back to me.
It seems it is possible that SERVER1 mounted the SERVER2 repository and then Windows created that $RECYCLE.BIN since it was a drive on SERVER1?
So if there are no concerns as far as VEEAM function, I should be able to run this command.

rd /s /q G:\VEEAM-Backup-repository\VM scheduled backups\$Recycle.bin

If SERVER1 ever needs to mount it again, then the OS should just recreate it. Do you agree?
My IT person said that only Windows creates the $RECYCLE.BIN, no other application would do it.

[HannesK]

Hello,
thanks for the explanation. Because I have never seen $RECYCLE.BIN in any of my repositories.

I did not fully understand what is really configured. In general: as long as you don't delete files and folders that belong to Veeam (vbk, vbm, vib etc.), I see no problem.

Best regards,
Hannes