Skip to main content
Druva Documentation

Release Notes for inSync Cloud 5.8

What's new in 5.8?

In keeping with the high standards of user and administrator experience, inSync 5.8 design fosters an intuitive experience for administrators to better manage and deploy inSync and monitor for non-compliance in emails (MAPI and Office 365 Exchange online). Furthermore, inSync 5.8 also simplifies the process of sharing files for easier collaboration amongst end-users and provides granular controls to manage the sharing of information while reducing on bandwidth and storage consumption.

inSync Server 5.8 update:

inSync Client 5.8 updates:

Email (MAPI and Office 365 Exchange Online) Automated Compliance Management 

inSync’s Proactive Compliance feature, powered by full-text search capabilities and built-in compliance templates (For example, HIPAA, GLBA, PHI / PII related), now monitors for sensitive information and potential data risks in the email body, subject, and attachments to easily meet data regulations. inSync displays emails in the EML file format in the Compliance Dashboard, provides granular information on the data infraction, and enables IT to download emails for offline review. 

For more information, see About inSync Compliance.

IPv6 Support

With the advent of IPv6, an internet protocol, many organizations have started planning for IPv6 support and are increasingly looking for applications to support IPv6. inSync 5.8 now supports IPv6 and it enables customers to use inSync over Microsoft DirectAccess. For more information, see inSync IPv6 Support

New Sync & Share Capabilities

inSync 5.8 Sync and Share for Enhancements:

Collaborating with users within and outside the organization just got easier with inSync Share! 

  • inSync 5.8 enables users to quickly share links to files and folders through a single step process. To enhance the collaboration experience, inSync 5.8 now enables email IDs to auto populate and allows users to add any context around the link (to the file or folder) they are sharing. 

    For more information, see Create and share a link.

  • Selective sync provides more granular controls for end users to choose which folders or subfolders they want to sync to their device. In doing so, end-users gain more flexibility and control over the information that gets synchronized and thereby allows them to save on storage (minimize disk utilization) and bandwidth consumption. 

    For more information, see Select a specific folder for sync.

Patch Update

Patch update is released to address various issues related to the product. Following table lists the issues that were fixed as part of patch update:

Fixed issue Released on Description
37519 August 06, 2016

This patch is available for the following issues.

  1. DLP on Mac Client 5.8 was failing due to changes made for FIPS:
    To enable FIPS changes, SSL was disabled. Hence even with Device Trace enabled, location on all devices was always displayed as "unknown".
  2. inSync Client auto-upgrade from 5.5 to 5.8 patch failed on MAC 10.10: 
    When customers tried to auto-upgrade inSync Client from version 5.5 to 5.8 on MAC 10.10, the inSyncDecommission process failed to start the inSyncDaemon server. This was because the older inSyncDecommission process although killed, was still bound on the sync-port.
  3. Clicking on Browse on inSync web for Folders, opened the Manage Collaborators folder instead:
    When customers clicked on 'Browse on inSync web for Folders', the Manage Collaborators' folder opened instead. This was because the integer (which denotes the operation name) passed from Finder plugin code to Syncer was incorrect.
  4. On MAC 10.10, inSync Client failed to launch after being deployed using IMD:
    When customers deployed inSync Client on MAC 10.10 using IMD, the Client user interface failed to launch automatically.
36574 May 28, 2016

inSync Mac Client 5.8 update: Auto-upgrade from inSync Client version 5.5 and earlier to version 5.8, required a device reboot post upgrade.

When customers initiate an upgrade of inSync Clients from version 5.5 or earlier, the Client might not start after the upgrade. In this case, the device needs to be restarted.

Deprecated feature

There is no deprecated feature in inSync 5.8.

Known issues and workarounds

The following table lists the known issues that exist in inSync 5.8.

Issue Description
36167 Profile administrator cannot cancel an ongoing restore operation for a user.

Context menu options in inSync Web do not work, if Restore Authentication and Geofencing policy are enabled simultaneously.


You can perform the required actions with the help of icons placed adjacent to the Share item.


Cannot back up Google Apps data from Google Drive and Gmail if inSync has exceeded Google's allowed API limit. inSync retries to process the API requests, and if unable to process the requests, then the backup operation fails.

Additionally, any of the following messages can appear:

  • 403 error: Could be encountered because of any of the following reasons:
    • Daily limit exceeded
    • User limit exceeded
    • Rate limit exceeded
  • 429 error: Too Many Requests


When you log on to inSync Web as a guest user with view permissions, the Delete option appears for any selected file. However, an error message appears when you attempt to delete the file.

30184 When an inSync administrator restores data for a user who is disabled in inSync, an incorrect error message “サーバと接続することができません。” appears on the Japanese inSync client.

When users uninstall the inSync client for Japanese, the Repair or Uninstall window appears in English.

29124 When users uninstall the inSync client from their laptops and choose not to retain inSync settings for future use, the Uninstalling Druva inSync 5.4.2 message appears in English.

Fixed issues

The following table lists the issues fixed in inSync version 5.8.

Issue Description
32625 Share DB files were corrupted leading to backup failure.

An inconsistent Restore activity completed email message was sent to inSync administrators in case of failed restores.

35625 An error was observed while saving proxy settings for inSync Client.

inSync could not backup up files from the My Documents folder, which was moved to another location, leading to generation of Misconfigured Folder alert.


inSync did not backup up all the files in incremental backup cycles, if the folder was renamed after a change occurred in the folder.

35117 Changes were missed during incremental backups if an administrator configured Share had junction point or symbolic link in its path.
35913 Alert message was not sent if the body of the message had unicode content in it.
32214 Flash parameter AllowScriptAccess was set to value Always
32154 Replaced Adobe Flash Player in inSync with other compatible technology.
34776 On sharing a link with other users using inSync Share, email message displayed inSync Username in the FROM field leading that message to the Spam folder.
30798 Provide built-in CA certificates for inSync CloudCache Server.


Previously, an inSync administrator could decommission devices of deleted and disabled users. 

Could not access WebDAV access URL if the legal hold policy name had special characters. 

36544 CSV report got generated and emailed although timeout error was displayed on the inSync Master Management Console. 
36207 Bulk export functionality does not work, and fails with an internal error.

Revision information

The revision numbers of the installers for inSync Cloud 5.8 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
inSync Client
  • Windows: r44506
  • Mac: r44798
  • Linux: r33966

Note: Druva has not released new version of inSync Client for Linux OS with inSync 5.8. You can continue using inSync Client 5.5 for Linux with inSync Cloud 5.8.

inSync AD/LDAP Connector
  • Windows: r42608
inSync CloudCache Server
  • Windows: r42608