Skip to main content
Druva Documentation

About inSync Client upgrade

Overview

With every inSync Client release, Druva introduces new features, improvements to existing features, and has required fixes. inSync Client upgrade is recommended so that the user devices are running on the up-to-date inSync Client version and have access to the latest features. In addition, to receive continued support, it is mandatory to upgrade the inSync Client to a version that is supported as per the EOL policy.

Supported upgrade options for the inSync Client

Druva provides different options to upgrade the inSync Client on devices. Along with an option to upgrade user devices to the latest release version, the devices can be upgraded to one version below the latest release, hotfix, or an Early Access (EA) release. Upgrade is a simple process and depending on your requirement or on the number of devices that need an upgrade, you select any of the following options to upgrade the inSync Client:

  • Autoupgrade - This option enables you to automatically run the inSync Client upgrade process for all the devices that need an upgrade. All the selected devices are automatically upgraded to the latest inSync Client GA version. A Cloud administrator can enable the auto-upgrade setting from the inSync Management Console by navigating to  icon settings.png > Settings > Deployment. After auto-upgrade is enabled, all the existing upgrade processes (manual or bulk) are aborted, and devices that are scheduled for an automatic upgrade will be upgraded in the upgrade cycle that starts at 10:00 am UTC every day. To stop the auto upgrade, you can disable the setting. For more information on how to enable an auto upgrade, see Upgrade the inSync Client.
  • Bulk upgrade - This option enables you to upgrade multiple devices in bulk. You can leverage the available filters to view the list of devices and plan upgrade based on the inSync Client version, Device OS, Profile, or Storage. You can choose to upgrade the user devices to a particular available version for upgrade, viz. the latest version, previous version, hotfix, or Early Access release. To know how to run a bulk upgrade, see Upgrade the inSync Client.
  • Manual upgrade - This option enables you to select one or many devices manually for an upgrade. Even though it is a time-consuming task for the administrator and requires monitoring, this method is preferred only if a manageable number of devices need an upgrade or if a new inSync Client version needs to be tested on a few select devices before upgrading inSync Client all devices. Using this option, the devices can be upgraded to the latest version, previous version, hotfix, or Early Access release. To know how to manually upgrade devices, see Upgrade the inSync Client.

Upgrade Matrix

The following table displays the supported upgrade paths of the inSync products from the earlier release versions to 6.1.1:

Operating System From To

inSync Client for Windows

  • 5.9
  • 5.9.5
  • 6.0.1
  • 6.1.0

6.1.1

inSync Client for Mac

  • 5.9
  • 5.9.5
  • 6.0.1
  • 6.1.0

6.1.1

inSync Client for Linux

  • 5.9

N/A

Upgrade the inSync Client using native software management tools

If you plan to upgrade inSync Client on multiple devices using a software management tool used in your environment, ensure that the upgrade conforms to the following considerations:

  • Do not remove the configuration details and the inSync Share folder on the device while performing the upgrade.
  • Package the inSync Client installer appropriately for Windows and Mac deployments so that it correctly upgrades the respective inSync.msi and inSyncConfig.ini files.

Note: If you plan to perform integrated mass deployment (IMD)  to upgrade the inSync Client, ensure you upgrade your package to use the latest installers.

For more assistance in upgrading inSync Client on multiple devices, contact Druva technical support