Review the installation notes below before beginning an installation or upgrade.
Because Double-Take 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 installed, you must remove Double-Take prior to the operating system upgrade. Uninstall Double-Take, perform the operating system upgrade, and then reinstall Double-Take.
During the installation, DTInfo is installed. This is a utility that can be run to collect configuration data for use when reporting problems to technical support. It gathers Double-Take log files; Double-Take and system settings; network configuration information such as IP, WINS, and DNS addresses; and other data which may be necessary for technical support to troubleshoot issues.
On Windows servers, the DTInfo utility is DTInfo.exe, and it is installed to the Double-Take installation directory. After running the executable, a zip file is automatically created with the information gathered. You can also collect this information from the Double-Take Console, storing the resulting zip file on the console machine . See Managing servers.
On Linux source servers, the DTInfo utility is DTInfo.sh, and it can be run from DTSetup. After running the script, a .tar.gz is automatically created with the information gathered. You must have root (or uid 0 equivalent) to execute the diagnostics or to copy or read the resulting file.You can also collect this information from the Double-Take Console, storing the resulting file on the console machine . See Managing servers.
On the Double-Take Linux virtual recovery appliance, DTInfo can be run manually from /usr/bin. It should be executed as DTInfo.sh -f. After running the script, a .tar.gz is automatically created with the information gathered. You can also collect this information from the Double-Take Console, storing the resulting file on the console machine . See Managing servers.
The following notes are specific to Windows servers.
Since Double-Take 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.
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 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. This registry setting denies permissions for retrieving and setting property values. Deleting this registry setting will not have a negative impact on your server.
Double-Take7.0 is interoperable back to version 5.3 for Windows servers and 6.0 for Linux servers but is restricted to the following limitations. The Double-Take 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.3 console—Supports 5.3 source and target, but does not support 6.0 or 7.0 source or target
6.0 console—Supports 5.3 or 6.0 source and target as long as the target is the same or newer than the source, but does not support 7.0 source or target
7.0 console—Supports 5.3, 6.0, or 7.0 source and target as long as the target is the same or newer than the source
Check the requirements for each individual job type for specific upgrade and console configurations.
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 on a Windows multi-node cluster. If both your source and target are clusters, use the following procedure on the target cluster first, then on the source. If you are protecting Hyper-V virtual machines at the host-level using a cluster configuration, you cannot upgrade. You must delete the existing job, upgrade all of your nodes, and then re-create the job.
Move all cluster resources to one node.
Upgrade to the new version of Double-Take on all of the other nodes.
Move the cluster resources to one of the upgraded nodes.
Upgrade to the new version of Double-Take on the last node.
If needed, move the cluster resources to the desired nodes.
Use the following procedure to upgrade Double-Take on a Windows single-node cluster. If both your source and target are clusters, use the following procedure on the target cluster first, then on the source.
Take your cluster resources offline.
Upgrade to the new version of Double-Take.
After the upgrade is complete, bring the resources back online.
If you are upgrading and are currently using the GeoCluster Replicated Disk as the quorum resource, you will need to select another quorum resource before upgrading. See Configuring a cluster for GeoCluster 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 upgraded the guest Windows operating system on a Hyper-V virtual machine that you intend to protect at the guest level, you must also upgrade Integration Services on that virtual machine.
Related Topics