New features and enhancements
The following table lists the new features and enhancements for inSync On-premise 5.4.
Persona backup enhancements
|Data governance|| |
|Efficient administration|| |
|Greater control over collaborative data|| |
|Improved data share experience|| |
|Improved end-user experience|| |
Known issues and workarounds
The following table lists the known issues that exist in version 5.4.
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.
If you are using Firefox 29, when you have more than 12 profiles, the Manage Profiles page does not display any information.
Workaround: Use any browser other than Firefox.
On a Linux server, the administrator cannot set the Web restore port number to a port number that is less than 1024.
Workaround: Set the Web restore port number to a port number that is greater 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.
Workaround: Add the same user to a non-unicode OU, and then activate the device by using IMD.
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.
Workaround: Contact Druva support to obtain your new license.
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.
Workaround: None. If you want to restore a file from within the folder containing large number of files, restore the folder without browsing through it.
Sometimes, the profile details pages do not appear if a storage is unhealthy. This is a rare occurrence.
|22439||Multiple versions are backed up for files with .eml extension stored in the inSync Share folder even if no changes are made to them. The Windows Search Service causes this issue. |
Workaround: Disable Windows Search Service or turn off Windows Indexing on the Windows computers where inSync client is installed.
On OS X Mavericks, overlay icons in inSync Share do not appear in the list view.
If users and groups belong to different domains during AD mapping, the Integrated mass deployment fails.
Workaround: Instead of putting users from all the domains to a single universal group, create groups in each subdomains.
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..
Workaround: Restart the inSync client service after activating the client using authkey.
Integrated mass deployment fails for users with Unicode characters in their name.
inSync Web becomes unresponsive when the user is browsing through a restore point that has more than 50,000 files.
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.
The following table lists the issues fixed in version 5.4.
Even after you enable password policy for inSync users, simple passwords that do not adhere to the password policy can be used for inSync clients on Linux computers.
|26329||inSync consumes more bandwidth for backup opertations than the limit set by the inSync administrator.|
In the German edition of the inSync client, the sync status on the UI appears in English.
If the size of the secondary storage is more than the primary storage, backup to the secondary storage continues even if it is full.
After upgrading from inSync Private Cloud 5.1.1 installed on Ubuntu Linux, inSync Master Management Console is not accessible.
If you update the port number of a storage node by using the inSync Master Management Console, the port number is not updated in the configuration file.
After upgrading to inSync Private Cloud 5.3.1, sharing with guest users fails.
Profile administrators cannot view the Storage Pool Details page.
On Linux and Mac computers, restore for some special files (such as socket and symbolic link) did not complete.
|21543||When you rename or move any folder in inSync Share while it is being synced, an empty folder with the old name is retained in the inSync Share folder.|
|24902||Files created by using the BarTender software failed to open from the inSync Share folder.|
|26061||When editing Windows Journal application files (JNT), they disappear from the inSync Share folder.|
|25756||Files created by using the KeePass software used to get automatically deleted from the inSync Share folder.|
|25623||Due to various reasons, clients would randomly get disconnected and backups would fail.|
|24700||The CPortal page takes more than 20 seconds, sometimes up to 2 minutes, to load.|
|24585||Profile configuration does not retain platform-specific changes. This issue occurs while saving changes to a Mac profile when the profile also has something configured in the Windows section. Changes to the Mac section's exclude files or include files are not saved even after multiple attempts.|
The FSCK script fails with the following error:
AttributeError: BlkStor instance has no attribute 'blk_getref'
|25271||Incorrect statistics appear in the Bytes Transferred and Time Taken columns of the Roll Out report.|
The Manage Users page does not display users who have 0 devices when you sort the content according to devices or quota.
|24260||Unable to move users from one storage to another when share data is associated with the user.|
The first backup after the activation of the inSync client fails with network errors.
|24248||On the Data Analytics page, # Files By Sizes displays some incorrect statistics.|
The Mobile Credentials tab contains a broken link.
|25129||When you do not import users from AD and you add them manually or by using a CSV file, if you want to enable Active Directory authentication for these users, you need to add the AD user name manually.|
The revision numbers of the installers for inSync On-premise 5.4 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|| |
If you are using inSync Enterprise or inSync Professional 5.3.1, you can directly upgrade to inSync 5.4. If you are using any other version of inSync Enterprise or inSync Professional, you must first upgrade to inSync 5.3.1, and then upgrade to inSync 5.4.
If you are using inSync Private Cloud 5.2 or later, you can directly upgrade to inSync 5.4. If you are using a version of inSync Private Cloud that is earlier than 5.2, you must first upgrade to inSync 5.3.1, and then upgrade to inSync 5.4.
|inSync Edition||Upgrade From||Revision (Windows)||Revision (Linux)|
|inSync Professional||5.3.1||r22685, r23138||r22679, r23147|
|inSync Enterprise||5.3.1||r22685, r23138||r22679, r23147|
|inSync Private Cloud||5.3.1||r22887, r23364||r22887, r23365|
Note: For upgrade assistance from the Enterprise or Professional editions to the Private Cloud edition, contact Druva Support.