Filter
Top Products
Conguration Data For Suxes With Multiple
Backends
Conguration data for suxes with multiple backends is not migrated. If dsmig detects that a
sux has more than one backend, it does not migrate any of the conguration entries that
belong to that sux. This includes conguration entries for the mapping tree, replicas,
replication agreements, LDBM instances, indexes, and encrypted attributes. Instead, all of these
entries are dumped in the le new-instance-path/migration/old_distribution_conf.ldif.
You can import the distribution conguration data from this le after migration, if required.
Replication Conguration Data
Conguration 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 le
new-instance-path/migration/old_replication_conf.ldif. You can import the replication
conguration data from this le after migration, if required.
Conguration Data for o=netscapeRoot
Conguration data for the o=NetscapeRoot sux is not migrated by default. If this information
is required, use the -N to migrate the conguration data. If you do not use the -N option, the data
is dumped in the le new-instance-path/migration/old_netscape_conf.ldif. You can
import the conguration data from this le after migration, if required.
Conguration Attributes Not Migrated by dsmig
The following common conguration attributes are not migrated automatically.
This is not an exhaustive list. You might have used additional conguration attributes that must
be migrated manually.
ds-hdsml-dsmlschemalocation
ds-hdsml-soapschemalocation
dsKeyedPassword
dsMappedDN
dsMatching-pattern
dsMatching-regexp
dsSaslPluginsEnable
dsSaslPluginsEnable
dsSaslPluginsPath
dsSearchBaseDN
dsSearchFilter
Usingdsmigto MigrateCongurationData
Chapter2 • AutomatedMigration Usingthe dsmigCommand 33
SunCondential:Registered