Offload to Capacity Tier fails with: Scale-out repository rescan is required: performance tier is not synchronized with capacity tier.

KB ID: 4303
Product: Veeam Backup & Replication | 10 | 11
Published: 2022-04-22
Last Modified: 2022-04-25
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Capacity Tier offload job fails with the error:
Error: Local index is not synchronized with object storage, please rescan the scale-out backup repository.
 Local index is not synchronized with object storage

Cause

There is a discrepancy between the information within the Veeam Configuration database and the archive indices.

Solution

How to Rescan the Scale-Out Backup Repository

  1. Disable all jobs that are targeting the Scale-Out Backup Repository
  2. Ensure no Offload tasks are running for the Scale-Out Backup Repository
  3. Configure a Capacity Tier Window to prevent offloads from occurring
    If a custom window is configured, take a screenshot of it before setting Deny to all time periods to make it easier to revert later in the steps.
    1. Edit the Scale-Out Backup Repository
    2. Go to the Capacity Tier tab
    3. Click Window
    4. Highlight all time periods
    5. Select the radio option for Denied
    6. At least one time slot must be selected, so select the time slot that is the furthest away
    7. After saving the Window, click Finish to save the settings for the Scale-Out Backup Repository
Deny Offload
  1. Wait about 3-5 minutes
  2. Rescan the Scale-Out Backup Repository
Rescan SOBR
  1. After the Rescan completes, Enable jobs from Step# 1
  2. Revert the Offload Window changes made in Step 3 above
  3. 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

More information

If, after performing the steps in the Solution section, the issue continues to occur, please do the following:

  1. 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).
  2. Create a Backup of the Veeam Configuration database
  3. Create a Support case and attach the collected logs and database backup to the case.
Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.