Chapter 10. Migrating Directory Server 10 to Directory Server 13

Procedure

1. On the Directory Server 13 host, enable replication, but do not create a replication agreement. For details about enabling replication, see the Configuring and managing replication section in the Red Hat Directory Server 13 documentation.

2. On the Directory Server 10 host, enable replication and create a replication agreement that points to the Directory Server 13 host. For details about enabling replication, see chapter 15 "Managing Replication" in the Red Hat Directory Server 10 Administration Guide.

   Important

   If you used a custom configuration on the Directory Server 10 host, do not replace the dse.ldif configuration file on the Directory Server 13 host with the file from previous versions, because the dse.ldif layout changes between versions. Instead, use the dsconf utility or the web console to add the custom configuration for each parameter and plug-in that you require.

3. Optional: Set up further Directory Server 13 hosts with replication agreements between the Directory Server 13 hosts.
4. Configure your clients to use only the Directory Server 13 hosts.

5. On the Directory Server 10 host, remove the replication agreements that point to the Directory Server 13 host:

   # ldapmodify -D "cn=Directory Manager" -W -x -H ldap://<ds.10.server.example.com>
   dn: cn=<agreement-to-ds-13-server>,cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping
   tree,cn=config
   changetype: delete

6. Uninstall the Directory Server 10 hosts. See the chapter 4.8 "Uninstalling Directory Server" in the Red Hat Directory Server 10 Installation Guide.

Procedure

1. Perform the following steps on the existing Directory Server 10 host:

   1. Stop and disable the dirsrv service:

      # dsctl <ds_10_instance_name> stop
      # systemctl disable dirsrv@<ds_10_instance_name>

   2. Export the backend. For example, to export the userRoot database and store it in the /tmp/userRoot.ldif file, run:

      # db2ldif -Z <ds_10_instance_name> -n userRoot -a /tmp/userRoot.ldif

   3. Copy the following files to the new Directory Server 13 host:

      • The LDIF file userRoot.ldif that you exported in the previous step.
      • The /etc/dirsrv/slapd-<ds_10_instance_name>/schema/99user.ldif file if you use a custom schema.

      • The /etc/dirsrv/slapd-<ds_10_instance_name>/dse.ldif configuration file.

        Important

        Do not replace the dse.ldif configuration file on the Directory Server 13 host with the file from the Directory Server 10 host because the dse.ldif layout changes between versions. Store the dse.ldif file for the reference.

      • If you want to migrate an instance with TLS enabled and reuse the same host name for the Directory Server 13 installation, copy:

        • /etc/dirsrv/slapd-<ds_10_instance_name>/cert8.db
        • /etc/dirsrv/slapd-<ds_10_instance_name>/key3.db
        • /etc/dirsrv/slapd-<ds_10_instance_name>/pin.txt
   4. If you want to use the same host name and IP on the Directory Server 13 host, disconnect the old server from the network.

2. Perform the following steps on the new Directory Server 13 host:

   1. Optional: Configure TLS encryption:

      • If the new installation uses a host name that differs from the Directory Server 10 instance host name, see the Enabling TLS-encrypted connections to Directory Server section in the Red Hat Directory Server Security and access control documentation.

      • If you want to use the same host name as the previous Directory Server 10 installation:

        1. Stop the instance:

           # dsctl <ds_13_instance_name> stop

        2. Remove the Network Security Services (NSS) databases and the password file for Directory Server, if they already exist:

           # rm /etc/dirsrv/slapd-<ds_13_instance_name>/cert*.db /etc/dirsrv/slapd-<ds_13_instance_name>/key*.db /etc/dirsrv/slapd-<ds_13_instance_name>/pin.txt

        3. Move the cert8.db, key3.db, and pin.txt files that you copied from the Directory Server 10 host to the /etc/dirsrv/slapd-<ds_13_instance_name>/ directory.

        4. Set the correct permissions for the NSS databases and the password file:

           # chown dirsrv:root /etc/dirsrv/slapd-<ds_13_instance_name>/cert8.db \
           /etc/dirsrv/slapd-<ds_13_instance_name>/key3.db \
           /etc/dirsrv/slapd-<ds_13_instance_name>/pin.txt
           
           # chmod 600 /etc/dirsrv/slapd-<ds_13_instance_name>/cert8.db \
           /etc/dirsrv/slapd-<ds_13_instance_name>/key3.db \
           /etc/dirsrv/slapd-<ds_13_instance_name>/pin.txt

        5. Start the instance:

           # dsctl <ds_13_instance_name> start

   2. If you used a custom schema, place the 99user.ldif file in the /etc/dirsrv/slapd-<ds_13_instance_name>/schema/ directory, set appropriate permissions, and restart the instance:

      # cp /etc/dirsrv/slapd-<ds_10_instance_name>/schema/99user.ldif /etc/dirsrv/slapd-<ds_13_instance_name>/schema/
      
      # chmod 644 /etc/dirsrv/slapd-<ds_13_instance_name>/schema/99user.ldif
      
      # chown root:root /etc/dirsrv/slapd-<ds_13_instance_name>/schema/99user.ldif
      
      # dsctl <ds_13_instance_name> restart

   3. Place the /tmp/userRoot.ldif file you prepared on the Directory Server 10 host in the /var/lib/dirsrv/slapd-<ds_13_instance_name>/ldif/ directory and set the correct permissions:

      # cp /tmp/userRoot.ldif /etc/dirsrv/slapd-<ds_13_instance_name>/ldif/
      
      # chown dirsrv:dirsrv /var/lib/dirsrv/slapd-<ds_13_instance_name>/ldif/userRoot.ldif

   4. Import the userRoot.ldif file to restore the userRoot backend with all entries:

      # dsconf <ds_13_instance_name> backend import userRoot /var/lib/dirsrv/slapd-<ds_13_instance_name>/ldif/userRoot.ldif

      Note that Directory Server 13 can import LDIF files only from the /var/lib/dirsrv/slapd-<ds_13_instance_name>/ directory.

      Important

      If you used a custom configuration on the Directory Server 10 host, do not replace the dse.ldif configuration file on the Directory Server 12 host with the file from previous versions. Instead, use the dsconf utility or the web console to add the custom configuration manually for each parameter and plug-in that you require.