cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec& NIC Teaming

MaximusK
Level 4

VBE ver. 20.6 rev. 1188
OS Windows Server 2016 1607 (14393.3686) + NIC Teaming
good afternoon
I have a problem
I have VBE ver.20.6 rev.1188, Windows Server 2016 1607 (14393.3686) + NIC Teaming (2 network cards, LACP, LoadBalancing - Dynamic). I use the LanTeam to transmit traffic.
The problem is that after a reboot OS, the “Network” settings for the backup job are LOST (values are reset ->use any network- globally and for each task). However, if you simply restart all the VBE services, there is no problem. I assume that when the server is loading, NIC Teaming has not yet completed initialization and the VBE services have already loaded.


After reboot, any task fails
Completed status: Failed
Final error: 0xe0000f02 - The Backup Exec server could not connect to the remote computer. The remote computer may not exist on the selected subnet. Try an alternative network interface, or allow Backup Exec to choose any available network interface.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-3842

Article 100030779 (https://www.veritas.com/support/en_US/article.100030779) does not provide a solution to these problems.
Tell me what can be done in this situation ??

temporarily to exit the situation, I change the network settings in bulk for all tasks .... but this is not the way out of their
situation

 

ice_screenshot_20200528-115252.png

 

ice_screenshot_20200528-115038.png

 

ice_screenshot_20200528-114943.png

 

 

1 ACCEPTED SOLUTION
5 REPLIES 5

pkh
Moderator
Moderator
   VIP    Certified
If I am not mistaken, NIC teaming is not supported by BE

NIC Teaming   

Slow throughput on teamed NIC's  

does VBE 20.6 matter which network to use?

I have no questions about performance

 

ice_screenshot_20200528-124819.png

kf2013
Moderator
Moderator
   VIP   

work before? Do u try to recreate the job?

you are absolutely right Robot Very Happy in this and there was a problem, I will add my answer later when I check in on the production server. maybe someone will need it