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?
-
Nas
- Enthusiast
- Posts: 59
- Liked: 6 times
- Joined: Oct 02, 2023 3:34 am
- Full Name: Nasreen
- Contact:
Who is online
Users browsing this forum: Baidu [Spider], Bing [Bot] and 228 guests