Remove a replication partner in AD Sites and Services
I have a site, say SITEA, in AD Sites and Services that shows NTDS settings that are set to replicate with 3 different DCs, 2 in SITEB, and 1 in SITEC. I want to remove one of the replication partners because it is from a site I don't need it to replicate with.
If I right click on the replication partner and choose Delete it says "Are you sure you want to delete this object", which scares me a little because I've never been faced with this situation before.
So, what is the correct way to remove a replication partner so that the DC in SITEA doesn't try to replicate with the DC in SITEC?
Please be 100% right if you answer cause this DC is in China and I don't feel like flying for 14 hours straight to fix it...so whatever happens I still need to be able to get to this DC. :)
If I right click on the replication partner and choose Delete it says "Are you sure you want to delete this object", which scares me a little because I've never been faced with this situation before.
So, what is the correct way to remove a replication partner so that the DC in SITEA doesn't try to replicate with the DC in SITEC?
Please be 100% right if you answer cause this DC is in China and I don't feel like flying for 14 hours straight to fix it...so whatever happens I still need to be able to get to this DC. :)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jay_Jay70
oh hold up, is this the site that isnt linked anymore at all due to other issues? so its now the standalone?
ASKER
Jay_Jay70, that may be an option to extend the cost out like crazy.
Here's more info in case someone wants to revise/clarify their answer:
SITEA has 1 DC in it - DC01
It shows in NTDS settings that it is set to replicate with 2 DC's in SITEB, and 1 DC in SITEC.
However, SITEB is "headquarters" and is the hub, SITEC is simply a spoke. So SITEA replicating with SITEB should already have the changes from SITEC, since SITEB and SITEC replicate every hour, whereas SITEA and SITEB are set to replicate every 3 hours. Also, SITEA and SITEC aren't "accessible" to each other, network wise, so I simply get errors stating that it cannot reach SITEC's DC.
So based on that, I can simply go into NTDS settings on that site and delete the DC I don't want to replicate with? This will NOT affect that DC I delete, correct? Last thing I want is for it to start having problems simply because I don't want to replicate with it.
Here's more info in case someone wants to revise/clarify their answer:
SITEA has 1 DC in it - DC01
It shows in NTDS settings that it is set to replicate with 2 DC's in SITEB, and 1 DC in SITEC.
However, SITEB is "headquarters" and is the hub, SITEC is simply a spoke. So SITEA replicating with SITEB should already have the changes from SITEC, since SITEB and SITEC replicate every hour, whereas SITEA and SITEB are set to replicate every 3 hours. Also, SITEA and SITEC aren't "accessible" to each other, network wise, so I simply get errors stating that it cannot reach SITEC's DC.
So based on that, I can simply go into NTDS settings on that site and delete the DC I don't want to replicate with? This will NOT affect that DC I delete, correct? Last thing I want is for it to start having problems simply because I don't want to replicate with it.
If i were you, I would create two Physical Site links under your Intersite Transports, one containing site A-B, one containg Site B-C, in your default IP transport link make sure that you dont have all 3 sites in there....
I would kill to have that trial system here, as i beleive that you can simply delete without issues, but i cannot give you a 1000%....let me grab the cavalry for you, ill see if someone more knowledgeable can post :)
James
I would kill to have that trial system here, as i beleive that you can simply delete without issues, but i cannot give you a 1000%....let me grab the cavalry for you, ill see if someone more knowledgeable can post :)
James
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
KCC will add the link as long as there is connectivity, if you delete the replication partner, then right click on the server in question and select check replication topology it will recreate manually if there is a connection
ASKER
Everyone,
Magically, after it finally replicated once, it removed itself...weird...but true.
By the way, I did indeed create a new Site Link originally when I created the DC, I wasn't sure why it threw another site's DC into the replication mix, maybe it was a fluke until that DC had replicated and knew what was going on.
Oh well, everything looks correct now for some reason, maybe the KCC knew to remove it as intended? There is no connectivity between the DC in the site and the DC I didn't want it to sync with so maybe that did it.
Now I need to go back and study up on how ADS&S replication really works....I'm one of those, "But, WHY??" people.
Thanks for all the suggestions and help!
Magically, after it finally replicated once, it removed itself...weird...but true.
By the way, I did indeed create a new Site Link originally when I created the DC, I wasn't sure why it threw another site's DC into the replication mix, maybe it was a fluke until that DC had replicated and knew what was going on.
Oh well, everything looks correct now for some reason, maybe the KCC knew to remove it as intended? There is no connectivity between the DC in the site and the DC I didn't want it to sync with so maybe that did it.
Now I need to go back and study up on how ADS&S replication really works....I'm one of those, "But, WHY??" people.
Thanks for all the suggestions and help!
yah, KCC is pretty efficient once there is no link...
Glad is all well though, cheers
James
Glad is all well though, cheers
James