Viewing the log files through a text editor

You can view the Double-Take, Double-Take Management Service, job, and Double-Take Console log files through any text editor.

Viewing the Double-Take log

This log file is located in the same directory where you installed Double-Take. By default, this is \Program Files\Vision Solutions\Double-Take.

The Double-Take log 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, Double-Take begins 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 5, 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 Double-Take will continue writing log messages to that file. The Double-Take log file settings can be modified for each server. See Log file properties for details.

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

Date the message was generated
Time the message was generated
Process ID
Thread ID
Sequence number is an incremental counter that assigns a unique number to each message
The type or level of message displayed - 1 for warning or error message and 2 for informational message
Message ID, if any
Message text

02/07/2013 05:26:32.954 1360 3668 1 2 0 Using default heap

02/07/2013 05:26:33.048 1360 3668 3 2 0 Winsock v2.2Enabled

02/07/2013 05:26:35.689 1360 3668 5 2 0 Virtual operating system detected.

02/07/2013 05:26:35.689 1360 3668 6 2 69 Kernel Starting on BETA ip://112.42.74.30:6320 Version: 7.0.0.1124.0.S

02/07/2013 05:26:35.689 1360 3668 7 2 0 WARNING: Unable to determine Firewall status, assuming disabled.

02/07/2013 05:26:35.751 1360 3668 8 2 69 Kernel Started on BETA ip://112.42.74.30:6320 Version: 7.0.0.1124.0.S

02/07/2013 05:26:35.954 1360 3668 9 2 503008 LoadNL set state to IDLE

02/07/2013 05:26:35.954 1360 3944 10 2 503008 Op Retrieval: entering standard retrieval mode

02/07/2013 05:26:35.954 1360 3020 11 2 503008 Op Parsing: entering standard parsing mode

02/07/2013 05:26:36.017 1360 3668 12 2 0 The local security process has been added to the list of trusted processes

