Skip to main content
Druva Documentation

Release Notes

What's new in 5.2.2

Druva is excited to announce the release of version 5.2.2 of inSync Private Cloud, industry’s best endpoint backup solution.

Release Highlights

Improved restore performance Version 5.2.2 greatly enhances user experience during restores. Depending on your inSync configuration and type of data, you can see a dramatic increase in the speed of restores. 

Known issues and workarounds

This section contains a list of known issues for Druva inSync Private Cloud 5.2.2. 

Tracking ID Description
21017 After you upgrade to inSync Private Cloud 5.2, the auto-delete functionality cannot be put on hold for iOS and Android devices.
20840 If you customize the help link while co-branding inSync Client, the default help links on inSync Web do not change.

Downloads initiated from inSync Web opened in Internet Explorer do not complete if the Storage Node addressing download requests is installed on Microsoft® Windows 2012. 


To download shared folders, open inSync Web using Google Chrome or Mozilla Firefox. 
20970 inSync Client installed on Mac 10.7 and 10.8 might crash while a backup is in progress. This issue is observed only if share is enabled. 
22625 You cannot email Analytics results that contain more than 15000 records.
22820 Restores initiated by administrators to user devices will fail if inSync client on the device is upgraded when the restore is in progress. The issue is observed if inSync client prior to version 5.2 is upgraded.

Fixed issues

This section contains a list of issues fixed in version 5.2.2 of inSync Private Cloud.

Tracking ID Description

When you attempted to launch inSync client, the following error was displayed:

Could not connect to inSync service
21467 The Active Alerts list was not purged after resolving alerts. 
21334 After the first seeding job from a secondary storage to a primary storage was complete, the value displayed for "Disk space savings" of the secondary storage was negative. 
20278 While installing inSync Master Server or Storage Node on Red Hat Enterprise Linux (RHEL) 6, a bad file descriptor error appeared on the RHEL 6 terminal.

After upgrading to version 5.2, the pre-upgrade share activities and global activity stream were not displayed on the inSync Admin Console.

On inSync Web, share activities before the upgrade were not displayed.
19148 If a Storage Node stopped responding, pending backup request entries appeared on the Live Activities page of the inSync Admin Console. These entries were purged after the Storage Node resumed backup operations. 

inSync Client, when opened on a Mac computer, obscured other applications that are running. 


20595 When you configured a folder for backup from the inSync Admin Console, the default list of extensions for office files did not include .dotx and .xltx (template files for MS Word and MS Excel respectively). 



The status of restore requests initiated by users from inSync Web appears as “failed” even if the restore completed successfully. This issue was observed when inSync clients of a version earlier than 5.2 initiated restore requests.


Upgrade to the most recent release of inSync client.

Revision information

The revision numbers of the installers for inSync Private Cloud 5.2.2 are listed in the following table. The revision number is a part of the installer name. Use the revision number to ensure that you have the correct installer.


Product Revision
Master server and storage node
  • Windows: r20256
  • Linux: r20254
inSync client
  • Windows: r20208
  • Linux: Not available
  • Mac: 20149

Upgrade matrix

If you have an existing installation of inSync Private Cloud, you can upgrade to version 5.2.2. Use the revision numbers listed in the table to identify if your current installation can be upgraded to version 5.2.2. 

Upgrade from Revision (Windows) Revision (Linux)
5.2.1 r18797 r18745
5.2 r17937 r17937
5.1.1 r15103, r15393 r15103
5.1 r14700, r13720 N.A.
5.0.1 r10605 N.A.
Note: If you are upgrading from version 5.2 or later, just install the latest version over the existing installation. If you are upgrading from a version prior to 5.2, you must first uninstall the old version of the product and then install the latest version. After uninstalling the old version, do not delete the configuration files.
  • Was this article helpful?