Open topic with navigation
Installation and upgrade notes
Review the following installation and upgrade notes before beginning your installation or upgrade.
- Since Double-Take RecoverNow 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 RecoverNow 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 RecoverNow installed, you must remove Double-Take RecoverNow prior to the operating system upgrade. Uninstall Double-Take RecoverNow, perform the operating system upgrade, and then reinstall Double-Take RecoverNow.
- 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 450 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 RecoverNow installation directory. This program can be run to collect configuration data for use when reporting problems to CustomerCare. It gathers Double-Take RecoverNow log files; Double-Take RecoverNow and system registry settings; network configuration information such as IP, WINS, and DNS addresses; and other data which may be necessary for CustomerCare to troubleshoot issues. After running the executable, a zip file is automatically created with the information gathered.
- Double-Take RecoverNow 5.3 can interoperate back to version 5.1 but is restricted to the following limitations. The Double-Take RecoverNow 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
- The application consistency feature for snapshots requires that the source and target be running version 5.3.
- When performing a rolling upgrade, update the target server first. After the upgrade is complete, any sources will automatically reconnect to the target. Upgrade the source(s) when convenient.
Related Topics