About Alerts
This topic provides an overview of alerts. It also includes information about the severity of the alerts and type of alerts.
Overview of alerts
Alerts are the notifications that Druva generates to provide pertinent information about an event or an exception situation. For example, if the cloud storage utilization crosses the 80% limit, Druva creates an alert. Druva creates an alert for specific events, or for every occurrence of an exception. The Alerts page displays the Alerts tab selected in the left pane. The corresponding alert details are displayed in the right pane.
An alert stays active until it is resolved and appears in the Alerts list. After fixing the event or exception that caused the alert, Druva treats the associated alert as resolved, and the alert no longer appears on the menu bar of the Dashboard or the Alerts list. A record of active alerts, as well as resolved alerts, appears in the Alerts History report. For more information, see Reports.
By default, all the administrators, such as cloud administrators, organization administrators, group administrators, custom administrators, and data protection officers are subscribed to alerts. However, they can unsubscribe themselves from the alerts using the My Subscriptions tab on the Alerts Subscriptions page. For more information, see Alert subscriptions for administrators.
Additionally, the cloud administrators and their custom administrators, organization administrators and their custom administrators, and data protection officers can manage alert subscriptions for the non-administrators. Based on the subscriptions, non-administrators receive email notifications in the event of job failures, reports, and so on.
Severity of alerts
The alerts that Druva generates can assume either of these levels of severity: Critical, Warning, or Information. The severity of the alerts usually indicates the priority for a resolution of the underlying event or exception. The following table provides details about the severity of the alerts:
Severity of alert | Description |
---|---|
Critical | Indicates a state that requires immediate resolution. |
Warning | Indicates a state that requires resolution as soon as possible. However, the priority of alert resolution is lower than that of the critical alert. |
Info | Indicates that the event may not require administrator-assisted resolution. Alerts of this severity are only informative. |
Types of alerts
The following table lists the alerts that Druva generates.
Alert | Alert type | Created when | Severity | Resolved when |
---|---|---|---|---|
Install VMware Tools for Sandbox Recovery | Jobs | VMware Tools is not installed. | Critical | VMware Tools need to be installed within 30 hours for the scan to proceed. |
Data Lock enabled | Configuration | The Data Lock is enabled. | Warning | Automatically after 7 days. Note: If the same alert is raised on the same target, the previous alert will be resolved automatically. |
Data Lock content updated | Configuration | There are modifications to the backup set content. | Warning | Automatically after 7 days. |
Auto discovery failed for the server |
Configuration |
The auto discovery job fails and databases on the server are not discovered. |
Warning |
When the discovery is done successfully for the Oracle Server. |
Some of the configured nodes not used in the backup | Jobs | The configured nodes are not used in the backup because they are not in the Open state. | Info | Automatically after 7 days. |
Instances went down for database | Jobs | The specified instance goes down during the backup. | Warning | Automatically after 7 days |
Backup triggered failed as server is disconnected | Jobs | Backup is not triggered as the server is disconnected for more than 7 days. Alert will be resolved automatically when the device reconnects. You must check if the agent or proxy is running and fix any connection or hardware issue. |
Warning | Automatically after the device reconnects. |
Backup triggered failed as NAS proxy is disconnected | Jobs | Backup is not triggered as the NAS proxy is disconnected for more than 7 days. Alert will be resolved automatically when the proxy reconnects. You must check if the agent or proxy is running and fix any connection or hardware issue. |
Warning | Automatically after the proxy reconnects |
Incarnation has changed. Incremental backup job converted to full. |
Jobs |
The incarnation of the database, which is being backed up changes. |
Info |
Auto-resolved in 7days. |
Archive log chain is broken. Converting Incremental backup to full. |
Jobs |
The archived log sequences are missing after the last backup. |
Info |
Auto-resolved in 7 days. |
Proxy deployment failed |
Jobs |
Backup proxy deployment fails. |
Warning |
The related error is fixed. |
Backup failed |
Jobs |
The backup job fails. |
Critical |
Not resolved.
|
Backup window expired |
Jobs |
Druva does not back up the entire data set within the specified duration and does not create a recovery point. |
Warning |
Not resolved.
|
Backup skipped | Jobs | The backup job is skipped as the scheduled backup window expired. The client was busy processing another job. | Warning | Automatically after 7 days |
Backup success with errors |
Jobs |
The backup is successful but with errors. |
Warning |
Not resolved.
|
Backup Proxy has been in Disconnected State for more than 15 minutes | Configuration |
The VMware backup proxy has been disconnected from the Druva Cloud or VMware vCenter for more than 15 minutes. Druva checks the connection status between the VMware backup proxy, Druva Cloud, and vCenter every 15 minutes and sends out the notification once. |
Warning | Resolved when the VMware Backup Proxy establishes a connection with Druva Cloud and VMware vCenter again. |
Restore failed |
Jobs |
The restore fails. |
Critical |
Not resolved.
|
Instant Restore failed | Cache | The creation of an Instant Restore virtual machine fails. | Critical | Automatically after 7 days. |
Instant Restored VM Deletion failed | Cache | The deletion of an instantly restored virtual machine fails. | Warning | Automatically after 7 days. |
VMware Instant Restore Migrate to Production job failed | Cache | The migration to production of an instantly restored virtual machine fails. | Critical | Automatically after 7 days. |
DR restore failed |
Jobs |
The triggered disaster recovery job fails. |
Critical |
Not resolved.
|
Failover job failed | Jobs | The failover job fails for a DR plan. | Critical | Auto-resolved in 7 days. |
Failover job completed successfully |
Jobs |
The failover job for a DR plan completes successfully. |
Info |
Auto-resolved in 7 days. |
Failover job successful with error | Jobs | The failover job for a DR plan completes successfully with error. | Warning | Auto-resolved in 7 days. |
Failback job completed successfully | Jobs | The failback job for a virtual machine completes successfully. | Info | Auto-resolved in 7 days. |
Failback job completed successfully with error | Jobs | The failback job for a virtual machine completes successfully with an error. | Warning | Auto-resolved in 7 days. |
Failback job failed | Jobs | The failback job for a virtual machine failed. | Critical | Auto-resolved in 7 days. |
Change in source network detected for the VM | Configuration | The target VPC and subnet needs to be changed due to new network mappings detected for the virtual machine. | Warning | Auto-resolved in 7 days. |
Failover operation failed |
Jobs |
The failover job fails for a DR plan. |
Critical |
Auto-resolved in 7 days. |
Failover time window expired | Jobs | The failover job fails for a DR plan. | Critical | Auto-resolved in 7 days. |
Jobs |
The backup job is triggered and the folder specified during the backup is missing.
|
Warning |
Auto-resolved in 7 days. |
|
License about to expire | License | The license is about to expire in 30 days. | Warning | Auto-resolved when the license is renewed |
License expired | License | The license has expired. | Critical | Auto-resolved when the license is renewed |
Pre-script execution failed |
Jobs |
The pre-backup script execution fails. |
Info |
Auto-resolved in 7 days. |
Post-script execution failed |
Jobs |
The post-backup script execution fails. |
Info |
Auto-resolved in 7 days. |
Upload logs success |
Jobs |
The user clicks Request Job Logs on the Job Details page and Druva successfully uploads logs to the server. |
Info |
Not resolved.
|
Upload logs failure |
Jobs |
The user clicks Request Job Logs on the Job Details page and the logs fail to get upload on the server. |
Warning |
Not resolved.
|
When the Send Alerts Only option is selected in the Manage Credit Limits dialog - | ||||
Billing |
|
Critical |
|
|
|
Billing |
|
Warning |
|
When the Disable Backups option is selected in the Manage Credit Limits dialog - | ||||
|
Billing |
|
Critical |
|
|
Billing |
|
Warning |
|
Backups are now enabled | Billing | Backups are now enabled for organizations. | Info | Automatically after 7 days. |
Configuration rule invalid |
Configuration |
|
Warning |
Resolved when,
|
Conflicting virtual machines | Configuration | When a virtual machine is part of more than one auto configuration rule, the virtual machine is not configured. | Warning | Admin has to manually resolve the conflict and apply the rule. For more information, see Conflicting VM scenarios. |
Auto discovery cron job failed | Configuration | Druva cannot auto-discover SQL instances or availability group on the server due to the failure of the cron job. | Warning | Resolved when the auto-discovery succeeds on the node. |
Different client versions for AG Nodes | Configuration | Druva discovers the different client versions of the nodes hosting the availability group. | Warning | Resolved when the client version of the nodes hosting the availability group is upgraded to the same version. |
All backup proxies in the backup proxy pool do not support application-aware processing | Configuration | Druva requires all backup proxies in a backup proxy pool to support application-aware processing. | Warning | Druva backs up the virtual machines without running application-aware backups. This alert is resolved when all the backup proxies are upgraded to the latest version. |
CloudCache storage space low |
CloudCache |
The CloudCache utilization exceeds 80% but is less than 100%. |
Warning |
CloudCache storage utilization falls below 80%. |
CloudCache Storage Space Full |
CloudCache |
The CloudCache utilization exceeds 100%. |
Critical |
CloudCache storage utilization falls below 100%. |
CloudCache not reachable for server |
CloudCache |
A server cannot connect to CloudCache during backup or restore job. |
Warning |
When the server connects to CloudCache in the subsequent backup or restore job. |
CloudCache not reachable for cloud |
CloudCache |
The Druva Cloud cannot connect to the CloudCache during the synchronization schedule. |
Warning |
When the Druva Cloud connects to the CloudCache in the current or the next synchronization schedule. |
CloudCache decommission started |
CloudCache |
The user clicks Decommission Cache for the respective CloudCache. |
Info |
When the Decommission CloudCache activity completes for the respective CloudCache. |
CloudCache decommission completed |
CloudCache |
The decommission CloudCache activity for the respective CloudCache is completed. |
Info |
Not resolved.
|
CloudCache volume: <volume> is not mounted |
CloudCache |
The CloudCache volume is not mounted properly. |
Critical |
When the CloudCache can successfully read or write data to the volume during the backup, restore, or the synchronization schedule. |
CloudCache unable to read/write on Volume |
CloudCache |
The CloudCache cannot read or write data to the volume during the backup, restore, or the synchronization schedule. |
Warning |
When the CloudCache can successfully read or write data to the volume during the backup, restore, or the synchronization schedule. |
CloudCache having low data upload rate to cloud |
CloudCache |
The data upload rate from the CloudCache to the Druva Cloud is significantly low. |
Warning |
When the data upload rate is sufficient enough to upload the unsynchronized data to the Druva Cloud. Note: If you modify the synchronization schedule, this alert is not generated for the next 7 days. |
Upgrade to version<x.x::revision number> failed |
Upgrade |
The upgrade fails. |
Warning |
Not resolved.
|
Backup mount is disabled | Jobs | A backup job fails for a disabled backup mount. A backup mount is disabled if the Phoenix Backup Store is unable to upload recovery points to the Druva Cloud for a while. | Critical | The backup mount is enabled. |
Phoenix Backup Store has reached 90% capacity | Oracle | The storage capacity on the Phoenix Backup Store is critically low. If the storage is not enough on the Phoenix Backup Store to store data, RMAN backups can fail. | Critical | Auto resolved when enough storage is available on the Phoenix Backup Store. |
Phoenix Backup Store has reached 80% capacity | Oracle | The storage capacity on the Phoenix Backup Store is low. If the storage is not enough on the Phoenix Backup Store to store data, RMAN backups can fail. | Warning | Auto resolved when enough storage is available on the Phoenix Backup Store. |
Seeding device has reached 80% capacity | Seeding | The 80% storage capacity of the seeding device is consumed. | Warning | Druva generates an 80% storage consumption alert or triggers a request to ship the device to AWS. |
Seeding device has reached 100% capacity | Seeding | The 100% storage capacity of the seeding device is consumed. | Warning | Druva triggers a request to ship the device to AWS. |
Failed to create changelist | Configuration | Isilon backup job fails while creating an Isilon changelist. | Critical | Automatically after 7 days |
User validation fails while backing up an Isilon NAS device | Configuration | User validation fails during backup. | Critical | Automatically after 7 days |
Failed to create recovery point using vendor APIs | Configuration | Isilon backup job fails while creating an Isilon recovery point. | Critical | Automatically after 7 days |
Note: The Jobs alerts will be automatically removed from the Alerts list after 7 days.