2.3 Upgrade

2.3.1 Upgrade Fails if the Mount Point Is Set to /var/opt/novell/eDirectory/data

Upgrading eDirectory by using the ndsconfig upgrade command fails, if mount point is set to /var/opt/novell/eDirectory/data.Upgrade halts and the following error message is displayed:

ERROR: Unable to check if the directory "/var/opt/novell/eDirectory/data_upg_bak" already exists. If the directory exists, delete it and execute `ndsconfig upgrade --config-file /etc/nds.conf`to restart the upgrade operation.

The problem arises because during the upgrade, the /var/opt/novell/eDirectory/data directory is renamed to /var/opt/novell/eDirectory/data_upg_bak in order that no customer data is lost. In this case, /var/opt/novell/eDirectory/data directory is the mount point, which cannot be renamed.

To workaround this issue, do either of the following:

  • Change the mount point to /var/opt/novell/eDirectory.

  • Perform the following:

    1. Create /var/opt/novell/eDirectory/data_upg_bak directory.

    2. Move the files from /var/opt/novell/eDirectory/data to /var/opt/novell/eDirectory/data_upg_bak.

      IMPORTANT:Keep the /var/opt/novell/eDirectory/data directory empty to ensure smooth upgrade.

2.3.2 Upgrading eDirectory After Applying a Patch Does Not Remove the Patch Version on a Windows System

When you upgrade eDirectory after applying a patch, the patch version is not upgraded; but, the base version of the product is upgraded.

This issue is observed and reproduced for the following upgrade scenarios:

Table 2-1 eDirectory Versions

Base Product Version

Patch Version

Upgraded Version

eDirectory 873


eDirectory 88 SP3

eDirectory 873

eDirectory 88 SP3

eDirectory 873

eDirectory 873 SP10

eDirectory 88 SP6

any patch

eDirectory 88 SP8

The issue occurs because eDirectory installers and patch installers in Windows are separate. Base product of eDirectory is installed via NIS framework and patches like eDirectory 8.8 SP5 Patch 2 are installed by using Nulsoft Installer Script (NSIS). Because the installers are different, only the base version of the product is upgraded; not the patch installed via NSIS.

To workaround this issue, remove the registry entry of the patch (for example: eDirectory 8.7.3 SP9/eDirectory 8.7.3 SP10/eDirectory 8.8 SP5 patch 2 and eDirectory 8.8 SP5 patch 3) during the upgrade.