Howto/Best Practice for 1GB/10GB needed

[nrc]

Hi all,

I think I need some advise for our new infrastructure.
We have a four node HyperV cluster here.
Each node has a 1G connection for management.
On this network card, the settings for a fixed IP (10.x.x.x), Subnet, gateway and DNS are set.
With this card the node appears in the DNS and AD.
The second card is 10G and is used for the VM Switch and therefore has no configuration
The third card is 10G an used for storage and is in a different subnet (172.x.x.x) then the management. Here is only the IP and subnet set. No gateway or DNS, the ‘register DNS’ is off.
(All of the cards are redundant)

Our Veeam server has also a 1G network card with all properties set.
And a second 10G card which is inside the 172.x.x.x net.

For my understanding the Veeam server and the HyperV cluster are talking to each other over the 1G NICs and will agree to use the 10G NIC for the backup.
To make this sure I have set the preferred network for replication and backup to this network.
Now in most of the times the 10G is used for backup.

But the challenge is now, how to backup/replicate our offsite servers.
We have some location overseas which will be backuped/replicated from the central server.
But they don’t have the 172. Network, only the 10. Network.
For this I always get an error ‘RPC is unavailable’ or ‘Proxy server 172.x.. is not reachable’

So is there a best practice to use 10G inside the campus and 1G for the remote locations?

Thanks for any suggestions

Florian

[Egor Yakovlev]

Hi nrc,
Those errors mentioned appear when backup starts or when you are trying to add remote Hyper-V servers to Veeam console using their 10.x addresses?
/Cheers!

[nrc]

Hi,
I can add the remote servers with their 10. address, only the backup or replication failed.

[Egor Yakovlev]

- RPC errors are typically due to firewall locking connection down, likely at your overseas network level \ HV host machine.
- Preferred Network Rules are set for automatic fail over, if condition could not be met, so those cannot be reason of failure.
- You mentioned no DNS on 172. network, so worth checking this KB.
- Last but not least, feel free to open Support Ticket.
/Cheers!