Overview#
A Custom Menu Driven Script used for a couple of Clients.Upgrading a Server Already Running a Previous eDirectory Version#
If the server is on at least 8.7.1, the following procedure will work. If a version prior to 8.7.1 is in use, please contact Directory Engineering before continuing.- Make a backup of the DIB on the server to be upgraded (ndsbackup.sh RC).
If this is the first server to be upgraded in the tree, it is recommended that a backup be completed on all servers in the tree prior to completing the first upgrade. (Upgrades generally include schema extensions, and may introduce database structure changes. This will provide a path to reverse these changes if necessary.)!Simple Health Check It is important to know that eDirectory is healthy before the upgrade, so it can be definitively understood if a post-upgrade problem is because of the upgrade, or a pre-existing condition.
Confirm the eDirectory tree is healthy and error-free according to an existing server in the target tree.
Correct any problems before proceeding.
IMPORTANT#
All production and most lab servers configured with ndscheck.sh in CRON to ensure that eDirectory services are running at all times. Before starting continuing this procedure, make sure that the flag is set to tell ndscheck.sh that manual maintenance is in progress. This will prevent unnecessary pages and e-mails, and more importantly, prevent the eDirectory service from starting unintentionally during our change.Tell ndscheck.sh to skip 6 polling cylces (6 is the maximum allowed, which equates to roughly 1 hour):
$ echo 6 > /tmp/nondscheck
Upgrade to eDirectory 8.7.3.##
From the Menu-MainBuildScriptMenu select Menu-BinaryInstallationAndMaintenance; then Menu-ApplyCurrentProductionReleaseFollow the prompts to complete the upgrade.
Answer yes to run Verify Edirectory Config(ModifyInstall) and VerifyFilePermissions(OwnerPermsFix).
Certificate Management#
If it has never been done for this server, complete the steps outlined at Certificate ManagementSimple Health Check#
Confirm the eDirectory tree is healthy and error-free according to an existing server in the target tree.Correct any problems before proceeding.
If the only errors are communication related (e.g. 625), just wait a few minutes and check again.