Installation guide

16 NetIQ eDirectory 8.8 SP8 Installation Guide
1.5.1 Need for Health Checks
In earlier releases of eDirectory, the upgrade did not check the health of the server before proceeding
with the upgrade. If the heath was unstable, the upgrade operation would fail and eDirectory would
be in an inconsistent state. In some cases, you probably could not roll back to the pre-upgrade
settings.
This new health check tool resolves this, letting you to ensure that your server is ready to upgrade.
1.5.2 What Makes a Server Healthy?
The server health check utility performs certain health checks to ensure that the tree is healthy. The
tree is declared healthy when all these health checks are completed successfully.
1.5.3 Performing Health Checks
You can perform server health checks in two ways:
 “With the Upgrade” on page 16
 “As a Standalone Utility” on page 16
NOTE: You need administrative rights to run the health check utility. The minimal right that can be
set to run the utility is the Public right. However, with the Public right some of the NetWare Core
Protocol (NCP) objects and partition information are not available.
With the Upgrade
The health checks are run by default every time you upgrade eDirectory.
Linux
Every time you upgrade, the health checks are run by default before the actual upgrade operation
starts.
To skip the default health checks, you can use the -j option with the
nds-install utility.
Windows
The server health checks happen as part of the installation wizard. You can enable or disable the
health checks when prompted to do so.
As a Standalone Utility
You can run the server health checks as a standalone utility any time you want. The following table
explains the health check utilities.