Time is changing and also the Hypervisors
... we are planning a migration from VMware to Hyper-V and I have some questions for that.
We are having a Hyper-V Cluster using CSV Datastores for the virtual machines, connected via 10G to dedicated Switches only being used for Storage Network (iSCSI).
We have a physical Veeam Repository server running on Windows Server 2016. This machine is also having a 10G connection to the storage switches using the same subnet as the Cluster.
The Veeam Server is a virtual machine running on the Hyper-V Cluster with no access to the storage network/subnet.
The Hyper-V Cluster, the Veeam Server and the Repository are having a normal network connection for management traffic in a completely different subnet as the storage network/subnet.
Off-Host backup is not an option for us, so we have to use On-Host backup.
At the moment, the repository is added to the Veeam Server via management network, due to the fact that the storage network is not routable and accessible for the Veeam Server.
How can I achieve that the Hyper-V Cluster (the Hosts performing the backup) can connect to the Repository via 10G despite the fact that the Repository is added to the Veeam Server with the 1G management IP?
Network connection between Hyper-V Cluster and Repository using the 10G storage network is working.