How to Safely Move Server Objects in NDS.
(Last modified: 14Nov2002)
This document (10018521) is provided subject to the disclaimer at the end of this document.
How to Safely Move Server Objects in NDS.
How to move a server to a different context.
Novell NetWare 5.0
Novell NetWare 4.11
Previously TID 2934240
To ensure a smooth move of a server object in NDS, complete the following procedure. Please note that there are differences in moving a server object in NW5, and are noted where necessary.
I. Prerequisites :
a) Ensure that all servers are running at least NetWare 4.1x. The limber process (which keeps the network address and server name updated in NDS) in NW 4.1x is more robust than previous versions of NetWare 4. Trees consisting of NetWare 4.0x or a mixture of NetWare 4.0x and NetWare 4.1x servers may cause a server object not to be moved successfully. NetWare 5 servers and mixed NetWare 4.1x and NetWare 5 environments do not pose a problem for a server object move.
b) Make certain that you are using the current DS.NLM versions on all servers. The latest patches can always be found at https://support.novell.com/misc/patlst.htm.
c) If you want to increase the speed of the move, ensure that the server to be moved holds a replica of the partition in which it exists (i.e., the "source" partition). If the server will be moved to a container in a different partition ("destination"), it is recommended that the server hold a replica of that partition also.
d) Verify that source and destination partitions (if different) are synchronizing properly. This should be done on server(s) holding a replica of the partition(s) in question. If source and target partition are not the same and do not reside one server, you need to perform the synchronization check both on a server holding the source partition and the destination partition.
The way to check this is to load DSREPAIR.NLM | Advanced options | Replica and Partition Operations. Select the partition in question and then "Report synchronization status of all servers". Any errors on this status screen should be resolved before proceeding.
e) Check that the partitions held on the moved server (if any) are synchronizing by loading DSREPAIR.NLM on the server and selecting Report synchronization status. Any errors on this status screen should be resolved before proceeding.
f) Ensure that there are no obituaries related to the server object. This is done by running DSREPAIR on the server holding the master replica of the source partition:
Load DSREPAIR -a | Advanced options | Check external references.
If there are any obituaries on the server object they should be resolved. An example of an obituary referring to the server object V70XC could look like :
Found obituary at VID: 00015680, EID: 04000408, DN: CN=V70XC.OU=Cemetary.OU=ESC.O=Novell.Novell_Inc
TV: 1-22-1998 13:27:10 0001, Type = 0003 INHIBIT_MOVE, Flags = 0000
Further information on resolving obituaries is available in the following TIDs :
2923724 - Previous Move in Progress -637 / Obituaries
2942837 - Resolving -637 errors without calling Novell
****NW5 NOTE: Movement of a NW5 server impacts several components that rely on the NW5 server's context. These include all license objects and containers, the NLS_LSP object, the SAS:Security object, LDAP and possibly other 3rd party objects. If the server is moved, all license components need to be deleted from the old container and re-installed in the new. .....SAS:Security and LDAP ........
II. The Actual Move:
Move the server object using NWAdmin.exe (SYS:PUBLIC/WIN32/NWADMIN.EXE.). Highlight the NetWare server object, go to the Object menu, then select Move from the destination context and launch the move. If the moved option is greyed out, use ConsoleOne.
Move the server object using ConsoleOne. Highlight the Server object, go to File menu, then select Move and browse to the destination context.
III. Post Move:
a) The move operation is not completed until the obituaries related to the move have disappeared from the master(s) of the partitions holding the server object. In large trees with many references to the object this can take some time - particularly if one or more servers referring to the moved server are not available. They will stop the move process until they "acknowledge" the move. Failure to complete this step often leads to "Previous move in progress" or -637 errors when attempting partition operations at a later stage. Use the previously described procedure to check obituaries on the server object. Keep in mind that slow WAN links or servers being down can delay the progress of the obituary. Refer to the above mentioned TIDs in case the obituaries do not disappear.
b) Check that the partitions held on the moved server are synchronizing by loading DSREPAIR.NLM | Report Synchronization Status. Any errors on this status screen should be troubleshot and resolved.
c) The volume objects are separate objects that can also be moved, but they do not move automatically with the file server object. They can be moved using the same method described above. Moving the volume object is optional; it is not required. Trustee assignments are not affected by moving the volume objects.
d) Update the server's bindery context using the SERVMAN.NLM utility or the SET BINDERY CONTEXT console command. The Bindery Context is located in Server parameters, Directory Services in AUTOEXEC.NCF (SERVMAN will prompt you to save the changes in AUTOEXEC.NCF when exiting)..
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
- Document ID:
- Solution ID: 1.0.33663814.2352104
- Creation Date: 07Oct1999
- Modified Date: 14Nov2002
Did this document solve your problem? Provide Feedback