Viewing the log files through a text editor

You can view all logs through a standard text editor.

• Windows and Linux engine log—On a Windows server, the engine log file is located, by default, in \Program Files\Carbonite\Replication. On a Linux server or appliance, the engine log file is located, by default, in /var/log/DT.

  The file consists of a base name, a series number, and an extension. The base name is dtlog and the extension is .dtl. The series number ranges from 1 to 999. For example, Carbonite Availability and Carbonite Migrate begin logging messages to dtlog1.dtl. When this file reaches its maximum size, which by default is 5 MB, the next log file will be written to dtlog2.dtl. As long as log messages continue to be written, files dtlog3.dtl, dtlog4.dtl, and dtlog5.dtl will be opened and filled. When the maximum number of files is reached, which by default is 20, the oldest file is deleted. For example, when dtlog6.dtl is created, dtlog1.dtl is deleted, and when dtlog7.dtl is created, dtlog2.dtl is deleted. When file dtlog999.dtl is created and filled, dtlog1.dtl will be re-created and Carbonite Availability and Carbonite Migrate will continue writing log messages to that file.

  The following list describes the information found in each column of the log file.

  1. Date the message was generated
  2. Time the message was generated
  3. Process ID
  4. Thread ID
  5. Sequence number is an incremental counter that assigns a unique number to each message
  6. The type or level of message displayed - 1 for warning or error message and 2 for informational message
  7. Message ID, if any
  8. Message text
• Windows Management Service log—On a Windows server, the Management Service log file is located, by default, in \Program Files\Carbonite\Replication\Service\Logs. The file consists of a base name, an optional date, an optional series number, and an extension. The base name is ManagementService and the extension is .log. When this file reaches its maximum size, 10 MB, the file will be renamed with the current date in year, month, day format. For example, it might be ManagementService.20190207.log. The latest log messages are then stored in ManagementService.log. If the main file fills again on the same day, then a series number will be used. In this case, the ManagementService.log file will be renamed to ManagementService.20190207.1.log. If the main file is filled on a different day, that date will be specified. In each case, the latest log messages will be stored in ManagementService.log. When the maximum number of files is reached, which is 5, the oldest file is deleted.
• Linux Management Service log—On a Linux server or appliance, the management service log file is called master.log and is located, by default, in /opt/dbtk/log. This log rolls when it reaches the maximum size. The series number for the log file is added after the .log extension, so you may see master.log, master.log.1, master.log.2, and so on.
• Windows job log—For a Windows job, the job log is located on the target server in the \Service\Logs subdirectory where you installed Carbonite Availability and Carbonite Migrate. The job log file consists of a global unique identifier (GUID) for the job and the job name. When this file reaches its maximum size, 10 MB, the file will be renamed with the current date in year, month, day format. For example, it might be a6cbf990-ba67-403d-855f-5bb44c18e1d6 (alpha to beta).20190207.log. The latest log messages are then stored in the base GUID_name.log file. If the main file fills again on the same day, then a series number will be used. In this case, the example file would be renamed to a6cbf990-ba67-403d-855f-5bb44c18e1d6 (alpha to beta).20190207.1.log. If the main file is filled on a different day, that date will be specified. In each case, the latest log messages will be stored in the main GUID_name.log file. When the maximum number of files is reached, which is 5, the oldest file is deleted.
• Linux job log—For a Linux job, the job log is located on the appliance in the /opt/dbtk/log directory. The file is called job-<GUID>.log, where GUID is a global unique identifier. The maximum size is 10 MB and then the file will roll to a new log file, maintaining three older log files before replacing the oldest.
• Carbonite Replication Console log—This file is called Carbonite Replication Console.log and is located in \Users\<your user name>\AppData\Local\Carbonite\ConsoleUI\Logs. This location is hidden, so you will have to search directly for the file name or display hidden files to browse for it. Also note that the log file is dependent on the user who is logged in, so there will be multiple Carbonite Replication Console log files if you have multiple Carbonite Availability and Carbonite Migrate users.