Setting the environment before you upgrade an instance

You must set up the directory server environment before you upgrade an existing instance.

1. Ensure that the operating system on which the instance for upgrade is present is supported by IBM Security Verify Directory, Version 10.0.1.
2. Ensure that the instance of a previous version that you want to upgrade starts successfully.
   If you want to upgrade a directory server instance, you must configure the database, if it is not already configured.

   Attention: If the server fails to start successfully, upgrade of a proxy server, or a directory server is not supported.
3. Take offline backup of the instance that you want to upgrade.
   For a directory server instance, back up the DB2® databases and DB2 settings. For more information, see the idsdbback command in the Command Reference.
4. To back up the schema and configuration files, run the migbkup command:

   Operating system	Command to run
   Microsoft Windows	migbkup.bat drive_name\idsslapd-instance_name backup_directory
   AIX, Linux	migbkup user_home_dir/idsslapd-instance_name backup_directory

   If you completed the installation of IBM Security Verify Directory, the migbkup command is in sbin folder of the IBM Security Verify Directory installation location. The following directory is the default installation location on various operating systems:

   Microsoft Windows

   C:\Program Files\IBM\ldap\V10.0.1

   AIX

   /opt/IBM/ldap/V10.0.1

   Linux

   /opt/ibm/ldap/V10.0.1

   The migbkup command backs up the following files:

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

   The migbkup command creates the following files:

   • db2info contains the path name and version information of the DB2 that is used by the directory server instance. The idsimigr command or Instance Administration Tool uses this file to upgrade DB2 instance and database when you upgrade a directory server instance. For a proxy server instance, this file is not available.
   • platforminfo contains the information about the operating system and process type.
5. If you manually modified the V3.modifiedschema file of an instance for upgrade, the file must not contain any duplicate object identifiers (OIDs) for object classes or attributes.
   If the file contains duplicate OIDs, they are not preserved during the upgrade. If schema files contain duplicate OIDs, the OID in the V3.modifiedschema is preserved. If the schema files do not contain the attributes or object classes, the administration server and the idsslapd process might fail to start. In such situations, you must manually add the missing attributes or object classes to the schema files before you start the servers.
6. If you configured the instance with custom schema files, copy the files manually to the backup directory.
   When you back up schema and configuration files, the migbkup command backs up the custom schema files. However, these schema files might not be used when you upgrade the instance.