The following table lists the notifications that appear on the desktop every time inSync Client performs an operation on the user 's desktop or laptop. The notifications are displayed only when the administrator has enabled Druva inSync notifications.
Druva inSync notifications are categorized as follows:
If your administrator has allowed you to modify notification settings, you can choose to select the type of notification you want Druva inSync to display on your device. To modify the Druva inSync notifications settings, refer Configure Druva inSync notification settings.
inSync Client Notifications
Following is the list of notifications displayed on your inSync Client interface. These notifications help you get information on important activities performed by inSync Client.
inSync Client status on Backup and Restore tab
|Icon||Client Status||Client Sub-Status||Description||Category|
|Authentication Error||Admin has deactivated the device. Please contact your IT administrator.||The device cannot be authenticated with Druva inSync Server. 432administrator has deleted or replaced the device from the inSync Management Console. To reinstate the device and resume backup through Druva inSync, contact your administrator.||Critical|
|Authentication Error||Admin has disabled the account. Please contact your IT administrator.||The administrator has disabled your Druva inSync user account or your device. To activate your user account, contact your administrator.||Critical|
|Backup Canceled||Canceled by the administrator.||The administrator has canceled an ongoing backup operation. Contact your Administrator before initiating a manual backup.||Warning|
|Backup Canceled||-||You have canceled an ongoing backup.||Informative|
|Backup Complete||Some files missed. Click details for more info||One of the following issues may have occurred:
|Backup Complete||-||All files were backed up successfully. No backup error or missed files were reported.||Informative|
|Backup Complete||Errors observed during Outlook Backup.||Backup of Outlook files failed or partially succeeded.||Warning|
|Backup in progress||Started today at <timestamp>||Displays the start time and the progress of the backup.||Informative|
|Backup incomplete||Backup interrupted due to error in Windows VSS service. Druva inSync will retry after some time.||The backup failed due to an internal error of the operating system. Microsoft VSS can be one of the reasons for the failure on a Windows device. Contact your Administrator if backups fail to complete after several retries.||Warning|
|Backup Interrupted||Backup disabled on <Network Name>. Druva inSync will retry after some time.||Backup is disabled on the network specified in the status message or on the network with 24-bit subnet mask and more. Connect to a different network and check if the backup succeeds. See Block specific networks from backing up data section for more information.||High|
|Backup Interrupted||Low network bandwidth detected. Druva inSync will retry after some time.||The available network bandwidth is not sufficient for Druva inSync to perform the backup. If inSync Client fails to back up on its own repetitively with the same message, increase the network bandwidth. See Update network bandwidth for more information. If backup status remains the same, contact your Administrator.||Warning|
|Backup interrupted||Server Busy. Please retry after sometime||The Druva inSync Server is busy in executing existing requests or backup is triggered before the storage is created and marked as healthy. Since there is a limit to the number of connections that can be established with the server, Druva inSync has interrupted the backup for some users. Druva inSync will automatically rectify this issue and resume backups.||Warning|
|Backup interrupted||Server not reachable. Please retry after sometime||inSync Client is not able to connect to the server due to a network issue. Wait till a healthy network connectivity is restored and subsequently resume your backups. Contact your Administrator if the backup is interrupted for a prolonged period of time.||Warning|
|Backup Paused||Paused today at <HH:MM> / Paused yesterday at <HH:MM>||The time when the backup was paused. See Pause and resume backup operation for more information.||Informative|
|Configuration Error||Server Security certificate is not trusted by OS. Please contact your IT administrator.||The operating system on the backup device does not trust the security certificate of the Druva inSync Server. You may need to upgrade your inSync Client to the latest version. Contact your Administrator to resolve this error. See Upgrade inSync Client on user device for more information.||Critical|
|Device not backed up||Your device has not backed up for <X> days.||The device is not backed up for at least <X> consecutive days. You can check when was the device last connected to the network for backup. You can also initiate a manual backup if required, as the backup did not happen for a long time. See Start and cancel backup for more information.||High|
|Error||Internal Error||An ongoing backup was interrupted most likely due to a disruption in network connectivity. Wait for Druva inSync to resume backup or contact your Administrator if the issue persists.||High|
|Finishing Backup||-||Backup will complete shortly.||Informative|
|Initializing backup||Started today at <HH:MM AM/PM>||The start time of the backup.||Informative|
|Insufficient Storage||User quota limit reached. Please contact your IT administrator.||The storage quota assigned to back up your data is exhausted. Request your Administrator to allocate additional storage quota.||Critical|
|Druva inSync Activated Successfully||Waiting for server to initiate backup.||inSync Client is active and ready to back up.||Warning|
|No Folders to backup||Please add folders for backup||You do not have any data to back up from the location specified in inSync Client. You can add folders or specify a location for Druva inSync to back up. See the Add folders section for more information.||High|
|Restore Completed||Some files missed. Click details for more info||Indicates that Druva inSync could not restore some of the files from the snapshot.||Informative|
|Unable to Connect||Backup will resume once connection to server is restored||Druva inSync has lost connectivity with the Druva inSync Server. Druva inSync will automatically resume backup once the connectivity is reestablished.||Informative|
Waiting for server to initiate backup.
inSync Client is about to resume a scheduled backup after an interruption, most likely due to a network failure, and is awaiting a response from the Druva inSync Server.
inSync Client status on Sync & Share tab
|Icon||Client Status||Client Sub-Status||Description|
The Sync and Share directory folder in this device is either deleted or moved to a new location. It used to be at <inSync Share directory path>.
|Druva inSync is unable to detect the inSync Share folder at its default location. Specify the new location of the folder or restore the folder to its default location. See Update the location of the inSync Share folder for more information.|
|Never Synced||-||inSync Client is yet to perform its first sync of the shared folders.|
|Share Disabled||-||Administrator has disabled share and sync. Ask you administrator to enable inSync Share if required.|
|Sync Complete||Sync Completed <XX> hours ago.||Time lapsed after the last successful sync activity.|
|Sync Completed With Errors||Internal error.||Some files could not be synced. Wait for inSync Client to sync again and resolve the error. Contact your administrator if the error is not resolved.|
MAPI based email backup error notifications
If your administrator has configured to display MAPI based email backup status, you can see the sub-status message below the Backup Completed Notification.
Note: The notifications listed below will appear only if the Backup Completed notification is displayed on the inSync Client, but Druva inSync failed to backup email using MAPI.
|Errors observed during Outlook Backup.||
Specifies that inSync Client completed email backup using MAPI on your device, but with some errors.
|Errors observed during Outlook Backup. <StoreName> skipped.||
Specifies that inSync Client completed email backup using MAPI on your device. However, Druva inSync skipped a message store because Druva inSync could not open or read it on your device.
|Errors observed during Outlook Backup. <FolderName> from <StoreName> skipped.||
Specifies that inSync Client completed email backup using MAPI on your device. However, Druva inSync skipped a folder in a message store because Druva inSync could not open or read it on your 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 your 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 Druva inSync could not locate PST message store on your device.
|Errors observed during Outlook Backup. <StoreName> is corrupt.||
Specifies that Druva inSync could not perform email backup using MAPI, because the PST message store on your device is corrupt.
|Errors observed during Outlook Backup. <StoreName> is not accessible.||Specifies that Druva inSync could not perform email backup using MAPI, because Druva inSync does not have permissions to access the PST message store on your device.|
|Outlook backup failed due to insufficient system resources.||Specifies that Druva inSync could not perform email backup using MAPI, because of insufficient system resources on your device.|