Client and Journal Daemon traceflags

Edit online

To run journal-based backup, you must use the Journal Daemon process. This process is used to track file system changes and maintain change journal databases.

The Journal Daemon uses the same tracing mechanism as the client, but the trace settings are specified in the journal configuration file (tsmjbbd.ini) as follows: 
[JournalSettings]
TraceFlags=all_jbb
;
; the following two settings allow tracefile segmentation
;
TraceMax=100
TraceSegMax=1
tracefile=tracefiles\trace.out
Journal Daemon specific trace settings:
  • BTREEDB - low-level BTREE database base class
  • CACHEDB - disk cache backup and Windows 2003 exclude cache processing
  • DBPERF - low-level database operation performance
  • DBSTATS - performance tracking of database query, insert/update, delete, and tree walk operations
  • FILEOPS - internal database activity
  • JBBCOMM - listening thread
  • JBBDAEMON - process manager
  • JBBFILEMON - file system monitor
  • JBBDBACCESS - database controller thread
  • JBBDBINFO - low-level database access
  • JBBNPCOMM - named pipe communications
  • JBBSERVICE - Windows platform-specific service tracing
  • JBBVERBINFO - detailed verb information
  • ALL_JBB - aggregate traceflag that includes all of the above settings
Trace Settings for the backup-archive client specified in dsm.opt:
  • JOURNAL - journal based backup tracing