Question : Netward 5.1 - Replicas not syncing in timely manner

I have a four server Netware 5.1 setup.  All servers have been patched with SP6e, and are running DS NLM 8.85.

There are four servers, server 1 through 4.  SERVER1 is the Master replica, with a R/W replica on 2,3,4.

When I do a DSRepair, 'Report Sync status...' I get results like this (going with a current time of 8:45)

Replica     Server1        9-07-2004        8:27:34
Replica     Server2        9-07-2004        8:39:34
Replica     Server3        9-07-2004        8:43:08
Replica     Server4        9-07-2004        8:44:43

My biggest problem is when I create users, we have to wait 15-30 minutes for everything to sync, and then they can log in.

My biggest personal quandry is why the Master replica is always the oldest.

I would assume, with all servers connected so closely, there shouldn't be any lag (esp. with high-priority items like password changes and user creation).  There are no communication problems between servers, and workstations can access all no problem.  Time is reported in sync.

Any insight, thoughts, opinions welcome.

Thanks,

TN

Answer : Netward 5.1 - Replicas not syncing in timely manner

It IS a little unusual for there to be such a spread in sync times across the replicas.

Try this

1) At the server console, enter --> SET DSTRACE=ON
2) Then enter --> SET DSTRACE=+s
3) Then enter --> SET DSTARCE=+h

This will activate the Trace to Screen feature in NDS, and specifically tell it to report synchronization and heartbeat activity. A new screen on the NetWare console will be created, you access it the same way you access any other screen on the NetWare console. You can watch the NDS activity.

You can do this on each server if you like.

Look for errors like "Replica in skulk", which is usually a transitory error message that means when a server went to synch NDS with another server, that server was already busy performing another synch, and so couldn't synch with the particular server on which you see the error message.

My suspicion, given what you've reported, is that your environment has too much NDS sychronization going on, and its delaying the propogation of changes, because everyone is trying to synch with everyone else (each server have to synch with 3 others). The result is a mild case of gridlock.

I'd suggest deleting one R/W replica and seeing is the situation doesn't improve.