Upgrading a remote instance of a previous version with Instance Administration Tool

Use Instance Administration Tool to upgrade a remote directory server instance or proxy server instance of a previous supported version to version 6.4.

1. Back up the database of a directory server instance that is on a remote computer with the idsdb2ldif command.
   Important: If you are upgrading a proxy server instance, do not back up database. Proxy server does not contain a database that is associated with it.

   idsdb2ldif -I instance_name -o inst_out.ldif

   For more information about the idsdb2ldif command, see the Command Reference.
2. Complete IBM® Security Directory Server, version 6.4 installation on a computer on which you want to upgrade the remote instance. See, Starting the installation.
3. To back up the schema and configuration files of the remote instance, run the migbkup command of the version 6.4 to which you want to upgrade:

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

   The migbkup command is in the tools subdirectory of the IBM Security Directory Server installation media.
4. Copy the backup directory, backup_directory, which you created with migbkup, from the remote computer to the computer with IBM Security Directory Server, version 6.4.
5. Optional: Copy the database backup file, inst_out.ldif, from the remote computer to the computer with IBM Security Directory Server, version 6.4.
6. Start Instance Administration Tool. See Starting Instance Administration Tool.
7. Click Create an instance.
8. On the Create or migrate panel, complete the following tasks:
   1. Click Migrate from a previous version of directory server.
   2. In the Enter path of the backed up files field, enter the path where you copied the backup of the remote instance configuration and schema files. You can click Browse and specify the backup location.
   3. Click Next.
9. On the Instance details panel of the Create new directory server instance window, specify the following values:
   Note: If you are upgrading an instance, you cannot edit an existing user information.
   1. From the User name list, select the user name that must own the directory server instance.
      The directory server instance is assigned the same name as the user name.
   2. If you want to associate a new user account with the instance, click Create user.
      In the Create new user for directory server instance window, complete the following steps:

      1. In the User Name field, enter the user name.
      2. In the Password field, enter a password for the user account.
      3. In the Confirm password field, enter the password for the user account.
      4. In the Home directory field, enter the home directory to configure for the user account. You can click Browse and specify the home directory.
      5. In the Primary group field, enter the primary group name of the user.
      6. To create the user account, click Create.
10. In the Instance location field, enter the location of the directory server instance. You can click Browse and specify the instance home directory.
    The location must contain at least 30 MB of free disk space.
    On Windows systems, the location is a disk drive, such as C:. The directory instance files are stored in the \idsslapd-instance_name directory on the disk drive you specify. The instance_name variable is the name of the directory server instance.
    On AIX, Linux, and Solaris systems, the home directory of the directory server instance owner is the default instance, but you can specify a different path.
11. Optional: In the Instance description field, a description of the directory server instance.
    The description helps in identifying the instance.
12. Click Next.
13. If you are upgrading a remote directory server instance with the DB2® database details, click Next on the DB2 instance details panel.
    If the backup files are of a remote proxy server instance, the DB2 instance details panel might not be displayed.
14. In the TCP/IP settings for multihomed hosts panel, select one of the following options:
    • If you want the directory server instance to listen on all IP addresses, select Listen on all configured IP addresses.
    • If you want the directory server instance to listen on a particular set of IP addresses that are configured on the computer, clear Listen on all configured IP addresses. Select the IP address or addresses in the list that you want the directory server instance to listen on.
15. Click Next.
16. In the TCP/IP port settings panel, specify the following values:
    Note: You must assign a unique port numbers to the directory server ports and must not conflict with existing ports that are in use on the computer. ON AIX, Linux, and Solaris systems, port numbers in the range of 1 - 1000 can be used only by root.
    1. In the Server port field, enter the port number that you want the server to use as its unsecured port. The number must be in range of 1 - 65535.
    2. In the Server secure port field, enter the port number that you want the server to use as its secured port. The number must be in the range of 1 - 65535.
    3. In the Administration server port field, enter the port number that you want the administration server to use as its unsecured port. The number must be in the range of 1 - 65535.
    4. In the Administration server secure port field, enter the port number that you want the administration server to use as its secured port. The number must be in the range of 1 - 65535.
    5. Click Next.
17. In the Verify settings panel, verify the summary that is generated.
18. To start the directory server instance creation with the backed up configuration and schema files, click Finish.
19. In the Results window, verify the log messages that are generated for the instance creation operations.
20. To close the Results window, click Close.
21. To close Instance Administration Tool, click Close.