Disabling/Enabling ADAM Replication

[Paul Stefancyk]

1. If I have 2 ADAM instances (both belong to same
Configuration Set; one setup as a replica of another at
installation time), is there a way to disable replication
between the 2?

2. Is there a programmatic way to do the above?

3. I then need to be able to enable replication.

TIA,
Paul

[Paul STefancyk]

An equivalent capability is to remove an ADAM instance
from a configuration set. However, reading the ADAM Mgmt
Help file tells me that instances may be added ONLY
during installation of that instance. Is the help file
correct or may instances be added to a config set in
another way?

>.
>

[Paul Stefancyk]

Also, how do I programmatically determine that an ADAM
instance is a replicated partner in a Configuration Set?

TIA,
Paul

>.
>

[Lion Shi]

Hello Paul,

I'd like to clarify the usage of ADAM here. Basically, it provides a data
store and services for accessing the data store, and cannot perform too
much management task. Either, it does not have the infrastructure
capabilities of Active Directory. you may find it from MSDN:

http://msdn.microsoft.com/library/en-us/netdir/adam/what_is_active_directory
_application_mode_.asp

It basically means that we have to enable/disable replication manualy.
Since we cannot add a new instance after installation, you my try
backup/resotre 2 ADAM instances to switch between replica and non-replica.

I hope this helps you.

Best regards,

Lion Shi [MSFT]
MCSE, MCSD
Microsoft Support Engineer
Get Secure! ¨C www.microsoft.com/security

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. 2003 Microsoft Corporation. All rights
reserved.
--------------------
| Content-Class: urn:content-classes:message
| From: "Paul Stefancyk" <Paul_St...@onesource.com>
| Sender: "Paul Stefancyk" <Paul_St...@onesource.com>
| Subject: Disabling/Enabling ADAM Replication
| Date: Thu, 11 Sep 2003 08:37:37 -0700
| Lines: 11
| Message-ID: <0a4201c3787a$a10d1c00$a501...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcN4eqENfbTA57/cTF6VDQGY/U7XVw==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.adsi.general
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.adsi.general:22249
| NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
| X-Tomcat-NG: microsoft.public.adsi.general

[Paul Stefancyk]

Thanks for the reply:

1. How does one manually enable/disable replication?
2. The problem I'm trying to solve is updating ADAM LDAP
schema on a replicated instance. I'll be doing this by
programmatically invoking ldifde.exe to import LDIF
files. However, I need a rollback mechanism in case there
are any errors in the LDIF files. If I'm adding 20 LDAP
attributes and I get a failure after successfully loading
15 of them, I don't want the 15 to be replicated to the
other ADAM replication instances.

I therefore need to isolate the machine in question by
disabling replication, loading LDIF files, re-enabling
replication. If an error occurs in the load, I restore
the original state of the machine, then re-enable
replication.

Thx,
Paul

>.
>

[Max L. Vaughn [MSFT]]

I found some additional information.

After discussing the issue with my peers. We cannot locate a way to completely disble the replication process, however, we did find the following:

First - they should test their schema extension before bringing it into a live environment by making a new partition and extending that schema first.

You can set the delay to be very long prior to making the changes.

the link: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netdir/ad/application_directory_partition_replication.asp

says:

Beginning with Windows Server 2003, domain partitions also use these attributes of the crossRef object to control intra-site replication latency. This is a
change from previous server versions in which the delay intervals were controlled by registry values on each domain controller. When the forest is
upgraded to Windows Server 2003, the existing registry values are preserved only if they have been modified from the default values. The domain
controllers notification intervals in the registry override the notification intervals stored on the partition's crossRef object.
These are the registry keys:
Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Value Name: Repl topology update delay (secs)
Value Type: REG_DWORD
Value Data: number of seconds to wait
Default: 300 (5 minutes)

Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters
Value Name: Repl topology update period (secs)
Value Type: REG_DWORD
Value Data: number of seconds between intervals
Default: 900 (15 minutes)

Sincerely,
Max Vaughn [MS]
Microsoft Developer Support

Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.

[Max L. Vaughn [MSFT]]

Found something else after further investigation.

One can use RepAdmin utility to control replication as well.

repadmin /options [DC] {+|-}DISABLE_INBOUND_REPL {+|-}DISABLE_OUTBOUND_REPL

See repadmin /advhelp for more details.