dsmig

- Migrates a Directory Server Instance

Synopsis

install-path/bin/dsmig 
subcommand [options] [operands]

Description

The dsmig command is the migration command for a single Directory Server instance. Use the dsmig command with any of the subcommands described in this man page.

dsmig migrates a Directory Server 5.1 instance to a Directory Server 11.1.1.5.0 instance.

dsmig must be run from the local machine on which the new instance will be located. If the new instance exists, migration subcommands are carried out on that instance. If the new instance does not exist, dsmig creates the new instance with the parameters specified in the global options.

SUBCOMMANDS

The following subcommands are supported.

dsmig info

Displays information on the status of each migration step.

The format of the subcommand is:

dsmig info NEW_INSTANCE_PATH

dsmig migrate-all

Migrates the old instance to the new instance in a single step. This subcommand essentially combines the functionality of all the other subcommands.

The format of the subcommand is:

dsmig migrate-all [-R] [-N] [-c] [-j] [-e | -Z]
 [-D USER_DN] [-w PWD_FILE] [-v] OLD_INSTANCE_PATH
 NEW_INSTANCE_PATH

dsmig migrate-config

Migrates the configuration from the old instance to the new instance.

The format of the subcommand is:

dsmig migrate-config [-R] [-N] [-c] [-j] [-e | -Z]
 [-D USER_DN] [-w PWD_FILE] [-v] OLD_INSTANCE_PATH
 NEW_INSTANCE_PATH

dsmig migrate-data

Migrates the data from the old instance to the new instance. Migrating the change logs of the old instance is optional. Migration of the NetscapeRoot database must be specified as this database is not migrated by default.

The format of the subcommand is:

dsmig migrate-data [-R] [-N] [-v] OLD_INSTANCE_PATH
 NEW_INSTANCE_PATH

dsmig migrate-schema

Migrates the schema from the old instance to the new instance.

The format of the subcommand is:

dsmig migrate-schema [-v] OLD_INSTANCE_PATH NEW_INSTANCE_PATH

dsmig migrate-security

Migrates the security files from the old instance to the new instance.

The format of the subcommand is:

dsmig migrate-security [-v] OLD_INSTANCE_PATH NEW_INSTANCE_PATH

GLOBAL OPTIONS

The following options are global, and are applicable to all commands and subcommands.

-?

--help

Displays help information for a command or subcommand.

-i

--no-inter

Does not request confirmation before executing the command.

-p PORT

--port PORT

The port used for LDAP traffic. The default LDAP port is 389 or 1389.

-P SSL_PORT

--secure-port SSL_PORT

The port used for secure LDAP traffic. The default secure LDAP port is 636 or 1636.

SUBCOMMAND OPTIONS

The following options are applicable to the subcommands where they are specified.

-c

--accept-cert

Specifies that confirmation should not be requested before accepting non-trusted server certificates.

-D USER_DN

--user-dn USER_DN

Defines the Directory Manager DN. The default is cn=Directory Manager.

-e

--unsecured

Specifies an unsecured connection over LDAP. If this option is not used, a secure LDAP connection using StartTLS is made by default.

-j

--reject-cert

Specifies that confirmation should not be requested before rejecting non-trusted server certificates (for this session only.)

-N

--netscapeRoot

Specifies that data for the “o=netscapeRoot“ suffix must be migrated. If this option is used with the migrate-config subcommand, it refers to the suffix configuration data. If this option is used with the migrate-data subcommand, it refers to the netscapeRoot database. Using the option with the migrate-all subcommand means that neither the configuration data nor the database is migrated.

-R

--replication

Specifies that replication data should be migrated. If this option is used with the migrate-config subcommand, it refers to replication configuration data. If this option is used with the migrate-data subcommand, it refers to replication changelogs. Using the option with the migrate-all subcommand means that both replication configuration data and changelogs are migrated.

-v

--verbose

Specifies that additional messages are displayed.

-w PWD_FILE

--pwd-file PWD_FILE

The file from which the Directory Manager password should be read. If this option is not specified, the command prompts for the password.

-Z

--secured

Specifies an SSL connection over LDAP.

SUBCOMMAND OPERANDS

The following operands are applicable to the subcommands where they are specified.

-OLD_INSTANCE_PATH

Specifies the path to the 5.x instance.

-NEW_INSTANCE_PATH

Specifies the path to the 7.x instance.

Exit Status

The following exit status values are returned:

0

Successful completion.

non-zero

An error occurred.

Examples

The following examples show how the dsmig command is used.

Example 1 Migrating the schema

$ dsmig migrate-schema -p 6389 -P 6636
  /local/ds52pX/slapd-old_52_instance /local/new_ds_instance/

This command migrates the schema from the old Directory Server instance to the new instance.

In this example, the LDAP port is specified as 6389, and the secure port is specified as 6636. If you do not specify port numbers, the default port numbers 389 and 636 (for root user) or 1389 and 1636 (for not-root user) are used. If you do not specify port numbers and the default port numbers are already being used, the dsmig command aborts.

Example 2 Migrating the configuration

$ dsmig migrate-config -N /local/ds52pX/slapd-old_52_instance 
 /local/new_ds_instance/

This command migrates the configuration from the old Directory Server instance to the new instance.

In this example, configuration data for the “o=netscapeRoot“ suffix and replication configuration data are migrated.

Example 3 Migrating the data

$ dsmig migrate-data -R -N /local/ds52pX/slapd-old_52_instance 
/local/new_ds_instance/

This command migrates the data from the old Directory Server instance to the new instance.

In this example, the replication change logs are not migrated. The NetscapeRoot database is migrated.

Example 4 Migrating everything in a single step

$ dsmig migrate-all -R -N /local/ds52pX/slapd-old_52_instance 
/local/new_ds_instance/

In this example, replication configuration data is not migrated. Data for the “o=netscapeRoot“ suffix is migrated.

Example 5 Obtaining migration status information

$ dsmig info /local/new_ds_instance/

Old instance path   :  /local/ds52pX/slapd-old_52_instance
New instance path   :  /local/new_ds_instance

Schema Migration    :  Completed
Security Migration  :  Not completed
Config Migration    :  Completed except NetscapeRoot and Replication configuration
Data Migration      :  Not completed

Attributes

See attributes(5) for descriptions of the following attributes:

See Also

dsconf(1M)