Table of Contents
Advertisement
Forcing Replication Updates
Exporting a Replica to LDIF
You can convert the replica to LDIF using one of the following three procedures:
When you create a replication agreement by selecting "Create consumer
1.
initialization file" in the Initialize Consumer dialog box of the Replication
Wizard.
From the Directory Server Console, at any time, by right-clicking the
2.
replication agreement under the Replication folder, and choosing "Create LDIF
File" from the pop-up menu.
From the command line, by using the export command as described in
3.
"Exporting to LDIF From the Command Line," on page 149.
Importing the LDIF File to the Consumer Server
You can import the LDIF file which contains the supplier replica contents to the
consumer server by using the import features in the Directory Server Console, or
by using either the
described in "Importing From the Command Line," on page 143.
If you use the
configured on the consumer server.
NOTE
Forcing Replication Updates
When you stop a Directory Server involved in replication for regular maintenance,
when it comes back online, you need to ensure that it gets updated through
replication immediately. In the case of a master in a multi-master environment, the
directory information needs to be updated by the other master in the multi-master
set. In other cases, when a hub supplier or a dedicated consumer is taken offline for
maintenance, when they come back online, they need to be updated by the supplier
server.
312
Netscape Directory Server Administrator's Guide • May 2002
script or
ldif2db
script, remember to bind using the supplier bind DN
ldif2db
If you use the
ldif2db.pl
does not require a server restart. For more information on
command-line scripts see Netscape Directory Server Configuration,
Command, and File Reference.
script. Both import methods are
ldif2db.pl
script the LDIF file import operation
Advertisement
Table of Contents
