VBR managing multiple locations

[Nas]

Hi. In our environment, we have a central VBR server managing backup and replication jobs for multiple physical locations.

Each location has its own dedicated local hypervisor (running both Hyper-V and VMware), repository, proxy, and mount server. Daily backups, backup copies, and replication jobs run perfectly. Additionally, full VM restores to the same hypervisor are fast since all Veeam components are local to each site.

However, we observe a significant 'hiccup' when using features that require cross-platform conversion or guest OS interaction. We are mainly on Windows environment, we’ve noted the following:

* Instant Recovery to a different hypervisor: The 'Guest OS modifications' step takes much longer via the central VBR. For example, using a local VBR, OS conversion completes within 1 minute; using the central VBR, it exceeds 10 minutes.

* Replication Re-IP: The local VBR completes the re-IP process 10 times faster than the central VBR.

* Disabling Windows Firewall during SureBackup: The local VBR completes this step 20 times faster than the central VBR.

Even though the Mount Server is local, these features seem to require direct, high-latency communication between the central VBR and the local workload.

Is there a way to improve performance for these three features in a centralized VBR architecture?

[david.domask]

Hi Nas,

Yes, some of these operations require use of the Default Mount Server to be performed (link is example with Re-IP)

Are you using a Windows-based backup server or the Software Appliance? With a Windows-based one very likely it's been set as the Default Mount server -- you can try setting the default mount server to a local managed server, it should help here.

[Nas]

Hi David,
I'm using Windows-based backup server. The tests I performed in the previous post is after setting the mount server to a local managed server.

Even with local managed server as mount server, the latency is still significant when using remote VBR compared to local VBR for IVMR/Re-IP/SureBackup operation.

[david.domask]

Hi Nas,

Thanks for the confirmation, but to confirm you set the Default Mount Server, correct?

In short, what is happening likely is that the Backup Server itself is being used for the Re-IP operations -- if I remember correctly Default Mount Server handles this role, so please confirm if the above link is the process you tried.

If it still will not use the correct server, please open a Support Case and let Support review the issue and confirm the behavior.

[Nas]

Hi David,
I am still on VBR12 and cannot find the Default Mount Server option. Is it a new feature in VBR13?

I assume by staying in VBR12, I am stuck with Backup Server itself is being used on any guest OS modification task, unless I upgrade to VBR13? No other workaround at this time.

[david.domask]

Ah, got it. Default Mount Server is a new feature in v13.

On v12 and earlier, Re-IP (and a few other operations) will always use the Backup server as the mount server.

[Nas]

Hi David,

Will setting up preferred networks speed things up when using VBR12 in this situation?

https://blog.workinghardinit.work/2019/ ... ion-speed/

[david.domask]

Hi Nas,

No, not in this case. Preferred networks only applies to data transfer operations (e.g., the actual backup / restore).