"Todd Spear" <(E-Mail Removed)> wrote in message
news:2342B60A-E521-43B7-BA39-(E-Mail Removed)...
> We have a Windows 2003 R2 server that we want to use primarly for a backup
> server. We are using Veritas 10d. We have an ISCSI SNAP storage
appliance
> connected via a private network 10.88.22.x. The production servers and
the
> backup server conenct to this layer 2 subnet.
There is no such thing as a "Layer2 Subnet".
> traffic appears to run over the production network (10.10.22.x) I would
like
> backups to run over the 10.88.22.x network.
The Servers need two nics with the second Nic using a 10.88.22.x address.
> We then want to access the
> backup server via the production network for RDP, management, etc.
Can't have your cake and eat it too, as the saying goes. If you have a
routed path from the 10.10.22.x to the 10.88.22.x network then all traffic
(including the "SNAP" storage) will run over the 10.10.22.x first till it
gets to the Router, then run from the Router to the Target on the 10.88.22.x
network. This means the above mention servers will do the same thing.
It is possible you can fool with Local Static Routes on the servers to
compensate, but it can get ugly.
The best thing to do is forget the whole thing and just run everything on
the 10.10.22.x network and forget it. As long as you are running a fully
switched network (no Hubs) then all traffic is already "isolated" via the
Logical Circuits (layer2) created by the Switches.
Usually when people try to create strange setups it is because they horribly
underestimate what their existing LAN design can already do on its own.
I have about 100 units on our LAN and am running 100mbps (not gigbit) and am
averaging only about 2% bandwidth usage "network wide".
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com