Hi HrvojeR, welcome to the forums.
Thank you for the details and for sharing the case number, and sorry to hear about the troubles.
The "Skipped" part during rescan means that a backup was detected, but not processed (added to Veeam/updated in Veeam), and typically a review of the logs is required to understand why, but it's not necessarily indicative of an issue.
Just to confirm, we're talking about image level backups (VMs or physical machines) or backups of File Shares/Object Storage? If it's image level, do you perhaps have left-over VBM files on the repository that do not have corresponding backup files? (VBK/VIB?) The rescan operation looks for VBM files, which are the metadata for the backups, and imports that into Veeam.
As it's Community (Free) edition, support is offered on a "best-effort" basis, so if you do have a license with an active Support contract, please do apply it to your installation and upload logs to the case for Support to review and to change it to a paid support case.
Thank you for the details and for sharing the case number, and sorry to hear about the troubles.
The "Skipped" part during rescan means that a backup was detected, but not processed (added to Veeam/updated in Veeam), and typically a review of the logs is required to understand why, but it's not necessarily indicative of an issue.
Just to confirm, we're talking about image level backups (VMs or physical machines) or backups of File Shares/Object Storage? If it's image level, do you perhaps have left-over VBM files on the repository that do not have corresponding backup files? (VBK/VIB?) The rescan operation looks for VBM files, which are the metadata for the backups, and imports that into Veeam.
As it's Community (Free) edition, support is offered on a "best-effort" basis, so if you do have a license with an active Support contract, please do apply it to your installation and upload logs to the case for Support to review and to change it to a paid support case.
Statistics: Posted by david.domask — Jan 27, 2025 10:58 am
