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 backup 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.
- 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 Availabilityand 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.2 is interoperable back to version 5.0 but is restricted to the following limitations. The Double-Take Availability clients can only control the same or earlier releases. To accommodate rolling upgrades, older sources can connect to newer targets, but newer sources cannot connect to older targets. Configurations not listed in the following chart are not supported.
| Client |
Source |
Target |
Supported |
| 5.0 |
5.1 or 5.2 |
5.1 or 5.2 |
No |
| 5.1 |
5.2 |
5.2 |
No |
| 5.2 |
5.0 |
5.0, 5.1, or 5.2 |
Yes |
| 5.2 |
5.1 |
5.0 |
No |
| 5.2 |
5.1 |
5.1 or 5.2 |
Yes |
| 5.2 |
5.2 |
5.0 or 5.1 |
No |
| 5.2 |
5.2 |
5.2 |
Yes |
- 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.
- Move all cluster resources to one node.
- Upgrade to the new version of Double-Take Availability on all of the other nodes.
- Move the cluster resources to one of the upgraded nodes.
- Upgrade to the new version of Double-Take Availability on the last node.
- If needed, move the cluster resources to the desired nodes.
- If you have protected clusters with an earlier version of the Double-Take Availability Application Manager, you should disable protection before upgrading to this version of Double-Take Availability.
Related Topics