Re: Replication to a specific network
- From: "Jill Zoeller [MSFT]" <jillz@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 14 Apr 2006 11:55:19 -0700
Brian, one of our developers has a method you could try:
It's not really possible in a general case, but you can sometimes cheat a
little. This will work if the number of machines that are replicating with
each other is small, and there isn't much other network traffic going
between the machines.
The general idea is to stuff DNS entries into the hosts file and let DFSR
resolve the partner host name in the normal fashion. It will get the IP
from the hosts file and will communicate with the server using the NIC that
has bound that IP. This works best when you have two machines and connect
them with a crossover cable, or you have a private network. Of course, all
network traffic between the machines will probably go through this
interface.
1) On M1.contoso.com, set up a static IP for a dedicated NIC (e.g.
192.168.1.10).
2) On M2.contoso.com, set up a static IP for a dedicated NIC (e.g.
192.168.1.11).
3) Connect a crossed Ethernet cable to both NICs.
4) On M1, create an entry for M2.contoso.com in
%WinDir%\System32\drivers\etc\hosts specifying the 192.168.1.11 IP address.
Note you must use the fully qualified domain name.
5) On M2, create an entry for M1.contoso.com and 192.168.1.10 using the same
procedure.
6) Configure replication between M1 and M2 in the normal fashion.
Replication traffic will go over the private network.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
"Jill Zoeller [MSFT]" <jillz@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OcHyyzkXGHA.1476@xxxxxxxxxxxxxxxxxxxxxxx
We had a similar question in the DFS_FRS newsgroup. Here is Ned Pyle's
original reply:
Unfortunately, there really isn't an easy way to do this through Windows.
You could change the NIC binding order so that it favored one interface
over
another, but that would simply mean most traffic *in general* flowed
through
that network. RPC does not really have a method for becoming 'sticky' with
one NIC simply for one RPCSS interface.
You could have all the various members on separate 'public'
networks/VLAN's,
then have the backdoor network remain the same - that would mean that
these
machines would use the backdoor network to speak to each other in general,
but that would be for all inter-server communication, not just DFSR. Some
backup software is capable of this, but they use custom agents/drivers to
bind to particular NIC's.
I wish I had a better answer for you here. I went back and did a sanity
check with a few other Networking engineers here as well and no one had an
alternate solution.
Ned
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
Want to learn more about Windows Server file and storage technologies?
Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
"BrianH" <BrianH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A4397689-A3CB-4DE1-87B9-1D61993AB592@xxxxxxxxxxxxxxxx
I'm running win03 R2 DFS and replication on 4 servers, 3 std 1 ent. I'd
like
to push and pull on a specific network. My servers are multi homed, with
a
primary client subnet and a backdoor subnet for replication only. When I
generate reports the servers are listed with both networks and when I
monitor
network traffic it seem to use both networks. How can I direct the
replication traffic to the backdoor network only...
Note: r2 DFS is the best solution I've found for replication. thanks
Brian
.
- References:
- Re: Replication to a specific network
- From: Jill Zoeller [MSFT]
- Re: Replication to a specific network
- Prev by Date: Re: Virtual Disk Service Error
- Next by Date: Re: Virtual Disk Service Error
- Previous by thread: Re: Replication to a specific network
- Next by thread: Re: Avoid Audit Deletion of the .tmp Office files
- Index(es):
Relevant Pages
|
