Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
JaxIsland7575
Veeam Vanguard
Posts: 385
Liked: 104 times
Joined: Apr 27, 2015 1:59 pm
Full Name: Ryan Jacksland
Location: NY, USA
Contact:

On Host Backups Using Same Host

Post by JaxIsland7575 » Sep 03, 2015 6:50 pm

Confusing title I know, but here is the issue. I spoke to Support about a different issue but asked, If virtual machine manager says the VM is on Host C why does Veeam use Host A as the on host proxy? The response was, Veeam uses whatever host has ownership of that guest vm. So my question is, if its not the host that the VM is on, how do I find this setting? Right now even though my VMs are spread across 3 clustered hosts, they are all using Host A for the backup proxy. I want to make sure that I don't clobber my Host A with all the backups.

Cheers!
VMCE v9

foggy
Veeam Software
Posts: 17827
Liked: 1492 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: On Host Backups Using Same Host

Post by foggy » Sep 04, 2015 9:17 am

Ryan, the CSV owner node (not VM owner node) is always selected as an on-host proxy that performs backup. This is more optimal and allows to avoid excessive load on the cluster network. There should be a registry key that allows to change this behavior, however spreading the load between VM owners you might overload the cluster network.

JaxIsland7575
Veeam Vanguard
Posts: 385
Liked: 104 times
Joined: Apr 27, 2015 1:59 pm
Full Name: Ryan Jacksland
Location: NY, USA
Contact:

Re: On Host Backups Using Same Host

Post by JaxIsland7575 » Sep 04, 2015 12:17 pm

So I should leave it be, and just have them all run through Host A as the proxy? I just want to verify that I am getting the expected behavior. Is there a place to check the ownership?

Cheers!
VMCE v9

foggy
Veeam Software
Posts: 17827
Liked: 1492 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: On Host Backups Using Same Host

Post by foggy » Sep 04, 2015 2:23 pm 1 person likes this post

Yes, the behavior is expected. You can look for the current owner in the Failover Cluster Manager, under Cluster Shared Volumes node.

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests