General discussion

Locked

configuring a second network

By ed.jaegers ·
I have multiple servers that I currently backup to standalone direct attached SCSI tape drives. Due to capacity concerns, I am considering implementing a DLT tape library. I have checked into running it on a SAN and decided that is solution is to expensive for my installation. I would like to install and configure a second set of 100 mbs nics in each server and direct attach the library to one server, with ArcServe software installed on that unit, and clients on the other units. How do I configure TCP/IP on that unit so that when I attach to the other servers to backup their data, it transfers over the second LAN and not the primary LAN.

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

configuring a second network

by ed.jaegers In reply to configuring a second netw ...

Almost forgot: The units that I want to backup consist of 4 NT4 servers and 2 Win2000 servers running on a NT4 domain. TCP/IP protocol running on switched 100 mbs LAN.

Collapse -

configuring a second network

by "Doctor" In reply to configuring a second netw ...

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.

Collapse -

configuring a second network

by ed.jaegers In reply to configuring a second netw ...

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 ?

Collapse -

configuring a second network

by ed.jaegers In reply to configuring a second netw ...

Point value changed by question poster.

Collapse -

configuring a second network

by kyw In reply to configuring a second netw ...

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".

Collapse -

configuring a second network

by ed.jaegers In reply to configuring a second netw ...

The obvious ideal solution is a SAN, however the high cost is prohibitive. I was looking at the secondary LAN as being a low cost, albeit lower performing replacement. The mb per minute is not the real problem that I have. I used to have 24x7 support from our AS400 operators that would change tapes for me when they were full, I no longer have that and need some type of library. Obviously I can't put a small library in place of each drive, so one shared unit must be used. Two of the server must be continuously available so by putting the traffic on a seperate LAN, I'll avoid collisions and keep the data flowing as fast as possible.

Collapse -

configuring a second network

by vh_s In reply to configuring a second netw ...

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

Collapse -

configuring a second network

by ed.jaegers In reply to configuring a second netw ...

Thanks, this seems to do the trick!

Collapse -

configuring a second network

by ed.jaegers In reply to configuring a second netw ...

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums