Sun ONE logo     Previous      Contents      Index      Next     
Sun ONE Meta-Directory 5.1 Installation Guide



Chapter 6   Upgrading to Sun ONE Meta-Directory 5.1

Sun ONE Meta-Directory 5.1 provides a utility that enables you to upgrade to Sun ONE Meta-Directory 5.1. This chapter contains the following sections:

Note: Due to the complexity of the upgrade procedure all of the subsequent sections must be considered before proceeding to execute the upgrade tool itself.

Upgrading to Sun ONE Meta-Directory 5.1

This document describes the usage of the tool to upgrade iPlanet Meta-Directory versions 5.0 and 5.0SP1 (including 5.0SP1 Patch 1 and 5.0SP1 Patch2) to Sun ONE Meta-Directory 5.1. The tool is written in Perl and uses PerLDAP as the Directory Access mechanism. The first section describes the environment settings for the script to run. The next section describes the usage of the tool with different options. It then gives the step by step information for upgrading to 5.1. Finally we describe known issues with the tool.

Preparing for Upgrade

The upgrade tool (upgrade.pl) is shipped along with the Sun ONE Meta-Directory 5.1 software. It is available in the same directory as the setup binary wherever you have untared it or on the CD-ROM itself. You may run the tool from the same location or copy it to another convenient location on the machine where the old Meta-Directory was installed. The tool uses nsPerl 5.005_03 or 5.004_04, and PerLDAP 1.4 which is installed along with iPlanet Directory Server 5.1 and also with Meta-Directory 5.1. If Directory Server and Meta-Directory are installed on the same machine, the paths can be set to nsPerl in the Directory Server installation. However If the directory server is not installed on the same machine, PerLDAP 1.4 must be copied on the machine to run the tool.

PerLDAP Installation

When taking the backup during the process of upgrade, PerLDAP packages must be copied into the existing Meta-Directory installation. These packages can be obtained from the Meta-Directory 5.1 CD. You must do this only during the initial step of the upgrade process. Once Meta-Directory 5.1 is installed, PerLDAP is automatically installed. (Follow the same procedure on both Windows and Solaris, and before doing anything it is advised that you take backup of your servers).

  1. Unzip the Meta-Directory 5.1 binary.

  2. Go to the perldap directory and unzip the perldap14.zip package. This will produce a directory named "lib".

  3. Copy this directory into Meta-Directory <NETSITE_ROOT>: Say yes, when asked if you want to overwrite the existing files.

Setting the Environment when Directory Server and Meta-Directory have not been installed on the same machine

Windows Path

set path=<NETSITE_ROOT>\lib\nsPerl5.004_04\bin;%path%

Solaris Path

On Solaris, when running script you need to give the include path of PerLDAP package directory to nsPerl as an argument. This can be done using the following option:

nsperl -I<NETSITE_ROOT>/lib/nsPerl5.004_04/lib/site <script_using_perldap>

Instead you can alias nsperl to also include the path to this PerLDAP directory (that is, alias nsperl to the above command). The rest of the document assumes this.

For csh:

% setenv PATH <NETSITE_ROOT>/lib/nsPerl5.004_04/bin:$PATH

% setenv LD_LIBRARY_PATH <NETSITE_ROOT>/lib:$LD_LIBRARY_PATH

% alias nsperl "nsperl -I<NETSITE_ROOT>/lib/nsPerl5.004_04/lib/site"

Setting the Environment when Directory Server and Meta-Directory are installed on the same machine

In the case of Directory Server and Meta-Directory servers installed on the same machine, you can also use nsPerl and PerLDAP packages of the Directory Server. This is described below:

Windows Path

set path=<DIR_SERVER_ROOT>\lib\nsPerl5.005_03\bin\MSWin32-x86;%path%

Solaris Path

For csh:

% setenv PATH <DIR_SERVER_ROOT>/lib/nsPerl5.005_03/bin:$PATH

% setenv LD_LIBRARY_PATH <DIR_SERVER_ROOT>/lib:$LD_LIBRARY_PATH

Replace <DIR_SERVER_ROOT> with the actual location where the iPlanet Directory server is installed. Once the above paths are set, you are ready to run the script.

Upgrade usage

The upgrade process involves running the script twice with different options. The first time, the script is run to perform a backup of all the Meta-Directory configuration and the server instances. This is run with -U, which stands for Upgrade. This gets all the Meta-Directory configuration and stores it in LDIF files, and then deletes all the existing configuration.Therefore, once the script is run with this option, Meta-Directory will not run.Then the administrator can go and uninstall the existing Meta-Directory (5.0/5.0SP1) and then re-install Sun ONE Meta-Directory 5.1. The reader should consult the previous chapter, in case of problems with uninstall of older versions.

The script is run again the second time with -R option to recreate all the configuration. This would ensure that original configuration is restored along with the latest fixes and features provided in Sun ONE Meta-Directory 5.1.

Usage :

upgrade.pl -<U|R> [-h <directory server hostname>] -p <port> -D <Directory Manager> -w <password>

Where:

U: Upgrade, R:Restore

For example:

nsperl upgrade.pl -U -h ldap_host -p 389 -D "cn=Directory Manager" -w dmanager

Each of the options are now described below:

U: Upgrade

This option is used the first time the script is run for upgrade. This gets all the existing Meta-Directory configuration and stores in a backup directory in the form of LDIF files. It also copies all the server instances in the file systems to the backup directory. Finally the script deletes all the existing Meta-Directory configuration. (The last step is done to ensure that no old data is left in the directory server). Meta-Directory will not work after running the script with this option. Hence this must be used only when upgrading to Meta-Directory 5.1.

R: Restore

This option is used to recreate the original Meta-Directory configuration that was created in the backup process.

Only one of the above options can be specified, when running the script.

Other options:

h: Host name on which the Directory Server storing the configuration is running; optional, defaults to localhost.

p: Port on which the directory server listens, mandatory, no default

D: The Directory Manager DN. (E.g.: cn=Directory Manager), mandatory.

w: Directory Managers password, mandatory.

Note that a part of Meta-Directory configuration is created by the Configuration Admin and hence during the restore operation, the tool also prompts for the Config admin and password. The next section describes the steps involved in a typical upgrade process.

Note also For a Universal Connector instance, if the configuration files like task.cfg, template.pl etc. are located under the config directory (like $NETSITE_ROOT/utc-CV2/config) of the connector, these files are automatically backed up. However, if they are located anywhere else, the user must manually backup the files and copy them back to exactly the same location after the restore process".

Step by Step Upgrade Example for Solaris

This section describes the steps in a typical upgrade process from an iPlanet Meta-Directory 5.0,5.0SP1,5.0SP1 Patch 1, and 5.0SP1 Patch 2 installation to a Sun ONE Meta-Directory 5.1 installation on a Solaris system.

  1. Login as the userid that was used to install original servers (typically 'root' for Solaris).

  2. Stop all the Meta-Directory Servers like Join-Engine, UTC etc.

  3. Ensure that the configuration Directory Server is running.

  4. Installing perLDAP and setting the environment:

    5. - In the case of Directory Server and Meta-Directory Server installed on the same machine, this step becomes unnecessary as perLDAP can then be obtained from Directory Server and environment variables can be set with respect to DIR_SERVER_ROOT e.g. if you are using "csh" :

    % setenv PATH <DIR_SERVER_ROOT>/lib/nsPerl5.005_03/bin:$PATH

    % setenv LD_LIBRARY_PATH <DIR_SERVER_ROOT>/lib:$LD_LIBRARY_PATH

    However if you decide to install perLDAP from Meta-Directory 5.1 CD, ensure that you set the environment variables appropriately i.e.

    % alias nsperl "nsperl -I<NETSITE_ROOT>/lib/nsPerl5.004_04/lib/site"

    % setenv PATH <NETSITE_ROOT>/lib/nsPerl5.004_04/bin:$PATH

    % setenv LD_LIBRARY_PATH <NETSITE_ROOT>/lib:$LD_LIBRARY_PATH

- In the case of Directory Server and Meta-Directory Server installed on different machines, it is mandatory to install perLDAP.It is also recommended to install perLDAP from Meta-Directory 5.1 CD. Set the environment variables with respect to NETSITE_ROOT. For example:

% alias nsperl "nsperl -I<NETSITE_ROOT>/lib/nsPerl5.004_04/lib/site"

% setenv PATH <NETSITE_ROOT>/lib/nsPerl5.004_04/bin:$PATH

% setenv LD_LIBRARY_PATH <NETSITE_ROOT>/lib:$LD_LIBRARY_PATH

  1. Archive the data by running following command: Move to the directory where your "upgrade.pl" is kept. "upgrade.pl" is provided with Meta-Directory 5.1 CD and will be available from the unzipped installable directory.

    2. nsperl upgrade.pl -U -h <FQDN> -p <iDS-PORT> -D <bind-dn> -w <bind-password>

    where FQDN stands for Fully Qualified Domain Name of the host, where iPlanet Directory Server is installed.

    Running the above script would allow you to modify the backup directory location. Provide a directory where you have write permissions. Press 'Enter' to accept the default location. Default location is provided with respect to the current directory so ensure that you take the backup in a safe location outside the NETSITE_ROOT, which may be deleted once the iPlanet Meta-Directory is uninstalled. The tool backs up all the Meta-Directory configuration in this directory in the form of LDIF files. The archive process detects the servers installed, backs up all configuration data in LDIF files located within the backup directory and also deletes all the existing configuration.

  2. Uninstall existing iPlanet Meta-Directory 5.0. If the Directory Server and iPlanet Meta-Directory are installed on the same server root, make sure that you are selecting only the components related to iPlanet Meta-Directory 5.0 and not selecting any of the Directory Server components to be uninstalled. Go through the uninstallation procedure described in the previous chapter on iPlanet Meta-directory 5.0 uninstallations.

  3. Customers using Netscape or iPlanet Directory 4.x or 5.0 should now upgrade to iPlanet Directory Server 5.1. Details of this procedure can be found in the iPlanet Directory Server 5.1 Installation Guide. However, the following must to be taken care when upgrading the Directory Server:

    1. While installing iPlanet Directory Server 5.1, use the same parameters as in the old Directory Server. This includes the same LDAP port number, Admininistration Domain, Configuration Admin ID, Directory Manager ID.

    2. Having the same port also means that you cannot have both old and the new Directory Server instances running at the same time. Hence stop the old Directory Server instance before installing Directory Server 5.1 and before running the Migration script.

    3. Run the migration script as explained in the Directory Server 5.1 installation Guide about how to migrate/upgrade to iPlanet Directory Server 5.1. Once the Directory Server is upgraded, you may proceed with the Sun ONE Meta-Directory upgrade process below

    4. You may leave the old Directory Server at its original place. However, do not start the old Directory Server or run its uninstall. This would result in permanent loss of configuration and data.

  4. Reset LD_LIBRARY_PATH before starting the installation setup for Sun ONE Meta-Directory 5.1 i.e. remove the change made in step 4.

  5. Follow the instructions mentioned in the Install and Administration guide for installing Sun ONE Meta-Directory 5.1. Make sure that Sun ONE Meta-Directory 5.1 has not been installed in the same server root as Directory Server. Make sure that you select and install at least the same set of components that were installed in the previous installation.

  6. Restore the original configuration by running the script again with -R option i.e.

    1. Set the environment variable LD_LIBRARY_PATH back to the same as explained in the section "Preparing for Upgrade" with the new NETSITE_ROOT ( if you are using nsperl from the iDS then set the LD_LIBRARY_PATH with respect to the DIR_SERVER_ROOT instead of NETSITE_ROOT). Ensure that other environment variables also comply as mentioned in "Preparing for Upgrade" section.

    2. Type the following command:

      3. nsperl upgrade.pl -R -h <FQDN> -p <iDS-PORT> -D <bind-dn> -w <bind-password>

      where FQDN stands for Fully Qualified Domain Name of the host, where iPlanet Directory Server is installed.

    3. Provide the backup directory location as specified in step 5 where you have the write permissions too. The tool creates new configuration files in the backup directory, with each file prefixed with "new_". Hence for a join-engine (join-engine.ldif) new_join-engine.ldif is created. These LDIF files are used to reinstall as the new configuration.

    4. Give the configuration admin Id when prompted or press Enter to accept the default. Also enter the password.

    5. The tool restores the Meta-Directory configuration and all the server instances.

Once the above steps are successfully followed, the upgrade process is complete. To verify a successful upgrade process you should be able to start all server instances from the meta-directory console and flow sample data appropriately.

Example Solaris Upgrade illustration

The following commands illustrate the case where iPlanet Meta-Directory 5.0 was upgraded to Sun ONE Meta-Directory 5.1 on the same Solaris machine assuming Directory Server has already migrated to Directory Server Version 5.1. This also assumes that the old Directory Server and Meta-Directory 5.0 were installed on separate directories. The following default setup is assumed:

  • Directory Server DIR_SERVER_ROOT = /space/uptool/dsins

  • iPlanet Meta-Directory SP1 Patch 2 NETSITE_ROOT = /space/uptool/meta5.0ins

  • Sun ONE Meta-Directory Unzipped Binaries Location= /space/S1MDBinary

  • Sun ONE Meta-Directory NETSITE_ROOT = /space/uptool/meta5.1ins

  • Default library path before upgrade commences. This can be any path e.g. /oracle/OraHome1/lib

    • # telnet tempHostName

    SunOS 5.8

    login: root

    Password:

    # cd /space/uptool/meta5.0ins

    # ./startconsole &

    # cd ../dsins/slapd-tempHostName

    # ./start-slapd

    ## User action: Stop Join Engine, any iPlanet meta-Directory

    ## Servers and UTCs via the console

    # setenv PATH /space/uptool/dsins/lib/nsPerl5.005_03/bin:$PATH

    # echo $LD_LIBRARY_PATH

    /oracle/OraHome1/lib

    # setenv LD_LIBRARY_PATH /space/uptool/dsins/lib:$LD_LIBRARY_PATH

    # echo $LD_LIBRARY_PATH

    /space/uptool/dsins/lib:/oracle/OraHome1/lib

    # cd /space/S1MDBinary

    # nsperl upgrade.pl -U -h tempHostName.tempDomainName -p 4389 -D

    "cn=directory manager" -w dirmanager

    Admin domain : ou=tempDomainName, o=NetscapeRoot

    Backup location to be created [/space/S1MDBinary/meta-config]:

    /space/uptool/meta-config

    # cd /space/uptool/meta5.0ins

    # setenv LD_LIBRARY_PATH /oracle/OraHome1/lib

    # ./uninstall

    # cd ..

    # rm -rf meta5.0ins

    ## User Action: Install Meta-Directory 5.1 in the

    ## directory /space/uptool/meta5.1ins

    # cd /space/S1MDBinary

    # setenv LD_LIBRARY_PATH /space/uptool/dsins/lib:$LD_LIBRARY_PATH

    # nsperl upgrade.pl -R -h tempHostName.tempDomainName -p 4389 -D

    "cn=directory manager" -w dirmanager

    Enter the full path path of the backup directory

    [/space/S1MDBinary/meta-config]: /space/uptool/meta-config

    Configuration Admin Id or DN: [admin]:

    password: admin

    # cd /space/uptool/meta5.1ins

    # ./startconsole &

Step by Step Upgrade Example for Windows

This section describes the steps in a typical upgrade process from an iPlanet Meta-Directory 5.0,5.0SP1,5.0SP1 Patch 1, and 5.0SP1 Patch 2 installation to a Sun ONE Meta-Directory 5.1 installation on Windows OS when Directory Server and Meta-Directory servers are installed on the same machine.

  1. Login as the userid that was used to install original servers (typically 'administrator' for Windows).

  2. Stop all the Meta-Directory Servers like Join-Engine, UTC etc.

  3. Ensure that the configuration Directory Server is running.

  4. Installing perLDAP and setting the environment:

    5. - In the case of Directory Server and Meta-Directory Server installed on the same machine, this step becomes optional as perLDAP can then be obtained from Directory Server and environment variables can be set with respect to DIR_SERVER_ROOT i.e.

    set path=<DIR_SERVER_ROOT>\lib\nsPerl5.005_03\bin\MSWin32-x86;%path%

    However if you still decide to install perLDAP from Meta-Directory 5.1 CD, ensure that you set the environment variables appropriately i.e.

    set path=<NETSITE_ROOT>\lib\nsPerl5.004_04\bin;%path%

    - In the case of Directory Server and Meta-Directory Server installed on different machines, it's must to install perLDAP. It's recommended to install perLDAP from Meta-Directory 5.1 CD. Set the environment variables with respect to NETSITE_ROOT

    set path=<NETSITE_ROOT>\lib\nsPerl5.004_04\bin;%path%

  5. Archive the data. Move to the directory where your "upgrade.pl" is kept."upgrade.pl" is provided with Meta-Directory 5.1 CD and will be available from the unzipped installable directory. Run the following command:

    6. nsperl upgrade.pl -U -h <FQDN> -p <iDS-PORT> -D <bind-dn> -w <bind-password>

    where FQDN stands for Fully Qualified Domain Name of the host, where iPlanet Directory Server is installed.

    Running the above script would require you to provide the backup directory location.Provide a directory where you have write permissions. Press 'Enter' to accept the default location. Default location is provided with respect to the current directory so ensure that you take the backup in a safe location outside the NETSITE_ROOT, which may be deleted once the iPlanet Meta-Directory is uninstalled. The tool backs up all the Meta-Directory configuration in this directory in the form of LDIF files. The archive process detects the servers installed, backs up all configuration data in LDIF files located within the backup directory and also deletes all the existing configuration.

  6. Uninstall existing iPlanet Meta-Directory 5.0. If the Directory Server and iPlanet Meta-Directory are installed on the same server root, make sure that you are selecting only the components related to iPlanet Meta-Directory 5.0 to be uninstalled and not any of the Directory Server components. Go through the uninstallation procedure described in the previous chapter on Meta-directory 5.0 uninstallations. Following is the sequence of components not to be uninstalled i.e. to be deselected:

    7. - Server Core Components

    - Administration Services

    - iPlanet Directory Suite

    - nsperl

    - PerLDAP

  7. Restart the machine once iPlanet Meta-Directory 5.0 uninstallation is done.

  8. Customers using Netscape or iPlanet Directory 4.x or 5.0 should now upgrade to iPlanet Directory Server 5.1. Details of this procedure can be found in the iPlanet Directory Server 5.1 Installation Guide. However, the following must to be taken care when upgrading the Directory Server:

    1. While installing iPlanet Directory Server 5.1, use the same parameters as in the old Directory Server. This includes the same LDAP port number, Admininistration Domain, Configuration Admin ID, Directory Manager ID.

    2. Having the same port also means that you cannot have both old and the new Directory Server instances running at the same time. Hence stop the old Directory Server instance before installing Directory Server 5.1 and before running the Migration script.

    3. Run the migration script as explained in the in the Directory Server installation Guide about migrate/upgrade to iPlanet Directory Server 5.1. Once the Directory Server is upgraded, you may proceed with the Sun ONE Meta-Directory upgrade process below

    4. You may leave the old Directory Server at its original place. However, do not start the old Directory Server or run the old uninstall. This could result in permanent loss of configuration and data.

    5. Disable the NT Services for the old Directory Server instance and Administration Server to make sure that they do not get started whenever the machine is restarted.

  9. Install Sun ONE Meta-Directory 5.1. Follow the instructions mentioned in the Install and Administration guide for installing Sun ONE Meta-Directory 5.1. Make sure that Sun ONE Meta-Directory 5.1 has not been installed in the same server root as Directory Server. Ensure that you select and install at least the same set of components that were installed in the previous installation.

  10. Restore the original configuration :

    1. Run the following command with appropriate arguments:

      2. nsperl upgrade.pl -R -h <FQDN> -p <iDS-PORT> -D <bind-dn> -w <bind-password>

      where FQDN stands for Fully Qualified Domain Name of the host, where iPlanet Directory Server is installed.

    2. Running the above script would require you to provide the backup directory location same as specified in step 5 where you have the write permissions too. The tool creates new configuration files in the backup directory, with each file prefixed with "new_". Hence for a join-engine (join-engine.ldif) new_join-engine.ldif is created. These LDIF files are used to reinstate the old configuration.

    3. Give the configuration admin Id when prompted or press Enter to accept the default. Also enter the password.

    4. The tool restores the Meta-Directory configuration and all the servers instances.

Once the above steps are successfully followed, the upgrade process is complete. To verify a successful upgrade process you should be able to start all server instances from the meta-directory console and flow sample data appropriately.

Example Windows Upgrade Illustration

The following commands illustrate the case where iPlanet Meta-Directory 5.0 SP1 Patch 2 was upgraded to Sun ONE Meta-Directory 5.1 on the same Windows machine assuming Directory Server has already migrated to Directory Server Version 5.1. The following defaults are assumed:

  • Directory Server DIR_SERVER_ROOT = D:\iplanet\Servers

  • iPlanet Meta-Directory 5.0 SP1 Patch 2 NETSITE_ROOT = D:\iplanet\Servers (same as DIR_SERVER_ROOT),

  • Before upgrade this was containing 1 instance of ADC, 2 instances of UTC and the Join-Engine.

  • Sun ONE Meta-Directory Unzipped Binaries Location : D:\S1MDBinary

  • Sun ONE Meta-Directory NETSITE_ROOT = D:\iplanet\S1MD

    • D:\iplanet\Servers>echo %username%

    Administrator

    D:\iplanet\Servers>cd slapd-hostname

    D:\iplanet\Servers\slapd-hostname>start-slapd

    D:\iplanet\Servers\slapd-hostname>net start slapd-hostname

    The requested service has already been started.

    More help is available by typing NET HELPMSG 2182.

    D:\iplanet\Servers\slapd-hostname>set path=D:\iplanet\Servers\lib\nsPerl5.005_03\bin\MSWin32-x86;%path%

    D:\iplanet\Servers\slapd-hostname>echo %path%

    D:\iplanet\Servers\lib\nsPerl5.005_03\bin\MSWin32-x86;D:\iplanet\Servers\lib\nsPerl5.005_03\bin\MSWin32-x86;D:\winserver\Oracle\Ora81\bin;D:\Program Files\Oracle\jre\1.1.7\bin;D:\WINNT\system32;D:\WINNT;D:\WINNT\System32\Wbem;

    D:\iplanet\Servers\slapd-hostname> cd D:\S1MDBinary

    D:\S1MDBinary>nsperl upgrade.pl -U -h hostname.fulldomainname -p 389 -D "cn=directory manager" -w dirmanager

    Admin domain : ou=fulldomainname, o=NetscapeRoot

    Backup location to be created [D:/S1MDBinary/meta-config]: D:\meta-config

    Backing up Meta-Directory configuration... Done.

    Following Meta-Directory servers were found:

    join-engine

    utc-CV2

    adc-CV3

    utc-CV4

    Performing backup for join-engine...1 File(s) copied

    Done.

    Performing backup for utc-CV2...1 File(s) copied

    Done.

    Performing backup for adc-CV3...5 File(s) copied

    Done.

    Performing backup for utc-CV4...1 File(s) copied

    Done.

    Deleting existing Meta-Directory configuration...Done.

    D:\S1MDBinary>echo "iMD5.0SP1P2 should be uninstalled at this point"

    "iMD5.0SP1P2 should be uninstalled at this point"

    D:\S1MDBinary>echo " When uninstall complete Restart the system and that is now..."

    " When uninstall complete Restart the system and that is now..."

    D:\S1MDBinary>echo "Once the system is restarted after iMD5.0SP1P2 uninstallation, install S1MD51 and restart the system once again, which should be done now..."

    "Once the system is restarted after iMD5.0SP1P2 uninstallation, install S1MD51 and restart the system once again, which should be done now..."

    ----------------------------------------------------------------

    D:\S1MDBinary>echo "So now we have S1MD51..."

    "So now we have S1MD51..."

    D:\S1MDBinary>set path=d:\iplanet\Servers\lib\nsPerl5.005_03\bin\MSWin32-x86;%path%

    D:\S1MDBinary>echo %path%

    D:\iplanet\Servers\lib\nsPerl5.005_03\bin\MSWin32-x86;D:\winserver\Oracle\Ora81\bin;D:\Program Files\Oracle\jre\1.1.7\bin;D:\WINNT\system32;D:\WINNT;D:\WINNT\System32\Wbem;

    D:\S1MDBinary>nsperl upgrade.pl -R -h hostname.fulldomainname -p 389 -D "cn=directory manager" -w dirmanager

    Enter the full path path of the backup directory [D:/S1MDBinary/meta-config]: D:\meta-config

    Creating new config ldifs ...Done.

    Configuration Admin Id or DN: [admin]:

    password: admin

    Creating Meta-Directory configuration and the servers instances...

    5 File(s) copied

    Creating Windows NT service for .. adc-CV3

    [SC] CreateService SUCCESS

    1 File(s) copied

    Creating Windows NT service for .. join-engine

    [SC] CreateService SUCCESS

    1 File(s) copied

    Creating Windows NT service for .. utc-CV2

    [SC] CreateService SUCCESS

    1 File(s) copied

    Creating Windows NT service for .. utc-CV4

    [SC] CreateService SUCCESS

    D:\S1MDBinary>cd d:\iplanet\S1MD

    D:\iplanet\S1MD>startconsole

    D:\iplanet\S1MD>

Known Issues

  1. The upgrade tool does not support migrations across platforms.

  2. The upgrade tool does not help in migrating the Meta directory configurations across different directory server installations or one machine to another machine

  3. Customers using Netscape Directory Server 4.x should upgrade to iPlanet Directory Server 5.1.You may leave the old Directory Server at its original place.

  4. During the restore process, new ldifs are created. For any reason, if you have to repeat the restore process, you must sure you delete all the new files created (starting with new_) in the backup directory before starting a new restore.

  5. No server instance in the Meta-Directory can have the View Name starting with new_.

Previous      Contents      Index      Next     
Copyright 2003 Sun Microsystems, Inc. All rights reserved.

Last Updated February 21, 2003