Alerts
Overview
inSync Master displays a high-level view of alerts in your environment on the Manage Alerts page. Alerts indicate an exception situation or give an indication of a potential issue that needs attention. inSync displays alerts based on their severity so that administrators can address issues based on their severity and take appropriate action to resolve them.
Alerts are processed periodically based on the respective alert interval. An alert is logged at the first instance and if the issue persists, the time and date of the same alert is updated for the subsequent instances.
Administrators can customize alert messages to provide actionable solutions to the subscribers. Customized messages and schedules of alerts are common for all administrator accounts and the change reflects for all administrators who can view or edit the alert message.
Widgets on the Manage Alerts page provide a snapshot of alerts based on alert severity, top alert types and alert activity over time. inSync also has the provision to mute an alert, without affecting its settings, to prevent the alert from generating any notifications.
inSync provides an option to collate emails for alerts of certain severity type and send it in a single mail communication at a configurable frequency. This saves the administrator’s mailbox from flooding with multiple emails of the same alert.
Refer About inSync Alerts, Manage Alerts, and Configure Alert Settings sections to know more on inSync alerts.
About inSync Alerts
The following table lists various inSync alert messages.
Alert | Indicates that... |
Antivirus Activity Detected |
You did not exclude some inSync storage folders from an antivirus scan. Severity: Critical Action required: Ensure that your antivirus software does not scan the Data folder, Database folder, and Database log folders. |
Checkpoint process is slow |
Database checkpoint process for performance-optimized storages is slower than the rate at which inSync Master might not be able to handle new requests. If the checkpoint process slows down further, the inSync Master stops all ongoing backups or compaction. This issue occurs when you use any sub-optimal hardware for storage. Severity: Critical Action required: Contact Druva Support if the problem persists. |
Compaction Completed |
Compaction of a storage is complete. This alert is generated only once. Severity: Notification Action required: None. |
Endpoint Encryption Failed |
inSync failed to encrypt the data on endpoint device. Severity: Critical Following reasons can trigger this alert
Action required: Based on your configuration, do the following to resolve the alert:
In addition to the above actions, you can get well acquainted with best practices for EFS. For more information, see Best practices for the Encrypting File System. |
License Expiry |
The inSync license is expired or is about to expire. Severity: Critical Action required: Contact Druva Support or your account manager to renew your inSync license. |
Low Database Storage Available |
The free space available on the disk that contains the database folder or the database log folder is less than double the required disk space.
If the database folder and database log folder are on the same disk, it should have 8 GB of free space. This alert is displayed when the disk space is less than the double the required disk space. Hence, an alert is generated when
If the database folder and database log folder are on the same disk, it should have 16 GB of free space. Severity: High Action required: Remove unnecessary files to free up the required space on the disk. |
Low Guest User License |
The number of inSync users or inSync guest users has exceeded 80% of the licenses available. This alert appears only if you have inSync Share license. Severity: High Action required: Contact Druva Support to purchase additional user licenses. |
Low Storage Space Available |
The storage assigned to your organization is almost full. Severity: High Action required: Delete older snapshots. Contact Druva Support to purchase more storage space. |
Low User Storage Space Available |
A user’s storage consumption is nearing the quota limit. For more information on user quota, see Assign user quota for data backup. Severity: High Action required: Increase the user quota or request the user to remove unnecessary files and folders. From the Profile settings, administrators can exclude the path to remove unnecessary folders from being backed up or exclude file extensions by using the Global Exclusion feature. |
Misconfigured Backup Folder |
A folder is configured for backup, but it does not exist on a user device. Severity: Warning Action required: Review the profile configuration or user device configuration, and then remove the backup path or reconfigure accordingly. |
Preserved Users Limit Reached |
You have breached the limit (110%) for maximum number of preserved users permitted and will no longer be able to place any more users in preserved state manually or through auto-preserve. Severity: Critical Action required: Do one of the following:
|
Preserved Users Limit Reached - Warning |
You have reached 107% of the total deployed users limit. Severity: Warning Action required: Do one of the following:
|
Restore Check Failed |
inSync checks the consistency of backed up data or device snapshots on a regular basis. Consistency check for a snapshot failed. Severity: Critical Action required: Contact Druva Support for assistance. |
Restore Status
|
The status of a restore activity. Severity: Notification
|
Storage Error |
The inSync Master could not read or write data to a storage. Severity: Critical Action required: View the log files to identify the issue with the storage and resolve it. Contact Druva Support for assistance. |
System, App Settings Backup Failed |
inSync did not backup System and Application Settings (Persona settings). Severity: Warning |
User Backup Inactivity
|
The user did not back up data from the user's device for a considerable period. This period is defined in the profile to which the user is associated. Severity: Warning Action required: Contact the user and ask him to initiate a backup from his device. Alternatively, trigger a backup of the user device from the inSync Admin Console. |
User Preservation Failed |
inSync failed to preserve users because of insufficient Preserved Users license. Severity: Critical Action required: Perform one of the following actions to remove this alert,
|
View alerts
To view the inSync alerts:
- On the inSync Management Console menu bar, click
icon.
Alerts are displayed on the Manage Alerts page. Alerts are distributed on the Recent and Older tabs based on their severity and time of generation.
Refer to the Manage alerts section for an overview of the details displayed on the Manage Alerts page.
Alert intervals
All inSync alerts are displayed on the Manage Alerts page immediately when a condition qualifies for an alert. The time and frequency of sending email notification about the alerts to its subscribers depends on:
- Alert severity
- Default notification schedule of the alert
- Alert collate setting
If you have not configured collate, inSync initiates email notifications based on the default schedule of the alert. For information on configuring collate, see Collate all emails for this alert under Configure Alert Settings.
The following table shows the approximate time in which inSync initiates email notification for each alert. You can configure collate only for High and Warning alerts as shown in the table. After you collate an alert, the second alert notification is sent according to the time configured in the collate setting.
In the following table:
- The 1st Alert column shows the approximate time of email notification for each alert sent to its subscribers.
- The 2nd Alert column displays the default interval after which the second notification is mailed.
For example, if Low Guest User License alert is generated for User A at 11 am:
- Low Guest User License will be immediately displayed against the user name on the Manage Alerts dashboard.
- First email notification for User A is sent immediately.
- Second email notification for User A is mailed after 7 days, provided the alert condition is not resolved.
Severity | Alert name | 1st Alert | 2nd Alert |
---|---|---|---|
Critical | Antivirus Activity Detected | Immediate | 6 hours |
Checkpoint process is slow | 1 hour | ||
Endpoint Encryption Failed | 2 days | ||
License Expiry | 1 day | ||
Preserved Users Limit Reached | 1 day | ||
Restore Check Failed | 1 day | ||
Storage error | 1 day | ||
User Preservation Failed | 3 days | ||
High | Low Database Storage Available |
9 am UTC daily. inSync Administrator can change this time using collate. |
6 hours |
Low Guest User License | 7 days | ||
Low Storage Space Available | 1 day | ||
Low User Storage Space Available | 1 day | ||
Warning | Misconfigured Backup Folder |
9 am UTC weekly. inSync Administrator can change this time using collate. |
3 days |
Preserved Users Limit Reached - Warning | 1 day | ||
System, App Settings Backup Failed | 3 days | ||
User Backup Inactivity | 3 days | ||
Notifications | Compaction Completed | Immediate after compaction | None |
Restore Status | Immediate after restore | None |