Configuring connection settings

This setting identifies the Target IP Address that the Double-Take Availability data will be transmitted through. You should only change this setting if you want to select a different route for Double-Take Availability traffic. On a machine with more than one NIC, this increases the flexibility of configuring Double-Take Availability activity. For example, you can separate regular network traffic and Double-Take Availability traffic on a machine. The default ports will be used.

By default, all of the SharePoint program and data files (except the \binn directory) are selected for replication to the target SharePoint server. This will allow the clients to access your production SharePoint server data and functionality on the target in the event of a failure.

The source and target servers must both have the exact same version of SharePoint (major and minor versions) as well as similar logical drive structures (the target must have at least the same logical drives as the source where SharePoint program and data files are stored).

Note:

If you are using a SQL server named instance for a back-end database server in your SharePoint setup, both the source and target SQL servers must have named instances with the exact same name and logical drive structure as the source SQL server installed prior to configuring protection. To enable the ability to add or remove SharePoint instances, you can launch Application Manager through the command line using the /sharepoint /advanced option (dtam /sharepoint /advanced). With this option enabled, a dialog box will appear when you select Configure Protection. If you need to reduce the amount of mirroring and replication traffic, you may choose to deselect the tempdb database if it is not necessary.

You can also select non-application specific data under the Volumes folder.

Note:

If Override Generated Rules is selected on the Advanced tab, this control will be disabled.

To refresh the tree view to show new source directories or files that may have been added or removed, select the logical node, then click the Refresh button. If a node in the volumes branch is selected, then the items under that node will be refreshed.

The following options specify what files you want sent from the source to the target during a mirror.

• Full—Copies all of the directories and files in the replication set to the target machine. If a mirror has already been completed, another full mirror will overwrite the data on the target.
• Checksum—(Default) This option performs a checksum comparison calculation. A checksum calculation is a formula applied to blocks of data to determine if the binary make-up of the block is identical. If the checksums on the source and target machine are the same, the block is skipped. If the checksums on the source and target machine are not the same, the block on the source is sent to the target. With this option, the entire file is not overwritten; only the block that is received from the source is overwritten.

Note:

The Mirror type setting also applies to the restoration connection.

This setting enables compression of data that is transmitted from the source to the target. Significant improvements in bandwidth utilization have been seen in Wide Area Network (WAN) configurations or in any case where network bandwidth is a constraint.

Compression may be used in Local Area Network (LAN) configurations, though it may not provide any significant network improvements.

You can specify compression for different source/target connections, but all connections to the same target will have the same compression settings.

By default, compression is disabled. To enable it, select Enable Compression, then set the level from minimum to maximum compression.