What's new in 5.2.2
Druva is excited to announce the release of the Enterprise edition of version 5.2.2 of Druva inSync, industry’s best endpoint backup solution.
|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 5.2.2.
|21039||When you share folders from inSync Share, reboot your computer and right-click the inSync client icon, the most-recent share updates are not reflected.|
|20840||If you customize the help link while co-branding inSync client, the default help links on inSync Web do not change.|
|18598||The synchronization of inSync Share fails if users exceeds quota. However, inSync client displays the share status as “Sync Completed”.|
|21013||If restores initiated by a user and administrator to the same device complete at the same time, inSync does not capture the details of the restores.|
|21407||inSync client cannot access inSync Web over WAN.|
|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.|
This section contains a list of issues fixed in version 5.2.2 of inSync Enterprise.
While launching inSync client, the following error was displayed:
Could not connect to inSync service
|21999||After upgrading from inSync 4.5.1, live activities of the type "restore check" appeared pending.|
|21467||The Active Alerts list was not purged after resolving the alerts.|
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).
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.
After upgrading inSync Client to version 5.2, the existing folders in the inSync Share folder appeared in the ‘Syncing’ state for a long time.
inSync Client, when opened on a Mac computer, obscured other applications that were running.
|21692||After upgrading to version 5.2.1 from version 4.5.1, at least one of the existing storages appeared “Unhealthy”. This happened only when a new storage was created after upgrade.|
|21445||After you upgraded to inSync 5.2, BMR license under License Summary appeared as "Available".|
The revision numbers of the installers for inSync 5.2.2 Enterprise edition 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.
|inSync server|| |
|inSync client|| |
If you have an existing installation of inSync Enterprise edition, you can upgrade to inSync 5.2.2. Use the revision numbers listed in the table to identify if your current installation can be upgraded to inSync 5.2.2.
You can upgrade from an earlier version of inSync Professional to inSync Enterprise 5.2.2. However, you cannot upgrade from an earlier version of inSync Enterprise to inSync Professional 5.2.2.
|Upgrade from||Revision (Windows)||Revision (Linux)|
|5.1.1||r16045, r15483, r15096, r14647||r17692, r15483, r15114, r14650|
|5.1||r13854, r13450, r12871||r13854, r13450, r13197|
|5.0.1||r12649, r11506, r10795, r10605, r10415, r10224||r11513, r10799, r10608, r10417, r10227|
|5.0||r9246, r9092||r9248, r9094|
|4.5.1||r14039, r11893, r10355, r9926, r8795, r8548, r7787, r7493, r7420||r14042, r11894, r10370, r9927, r8797, r8555, r7789, r7529, r7423|
|4.5||r7126, r6986||r7128, r6987|