APPLICATION MANAGEMENT
Temporarily disable replication
Select this option to temporarily suspend replication while you troubleshoot a problem. You can select this for one database, or if you use the IBMR LotusR Domino(TM) Administrator, you can disable replication of multiple databases. If a database is on a cluster server, disabling replication suspends both cluster replication and scheduled replication.
Scheduled replication priority
You can assign a replication priority of High, Medium, or Low to a database. Then in a Connection document, you can schedule replication so that databases of a particular priority replicate at specific times. For example, you can schedule low-priority databases to replicate less frequently and schedule high-priority databases to replicate more frequently. If you assign a different priority to two replicas, the priority of the replica on the server that initiates the scheduled replication takes precedence.
Replication priority doesn't apply to replicas on a server cluster. Cluster replication occurs whenever a change occurs, not according to schedules in Connection documents.
CD-ROM publishing date
Some organizations -- for example, publishing companies -- distribute databases on CD-ROM rather than replicate them. To receive updates, users replicate with a replica on the organization's server. The users specify the date the information was published on the CD-ROM so that the first replication with the organization's replica scans only documents created or modified since the publication date. If users do not specify the date, the initial replication unnecessarily scans the entire database, which can be a slow process, especially if it occurs over a dial-up connection.
See Also