Networks

This is an article from CNENET. Hope it helps. Good Luck! Mike Tomasiewicz CNE, MCSE, CCA

The good part is the DSRepair option under replica and partition operations, specifically where you can remove the selected replica from the server.
Issue
Replica and Partition Operation

What is a partition?
It is a logical piece of the NetWare Directory Services database. It can be copied or replicated across servers. The first partition is the partition that encompasses the entire tree. The user can then segment the tree with more partitions. Partitions are created at the container level.

What is a replica?
A replica is a copy of a partition. Each partition will have one master replica, and could have one or more read/write or read only replicas. It is stored on the server and cannot be directly accessed by a user. Subordinate Replicas are automatically created where needed. They are created for tree walking and should NOT be deleted forcefully.

How many replicas are crea

if I remember right, what you need to do to remove the replica is to bring a server up with the server that origionaly held that replicas name. once it has been added into nds you can use ndsmanager to remove the replica from that server. after you have removed the replica you can remove nds from the server, and then remove the any objects in nds that point to that server ( like volume objects, the server object, or anything else like that)

I dont know how your partitions are build up but you can use DSREPAIR with some parameter to remove a replica and some dstrace commands to check your backlinks. But if are not familiar with this i recommand that you call novell support and they willguide you through this. This can dammage your system if not know for sure what your are doing.

I removed dying and bad replicas with this and it works

john

Tammy,

This is considered an advanced operation and you would probably be best off calling Novell Technical Support (with your credit card in hand :-). However, the tools to perform this operation are available to you.

First see Novell TID #10012858 in the Knowledgebase at support.novell.com. The health check for NDS that it describes is an excellent way of both knowing what's going on in NDS and in preparing for the kind of operation that you are contemplating.

Then try deleting theserver object in NDS (NWADMIN or NDSMgr) and giving NDS a chance to fix itself. Be sure also to remove the volume objects associated with the departed server.

If after a day that doesn't fix the problem:

(A)Have two good backups of your NDS database.
(B)Be sure that all servers holding replicas of the partition you wish to work with are up, running and communicating.
(C)At the console of the server holding the master replica of the partition you're going to work on:
1. LOAD DSREPAIR -A
2. Check time sync

Ok, first up, you cannot delete a server object from NWAdmin, you cannot delete a server that is up and running and in the tree. Go to NDSMgr, locate the server. Highlight it. You will (eventually) get an error. Right mouse click and select delete. Give your tree a chance to clean itself up. The main problem is that the other servers think that the server is up and running and are trying to sync with it. So deleting the server object SHOULD be enough for your tree to repair itself. Don't force a sync don't dsrepair it. Leave for maybe a day. You could cause more problems than you have now. If you still have problems after a couple of days, let me know.

Regards