Performing a NetWare 6.5 Down Server Upgrade

  • Document ID:3617668
  • Creation Date:25-Jun-2007
  • Modified Date:26-Apr-2012
    • Micro Focus Products:
      NetWare

Environment

Novell NetWare 6.5

Upgrades to NetWare 6.5 are performed on a running server from the server GUI console or a remote workstation. However, there are times when it might be necessary to perform an upgrade on a downed server. You should only attempt a down-server upgrade if:

  • An in-place or remote upgrade on a running server fails at some point after the Health Check Summary step completes.
  • After the failure, the upgrade cannot be restarted.

Down server upgrades from NetWare 4.2 to NetWare OES have not been tested and therefore are not supported.

Situation

Applying Support Pack to NW 6.5 does not complete.
Upgrade to NW 6.5 does not complete.
Down Server Upgrade

Resolution

To perform a Down Server Upgrade using the NetWare 6.5 SP1 or higher overlay CD: (Please read instructions fully before proceeding)
NOTE: If you are performing this operation to fix a fresh install, please create a directory on C:\ called NWUPDATE. In that directory, create a file called health.log.
This is necessary as the upgrade procedure looks for this document. It does not have to be populated. It simply must exist.
NOTE: Ensure that you know or write down your SERVER ID before performing this operation...SERVERID can be found in the AUTOEXEC.NCF near the top of the file, usually right after the SERVERNAME. If the server was installed IP only it will not have a SERVERID line.

1. If the server is not down, enter DOWN at the server console.
2. Insert the appropriate NetWare 6.5 Overlay (NW65SP2, NW65SP4, etc.), CD 1 (Operating System) in the server's CD drive.
3. Restart the server.
4. When prompted, press any key to interrupt the installation process.
5. Enter P to specify installation parameters.
6. ** MAKE SURE TO USE THE BRACKETS IN THE FOLLOWING COMMAND** Type

[inst: upgrade]

7. Enter I to continue the installation.

In step 6, include the brackets in the command...if you do not, it will perform a regular install and the SYS volume will be recreated and any existing data on SYS will be lost.

8. Select the langauge to install in

9. Accept the license agreement

10. If the command was typed properly in step 6 you should see"Welcome to the NetWare 6.5 Down Server Upgrade"

NOTE: If the down-server upgrade fails to kick off at this point and presents you with either an "ERROR: EXECUTABLE RETURNED CODE 1" or just continues to drop you back to the menu, try burning the ISO image again on a workstation that does not have a virus scanner enabled and burn it at 4x speed.

NOTE: If soon after the upgrade starts it returns Error: "An upgrade must be attempted on a running server before trying to upgrade a server that is in a powered down state" this means the C:\NWUPDATE directory with the file health.log doesn't exist. See instructions above on creating this directory and file.

To perform a Down Server Upgrade using the NetWare 6.5 shipping CD:
NOTE: If you are performing this operation to fix a fresh install, please create a directory on C:\ called NWUPDATE. In thatdirectory, create a file called health.log.
This is necessary as the upgrade procedure looks for this document. It does not have to be populated. It simply must exist.
NOTE: Ensure that you know or write down your SERVER ID before performing this operation...

1. If the server is not down, enter DOWN at the server console.
2. Insert NetWare 6.5 CD 1 (Operating System) in the server's CD drive.
3. Restart the server.
4. Answer the install questions and select "M" for "'M' - Manual Execution of Install.bat"
5. At the DOS prompt enter "install /upgrade" then press enter. The upgrade will begin.


NOTE: For servers with eDirectory 8.8.x - You will need to copy C:\NWSERVER\MASV.NLM, C:\NWSERVER\DSLOADER.NLM, and SYS:\SYSTEM\DSREPAIR.NLM from another server running eDirectory 8.8.x after performing the upgrade to ensure Directory Services loads properly.



Additional Information


Formerly known as TID# 10090315

Change Log

Juston Mortenson: Sept 28, 2009: Added "and the SYS volume will be recreated and any existing data on SYS will be lost." as requested by customer.