Open topic with navigation
Installation notes
Review the installation notes below before beginning an installation or upgrade.
- Requirements—Although the installations are shared between Double-Take products, the requirements for each Double-Take product and each job type within each Double-Take product are unique. Be sure and review the requirements for your product and job type in that product's User's Guide or in the Double-Take Console help.
- Operating system 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. Also, if you have upgraded the guest Windows operating system on a Hyper-V virtual machine that you intend to protect at the guest level or to migrate, you must also upgrade Integration Services on that virtual machine.
- Windows 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.
- Version interoperability—Double-Take has different interoperability requirements for different products.
- Double-Take Move—This product is not interoperable between versions. Each source, target, and Double-Take Console must be running the same version of Double-Take Move.
- Double-Take Availability—Version 7.1 is interoperable back to version 6.0 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.
- 6.0 console—Supports 6.0 source and target, but does not support 7.0 or 7.1 source or target
- 7.0 console—Supports 6.0 or 7.0 source and target as long as the target is the same or newer than the source, but does not support 7.1 source or target
- 7.1 console—Supports 6.0, 7.0, or 7.1 source and target as long as the target is the same or newer than the source
- Double-Take Console—Options available in a newer console will not be functional when creating jobs for servers running older versions.
- Upgrades—Keep in mind the following caveats when upgrading.
- Rolling upgrade—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.
- Chained upgrades—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.
- Restore and reverse—If you are using a configuration where the source is an older version than the target, you will not be able to restore or reverse 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 or reversing.
- Agentless Hyper-V jobs—If you are upgrading an agentless Hyper-V job on a cluster configuration, you cannot upgrade. You must delete the existing job, upgrade all of your nodes, and then re-create the job.
- Clusters—If you are upgrading from 7.1.x, there are no upgrade restrictions for a cluster. If you are upgrading from 7.0.x or earlier, you must use one of the following procedures to upgrade Double-Take.
- Multi-node clusters—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 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.
- Single node clusters—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.
- GeoCluster—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.
