Parameter:
ReplicationTimeLimitShort description: Maximum duration (in minutes) for a single replication run – if replication runs longer, it is aborted and resumed later.
Profile
Parameter | ReplicationTimeLimit |
Category | Cluster |
Component | Server |
Available since | R4 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | Integer in minutes, 0 = no limit (default) |
Description
ReplicationTimeLimit sets a hard upper bound (in minutes) for a single replicator run to a target server. If the limit is exceeded, the replicator aborts the current run and resumes at the same point on the next trigger.Useful for preventing “endless replication loops” on databases with schema errors, and for making sure that short-lived replication windows (e.g. to mobile branch offices) are released again reliably.
Example configuration
ReplicationTimeLimit=60
Notes & pitfalls
- Value in minutes;
0= no limit.
- The next run continues where the previous one left off – no consistency risk.
- The cluster replicator has its own mechanisms; the limit primarily affects the classic Replicator.
- For very large databases (e.g. after a DAOS resync), prefer to raise the value temporarily.
- The change only takes effect after a replicator restart (
restart task replica).