Open topic with navigation

Installation and upgrade notes

Review the following installation and upgrade notes before beginning your installation or upgrade.

• Since Double-Take Availability installs device drivers, it is recommended that you update your Windows Recovery Disk, before installing or making changes to your servers. For detailed instructions on creating a recovery disk, see your Windows reference manuals. Make sure that you select the option to back up the registry when building the repair disks.
• Because Double-Take Availability has operating system dependent files, if you are upgrading your operating system (to a new major version, not a service pack) and have Double-Take Availability installed, you must remove Double-Take Availability prior to the operating system upgrade. Uninstall Double-Take Availability, perform the operating system upgrade, and then reinstall Double-Take Availability.
• If you are installing to a drive other than the drive which contains your system TEMP directory, the Microsoft Windows Installer will still load approximately 100 MB of data to the TEMP directory during the installation. If you do not have enough disk space on the drive that contains the TEMP directory, you may need to change where it is located.
• If during the installation you receive a message for incorrect command line parameters, 8.3 file name support is disabled and there is a long file name component in the path to the temp directory. To work around this issue, you can enable 8.3 support or change your TEMP environment variable. See Microsoft Knowledge Base article 121007 for more details.
• If during the installation you receive the message that the wizard was interrupted before the installation could be completed, you will need to delete the registry value DefaultAccessPermissions under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole key in order to install Double-Take Availability. This registry setting denies permissions for retrieving and setting property values. Deleting this registry setting will not have a negative impact on your server.
• During installation, a file called dtinfo.exe is installed to the Double-Take Availability installation directory. This program can be run to collect configuration data for use when reporting problems to technical support. It gathers Double-Take Availability log files; Double-Take Availability and system registry settings; network configuration information such as IP, WINS, and DNS addresses; and other data which may be necessary for customer support to troubleshoot issues. After running the executable, a zip file is automatically created with the information gathered.
• Double-Take Availability 5.3 is interoperable back to version 5.1 but is restricted to the following limitations. The Double-Take Availability clients can only control the same or older releases. To accommodate rolling upgrades, older sources can connect to newer targets, but newer sources cannot connect to older targets.
• 5.1 client—Supports 5.1 source and target, but does not support 5.2 or 5.3 source or target
• 5.2 client—Supports 5.1 or 5.2 source and target as long as the target is the same or newer than the source, but does not support 5.3 source or target
• 5.3 client—Supports 5.1, 5.2, or 5.3 source and target as long as the target is the same or newer than the source
• When performing a rolling upgrade, update the target servers first. After the upgrade is complete, the sources will automatically reconnect to the targets. Upgrade the sources when convenient. 
• If you are using a chained configuration, update the last target first, then update the middle server acting as both a source and target, and update the production source last.
• If you are using a configuration where the source is an older version than the target, you will not be able to restore from the newer version target back to the older version source. You must upgrade the source to the same version as the target before restoring.
• Use the following procedure to upgrade Double-Take Availability on a cluster. If both your source and target are clusters, use the following procedure on the target cluster first, then on the source.
1. Move all cluster resources to one node.
2. Upgrade to the new version of Double-Take Availability on all of the other nodes.
3. Move the cluster resources to one of the upgraded nodes.
4. Upgrade to the new version of Double-Take Availability on the last node.
5. If needed, move the cluster resources to the desired nodes.
• If you are upgrading GeoCluster using a rolling upgrade of the nodes and the connection goes into an error state, you will have to manually restart a mirror or take the GeoCluster Replicated Disk Resource offline and then bring it back online to force the mirror.
• If you are upgrading GeoCluster and are currently using the GeoCluster Replicated Disk as the quorum resource, you will need to select another quorum resource before upgrading. See Configuring your cluster for GeoCluster installation for more information.
• During an installation or upgrade, if the GeoCluster Replicated Disk resource files fail to register with the cluster, use the DTResUtility, located in the \windows\cluster directory, to manually register the resources.
• If you have protected clusters with an earlier version of the Application Manager, you should disable protection, uninstall, and perform a clean install of the new version.