You can enable notifications in inSync to notify or alert users about the activities performed by the inSync client on their computer. It helps users to know the status and the operations performed by the inSync client.
Note: You can enable inSync notifications through profiles. You cannot do this on an individual user level.
To enable inSync notifications
- Login to the inSync Management Console.
- On the inSync Management Console menu bar, click Profiles.
- Click the profile for which you want to enable inSync notifications.
- Click the Devices tab > User Settings, click Edit. The Edit Profile window appears.
- If you want to display inSync icon on the system tray, select the Show inSync icon in system tray checkbox.
- If you want to display inSync notifications on the user devices, select the Notification Shown on Devices as applicable.
You can configure the Notification types, however, the Notifications will be displayed on user devices only with the upcoming inSync Client v6.7.0. For more information, contact Druva Support.
Critical notifications appear when inSync fails to initiate backup operations. These notifications require the user's immediate attention and action by the inSync administrator.
High notifications appear when inSync backups are interrupted or affected. These notifications require recommended actions by users to allow inSync to resume normal operations.
Warning notifications appear when inSync operations are temporarily affected due to connection errors or OS errors. These notifications may require users' actions to allow inSync to resume normal operations.
Informative notifications appear to provide additional information on the ongoing and completed backups. These notifications are informative and may not necessarily require users' actions.
- Click Save.
Notifications displayed by inSync client
The following table lists the notifications that appear every time inSync client performs any operation on the user computer.
|Backup started||Specifies that inSync client has started performing backup operation on the computer. If the backup has started on network with 24 bit subnet mask or more, then the inSync administrator can block the network from backing up data.||Informative|
|Insufficient Storage||Specifies that either the user quota is full, or the server storage space is full.||Critical|
|Authentication Error||Specifies that the device cannot be authenticated with inSync Server. This notification is displayed when the device is deleted or decommissioned, or when the user/device is disabled from inSync.||Critical|
|Configuration Error||Specifies that the device's operating system does not trust inSync Server's security certificate. This notification is displayed when the client certificate is invalid during backup activity, or when you trigger the backup of a user's data and immediately migrate the storage of that user.||Critical|
|Backup Incomplete||Specifies that the backup had started but failed because of the operating system's internal errors. For example, Microsoft VSS error.||Warning|
Specifies that the backup operation was interrupted. This notification is displayed in any of the following situations:
|Backup Canceled||Specifies that a running backup operation was canceled either by the inSync user or the inSync administrator.||Warning|
|Device Not Backed Up||Specifies that the device is not backed up for at least 7 consecutive days.||High|
Specifies that the backup is completed.
|No Folders To Backup||Specifies that there were no folders configured when the last backup was triggered.||High|
MAPI based email backup error notifications
If configured, inSync Client users can view the MAPI based email backup status below the Backup Completed Notification.
- Email backup using MAPI sub-status notifications listed here appear only if the Backup Completed notification is displayed on the inSync Client and if there is any MAPI based email backup error notification.
- If any other notification is displayed and Email backup using MAPI sub-status notification is also generated, MAPI based error notifications are not displayed.
|Errors observed during Outlook Backup.||
Specifies that inSync Client completed email backup using MAPI on the user device, but with some errors.
|Errors observed during Outlook Backup. <StoreName> skipped.||
Specifies that inSync Client completed email backup using MAPI on the user device. However, inSync skipped a message store because inSync could not open or read it on the user device.
|Errors observed during Outlook Backup. <FolderName> from <StoreName> skipped.||
Specifies that inSync Client completed email backup using MAPI on the user device. However, inSync skipped a folder in a message store because inSync could not open or read it on the user device.
|Errors observed during Outlook Backup. Could not open message store <StoreName>.||
Specifies that inSync Client could not perform email backup using MAPI, due to an issue while opening or reading a password protected PST message store on the user device.
|Errors observed during Outlook Backup. PST file could not be located for <StoreName>.||
Specifies that inSync Client could not perform email backup using MAPI, as inSync could not locate PST message store on the user device.
|Errors observed during Outlook Backup. <StoreName> is corrupt.||
Specifies that inSync could not perform email backup using MAPI, because the PST message store on the user device is corrupt.
|Errors observed during Outlook Backup. <StoreName> is not accessible.||Specifies that inSync could not perform email backup using MAPI, because inSync does not have permissions to access the PST message store on the user device.|
|Outlook backup failed due to insufficient system resources.||Specifies that inSync could not perform email backup using MAPI, because of insufficient system resources on the user device.|