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.
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.
Statistics: Posted by Andreas Neufert — Nov 11, 2024 7:56 am
