#1 Global Leader in Data Protection & Ransomware Recovery

Backup Repository in Invalid State - Causes and Troubleshooting Advice

KB ID: 4468
Product: Veeam Backup for Microsoft 365 | 7.0
Published: 2023-07-27
Last Modified: 2023-09-11
mailbox
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.

Purpose

This article documents possible causes for a Veeam Backup for Microsoft 365 Backup Repository to be listed as having an Invalid status and provides troubleshooting advice.
Invalid State Example
Note: Clicking on the blue Invalid word in the status column will cause a pop-up to display an error that may help diagnose the issue.

Solution

The sections below list different reasons why Veeam Backup for Microsoft 365 may list a backup repository as having an Invalid state.

The list below is in no particular order. Each possibility must be investigated individually.
If you would like assistance, please open a support case.

Local cache on an extended backup repository is different from that in object storage.

The cache state is verified by comparing timestamps and an identification number of the associated backup and proxy repositories; these values must be identical.

Solution: Force PersistentCache Resync

  1. Edit the Object Storage Repository, and on the "Backup proxy and cache location" step, identify the "Local cache path." where the PersistentCache is stored.
  2. Empty the PersistentCache Folder:
    Note: Make sure no backup jobs or restore sessions are running.
    1. Stop the Veeam Backup Proxy for Microsoft 365 service on the machine where the PersistentCache is stored.
    2. Navigate to the PersistentCache folder and empty it. This will force the repository into the "Out of Sync" state.
    3. Re-start the Veeam Backup Proxy for Microsoft 365 service.
  3. Use the sync option to recreate the cache.

A repository lock in Object Storage is missing.

A repository lock is imposed by the backup proxy server and prevents such locked object storage from being added as an extension to any other backup repository configuration. A lock file is saved to the RepositoryLock directory. For more information, see Object Storage Structure.

Solution: Restart Services if RepositoryLock is missing.

  1. Check if the RepositoryLock file is missing:
    1. Explore the bucket of the Object Storage.
    2. Navigate to the RepositoryLock directory.
  2. If the RepositoryLock is missing:
    1. Make sure no Backup jobs or Restore sessions are running.
    2. Restart the Veeam Backup Proxy for Microsoft 365 service.

A trusted certificate for S3-Compatible object storage has been changed.

Unable to check object storage lock (reason: The object storage server security certificate is not valid. Examine and accept the certificate.)

Solution: Readd Storage to Veeam Backup for Microsoft 365

  1. Create a Temporary Repository, this will be used to unassign the existing jobs from the repository being investigated.
  2. Disable the jobs that are using the backup repository that is in the Invalid state.
  3. Edit those jobs, and reconfigure them to use the temporary repository created in Step 1.
  4. Remove the Backup Repository and remove the Object Storage from the console.
  5. Re-add the Object Storage entity where the correct certificate will be used.
  6. Configure a repository to Offload the data to the re-added Object Storage.
  7. Reconfigure the jobs that you modified in Step 3 to use the re-added repository.

Specific to the Object Storage used to Extended Backup Repositories:

A connection to object storage is missing.

Solution: Isolation Testing and Checking Firewall

  1. Test connecting to the Object Storage using a third-party tool from the machine where Veeam Backup for Microsoft 365 is installed. For example, using S3 Browser or Azure Storage Explorer. If both the third-party tool and Veeam Backup for Microsoft 365 are unable to connect, you'll need to take steps to resolve the connectivity issue.
  2. If the third-party tool is able to connect, but the issue persists for Veeam Backup for Microsoft 365, check the firewall configuration to confirm that the ports used by Veeam Backup for Microsoft 365 have been opened.

 

A container/bucket is missing or has been renamed.

Solution: Create a New Bucket and Repository

  1. First, use an explorer (S3 Browser or Azure Storage Explorer) or the respective web interface to check if the container or bucket exists.
  2. If the bucket or container is missing, you must create a new bucket and configure a new object storage repository.

A repository folder is missing or has been renamed.

Solution: 

  1. Make sure that the folder that contains the PersistentCache exists.
  2. If the folder doesn't exist or is empty, make sure no Backup jobs or Restore sessions are running and restart the Veeam Backup Proxy for Microsoft 365 service.
  3. Then, use the sync option to create the cache.
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.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.