Offloading to Object Storage Fails With: Backup file version mismatch: scale-out backup repository rescan is required.
Challenge
SOBR Offload task fails with the error:
Error: Backup file version mismatch: scale-out backup repository rescan is required.
![Error: Backup file version mismatch: scale-out backup repository rescan is required.](http://cdn.veeam.com/content/veeam/en/knowledge-base/kb4303/jcr:content/content-parsys/section-main/section-with-background-content/section-sections/section-with-background-content/section_with_backgro_challenge/section-with-background-content/image/file.web.ntfile.png/1error.png)
Cause
There is a discrepancy between the information within the Veeam Backup & Replication configuration database and the metada in the object storage repository.
Solution
How to Rescan the Scale-Out Backup Repository
- Disable all jobs that are targeting the Scale-Out Backup Repository
- Ensure no Offload tasks are running for the Scale-Out Backup Repository
- Configure a Capacity Tier Window to prevent offloads from occurring
If a custom window is configured, take a screenshot of it before setting Denied to all time periods to make it easier to revert later in the steps.
- Edit the Scale-Out Backup Repository
- Go to the Capacity Tier tab
- Click the hyperlinked word after "Offload window:" ( Any time / Restricted )
- In the Time Periods window that appears:
- Click Denied on the right side.
- Highlight all time periods.
- Click Permitted, and select a single time slot 2 hours before now. (This will prevent offload from occurring for the largest amount of time.)
- Click Ok
- Click Finish to save the settings for the Scale-Out Backup Repository.
![Deny Offload](http://cdn.veeam.com/content/veeam/en/knowledge-base/kb4303/jcr:content/content-parsys/section-main/section-with-background-content/section-sections/section-with-background-content/section_with_backgro_solution/section-with-background-content/image_133790877/file.web.ntfile.png/2restrict.png)
- Wait 5 minutes to allow backend tasks to complete.
- Rescan the Scale-Out Backup Repository.
![Rescan SOBR](http://cdn.veeam.com/content/veeam/en/knowledge-base/kb4303/jcr:content/content-parsys/section-main/section-with-background-content/section-sections/section-with-background-content/section_with_backgro_solution/section-with-background-content/image/file.web.ntfile.png/12.1Rescan.png)
- After the Rescan completes, Enable jobs from Step# 1.
- Revert the Offload Window changes made in Step 3 above.
- Force the Tiering Job to start.
Hold Ctrl and right-click the Scale-Out Backup Repository, and select "Run tiering job now"
![Run tiering job](http://cdn.veeam.com/content/veeam/en/knowledge-base/kb4303/jcr:content/content-parsys/section-main/section-with-background-content/section-sections/section-with-background-content/section_with_backgro_solution/section-with-background-content/image_1700996399/file.web.ntfile.png/12.1RunTier.png)
More Information
If, after performing the steps in the Solution section, the issue continues to occur, please do the following:
- Collect a new set of logs for the Offload.
- Use the 3rd option to Export logs by components.
- Select all servers associated with the Offload job, including:
- The Veeam Backup Server
- Gateway Server for the Object Storage
- Gateway Server(s) for SOBR Performance extent(s).
- Create a Backup of the Veeam Configuration database
- Create a Support case and attach the collected logs and database backup to the case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.