Novell is now a part of Micro Focus

Restoring NDPS Without Disrupting Users

Novell Cool Solutions: Trench
By Jason Harris

Digg This - Slashdot This

Posted: 22 Apr 2002

Jason Harris recently had a NetWare 5 SP6A server crash in a multi-server tree. When he restored the server, his NDPS (Novell Distributed Print Services) had stopped working. Below are the steps he used to get everything back on track.

How to Restore NDPS after a Server Crash

The following procedures explain how to restore NDPS onto a server that has crashed and contains the NDPS\RESDIR directory and the *.PA folders of the printer agents. If followed correctly, end users should not have to re-map their printers. The procedure assumes a multi-server tree with another replica on a different server.

Server-Side Installation Special Instructions

  1. Remove server from the existing NDS tree. Open NDSMGR32.EXE from SYS:\PUBLIC\WIN32. Right click on the server you want to delete and choose delete from the list. Wait for a few minutes and do a refresh of the list to make sure the server is out of all the replica rings. Once you are sure the server is completely out of NDS, proceed to step2.
  2. Open NwAdmin. You should see the original server objects with a yellow question mark for their icon. You will need to delete these before starting the installation of NetWare 5.

  3. Begin the installation of NetWare 5. When you get to the section about removing NetWare volumes, choose the 2nd option to remove all NetWare/NSS partitions and continue.
  4. Create the SYS volume the same size as before and continue.
  5. Enter the same server name when prompted during the server installation.
  6. Since you removed the server from NDS in step 1, install the server back into the same tree and the same context.
  7. At the screen labeled 'Additional Products and Services', make sure to place a checkmark in the box next to Novell Distributed Print Services (NDPS) and Finish to complete the installation.
  8. NOTE -- Even though the same IPX Internal Network number is not needed, it doesn't hurt to keep it the same. To change it, at the end of the install when it you asks you to reboot, say no, then edit the autoexec.ncf. The line to edit is 'SERVERID'. You can get the original network number by restoring the Server Specific Information from ADSM to another server and looking at the autoexec.ncf it restores.

  9. Click YES to reboot when the installation is finished.
  10. After the server reboot, install any Service Packs and patches. Also recreate any volumes that the server had before proceeding with the restore.

Procedure from a Workstation

  1. After logging into the NDS Tree, you will need to open ConsoleOne. The path is as follows:
  2. In ConsoleOne, browse to the context where the NDPS Manager and Broker reside and double click on the NDPS Manager object.
  3. Click on the 'Other' tab on top and then click the 'Add' button on the right to add an attribute to the object.
  4. Choose 'Host Device' and then click OK. Once that attribute is there, you need to give it a value. Browse and choose the server that you just reinstalled.
  5. Before you try loading the NDPS Broker, you will want to restore a directory of the Broker that contains the print drivers, banner pages and definitions that were previously setup. The directory to restore from backup is SYS:\NDPS\RESDIR. Restore this making sure to overwrite everything. Once you are sure the restore has been completed successfully, proceed to step 6.
  6. Go to the server console either physically or through RCONJ.EXE. Type in 'broker' at the console and choose the broker from the menu.
  7. If you get an error that the RMS server could not load, press <enter> to continue past the error. Arrow down to where it says 'Resource Management Service' disabled. Press <enter> and choose enable. It will prompt you for the path to the volume object. Enter it in the following format:
  8. Press <enter> and the RMS should load fine.

  9. Go back to the system console and type in 'ndpsm'. Browse to the NDPS Manager and press <enter>.
  10. You will get a message saying that the NDPS Manager resides on volume 'unknown'. Press <enter> to continue and then choose YES to move the NDPS Manager database. You will now be prompted to choose the volume on which you want to place the database. Choose the same volume as, ex. NDPS. The Manger and Printer Agents will now load correctly.

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions.

© Copyright Micro Focus or one of its affiliates