# Alert Type Details

You can create an alert by using predefined alert criteria. The criteria you select trigger the alert.

Alert Type | Description
--- | ---
Backup Delayed by X Hrs | A backup operation was in a waiting state for the hours specified by the user at time of configuration.
Backup Job Activity | A backup operation was killed, resumed, or suspended by a user, or resumed by the system.
Backup Job completed with Errors | A backup operation completed with errors.
Backup Job Failed | A backup operation failed to complete or was stopped by the system.
Backup Job Skipped | A scheduled backup operation ran late, was skipped, or skipped due to a holiday.
Backup Job Succeeded | A backup operation completed successfully.
Decrease in Data size by X percent for backup job | A backup job is at least n% smaller in data size than the previous job of the same type (full, incremental, differential or synthetic full). Default is set at 10%. (n is the percentage of decrease in data size, at which if met, will trigger the alert. The actual data size decrease may be larger than the n%.)
Disk space low on client | The disk space for the client software installation and system directories (including the Job Results folder) reached the minimum thresholds: The thresholds for the software installation and system directories, as well as the frequency interval at which the directories are monitored, are configurable. The threshold for the Job Results directory is configurable. If the Data Classification Enabler is installed, this alert is sent if 85% or more of the volume disk space is consumed. If the Content Indexing Engine is installed, this alert is sent if 80% or more of the volume disk space is consumed or if the minimum free space falls below 10 GB.
Failover activity | A failover event occurred.
Failover completed | A failover operation completed successfully.
Failover failed | A failover operation failed to complete.
Failover started | A failover operation started.
Increase in Data size by X percent for backup job | A backup job was at least n% larger in data size than the previous job of the same type (full, incremental, differential or synthetic full). Default is set at 10%. (n is the percentage of increase in data size, at which if met, will trigger the alert. The actual data size increase may be larger than the n%.)
May miss SLA | The client computer may miss the SLA. The alert is triggered in the following cases: There is no job scheduled before the SLA period. A job that is scheduled or running is expected to run beyond the SLA period based on the job forecast time. There is a history of failing jobs. A job is running longer than usual time and is about to cross the SLA period. Blackout window impacts a job that is scheduled or running, which further impacts the job and the SLA.
Missed SLA | The client computer missed the SLA. The alert is triggered in the following cases: There is no job within SLA period. A backup job is failed.
No Backup for last X Days | No backup jobs have run in the specified number of days. When the Data Protection alert is configured as a subscription-based alert, this criterion is used by default to notify laptop users when no backups are performed. Note This criteria does not apply to synthetic full backups. No backup alert condition is calculated based on the start time of the last successful backup job.
Passive node is not reachable | One of the passive nodes in the failover cluster is not reachable.
Production Commserve is not reachable | The active, production CommServe host is not reachable.
Production Commserve is not running | The active, production CommServe host is not running.
Restore Job Activity | A data recovery operation was killed, resumed, or suspended by a user.
Restore Job complete with Errors | A restore operation completed with errors.
Restore Job Failed | A restore operation failed to complete, failed to start, or was stopped by the system. When the Data Recovery alert is configured as a subscription-based alert, this criterion is used by default to notify laptop users when the backup data failed to be restored for a client.
Restore Job Skipped | A scheduled restore operation ran late, was skipped by a user or skipped due to a holiday.
Restore Job Started | A restore operation was started by a user.
Restore Job Succeeded | A restore operation completed successfully.
VM Backup failed | A VM backup job failed to complete, failed to start, or was stopped by the system.
VM Backup succeeded | A VM backup job completed successfully.
VM Backup succeeded with errors | A VM backup job completed with errors.

×

Loading...