02/07/2013 05:26:38.751 1360 3668 14 2 0 SourceRelationships::UpdateSourceMap:GUID(A0779CDA-6FD7-4CB1-ACF0-804C710DCCD8)+SrcAddr(10.10.10

02/07/2013 05:26:38.751 1360 3668 15 2 0 Source IP '10.10.10.29:6320' for ServerID 'GUID(A0779CDA-6FD7-4CB1-ACF0-804C710DCCD8)+SrcAddr(10

02/07/2013 05:26:38.814 1360 3668 16 2 52000 New Target Internals created for 10.10.10.29:6320(ID GUID(A0779CDA-6FD7-4CB1-ACF0-804C710DCC

02/07/2013 05:26:38.876 1360 3668 17 2 302004 Queuing to disk has started

02/07/2013 05:26:38.876 1360 3668 18 2 302005 Disk Queue is empty - Queuing to disk has stopped

02/07/2013 05:26:38.939 1360 3668 19 2 52501 Target module loaded successfully

02/07/2013 05:26:39.064 1360 3816 20 2 71 Originator Attempting ip://10.10.10.29:6320

02/07/2013 05:26:39.157 1360 2260 21 2 72 Connection request from IP address 112.42.74.30

Viewing the Double-Take Management Service log

This file is located in the \Service\Logs subdirectory where you installed Double-Take.

The Double-Take Management Service log 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.20130207.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.20130207.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. The Management Service log file settings cannot be modified.

[2013-02-07 05:27:19] Verbose: Successfully opened service host JobManager (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-485657267ead - S

[2013-02-07 05:27:19] Verbose: Successfully opened service host WorkloadManager (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-485657267ea

[2013-02-07 05:27:19] Verbose: Successfully opened service host ManagementService (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-485657267

[2013-02-07 05:27:19] Verbose: Successfully opened service host CoreEngine (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-485657267ead - S

[2013-02-07 05:27:19] Verbose: Successfully opened service host CoreSystemState (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-485657267ea

[2013-02-07 05:27:19] Verbose: Successfully opened service host DiskManager (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-485657267ead -

[2013-02-07 05:27:20] Verbose: Completed: 10.10.10.30 (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-485657267ead - Establishing reserved

[2013-02-07 05:27:20] Information: The Double-Take engine is initialized. (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-485657267ead - St

[2013-02-07 05:27:20] Verbose: The Double-Take engine source module is initialized. (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-4856572

[2013-02-07 05:27:20] Verbose: The Double-Take engine target module is initialized. (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-4856572

[2013-02-07 05:27:20] Verbose: Removing Connection: Id = f34dcb1e-ac6b-4267-a891-5e45629bad8d, ReplicationSetName = (FilesAndFolders_cde9

[2013-02-07 05:27:20] Verbose: The Double-Take engine failover module is initialized. (PID:2512, TID:9, AID:fce50580-0307-4fe7-bcdb-48565

[2013-02-07 05:27:21] Verbose: Removing Monitor: Id = 5fa3b4eb-ea21-4e47-976e-25fd62c10c56, Name = ALPHA (PID:2512, TID:6, AID:fce50580-0

[2013-02-07 06:48:44] Verbose: Entered TopState (PID:2512, TID:13, AID:7c5f8158-16f0-4330-ad7a-f0f373475771 - Monitor ALPHA e74d0db8-1cbb

[2013-02-07 06:48:44] Verbose: Entered UninitializedState (PID:2512, TID:13, AID:7c5f8158-16f0-4330-ad7a-f0f373475771 - Monitor ALPHA e74

[2013-02-07 06:48:44] Verbose: Changing to StoppedState from UninitializedState in response to InitializeEvent consumed by UninitializedS

[2013-02-07 06:48:44] Verbose: Exited UninitializedState (PID:2512, TID:13, AID:7c5f8158-16f0-4330-ad7a-f0f373475771 - Monitor ALPHA e74d

[2013-02-07 06:48:44] Verbose: Entered InitializedState (PID:2512, TID:13, AID:7c5f8158-16f0-4330-ad7a-f0f373475771 - Monitor ALPHA e74d0

Viewing the job log

This file is located on the target server in the \Service\Logs subdirectory where you installed Double-Take.

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).20130207.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).20130207.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. The job log file settings cannot be modified.

[2013-02-07 06:48:46] Verbose: Entered TopState (PID:2512, TID:13, AID:e6246673-57a9-4a25-b67a-df5019c122ca - FilesAndFolders a6cbf990-ba

[2013-02-07 06:48:46] Verbose: Entered UninitializedState (PID:2512, TID:13, AID:e6246673-57a9-4a25-b67a-df5019c122ca - FilesAndFolders a

[2013-02-07 06:48:46] Information: Target beta is a NOT a cluster. Setting JobFilePath default (PID:2512, TID:4, AID:e6246673-57a9-4a25-b

[2013-02-07 06:48:47] Verbose: Entered TopState (PID:2512, TID:13, AID:e6246673-57a9-4a25-b67a-df5019c122ca - Monitor FilesAndFolders_a6c

[2013-02-07 06:48:47] Verbose: Entered UninitializedState (PID:2512, TID:13, AID:e6246673-57a9-4a25-b67a-df5019c122ca - Monitor FilesAndF

[2013-02-07 06:48:47] Verbose: Attaching to engine monitor 00000000-0000-0000-0000-000000000000 (PID:2512, TID:13, AID:e6246673-57a9-4a25

[2013-02-07 06:48:47] Verbose: Changing to StoppedState from UninitializedState in response to InitializeEvent consumed by UninitializedS

[2013-02-07 06:48:47] Verbose: Exited UninitializedState (PID:2512, TID:5, AID:e6246673-57a9-4a25-b67a-df5019c122ca - Monitor FilesAndFol

[2013-02-07 06:48:47] Verbose: Entered InitializedState (PID:2512, TID:5, AID:e6246673-57a9-4a25-b67a-df5019c122ca - Monitor FilesAndFold

[2013-02-07 06:48:47] Verbose: Entered StoppedState (PID:2512, TID:5, AID:e6246673-57a9-4a25-b67a-df5019c122ca - Monitor FilesAndFolders_

[2013-02-07 06:48:47] Verbose: Stopping monitor ab2268f7-85c6-4b68-819c-3d2912f5380a: name = FilesAndFolders_a6cbf990ba67403d855f5bb44c18

[2013-02-07 06:48:47] Information: Successfully created monitor 618b51de-70f0-418b-9869-169f6f7d7049 (PID:2512, TID:13, AID:e6246673-57a9

[2013-02-07 06:48:47] Verbose: Changing to StoppedState from UninitializedState in response to InitializeEvent consumed by UninitializedS

[2013-02-07 06:48:47] Verbose: Exited UninitializedState (PID:2512, TID:13, AID:e6246673-57a9-4a25-b67a-df5019c122ca - FilesAndFolders a6

[2013-02-07 06:48:47] Verbose: Entered InitializedState (PID:2512, TID:13, AID:e6246673-57a9-4a25-b67a-df5019c122ca - FilesAndFolders a6c

[2013-02-07 06:48:47] Verbose: Entered StoppedState (PID:2512, TID:13, AID:e6246673-57a9-4a25-b67a-df5019c122ca - FilesAndFolders a6cbf99

[2013-02-07 06:48:47] Verbose: Changing to StartingState from StoppedState in response to StartEvent consumed by StoppedState (PID:2512,

[2013-02-07 06:48:47] Verbose: Exited StoppedState (PID:2512, TID:13, AID:5decb7a7-ff7a-434b-a79d-0b31547b1dea - FilesAndFolders a6cbf990

[2013-02-07 06:48:47] Verbose: Entered StartingState (PID:2512, TID:13, AID:5decb7a7-ff7a-434b-a79d-0b31547b1dea - FilesAndFolders a6cbf9

[2013-02-07 06:48:48] Information: Event log entry written: '6008'. (PID:2512, TID:13, AID:e6246673-57a9-4a25-b67a-df5019c122ca)

[2013-02-07 06:48:48] Verbose: Target beta is not clustered (PID:2512, TID:13, AID:5decb7a7-ff7a-434b-a79d-0b31547b1dea)

[2013-02-07 06:48:48] Verbose: Changing to RunningState from StoppedState in response to StartEvent consumed by StoppedState (PID:2512,

[2013-02-07 06:48:48] Verbose: Exited StoppedState (PID:2512, TID:14, AID:e6246673-57a9-4a25-b67a-df5019c122ca - Monitor FilesAndFolders_

[2013-02-07 06:48:48] Verbose: Entered RunningState (PID:2512, TID:14, AID:e6246673-57a9-4a25-b67a-df5019c122ca - Monitor FilesAndFolders

[2013-02-07 06:48:48] Verbose: Starting monitor ab2268f7-85c6-4b68-819c-3d2912f5380a: name = FilesAndFolders_a6cbf990ba67403d855f5bb44c18

Viewing the Double-Take Console log

This file is called Double-Take Console.log and its location depends on your operating system. If you are using Windows 2008 or 2012, the file will be located in \Users\<your user name>\AppData\Local\Vision Solutions\Double-Take Console\Logs. If you are using Windows 2003, the log file will be located in \Documents and Settings\<your user name>\Local Settings\Application Data\Vision Solutions\Double-Take Console\Logs. Note that these are hidden locations, 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 Double-Take Console log files if you have multiple Double-Take users.

[2013-02-07 05:28:01] Verbose: Activating DoubleTake.Virtualization.VRA.Console.VRAConsoleExtension. (PID:620, TID:1, AID:fcdff5bc-0a6e-4

[2013-02-07 05:28:01] Verbose: Activating DoubleTake.Virtualization.VRA.Console.VRABindingProvider. (PID:620, TID:1, AID:4bd04ba6-0e54-4a

[2013-02-07 05:28:01] Verbose: Activating DoubleTake.Virtualization.VRA.Console.Model.VRASessionProvider. (PID:620, TID:1, AID:969421f5-b

[2013-02-07 05:28:02] Verbose: Rendering Tier = 0 (PID:620, TID:1, AID:00000000-0000-0000-0000-000000000000)

[2013-02-07 05:28:02] Verbose: Component Versions:

Microsoft .NET Framework: 2.0.50727.3053

Double-Take Console Framework: 7.0.0.1124

Double-Take Applications Console Library: 7.0.0.1124

Double-Take Dashboard Console Library: 7.0.0.1124

Double-Take Diagnostics Console Library: 7.0.0.1124

Double-Take Full Server Console Library: 7.0.0.1124

Double-Take Move Console Library: 7.0.0.1124

Double-Take for Hyper-V Console Library: 7.0.0.1124

Double-Take Virtualization UVRA Console Library: 7.0.0.1124

Double-Take Virtualization VRA Console Library: 7.0.0.1124

(PID:620, TID:1, AID:2e1d2989-7b38-4c9a-93b9-063a3c12b6f3 - Extensibility)

[2013-02-07 05:29:33] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0000-0000-000000000000)

[2013-02-07 05:40:52] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0000-0000-000000000000)

[2013-02-07 06:06:38] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0000-0000-000000000000)

[2013-02-07 06:25:02] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0000-0000-000000000000)

[2013-02-07 06:47:48] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0000-0000-000000000000)

[2013-02-07 06:48:46] Verbose: Creating job with options:

<JobOptions xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/DoubleTake.Jobs.Contra

<d2p1:Entries i:nil="true" />

<d2p1:Limit>0</d2p1:Limit>

<d2p1:Mode>NotLimited</d2p1:Mode>

<d2p1:Specifications xmlns:d3p1="http://schemas.datacontract.org/2004/07/DoubleTake.Core.Contract.Connection" i:nil="true" />

</BandwidthOptions>