Before you upgrade

Before you upgrade to Tivoli Directory Server 6.3 from a previous version, do the following steps:

1. Be sure that the server you plan to migrate to Tivoli Directory Server 6.3 can be successfully started. (If the server is not a proxy server, be sure that the database is configured.) If the server cannot be started successfully, whether it is a proxy server or a full directory server, the upgrade is not supported.
   Note:
   You must not remove the directory server instance that you want to upgrade. For a full directory server instance, you must not unconfigure the database. If you do either of these, upgrade is not supported.
2. Back up the databases and DB2® settings. See the Administration Guide for your release of Tivoli Directory Server for information about backing up databases using DB2 commands, the dbback or idsdbback command, or the Configuration Tool. Take an offline database backup for each local database on the server. (You can do this step now or after step 3.)
3. Back up the configuration files and schema files by using the migbkup utility.
   Notes:
   1. You can find this utility in one of the following locations:

      For Windows systems:

      If you created a DVD: the \tools subdirectory on the DVD

      If you downloaded a .zip file, the tdsV6.3\tools subdirectory of the directory where you unzipped the file

      For AIX®, Linux, and Solaris systems:

      If you created a DVD: the /tools subdirectory on the DVD

      If you downloaded a .tar file: the tdsV6.3/tools subdirectory of the directory where you untarred the file

   2. If you manually edited the V3.modifiedschema file for the version of Tivoli Directory Server that you are upgrading, be sure that you do not have duplicate object identifiers (OIDs) for objectclasses or attributetypes in the file. If duplicate OIDs exist, they are not all preserved during the upgrade, and only the first OID is migrated. After upgrade is complete, the administration server and the idsslapd server might fail to start. If this occurs, you must manually add the missing attributes or objectclasses to the V3.modifiedschema file before starting the servers.

   Type the following at a command prompt:

   • For Windows systems:

     migbkup.bat instance_home backup_directory 

   • For AIX, Linux, and Solaris systems:

     migbkup instance_home backup_directory

   This utility backs up the server configuration file (ibmslapd.conf) and all standard schema files that are supplied with Tivoli Directory Server from the instance_home\etc directory to a temporary directory, specified by backup_directory.

   The parameter instance_home is the location of the directory server instance (for example, C:\idsslapd-instance_name on a Windows system, or owner_home_directory/idsslapd-instance_name on an AIX, Linux, or Solaris system).

   For example:

   • On a Windows system, to back up files from Tivoli Directory Server 6.2 for directory server instance myinst to a directory named d:\tds62\savefiles, type the following:

     migbkup.bat c:\idsslapd-myinst d:\tds62\savefiles

   The command backs up the following files:

   • ibmslapd.conf
   • V3.ibm.at
   • V3.ibm.oc
   • V3.system.at
   • V3.system.oc
   • V3.user.at
   • V3.user.oc
   • V3.modifiedschema
   • V3.config.at
   • V3.config.oc
   • V3.ldapsyntaxes
   • V3.matchingrules
   • ibmslapdcfg.ksf
   • ibmslapddir.ksf
   • ibmdiradmService.cmd (for Windows only)
   • ibmslapdService.cmd (for Windows only)

   The command also creates the db2info file. This file contains the path to the copy of DB2 that is used by the backed-up directory server. (This information is required by the migration tool to perform DB2 instance and database migration while performing Tivoli Directory Server instance migration.)

4. If you have additional schema files that you used in your previous release, copy them manually to the backup_directory. When you migrate the configuration and schema files during instance creation, these files will not be migrated, but they will be copied to the new directory server instance location for use by the directory server instance.
5. Be sure that the operating system on which you will install Tivoli Directory Server 6.3 is supported. See IBM® Tivoli® Directory Server Version 6.3 System Requirements for information about supported levels. If the operating system is not supported, install a supported version.
6. Use one of the following procedures to upgrade a directory server instance from versions 6.0, 6.1, or 6.2 to Tivoli Directory Server 6.3:
   • If you want to upgrade using the Instance Administration Tool (idsxinst GUI), see Before you install, and then use the information in Migrating an instance to migrate to Tivoli Directory Server 6.3.
   • If you want to upgrade Tivoli Directory Server on an AIX, Linux, or Solaris system using operating system utilities and commands, use the information in Upgrading using the command line and operating system utilities.

[ Top of Page | Previous Page | Next Page ]