viaNetwork failed to find a NIC that matches request

[FSE]

Hello everybody,
two days ago our UPS sent a power surge into our network, shutting down our complete internal infrastructure.

We replaced the faulty machine and went on with our daily tasks. But yesterday, our backup using Backup Exec 12.5 didn't work properly, it just "lost connection" halfway through. We backup six servers on tape, the servers being connected as follows:

1x the media server (backups from harddrive top tape)
1x directly connected via our switch stack
4x media server -> stack -> fiber switch -> remote servers
All of them being Windows Server 2008 R2 servers with absolutely no change in configuration since weeks.

The direct connections didn't lose connection, the others did. First to assume is that the fiber switch got some damage from the power surge, so I replaced it and tested again, doesn't matter, same problem. Then I debugged the test backup job on the media server (using specified NICs and subnets for each job), this is what the log says:

BENGINE:  [02.21.13 09:21:55] [0000]     [7328] 02/21/13 09:21:54 viaNetwork enabled 1
BENGINE:  [02.21.13 09:21:55] [0000]     [7328] 02/21/13 09:21:54 viaNetwork useAny 0
BENGINE:  [02.21.13 09:21:55] [0000]     [7328] 02/21/13 09:21:54 viaNetwork protocol 1
BENGINE:  [02.21.13 09:21:55] [0000]     [7328] 02/21/13 09:21:54 viaNetwork subnet --->192.168.0.0/24<---
BENGINE:  [02.21.13 09:21:55] [0000]     [7328] 02/21/13 09:21:54 viaNetwork MAC --->00-11-25-8E-71-F9<---
BENGINE:  [02.21.13 09:21:55] [0000]     [7328] 02/21/13 09:21:54 viaNetwork failed to find a NIC that matches request

So I changed the setting to automatically choose the appropriate NIC / subnet:

BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork enabled 0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork useAny 0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork protocol 0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork subnet --->192.168.0.0/24<---
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork MAC --->00-11-25-8E-71-F9<---
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork IPv4 Enabled 0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork IPv4 subnetAddress 0.0.0.0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork IPv4 subnetMask 0.0.0.0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork IPv4 autoObtain 0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork IPv4 physical
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork selectedProtocol 0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork InterfaceIndexProtocol 0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork InterfaceIndex 0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork subnet 192.168.0.0
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork PrefixLength 24
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork ipAddr <zero>
BENGINE:  [02.21.13 09:46:50] [0000]     [13392] 02/21/13 09:46:50 viaNetwork FallBackOptions 0xD  Protocol Tunnel NIC

With this setting, the _test_ job runs fine, but the real ones, transferring data don't (german error messages):

Endgültiger Fehler: 0xe00084f8 - Die Netzwerkverbindung mit Backup Exec Remote Agent wurde unterbrochen. Überprüfen Sie, ob ein Netzwerkfehler vorliegt. Endgültige Fehlerkategorie: Ressourcenfehler Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-34040

V-79-57344-65072 - Die Verbindung mit dem Zielsystem ging verloren. Sicherungssatz abgebrochen.
V-79-57344-65072 - Die Verbindung mit dem Zielsystem ging verloren. Sicherungssatz abgebrochen.

It transfers about 10% of the data, then just kills the connection.

I am completely at loss here, did somebody encounter anything like this before?
Appreciating any input I can get!

Thanks in advance,
Lennart

[CraigV]

Hi Lennart,

This could be 1 of many issues. Check the TNs below:

www.symantec.com/business/support/index?page=content&id=TECH71227

http://www.symantec.com/business/support/index?page=content&id=TECH56772

Thanks!

[FSE · Accepted solution]

Hey there,

thanks for your response.
Just wanted to clear things up:
It was a switch-stack related issue. After the power surge the stack booted up completely insane (switched stack members internally, but left the configuration on the "old" member...), I didn't recognise this at first as you can't see it via the diagnostic lights.

I repaired that and over the weekend the backup ran just fine, so it never was a BackupExec related matter.

Thanks again for you support.

Regards,
Lennart