Red Hat DIRECTORY SERVER 8.0, Руководство администратора

Страница: 303 / 552

Filesystem Replica Initialization
285
Directory Server has the capability to initialize a replica using the database files from the supplier
server. This avoids the need to rebuild the consumer database and can be done at essentially the
speed of the network between the two servers by transferring the files with FTP or NFS, for example.
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
the database on the destination server.
This method of initializing consumers is especially useful in replication over wide-area networks or
over networks with slow or unstable connections.
For smaller databases, Red Hat recommends using manual initialization or initialize consumers 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, Red Hat Enterprise Linux 5
(32-bit) to Red Hat Enterprise Linux 5 (32-bit).
8.10.5.1. Initializing the Consumer Replica from the Backup Files
1. Create a new database on the destination server to match the database from the source server.
Before initializing the consumer from the backup files, be certain that the appropriate database has
been created on the destination server so that the database exists to be restored and initialized.
2. Enable replication on the backend as a dedicated consumer.
3. If there is already a replication agreement to that host and port, then replication should resume
immediately after running the restore script. Otherwise, create the replication agreement on the
source server (or whatever server is the supplier), and select the
Do not initialize consumers at
this time
radio button.
4. Stop the source Directory Server if it is running. For example:
service dirsrv stop slapd-example
5. From the command-line, run the
db2bak
utility, and archive the current directory installation.
/usr/lib/dirsrv/slapd- instance_name /db2bak
In addition, a new backup can be created by hitting the
Back Up Directory Server
button in the
Tasks
tab of the Directory Server Console and then putting the name of the archive directory in
the
Directory:...
field. Alternatively, select any previous back-up to initialize the consumer.
This backup information is recovered in the destination replica.
6. Restart the source Directory Server. For example:
service dirsrv start slapd-example
7. Copy the archived files to a directory on the destination server, such as
archiveDirectory
.