Backup Repository in Invalid State - Causes and Troubleshooting Advice

A repository lock in object storage is missing.

A repository lock denotes that an object storage repository is in use by a backup proxy server or a backup proxy pool, and it prevents the same object storage from being added to another backup infrastructure configuration. The lock file is stored in the RepositoryLock directory. For more information, see Object Storage Repository Structure.

When the repository lock is missing, the repository is marked Invalid, and an error similar to the following occurs:

Repository is invalid.: Cannot find expected repository lock in object storage (owner ID: {owner ID}, repository ID: {repository ID}).

Solution: Remove and re-add the object storage.

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 object storage repository from the console.
5. Re-add the object storage entity.
6. Reconfigure the jobs that you modified in Step 3 to use the re-added repository.

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: Accept the updated certificate.

1. In the Backup Infrastructure view, edit the object storage repository that is in the Invalid state.
2. Proceed through the wizard by clicking Next until the updated certificate is presented, and accept it.
3. Complete the wizard to save the object storage repository.

A connection to the object storage repository is missing.

The object storage repository is marked Invalid when Veeam Backup for Microsoft 365 cannot establish a connection to the object storage.

Solution: Isolation testing and firewall check.

1. From the machine where Veeam Backup for Microsoft 365 is installed, test connecting to the object storage using a third-party tool, for example S3 Browser or Azure Storage Explorer. If neither the third-party tool nor Veeam Backup for Microsoft 365 can connect, resolve the underlying connectivity issue.
2. If the third-party tool connects 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 or bucket is missing.

The object storage repository is marked Invalid when the container or bucket that holds its data can no longer be found.

Solution: Verify the container or bucket.

1. Using a storage explorer (S3 Browser or Azure Storage Explorer) or the storage web interface, confirm whether the container or bucket still exists.
2. If the container or bucket is missing, a new bucket or container must be created and a new object storage repository configured.