Re: Moving ADAM instances between sites

On Aug 20, 5:03 am, "Lee Flight" <l...@xxxxxxxxxxxxxxx> wrote:
Hi

creating a site and then using a siteLink object to control
schedule and cost is the standard way to go. However
I'm confused about what you are trying to achieve...if
you have members of a configuration set in two sites
with no replication scheduled between them then you
have broken the replication model, why do you want
to do that? If you check the ADAM instance event logs
on the servers I would expect to find KCC complaining
about lack of available siteLink for the site etc.,

Thanks
Lee Flight

<compurhyt...@xxxxxxxxx> wrote in message

news:1187365368.317232.311570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



On Aug 17, 8:48 am, "Lee Flight" <l...@xxxxxxxxxxxxxxx> wrote:
Hi

I'm assuming from your post that you removed the second
site from the defaultipsitelink?
To then limit replication you would need to create a siteLink
between the two sites and then create a replication schedule
for that siteLink, does that work for you?

As to what you actually got when you "orphaned" the second
site you would need to run
repadmin /showrepl
against the servers to see what's happening (and review
the ADAM instance event logs on those servers).

Lee Flight

<compurhyt...@xxxxxxxxx> wrote in message

news:1187272368.605696.151570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I'm trying to limit replication to a few instances in my ADAM
configuration set. This is my situation:

1. All my instances were in Default-Site-First-Name to begin with
2. For the instances I was targeting, I created a new site as follows:
a. Created the new "Site" object under "Sites" using ADAM ADSI
Edit
b. Created a "Servers" container under the site
c. Created an "NTDS Site Settings" container under the site
d. Shut off replication under "NTDS Site Settings" using the
"Schedule" menu item
3. Used the "Move" menu item to move the target instances from Default-
Site-First-Name to my new site (under the Servers container)
4. There are no site links that include my new site (My expectation
was that this meant that there would be no replication traffic to or
from the site after the settings took)

But even after 30 minutes or so, there was still outbound TCP 135
traffic (RPC endpoint detector) attributed to ADAM from the machines
where the instances reside.

I guess I have a few questions:

1. Did I go about this the right way? I tried to stick religiously to
the ADAM Administrators Guide
2. Are there any steps that I missed? or
3. Would I potentially still see RPC traffic from the affected
instances, regardless of site topology?

Mike- Hide quoted text -

- Show quoted text -

Yes,

The second site (which is the one I'm trying to limit traffic/
replication to) is not a member of any site link. So are you saying
that if I add a site link between that site and others and set
replication to "unavailable", that I should get my desired result?

If this is the case then yes, this is most certainly doable for me.
As of now (with the site not in the siteList of any site link)
repadmin /showrepl is still showing replication partneships with
instances on other sites (which is undesirable, hence my initial
questions)

Mike

Mike- Hide quoted text -

- Show quoted text -

I'm going with a hub a spoke approach. Basically I want a few central
instances to have siteLinks with all the remote instances. So the
remote instances would not replicate between each other, but rather
with the central instances. So there are no site links between remote
sites, only to the central instances.

My goal is that all replication traffic is routed through the central
instances. But I think I have achieved that. Here's my new problem:

I have created this hub and spoke topology to fit my needs. I have
done the following:

1. I've created all the appropriate subnets
2. I've created sites for my remote and central instances and
associated them with the proper subnets
3. I've made site links that link the remote sites with the central
sites only

Here's the kicker.

When I run repadmin /showrepl on any instance it shows only the
replication partners that I want. But, network traces are showing TCP
135 (RPC) traffic between instances on remote sites which have no
links, and who do not show up on each other's replication partner list
in repadmin /show repl. When I stop my ADAM service the traffic
stops, so it is not another app.

Am I missing something? Here is an example:

1. Site "central" is on subnet 10.1.200.0/24
2. Site "Remote1" is on subnet 10.3.221.0/24 and is a member of only
one site link (linkA) which it shares with "central"
3. Site "Remote2" is on subnet 10.4.220.0/24 and is a member of only
on site link (linkB) which it shares with "central"

So my expectation would be that changes that originate at Remote1
would first replicate to "Central" via linkA and then from "Central"
to "Remote2" via linkB. But in my case instances on Remote1 seems to
me making outgoing TCP 135 requests to instances Remote2, even when
repadmin does not show them as replication partners.

My expectation is that there would be no traffic (RPC or otherwise)
between instances where the site topology did not have a joining
siteLink. Is this assumptin wrong? I think both links are set to the
same cost.

Mike

Mike

.

Relevant Pages

  • Re: Event ID 1566 and 1311 KCC errors
    ... All replication is being done from each remote site ... I know replication is pull-based, ... A Site Link Bridge isn't used for this. ... A Site Link Bridge is a grouping of site links, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Moving ADAM instances between sites
    ... To then limit replication you would need to create a siteLink ... the ADAM instance event logs on those servers). ... replication to) is not a member of any site link. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Questions regarding replication connections
    ... Let me start by saying that if you have 3 different subnets and 3 different sites you should create 1 subnet for each different site, remember you can have multiple subnets assigned to one site, but you CAN'T have more than 1 site assigned to the same subnet. ... Also note that Sites and subnets play a very important role in user authentication, AD replication, File replication, COs, etc... ... The Knowledge Consistency Checker uses site link configuration information to enable and optimize replication traffic by generating a least-cost replication topology. ... have a high-speed connection such as a T1 and a dial-up link in case the T1 ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Forward lookup problem - now having problems with a period
    ... How did you set the replication scopes in the zone's properties in DNS on ... > each DNS server? ... to the remote 10.0.2.3 server, which runs on cable (we are working on ...
    (microsoft.public.windows.server.dns)
  • Re: Advice Needed: Asynchronous Replication/Mirroring to central o
    ... Looking for a SQL Server replication book? ... field offices return data to the central office so some of this "advanced" ... geographically-dispersed remote locations. ...
    (microsoft.public.sqlserver.replication)
Loading