Filter
Top Products
2. Demote the master server to a hub, as described in “Promoting or Demoting Replicas” in
Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide.
3. Migrate the hub server, either using dsmig or the manual migration progress.
4. Promote the hub server to a master, as described in “Promoting or Demoting Replicas” in
Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide. When you
promote the hub, you must assign a replicaID to the new migrated master. This new
replicaID must be dierent to the replicaID of the old server that is being migrated, and
must be unique within the replicated topology.
Manual Reset of Replication Credentials
dsmig does not migrate the password of the default replication manager entry (cn=replication
manager,cn=replication,cn=config). Instead, the replication manager password is deleted.
Therefore, whether you are using manual or automatic migration, you must reset the
replication manager password manually.
To reset the replication manager password, use the following command:
$ dsconf set-server-prop -h host -p port def-repl-manager-pwd-file:lename
In addition, dsmig does not migrate non-default replication manager entries. If a version 5
replica uses an entry other than the default replication manager, and if this entry is under
cn=config, you must add the default replication manager manually. Please refer to the
documentation to add a non-default replication manager entry manually. For information
about adding a non-default replication manager, see “Using a Non-Default Replication
Manager” in Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide.
Problems Related to Tombstone Purging
In some cases, after migrating a replicated topology you might experience problems related to
tombstone purging. In some cases, tombstone entries are not purged when they should be. This
problem can be resolved by re-indexing the objectclass attribute of the corresponding sux.
New Replication Recommendations
Directory Server 6.0 does not limit the number of masters in a multi-master topology. A
fully-meshed, multi-master topology with no hubs or consumers is recommended in most
cases.
NewReplicationRecommendations
Chapter4 • Migrating aReplicatedTopology 53
SunCondential:Registered