About Alerts

Last updated
Save as PDF
Share
1. Share
2. Tweet

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 Phoenix generates to provide pertinent information about an event or an exception situation. For example, if the cloud storage utilization crosses the 80% limit, Druva Phoenix creates an alert. Druva Phoenix 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 Phoenix 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.

Alert subscriptions.png

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 Phoenix 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 Phoenix generates.

Alert	Alert type	Created when	Severity	Resolved when
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.
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 after 7 days, but you must check if the Phoenix agent or proxy is running and fix any connection or hardware issue.	Warning	Automatically after 7 days
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 seven days.
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 seven days.
Proxy deployment failed	Jobs	Backup proxy deployment fails.	Warning	The related error is fixed.
Backup failed	Jobs	The backup job fails.	Warning	Not resolved. Note: This alert is valid for 7 days.
Backup window expired	Jobs	Druva Phoenix does not back up the entire data set within the specified duration and does not create a restore point.	Warning	Not resolved. Note: This alert is valid for 7 days.
Backup success with errors	Jobs	The backup is successful but with errors.	Info	Not resolved. Note: This alert is valid for 7 days.
BackupProxy 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 Phoenix 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. Note: This alert is valid for 7 days.
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.	Warning	Not resolved. Note: This alert is valid for 7 days.
Failover job failed	Jobs	The failover job fails for a DR plan.	Critical	Auto-resolved in seven days.
Failover job completed successfully	Jobs	The failover job for a DR plan completes successfully.	Info	Auto-resolved in seven days.
Failover job successful with error	Jobs	The failover job for a DR plan completes successfully with error.	Warning	Auto-resolved in seven days.
Failback job completed successfully	Jobs	The failback job for a virtual machine completes successfully.	Info	Auto-resolved in seven days.
Failback job completed successfully with error	Jobs	The failback job for a virtual machine completes successfully with an error.	Warning	Auto-resolved in seven days.
Failback job failed	Jobs	The failback job for a virtual machine failed.	Critical	Auto-resolved in seven 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 seven days.
Failover operation failed	Jobs	The failover job fails for a DR plan.	Critical	Auto-resolved in seven days.
Failover time window expired	Jobs	The failover job fails for a DR plan.	Critical	Auto-resolved in seven days.
Folder(s) misconfigured for backup	Jobs	The backup job is triggered and the folder specified during the backup is missing. Note: This alert will be generated for Phoenix agents 4.6.5 and later. For earlier Phoenix agent versions, emails will be sent only to the respective administrators and non-administrator; however, alert will not be created.	Warning	Auto-resolved in seven days. Conditional content (Pro member)
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 Phoenix successfully uploads logs to the server.	Info	Not resolved. Note: This alert is valid for 7 days.
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.	Info	Not resolved. Note: This alert is valid for 7 days.
When the Send Alerts Only option is selected in the Manage Credit Limits dialog -
Credit usage of Organization reached 110% of its limit Credit usage of Organization reached 100% of its limit	Billing	An organization consumes an additional 10% credits beyond the configured credit limit. An organization consumes all configured credits.	Critical	Resolved when the credit usage is decreased below 110% of the consumption limit. Resolved when the credit usage drops below 100% of the consumption limit.
Credit usage of Organization reached 90% of its limit Credit usage of Organization reached 80% of its limit	Billing	An organization consumes 90% of the configured credit limit. An organization consumes 80% of the configured credit limit.	Warning	Resolved when the credit usage is decreased below 90% of the consumption limit. Resolved when the credit usage is decreased below 80% of the consumption limit.
When the Disable Backups option is selected in the Manage Credit Limits dialog -
Credit usage of Organization reached 110% of its limit Credit usage of Organization reached 100% of its limit Credit usage of Organization reached 90% of its limit Credit usage of Organization reached 80% of its limit	Billing	An organization consumes an additional 10% credits beyond the configured credit limit. An organization consumes 100% of the configured credit limit. An organization consumes 90% of the configured credit limit. An organization consumes 80% of the configured credit limit.	Critical	Resolved when the credit usage drops below 110% of the consumption limit. Resolved when the credit usage is decreased below 100% of the consumption limit. Resolved when the credit usage is decreased below 90% of the consumption limit. Resolved when the credit usage is decreased below 80% of the consumption limit.
Credit usage of Organization reached 90% of its limit Credit usage of Organization reached 80% of its limit Credit usage of Organization reached 70% of its limit	Billing	An organization consumes 90% of the configured credit limit. An organization consumes 80% of the configured credit limit. An organization consumes 70% of the configured credit limit.	Warning	Resolved when the credit usage is decreased below 90% of the consumption limit. Resolved when the credit usage is decreased below 80% of the consumption limit. Resolved when the credit usage is decreased below 70% of the consumption limit.
Backups are now enabled	Billing	Backups are now enabled for organizations.	Info	Automatically after 7 days.
Configuration rule invalid	Configuration	The selected vCenter object is invalid (the vCenter folder in the rule is renamed, moved, or deleted.) Druva Phoenix removes the server group in the rule. Druva Phoenix deletes the backup proxy pool in the rule.	Warning	Resolved when, A valid vCenter object replaces an invalid vCenter object. Druva Phoenix assigns a valid server group. Druva Phoenix assigns a valid backup proxy pool.
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 Phoenix 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 Phoenix 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 Phoenix requires all backup proxies in a backup proxy pool to support application-aware processing.	Warning	Druva Phoenix 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 Phoenix CloudCache.	Info	When the Decommission CloudCache activity completes for the respective Phoenix CloudCache.
CloudCache decommission completed	CloudCache	The decommission CloudCache activity for the respective Phoenix CloudCache is completed.	Info	Not resolved. Note: This alert is valid for 7 days.
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. Note: This alert is valid for 7 days.
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 snapshots 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 Phoenix 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 Phoenix 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 snapshot using vendor APIs	Configuration	Isilon backup job fails while creating an Isilon snapshot.	Critical	Automatically after 7 days

Note: The Jobs alerts will be automatically removed from the Alerts list after 7 days.

SUPPORT community

support Resources

More links

Support Contacts