Here is a quick description of my setup: Veeam server and Hyper-V hosts are on 10.0.0.0/24 (called the LAN network). A group of Windows VMs are on 10.200.0.0/16 (called the NET1 network), they run their own separate Windows domain and have no connectivity with the 10.0.0.0/24 network.
We need to have application-aware image processing (Exchange in running on those VMs), but there is no connectivity from the Hyper-V hosts (acting as backup proxy) to the NET1 network and I receive an error
- Code: Select all
Unable to subscribe to guest processing components: Failed to connect to guest agent. Errors: 'Cannot connect to the host's administrative share. Host: [10.200.1.25]. Account: [NET1\veeam]. Win32 error:The network path was not found. Code: 53'
What solutions would you implement? I can only think of creating a VM to act as backup proxy, with one NIC on the 10.0.0.0/24 network and one on the 10.200.0.0/16 network, but I would prefer to have the Hyper-V hosts do the proxy, as they are far more powerful, under light load when the backup runs and they would host the VM that acts as proxy anyway.
I can connect a NIC of the Veeam server to the NET1 network, is there a way to have the Hyper-V host act as proxy, but start guest component processing from the Veeam server?
Thanks in advance, Alessandro