The underlying reason this issue occurs is that when a Backup or Backup Copy job needs to update the VBM file, rather than modify the known good VBM, a temporary VBM is written to disk. Then, once the write operation is completed, the old VBM is deleted, and then the new VBM is renamed. When the Recycle Bin feature is enabled on a NAS, it may capture these deleted VBM files in the Recycle Bin (e.g., @recycle or #recycle). When a Repository within Veeam Backup & Replication is configured to use a path that contains the Recycle Bin (even if hidden), the content of that folder will be scanned during a rescan. The rescan operation searches all folders in the Repository path recursively, looking for VBM files. If a VBM file is located in the Recycle Bin, the rescan operation will create a database entry for the found VBM file and an entry within the UI's Backups > Disk (Imported) section.
- An SMB repository configured to use the root of the share (e.g., \\<hostname>\<sharename>\), causing Veeam Backup & Replication to scan the Recycle Bin if enabled in the NAS settings.