Working With Log Files > Data Collector Log Files
  
Version 9.2.00
Data Collector Log Files
Table 16.1 Data Collector Logs
Log File Name
Location
Description
Component
 
wrapper.log
C:\Program Files\aptare\mbs\logs
Logging for the high-level management of the Watchdog component. Management includes startup, shutdown, and initialization.
Watchdog
start_watchdog.log
/opt/aptare/mbs/logs
watchdog.log
C:\Program Files\aptare\mbs\logs
Detailed logging for the Watchdog component. Logs all the functions Watchdog performs including downloading new configuration files etc.
/opt/aptare/mbs/logs
eventcollector.<id>.log
C:\Program Files\aptare\mbs\logs
Detailed logging for the processing of each backup job. The <id> corresponds to the event collector id specified in the collectorconfig.xml file. NOTE: To find the correct <id>, you can use the listcollectors utility.
Event Data Collector
/opt/aptare/mbs/logs
metadata.log
metadata.<id>.log
C:\Program Files\aptare\mbs\logs
Detailed logging for each of the meta data components. The <id> corresponds to the meta collector id specified in the collectorconfig.xml file. NOTE: To find the correct <id>, you can use the listcollectors utility.
Meta Data Collector
/opt/aptare/mbs/logs
To find the Event/Meta Collector ID
1. List the Data Collectors to get the Event/Metadata Collector ID.
Windows:
C:\opt\APTARE\mbs\bin\listcollectors.bat
Linux:
/opt/aptare/mbs/bin/listcollectors.sh
In the output, look for the Event Collectors section associated with the Software Home—the path that was specified when the Data Collector Policy was created.
==== Event Collectors ===
Event Collector Id: EVENT_1029161_9
Active: true
Active: true
Software Home: C:\gkgenericBackup.csv
Server Address: 102961
Domain: gkdomain
Group Id: 102961
Sub-system/Server Instance/Device Manager Id: 102961
Schedule: */10 * * * *