Replication enterprisewide

hcl-bot · May 13, 2004, 1:58pm

I’m transitioning from a development role into that of sys admin and I’m puzzled about server → server replication.

Isn’t it enough to name one server in the “master” replica of a database as Manager, and list “LocalDomainServers” as Reader, so that the main server can push changes to the outlying servers and their replicas? All I get in my LOG.NSF are a series of message like:

5/13/2004 7:17:50 AM Access control is set in DB.NSF to not allow replication from DB.NSF

5/13/2004 7:33:07 AM Access control is set in DB.NSF to not allow replication from DB.NSF

What am I missing?

hcl-bot · May 13, 2004, 2:33pm

Subject: Replication enterprisewide

I don’t think so. When replication happens, server A isn’t making changes on server B. Rather, server A tells server B what changes to make. Server B still has to have appropriate permissions to the database in order to make those changes. That means, among other things, that if you want permission changes to propogate among replicas, all the servers involved need to have Manager permission.