9 replies
by ed.jaegers
by "doctor"
Use the route command. Setup a persistant route so that when TCP makes a request to this server's IP address (the arcserve server) It will trave a specific route. What you can do is configure the acrserve to be on another subnet altogether. You can then configure those additional NICs to be on that subnet. When you install the second nics, you will have to give the server a second Ip address. You then add a route to
the arcserve box.
Hope this helps.
by ed.jaegers
If the arcserve box had the primary nic with address xxx.xxx.xxx.001 and secndary nic with address yyy.yyy.yyy.001 and the target box had primary nic xxx.xxx.xxx.002 and secondary nic yyy.yyy.yyy.002. Would the route command be:
route add yyy.yyy.yyy.002 yyy.yyy.yyy.001 ?
by ed.jaegers
by kyw
You can add a 2nd nic to all the servers and set it up with a different segment to do backups. The question is why? Do you backup your servers during regular office hours? Do you have to be "there" during backups? Do your company operate at 24x7?
Do you backup more than once a day?
DLT backups can do 20-100mb per minute. 100mb network can do 40MB or more per minute. If you backup your servers at night, less traffic and less open files. Unless you have bandwidth problems during backup, there's no reason to add another nic just for backup purposes.
Processing time will be taken up during backup anyways, how much can a second nic buy you. Instead of spending on a second 100mb segment, I would probably spend it on a good backup strategy.
This does not answer your question directly, but you stated that "I would like to", and I am just asking, "do you really want to".
by ed.jaegers
by vh_s
Let me analyse the situation.
The problem with Client-Server architecture is (at least in Windows) that they are masking the destination with COMPUTERNAME in Windows.
Whenever you use COMPUTERNAME as your target or destination, Windows would resolve this to hardware address. There is no guarantee which NIC would be used in this kind of process.
But to my opinion there is one way to overcome this problem. Add your secondary NIC in each server with different subnet. Instead of using COMPUTERNAME (which Windows would resolve using DHCP or DNS to get its IP address), type your UNC path using the secondary IP address directly.
Server A (master)
primary IP is : xxx.xxx.xxx.01
secondary IP is : yyy.yyy.yyy.01
Server B (client)
primary IP is : xxx.xxx.xxx.02
secondary IP is : yyy.yyy.yyy.02
then you could use this:
NET USE X: \\yyy.yyy.yyy.02\shared_folder
Instead of letting Windows to resolve your computername, you enforce using that secondary route to backup your data.
Hope it help you.
vh_s
by ed.jaegers
by ed.jaegers
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending