Skip to main content

 

Druva Documentation

About the inSync Client upgrade

Overview

With every release, Druva introduces new features and improvements, and periodic security fixes. An upgrade is recommended to ensure that devices are running on the latest version and have access to the latest release. Using the latest version, you can take advantage of fixes and avoid issues that have already been corrected, and ensure that the devices are running smoothly. 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.

Download the inSync Client

For details about the download link to the latest version of the inSync Client, see Download Links

Supported upgrade options for the inSync Client

Druva provides different options to upgrade the inSync Client on devices. Along with the option to upgrade the device to the latest release version, the devices can be upgraded to the previous release, hotfix, or Early Access release. These options are simple to run and depending on the requirement or on the number of devices that need an upgrade, you can select any of the following options:

  • Autoupgrade - This option enables you to automatically run the upgrade process for all devices that need an upgrade, wherein, all the devices automatically to the latest version. A Cloud administrator can enable this setting from the inSync Management console by navigating to  icon settings.png > Settings > Deployment. Once this setting is enabled, all existing upgrade processes (manual or bulk) will be aborted, and devices that are scheduled for an upgrade will be automatically upgraded in the upgrade cycle that starts at 10:00 am UTC every day. To stop the autoupgrade cycle, you can disable the setting. For more information on how to enable an autoupgrade, see Upgrade the inSync Client.
  • Bulk upgrade - This option enables you to upgrade multiple devices in a bulk. With this option, you can leverage the available filters to view the list of devices to be upgraded based on the client version, device OS, profile, or storage. In addition, you can select the version to which the devices must be upgraded to;  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 if only a manageable number of devices need an upgrade or if a new client version needs to be tested on a few select devices before upgrading 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.0.1:

Operating System From To

inSync Client for Windows

  • 5.5
  • 5.6
  • 5.7
  • 5.8
  • 5.8.1
  • 5.9
  • 5.9.5

6.0.1

inSync Client for Mac

  • 5.5
  • 5.6
  • 5.7
  • 5.8
  • 5.9
  • 5.9.5
  • 6.0.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