|
|
You might be a Domino geek if ... You understand your replication topology!
Notes replication. The synchronisation of data over time by distributing changes. If your compulsion to minimise replication conflicts means your replication topography resembles a spiders web, you might just be a Domino Geek.
Last week I mentioned the Comms Rule, and the Routing Rule. Today - The Replication Rule!
The Replication rule is even easier than the Routing Rule, and maybe just a little more complex than the Comms rule, but even so it's still pretty simple...
And the Replication rule is:
Replication ONLY occurs according to the schedule set in connection documents.
Of course, you could sit at the Domino console all day long typing "rep ....", but who wants to pass their days that way?
That's where Notes replication connection documents come in. Which databases, at what frequency, with which other servers?
Server to server replication is different within a Notes domain to Mail routing. With mail routing, as long as the Comms rule is met, works all by itself with little, or no, administrative intervention. With Replication, as long as the Comms rule is met, only works by itself if a connection document is in place.
Replication connection documents allow you to choose individual databases, directories full of databases, or even databases with a certain replication priority to replicate on a schedule.
The important thing to note is that this all occurs ONLY according to the schedule set in the connection documents.
No Schedule. No Replication.
Which leads me to the bane of a database administrators life - replication conflicts.
Most replication conflicts are a symptom of an inadequate replication schedule. The less frequently two notes applications synchronise, the more likely there will be a replication conflict. Another simple Notes concept.
So get your replication connections under control and enjoy an easier administrative life.
Notes Rulez!
|