Solved

Moving Server object in NDS

Posted on 1997-09-08
1
219 Views
Last Modified: 2006-11-17
In Netware 4.1, I want to move a server object and other leaf objects in the same container to another container in the tree using the move function in NWADMIN. What is the impact of doing this? Do I need to change the context in the server and restart it? Do I need to remove it from the tree before doing this?
0
Comment
Question by:chipsd
1 Comment
 
LVL 1

Accepted Solution

by:
sundancer earned 100 total points
ID: 1590623

It's either very easy or a nightmare, depending on how well you know your environment.  The move affects everything on that server and on those servers with which is shares replicas.  One wrong step, and your server object and/or tree is hosed.  That's the nightmare.  

But it actually very easy to move, as trustee rights will travel with the object(s) when moved within NwADMIN. (Trivia question:  what ONE instance is this not true?)

A few tips:

    o backup the server *AND* NDS first!

    o speed up move by making sure the server to be moved
       holds a replica of the partition where it currently exists

    o if moving to a container with a different partition, add
      a replica for it on the server to be moved.

    o the obvious, make sure NDS is synching properly.                  Especially check all servers hold replicas of it's
         partitions (old container and new one).

  Use dstrace to check them:
    SET DSTRACE=ON  
    SET DSTRACE=*h.
Check the directory screen to make sure ALL PARTITIONS PROCESSED = YES.  Make sure you resolve any errors!!!!


To move it, in NWADMIN click on it and hit F7 (move).  Then walk the tree to put it where you want.

Then check the partition states on the moved server, and at least one other server which holds a RW replica of that partition.
     
     SET DSTRACE=+limber
     Type SET DSTRACE=*L
 
Check the directory services screen for errors.  If you see "Limber: start connectivity check" and "Limber: end connectivity check", the server object was successfully moved.

The corresponding volume objects can be, but don't have to be, moved.  User rights travel with the objects when moved within NWADMIN.

Only remove the server as a last resort.  Even though you can now  remove a server without removing the rights, it's a bigger risk than just moving the server.

    If using bindery emulation (sounds like you are), make the necessary changes to AUTOEXEC.NCF, and make them live by:
  SET BINDERY CONTEXT = new.bindery.context;plus.others.needed


You don't need to reboot the server, but I like too anyway, just for grins. (That is, after I'm sure it's working!)

Keep in mind the static assignments when changing the server context.  Make sure you update the NDS clients, NDS-aware printers, NDS-aware backups, scripts, AUDIT assignments and test 'em out.


Cool trick for small networks (< 100):
  Create an alias in the server context for each user.  This allows them to log in no matter what the Preferred Context is set up as.  Cuz if it doesn't find them in the current context, it looks in the server context for the user object.  


If you are Netware smart, you'll be sweating bullets the whole time.  I've done several hundred moves, only blown the first couple (NDS.NLM rev 4.63 SUCKED), but it still makes me nervous.


Test test test to make sure it works.  It makes for happy clients!
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Performance in games development is paramount: every microsecond counts to be able to do everything in less than 33ms (aiming at 16ms). C# foreach statement is one of the worst performance killers, and here I explain why.
Moving applications to the cloud or switching services to cloud-based ones, is a stressful job.  Here's how you can make it easier.
This video discusses moving either the default database or any database to a new volume.
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now