Administration Server Failover

switch the configuration directory for server2 to its own o=NetscapeRoot database from

server1.

/usr/sbin/register-ds-admin.pl

5.Disable the PTA Plug-in on server2 so that it does not pass bind operations for the administrative users in its o=NetscapeRoot to server1.

See Section 2, “Enabling and Disabling Plug-ins”.

15. Replication with Earlier Releases

This section provides information on how to optimize replication with earlier releases of Directory Server. Directory Server 8.0 can be involved in replication with earlier releases of Directory Server, providing the following conditions are met:

Directory Server 8.0 is a consumer.

The legacy suppliers can be Directory Server 4.0, 4.1, and 4.1x.

The following restrictions apply:

A legacy Directory Server and Directory Server 8.0 cannot update the same replica. However, this version of Directory Server can have different replicas, where one is supplied by a legacy Directory Server and the other is supplied by Directory Server 8.0.

Directory Server 8.0 cannot be a supplier for other replicas.

The main advantage of using Directory Server 8.0 as a consumer of a legacy Directory Server is to ease the migration of a replicated environment. For more information on the steps to follow to migrate a replicated environment, refer to the Directory Server Installation Guide.

To set up legacy replication, do the following:

1.In the Directory Server Console, click the Configuration tab.

2.Select the Replication node, and click the Legacy Consumer Settings tab in the right pane.

3.Check the Enable Legacy Consumer checkbox. This activates the fields in the Authentication box.

4.Specify the supplier bind DN that the legacy supplier server will use to bind to the consumer. Optionally, specify a password at least 8 characters long.

335

Page 355
Image 355
HP UX Red Hat Direry Server Software manual Replication with Earlier Releases, Administration Server Failover