I've got a bunch of replica databases that I'm trying to consolidate into one new database. I created a navigator with a link to the database that I want to use. I set the old database properties for all of the old databases to open this navigator in a new window when opening, however these database settings keep getting copied to the new database as well (so no matter how many times a user clicks on the redirection button, the same navigator window pops up). Is there a way to stop the database properties from being replicated without turning off replication? I am not very knowledgeable about Notes replication, so any info will be much apprecicated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Replica Database Properties
- Thread starter 1uptheman
- Start date
I am a bit confused about where exactly is your issue. Thankfully, you state that you do not know much about replication, so I might be able to clarify some things about it.
First of all, what is a replica ? Technically, a replica is a copy of a given database on another server, copy which reduces intra-server traffic (since users go to the closest copy to get the info). Replicas are updated regularly, sometimes more than once an hour. When replica copies update, they exchange their changelog and each grabs the updates from the other.
Thus, at the end of a replication, you (normally) have two identical copies of the same thing.
That said, I have difficulty understanding why you state that you need to "merge" replicas, since, in effect, they already do that several times a day.
Not understanding your question, I am tempted to answer that all you need is to link to the replica on the server closest to you, and leave it at that.
The usefulness of linking to several replica copies of the same database is quite questionable, especially since the server tends to give you access to the one closest to you, and not the one you actually clicked on.
Pascal.
First of all, what is a replica ? Technically, a replica is a copy of a given database on another server, copy which reduces intra-server traffic (since users go to the closest copy to get the info). Replicas are updated regularly, sometimes more than once an hour. When replica copies update, they exchange their changelog and each grabs the updates from the other.
Thus, at the end of a replication, you (normally) have two identical copies of the same thing.
That said, I have difficulty understanding why you state that you need to "merge" replicas, since, in effect, they already do that several times a day.
Not understanding your question, I am tempted to answer that all you need is to link to the replica on the server closest to you, and leave it at that.
The usefulness of linking to several replica copies of the same database is quite questionable, especially since the server tends to give you access to the one closest to you, and not the one you actually clicked on.
Pascal.
- Status
Similar threads
- Locked
- Question