Fragensteller
AD Replication zwischen mehrer Standorten

Frage
-
Hallo zusammen,
zuerst einmal der Aufbau unsere Struktur:
HQ: DC1, DC2
Standort A: DC3
Standort b: DC4
Auf allen DCs läuft soweit Windows Server 2008 R2. Von HQ hat man zugriff auf Standort A und B. Die Standort untereinander haben kein Zugriff, sprich Standort A kann nicht auf B zugreif und umgekehrt. Beide Standort haben aber zugriff auf HQ. Seit einige Tage bekommen wir jetzt bei Standort B folgende Fehelrmeldung:
AD Replication Monitoring : The following DCs took more than three times the expected replication time to replicate.
Format: DC, Naming Context, Calculated Replication Time (in minutes)Site name: Standort A
(Intersite, expected replication time is 15 minutes)
Wenn ich im Standort B den Befehl repadmin /showrepl ausführe erhalte ich folgende Meldungen:
Repadmin: running command /showrepl against full DC localhost
Standort B\DC4
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: e3bd5783-78a3-4e49-bfca-92af3a1469f1
DSA invocationID: 3bd9023a-e941-4a50-8a68-0102e61b5dba
==== INBOUND NEIGHBORS ======================================
DC=g-i-m,DC=com
HQ\DC2 via RPC
DSA object GUID: 862e8cc0-aa83-4586-85a3-8cc9b55cd9cb
Last attempt @ 2011-08-16 12:56:01 was successful.
CN=Configuration,DC=g-i-m,DC=com
HQ\DC2 via RPC
DSA object GUID: 862e8cc0-aa83-4586-85a3-8cc9b55cd9cb
Last attempt @ 2011-08-16 12:56:01 was successful.
CN=Schema,CN=Configuration,DC=g-i-m,DC=com
HQ\DC2 via RPC
DSA object GUID: 862e8cc0-aa83-4586-85a3-8cc9b55cd9cb
Last attempt @ 2011-08-16 12:56:01 was successful.
DC=DomainDnsZones,DC=g-i-m,DC=com
HQ\DC2 via RPC
DSA object GUID: 862e8cc0-aa83-4586-85a3-8cc9b55cd9cb
Last attempt @ 2011-08-16 12:56:02 was successful.
DC=ForestDnsZones,DC=g-i-m,DC=com
HQ\DC2 via RPC
DSA object GUID: 862e8cc0-aa83-4586-85a3-8cc9b55cd9cb
Last attempt @ 2011-08-16 12:56:02 was successful.Wenn ich hingegen dann hingegen repadmin /replsum ausführe erhalte ich folgende Meldung:
Replication Summary Start Time: 2011-08-16 14:31:40
Beginning data collection for replication summary, this may take awhile:
.......
Source DSA largest delta fails/total %% error
DC3 01h:36m:04s 0 / 5 0
DC4 01h:36m:04s 0 / 5 0
DC1 06m:05s 0 / 5 0
DC2 01h:35m:39s 0 / 10 0
Destination DSA largest delta fails/total %% error
DC4 01h:35m:41s 0 / 5 0
DC1 11m:32s 0 / 5 0
DC2 01h:36m:27s 0 / 15 0
Experienced the following operational errors trying to retrieve replication information:
58 - DC3Kann mir jemand weiterhelfen?
Alle Antworten
-
Howdie!Am 16.08.2011 14:38, schrieb PatrickFries:> The following DCs took more than three times the expected replication> time to replicate.How's the schedule for inter-site change replication configured? You canfind that in Sites&Services. The script in MOM/SCOM expects it to be 15minutes, you if it is configured differently in Active Directory, you'llhave to re-configure SCOM/MOM to reflect the correct number of minutes.That'll make sure no false alerts arise.From the outputs you've shown, I don't see any errors - it looks okay,replication takes place between the DCs involved (in the commands).Florian
The views and opinions expressed in my postings do NOT necessarily correlate with the ones of my friends, family or my employer. If anyone should be allowed to mark a response as an "answer", it should be the thread creator. No one else. -
Haha,Am 16.08.2011 22:25, schrieb Florian Frommherz:> Howdie!> Am 16.08.2011 14:38, schrieb PatrickFries:> > The following DCs took more than three times the expected replication> > time to replicate.> How's the schedule for inter-site change replication configured? You can> find that in Sites&Services. The script in MOM/SCOM expects it to be 15> minutes, you if it is configured differently in Active Directory, you'll> have to re-configure SCOM/MOM to reflect the correct number of minutes.> That'll make sure no false alerts arise.> From the outputs you've shown, I don't see any errors - it looks okay,> replication takes place between the DCs involved (in the commands).Nochmal auf deutsch: die Logs sehen "okay" aus, Replikation zwischen denDCs aus den Kommandos, die du gezeigt hast, funktionieren.Ich würde überprüfen, wie die inter-site Repliation konfiguriert ist -wenn der Schedule größer als 15 Minuten ist, solltest du das Skript inMOM/SCOM anpassen, sodass es keine "falschen" Alerts herausgibt.Cheers,Florian
The views and opinions expressed in my postings do NOT necessarily correlate with the ones of my friends, family or my employer. If anyone should be allowed to mark a response as an "answer", it should be the thread creator. No one else.