Hello again folks,
I have a very simple question regarding the time is takes to replicate a Schema update.
I have a test domain that consists of 5 DC's restored (and recovered) from my production domain. They are all in the same site and LAN, different domains. I did a /forestprep this morning on the Schema Master, and it took about 2 hours before the Forest was replicated with the changes.
Does that sound about right? Is is likely to increase excessively when done with 52 production DC's? Is there any wait to speed it up? A Repadmin /syncall /APed didn't seem to help.
Schema Upgrade question
- 167 Views
- Last Post 28 January 2016
Hello again folks,
That seems long. It will follow AD replication. Are other AD changes getting replicated quicker or also taking
the same 2 hours? If so, check replication schedules/site links/how often sites replicate (default I think is 180 minutes).
I have a lab with 10 DC’s (4 domains in 1 forest) with 5 sites defined with site links similar to production (15
minute schedule). A schema change takes 30-45 minutes or less to replicate to all DC’s.
In a production forest, the last schema change I made (small one) took about an hour (100+ DC’s, 80+ sites; although
I didn’t check each and every DC – monitoring would have alerted us to replication not occurring).
Check the AD replication if it's working fine as it could be the problem here as well, normally it should not take so much time.
Hope this helps you.
I'll check if other changes take that long. I should have mentioned before that a repadmin /showrepl did state that replication had been delayed because of a Schema change and that that was normal.
Will you please run repadmin /replsummary and check if the result is showing as expected.
All seems good. Sorry for the screenshot, isolated environment.
you can check repadmin /showattr * "cn=schema,cn=configuration,dc=xxx,dc=xxx" /atts:ObjectVersion. Wait to speed it up based on network latency
Rajeev, all DC's are reporting the correct Schema now.
Replication in general seems fine, it was only for the 2 hours immediately after the Schema upgrade that replication was paused while the schema directory partition was being updated. It was the length of that 2 hour period that was worrying.
The lab environment was re-built from backups in a authoritative recovery/DR test scenario, it's quite possible that it didn't go quite to plan, and I'm seeing the fail-out of that now.
Anyway the Schema upgrade went fine, and I would imagine that it's won't take that long in production.
If anyone knows what might have caused it, it would be great to hear still.
What is the replication interval. Since this is lab, there should not be much latency
They're all in one-site, so 15 secs, I believe. VMWare infrastructure, on an isolated VLAN, so zero latency.