Open topic with navigation

Configuring server startup options

From the Replication Console, you can configure server startup options for each Double-Take Availability server.

1. Right-click a server on the left pane of the Replication Console.
2. Select Properties

3. Select the Setup tab.

   

4. Specify the server setup and source startup options.
• Log Statistics Automatically—If enabled, Double-Take Availability statistics logging will start automatically when Double-Take Availability is started.

• Enable Task Command Processing—Task command processing is a Double-Take Availability feature that allows you to insert and run tasks at various points during the replication of data. Because the tasks are user-defined, you can achieve a wide variety of goals with this feature. For example, you might insert a task to create a snapshot or run a backup on the target after a certain segment of data from the source has been applied on the target. This allows you to coordinate a point-in-time backup with real-time replication.

  Task command processing can be enabled from the Replication Console, but it can only be initiated through the scripting language. See the Scripting Guide for more information.

  If you disable this option on a source server, you can still submit tasks to be processed on a target, although task command processing must be enabled on the target.

• Enable Extended Attribute replication/mirroring—This option enables extended attribute replication and mirroring. You must enable this option on all of your source and target servers.
• Automatically Reconnect During Source Initialization—If enabled, Double-Take Availability will automatically reconnect any connections that it automatically disconnected.
• Perform Remirror After Auto-reconnect—If enabled, Double-Take Availability will automatically perform a remirror after an auto-reconnect has occurred. You will also need to specify the type of mirror that you wish to perform after an auto-reconnect.
• Differences with Checksum—Any file that is different on the source and target based on date, time, and/or size is flagged as different. The mirror then performs a checksum comparison on the flagged files and only sends those blocks that are different.
• Differences with no Checksum—Any file that is different on the source and target based on date, time, and/or size is sent to the target.

• Full—All files are sent to the target. 

  Database applications may update files without changing the date, time, or file size. Therefore, if you are using database applications, you should use the Differences with checksum or Full option.

   

5. Click OK to save the settings.

Related Topics