Parameter:
REPL_OBEY_QUOTASShort description: Forces the replicator to respect a target NSF's quota settings and stop writing documents as soon as the limit is reached.
Profile
Parameter | REPL_OBEY_QUOTAS |
Category | Cluster |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | 0 = ignore quota during replication (default), 1 = strictly enforce quota |
Description
NSF databases can have a quota (storage upper limit) and a warning threshold. With normal writes through the server, the quota is enforced automatically – historically, replication was not enforced: the replicator was allowed to write past the quota so that missing documents in full mail files could still be synced.
REPL_OBEY_QUOTAS=1 changes this: the replicator also stops at the quota. For compliance and storage-platform requirements ("nobody may exceed their quota"), this is often desired; in classic mail setups it is sometimes counterproductive, because mail is then lost instead of merely letting the file overflow temporarily.Example configuration
REPL_OBEY_QUOTAS=1
Notes & pitfalls
- Use cautiously for mail files – prefer setting the quota to a sufficiently large value, or use
Mail_Disable_Delivery_Above_Quota.
- Takes effect after a replicator restart (
restart task replica).
- Pairs with
Quota_Warning_Threshold,MailQuotaWarning,Mail.UseDelayMessage.
- The cluster replicator has its own switches – this value primarily affects the classic Replicator.
- Document in the audit log when enabled.