Installation and upgrade notes

Review the installation notes below before beginning an installation or upgrade.

• Requirements—Although the installations are shared between Carbonite Availability and Carbonite Move products, the requirements for each Carbonite Availability and Carbonite Move product and each job type within each 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 Carbonite Replication Console help.
• Prerequisites—Installation prerequisites depend on your operating system.
  • Windows—The Carbonite Availability and Carbonite Move Windows installation will automatically install the following software, if they are not installed already.
    • Microsoft .NET 4.5.1 Full Setup—This package is installed on all supported Windows operating systems.
    • Visual C++ 2013 Runtime—The 12.0.21005 version (x64 or x86 version) of this package is installed on all supported Windows operating systems.

  • Linux—Each Linux server must have the following packages and services installed before you can install and use Carbonite Availability and Carbonite Move. See your operating system documentation for details on these packages and utilities.

    • sshd (or the package that installs sshd)
    • parted
    • /usr/bin/which
    • /usr/sbin/dmidecode
    • /usr/bin/scp (only if you will be performing push installations from the Carbonite Replication Console to your Linux servers)
    • /lib/lsb/init-functions (only if you are installing on Red Hat, Oracle Enterprise Linux, CentOS, or SUSE)
• Operating system upgrade—Because Carbonite Availability and Carbonite Move have operating system dependent files, if you are upgrading your operating system (to a new major version, not a service pack) and have Carbonite Availability and Carbonite Move installed, you must remove Carbonite Availability and Carbonite Move prior to the operating system upgrade. Uninstall Carbonite Availability and Carbonite Move, perform the operating system upgrade, and then reinstall Carbonite Availability and Carbonite Move. Also, if you have upgraded the guest Windows operating system on a Hyper-V virtual machine that you intend to protect or migrate, you must also upgrade Integration Services on that virtual machine.
• Windows servers—The following notes are specific to Windows servers.
  • Since Carbonite Availability and Carbonite Move install 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 Carbonite Availability and Carbonite Move. 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—Carbonite Availability and Carbonite Move have different interoperability requirements for different products.
  • Carbonite Availability—Version 8.1 is interoperable back to version 7.1 but is restricted to the following limitations. The Carbonite 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.
    • 7.1 console—Supports 7.1 source and target, but does not support 8.0 or 8.1 source or target
    • 8.0 console—Supports 7.1 or 8.0 source and target as long as the target is the same or newer than the source, but does not support 8.1 source or target
    • 8.1 console—Supports 7.1, 8.0, or 8.1 source and target as long as the target is the same or newer than the source
  • Carbonite Move—Interoperability for this product is dependent on the type of job you will be creating.
    • Files and folders and full server jobs—These job types are not interoperable between versions. Each source, target, and Carbonite Replication Console must be running the same version of Carbonite Move.
    • Full server to ESX and full server to Hyper-V jobs—These jobs are interoperable between versions. Version 8.1 is interoperable back to version 7.1.2 but is restricted to the following limitations. The Carbonite Move 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.
      • 7.1.2 console—Supports 7.1.2 source and target, but does not support 8.0 or 8.1 source or target
      • 8.0 console—Supports 7.1.2 or 8.0 source and target as long as the target is the same or newer than the source, but does not support 8.1 source or target
      • 8.1 console—Supports 7.1.2, 8.0, or 8.1 source and target as long as the target is the same or newer than the source
  • Carbonite Replication 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.
  • 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.
  • Jobs no longer supported—Beginning with version 8.0, V to ESX and V to Hyper-V jobs will be upgraded to Full server to ESX and Full Server to Hyper-V jobs, respectively. You may want to check your job settings to confirm they are as expected after the upgrade. For example, the old job has virtual switch mappings while the new job will have NIC to virtual switch mappings.