When you use multiple replicators, each replicator handles only one replication session at a time. For example, if Hub-E/East/Acme is scheduled to replicate with HR-E/East/Acme and with Hub-W/West/Acme simultaneously, one replicator handles replication between Hub-E/East/Acme and HR-E/East/Acme, while a second replicator handles replication between Hub-E/East/Acme and Hub-W/West/Acme.

Multiple replicators handle multiple replications between one source server and multiple destination servers simultaneously. Multiple replicators do not handle replications of multiple individual databases on a source server with a single destination server. For example, if both Database 1 and Database 2 on Hub-E/East/Acme need to replicate with Hub-W/West/Acme, only one replicator handles each replication session, one at a time.

Examine the Connection documents that schedule replication on each server. By adjusting the schedules and enabling multiple replicators, you can shorten the time it takes to complete a replication cycle. With this shortened cycle, you can schedule one or more additional cycles per day, which means fewer database updates and speedier replications per cycle. After you start multiple replicators, you can use the Tell command to stop all replicators; however, you can't use the Tell command to stop a specific replicator.

To enable multiple replicators

Method	Steps
From the NOTES.INI file	Edit the Replicators or ServerTasks setting in the NOTES.INI file.
From the console	Enter the Load Replica command at the console. Use this method if you need more replicators and you don't want to shut down the server to change the NOTES.INI file. Each time you enter this command, the server loads another replicator.

Related topics

Customizing server-to-server replication
Scheduling server-to-server replication
Replicators
Using a console to send commands to a server
Editing the NOTES.INI file
NOTES.INI Settings

Glossary