This is an archive version of the document. To get the most up-to-date information, see the current version.

Invalid State

In this article

In Veeam Backup for Microsoft Office 365, a backup repository can be put into an Invalid state in any of the following cases:

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

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

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, as described in Object Storage Repository Structure.

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

If any of the following is true for extended backup repositories:

A connection to object storage is missing.
A container/bucket is missing or has been renamed.
A repository folder is missing or has been renamed.

If the connection to DAS or NFS is missing.

Such an invalid backup repository becomes available after your DAS or NFS storage is online.

Once a repository is put into an Invalid state, restore or backup from/to such a repository is not possible.

Invalid backup repositories can be found in the Backup Infrastructure view under the Backup Repositories > Invalid node.