New features and enhancements
The following table lists the new features and enhancements for inSync On-premise 5.4.1.
|High performance backup for Mac endpoints||FSEvents (File System Events API in Mac OS X) integration to detect incremental changes to file, minimizing system resource usage by up to 40%.|
|inSync and MobileIron AppConnect Partnership|| |
Easier administration and deployment of inSync: IT admins can now provision the inSync mobile app on endpoint devices quickly with auto-configuration of inSync Master parameters to simplify the end-user experience.
Enhanced security for endpoint devices: PIN and encryption of data, enabling or disabling copy, paste, and print functionality, restricting open-in with whitelisting functionality to other apps, and de-provisioning of the inSync mobile app.
|Easier administration and deployment of inSync||IT admins can now provision the inSync mobile app on endpoint devices quickly with auto-configuration of inSync Master parameters to simplify the end-user experience.|
|Enhanced security for endpoint devices||PIN and encryption of data, enabling or disabling copy, paste, and print functionality, restricting open-in with whitelisting functionality to other apps, and de-provisioning of the inSync mobile app.|
|Time-based file locking|| |
File locking is a mechanism that restricts share users from simultaneously editing the same shared files to prevent file conflicts.
Users can exclusively edit a file for a duration of time to avoid file editing conflicts, while also providing a mechanism to ensure locks are removed so other collaborators can efficiently edit shared content when needed.
|Enhanced Data Loss Prevention (DLP)||Encryption of shared folders and workspaces, resulting in an additional layer of protection for confidential enterprise data on endpoints.|
|Greater control over data restores and share for inSync Private Cloud||Enforcing user authentication for data restores and share, results in an additional layer of protection for confidential enterprise data on endpoints. The inSync administrators can make it mandatory for users to provide their inSync account credentials when they restore data by using the inSync client or share a file or folder from their inSync Share folder.|
|User data privacy||The user data privacy feature is enhanced to ensure that when administrator access to user data is disabled, the administrator cannot: |
|Improved end-user experience|| |
|Enhanced sharing permissions||Workspace owners can provide expanded responsibilities to collaborators to become co-managers, distributing the day-to-day management of workspaces and providing more defined roles to other users: manager, editor, or viewer.|
|Configure the maximum file upload size for Share||The inSync administrators can now configure the maximum size for the file that users can upload to inSync Share by using the inSync Web. The maximum size that you can configure is up to 1000 MB.|
|AD import UI scalability||A new tab, Selected Users is added to the Import Users Now window. Under this tab, you can view all the users that you have selected to import from the Active Directory. The count for users selected to import from AD appears next to the Selected Users tab. The inSync administrators can easily remove users that they do not want to add to the inSync Master.|
|Enable a user or a user device||For improved performance and scalability, when the inSync administrator disables a user or a user device, the inSync Cloud now checks for updates on the user or user device status every 30 minutes instead of every minute. Therefore, the inSync client can take up to 30 minutes to perform the manual backup, scheduled backup, restore, auto-upgrade, decommission, and sync operations after the user or the user device is enabled. Users can continue to use inSync Web for downloading their backup data and for collaborating with other users.|
|Default profile optimized for faster and smoother backups||New options are added to the Default profile to ensure faster and smoother backups.|
Known issues and workarounds
The following table lists the known issues that exist in version 5.4.1.
The Watchdog service is not working for RHEL 7 and CentOS 7.
Unable to backup thunderbird email on Ubuntu 13.04.
inSync Cloud master services do not start automatically after restarting the server.
Workaround: Start the services manually after restarting the server.
|23903||Overlay icons appear fine in the Icon view. However, they do not appear in the Column view, List view, or Cover Flow view for MAC OS X 10.10.|
The inSync client Quick Start guide link opens the Quick start guide for an earlier version of inSync client.
Workaround: To view the inSync Client 5.4.1 Quick start guide, see http://docs.druva.com/005_inSync_Client/5.4.1/001_Quick_start_guides/Quick_Start_to_inSync_client.
If a user tries to create a Share link for a file before the file is completely synced, an "Access Denied" screen appears.
Workaround: Ensure that the file is completely synced before creating the Share link for the file.
Active Directory (AD) mapping does not work with an Integrated Mass Deployment (IMD) token for an AD that is configured on a global catalog (GC).
Workaround: Instead of putting users from all the domains in a single universal group, create groups in each subdomain.
When using a NAS storage that is accessible through an AD user, after upgrading the storage node from 5.3.1 to 5.4, the administrator needs to manually set the AD user permission for the config folder in order to start the storage node.
On Mozilla Firefox 29, if the Profile page has more than 12 profiles, administrators are unable to open a specific profile page. After refreshing the page, a blank Dashboard page appears.
The following table lists the issues fixed in version 5.4.1.
When you have more than 20,000 users or devices that use inSync, you might not be able to view or download the Complete Report report type on the inSync Master Management Console.
On a Linux server, the administrator cannot set the Web restore port number to a port number that is less than 1024.
When a user belongs to an organization unit (OU) with unicode characters in its name in the Active Directory (Active Directory), the MAC device activation by using integrated mass deployment (IMD) fails.
Instead of the license key, the CPU ID appears in various places, such as the license expiry alert email, the License Information section in the Complete Report, and in the serverinfo file.
After an inSync Server backed up using Microsoft NTBackup is restored, all devices associated with the storage on the server are expected to backup all files from the backup folders. However, for performance optimized storage, backup from devices fail.
The first backup after restore check on a device should be a full backup if any file fails to restore. However, for devices backing up to a performance optimized storage, only files that failed to restore are backed up.
When browsing through a snapshot, if a folder contains more than 10,000 files, the inSync interface stops responding.
If the administrator activated the inSync client by using an authkey, optimized PST backup from Outlook (MAPI backup), backup of encrypted files, and syncing of encrypted files fail.
Integrated mass deployment fails for users with Unicode characters in their name.
When the administrator views data for a user that is on legal hold by using the WebDAV data access URL, an incorrect timestamp appears for some files or folders.
|26950||Default storage created by using the wizard sets the compaction to a 1-hour window for daily and weekly compaction.|
|23482||When office files are configured for backups, inSync should add default visio files extensions in the inclusions.|
(Mac only) inSync is trying to back up the symbolic link and is trying to look for the actual data. If the actual data, does not exist, the backup fails with the following error:
No Permission to read file/folder.
|27485||Users present in the AD group imported from AD to inSync do not get listed.|
|26815||When a user does not have any device activated, after the compaction schedule, an alert appears informing that the Share device compaction failed. The alert does not clearly state that the failure occurred because the user does not have any device activated.|
|28103||Backup data goes to the secondary storage instead of the primary storage.|
|27922||Old alerts are appearing for a few clients.|
Backup of reparse points (Windows) for LFO sync generated the following error:
'int' object is not iterable.
|28253||The legal admins were receiving weekly reports that they did no not request for or subscribe to.|
|28126||The Download and Install Edge Server link points to an incorrect URL.|
The Configuration Wizard (on Linux and Windows) has a hard limit of 100 parallel connections for the Storage. After you complete the Configuration Wizard steps, you can edit the connections to any value more than 100.
|27170||The inSync client was not properly handling case-sensitive cross, cyclic renames.|
After upgrading to inSync 5.4, the log on credentials disappears from storage node service.
|26461||Unable to use PAC file for proxy settings.|
|27783||Outlook All PST is not backing up attached PST files in custom locations.|
|23408||At times, the Administrator cannot open the Profile Details page when the storage is unhealthy.|
Users cannot open shared links after the inSync Master is upgraded to 5.4.
The automatic sync process for users disabled in the Active Directory fails.
The legal administrator login fails with the following error; Access denied. The legal administrator is unable to perform any action in the inSync Master Management Console.
|23390||When users activate the inSync client, the activation details are saved in the Registry Editor.|
|24720||The reports on device backup display incorrect values.|
|27002||When you update a profile, the inSync Master does not save files or file extensions that you include for backup for the Lotus Notes email client on Windows.|
When you upload a certificate from a Trusted CA on the Edge Server, the backup operation fails with the following error: Unable to connect.
When you remove the Trusted certificate and upload the self-signed certificate, the backup operation starts without any issues.
|27682||The Reply to address for the inSync administrator does not get updated in the inSync Master Management Console.|
|26565||Incorrect modified date for the backup folders appears in the snapshot.|
|26334||When you update a profile, the inSync Master does not save files or file extensions that you include for backup for the Lotus Notes email client.|
The inSync client activation fails with the following error:
Server not reachable.
|25537||When you disable a user, the count for users configured for backup on the Dashboard page is not updated.|
|22000||Integrated mass deployment for Mac clients fails when you add an extra line in the inSyncConfig.ini script.|
|25115||An incorrect message, "Failed to upload, try again" appears after users upload files to inSync Share when using Internet Explorer 9.|
When you run the insync-config.sh script to create the first inSync administrator on Linux, the operation fails.
|24441||The Antivirus installed on user laptops identifies the Python version as insecure.|
The revision numbers of the installers for inSync On-premise 5.4.1 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 Master|| |
|inSync Storage Node|| |
|inSync client|| |
|inSync Edge Server|| |
Upgrade from earlier versions of inSync
If you are using inSync On-premise 5.4, you can directly upgrade to inSync On-premise 5.4.1. If you are using any other version of inSync On-premise, you must first upgrade to inSync 5.4, and then upgrade to inSync 5.4.1.
Note: For upgrade assistance from the Enterprise or Professional editions to the Private Cloud edition, contact Druva Support.