Table of Contents
Advertisement
Using dsmig to Migrate Configuration Data
Configuration Data For Suffixes With Multiple
Backends
Configuration data for suffixes with multiple backends is not migrated. If dsmig detects that a
suffix has more than one backend, it does not migrate any of the configuration entries that
belong to that suffix. This includes configuration entries for the mapping tree, replicas,
replication agreements, LDBM instances, indexes, and encrypted attributes. Instead, all of these
entries are dumped in the file new-instance-path/migration/old_distribution_conf.ldif.
You can import the distribution configuration data from this file after migration, if required.
Replication Configuration Data
Configuration data for replication is not migrated by default. If you want this data to be
migrated, select the -R option. By default, the data is dumped in the file
new-instance-path/migration/old_replication_conf.ldif. You can import the replication
configuration data from this file after migration, if required.
Configuration Data for o=netscapeRoot
Configuration data for the o=NetscapeRoot suffix is not migrated by default. If this information
is required, use the -N to migrate the configuration data. If you do not use the -N option, the data
is dumped in the file new-instance-path/migration/old_netscape_conf.ldif. You can
import the configuration data from this file after migration, if required.
Configuration Attributes Not Migrated by dsmig
The following common configuration attributes are not migrated automatically.
This is not an exhaustive list. You might have used additional configuration attributes that must
be migrated manually.
ds-hdsml-dsmlschemalocation
ds-hdsml-soapschemalocation
dsKeyedPassword
dsMappedDN
dsMatching-pattern
dsMatching-regexp
dsSaslPluginsEnable
dsSaslPluginsEnable
dsSaslPluginsPath
dsSearchBaseDN
dsSearchFilter
Chapter 2 • Automated Migration Using the dsmig Command
33
Sun Confidential: Registered
Advertisement
Table of Contents
