Forum Discussion

Astickar's avatar
Astickar
Level 0
14 days ago

HyperV backup taking too log NBU 10.5

We are making some test in a 6 nodes HyperV Cluster

In node 6 is running our test machine, but, when the backup starts try every  node in the cluster all the time and the backup process takes too long. At last use the LAB_HYPERV-006 after almost 50 minutes.

In the log we can see the continuous chahnge of node  

10:05:39.453 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[bksrv-001.lab.local] name2:[localhost]
10:05:39.453 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3456] matched as locals NAME1=bksrv-001.lab.local NAME2=localhost
10:05:39.455 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[localhost] name2:[LAB-HYPERV-003]
10:05:39.455 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[LAB-HYPERV-003] name2:[LAB-HYPERV-003]
10:05:39.455 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[LAB-HYPERV-003] name2:[LAB-HYPERV-003]
10:05:39.455 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[localhost] name2:[LAB-HYPERV-003]
10:05:39.455 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[LAB-HYPERV-003] name2:[localhost]
10:10:54.837 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[bksrv-001.lab.local] name2:[localhost]
10:10:54.837 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3456] matched as locals NAME1=bksrv-001.lab.local NAME2=localhost
10:10:54.840 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[localhost] name2:[LAB-HYPERV-002]
10:10:54.840 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[LAB-HYPERV-002] name2:[LAB-HYPERV-002]
10:10:54.840 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[LAB-HYPERV-002] name2:[LAB-HYPERV-002]
10:10:54.840 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[localhost] name2:[LAB-HYPERV-002]
10:10:54.840 [76246.76246] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3321] Comparing name1:[LAB-HYPERV-002] name2:[localhost]

There is a way to prevent this  behaviour ?

Thanks in advance

1 Reply

  • was there any change in your environment recently? Was this policy working fine before ?
    what is the configuration for the policy (Hyper-V tab , client), is it same for all  hyper-v policies ?
    is the name resolution working fine for the mentioned node ?(master<>host<>media)