Re: Slow Replication on DomainDNSZones
- From: Akila <Akila@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 May 2008 05:53:00 -0700
yes.
DomainDNSZones are only on a DC that has DNS Service on it.
all real site and configured fine.
"Herb Martin" wrote:
.
"Akila" <Akila@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D275EA9A-5222-4835-B731-AF1B476A1BA7@xxxxxxxxxxxxxxxx
Problem Description: I have a large Domain in one forest (one Forest & one
Domain) with over 30 DC's and over 20 Sites.
What sort of user and computer populations?
Are these real sites with all DCs properly assigned to the correct site
in AD Sites and Services?
I get a lot of SCOM Alerts of slow replication that are over 45 min which
supposed to be the maximum time by Microsoft if you take in consideration
Maximum 3 hops + 15 min Inter-Site Replication time
Where are you getting 3 hops? 3-4 hops is an INTRASITE number (only)
as far as I know.
And you reduced the INTERsite replication to 15 minutes?
(Nothing necessarily wrong with that, just want to make sure.)
(all my Site-Links are
15min'), BTW - I do have the "Bridge All Site-Links" enabled on the IP
Transport so that should cover the fact that all DC's could communicate
with
each other,
No, that's not the meaning of that item. It means that all Site Links
are TRANSITIVE for INTERsite replication.
I got no Network Limitation, meaning all site are connected with
each other on a MPLS line and no Firewalls what so ever. So All DC's could
be
reached up to 3 Hops .
If you say so, but you would need to describe the ACTUAL
topology as currently established for us to tell, or you to
analyze it.
The SCOM Alerts me some time up to 56 min, mostly on
the DomainDnsZone partition and hardly any or even none on the Domain Data
Partition.
how come I get slow replication on the DNS Partition and not on the Domain
Data Partition , is it not the same replication Topology?
Maybe due to larger number of (dynamice DNS) changes per
replication interval?
Just a guess.
I have to find a solution for the slow Inter-Site Replication for the
DomainDNSZones Partition.
We got few Data center and the rest are small sites, the largest small
site
contains about 600 Users give or take.
some of the sites have more then one DC but most of the smaller sites have
one DC.
all the Sites are connected using the MPLS Cloud method from AT&T meaning
all sites are connected with each other through the cloud.
the only bottle neck is the site's out going WAN line to the cloud ,which
in
away makes it very flexible reconfiguring Site Links.
"Bridge all site links" is enabled meaning every site could communicate
with
each other if needed.
all of my site links are configured for 15 min' replication schedule.
The only thing is I can't understand how come replication is taking over
45
min' if there are no more then 3 hops and the most bizarre thing is that
it
How do you know the "3 hop" thing?
happens only in the DomainDNSZones partition and on on the Domain Data
partition, is it not the same replication topology?
- References:
- Slow Replication on DomainDNSZones
- From: Akila
- Re: Slow Replication on DomainDNSZones
- From: Herb Martin
- Slow Replication on DomainDNSZones
- Prev by Date: Re: Redirecting the users and computers containers in Windows Serv
- Next by Date: Re: Redirecting the users and computers containers in Windows Serv
- Previous by thread: Re: Slow Replication on DomainDNSZones
- Next by thread: Re: Migration To Server 2008(Sta. Adition) from server 2003 (Sta. adit
- Index(es):
Relevant Pages
|
