Upgrading the Directory Server

The directory server provides an upgrade mechanism that enables you to move an existing server instance to a later version. However, upgrading from Sun OpenDS Standard Edition 1.0 to Sun OpenDS Standard Edition 2.0 does not enable you to make use of all of the new features provided in the 2.0 release.

The current upgrade mechanism has the following behavior and limitations:

• Custom scripts and files are not preserved in the upgrade process. These scripts and files are moved to the install-dir/history/timestamp directory.

• Any customizations or modifications made to the configuration or to the schema must be migrated manually to the upgraded server instance.

• Database incompatibilities between Sun OpenDS Standard Edition 1.0 and Sun OpenDS Standard Edition 2.0 require that you rebuild all indexes when you export and re-import the data after an upgrade. For information about rebuilding the indexes, see rebuild-index in Sun OpenDS Standard Edition 2.0 Command-Line Usage Guide.

• Upgrading two 1.0 servers that are running on the same host is not supported.

  If two servers are running on the same host, and both servers are upgraded using the upgrade command, the second server is upgraded but fails to start. This is because the upgrade automatically assigns an administration port of 4444 to both servers. If you must migrate two servers running on the same host, start the first server after the upgrade and, using dsconfig, change the administration port to something other than 4444, as follows:

  $ dsconfig -D "cn=directory manager" -w password -n \
    set-administration-connector-prop --set listen-port:5444

  After changing the administration port on the first server, you will be able to start the second server with the default administration port.

• You cannot revert from Sun OpenDS Standard Edition 2.0 to any previous version.

Instead of upgrading, it is preferable to migrate existing server instances manually. If you choose to use the upgrade command, take note of the following steps:

• To move a standalone directory server to the latest version, stop the server, export the data to LDIF, use the upgrade command to change to the latest version, verify your configuration, ensure that the database on the upgraded server is removed, import the data from the exported LDIF, and then restart the server.

• To move an entire replicated topology of servers from 1.0 to 2.0, each server in the topology must be upgraded successively. Because some commands (such as dsreplication) do not work properly in mixed topologies, you must complete the process on all servers in the topology as quickly as possible. After the change, verify that replication is working as expected.