Enabling scheduled replication

When clustering Domino servers, the cluster replicator task will keep the databases synchronized, but it is a best practice to also schedule a periodic replication.

About this task

Related: Using scheduled replication in a cluster

Enabling scheduled replication of the Sametime databases to the cluster members

It is recommended to both cluster replicate and schedule replication between servers for these databases:
  • Names.nsf – contains the directory.
  • Any secondary names.nsf files if they are used in your environment.
  • Directory assistance database (file name varies, and may not be used).
  • stnamechange.nsf – used by the name change task.
  • vpuserinfo.nsf – contains the user’s contact list and privacy settings.

By default the names.nsf and vpuserinfo.nsf should have the same replica ID on each server. You may need to pull a new replica of the other databases so that each server have the same replica ID.

Enabling scheduled replication of the Sametime databases to other Sametime servers outside the cluster

Your Sametime environment may include servers outside of the Sametime cluster, or Sametime servers in other clusters. It is important to replicate the names.nsf changes to these servers as well. They should be periodically replicating using a scheduled replication. Typically once every 4-6 hours is sufficient.

Note: The VPUserInfo.nsf and stnamechange.nsf should be unique to each Sametime cluster. Do not replicate these databases outside of the cluster from which they belong.


Use the steps from the Domino Help Center to create a new replica from one server to the other.

Use these steps from the Domino Help Center to Schedule replication for a time range with a repeat interval. Again you only need to replicate the databases listed above. If you do not specify which databases to replicate, all databases and templates with the same replica ID will replicate.