Before you can establish a connection, you must create a replication set.
Expand the tree under the replication set name to view the volume and directory tree for the source.
The default number of files that are listed in the right pane of the Replication Console is 2500, but this is user configurable. A larger number of file listings allows you to see more files in the Replication Console, but results in a slower display rate. A smaller number of file listings displays faster, but may not show all files contained in the directory. To change the number of files displayed, select File, Options and adjust the File Listings slider bar to the desired number.
To hide offline files, such as those generated by snapshot applications, select File, Options and disable Display Offline Files. Offline files and folders are denoted by the arrow over the lower left corner of the folder or file icon.
Identify the data on the source that you want to protect by selecting volumes, drives, directories, and/or specific files.
Be sure and verify what files can be included by reviewing Replication capabilities.
Replication sets should only include necessary data. Including data such as temporary files, logs, and/or locks will add unnecessary overhead and network traffic. For example, if you are using Samba, make sure that the location of the lock file (lock dir in samba.conf) is not a location in your Double-Take Availability replication set.
The block devices configured for Double-Take Availability replication are shown by default. Highlight the device to include in the replication set and click OK.
If the device you want to include is not displayed, you can click Show Other Devices to view all devices which are eligible for Double-Take Availability replication. You can select any of these devices, but you cannot use them for Double-Take Availability replication until they are configured for Double-Take Availability replication. The status no dtloop indicates the device is not configured for Double-Take Availability replication.
Make sure your target has a partitioned device with sufficient space. It should be equal to or greater than the storage of the source device.
The partition size displayed may not match the output of the Linux df command. This is because df shows the size of the mounted file system not the underlying partition which may be larger. Additionally, Double-Take Availability uses powers of 1024 when computing GB, MB, and so on. The df command typically uses powers of 1000 and rounds up to the nearest whole value.