[13] Backup copy to different site

[Nico L.]

Hi,

we have two data centers with separate VMware and Veeam environments. Our goal is to keep a primary copy of each backup/job on-site and a second copy off-site.

Specifically, we want VBR Server A to store backups from Job A in a repository at Site A, and then either:
- write a secondary copy of the backups to a repository connected to VBR Server B at Site B, or
- copy the entire repository from Site A to a repository at Site B.

Is this setup achievable?

I initially assumed that I could add VBR Server B as a managed server in VBR Server A and then have visibility into the full infrastructure of VBR Server B. Based on that, I expected to be able to select a repository managed by VBR Server B as a secondary target for jobs running on VBR Server A (and vice versa).

Kind regards
Nico

[Mildur]

Hi Nico,

Sharing components is not supported, especially adding a “second backup server” as a managed server to backup server A — doing so will likely break functionality.
Even if you managed to add the server, VBR Server A would have no visibility into Server B’s configuration. Server A would know nothing about Server B configuration.

The recommended approach is to use a single backup server to manage all infrastructure components across both data centers.
Ensure that each data center has its own proxy and repository servers. The backup server should be hosted in the disaster recovery data center.

Best regards,
Fabian

[Nico L.]

Hi Fabian,

this could be a possible solution, but not without high availability. Unfortunately, the current Veeam HA mechanism requires both Veeam servers to be located in the same subnet, which is not feasible in our case, as we need to operate one Veeam server per site.

Our network design does not support stretched Layer-3 subnets across multiple sites and explicitly prohibits such configurations.

From an architectural perspective, it would be highly beneficial in the future to be able to interconnect multiple independent Veeam infrastructures, for example to enable the use of off-site repositories or repository replication across environments. At the moment, the only viable approach to achieve our requirements appears to be a separate Veeam Cloud Connect infrastructure hosted at a third site.

Kind regards,
Nico