TRANSLOG_Style

Parameter: TRANSLOG_Style
Short description: Determines the logging style of the transaction log: 0 = Circular (default, max 4 GB, circularly overwritten), 1 = Archive (logs are archived, prerequisite for incremental/point-in-time backups).

Profile

Parameter
TRANSLOG_Style
Component
Server
Category
Transaction log
Available since
Domino 5.x; currently documented in HCL Domino 9.0.x–14.5.1
Value format
Integer
Possible values
0 = Circular (default), 1 = Archive
GUI equivalent
Server document → "Transactional Logging" → "Logging style"

Description

Circular (TRANSLOG_Style=0, default)

  • Domino uses up to 4 GB of disk space in the translog directory and circularly overwrites the oldest entries once the limit is reached.
  • Advantages: simple, no external backup software required, low administrative overhead.
  • Disadvantages: no point-in-time recovery, no incremental backup based on translog. If a database is lost between two full backups, only data up to the last full backup can be restored.
  • Suitable when the change volume between two full backups stays under 4 GB.

Archive (TRANSLOG_Style=1)

  • Domino creates log file extents of 64 MB each and keeps them until a backup-capable tool (HCL Domino Backup, Tivoli Storage Manager, Veritas, IBM Spectrum Protect for Domino, ...) marks them as backed up. Only then are the extents reused.
  • Advantages: point-in-time recovery and incremental backup based on translog possible; disaster recovery via TRANSLOG_Recreate_Logctrl=1 is permitted only in this mode.
  • Disadvantages: requires a matching backup solution; without regular backup, the log area grows unbounded and can fill the translog volume.
  • Recommended for productive servers with high data criticality.

Linear (GUI only)

The server document additionally offers the "Linear" option. From the notes.ini perspective it behaves like Circular (TRANSLOG_Style=0), but allows a log file size beyond 4 GB (via TRANSLOG_MaxSize). HCL describes this in the Domino 11.0.1 Documentation "Preparing for transaction logging" as a solution for cases where more than 4 GB accumulates between two full backups but no archive medium should be used.

Switching from Circular to Archive

Per HCL KB0099512 "How to change the transaction logging style from 'Circular' to 'Archived'":
  1. Open the server document, "Transactional Logging" tab.
  1. Change "Logging style" from "Circular" to "Archived".
  1. Save the server document and let it replicate.
  1. Restart the Domino server – Domino assigns a new DBIID to every database when switching, the old DBIIDs are invalid.
  1. Take a full backup as soon as the server is running. Within a minute after start, the *.txn and logctrl.lfh are recreated; existing incremental backups are worthless without this full backup.

Examples

Circular for small to medium servers:
TRANSLOG_Status=1 TRANSLOG_Style=0 TRANSLOG_Path=D:\Domino\txn
Archive for productive servers with backup solution:
TRANSLOG_Status=1 TRANSLOG_Style=1 TRANSLOG_Path=D:\Domino\txn TRANSLOG_UseAll=0

Notes

  • DBIID change – Every change of style produces new DBIIDs on all logged databases. Incremental backups based on old DBIIDs are no longer usable.
  • Archive without a backup tool is dangerous – Without backup software that "releases" logs, the translog volume fills up and Domino stops incoming writes.
  • Effective only after restart – Changes to TRANSLOG_Style take effect at the next server start.
  • Companion parametersTRANSLOG_Status, TRANSLOG_Path, TRANSLOG_MaxSize, TRANSLOG_Performance, TRANSLOG_AutoFixup, TRANSLOG_UseAll, TRANSLOG_MAX_ARCHIVE_EXTENTS, TRANSLOG_Recreate_Logctrl.

Sources (HCL Product Documentation)