Double-Take Availability Release Notes

Double-Take Availability version 7.0, Wednesday, May 15, 2013

© 1996-2013 Double-Take Software, Inc. All rights reserved.

Check the Vision Solutions support web site for the most up-to-date version of this readme file.

This readme file contains last minute release notes about Double-Take Availability that are not included in the user documentation. The user documentation is available on the product CD and in the installation directory after you have installed Double-Take Availability.

Contents

Overview

  1. This release is an updated release that includes, but may not be limited to, the modifications and features listed in this section.
  2. Since this release is an updated release, it supersedes all previous releases. You can safely upgrade to this release from any previous Double-Take Availability 4.7.x or 6.0 release.
  3. This release does not support full server failover. However, you can configure a full server job and use an application note to walk you through a manual recovery process. Contact technical support if you are interested in this process and to get a copy of the application note.

Known Issues

Installation and configuration

  1. If you are using SLES version 10.x, you may get an installation database warning regarding an exclusive database lock. You can safely disregard this message.
  2. Double-Take Availability does not currently support Red Hat Enterprise Linux version 6.0 eCryptfs, which is a new operating system feature that provides data and filename encryption on a per-file basis. This limitation may be resolved in a future release.
  3. If you are upgrading from version 4.7, use the following steps to update the Double-Take driver on the Linux source to the new driver included in this release.
    1. Shut down all of your protected applications on your Linux source.
    2. Save your DTFS configuration by moving /etc/DT/dtfs_mounts to another location, outside of /etc/DT.
    3. If you were using full server protection with version 4.7, you will need to remove it using DTSetup (Setup tasks, Configure File System or Block Device Replication, Full Server Replication Configuration, Remove Full Server Protection).
    4. Stop the Double-Take service and driver using DTSetup (Start/Stop Double-Take daemon, Stop the running service and teardown driver config).
    5. If you were using full server protection with version 4.7, reboot the Linux source server to unload the old driver.
    6. Upgrade Double-Take on your Linux source using the installation instructions in the User's Guide.
    7. Restart Double-Take on your Linux source.

Replication

  1. If you have hard links in your replication set, note the following caveats.
  2. Two replication operations are sent when a file is closed. This may have a negative effect on performance. This issue may be resolved in a future release.
  3. If your replication set contains exclude rules for specific files, the replication set generated during the restoration process will not contain those same exclude rules. Therefore, if those excluded files exist on the target, they may be restored, potentially overwriting the files on the source. This issue may be resolved in a future release.

General functionality

  1. If you specify NoMoveAddresses with the MonitorOption DTCL command, the addresses will still be moved after failover. This issue may be resolved in a later release.
  2. When you schedule start criteria for transmission, you may see the transmission status in an error state at the scheduled start. The transmission will still continue as expected. This may be resolved in a later release.
  3. When you schedule a verification process, it may run a verification report when you save the scheduled verification settings. The scheduled verification will still process as expected. This may be resolved in a later release.
  4. If you are moving or deleting orphan files, select a move location outside of the replication set. If you select the location where the files are currently located, the files will be deleted. If you select another location inside the replication set, the files will be moved multiple times and then possibly deleted.
  5. The ability to stop transmission based on a specified byte limit is currently not functional. This issue may be resolved in a later release.

Clients

  1. The Replication Console and interactive text client (DTCL -i) will fail if there is no DNS entry or way for a server to resolve server names.
  2. If you have created a full server to ESX appliance job using the Double-Take Availability for Windows product, do not use the Replication Console that is installed with Double-Take Availability for Linux to try and control the full server to ESX appliance job.

Contact Information

This documentation is subject to the following: (1) Change without notice; (2) Furnished pursuant to a license agreement; (3) Proprietary to the respective owner; (4) Not to be copied or reproduced unless authorized pursuant to the license agreement; (5) Provided without any expressed or implied warranties, (6) Does not entitle Licensee, End User or any other party to the source code or source code documentation of anything within the documentation or otherwise provided that is proprietary to Vision Solutions, Inc.; and (7) All Open Source and Third-Party Components (“OSTPC”) are provided “AS IS” pursuant to that OSTPC’s license agreement and disclaimers of warranties and liability.

Vision Solutions, Inc. and/or its affiliates and subsidiaries in the United States and/or other countries own/hold rights to certain trademarks, registered trademarks, and logos. Hyper-V and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a registered trademark of Linus Torvalds. vSphere is a registered trademark of VMware. All other trademarks are the property of their respective companies. For a complete list of trademarks registered to other companies, please visit that company’s website.

© 2013 Vision Solutions, Inc. All rights reserved.