Server document - Transactional Logging tab

Use the fields on this tab to enable and configure transaction logging, or to disable transaction logging.


  1. Complete these fields:
    Table 1. Basics



    Transactional Logging

    Choose one:

    • Enabled -- To start transaction logging. When you choose Enabled, all other fields in this table display.
    • Disabled (default) -- To not use transaction logging

    Log path

    Enter the path name location of the transaction log.

    For best results, use a separate mirrored device, such as a RAID (Redundant Array of Independent Disks) level 0 or 1 device with a dedicated controller. This provides better performance and data integrity than using the default path (\LOGDIR) in the Domino® data directory.

    Note: If the device is used solely for storing the transaction log, set the Use all available space on log device field to Yes.

    Use all available space on log device

    For circular and linear logging only. Choose one:

    • Yes -- To use all available space on the device for the transaction log. Choose Yes if you use a separate device dedicated to storing the log.
    • No -- To use the default or specified value in the Maximum log space field.

    Maximum log space

    For circular and linear logging only. The maximum size, in MB, for the transaction log. Default is 192MB. Maximum is 4096MB (4GB).

    Allocate a separate disk with at least 1024MB (1GB) of disk space for the transaction log.

    Domino® formats at least 3 and up to 64 log files, depending on the maximum log space you allocate.

    Automatic fixup of corrupt databases

    Choose one:

    • Enabled (default) -- To run the Fixup task automatically if a database is corrupted and Domino® cannot use the transaction log to recover it. Domino® assigns a new DBIID and notifies the administrator that a new database backup is required.
    • Disabled -- To not run the Fixup task automatically. Domino® notifies the administrator to run the Fixup task with the -J parameter on corrupted logged databases.

    Runtime/Restart performance

    This field controls how often Domino® records a recovery checkpoint in the transaction log. This affects server performance as databases may be flushed from the cache to disk.

    To record a recovery checkpoint, Domino® evaluates each active logged database to determine how many transactions would be necessary to recover each database after a system failure. When Domino® completes this evaluation, it:

    • Creates a recovery checkpoint record in the transaction log that lists each open database and the starting point transaction needed for recovery
    • Forces database changes to be saved to disk if they have not been saved already

    Choose one:

    • Standard (default and recommended) -- To record checkpoints regularly.
    • Favor runtime -- To record fewer checkpoints. This option requires fewer system resources and improves server run-time performance but causes more of the log to be applied during restart.
    • Favor restart recovery time -- To record more checkpoints. This option improves restart recovery time because fewer transactions are required for recovery.

    Logging style

    Choose one:

    • Circular (default) -- To re-use the log files and overwrite old transactions.
    • Archived (recommended) -- To re-use the log files after they are archived. A log file can be reused when it is inactive, which means that it does not contain any transactions necessary for a restart recovery. Use a third-party backup utility to copy and archive the existing log. When Domino® using the existing file again to Start, Domino® increments the log file name. If all the log files become inactive and are not archived, Domino® creates additional log files.
    • Linear -- To re-use the log files and overwrite old transactions for log size greater than 4GB.
  2. Use this field to define the database quota enforcement method. When you complete these fields, you generate the NOTES.INI setting NSF_QUOTA_METHOD on server startup. This NSF NOTES.INI affects all processes on the server. Any Note that is updated by any process uses this setting.
    Table 2. Quotas



    Quota enforcement

    If quota enforcement methods are enabled, when a note is updated, Domino® compares the current file size to the configured quota or threshold. If the size exceeds the quota, Domino® takes appropriate action.

    Choose one of these:

    • Check space used in file when adding a note -- Domino® calculates the current size of an NSF and determines whether the NSF is in compliance with configured warning thresholds or quotas based on this calculation. White space in the database is discounted.
    • Check file size when extending the file -- Domino® calculates the current size of a file from its actual physical size. The calculated physical size includes the unused white space in an NSF that results when information is deleted or archived. Domino® does not immediately recover this white space. As a result, accumulated white space may account for a large portion of the NSF size.
    • Check file size when adding a note -- Domino® calculates the current size of an NSF from its actual size. White space in the database counts toward the total size. This option is more restrictive than the preceding option, because Domino® checks the quota every time a note is updated, regardless of whether this results in an increase in file size.