Backup Failure with specific NIC-Interface

[Gunni75]

Hello,

Now we have a Backup Exec Media-Server with a additional 10Gbit-NIC-Interface.
Both NIC-Interfaces, the old and the new one, are on the same Subnet.
If we configure a backup-job with selecting the new 10G-NIC-Interface, the Backup Job results in a Failure.

Error Message: Can Connect to Agent

But Connection-Pings are succesfull.

Whats wrong?
It is possible to use the second 10Gbit-NIC-Interface on the same subnet for Backup or not ?

regards




 

[CraigV]

Hi,

That 10GbE NIC would have an IP address, so have you pointed your RAWS agent on each remote server to that specific IP address?

Thanks!

[pkh]

If you use the same sub-net then there is no advantage. You are still using the same network as the other NIC. The whole idea is to use a completely separate network for your backups. That said, your problem is probably due to the DNS resolving the server name to the other NIC. Also your remote agents must publishing to the second NIC

[Gunni75]

That 10GbE NIC would have an IP address, so have you pointed your RAWS agent on each remote server to that specific IP address?
 

yes, now the specific IP adress was pointed in RAWS

Now, the Backup process are run succesfully.
But during the backup process Backup Exec is changing the Nic-Interface from 10Gbit to the other NIC-Interface.
Why ?

 

[CraigV]

...it shouldn't be doing that if you have specified that BE run over a specific NIC...can you verify again that this is the case? If the media server's primary LAN IP address still shows on the RAWS agent publishing tab of the remote servers, can you remove this?

Thanks!

[Gunni75]

The primary LAN IP adress isn't exit on the RAWS-Settings.
Only the IP Adress of the 10Gbit LAN Interface is configured.

If i started the backup job, Backup Exec runs over the 10Gbit/s Interface first ( Task-Manager -->Network Monitor).
But in the middle of the backup process he is changing to the primary network interface.

 

[CraigV]

...shouldn't be doing that at all unless 1 of the remote servers was still pointing to the wrong IP address.

Have you got the latest service pack for BE 2012 installed?

Thanks!