Initializing Consumers
348
Red Hat Directory Server Administrator’s Guide • May 2005
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
ldif2db
script or
ldif2db.pl
script. Both import methods are
described in “Importing from the Command-Line,” on page 153.
If you use the
ldif2db
script, remember to bind using the supplier bind DN
configured on the consumer server.
Filesystem Replica Initialization
If you have a very large database, such as one with several million entries, it can
take an hour or more to initialize a consumer from the Console or even with
manual initialization. To save time, you can use
filesystem replica initialization
.
Directory Server initializes the replica by copying over the database files from the
supplier server to the consumer. This method of initializing consumers is
especially useful in replication over wide-area networks or over networks with
slow or unstable connections.
Instead of sending entries via LDAP to replica servers, filesystem replica
initialization populates the new database on the destination server by “backing
up” the supplier database on one server and “restoring” that database on the
destination server. Since this is done by transferring the files with FTP or NFS
between the two servers at essentially the speed of the network, filesystem replica
initialization avoids rebuilding the consumer database during initialization and
speeds up the initialization process.
NOTE
If you use the
ldif2db.pl
script, the LDIF file import operation
does not require a server restart. For more information on
command-line scripts, see
Red Hat Directory Server Configuration,
Command, and File Reference
.
NOTE
For smaller databases, it is recommended that you still initialize
consumers manually or from the Console.
NOTE
The destination server must have the same architecture and the
same bit size as the supplier server for the initialization to succeed.
For example, Sun Solaris 32-bit to Sun Solaris 32-bit, HP-UX 64-bit
to HP-UX 64-bit.
Summary of Contents for DIRECTORY SERVER 7.1
Page 1: ...Administrator s Guide Red Hat Directory Server Version7 1 May 2005 Updated February 2009 ...
Page 20: ...20 Red Hat Directory Server Administrator s Guide May 2005 Glossary 619 Index 635 ...
Page 22: ...22 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 26: ...26 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 78: ...Maintaining Referential Integrity 78 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 200: ...Assigning Class of Service 200 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 488: ...488 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 528: ...PTA Plug in Syntax Examples 528 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 572: ...572 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 612: ...Examples of LDAP URLs 612 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 634: ...634 Red Hat Directory Server Administrator s Guide May 2005 ...