Spreading activity among three NICs
New to the forum and this product (BE 2012). I am in the process of setting up multiple backup jobs. My server has four NIC's. I have setup one as an external IP for me to access the server remotely. The other three NIC's are in my DMZ (*.22,*.23,*.24). I was hoping that the Symantec software would pick an available NIC and run with it. Instead all my jobs are running through the *.22 which I am assuming is causing a bottleneck and performance issues because my jobs are really slow.
Have tried going into the agent on the remote server and changing the IP address from *.22 to *.23. I ran trust on the BE Server. I edited the job for that server to use the *.23 NIC and the job immediately fails with a comm error.
I tried to uninstall and re-install the agent and point to *.23 and it still fails saying it can not connect.
I can ping from the remote server *.22, *.23 and *.24. Have to assume I need to do something in Symantec.
The software appears to want to be flexible about using the NIC's. Jobs will allow me to point to any one of the three, it just won't connect to anything other than *.22. Open to any ideas or suggestions.