You are here: Monitoring tools > Log files

Log files

Double-Take generates log files to gather alerts, which are notification, warning, and error messages.

Double-Take log—This log records data from the Double-Take service, also referred to as the Double-Take engine. The Double-Take service controls the data movement functions like Double-Take mirroring and replication. This log file can be viewed from within the Double-Take Console (see Viewing the log files through the Double-Take Console) or through any standard text editor (see Viewing the log files through a text editor). You can also filter the data in the log file using the Double-Take LogViewer utility. (see Filtering the log file with LogViewer).
Double-Take Management Service log—This log records data from the Double-Take Management Service. It controls all non-data movement aspects of each job. This log file can be viewed from within the Double-Take Console (see Viewing the log files through the Double-Take Console) or through any standard text editor (see Viewing the log files through a text editor).
Double-Take job log—This log records job specific message. There is a unique job log for each job you create. This log file can be viewed from within the Double-Take Console (see Viewing the log files through the Double-Take Console) or through any standard text editor (see Viewing the log files through a text editor).
Double-Take Console log—This log records data and user interaction from the Double-Take Console. This log file can be viewed through any standard text editor (see Viewing the log files through a text editor).
Appliance log—For full server to ESX appliance jobs, there are log files maintained on the appliance that record appliance processing. These log files are called master.log and job-<uid>.log, where uid is a unique identifier. You can find them on the appliance under /opt/dbtk/log. You can use any standard text editor to view the log files. If you are looking for source specific logging, check the log file on the source. For Windows source servers, that would be the Management Service log file described above. For Linux source servers, check the /var/log/messages file.

For cluster environments, be sure and review the log files on all nodes of the cluster.