Hi EricinIT,
Thanks for sharing the cases and sorry to hear about the challenges.
I would advise continue with Support and request a root cause analysis on the errors -- the need for the rescan happens when there is an inconsistency between the Backup Server's understanding of the state of the backups on Capacity Tier and what is found when actually checking Capacity Tier -- the check is done to ensure backup integrity and to avoid creating inconsistent states.
However, there can be quite a few reasons why this might happen, typically related to connectivity to the S3 provider and / or issues on the S3 provider side, and this will require a review of the debug logs to understand, which Support can help with.
From experience, I've seen this happen a lot when the S3 target handles situations like deletes or API limits in a non-ideal way (returning incorrect information to the S3 client (Veeam in this case), such as a CRUD operation failing that actually succeeded on the S3 side), but as noted before this is very much so contextual.
I see a few of the cases are already with Advanced Support (T2), so please continue working with them and ask for root cause analysis to better understand where and why the issues appeared.
Thanks for sharing the cases and sorry to hear about the challenges.
I would advise continue with Support and request a root cause analysis on the errors -- the need for the rescan happens when there is an inconsistency between the Backup Server's understanding of the state of the backups on Capacity Tier and what is found when actually checking Capacity Tier -- the check is done to ensure backup integrity and to avoid creating inconsistent states.
However, there can be quite a few reasons why this might happen, typically related to connectivity to the S3 provider and / or issues on the S3 provider side, and this will require a review of the debug logs to understand, which Support can help with.
From experience, I've seen this happen a lot when the S3 target handles situations like deletes or API limits in a non-ideal way (returning incorrect information to the S3 client (Veeam in this case), such as a CRUD operation failing that actually succeeded on the S3 side), but as noted before this is very much so contextual.
I see a few of the cases are already with Advanced Support (T2), so please continue working with them and ask for root cause analysis to better understand where and why the issues appeared.
Statistics: Posted by david.domask — Sep 30, 2025 8:11 am
