Separate Backup Network (direct) wont work

[GrafPacula]

Hello,
I am currently trying to set up my B+R environment for Hyper-V.
Two Hyper-V hosts with Server 2016 Datacenter

Code: Select all

NODE01
10GBE NIC 192.168.0.x
40GBE NIC 192.168.101.101

Code: Select all

NODE02
10GBE NIC 192.168.0.x1
40GBE NIC 192.168.101.102

Code: Select all

VEEAM Server
10GBE NIC 192.168.0.x2
40GBE NIC 192.168.101.100

I have now created the NODE01 as a Hyper-V standalone via the IP 192.168.101.101 in the B+R.
The repository is on the Veeam server.
The Hyper-V servers and the B+R server are connected directly via 40GBE fiber optics without a switch. The 10GBE network goes via a router, etc.
For replication and backup, I have defined the network 192.168.101.0/24 with 255.255.255.0 in B+R.
When creating a job, it also shows me the VMs. However, when I run the JOB, after Processing...“ the error” Reconnectable protocol device was closed.
If I use the 192.168.0.0 network, it works.
So I only want to run the backups&replications via the direct 40GBE connection. The 10 network should only function as a management network.
What am I doing wrong?
Thanks for your help
Frank

[Andreas Neufert]

Hello GrafPacula,

I guess you use the preferred network setting in Backup & Replication to let Veeam know to use the 40GbE network? If not, you need to set these to let Veeam know what to use.
It is in the Global Settings at the top left menu.

If this is set and you experience still the issue, then let me ask you somethings that is a bit strange.
You said the 40GbE network is attached directly, but you list only 1 IP subnet.
Does that mean you have somehow a dual prot 40GbE card and created some kind of port mirroring so that both ports have the same IP?

If you have direct connections:
Node1-Veeam
Node2-Veeam

You need to place both in separate subnets. Like 192.168.101 and 192.168.102
Then go to the preferred network setting and set a rule for both networks.
Rescan the managed server (the hosts) so that the changes are detected. Go to backup-infrastructure - Managed Server to do so.
Then start the jobs again.

[GrafPacula]

Hello Andreas,

many thanks. Yes i have the network settings set to 192.168.100.0/24.

AND I HAVE FOUND THE CAUSE. I change the Fibercable to another vendor. And so it will work with a great performance and without no problems. The little thinks in life are the heavyest....

Frank

[Andreas Neufert]

Thanks for the follow up. It is great that it works now.