Is it possible to use multiple VBR servers with a single Veeam Vault?

[i3uln]

Hello,

First, we opened a case to answer the question in the post. (Case #07772213)

Our DR scenario is as follows
1. 2 VBR servers in different regions
2. each VBR server offloads backup files via different Blob Storage
3. if the infrastructure in one region fails (including the VBR server), we import a backup of the failed VBR's Blob Storage from the other region and restore it.

In the above scenarios, we were told that it is not recommended to test restores in different VBR environments.

Therefore, we would like to suggest a better DR scenario to our customers.

For example, using Blob Storage with different VBR servers consolidated into one Blob Storage after consolidating them into a single VBR server.

However, in the above case, the prediction is that the different VBRs will not be able to take ownership properly since they are using 1 Blob Storage.

I have a DR scenario and configuration that looks like the above, but with a slight problem.

So I thought, why not configure 2 VBR servers in different regions to use 1 Veeam Vault to keep backup files and then when the infrastructure fails in the region including 1 VBR, the other VBR server can recover from the backup files offloaded by the failed VBR server?

[KirillChuxlancev]

Hello,

The first scenario you've outlined is perfectly valid. The physical location of the VBR server is not a limiting factor here. Importing backups from Azure Object Storage for restore purposes is a well-supported and common use case. The key point is ensuring that no two VBR servers write to the same container prefix (folder) in the object storage simultaneously. For the case that you outline (i.e. one of the VBR servers is down) it shall not be an issue.

For the second outlined scenario - you're absolutely right that having two VBR servers simultaneously writing to the same Blob Storage repository (or folder path) is not supported and may lead to data corruption or loss. This is exactly what the repository ownership mechanism in Veeam is designed to prevent.

Regarding your final scenario: if both VBR servers are configured to use the same Veeam Vault storage account but two separate prefixes (folders), that configuration is supported. It allows you to isolate backup chains and avoid conflicts. In a DR event, the surviving VBR server can import and restore from the failed VBR’s prefix (folder) as long as it retains access to the storage.

Just keep in mind that even with a shared storage account, manual import of the backups from the failed VBR server will still be necessary. Simultaneous writes to the same path remain unsupported.

Hope this helps!