Names database not replicating

[Bob Terry]

I receive a message from our domnio server that owns the names.nsf
that it has not replicated with any domino server in 24 then 48 then
ect... hours. We have 3 domino servers. The install is quite generic.
Where can I look to correct this problem?
Thanks

[Alex Kassabov]

Are your servers replicating at all? Do you have connection documents that
are enabled for scheduled replication? Check replication events in the Notes
log. If they are replicating, Notes log will tell you if there are errors
when trying to replicate the NAB.

--
Alex Kassabov
akas...@hotmail.com
Bob Terry wrote in message <36748102.228599543@news-server>...

[Sue Byers]

I would first make sure that the servers are communicating - that they
see each other. If they are, then look in the server connection documents

to make sure that they have replication schedules set up for them. Also,
look in the replication settings of each to make sure that they don't
have replication temporarily disabled. Also, make sure that they have the

same replica ID's!! If they don't, they won't replicate.

[John McCann]

Bob Terry wrote:
>
> I receive a message from our domnio server that owns the names.nsf
> that it has not replicated with any domino server in 24 then 48 then
> ect... hours. We have 3 domino servers. The install is quite generic.
> Where can I look to correct this problem?
> Thanks

Bob,

This may not be a problem. The message occurs because you have a
replication monitor in your events4.nsf database for names.nsf. The
replication monitor event will notify you if a particular database
hasn't replicated changes in the last xx hours.

Note key point, replicated changes. This message is based off the
replication history of the database in question. The replication
history maintains the last time stamp the a replication change was
made. If there is nothing to replicate because you haven't made any
changes to names.nsf, then the replication history won't get updated --
even though the servers are replicating successfully.
Regards,

John McCann
C-Lutions, Inc.
******************************************************************
Authors of C-Lutions SnapShot - for managing your Domino databases
http://www.c-lutions.com/snapshot
******************************************************************

[Bob Terry]

I do in fact have the monitor turned on and set for every 24 hours...
this is why I receive the messages. The server docs do have schedules
(and are enabled.). The servers can communicate (can ping by name from
the OS). Mail routing is working. As far as doc IDs go, the replicated
copies were created during the server setup.
From the notes workspace, I can force a one time repl (have not tried
letting it work in the background) and I will see 1, 2 maybe 4
changes: added, deleted updated ect...
From a server console, I can repl server/domain names.nsf and that
works also. But while monitoring the console of the one AS/400 domino
server yesterday, I noticed the server fired off replication and
stated that it could not communicate with one of the other two domino
servers. I entered a pull then a push of names.nsf to that server from
the console and that went fine. Go figure.
It seems that I get the message always over a weekend and maybe once
or twice during the week.

[Duane Scott]

This could also be based on your connection documents. If all your
replication is being pulls from the administrating server of the nab, it's
not doing any of the work, so technically, IT has not replicated with
another server....

Bob Terry wrote in message <367c4675.475536425@news-server>...