Hey toasters....
I have a networking question for you - thought I'd check here first to see if anyone else has this configuration, or if there are any ideas you might have that I could try...
I have a filer (F825) on a small network with a few servers and around 100 client computers. This network is being backed up using Veritas NetBackup v6MP4 running on a Windows 2003 server. It's all connected using 100Mb networking...however, for the filer, the backup server, and a few of the critical servers, I have a Gb 8-port unmanaged switch connecting a second interface on these machines together. This Gb connection is mostly for a particular application, which needs fast access from its servers (Sun Solaris) to the filer. This "private" network has no DNS, no NIS, no services at all - just a fast connection between the filer and some of the servers. I make this work by putting the "private" network addresses of these servers (ie, 192.168.1.x) in their hosts file, and then use "hosts" first in the nsswitch.conf file for the servers and the filer. Seems to work fine for the app - I can confirm that the servers and the filer communicate over the Gb network.
Now, here's where the problem comes in... I decided to try to use this private Gb network for backup, too. NetBackup seems to work fine with the Solaris servers on the private network - I can watch the output of a "netstat -gin 1" on them and verify that the traffic is running over the Gb network, and not the 100 Mb network. However, for the life of me I have not been able to get the filer to do the same thing...using the same command on the filer shows that the backup traffic always runs over the 100Mb network, and not the Gb one. I know the Gb network is up and running on the filer, since ping shows the correct network, and the app mentioned above is using it OK - but I can't seem to get NetBackup and the filer to agree to use the Gb network...
Anyone have any insight or ideas on this (rather strange, admittedly) problem ?
Thanks !
John