The following table lists all of the Linux server and job settings, in decimal value.
Double-Take products share the same set of server and job settings. You may only have a subset of the settings listed below depending on Linux your operating system and Double-Take product.
Double-Take Availability terminology is used in the following list. For example, failover is used for Double-Take Availability and cutover for Double-Take Move.
ActivationCode
Description—24-character Double-Take license key
Values—Unique value for each customer
Default—N/A
Console setting—Edit Server Properties page, Licensing section, Current license keys
Service restart required—No
AdapterFlags
Description—Specifies the adapter to use when establishing a connection. This option should not be changed.
Values—2 Encryption, 4 Network Data Representation
Default—4
Console setting—None
Service restart required—No
Advertisement
Description—This setting is no longer used.
AllFailover
Description—Specifies which IP addresses to failover
Values—0 Failover only monitored IP addresses, 1 Failover all IP addresses
Default—1
Console setting—None
Service restart required—No
AllMustFail
Description—Specifies whether or not all IP addresses must fail for failover to take place
Values—0 Any IP address can fail, 1 All IP addresses must fail
Default—1
Console setting—None
Service restart required—No
AutoReconnect
Description—Specifies whether to reinstate the target connection(s) when the source machine is brought online after a source machine failure
Values—0 Do not reconnect, 1 Reconnect
Default—1
Console setting—None
Service restart required—Yes
AutoRemirror
Description—Specifies whether to remirror when a source is brought online after an auto-disconnect
Values—0 Do not compare or send any files, 1 Compare file attributes and send the attributes and bytes that are different, 2 Do not compare files, just send all files (the entire file), 3 Compare file attributes and send the entire file for those that are different, 4 Compare file attributes and data and send the attributes and bytes that are different
Default—1
Console setting—None
Service restart required—No
AutoRemirrorRetry
Description—Specifies how often, in seconds, the source should check for connections that have been reconnected but still need to be remirrored
Values—any integer
Default—30
Console setting—None
Service restart required—No
AutoRetransmit
Description—Determines whether or not a source that has lost its connection with a target will attempt to reconnect to the target
Values—0 Do not attempt to reconnect, 1 Attempt to reconnect
Default—1
Console setting—None
Service restart required—No
BackupDir
Description—Location on the target of the backup of the protected data sets
Values—any valid path
Default—the location where the Double-Take files were installed
Console setting—None
Service restart required—No
CalculateOnConnect
Description—Specifies whether or not the amount of data to be mirrored should be calculated on connection
Values—0 Do not calculate on connection, 1 Calculate on connection
Default—1
Console setting—None
Service restart required—Yes
CaseSensitiveRepSetQueries
Description—This entry is no longer used.
ChecksumAll
Description—Indicates if a mirror, verify, or restore will ignore all attributes and perform a checksum calculation on all files
Values—0 Compare files by attribute, 1 Compare files by checksums
Default—1
Console setting—None
Service restart required—No
Cleaner
Description—Specifies if a clean mirror will delete files on the target before mirroring
Values—0 Do not delete files before mirroring, 1 Delete files before mirroring
Default—0
Console setting—None
Service restart required—No
Notes—This option is only valid if you have this option enabled and use the clean option with the DTCL mirror command.
ClientLog
Description—This setting is no longer used.
ClientLogName
Description—This setting is no longer used.
ConnectionFile
Description—Name of the database file containing connection information
Values—any valid file name
Default—connect.sts
Console setting—None
Service restart required—No
DataPath
Description—The location of the Double-Take file attribute, protected data set, connection, and schedule database files
Values—any valid path
Default—the location where the Double-Take files were installed
Console setting—None
Service restart required—No
DefaultProtocol
Description—The default protocol
Values—1 IPv4 protocol only
Default—1
Console setting—None
Service restart required—Yes
DirUNetPort
Description—Port used for directed UDP communications
Values—1025 - 65535
Default—1505
Console setting—None
Service restart required—Source yes, Target no
DisableAttributeReplication
Description—Specifies whether or not attributes (user, group, or other permissions) are replicated to the target
Values—0 Enable attribute replication, 1 Disable attribute replication
Default—0
Console setting—None
Service restart required—No
EnablePerformanceTracking
Description—This entry will be used in the future.
EnableSparseFileMirroring
Description—Specifies if sparse files are mirrored
Values—0 Disable mirroring of sparse files, 1 Enable mirroring of sparse files
Default—1
Console setting—None
Service restart required—No
EnableTaskCmdProcessing
Description—Queues tasks inline with replication data
Values—0 Disable task command processing, 1 Enable task command processing
Default—0
Console setting—None
Service restart required—No
EnableVolumeLevelReplication
Description—Used by internally for full server jobs
EncryptionCipherFilter
Description—Encryption uses AES 256. Public key exchange uses industry-defined methods implemented by OpenSSL.
EncryptNetworkData
Description—Encrypts Double-Take data before it is sent from the source to the target
Values—0 Disable data encryption, 1 Enable data encryption
Default—0
Console setting—Edit Server Properties page, General section, Encrypt network data
Service restart required—No
Notes—Both the source and target must be Double-Take encryption capable (Double-Take version 8.0.0 or later), however this option only needs to be enabled on the source or target in order to encrypt data. Keep in mind that all jobs from a source with this option enabled or to a target with this option enabled will have the same encryption setting. Changing this option will cause jobs to auto-reconnect and possibly remirror.
ExtendedAttributes
Description—Specifies whether or not extended attributes are replicated to the target
Values—0 Extended attributes are not mirrored or replicated, 1 Extended attributes are mirrored and replicated
Default—0
Console setting—None
Service restart required—No
ExtensionNumber
Description—Used by the Double-Take log files.
FileQueueSize
Description—When a mirror is started, one thread reads from the disk and builds the file queue. Another set of threads reads files off of the queue and sends them to the target. This setting is the maximum size of the queue in entries. If you had 100 files to be mirrored and this was set to 16 (the default value), the first thread would fill the queue to a maximum of 16 entries.
Values—1 - 65535
Default—16
Console setting—None
Service restart required—No
Notes—This value must be set prior to starting the mirror process. The higher the number, the more memory that is used.
HBExternalRate
Description—Number of seconds between heartbeats
Values—0 - 65535
Default—3
Console setting—None
Service restart required—No
Notes—Double-Take Software recommends a value that is less than 10 (see HBTTL). Zero (0) turns the heartbeats off.
HBInteralRate
Description—This entry is no longer used
HBLoopback
Description—This entry is no longer used.
HBTrace
Description—Specifies whether heartbeat debugging information is generated
Values—0 not generated, 1 Generated
Default—0
Console setting—None
Service restart required—No
HBTTL
Description—Number of seconds without receiving a heartbeat before a remote machine is considered unavailable
Values—0 - 65535
Default—10
Console setting—None
Service restart required—No
HPQueueRatio
Description—Ratio of replication packets to one mirror packet
Values—1 - 65535
Default—5
Console setting—None
Service restart required—No for future connections, Yes for the current connection
Notes—An HPQueueRatio of 5 indicates 5 replication packets to 1 mirror packet.
IgnoreDeleteOps
Description—Specifies if file and directory delete operations will be replicated to the target
Values—0 Delete operations are replicated to the target, 1 Delete operations are not replicated to the target
Default—0
Console setting—None
Service restart required—No
LoadSourceTarget
Description—Specifies the functionality of the Double-Take
Values—0 Neither the source nor target modules are loaded, 1 Only the source module is loaded, 2 Only the target module is loaded, 3 Both the source and target modules are loaded
Default—3
Console setting—None
Service restart required—Yes
LogAllOrphans
Description—Specifies whether success messages regarding orphan files are logged to the Double-Take log
Values—0 Do not log orphan file success messages to the Double-Take log, 1 Log orphan file success messages to the Double-Take log
Default—0
Console setting—None
Service restart required—No
LogDir
Description—The location of the Double-Take messages/alerts, verification, and statistics log files
Values—any valid path
Default—the location where the Double-Take files were installed
Console setting—None
Service restart required—Yes
LogFile
Description—The name of the Double-Take messages/alerts log file
Values—any valid file name
Default—DTLog
Console setting—None
Service restart required—No
LogMessageLevel
Description—Specifies the types of messages logged to the.dtl files
Values—0 No messages will be logged, 1 Only alert messages will be logged, 2 Alert and release messages will be logged, 3 Alert, release, and debug messages will be logged
Default—2
Console setting—None
Service restart required—No
MaxChecksumBlocks
Description—Specifies the number of checksum values retrieved from the target
Values—any integer
Default—32
Console setting—None
Service restart required—No
MaxConnections
Description—Number of network requests that can be processed simultaneously.
Values—0 - 65535
Default—5
Console setting—None
Service restart required—Yes
Notes—Double-Take Software recommends that you not change this value.
MaxLogFileSize
Description—Maximum size, in bytes, of any .dtl log file
Values—limited by available disk space
Default—5242880
Console setting—None
Service restart required—No
MaxNumberofLogFiles
Description—Maximum number of .dtl log files that can exist at one time. When Double-Take creates a new .dtl file, if this number is exceeded, the oldest .dtl file is deleted.
Values—1 - 999
Default—20
Console setting—None
Service restart required—No
MaxRemoveOrphansOpSize
Description—Determines whether or not Double-Take will send over multiple orphan operations. Double-Take will send over the operations if a directory has more files than this number.
Values—0 - 131072
Default—1000
Console setting—None
Service restart required—No
MaxRetry
Description—A generic, application wide setting specifying the number of retry attempts for processes such as creating sockets, starting the service, and so on
Values—any integer
Default—5
Console setting—None
Service restart required—Yes
MaxWriteChunkSize
Description—Maximum merged op size (in bytes) used during replication
Values—1 - 131072
Default—65536
Console setting—None
Service restart required—No
MemoryQueueToDiskThreshold
Description—A percentage of QmemoryBufferMax that will trigger queuing to disk.
Values—any valid percentage
Default—100
Console setting—None
Service restart required—Yes
MinCompressionFileSize
Description—The minimum file size, in bytes, that will be compressed. Files smaller than this size will not be compressed.
Values—any file size
Default—1024
Console setting—None
Service restart required—No
MirrorChunkSize
Description—Block size, in bytes, used in the mirroring process
Values—1 - 1048576
Default—65536
Console setting—None
Service restart required—No
Notes—A higher block size value gives you better throughput, but only to a certain point, then it starts using more memory (this has to do with the way memory is allocated and deallocated). A lower block size value produces slower throughput, but uses memory efficiently.
MirrorOverwrite
Description—Determines if the mirror process overwrites existing files
Values—0 never overwrite, 1 always overwrite, 2 overwrite if older
Default—1
Console setting—None
Service restart required—No
MirrorPrompting
Description—This entry is no longer used.
MirrorQueueLimit
Description—Maximum number of mirror operations that can be queued on the source machine
Values—1 - 65535
Default—1000
Console setting—None
Service restart required—No
MirrorZeroKFiles
Description—Specifies whether or not empty files, zero byte files, are included in a mirror
Values—0 Zero byte files are skipped and not mirrored to the target, 1 All files are mirrored to the target
Default—1
Console setting—None
Service restart required—No
Notes—If MirrorZeroKFiles is enabled (0), zero byte files are skipped during a full mirror, file differences mirror, and a verification with synchronization.
MissedPackets
Description—Specifies the number of requests sent by the target that go unanswered by the source before failover occurs, when using network responses to monitor for failover
Values—1 - 65535
Default—5
Console setting—None
Service restart required—No
MoveOrphanedFiles
Description—Specifies if orphaned files are deleted or moved to the directory specified by MoveOrphansDir
Values—1 Move, 0 Delete
Default—0
Console setting—None
Service restart required—No
MoveOrphansDir
Description—Indicates the name of the directory where orphaned files will be moved if MoveOrphanedFiles=1
Values—any valid path
Default—the location where the Double-Take files were installed
Console setting—None
Service restart required—No
NetPort
Description—Port connection for TCP communications
Values—1025 - 65535
Default—1500
Console setting—None
Service restart required—Yes
NetworkRetry
Description—Specifies the interval, in seconds, at which Double-Take will attempt to reconnect to the target
Values—any positive number
Default—10
Console setting—None
Service restart required—No
NetworkStatusInterval
Description—An internal setting for network communications. Do not modify this setting.
NetworkTimeout
Description—The maximum length of time, in seconds, to wait on a network connection. If data is not received over a network connection within the specified time limit, the connection is closed. During idle periods, Double-Take sends small amounts of keep-alive data at an interval 1/6 of the NetworkTimeout value to keep the socket from being inadvertently closed.
Values—any integer
Default—120
Console setting—None
Service restart required—No
Notes—If you are archiving files and it takes longer than the NetworkTimeout specified (for example, this may happen if the DTArchiveBin is located on an alternate volume), the archive operation will complete on the target, but the full file will not be changed to a link on the source because the source detected the network timeout.
NodeLockedLicenseKey
Description—An internal setting for licensing. Do not modify this setting.
OpBufferSize
Description—Specifies the number of operations that can be stored in the memory queue prior to queuing to disk.
Values—0 There is no limit to the number of operations that can be stored in the memory queue, 1 or any larger integer
Default—0
Console setting—None
Service restart required—No
PingFrequency
Description—Specifies, in seconds, how often a ping is sent to the source from a monitoring target
Values—1 - 65535
Default—5
Console setting—None
Service restart required—No
PreFailbackWait
Description—Specifies whether or not to wait for the target pre-failback script to complete before finishing a failback
Values—0 Do not wait, 1 Wait
Default—0
Console setting—None
Service restart required—No
PreFailoverWait
Description—Specifies whether or not to wait for the target pre-failover script to complete before finishing a failover
Values—0 Do not wait, 1 Wait
Default—0
Console setting—None
Service restart required—No
QJournalDir
Description—The location where the queue is stored.
Values—any valid path
Default—the location specified during the installation
Console setting—None
Service restart required—No
Notes—For best results and reliability, you should select a dedicated, non-boot volume. The queue should be stored on a dedicated, high-performance local volume (like SSD or high-speed HDD backed volume). The volume should not be used for any high I/O activity applications.
QJournalFileSize
Description—The size, in MB, of each queuing transaction log file.
Values—any valid file size, up to 4095 MB
Default—5
Console setting—None
Service restart required—No
QJournalFreeSpaceMin
Description—The minimum amount of disk space, in MB, in the specified QJournalDir that must be available at all times.
Values—dependent on the amount of physical disk space available
Default—250
Console setting—None
Service restart required—No
Notes—The QJournalFreeSpaceMin should be less than the amount of physical disk space minus QJournalSpaceMax.
QJournalPreload
Description—The number of operations being pulled from the disk queue at one time. Do not modify this setting.
QJournalSpaceMax
Description—The maximum amount of disk space, in MB, in the specified QJournalDir that can be used for Double-Take queuing. When this limit is reached, Double-Take will automatically begin the auto-disconnect process.
Values—dependent on the amount of physical disk space available
Default—Unlimited
Console setting—None
Service restart required—No
Notes—The unlimited setting allows the disk queue usage to automatically expand whenever the available disk space expands. Setting this option to zero (0) disables disk queuing. Even if you are using the unlimited option, Double-Take will only store 16,384 log files. If you are using the default 5MB file size, this is approximately 80GB of data. If you anticipate needing to be able to queue more data than this, you should increase the size of the log files.
QLogWriteThrough
Description—Specifies if the disk queues are write-through mode
Values—0 Disk queues are not write-through mode, 1 Disk queues are write-through mode
Default—0
Console setting—None
Service restart required—No
Notes—While write-through mode may decrease the frequency of auto-disconnects, it may also decrease the performance of the source server.
QMemoryBufferMax
Description—The amount of system memory, in MB, that, when exceeded, will trigger queuing to disk.
Values—minimum 512, maximum is dependent on the server hardware and operating system
Default—1024
Console setting—None
Service restart required—Yes
QueueSizeAlertThreshold
Description—The percentage of the queue that must be in use to trigger an alert message
Values—any valid percentage
Default—50
Console setting—None
Service restart required—Yes
RemapLink
Description—Specifies how Double-Take handles a soft link
Values—0 If a soft link exists in a replication set and points to a file or directory inside the replication set, the path contained in the link will retain its original mapping, 1 If a soft link exists in a replication set and points to a file or directory inside the replication set, Double-Take will remap the path contained in that link based on the Double-Take target path
Default—1
Console setting—None
Service restart required—No
RemoveAllOrphans
Description—Specifies if all orphan files will be removed or only those based on RemoveOrphanTime
Values—0 Remove orphans based on the entry RemoveOrphansTime, 1 Remove all orphans
Default—1
Console setting—None
Service restart required—No
RemoveOrphansTime
Description—Specifies the amount of time, in minutes, that must be expired before an orphan file is removed
Values—1 - 131072
Default—60
Console setting—None
Service restart required—No
ReplaceTarget
Description—Specifies whether or not to replace the target identity with the source identity during a failover
Values—0 Do not replace, 1 Replace
Default—0
Console setting—None
Service restart required—No
RepSetDBName
Description—Name of the database that contains protected data set information
Values—any valid file name
Default—DblTake.db
Console setting—None
Service restart required—No
RestoreOverwrite
Description—Determines if the restoration process overwrites existing files
Values—0 never overwrite, 1 always overwrite, 2 overwrite if older
Default—2
Console setting—None
Service restart required—No
RestorePrompting
Description—This entry is no longer used.
RestoreSpecialExecutableHandling
Description—Specifies if an alternate file is created and updated during a restoration for executables that are in use
Values—0 Do not use alternate files for executables that are in use, 1 Use alternate files for executables that are in use
Default—1
Console setting—None
Service restart required—No
SaveStatFile
Description—Determines if the statistic.sts (statistics logging) file is saved or ovewritten
Values—0 overwrite, 1 saved as statistic-old.sts
Default—1
Console setting—None
Service restart required—No
ScheduleFile
Description—Name of the database file that contains transmission scheduling information
Values—any valid file name
Default—Schedule.sts
Console setting—None
Service restart required—Yes
ScheduleInterval
Description—The number of seconds to wait before checking the transmission schedules to see if transmission should be started or stopped
Values—1 - 3600
Default—1
Console setting—None
Service restart required—Yes
ShareUpdateInterval
Description—Specifies how often, in minutes, the share file will be sent to the target
Values—1 - 65535
Default—60
Console setting—None
Service restart required—No
SkipCompressionFileExt
Description—A period delimited list of file types that are not compressed, even if compression is enabled.
Values—any period delimited list of file types
Default—mp3.exe.wmv.wma.qt.mpg.mpeg.zip.jpg.jpeg.tiff.rar.cab.tgz.bz.bz2.z.pkg.sea.sit.sitx
Console setting—None
Service restart required—No
SmallFileThreshold
Description—Identifies the size of a small file. The entire file will be mirrored if the file size is below this threshold, thus improving mirror speeds.
Values—any integer
Default—65536
Console setting—None
Service restart required—No
SourcePendingAcks
Description—The number of operations received by the target queue in which the source is waiting for a response
Values—100 - 20,000
Default—2000
Console setting—None
Service restart required—No
StatsFileName
Description—Default file for logging statistics
Values—any valid file name
Default—statistic.sts
Console setting—None
Service restart required—No
StatsLoggingOn
Description—Specifies if Double-Take logs statistics at startup
Values—0 Stats logging does not start when Double-Take starts, 1 Stats logging starts when Double-Take starts
Default—0
Console setting—None
Service restart required—No
StatsMaxFileSize
Description—Maximum size, in MB, for the statistic.sts file
Values—limited by available disk space
Default—10485760
Console setting—None
Service restart required—No
StatsMaxObjects
Description—This entry is no longer used.
StatsPort
Description—Port used by DTStat to gather Double-Take statistics
Values—1025 - 65535
Default—1506
Console setting—None
Service restart required—No
StatsShmSize
Description—This entry is no longer used.
StatsWriteInterval
Description—Interval, in minutes, in which statistics are written to the statistic.sts file
Values—0 - 65535
Default—5
Console setting—None
Service restart required—No
SystemMemoryLimit
Description—Set by the Double-Take service, each time it is started, to record the amount of available memory.
TargetPaused
Description—Internal setting that indicates if the target machine is paused. Do not modify this setting.
TargetPausedVirtual
Description—Internal setting that indicates which target machines are paused. Do not modify this setting.
TCPBufferSize
Description—Size of the TCP/IP buffer in bytes.
Values—4096-7500000
Default—375000
Console setting—None
Service restart required—Yes
Notes—This is an operating system buffer, not a Double-Take buffer. If this option is set to zero (0), Linux kernel versions 2.6.7 or later can automatically tune this buffer setting for best server performance. Therefore, the recommended setting is 0 for automatic tuning, if you are using a version 2.6.7 or later Linux kernel. If you want to reduce or control network traffic, you can configure this option to a static size. The default is 375000 for a 1 GB network. Modifications should be relative to that speed using the calculation 37500 * network_speed_in_bits_per_second / 100 Mbit.
TGCloseDelay
Description—The length of time, in milliseconds, a file is held open on the target
Values—0 - 2000
Default—1000
Console setting—None
Service restart required—No
Notes—If disk caching on the target is disabled either manually or by default (for example, by default on disks that host Active Directory database files), the target system may be slow during a mirror. If so, descreasing this setting to 100, 10, and 0 will result in incremental improvements, with 0 returning the system performance to normal.
TGExecutionRetryLimit
Description—The number of times an unfinished operation will be retried on the target before it is discarded. If this value is set to zero (0), an operation will never be discarded and will be retried on the target until it is applied.
Values—0 - 65536
Default—0
Console setting—None
Service restart required—No
TGMirrorCapacityHigh
Description—Maximum percentage of system memory that can contain mirror data before the target signals the source to pause the sending of mirror operations.
Values—2-75
Default—20
Console setting—None
Service restart required—No
TGMirrorCapacityLow
Description—Minimum percentage of system memory that can contain mirror data before the target signals the source to resume the sending of mirror operations.
Values—1-75
Default—15
Console setting—None
Service restart required—No
Notes—The maximum value forTGMirrorCapacityLow is either 75 or TGMirrorCapacityHigh, which ever is lower.
TGRetryLocked
Description—Minimum number of seconds to wait before retrying a failed operation on a target
Values—0-65536
Default—3
Console setting—None
Service restart required—No
TGThreadCount
Description—This setting is no longer used
TGUseExtendedQueue
Description—Specifies whether or not Double-Take uses the extended queue
Values—0 Use the extended queue, 1 Do not use the extended queue
Default—1
Console setting—None
Service restart required—No
TGWriteCache
Description—Specifies whether or not Double-Take uses the intermediate cache
Values—0 Bypass the intermediate cache and write directly to disk, 1 Do not bypass the intermediate cache
Default—0 for full server to ESX jobs, 1 for all other job types
Console setting—None
Service restart required—No
TGWriteFailureBeforeNotification
Description—Specifies the number of times an operation will be retried on the target before a notification is sent to update the target status
Values—0-1024
Default—10
Console setting—None
Service restart required—Yes
Notes—If you change the setting to 0, the notification will be disabled. Changing this option will only affect how the target status is displayed. To solve the underlying issue of why the operations are failing will require investigation into the Double-Take log files.
UNetPort
Description—Port connection for UDP communications
Values—1025 - 65535
Default—1500
Console setting—None
Service restart required—Yes
UpdateInterval
Description—Interval, in seconds, at which the Failover Control Center updates the monitored machines display
Values—1 - 9999
Default—1
Console setting—None
Service restart required—No
UserIntervention
Description—Specifies whether or not user intervention is required to initiate a failover
Values—0 User intervention is not required, 1 User intervention is required
Default—1
Console setting—None
Service restart required—No
UseShareFile
Description—Specifies whether to create and use a share file or to use the shares that are currently stored in the target memory
Values—0 Use the shares that are currently stored in the target memory, 1 Create and use a file containing the share information
Default—1
Console setting—None
Service restart required—No
VerifyLogAppend
Description—Specifies whether the DTVerify.log file will be appended to or overwritten
Values—0 Overwrite, 1 Append
Default—1
Console setting—None
Service restart required—No
VerifyLogLimit
Description—Maximum size of the DTVerify.log file in bytes
Values—limited by available hard drive space, up to 4 GB
Default—1048576
Console setting—None
Service restart required—No
VerifyLogName
Description—Name of the verification log file
Values—any valid file name
Default—DTVerify.log
Console setting—None
Service restart required—No
VerifyRetryInterval
Description—The time, in minutes, between when one verification fails and a retry is scheduled to begin.
Values—any valid number
Default—3
Console setting—None
Service restart required—No
VerifyRetryLimit
Description—The number of time a verification will be retried.
Values—any valid number
Default—5
Console setting—None
Service restart required—No
WarningPings
Description—This entry is no longer used.