Veeam ONE

Version 9.5
Working with Alarms
July, 2018
© 2018 Veeam Software.

All rights reserved. All trademarks are the property of their respective owners.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language in any form by any means, without written permission from Veeam Software
(Veeam). The information contained in this document represents the current view of Veeam on the issue
discussed as of the date of publication and is subject to change without notice. Veeam shall not be liable for
technical or editorial errors or omissions contained herein. Veeam makes no warranties, express or implied, in
this document. Veeam may have patents, patent applications, trademark, copyright, or other intellectual property
rights covering the subject matter of this document. All other trademarks mentioned herein are the property of
their respective owners. Except as expressly provided in any written license agreement from Veeam, the
furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other
intellectual property.

NOTE:

Please read the End User Software License Agreement before using the accompanying software program(s).
Using any part of the software indicates that you accept the terms of the End User Software License
Agreement.

2 | Veeam ONE | Working with Alarms | REV 7

Contents
CONTENTS ..............................................................................................................................................................3
CONTACTING VEEAM SOFTWARE ...........................................................................................................................5
ABOUT THIS DOCUMENT ........................................................................................................................................6
ABOUT ALARMS ......................................................................................................................................................7
HOW ALARMS WORK................................................................................................................................................... 8
ALARM RULES ........................................................................................................................................................... 9
ALARM SEVERITY ...................................................................................................................................................... 11
ALARM ASSIGNMENT OPTIONS ...................................................................................................................................... 12
ALARM RESPONSE ACTIONS ......................................................................................................................................... 13
ADVANCED ALARM OPTIONS ......................................................................................................................................... 14
ALARM REPORTS ....................................................................................................................................................... 15
CONFIGURING ALARMS ...................................................................................................................................... 16
CREATING ALARMS .................................................................................................................................................... 17
Step 1. Select Alarm Type ........................................................................................................................... 18
Step 2. Specify General Alarm Settings ........................................................................................................ 19
Step 3. Specify Alarm Rules and Severity ..................................................................................................... 20
Step 4. Specify Alarm Assignment ............................................................................................................... 25
Step 5. Specify Alarm Actions ...................................................................................................................... 27
Step 6. Configure Alarm Suppression Settings .............................................................................................. 29
Step 7. Specify Alarm Details ...................................................................................................................... 31
Step 8. Save Alarm Settings ........................................................................................................................ 32
MODIFYING ALARMS .................................................................................................................................................. 33
Adding Alarm Rule from Task or Event ........................................................................................................ 35
Adding Alarm Rules from Performance Counters .......................................................................................... 36
CHANGING ALARM ASSIGNMENT SCOPE ........................................................................................................................... 37
Modifying Alarm Assignment Scope ............................................................................................................. 38
Excluding Single Objects from Alarm Assignment Scope................................................................................ 40
Excluding Multiple Objects from Alarm Assignment Scope ............................................................................. 41
Excluding Objects from Multiple Alarms ....................................................................................................... 43
Viewing Alarm Exclusions ............................................................................................................................ 45
COPYING ALARMS...................................................................................................................................................... 46
DISABLING AND ENABLING ALARMS ................................................................................................................................ 47
DELETING ALARMS .................................................................................................................................................... 48
EXPORTING AND IMPORTING ALARMS .............................................................................................................................. 49
SUPPRESSING ALARMS ................................................................................................................................................ 51
Maintenance Mode ..................................................................................................................................... 52
Alarm-Specific Suppression Settings ............................................................................................................ 55
Suppressing Guest Disk Space Alarms ......................................................................................................... 56
MODELLING ALARM NUMBER ........................................................................................................................................ 57
CONFIGURING ALARM NOTIFICATIONS............................................................................................................................. 59
Email Notifications ...................................................................................................................................... 60
SNMP Traps ............................................................................................................................................... 72
EXAMPLES: HOW TO CREATE ALARMS ............................................................................................................................. 75
How to Create Alarm Notifying About Multiple Snapshot Problems ................................................................. 76
How to Create Alarm Notifying About Increased Host Disk Latency................................................................ 79
WORKING WITH TRIGGERED ALARMS ............................................................................................................... 82
VIEWING TRIGGERED ALARMS ...................................................................................................................................... 83
RESOLVING ALARMS ................................................................................................................................................... 85

3 | Veeam ONE | Working with Alarms | REV 7

 Resolving Individual Alarms ........................................................................................................................ 86
Resolving Multiple Alarms ........................................................................................................................... 87
Notifications on Resolved Alarms ................................................................................................................. 88
ACKNOWLEDGING ALARMS ........................................................................................................................................... 89
Acknowledging Individual Alarms ................................................................................................................ 90
Acknowledging Multiple Alarms ................................................................................................................... 91
Notifications on Acknowledged Alarms ......................................................................................................... 92
VIEWING ALARM HISTORY ........................................................................................................................................... 93
EXPORTING TRIGGERED ALARMS ................................................................................................................................... 94
WORKING WITH INTERNAL ALARMS .................................................................................................................. 95
VIEWING INTERNAL ALARMS......................................................................................................................................... 96
CONFIGURING INTERNAL ALARMS .................................................................................................................................. 97
APPENDIX A. ALARMS ......................................................................................................................................... 98
VEEAM BACKUP & REPLICATION ALARMS.......................................................................................................................... 99
VMWARE VSPHERE ALARMS ....................................................................................................................................... 104
MICROSOFT HYPER-V ALARMS .................................................................................................................................... 127
INTERNAL ALARMS ................................................................................................................................................... 141
APPENDIX B. ALARM RULES .............................................................................................................................. 145
ALARM RULES FOR VMWARE VSPHERE .......................................................................................................................... 146
ALARM RULES FOR MICROSOFT HYPER-V ....................................................................................................................... 152
ALARM RULES FOR VEEAM BACKUP & REPLICATION........................................................................................................... 155

4 | Veeam ONE | Working with Alarms | REV 7

Contacting Veeam Software
At Veeam Software we value the feedback from our customers. It is important not only to help you quickly with
your technical issues, but it is our mission to listen to your input, and build products that incorporate your
suggestions.

Customer Support
Should you have a technical concern, suggestion or question, please visit our Customer Center Portal at
www.veeam.com/support.html to open a case, search our knowledge base, reference documentation, manage
your license or obtain the latest product release.

Company Contacts
For the most up to date information about company contacts and offices location, please visit
www.veeam.com/contacts.html.

Online Support
If you have any questions about Veeam products, you can use the following resources:

 Full documentation set: www.veeam.com/documentation-guides-datasheets.html

 Community forum at forums.veeam.com

5 | Veeam ONE | Working with Alarms | REV 7

About This Document
This document describes how to work with Veeam ONE alarms for Veeam Backup & Replication, VMware vSphere
and Microsoft Hyper-V infrastructures. It provides instructions on configuring alarms, enabling alarm notifications
and working with triggered alarms in Veeam ONE Monitor.

Intended Audience
The guide is designed for anyone who plans to use the Veeam ONE solution. It is primarily aimed at
administrators managing Veeam Backup & Replication, VMware vSphere and Microsoft Hyper-V environments,
but can also be helpful for other current and perspective Veeam ONE users.

Document Revision History

Revision # Date Change Summary

Revision 7 7/29/2018 Information about alarm aggregation types added to section

Alarm Rules. Section Appendix B. Alarm Rules updated.

Revision 6 12/19/2017 Document updated for Veeam ONE 9.5 Update 3.

Revision 5 3/14/2017 Updated Step 1 in section SNMP Traps.

Revision 4 1/17/2017 Document updated for Veeam ONE 9.5 Update 1.

Revision 3 1/11/2016 Added note about objects to exclude in section Step 3. Specify
Alarm Rules and Severity.

Revision 2 12/30/2016 Added sections VMware vSphere Alarms and Microsoft Hyper-V
Alarms.

Revision 1 11/16/2016 Initial version of the document for Veeam ONE 9.5.

6 | Veeam ONE | Working with Alarms | REV 7

About Alarms
Veeam ONE alarms notify users about important events, changes and potential problems in the managed virtual
and backup environment. Alarms speed up the process of identifying, troubleshooting and reacting to issues that
may affect mission critical services and business operations.

Out of the box, Veeam ONE comes with a set of predefined alarms so that you can start monitoring your
environment immediately after installing the solution. Predefined alarms include:

 VMware vSphere and vCloud Director alarms

 Microsoft Hyper-V alarms

 Veeam Backup & Replication alarms

 Internal alarms for monitoring issues with Veeam ONE

Predefined alarms are based on best practices and include an extensive knowledge base. When a problem
occurs, you will not only be alerted, but will also have all the necessary information for troubleshooting and
finding the root cause of the issue.

Veeam ONE offers an extensive set of tools that will help you develop your own alarm model. Depending on your
requirements to the virtual and backup environment, you can customize predefined alarms, or create new
alarms. This section describes various aspects of alarms in Veeam ONE, including alarm rules, severity levels,
assignment options, response actions and other.

7 | Veeam ONE | Working with Alarms | REV 7

How Alarms Work
After you connect virtual or backup servers, Veeam ONE Monitor starts collecting data about objects in your
environment and their health state, and checks this data against alarm configuration in real time. If Veeam ONE
Monitor detects that behavior or state of an infrastructure object meets alarm criteria, or that a specific event
occurs, it triggers an alarm with the corresponding severity level.

After an alarm is triggered, Veeam ONE Monitor console will display alarm details and information about the
affected object. You can view, acknowledge or resolve the alarm. If an alarm is configured to perform some
action, Veeam ONE Monitor performs a response action after the alarm is triggered — sends an email
notification, SNMP trap or runs a custom script.

If the event, state or condition that triggered the alarm is resolved, Veeam ONE Monitor updates the alarm status
in the console.

8 | Veeam ONE | Working with Alarms | REV 7

Alarm Rules
Every alarm has one or more associated rules that define conditions to trigger the alarm, severity of the alarm
and rule suppression settings.

There are two types of alarm rules:

 Event-based rules are rules for alerting about specific events that occur in the backup or virtual
infrastructure. These can be events issued by the hypervisor or Veeam Backup & Replication events.

 Rules for a specific condition or state are rules for alerting about an important condition or changed
state of infrastructure objects.

For the full list of available rule types, see Appendix B. Alarm Rules.

Aggregation Type
For state-based rules that have parameter counters, Veeam ONE allows to select an aggregation type. An
aggregation type defines how Veeam ONE analyzes performance data collected for a specified period of time,
and compares it to the threshold.

The following table explains how Veeam ONE alarms trigger depending on the aggregation type and rule
condition:

Condition
Aggregation
Type
Above Below

Min Veeam ONE takes the minimum value across the Veeam ONE takes the minimum value across the
collected performance parameters and compares it collected performance parameters and compares it
to the specified threshold. If the value is above the to the specified threshold. If the value is below the
threshold, Veeam ONE triggers an alarm. That threshold, Veeam ONE triggers an alarm. That
means that the alarm triggers only if all the values means that the alarm triggers if at least one of the
are above the threshold. collected values is below the threshold.

Avg Veeam ONE takes the average value across the Veeam ONE takes the average value across the
collected performance parameters. The alarm collected performance parameters. The alarm
triggers if this value is above the threshold. triggers if this value is below the threshold.

Max Veeam ONE takes the maximum value across the Veeam ONE takes the maximum value across the
collected performance parameters and compares it collected performance parameters and compares it
to the specified threshold. If the value is above the to the specified threshold. If the value is below the
threshold, Veeam ONE triggers an alarm. That threshold, Veeam ONE triggers an alarm. That
means that the alarm triggers if at least one of the means that the alarm triggers only if all the values
collected values is above the threshold. are below the threshold.

To learn how to configure state-based rules, see Step 3. Specify Alarm Rules and Severity.

Linking Rules
One alarm can include up to 8 rules. You can link two or more rules with the help of Boolean operators:

 AND — if rules are joined with this operator, an alarm is triggered when conditions for all linked rules
are met.

9 | Veeam ONE | Working with Alarms | REV 7

  OR — if rules are joined with this operator, an alarm is triggered when a condition for any of the linked
rules is met.

You can form several groups of linked rules and join them with different operators. To learn how to link rules,
see Step 3. Specify Alarm Rules and Severity.

10 | Veeam ONE | Working with Alarms | REV 7

Alarm Severity
Every alarm rule is associated with a specific severity level. The severity level defines how serious the state or
event is and how badly it can affect an object health state.

There are 4 severity levels that are color-coded as follows:

 Error (red) indicates a critical situation or a major problem that requires immediate action.

 Warning (yellow) indicates a potential problem or non-critical issue that needs your attention. If the
issue is left without attention, it can potentially cause a major problem.

 Resolved (green) indicates that the issue was eliminated because of the changed conditions, or shows
that the alarm was resolved manually.

 Information (blue) indicates general information about a specific condition or health state of an
object.

You can define different severity levels for conditions of different intensity. For example, if the level of memory
usage must not exceed 75%, you can create the following alarm rules:

 If the memory usage is over 70%, an alarm with the Warning severity level must be triggered.

 If the memory usage is over 75%, an alarm with the Error severity level must be triggered.

In such situation, if the memory usage level is constantly growing and exceeds 70%, Veeam ONE will trigger a
warning alarm, notifying about a potentially dangerous situation. If the memory usage level keeps on growing
and exceeds the level of 75%, Veeam ONE will trigger an error alarm notifying about severe danger.

11 | Veeam ONE | Working with Alarms | REV 7

Alarm Assignment Options
Veeam ONE alarms are assigned to objects of the backup or virtual infrastructure. There are several options for
assigning alarms:

 Object-level assignment — you can assign an alarm to a single object.

This type of assignment can be useful if you need to customize alarms for specific objects, like separate
hosts, VMs or backup infrastructure components.

 Group-level assignment — you can assign an alarm to a group of objects (for example, to an
infrastructure container or Veeam ONE Business View group).
This type of assignment can be useful if you need to assign an alarm to all objects under a specific
parent entity, for example, to all VMs residing on a host or to all backup proxies connected to a backup
server.

 Infrastructure-level assignment — you can assign an alarm to all objects of a particular type in the
entire managed environment.
This is the default type of assignment used for all predefined alarms.

You can combine various assignment options. For example, an alarm can be assigned to all VMs running on a
chosen host, to all VMs in a Veeam ONE Business View group and to a few single VMs at the same time.

In addition to flexible alarm assignment options, Veeam ONE offers a possibility to exclude specific objects or
object groups from the assignment scope. Thus, you can easily point out what part of your environment the
alarm must ‘disregard’.

12 | Veeam ONE | Working with Alarms | REV 7

Alarm Response Actions
Every alarm performs a specific action when it gets triggered. Depending on its configuration, an alarm can:

 Send email notifications to the default notification group or to specific recipients

 Send SNMP traps to third-party consoles

 Run a custom script

 Perform two or all of these actions at once

Alarm actions are defined in alarm settings. You can specify in which cases Veeam ONE must perform response
actions:

 Alarm severity changes to Error

 Alarm severity changes to Error or Warning

 Alarm severity changes to any level (Error, Warning or Info)

By default, all predefined alarms are configured to send email notifications to the default notification group when
the alarm severity changes from one level to another. You can change alarm actions and define conditions when
these actions should be performed.

13 | Veeam ONE | Working with Alarms | REV 7

Advanced Alarm Options
To avoid alarm storms and ensure that critical issues are not overlooked, you can use advanced alarm
configuration options — alarm suppressing and alarm modelling.

 Alarm suppressing is used to disregard events and prevent sending alarms when specific activities are
performed. For example, during backup Veeam ONE may send a great number of alarms informing about
potential problems or increased resource pressure. Alarms suppressing allows you to 'switch off' alarms
during such activities, or at a specific period of time, when resource-consuming operations are
performed.

 Alarms modelling is used to verify the created alarm scheme and estimate the need of adjusting alarm
settings. During alarm modelling, Veeam ONE applies alarm settings to collected historical data and
produces a forecast how many alarms will be sent over a specific period of time. If the number of alarms
is too high, alarm thresholds may need to be changed to avoid numerous useless alarms. If the number
is too low, the alarms sensitivity may need to be increased not to miss important issues.

14 | Veeam ONE | Working with Alarms | REV 7

Alarm Reports
In addition to receiving alarms in real-time, Veeam ONE allows you to analyze alarm statistics. You can use
Veeam ONE Reporter dashboards and reports to track how the number of alarms was changing over time,
identify short- and long-term alarm trends, detect the most affected infrastructure objects, troubleshoot
commonly encountered issues and ensure that your infrastructure stays fully reliable and productive.

You can use the following dashboards and reports for analyzing alarms:

 Alarms Dashboard analyzes alarms triggered over the previous week. The dashboard provides
information on the general health state of virtual infrastructure objects, shows daily roll-ups for errors
and warnings, enumerates typical problems and helps detect the most affected VMs, clusters, hosts and
datastores/storages.

 Alarms Overview Report provides an overview of the current health state of the virtual infrastructure,
details the most common alarms and identifies the most affected infrastructure objects. The report
consolidates information about raised alarms and provides a summary for the selected time interval.

 Alarms Current State Overview Report provides information about all currently unresolved alarms,
that is alarms with the Error or Warning severity level, and displays reasons why these alarms were
triggered.

For details on Veeam ONE reports and dashboards, see Veeam ONE Reporter Guide.

15 | Veeam ONE | Working with Alarms | REV 7

Configuring Alarms
Veeam ONE comes with a set of predefined alarms so that you can start monitoring your environment
immediately after installing the solution. You can leave alarm defaults without changes, you can customize
predefined alarms, or create new alarms for specific monitoring conditions.

To access the list of alarms:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. To limit the list of displayed alarms, you can use filter buttons — Show predefined alarms only, Show
custom alarms only, All.

The Alarm Management view is divided into three panes — inventory pane, information pane and actions pane.

 The inventory pane on the left shows the alarm management tree with alarm types (virtual infrastructure
components to which alarms can be applied, vCloud Director components, Veeam Backup & Replication
infrastructure components and internal alarms).

 The information pane contains the list of predefined and custom alarms for the type that is selected in
the alarm management tree. Every alarm is described with the following details: type, name, source,
state (Enabled or Disabled), assignment scope and resolve action (Automatic or Manual). The bottom
section of the information pane displays alarm knowledge base — information on the selected alarm,
such as summary, cause, resolution and external resources.

 The Actions pane on the right displays a list of links for performing alarm actions.

16 | Veeam ONE | Working with Alarms | REV 7

Creating Alarms
If predefined alarms do not cover all important events, conditions or state changes about which you need to be
notified, you can create custom alarms.

To create a new alarm, perform the following steps.

17 | Veeam ONE | Working with Alarms | REV 7

Step 1. Select Alarm Type
All alarms are applied to a certain level of the virtual, vCloud Director or backup infrastructure. The Type
attribute of an alarm defines to what kind of infrastructure objects this alarm applies. The list of available alarm
types is displayed in the inventory pane of the Alarm Management view.

To create a new alarm, select its type first:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. In the alarm management tree, select the necessary object type.

4. In the Actions pane on the right, click the New link.

You can also right-click anywhere in the information pane and choose New from the shortcut menu.

Creating Alarms from Tasks or Events

You can create an alarm that is based on an occurred task or event:

1. Open Veeam ONE Monitor.

2. Choose the necessary view — Infrastructure view, vCloud Director View, Business View or Data
Protection View.

3. Open the Tasks & Events tab of the information pane for a target object.

4. Right-click a task or event in the list, choose Create new alarm from the shortcut menu and then
choose an object type.

Creating Alarms from Performance Chart Counters

You can create an alarm from a performance counter:

1. Open Veeam ONE Monitor.

2. Choose the necessary view — Infrastructure view, vCloud Director View, Business View or Data
Protection View.

3. Open a tab with performance parameters for which you want to create an alarm (for example, Network,
Memory, CPU, etc.).
4. At the bottom of the performance chart, right-click the necessary counter and choose Create new
alarm from the shortcut menu.

18 | Veeam ONE | Working with Alarms | REV 7

Step 2. Specify General Alarm Settings
On the General tab of the Alarm settings window, specify general alarm settings:

1. In the Alarm name field, enter the name of the new alarm.

2. Select the Enable this alarm check box if you want to enable the alarm immediately after you save its
settings.
If the check box is not selected, the alarm settings will be saved, but the alarm will be disabled and will
not raise any notifications.

Note that at this point, the alarm type cannot be changed.

19 | Veeam ONE | Working with Alarms | REV 7

Step 3. Specify Alarm Rules and Severity
On the Rules tab of the Alarm settings window, specify rules for triggering the alarm.

There are two types of rules — state or condition-based rules, and event-based rules. You can add up to 8 rules
of different type to one alarm and link them.

Adding State-Based Rules

Alarms with state or condition-based rules alert about an important condition or state change.

To add a rule for a specific condition or state change:

1. On the Rules tab, click Add.

2. At the Choose Rule Type step of the wizard, choose the Rule for specific conditions or state
trigger type.

3. Click Next, and select the necessary rule condition. Available options depend on an alarm type.

4. At the Define Rule step of the wizard, specify conditions (or other settings, as applicable) for the alarm
rule and the alarm severity.

5. [Optional] Exclude specific objects from the alarm scope.

Some state-based rules can include storage counters (such as virtual storage, datastore, VSAN). By
default, such rules will apply to all storage objects in the alarm scope. For example, if you create an
alarm rule for a host and select a datastore usage counter, this rule will apply to all datastores connected
to the host.
You can exclude specific storage objects from the alarm scope. Excluded objects will not be monitored by
the alarm. To exclude one or more storage objects, specify their names in the Exclude instances field.
Separate object names with semicolon (;).

NOTE:
1. When you specify objects to exclude, use object display names. To learn an exact object display
name, navigate to a performance chart for the necessary object in Veeam ONE Monitor, and
choose a chart view with the necessary counter. You can check the object display name either in
the chart legend or in the Select Devices and Counters window > Devices list. For details, see
Veeam ONE Monitor Guide section Selecting Chart Views and Performance Counters.
2. Names of drives must be specified with the backward slash, for example, C:\; Z:\.

6. Specify alarm severity.

For more information on alarm severity, see Alarm Severity.

7. Select the Enable this rule check box if you want to put the rule in action for the alarm.
If the check box is not selected, the rule settings will be saved, but the rule will be disregarded.

20 | Veeam ONE | Working with Alarms | REV 7

 8. Click Finish.

Adding Event-Based Rules

Alarms with event-based rules alert about specific events that occur in your backup or virtual infrastructure.
These can be events issued by the hypervisor or Veeam Backup & Replication events.

To add an event-based rule:

1. On the Rules tab, click Add.

2. At the Choose Rule Type step of the wizard, select Event based rule.

3. At the Define Rule step of the wizard, specify rule settings:

a. In the Event name field, specify an event that must trigger an alarm.
For a list of Veeam Backup & Replication events, see section Appendix A. Alarms. For a list of
virtual infrastructure events, see VMware vSphere Documentation or Microsoft TechNet library.

b. In the Event text field, specify one or more key words that an event description must contain.
This can be name of a user who initiated an action, name of a changed object, or a specific
action.
You can use ‘*’ (asterisk) and ‘?’ (question) wildcards in the Event name and Event text
fields. The ‘*’ (asterisk) character stands for zero or more characters. The ‘?’ (question mark)
stands for a single character.
For example, if you want to want to receive notifications when users reconfigure VMs on the
host.domain.local host, in the Event name field, specify VmReconfiguredEvent, and in the
Event text field, specify ‘reconfigured * on host.domain.local’. Here the ‘*’ (asterisk) replaces
a name of a reconfigured VM. As a result, the alarm will be triggered each time any user
reconfigures any VM on the host.

c. Specify the alarm severity.

For more information on alarm severity, see Alarm Severity.

21 | Veeam ONE | Working with Alarms | REV 7

 d. In the Ignore after field, enter the number of times the alarm will be triggered before all
further repetitive alarms are suppressed.
For example, an alarm is configured to fire when a host loses its network connection, and the
Ignore after value is set to 1. If a host loses its network connection, an event informing about
connection loss will be raised by the hypervisor, and Veeam ONE will trigger an alarm. All
further events informing about problems with host network connectivity will be ignored until
you resolve the alarm that has already been triggered.
By default, this value is set to 1.

e. In the Trigger after field, enter the number of times an event must repeat before Veeam ONE
must trigger an alarm.
By default, this value is set to 0, which means that Veeam ONE must trigger an alarm after the
first event occurrence.

f. Select the Enable this rule check box if you want to put the rule in action for the alarm.
If the check box is not selected, the rule settings will be saved, but the rule will be disregarded.

4. Click Finish.

Linking Rules
If you add multiple rules to one alarm, Veeam ONE will trigger an alarm when conditions for at least one rule are
met. You can change the default way of evaluating alarm rules and link rules using Boolean AND or OR
operators. For example, if an alarm must be triggered when conditions for two rules are met simultaneously, you
can link these rules with Boolean AND.

To link alarm rules:

1. Make sure that rules you want to link follow one another in the list. You cannot link rules that do not
follow one another. For example, you cannot link the first and the fifth rule.
To move a rule one position up, select the check box next to the rule and click Move up. To move a rule
one position down, select the check box next to the rule and click Move down.

2. Select check boxes next to rules you want to link, and click Link on the right.

22 | Veeam ONE | Working with Alarms | REV 7

 3. In the Rule condition window, select a condition:

 AND — if rules are linked with this operator, an alarm is triggered when conditions for all
linked rules are met.

 OR — if rules are linked with this operator, an alarm is triggered when a condition for any of
the linked rules is met.

4. Click Apply.
After you link two or more rules, Veeam ONE will display a dotted line and a linking condition between
the rules.

To unlink rules:

1. Select the check box next to linked rules.

2. On the right, click Unlink.

When you unlink rules, you cancel a custom condition so that an alarm will be triggered each time conditions for
any alarm rule are met.

23 | Veeam ONE | Working with Alarms | REV 7

Removing Rules
To remove a rule from an alarm:

1. Select the check box next to a rule you want to remove.

2. On the right, click Remove.

24 | Veeam ONE | Working with Alarms | REV 7

Step 4. Specify Alarm Assignment
On the Assignment tab of the Alarm settings window, specify one or more infrastructure objects to which the
alarm must be assigned.

Adding Objects to Alarm Assignment Scope

To add one or more objects to alarm assignment scope:

1. On the Assignment tab, in the Assignment for alarm section, click Add.

2. From the list, select the necessary node — Infrastructure tree, Business View, vCloud Director View or
Data Protection.

3. In the Assign Alarm window, select check boxes next to objects to which you want to assign the alarm.

4. Click Assign.

To remove an object from the alarm assignment:

1. On the Assignment tab, in the Assignment for alarm section, select an object you want to remove
from the assignment.

25 | Veeam ONE | Working with Alarms | REV 7

 2. On the right, click Remove.

Excluding Objects from Alarm Assignment Scope

You can exclude specific objects from alarm assignment scope:

1. On the Assignment tab, in the Excluded objects section, click Add.

2. From the list, select the necessary node — Infrastructure tree, Business View, vCloud Director View or
Data Protection View.

3. In the Exclude Alarm window, select check boxes next to objects you want to exclude from alarm
assignment.

4. Click Exclude.

26 | Veeam ONE | Working with Alarms | REV 7

Step 5. Specify Alarm Actions
On the Actions tab of the Alarm settings window, specify what actions must be performed after the alarm is
triggered, or after the alarm status changes. You can choose to notify virtual infrastructure administrators by
email, send SNMP traps or run a custom script.

NOTE:

To be able to receive email and trap notifications, you must first configure mail and trap notification settings in
the Veeam ONE Monitor Configuration Wizard or in Veeam ONE Monitor server settings. To learn how to
configure notification settings for alarms, see Configuring Alarm Notification Settings.

To define alarm response actions:

1. From the Action list, select the necessary action:

 Send email to a default group is the default action that applies to all new and predefined
alarms. Select this option if you want to send an email notification to all recipients included in
the default email notification group when the alarm is triggered or when the alarm status
changes.
For more information see Email Notifications.

 Send email notification — select this option if you want to send an email notification to
specific recipients when the alarm is triggered or when the alarm status changes. In the Value
field, enter recipients’ email addresses. If you want to specify several recipients, separate email
addresses with semicolon (;), comma (,) or space ( ).
For more information see Email Notifications.

 Send SNMP trap — select this option if you want to send a Simple Network Management
Protocol (SNMP) trap when the alarm is triggered or when the alarm status changes.
For more information, see SNMP Traps.

 Run script — select this option if you want to run a custom script when the alarm is triggered
or when the alarm status changes. By running a script, you can automate routine tasks that are
normally performed when specific alarms fire. For example, if a critical system is affected, you
may need to immediately open a ticket with the in-house support or perform some corrective
actions that will eliminate the problem.
In the Value field, enter the path to the executable file. The executable file must be located on
the machine running the Veeam ONE Server component. You can use the following parameters
in the command line for running the script: %1 — alarm name; %2— affected node name; %3
— alarm summary; %4 — time; %5 — alarm status; %6 — old alarm status.

2. In the Condition field, describe when the action must be performed:

 Errors and warnings — select this option if the action must be performed every time when
the alarm status changes to Error or Warning.

 Errors only — select this option if the action must be performed every time when the alarm
status changes to Error.

 Any state — select this option if the action must be performed every time when the alarm
status changes to Error, Warning or Info.

27 | Veeam ONE | Working with Alarms | REV 7

You can specify multiple response actions for the same alarm. To add a new action, click the Add button and
repeat steps 1-2 for every new action.

28 | Veeam ONE | Working with Alarms | REV 7

Step 6. Configure Alarm Suppression Settings
In some cases, you might need to suppress alarms that occur under specific conditions or during a specific time
interval. For example, alarms informing about high resource utilization may need to be suppressed if these
alarms occur during a scheduled resource consuming operation (such as backup performed with Veeam Backup
& Replication or other operations).

For suppressed alarms, Veeam ONE does not show any notifications and does not perform any response actions.
If, by the end of suppression period, the object stays affected, Veeam ONE will trigger the alarm with the
corresponding severity and will perform the alarm response actions.

On the Suppress tab of the Alarm settings window, specify alarm suppression settings.

Suppressing Alarm During Events

To suppress the alarm under specific conditions or when a specific event occurs, choose one of the following
options:

 Veeam Backup activity — suppresses the alarm when Veeam backup and replication jobs are running.
Veeam ONE detects the beginning and the end of jobs and does not trigger the alarm while the jobs are
running.
For example, if you select Veeam Backup activity check box for the VM CPU Usage alarm, this alarm
will be suppressed for all VMs that are being backed up or replicated — until the jobs are finished.
If you select the Veeam Backup activity check box for the Host CPU Usage alarm, this alarm will be
suppressed for the entire host where at least one VM is being backed up or replicated — until the jobs
are finished.

 Snapshot creation — suppresses the alarm during snapshot creation for the object itself or its parent
objects.
For example, if you create an alarm for a VM, the alarm will be suppressed for a VM while a snapshot is
being created. If you create an alarm for a host, the alarm will be suppressed for the host while a
snapshot is being created for any VM on this host.

 Snapshot deletion — suppresses the alarm during snapshot deletion for the object itself or its parent
objects.
For example, if you create an alarm for a VM, the alarm will be suppressed for a VM while a snapshot is
being deleted. If you create an alarm for a host, the alarm will be suppressed for the host while a
snapshot is being deleted for any VM on this host.

NOTE:
1. To enable the Veeam Backup activity option, make sure that you connected a Veeam Backup & Replication
server to Veeam ONE. Otherwise, alarms will not be suppressed during Veeam Backup activity.
2. Snapshot creation and Snapshot deletion suppression options apply to VMware vSphere alarms only.

Scheduled Alarm Suppression

To suppress the alarm according to a specific schedule during the week:

1. Select the Suppress alarm based on schedule option.

2. Specify time intervals on specific weekdays during which the alarm must be suppressed.

29 | Veeam ONE | Working with Alarms | REV 7

You can add more than one record for one weekday. Note that the time intervals specified for the same day
must not intersect.

30 | Veeam ONE | Working with Alarms | REV 7

Step 7. Specify Alarm Details
On the Knowledge base tab of the Alarm settings window, specify alarm details. Alarm details are displayed
when you select the alarm in the Alarm Management view or on the Alarms monitoring dashboard in Veeam
ONE Monitor, and included in alarm email notifications.

1. In the Knowledge, Cause and Resolution fields, specify alarm details, what could cause the alarm
and steps to resolve the alarm.

2. In the External field, provide links to external resources containing reference information, such as
VMware vSphere Documentation or Microsoft TechNet Library.

3. In the Custom field, specify additional information, such as comments of additional instructions.

31 | Veeam ONE | Working with Alarms | REV 7

Step 8. Save Alarm Settings
Review the specified alarm settings, click OK to save the alarm.

32 | Veeam ONE | Working with Alarms | REV 7

Modifying Alarms
You can modify settings of a predefined or a custom alarm:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. Select an alarm in the list and do one of the following:

 Double click the alarm.

 Right-click the alarm and choose Edit from the shortcut menu.

 In the Actions pane, click Edit.

4. Change the necessary alarm settings.

For details on working with alarm settings, see Creating Alarms.

Other Ways to Modify Alarms

You can also modify alarms on the Alarms tab of the Infrastructure View, Business View, vCloud Director View
or Data Protection View.

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director View or Data Protection View.

3. In the inventory pane, select the necessary infrastructure object.

4. In the information pane, open the Alarms tab.

5. To open the Alarm settings window, do one of the following:

 Right-click the alarm and choose Edit alarm from the shortcut menu.

 Select the alarm in the list and click Edit alarm in the Actions pane on the right.

6. Change the necessary alarm settings.

For details on working with alarm settings, see Creating Alarms.

Modifying Multiple Alarms

Veeam ONE supports batch alarm editing. In the batch editing mode, you can change only the Actions and
Suppression alarm settings.

To modify settings of several alarms in batch:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

33 | Veeam ONE | Working with Alarms | REV 7

 3. Select the necessary alarms in the list using the [CTRL] or [SHIFT] key on the keyboard and do one
of the following:

 Right-click the selection and choose Edit from the shortcut menu.

 Click Edit in the Actions pane on the right.

4. Change the actions or suppression settings.

For details on working with alarm settings, see Creating Alarms.

34 | Veeam ONE | Working with Alarms | REV 7

Adding Alarm Rule from Task or Event
You can to an alarm a new rule based on a task or event that occurred in the managed environment. For
example, you can create a rule that monitors the event ‘Create virtual machine’ and notifies you whenever a new
VM is created.

To create a new rule from a task or event:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director View or Data Protection View.

3. In the inventory pane on the left, select the necessary object.

4. In the information pane, open the Tasks & Events tab.

5. Right-click a task or event about which you want to be notified, select Add this even to the existing
alarm from the shortcut menu, and choose the necessary infrastructure object type.

6. In the Select Alarms window, choose an alarm to which the rule must be added and click Add.

7. In the Alarm Settings window, change the rule settings, and click Save.
For details on working with alarm rules, see Step 3. Specify Alarm Rules and Severity.

8. In the Select Alarms window, click Close.

35 | Veeam ONE | Working with Alarms | REV 7

Adding Alarm Rules from Performance Counters
You can add to an alarm a new rule based on a performance counter.

NOTE:

You can use this option with objects for which Veeam ONE collects performance data. For objects that do not
have any performance data, such as datacenters and clusters, this option is not available.

To create a new rule from a performance counter:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director View or Data Protection View.

3. In the inventory pane on the left, select the necessary object.

4. Open a tab with performance parameters for which you want to create an alarm (for example, Network,
Memory, CPU, etc.).
5. At the bottom of the performance chart, right-click the necessary counter and choose Add this counter
to the existing alarm from the shortcut menu.

6. In the Select Alarms window, choose an alarm to which the rule must be added and click Add.

7. In the Alarm Settings window, change the rule settings, and click Save.
For details on working with alarm rules, see Step 3. Specify Alarm Rules and Severity.

8. In the Select Alarms window, click Close.

36 | Veeam ONE | Working with Alarms | REV 7

Changing Alarm Assignment Scope
By default, all predefined alarms are assigned to the root level of the managed infrastructure. Alarms for
monitoring the virtual environment apply to the root level of the virtual infrastructure (connected vCenter Server,
SCVMM, failover cluster of host), vCloud Director alarms apply to the root vCloud Director level and Veeam
Backup & Replication alarms apply to the root level of the backup infrastructure (connected backup server or
Veeam Backup Enterprise Manager).

You can change the alarm assignment scope for predefined and custom alarms, exclude one or more objects
from the alarm scope, or even exclude an object from the scope of multiple alarms at once.

37 | Veeam ONE | Working with Alarms | REV 7

Modifying Alarm Assignment Scope
To modify assignment scope of one or more alarms:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. In the alarm management tree, select the necessary type of infrastructure objects.

4. Select one or more alarms in the list and do one of the following:

 Right-click the alarm and choose Edit assignment from the shortcut menu.

 In the Actions pane on the right, click Edit assignment.

5. In the Edit assignment window, select the effective assignment rules and click Remove.

6. Click Add and choose one of the following options:

 Infrastructure tree — choose this option if you want to assign the alarm to a specific level of
the virtual infrastructure.
You can select infrastructure objects that match the alarm type or choose containers from the
virtual infrastructure hierarchy. For example, you can assign an alarm of the Virtual Machine
type to a specific VM, resource pool, host, cluster, datacenter or vCenter Server or SCVMM
server.

 Business View — choose this option if you want to assign the alarm to custom categorization
groups that you have configured in Veeam ONE Business View.
For example, if VMs in your environment are divided into SLA groups, you can create a set of
alarms that correspond to specific service level requirements and assign these alarms to the
necessary SLA group.

 vCloud Director View — choose this option if you want to assign the alarm to a certain level
of your vCloud Director infrastructure.
You can select infrastructure objects that match the alarm type or choose containers from the
vCloud Director hierarchy. For example, you can assign an alarm of the vCloud Director vApp
type to a specific vApp, organization VDC, organization or vCloud Director cell.

 Data Protection View — choose this option if you want to assign the alarm to a certain level
of the Veeam Backup & Replication infrastructure.
You can select backup infrastructure objects that match the alarm type or choose containers
from the backup infrastructure hierarchy. For example, you can assign an alarm of the
Repository type to a specific repository, Veeam backup servers or Veeam Backup Enterprise
Manager.
You can combine various types of alarm assignment options for the same alarm. The type of options you
can combine depends on the alarm type. For example, if an alarm has the Virtual machine type, you can
include in the assignment scope virtual infrastructure, vCloud Director and Veeam ONE Business View
objects.

7. Repeat step 1-5 for all virtual infrastructure objects or categorization groups to which the alarms must be
assigned.

38 | Veeam ONE | Working with Alarms | REV 7

Notes
There are following restrictions for alarm assignment:

 Alarm can be assigned to infrastructure objects that correspond to the alarm type. For example, alarm of
the VM type can be assigned to VMs or to a container that includes VMs.

 The same applies to Veeam ONE Business View groups: the alarm type must match the Business View
category type. You cannot assign an alarm of the Host type to a Veeam ONE Business View group that is
used to categorize VMs.

39 | Veeam ONE | Working with Alarms | REV 7

Excluding Single Objects from Alarm Assignment
Scope
You can exclude a single infrastructure object from alarm assignment:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director View or Data Protection View.

3. In the information pane, open the Alarms tab.

4. Select the necessary alarm in the list and do one of the following:

 Right-click the alarm and choose Exclude from the shortcut menu.

 In the Actions pane on the right, click Exclude.

If you select a container object and choose an alarm that was triggered for its child object, Veeam ONE
will provide two exclusion choices — exclude the child object only or exclude the whole container from
the alarm assignment scope.
For example, you have selected a cluster in the inventory pane. In the list of alarms, you will see alarms
on the cluster and alarms on the hosts in the cluster. If you select an alarm that was triggered for a host,
you can exclude either the host (child object) or the whole cluster (container).

5. Click Yes in the dialog box to confirm exclusion.

NOTE:

When you exclude an object from an alarm, all unresolved Warning or Error notifications that were triggered
by this alarm for the object will change their status to Resolved.

40 | Veeam ONE | Working with Alarms | REV 7

Excluding Multiple Objects from Alarm
Assignment Scope
You can exclude infrastructure objects from the alarm assignment scope:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. Select the necessary alarm in the list and do one of the following:

 Right-click the alarm and select Edit exclusions from the shortcut menu.

 In the Actions pane on the right, click Edit exclusions.

4. In the Edit exclusions window, click Add and choose objects that you want to exclude from the
assignment scope:

 Infrastructure tree — choose this option if you want to select objects from the virtual
infrastructure hierarchy.
You can select objects that match the alarm type or choose parent objects (containers) from
the virtual infrastructure hierarchy. For example, if you work with the alarm of the Virtual
Machine type, you can exclude a specific VM, host, cluster and so on.
 Business View — choose this option if you want to exclude custom categorization groups that
you have previously configured in Veeam ONE Business View, or objects from these groups.
For example, if you do not want to monitor resource usage metrics for VMs that belong to the
QA and RnD departments, you can group VMs by department in Veeam ONE Business View and
then exclude QA and RnD VMs from the alarm assignment scope in Veeam ONE Monitor.

 vCloud Director View — choose this option if you want to select objects from the vCloud
Director hierarchy.
You can select objects that match the alarm type or choose containers from the vCloud Director
infrastructure hierarchy. For example, if you work with an alarm of the vCloud Director vApp
type, you can exclude a specific vApp, organization VDC, organization or vCloud Director cell.

 Data Protection View — choose this option if you want to select objects from the Veeam
Backup & Replication hierarchy.
You can select backup infrastructure objects that match the alarm type or choose containers
from the backup infrastructure hierarchy. For example, if you work with an alarm of the
Repository type, you can exclude specific repositories, Veeam backup servers or Veeam Backup
Enterprise Manager.
You can combine various types of exclusion options for the same alarm. The type of options
you can combine depends on the alarm type. For example, if an alarm has the Virtual machine
type, you can exclude virtual infrastructure, vCloud Director and Veeam ONE Business View
objects from the alarm assignment scope.

5. Repeat step 3 for all virtual infrastructure objects or categorization groups you want to exclude.

6. In the Edit exclusions window, click OK.

41 | Veeam ONE | Working with Alarms | REV 7

Other Ways to Exclude Multiple Objects from Alarm
Assignment
You can also exclude objects from the alarm assignment scope on the Alarms tab of the Infrastructure View,
Business View, vCloud Director View or Data Protection View.

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director View or Data Protection View.

3. In the inventory pane, select the necessary infrastructure object.

4. In the information pane, open the Alarms tab.

5. Repeat steps 2-5 of the procedure above.

42 | Veeam ONE | Working with Alarms | REV 7

Excluding Objects from Multiple Alarms
You can exclude a single infrastructure object from the scope of multiple alarms:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director View or Data Protection View.

3. In the inventory pane, select the necessary infrastructure object.

4. In the information pane, open the Alarms tab.

5. Select an alarm and do one of the following:

 Right-click the alarm and choose Defined alarms in the shortcut menu.

 In the Actions pane on the right, click Defined alarms.

Alternatively, you can right-click the object in the inventory pane and select Alarms > Exclude from the
shortcut menu.

6. In the Defined Alarms window, select check boxes next to alarms from which you want to exclude the
object.

7. Click OK.

43 | Veeam ONE | Working with Alarms | REV 7

Other Ways to Exclude Objects from Multiple Alarms
You can also exclude an object from multiple alarms using the object tree in the inventory pane.

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director View or Data Protection View.

3. In the inventory pane, right-click the necessary object in the inventory pane and select Alarms >
Exclude from the shortcut menu.

4. In the Defined Alarms window, select check boxes next to alarms from which you want to exclude the
object.

5. Click OK.

44 | Veeam ONE | Working with Alarms | REV 7

Viewing Alarm Exclusions
You can view the list of excluded objects for an alarm:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. Select the necessary alarm in the list and click Show all exclusions in the Actions pane on the right.

45 | Veeam ONE | Working with Alarms | REV 7

Copying Alarms
Instead of creating a new alarm from scratch, you can create a copy of an existing alarm and modify its settings.

An alarm copy keeps the same settings as the original alarm, except the alarm assignment — initially, an alarm
copy is not assigned to any virtual infrastructure, vCloud Director objects, Veeam ONE Business View groups or
Veeam Backup & Replication infrastructure components.

To copy an alarm:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. Select the necessary alarm in the list.

Press and hold the [CTRL] or [SHIFT] key on the keyboard to select multiple alarms.

4. Do one of the following:

Right-click the selection and choose Copy from the shortcut menu.

In the Actions pane on the right, click Copy.

What You Can Do Next

After you create an alarm copy, you can change its settings and assignment scope:

1. Find the alarm copy in the list of alarm.

Veeam ONE uses the following pattern for names of alarm copies: 'Copy of <alarm name>'.

2. Change alarm settings and alarm assignment scope.

For details on working with alarm settings, see Creating Alarms.

46 | Veeam ONE | Working with Alarms | REV 7

Disabling and Enabling Alarms
You can disable and enable predefined and custom alarms.

Disabling Alarms
You can disable alarms that you do not use for monitoring:

1. Open Veeam ONE Monitor.

2. At the bottom of the information pane, click Alarm Management.

3. In the information pane, select the necessary alarm.

Press and hold the [CTRL] or [SHIFT] key on the keyboard to select multiple alarms.

4. Do one of the following:

 Right-click the selection and choose Disable from the shortcut menu.

 In the Actions pane on the right, click Disable.

NOTE:

After you disable an alarm, all unresolved Warning or Error notifications that were triggered by this alarm will
change their status to Resolved.

Enabling Alarms
To enable alarms that were previously disabled:

1. Open Veeam ONE Monitor.

2. At the bottom of the information pane, click Alarm Management.

3. In the information pane, select the necessary alarm.

Press and hold the [CTRL] or [SHIFT] key on the keyboard to select multiple alarms.

4. Do one of the following:

 Right-click the selection and choose Enable from the shortcut menu.

 In the Actions pane on the right, click Enable.

47 | Veeam ONE | Working with Alarms | REV 7

Deleting Alarms
You can delete alarms you no longer need for monitoring:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. In the information pane, select the necessary alarm.

Press and hold the [CTRL] or [SHIFT] key on the keyboard to select multiple alarms.

4. Do one of the following:

 Right-click the selection and choose Delete from the shortcut menu.

 In the Actions pane on the right, click Delete.

5. In the displayed dialog box, click Yes to confirm deletion.

NOTE:

When you delete an alarm in the Alarm Management view, Veeam ONE retains its history — all triggered
alarms and alarm status changes will be available on the Alarms view.

The status of a deleted alarm is changed to Resolved. To view history of a deleted alarm, you need to apply
the Show resolved alarms filter. For details on working with triggered alarms, see Viewing Triggered Alarms.

48 | Veeam ONE | Working with Alarms | REV 7

Exporting and Importing Alarms
You can export alarms to an XML file and import alarms from an XML file. Exporting and importing alarms can be
useful if you need to back up you alarm settings, or if you want to copy alarm settings from one Veeam ONE
deployment to another.

You can use export and import possibilities to copy alarm settings between different Veeam ONE versions.
Veeam ONE 9.5 supports import of alarm settings that were exported from Veeam ONE 8.0 and 9.0.

Exporting Alarms
To export alarms to an XML file:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. In the alarm management tree, select the type of infrastructure object for which you want to export
alarms.

4. Right-click the object and choose Export Alarms from the shortcut menu.

5. Save the XML file with alarm settings.

Importing Alarms
To import alarms from an XML file:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. In the alarm management tree, right-click any object and choose Import Alarms from the shortcut
menu.

4. In the Alarms Import window:

 Specify a path to an XML file with alarm settings.

 Select the Import assignment check box if you want to import a list of alarms together with
their assignment settings.

 Select the Replace all existing alarms check box if you want to replace existing alarms with
imported alarms.
If you do not select this check box but during import Veeam ONE detects an alarm with a
matching name, Veeam ONE will suggest you to update settings of the existing alarm with data
from the XML file. You can either replace the existing alarm with the alarm from the XML file, or
leave the existing alarm without any changes.
If an alarm in the XML file does not match any existing alarm by name, Veeam ONE will create
a new alarm.

49 | Veeam ONE | Working with Alarms | REV 7

 5. When the import is finished, the Alarm Import window will display a report with the import status, the
total number of added, replaced and skipped alarms and the number of alarms that were imported with
errors.
Review the report and click Close to close the Import Alarms window.

50 | Veeam ONE | Working with Alarms | REV 7

Suppressing Alarms
During resource-consuming operations, such as backup, Veeam ONE may send a great number of alarms
informing about potential problems or increased resource pressure. If you do not want to receive notifications
during specific activities or at a specific period of time, you can disable alarms for object in your infrastructure.
When alarms are suppressed, Veeam ONE disregards events and state changes to which the alarms react and
does not trigger any alarms.

To suppress alarms, you can use one of the following options:

 Maintenance mode

 Alarm-specific suppression settings

 Suppression of guest disk space alarms

51 | Veeam ONE | Working with Alarms | REV 7

Maintenance Mode
Maintenance mode is used to suppress alarms for specific infrastructure objects during planned maintenance
operations. When you place an infrastructure object to the maintenance mode, Veeam ONE will suppress all
alarms on this object.

You can enable the maintenance mode for single infrastructure objects or containers. When you enable the
maintenance mode for a container, you can choose to suppress alarms on its child objects as well. For example,
if you want to perform maintenance on a host, you can enable the maintenance mode for the host itself and for
all VMs on this host.

You can enable the maintenance mode manually or set a maintenance schedule.

Manual Maintenance Mode

You can enable the maintenance mode for an infrastructure object manually. After you place an infrastructure
object to the maintenance mode manually, Veeam ONE will stop triggering alarms for this object until you
manually disable the maintenance mode.

To enable the maintenance mode for an infrastructure object manually:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the inventory pane, right-click an infrastructure object and choose Maintenance Mode from the
shortcut menu.

4. Choose the scope of objects for which you want to enable the maintenance mode:

 If you choose For this object, the maintenance mode will be enabled for the selected object
only. Alarms on its child objects will not be suppressed.

 If you choose For this and all contained objects, the maintenance mode will be enabled for
the container and its child objects.

After you enable the maintenance mode for an infrastructure object, Veeam ONE will change the infrastructure
object icon, and will display the (Maintenance mode) label next to the object name in the inventory pane.

Scheduled Maintenance Mode

You can configure a maintenance schedule for infrastructure objects. When a schedule is set, the maintenance
mode will be enabled and disabled automatically according to the schedule.

To configure a maintenance schedule:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the inventory pane, right-click an infrastructure object and choose Schedule Maintenance Mode
from the shortcut menu.

4. In the Schedule Maintenance Mode window, configure the maintenance schedule.

a. Click Add.

52 | Veeam ONE | Working with Alarms | REV 7

 b. In the Type field, specify how often the object must be placed into the maintenance mode
(once, monthly, weekly, daily).

c. In the Day/Date field, specify a day when the maintenance mode must be enabled.

d. In the Start time and End time fields, specify the start and end time of the maintenance
period.

e. Select the Apply to child objects check box if you want to enable the maintenance mode on
the object itself and its child objects.

f. In the Comment field, type additional information about the planned maintenance. You can
enter up to 512 characters in this field.

g. Select the Enabled check box to enable the new maintenance schedule.

h. Repeat steps a-g for each new schedule entry you want to add.

5. Click OK.

To temporary disable a maintenance schedule:

1. In the Schedule Maintenance window, clear the Enabled check box next to the necessary schedule
entry.

2. Click OK.

The disabled schedule will remain in the list, but it will not be applied to the object.

To delete a schedule:

1. In the Schedule Maintenance window, select the check box next to the schedule entry you want to
remove.

2. Click Delete.

3. Click OK.

53 | Veeam ONE | Working with Alarms | REV 7

Exiting Maintenance Mode
To exit a scheduled or manual maintenance mode

1. Open Veeam ONE Monitor.

2. Right-click an object in the inventory pane and choose Exit Maintenance Mode.

After you exit the maintenance mode, Veeam ONE will resume triggering alarms.

54 | Veeam ONE | Working with Alarms | REV 7

Alarm-Specific Suppression Settings
For each alarm, you can configure individual suppression settings to 'switch off' the alarm during specific
resource-consuming operations (such as backup). For details on configuring alarm suppression settings, see
Creating Alarms > Step 6. Configure Alarm Suppression Settings.

55 | Veeam ONE | Working with Alarms | REV 7

Suppressing Guest Disk Space Alarms
You can suppress Guest disk space alarms for separate VM guest OS disks:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View or
vCloud Director View.

3. In the inventory pane, choose the necessary VM.

4. In the information pane, open the Summary tab.

5. In the Guest Disk Usage section, click View all disks.

6. In the Guest disks list, select check boxes next to guest OS disks for which alarms must be suppressed.

7. Click OK.

56 | Veeam ONE | Working with Alarms | REV 7

Modelling Alarm Number
Alarm modelling allows you to forecast the number and type of alarms that will be sent for a specific
infrastructure object within a chosen time interval. To model the alarm number, Veeam ONE applies the current
alarm settings to historical data collected for the chosen infrastructure object, and calculates the approximate
number of alarms that will be sent within the specified time interval in future.

Alarm modelling can help you avoid receiving non-significant alarms, or vice versa missing important events.
After you change alarm settings, you can perform alarm modelling to estimate how many alarms will be triggered
for an infrastructure object if you keep the effective alarm settings. Taking into consideration the modeled
number of alarms, you can consider changing alarm settings — for example, if the number is too high, you may
need to adjust alarm rule conditions.

To forecast the number of alarms that will be sent for a specific infrastructure object:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Modelling.

3. In the Alarm Modelling window, click Select and choose the necessary type of infrastructure
objects — Infrastructure View, vCloud Director, Business View or Data Protection View.

4. In the Select Node window, choose an infrastructure object for which you want to model the number of
alarms.

5. In the Use data for the past list, specify the period for which historical data must be analyzed (week,
month or year).

6. In the list of alarms, select check boxes next to alarms for which you want to perform modelling.

7. Click Start Modelling.

Veeam ONE will display the number of alarms of different severity that, according to the forecast, will be sent
within the selected period of time.

Other Ways to Perform Alarm Modelling

To perform alarm modelling for an infrastructure object:

1. Open Veeam ONE Monitor.

57 | Veeam ONE | Working with Alarms | REV 7

 2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, vCloud Director,
Business View or Data Protection View.

3. Do one of the following:

 In the inventory pane, select an infrastructure object and click Modelling on the toolbar.

 In the inventory pane, right-click an infrastructure object and select Alarms > Modelling from
the shortcut menu.

4. Repeat steps 5-7 of the procedure above.

To perform alarm modelling for selected alarms:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. Select the one or more alarms in the list, right-click the selection and choose Modelling from the
shortcut menu.

4. Repeat steps 3-7 of the procedure above.

58 | Veeam ONE | Working with Alarms | REV 7

Configuring Alarm Notifications
To ensure you do not miss critical events or state changes in the managed infrastructure, you can configure
Veeam ONE to send notifications when alarms are triggered. Veeam ONE supports two types of alarm
notifications:

 Email Notifications

 SNMP Traps

59 | Veeam ONE | Working with Alarms | REV 7

Email Notifications
To stay informed about potential problems, state changes, events and tasks performed by users in your
infrastructure, you can configure Veeam ONE to send email notifications about alarms. Email notifications contain
basic information necessary to find the root cause of an issue and resolve it.

An email notification can be sent when a new alarm is triggered or when an existing alarm changes its status.

To configure alarm email notifications, perform the following steps:

1. Configure SMTP server settings.

2. Configure notification frequency.

3. Customize the email template.

4. Configure email recipients.

5. [Optional] Disable notifications about resolved alarms.

Step 1. Configure SMTP Server Settings

To deliver email notifications, Veeam ONE needs an SMTP server.

To configure SMTP settings:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. In the SMTP Server field, specify DNS name or IP address of the SMTP server that must be used for
sending email notifications.

4. In the Port field, change the SMTP communication port if required.

The default port number is 25.

5. In the From field, enter an email address of the notification sender.

This email address will be displayed in the From field of the email header.

6. For a SMTP server with SSL support, select Enable SSL security to enable SSL data encryption.

60 | Veeam ONE | Working with Alarms | REV 7

 7. If your SMTP server requires authentication, select the Use authentication check box and specify
authentication credentials in the Login and Password fields.

Sending Test Email

To check whether you have specified SMTP settings correctly, you can send out a test email:

1. Click Send test email.

2. In the Test email settings window, specify an email address to which a test notification must be sent.

3. Click OK.

The test email will be sent to the specified email address. Veeam ONE will notify you whether the message was
successfully sent.

61 | Veeam ONE | Working with Alarms | REV 7

Step 2. Configure Notification Frequency
Veeam ONE sends an email notification when a new alarm is created or when the status of an existing alarm is
changed. If you do not want to receive an email message each time a new alarm is triggered or alarm status
changes, you can change the notification frequency.

The frequency with which Veeam ONE sends email notifications is defined by notification policy. There are two
types of notification policies:

 Mission Critical

 Other

Enabling Mission Critical Notifications

Mission Critical notification policy is the default policy that is enabled for all infrastructure objects. This policy
prescribes Veeam ONE to send an email notification every time a new alarm is created or the status of an
existing alarm changes. An email notification contains details on the triggered alarm and affected object.

The following image shows an example of an email notification for the Mission Critical policy.

62 | Veeam ONE | Working with Alarms | REV 7

To apply the Mission Critical notification policy to an infrastructure object:

1. Open Veeam ONE Monitor

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. In the Server Settings window, open the Notification Policy tab.

4. In the Email notification policies section, select Mission Critical and click Edit.

5. In the Edit Email Policy window, click Select and choose one of the following options:

 Infrastructure Tree — browse the virtual infrastructure hierarchy and select check boxes
next to objects or infrastructure segments to which the policy settings must apply.

 Business View — browse the Veeam ONE Business View hierarchy and select check boxes
next to groups or infrastructure objects to which the policy settings must apply.

 Data Protection View — browse the Veeam Backup & Replication infrastructure and select
check boxes next to infrastructure components to which the policy settings must apply.

 vCloud Director View — browse the vCloud Director infrastructure and select check boxes
next to infrastructure components to which the policy settings must apply.

6. In the Select Objects window, click Select.

7. In the Edit Email Policy window, Click OK.

Enabling Summary Notifications

Other notification policy prescribes Veeam ONE to accumulate information about alarms and send an email
notification once within a specific time interval (by default, a notification is sent once every 30 minutes).

63 | Veeam ONE | Working with Alarms | REV 7

You do not receive a notification on every triggered alarm. Instead, Veeam ONE generates a message with a list
of all alarms triggered over the past period.

You can choose how often you want to receive summary email notifications. For example, if you specify the time
interval of 15 minutes, you will receive notifications with the list of alarms triggered over the past 15 minutes. If
no alarms are triggered over the past 15 minutes, you will not receive a summary email notification.

The following image shows an example of a summary email notification for the Other policy.

By default, all infrastructure objects have the Mission Critical policy assigned. Before you apply the Other
notification policy to an object, you must remove the default Mission Critical policy assignment:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. In the Server Settings window, open the Notification Policy tab.

4. In the Email notification policies section, select the Mission Critical policy and click Edit.

5. In the Edit Email Policy window, select the necessary type of infrastructure objects — Virtual
Infrastructure, vCloud Infrastructure or Backup Infrastructure) and click Remove.

64 | Veeam ONE | Working with Alarms | REV 7

 6. In the Edit Email Policy window, click OK.

To apply the Other notification policy to one or more infrastructure objects:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. In the Server Settings window, open the Notification Policy tab.

4. In the Email notification policies section, select Other and click Edit.

5. In the Edit Email Policy window, click Select and choose one of the following options:

 Infrastructure Tree — browse the virtual infrastructure hierarchy and select check boxes
next to objects or infrastructure segments to which the policy settings must apply.

 Business View — browse the Veeam ONE Business View hierarchy and select check boxes
next to groups or infrastructure objects to which the policy settings must apply.

 Data Protection View — browse the Veeam Backup & Replication infrastructure and select
check boxes next to infrastructure components to which the policy settings must apply.

 vCloud Director View — browse the vCloud Director infrastructure and select check boxes
next to infrastructure components to which the policy settings must apply.

6. In the Select Objects window, click Select.

7. In the Time interval to send summary email (minutes) field, specify how often Veeam ONE must
send out a summary email informing about triggered alarms. The default time interval is 30 minutes.

8. In the Edit Email Policy window, click OK.

65 | Veeam ONE | Working with Alarms | REV 7

Step 3. Customize Email Template
You can customize the email template used for alarm notifications. In the template, you can change the following
items:

 Email subject and body

 Email format

NOTE:

You can customize the email template for Mission Critical notifications only. You cannot modify the template
for alarm summary notifications sent in accordance with the Other notification policy. For more information on
notification policies, see Step 2. Configure Notification Frequency.

Configuring Email Subject and Body

You can customize the email notification subject:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. In the Server Settings window, open the Notification Policy tab.

4. In the Email notification policies section, select Mission Critical and click Edit template.

5. In the Email subject template field, specify the subject of the notification.
You can use the following variables in the subject text:

 %ALARM_NAME% — name of the alarm

 %TIME% — date and time when the alarm was triggered or when the alarm status changed
 %STATUS% — current alarm status
 %OLD_STATUS% — status of the alarm before its status was changed
 %OBJECT% — affected infrastructure object
 %OBJECT_TYPE% — type of the affected infrastructure object
6. In the Select additional fields to include to the email notifications section, select check boxes
next to options you want to include in the body of the email message.
General options apply to email notification for all types of alarms.

 KB article — select this check box if an email notification must include a knowledge base
article.

 Business View group — select this check box if an email notification must include a category
assigned to the object in Veeam ONE Business View.
VM options apply to email notifications for VM alarms.

 Guest OS IP address — select this check box if an email notification must include IP and MAC
addresses of the affected VM.

66 | Veeam ONE | Working with Alarms | REV 7

  Guest OS type — select this check box if an email notification must include information about
the guest OS of the affected VM.

 Guest OS hostname — select this check box if an email notification must include a DNS name
of the affected VM.

 Notes — select this check box if an email notification must include custom notes that can be
specified in alarm details.

7. Click OK.

Configuring Email Format

By default, Veeam ONE sends email notifications in the HTML format. You can change notification format to plain
text. Note that plain text notifications do not support HTML elements, formatted text, colors or graphics. Plain
text notifications also do not include knowledge base articles.

To choose the email notification format:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. On the SMTP Settings tab, in the Email format section, choose a format: HTML or Plain Text.

67 | Veeam ONE | Working with Alarms | REV 7

 4. Click OK.

Step 4. Configure Email Recipients

To report about triggered alarms by email, Veeam ONE must know where to deliver messages. When you
configure alarm notifications, you must specify email addresses of users who will receive these notifications.

There are several options for configuring email notification recipients:

 You can add recipients to the default email notification group.

This option can be useful if you want to notify responsible personnel when critical alarms are triggered or
when alarms change their statuses.

 You can configure recipients for individual alarms.

This option can be useful if you want to notify responsible personnel when a specific event occurs in the
managed infrastructure.

Configuring Default Email Notification Group

The default email notification group includes a list of recipients who must be notified about alarms by email. All
predefined alarms are configured to send email notifications to the default notification group. You can also
configure custom alarms to send notifications to the default notification group.

To add recipients to the default email notification group:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. Open the Notification Policy tab.

4. In the Default email notifications group section, click Configure.

5. In the Default Email Notification Group window, specify email addresses of notification recipients.
To add a recipient, in the Add this recipient field enter recipient’s email address and click Add.

68 | Veeam ONE | Working with Alarms | REV 7

 6. From the Notification Level list, choose the severity of alarms about which recipients must be notified:

 Any state — an email notification will be sent every time when an alarm status changes to
Error, Warning or Info.
 Errors and warnings — an email notification will be sent every time when an alarm
status changes to Error or Warning.

 Errors only — an email notification will be sent every time when an alarm status changes
to Error.

7. Click OK.

You can temporary disable email notifications for specific recipients in the default email notification group. The
recipients will remain in the list, but they will no longer receive email notifications on triggered alarms.

1. In the Default Email Notification Group window, clear the check box next to recipient’s email
address.

2. Click OK.

To permanently remove a recipient from the default email notification group:

1. In the Default Email Notification Group window, select an email address you want to delete and click
Remove.

2. Click OK.

Configuring Recipients for Specific Alarms

You can add email notification recipients to each alarm individually and specify alarm severity about which the
recipients must be notified.

To add one or more recipient to a specific alarm:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

69 | Veeam ONE | Working with Alarms | REV 7

 3. Open the Alarm settings window for the necessary alarm:

 Double click the alarm in the list.

 Right-click the alarm and choose Edit from the shortcut menu.

 Select the alarm in the list and click Edit in the Actions pane on the right.

4. In the Alarm settings window, open the Actions tab.

5. On the Actions tab, click Add.

6. From the Action list, select the Send alarm notification option.

7. In the Value field, specify an email address of the recipient.

If you want to specify several recipients, separate email addresses with ";" (semicolon), "," (comma) or
", " (comma with space).

8. From the Condition list, choose the severity of alarms about which the recipient must be notified:

 Any state — an email notification will be sent every time when an alarm status changes to
Error, Warning or Info.
 Errors and warnings — an email notification will be sent every time when an alarm status
changes to Error or Warning.

 Errors only — an email notification will be sent every time when an alarm status changes to
Error.
9. Click Save.

Step 5. Disable Notifications About Resolved and

Acknowledged Alarms
By default, Veeam ONE sends an email notification when an alarm is triggered, when its status changes to Error,
Warning, when an alarm is resolved and acknowledged. If you do not want to receive notifications on resolved
and acknowledged alarms, you can disable them.

70 | Veeam ONE | Working with Alarms | REV 7

To disable email notifications on resolved and acknowledged alarms:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. In the Server Settings window, open the Notification Policy tab.

4. In the Miscellaneous section, clear the Send notification when alarm metrics are back to
normal check box.

5. Click OK.

71 | Veeam ONE | Working with Alarms | REV 7

SNMP Traps
If you use SNMP to monitor applications and devices in the managed infrastructure, you can configure Veeam
ONE to report about triggered alarms by means of SNMP traps. When SNMP trap notifications are enabled,
Veeam ONE acts as an agent. It generates trap messages when an alarm is triggered, and sends them to SNMP
receivers. SNMP receivers can then forward the traps to a management application.

SNMP traps sent by Veeam ONE include the following information:

 Date and time the alarm was triggered

 Name of the affected node

 Old alarm status

 New alarm status

 Alarm name

 Alarm summary

Veeam ONE supports SNMP versions 1, 2 and 3.

To configure SNMP traps, perform the following steps:

1. Configure SNMP receivers and manager.

2. Configure SNMP settings in Veeam ONE.

3. Change alarm action settings to enable SNMP traps for the necessary alarms.

Step 1. Configure SNMP Receivers and Manager

To receive and process SNMP traps generated by Veeam ONE, you must install and configure:

1. SNMP receivers that will listen for traps.

2. SNMP management application that will obtain and process traps from receivers.

The configuration procedure depends on the SNMP processing solution you use to handle traps. For example, to
learn how to configure an SNMP receiver in Windows Server, see SNMP Traps in Windows Server. To learn how
to configure an SNMP receiver with Net-SNMP, see SNMPTRAPD.

Step 2. Configure SNMP Settings in Veeam ONE

To send SNMP traps, Veeam ONE must know trap destinations. You must specify a list of receivers to which
Veeam ONE must send traps, and ports that SNMP receivers will be listening.

To configure SNMP trap destination settings in Veeam ONE:

1. Open Veeam ONE Monitor.

2. On the toolbar, click Options and select Server Settings.

Alternatively, press [CTRL + S] on the keyboard.

3. In the Server Settings window, open the SNMP tab.

72 | Veeam ONE | Working with Alarms | REV 7

 4. Click Add and configure receiver settings:

a. Double-click the added entry in the list.

Alternatively, select the receiver entry and click Configure.

b. In the Receiver field, specify FQDN or IP address of the SNMP receiver.

c. In the Port field, specify the port number.

The default SNMP port is 162.

d. In the Community string field, specify the community identifier.

e. Click OK.

f. To add a new receiver to the list, click Add and repeat steps a-e.
You can send trap notifications up to 4 different destinations.

5. In the list of SNMP receivers, choose the version of the SNMP protocol.

6. Click OK.

Step 3. Enable SNMP Notification for Alarms

To receive SNMP traps when an alarm is triggered, you must set SNMP notification as a response action for each
alarm manually.

To configure SNMP traps for an alarm:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. To open the Alarm settings window for the necessary alarm, do one of the following:

 Double click the necessary alarm in the list.

 Right-click the alarm and choose Edit from the shortcut menu.

73 | Veeam ONE | Working with Alarms | REV 7

  Select the alarm in the list and click Edit in the Actions pane on the right.

4. In the Alarm settings window, open the Actions tab.

5. On the Actions tab, click Add.

6. From the new Action list, select Send SNMP trap.

7. In the Condition field, specify at which state Veeam ONE must send trap messages.

8. Click Save.

74 | Veeam ONE | Working with Alarms | REV 7

Examples: How to Create Alarms
This section provides examples of how to create Veeam ONE alarms.

75 | Veeam ONE | Working with Alarms | REV 7

How to Create Alarm Notifying About Multiple
Snapshot Problems
This example shows how to create an alarm that notifies about multiple snapshot problems. The example is
based on the following scenario:

Users in your organization often forget to delete snapshots they do not use. You want Veeam ONE to notify the
administrator by email about VMs with multiple snapshot problems, such as large and outdated snapshots.

To detect problems with forgotten snapshots, you can create an alarm based on two already existing alarms:
Latest snapshot age and Latest snapshot size:
1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. In the alarm management tree, select All Alarms > VMware > Virtual Machine.

4. In the Actions pane on the right, click the New link.

5. In the Alarm Settings window, open the General tab and specify the alarm name — Multiple snapshot
problems.
6. Open the Rules tab and add two rules that are based on existing alarms:

 Latest snapshot size

 Latest snapshot age

7. Select check boxes for both rules and click Link on the right. In the Rule condition window, choose
AND and click OK.

76 | Veeam ONE | Working with Alarms | REV 7

 According to these joint rules, the alarm will be used to track snapshots that are large and outdated at
the same time.

8. Open the Assignment tab and do the following:

a. In the Assignment for alarm section, click Add and select Infrastructure tree.

b. Select an infrastructure object to which the alarm must be assigned.

c. Click Assign.

9. Open the Actions pane and do the following:

a. Select the default action.

b. From the Actions list, select Send email notification.

77 | Veeam ONE | Working with Alarms | REV 7

 c. In the Value filed, specify an email address of the virtual infrastructure administrator who must
receive alarm notifications by email.

d. From the Conditions list, select Errors and warnings.

10. Click Save.

Expected Result
The Multiple snapshot problems alarm is based on existing alarms: Latest snapshot age and Latest snapshot size.
Default thresholds for these alarms are:

 If the age of the latest snapshot is more than 48 hours, an Error alarm is triggered.

 If the size of the latest snapshot is more than 10% of the VM size, a Warning alarm is triggered. If the
size of the latest snapshot is more than 20% of the VM size, an Error alarm is triggered.

According to these settings, Veeam ONE:

 Will trigger a Multiple snapshot problem Warning alarm for VMs that have snapshots with the age more
than 48 hours and size more than 10% but less than 20%.

 Will trigger a Multiple snapshot problem Error alarm for VMs that have snapshots with the age more than
48 hours and size more than 20%.

The administrator will be notified about Warning and Error alarms by email.

78 | Veeam ONE | Working with Alarms | REV 7

How to Create Alarm Notifying About Increased
Host Disk Latency
This example shows how to add a rule to an existing alarm to get notifications about Hyper-V host disk latency
caused by memory pages usage. The example is based on the following scenario:

VMs on a Hyper-V host are trying to consume more RAM than there are memory resources available on a host.
This makes operating system swap the content of memory to disk. This negatively affects the performance and
causes host disk latency. You want to get notifications when Veeam ONE detects host disk latency caused by the
increased hard page faults. This way you will find out that VMs lack RAM.

To create a custom alarm:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. In the information pane, search for the Host Memory Pages Usage alarm.

4. Right-click the Host Memory Pages Usage alarm and select Copy.
The new alarm Copy of Host Memory Pages Usage will appear in the list.

5. Double-click the Copy of Host Memory Pages Usage alarm.

6. On the General tab of the Alarm Settings window:

a. Change alarm name to 'Disk Latency Caused by Hard Page Faults'.

b. Select the Enable this alarm check box.

c. Click Save.

7. At the bottom of the inventory pane, click Infrastructure View.

8. In the inventory pane, click the necessary Hyper-V host.

9. In the information pane, open the Disk tab.

79 | Veeam ONE | Working with Alarms | REV 7

 10. Below the chart, in the Chart views list, select Disk Latency.

11. In the Performance chart legend section, right-click a latency counter and select Add this counter
to the existing alarm.

12. In the Select Alarm window, search for the Disk Latency caused by Hard Page Faults alarm and click
Add.

13. In the Alarm Settings window, open the Rules tab.

14. For the new counter Disk/Host: Avg Disk sec/read, specify triggering thresholds:

 Warning: 70 Milliseconds

 Error: 90 Milliseconds

 Time period: 10 minutes

15. Select the check boxes of the two rules and click Link.

80 | Veeam ONE | Working with Alarms | REV 7

 16. In the Rule condition window, select the And rule and click OK.

17. Click Save.

Expected Result
 Each time hard page faults cause disk latency of 70 milliseconds, Veeam ONE will trigger a Warning
alarm.

 If disk latency caused by hard page faults reaches 90 milliseconds, Veeam ONE will trigger the Error
alarm.

81 | Veeam ONE | Working with Alarms | REV 7

Working with Triggered Alarms
You can perform the following actions with alarms that were triggered by Veeam ONE:

 View triggered alarms

 Resolve alarms

 Acknowledge alarms

 View alarm history

 Export triggered alarms

82 | Veeam ONE | Working with Alarms | REV 7

Viewing Triggered Alarms
To view alarms triggered for a specific infrastructure object:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the inventory pane, select the necessary object.

4. In the information pane, open the Alarms tab.

The list of alarms shows alarms triggered for the selected infrastructure object and alarms for child objects.

For every alarm, the following details are available:

 Status — current status of the alarm (Warning, Error, Resolved, Info or Acknowledged). If an alarm was
triggered multiple times, its latest state will be displayed in the list.

 Alarm time — date and time when the alarm was triggered. If the alarm was triggered multiple times,
the latest date time when the alarm was triggered will be displayed in the list.

 Source — name of the infrastructure object that caused the alarm. To view all alarms related to the
infrastructure object, click the source link.

 Type — type of the infrastructure object that caused the alarm.

 Name — alarm name. Click the name link to open alarm details in the Alarm Management section.
If a corresponding alarm has been already deleted and not available in the Alarm Management
section, the alarm name is shown as plain text.

 Repeat count — the number of times the alarm was triggered. Click the repeat count link to view the
alarm history.
For more details, see Viewing Alarm History.

83 | Veeam ONE | Working with Alarms | REV 7

The Alarm details section of the information pane displays knowledge base for the selected alarm — description
of the problem, possible causes, instructions for resolution, links to external resources and other details.

The Actions pane on the right displays links to actions that you can perform against triggered alarms, as well as
navigation links.

Finding Alarms
To quickly find the necessary alarms, you can use filters and controls at the top of the Alarms list.

You can limit the list of alarms by the following criteria:

 To display or hide alarms with a specific severity, click the Status icons — Show all alarms, Show objects
with errors, Show objects with warnings, Show resolved alarms, Show information messages and Show
acknowledged messages.
 To display or hide alarms for a specific type of infrastructure objects, click the object type icons — Show
alarms for all types of objects or Show [object type] alarm.
 To display alarms that are related to the selected infrastructure object, use the This object icon.
Release the icon to display alarms for the selected infrastructure object and alarms for its child objects.
Press the icon to display alarms for the selected object only.

 To set the time interval within which alarms were triggered, use the Filter alarms by time period icon
and set the necessary time interval. Release the icon to discard the time interval filter.

 To find alarms by alarm name, use the search field.

You can click column names to sort alarms by a specific parameter. For example, to view repetitive alarms, you
can sort alarms in the list by Repeat Count in the descending order.

84 | Veeam ONE | Working with Alarms | REV 7

Resolving Alarms
Veeam ONE alarms can be resolved automatically or manually.

Alarms are resolved automatically in the following cases:

 When an alarm is disabled or deleted.

 When an object that caused the alarm is deleted or excluded from the alarm assignment scope.

 When conditions that caused the alarm are eliminated, and the alarm is configured to react to this (the
alarm resolve action is automatic).
For example, some alarms are configured to change the alarm severity to Resolved in specific cases or
events that occur in the managed infrastructure. Other alarms (such as alarms that are triggered when
resource usage is above a certain threshold) are resolved automatically when the resource usage level is
back to normal.

You can manually resolve alarms if the state of the monitored object has returned back to normal, and/or if the
alarm requires no further investigation and no corrective actions should be taken.

85 | Veeam ONE | Working with Alarms | REV 7

Resolving Individual Alarms
To resolve individual alarms:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the inventory pane, select the necessary object.

4. In the information pane, open the Alarms tab.

5. In the list of alarms, select one or more alarms and do one of the following:

 Right-click the selection and choose Resolve from the shortcut menu.

 Select one or more alarms in the list and click Resolve in the Actions pane.
Press and hold the [CRTL] or [SHIFT] key to select several alarms.

6. In the Resolve Alarm window, specify a reason for changing the alarm status, or add any other
information.
The message you specify will be available in the Comment field of the alarm history details, and in the
email notification on resolved alarms. For more information, see Viewing Alarm History and Notifications
on Resolved Alarms.

7. Click OK.

86 | Veeam ONE | Working with Alarms | REV 7

Resolving Multiple Alarms
To resolve a number of alarms at once:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the inventory pane, select the necessary object.

4. In the information pane, open the Alarms tab.

5. In the list of alarms, display all alarms that you want to resolve.
Use the filters and the search field at the top of the list to display the necessary alarms.

6. Do one of the following:

 Right-click anywhere in the list of alarms and choose Resolve all alarms from the shortcut
menu.

 In the Actions pane, click Resolve all alarms.

7. In the Resolve Alarm window, specify a reason for changing the alarm status, or add any other
information.
The message you specify will be available in the Comment field of the alarm history details, and in the
email notification on resolved alarms. For more information, see Viewing Alarm History and Notifications
on Resolved Alarms.

8. Click OK.

87 | Veeam ONE | Working with Alarms | REV 7

Notifications on Resolved Alarms
When one or more alarms are resolved, Veeam ONE sends an email notification to users who monitor the
affected object. The notification includes information about the number of alarms resolved, resolve action, time
and reason, as well as the list of resolved alarms.

To receive a notification about resolved alarms, make sure that:

 You have configured SMTP Server settings.

For details, see Step 1. Configure SMTP Server Settings.

 Your email address is included either in the default notification group, or in the list of notification
recipients specified in the alarm action settings, and the notification level is set to Any state.
For details, see Step 4. Configure Email Recipients.

 Notifications about resolved and acknowledged alarms are enabled.

For details, see Step 5. Disable Notifications About Resolved and Acknowledged Alarms.

The following image shows an example of a notification about a resolved alarm.

88 | Veeam ONE | Working with Alarms | REV 7

Acknowledging Alarms
By acknowledging an alarm you can let other administrators know that an issue is being investigated or resolved,
so no attention is required from their side.

You can acknowledge alarms that have the Error or Warning status. When you acknowledge an alarm, its status
is changed to Acknowledged, and no response actions are performed on it. Additionally, Veeam ONE notifies
users who monitor the affected object that the alarm is acknowledged.

89 | Veeam ONE | Working with Alarms | REV 7

Acknowledging Individual Alarms
To acknowledge individual alarms:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the inventory pane, select the necessary object.

4. In the information pane, open the Alarms tab.

5. In the list of alarms, select one or more alarms and do one of the following:

 Right-click the selection and choose Acknowledge.

 In the Actions pane on the right, click Acknowledge.

Press and hold the [CTRL] or [SHIFT] key to select multiple alarms.

6. In the Acknowledge Alarm window, specify a comment or a reason for acknowledging the alarms.
The message you specify will be available in the Comment field of the alarm history details, and in the
email notification on acknowledged alarms. For more information, see Viewing Alarm History and
Notifications on Acknowledged Alarms.

7. Click OK.

90 | Veeam ONE | Working with Alarms | REV 7

Acknowledging Multiple Alarms
To acknowledge a number of alarms at once:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the inventory pane, select the necessary object.

4. In the information pane, open the Alarms tab.

5. In the list of alarms, display all alarms that you want to acknowledge.
Use the filters and the search field at the top of the list to display the necessary alarms.

6. Do one of the following:

 Right-click anywhere in the list of alarms and choose Acknowledge all alarms from the
shortcut menu.

 In the Actions pane, click Acknowledge all alarms.

7. In the Acknowledge Alarm window, specify a reason for changing the alarm status, or add any other
information.
The message you specify will be available in the Comment field of the alarm history details, and in the
email notification on acknowledged alarms. For more information, see Viewing Alarm History and
Notifications on Acknowledged Alarms.

8. Click OK.

91 | Veeam ONE | Working with Alarms | REV 7

Notifications on Acknowledged Alarms
After an alarm is acknowledged, Veeam ONE sends a notification to users who monitor the affected object. The
notification includes information about the number of alarms acknowledged, time when the alarms were
acknowledged and reason, as well as the list of acknowledged alarms.

To receive a notification about acknowledged alarms, make sure that:

 You have configured SMTP Server settings.

For details, see Step 1. Configure SMTP Server Settings.

 Your email address is included either in the default notification group, or in the list of notification
recipients specified in the alarm action settings, and the notification level is set to Any state.
For details, see Step 4. Configure Email Recipients.

 Notifications about resolved and acknowledged alarms are enabled.

For details, see Step 5. Disable Notifications About Resolved and Acknowledged Alarms.

The following image shows an example of a notification about an acknowledged alarm.

92 | Veeam ONE | Working with Alarms | REV 7

Viewing Alarm History
Veeam ONE keeps the history of alarm status changes for every triggered alarm. The number of times the alarm
changed its status is displayed as the Repeat Count value.

To view alarm history:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the information pane, open the Alarms tab.

4. Select the necessary alarm and do one of the following:

 Click the Repeat Count link in the list of alarms.

 Double-click the alarm in the list.

 Right-click the alarm and select Show history from the shortcut menu.

 In the Actions pane, click Show history.

The Alarm history window provides detailed data on the history of alarm status changes: assigned status, time,
rule that triggered the alarm or changed its state, and comments for resolved or acknowledged alarms.

93 | Veeam ONE | Working with Alarms | REV 7

Exporting Triggered Alarms
You can export to a CSV file information about triggered alarms. For each exported alarm, the following details
are available:

 Alarm status

 Alarm name

 Date and time when the alarm was triggered

 Name of the affected object

 Repeat count

To export one or more triggered alarms to a CSV file:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click the necessary view — Infrastructure View, Business View,
vCloud Director or Data Protection View.

3. In the inventory pane, select the necessary object.

4. In the information pane, open the Alarms tab.

5. In the list of alarms, display all alarms that you want to export.
Use the filters and the search field at the top of the list to display the necessary alarms.

6. In the Actions pane on the right, click Export history.

7. Save the CSV file with exported data.

8. Click OK.

The following image shows an example of alarm details exported to a CSV file.

94 | Veeam ONE | Working with Alarms | REV 7

Working with Internal Alarms
In addition to alarms for monitoring the virtual and backup infrastructure, Veeam ONE includes a set of
predefined alarms to monitor internal Veeam ONE problems — such as data collection, connection problems or
license issues. For the list and description of internal alarms, see Internal Alarms.

95 | Veeam ONE | Working with Alarms | REV 7

Viewing Internal Alarms
To view Veeam ONE internal alarms:

1. Open Veeam ONE Monitor.

2. In the Configuration issues pane, click the Show details link.

3. Click the object name to drill-down to the list of alarms for the selected object.

96 | Veeam ONE | Working with Alarms | REV 7

Configuring Internal Alarms
You can configure internal alarms similarly to regular alarms:

1. Open Veeam ONE Monitor.

2. At the bottom of the inventory pane, click Alarm Management.

3. In the alarm management three, select the Internal node.

4. Select an alarm in the list and do one of the following:

 Double click the alarm.

 Right-click the alarm and choose Edit from the shortcut menu.

 In the Actions pane, click Edit.

5. Change the necessary alarm settings.

For details on working with alarm settings, see Creating Alarms.

97 | Veeam ONE | Working with Alarms | REV 7

Appendix A. Alarms
This section lists predefined Veeam ONE alarms.

98 | Veeam ONE | Working with Alarms | REV 7

Veeam Backup & Replication Alarms
This section describes predefined alarms for Veeam Backup & Replication infrastructure components:

 Enterprise Manager

 Backup Server

 Repository

 Proxy

 WAN Accelerator

 Tape Server

 Cloud Repository

 Cloud Gateway

Enterprise Manager
Resolve
Alarm Name Event/Condition Severity Description
Action

Veeam Backup State not equals Connected. Error Automatic Veeam ONE failed to
Enterprise connect to Veeam Backup
Manager Enterprise Manager.
connection failure

Veeam Backup & Replication Server

Resolve
Alarm Name Event/Condition Severity Description
Action

Agent backup job Based on event Error Manual One or more computers
state VeeamBpEpAgentBackupWorkerSessionE failed to backup
(available since rrorEvent successfully.
Veeam ONE 9.5
Update 3)
Based on event Warning
VeeamBpEpAgentBackupWorkerSession
WarningEvent

Agent backup Based on event Error Manual One or more computers

policy session VeeamBpEpAgentPolicyWorkerSessionErr failed to backup
state orEvent successfully.
(available since
Veeam ONE 9.5
Based on event Warning
Update 3)
VeeamBpEpAgentPolicyWorkerSessionWa
rningEvent

99 | Veeam ONE | Working with Alarms | REV 7

Backup Copy job Based on event Error Manual One or more backup copy
exceeded data VeeamBpCopyJobNetworkWindowExceed jobs exceeded defined
transfer window edEvent window, and data transfer
between source and target
backup repositories has
been stopped.

Backup Copy job Based on event Error Manual One or more VMs could not
state VeeamBpBackupSyncSessionErrorEvent be successfully copied from
the backup repository.
Based on event Warning
VeeamBpBackupSyncSessionWarningEve
nt

Backup job Job is disabled for more than 12 hours Warning Automatic Job is in a disabled state for
disable more that allowed time
period.

Backup job state Based on event Error Manual One or more VMs failed to
VeeamBpBackupSessionErrorEvent backup successfully.

Based on event Warning

VeeamBpBackupSessionWarningEvent

Backup to tape Based on event Error Manual One or more VMs failed to
job status VeeamBpFileTapeSessionErrorEvent be transferred to the tape
device.
Based on event Error
VeeamBpVmTapeSessionErrorEvent

Based on event Warning

VeeamBpFileTapeSessionWarningEvent

Based on event Warning

VeeamBpVmTapeSessionWarningEvent

File copy job state Based on event Warning Manual One or more files failed to
VeeamBpCopySessionWarningEvent be transferred to the
destination folder.
Based on event Error
VeeamBpCopySessionErrorEvent

Job exceeded Based on event Error Manual One or more jobs exceeded
backup window VeeamBpJobWindowExceededEvent allowed backup window and
has been terminated.

License expiration Based on event Warning Automatic Veeam Backup &

date VeeamBackupServerLicenseExpiration Replication license expired.

Based on event Resolve

VeeamBackupServerLicenseChanged

Based on event Resolve

VeeamBackupServerLicenseExpirationRes
olve

100 | Veeam ONE | Working with Alarms | REV 7

Max allowed job Job duration is more than 480 minutes Error Manual Job has exceeded its
duration allowed execution time.
Job duration is more than 120 minutes Warning

Quick Migration Based on event Warning Manual One or more VMs failed to
job state VeeamBpQMigrationSessionWarningEven migrate to another host.
t

Based on event Error

VeeamBpQMigrationSessionErrorEvent

Replication job Based on event Error Manual One or more VMs failed to
state VeeamBpRepSessionErrorEvent replicate successfully.

Based on event Warning

VeeamBpRepSessionWarningEvent

Support Based on event Warning Automatic Veeam Backup &

expiration date VeeamBackupServerLicenseSupportExpir Replication prepaid support
ation contract expired.

Based on event Resolve

VeeamBackupServerLicenseChanged

Based on event Resolve

VeeamBackupServerLicenseSupportExpir
ationResolved

SureBackup job Based on event Error Manual One or more VMs could not
state VeeamBpSbSessionErrorEvent be successfully verified.

Based on event Warning

VeeamBpSbSessionWarningEvent

Veeam Backup & State not equals Connected Error Automatic Connection to Veeam
Replication Server Backup & Replication server
connection failure failed.

Veeam Broker Based on event Warning Automatic Veeam Broker Service that
Service state VeeamBackupServerBrokerServiceDownE interacts with virtual
vent infrastructure to collect and
cache its topology is not
started and not working
Based on event Resolve properly.
VeeamBackupServerBrokerServiceDownE
vent

Based on event Resolve

VeeamBackupServerBrokerServiceDownE
vent

101 | Veeam ONE | Working with Alarms | REV 7

Repository
Resolve
Alarm Name Event/Condition Severity Description
Action

Backup repository State equals Not accessible for more Error Automatic Veeam Backup &
connection failure than 5 minutes Replication server lost
connection to the backup
repository.
State equals Warning for more than 5 Warning
minutes

Backup repository Free space is below 5% Error Automatic Backup repository is low on
free space free space.
Free space is below 10% Warning

Backup repository Component version mismatch Warning Automatic Veeam backup repository
version is out-of- version does not match the
date version of Veeam Backup &
Replication server.

Proxy
Resolve
Alarm Name Event/Condition Severity Description
Action

Backup proxy State not equals Accessible for more Error Automatic Veeam Backup &
connection failure than 5 minutes Replication server lost
connection to the proxy
server.

Backup proxy Component version mismatch Warning Automatic Veeam backup proxy
version is out-of- version does not match the
date version of Veeam Backup &
Replication server.

WAN Accelerator
Resolve
Alarm Name Event/Condition Severity Description
Action

WAN accelerator State not equals Accessible for more Error Automatic Veeam Backup &
connection state than 5 minutes Replication server lost
connection to the WAN
accelerator.

WAN accelerator Component version mismatch Warning Automatic Veeam WAN accelerator
version is out-of- version does not match the
date version of Veeam Backup &
Replication server.

102 | Veeam ONE | Working with Alarms | REV 7

Tape Server
Resolve
Alarm Name Event/Condition Severity Description
Action

Tape server State not equals Accessible for more Error Automatic Veeam Backup &
connection state than 5 minutes Replication server lost
connection to the tape
server.

Tape server Component version mismatch Warning Automatic Veeam tape server version
version is out-of- does not match the version
date of Veeam Backup &
Replication server.

Cloud Repository
Resolve
Alarm Name Event/Condition Severity Description
Action

Cloud repository Free space is below 10% Warning Automatic Cloud repository is low on
free space available free space.
Free space is below 5% Error

Cloud repository 14 days to lease expiration Warning Automatic Cloud repository lease time
lease expiration is about to expire.
date
0 days to lease expiration Error

VM backups in Number of stored VMs is above the Warning Automatic Number of VMs stored in
cloud repository specified threshold the cloud repository is
above the defined
threshold.

Cloud Gateway
Resolve
Alarm Name Event/Condition Severity Description
Action

Cloud gateway State not equals Accessible for more Error Automatic Veeam Backup &
connection state than 5 minutes Replication server lost
connection to the cloud
gateway.

Cloud gateway Component version mismatch Warning Automatic Veeam cloud gateway
version is out-of- version does not match the
date version of Veeam Backup &
Replication server.

103 | Veeam ONE | Working with Alarms | REV 7

VMware vSphere Alarms
This section describes predefined alarms for VMware vSphere infrastructure components:

 vCenter Server

 Cluster

 Host

 Virtual Machine

 Datastore

 Any VMware Object

 vCloud Director vApp

 vCloud Director Organization

 vCloud Director Org VDC

 vCloud Director Provider VDC

vCenter Server
Resolve
Alarm Name Event/Condition Severity Description
Action

Bad vCenter Based on event Error Manual This event records a failed
Server username BadUsernameSessionEvent user logon. The
logon attempt combination of username,
password, and permissions
is the mechanism by which
vCenter Server authenticate
a user for access and
authorize the user to
perform activities.

Insufficient user Based on event Error Manual This event records a failed
access NoAccessUserEvent user logon due to
permissions insufficient access
permission.

Invalid license Based on event Error Manual This event records if the
edition InvalidEditionEvent license edition is set to an
invalid value.

License expired Based on event Error Manual This event records the
LicenseExpiredEvent expiration of a license.

License file Based on event Error Manual This event records if the
restricted LicenseRestrictedEvent required licenses could not
be reserved because of a
restriction in the option file.

104 | Veeam ONE | Working with Alarms | REV 7

License is not Based on event Error Manual This event records that the
compliant LicenseNonComplianceEvent inventory is not license
compliant.

Maximum host Based on event Error Manual This event records if the
connections HostInventoryFullEvent inventory of hosts has
reached reached capacity.

No license Based on event Error Manual These are events reported

reservation NoLicenseEvent by License Manager. A
NoLicenseEvent is reported
if the required licenses
could not be reserved. Each
feature that is not fully
licensed is reported.

Non VI workload Based on event Error Manual A potential misconfiguration

detected NonVIWorkloadDetectedOnDatastoreEve or I/O performance issue
nt caused by a non-ESX
workload has been
detected. This alarm is
triggered when Storage I/O
Control (SIOC) detects that
a workload that is not
managed by SIOC is
contributing to I/O
congestion on a datastore
that is managed by SIOC.

vCenter Server Based on event Error Manual This event records when the
agent uninstall VcAgentUninstallFailedEvent vCenter Server agent on a
failure host failed to uninstall.

vCenter Server Based on event Error Manual This event records when the
agent upgrade VcAgentUpgradeFailedEvent vCenter Server agent on a
failure host failed to upgrade.

vCenter Server Based on event Error Manual This event records an

license expired ServerLicenseExpiredEvent expired vCenter Server
license.

Cluster
Resolve
Alarm Name Event/Condition Severity Description
Action

Admission control Based on event Information Automatic This event records when
disabled DasAdmissionControlDisabledEvent admission control checks
have been disabled in a HA
cluster.

Admission control Based on event Information Automatic This event records when
enabled DasAdmissionControlEnabledEvent admission control checks
have been enabled in a HA
cluster.

105 | Veeam ONE | Working with Alarms | REV 7

All hosts in cluster Based on event Error Manual This event records that all
isolated DasClusterIsolatedEvent hosts have been isolated
from the network in a HA
cluster.

DRS invocation Based on event Error Manual This event records DRS
failure DrsInvocationFailedEvent invocation failure. DRS
invocation not completed.

HA disabled for Based on event Information Automatic This event records when a
cluster DasDisabledEvent cluster has been disabled
for HA.

HA enabled for Based on event Information Automatic This event records when a
cluster DasEnabledEvent cluster has been enabled for
HA.

Host cluster Based on event Error Manual This event records when a
capacity ClusterOvercommittedEvent cluster's host capacity
overcommitted cannot satisfy resource
configuration constraints.

vSphere cluster Based on event Warning Manual One of the hosts in an HA

warning com.vmware.vc.HA.ClusterContainsIncom cluster has been isolated.
patibleHosts

Based on event
com.vmware.vc.HA.DasFailoverHostIsolat
edEvent

Based on event
com.vmware.vc.HA.DasFailoverHostPartit
ionedEvent

Based on event
com.vmware.vc.HA.DasFailoverHostUnre
achableEvent

Based on event
com.vmware.vc.HA.DasHostIsolatedEven
t

Host
Resolve
Alarm Name Event/Condition Severity Description
Action

Bad Host Based on event Warning Manual This event records a failed
username logon BadUsernameSessionEvent user logon. The
attempt combination of username,
password, and permissions
is the mechanism by which
hosts authenticate a user
for access and authorize the
user to perform activities.

106 | Veeam ONE | Working with Alarms | REV 7

Connection to Based on event Error Manual The iSCSI initiator is unable
iSCSI storage esx.problem.storage.iscsi.discovery.conn to establish a connection to
target failure ect.error the target.

Based on event
esx.problem.storage.iscsi.discovery.login.
error

Based on event
esx.problem.storage.iscsi.target.connect.
error

Based on event
esx.problem.storage.iscsi.target.login.err
or

DPM failed to Based on event Error Automatic This event records that
bring host out of DrsExitStandbyModeFailedEvent Distributed Power
standby mode Management tried to bring
a host out of standby mode,
Based on event Resolve but failed.
DrsExitedStandbyMode
Standby Mode powers off a
Based on event Resolve host and allows it to be
ExitedStandbyMode powered back on again
through the Wake-on-LAN
protocol. It can be
triggered either manually or
automatically by vCenter
Server.

DRS host standby Based on event Information Automatic This event records that the
mode entrance DrsEnteredStandbyModeEvent host has successfully
entered standby mode
initiated by Distributed
Power Management. A host
in this mode has no running
virtual machines and no
provisioning operations are
occurring.

DRS host standby Based on event Information Automatic This event records that
mode exit DrsExitedStandbyModeEvent Distributed Power
Management brings this
host out from standby
mode.

DRS Based on event Error Manual This event records when

synchronization DrsResourceConfigureFailedEvent resource configuration
failure specification synchronization
fails on a host.

DVS host Based on event Warning Manual The list of hosts that have
configuration out OutOfSyncDvsHost the DVS configuration on
of sync the host diverged from that
of the vCenter Server.

107 | Veeam ONE | Working with Alarms | REV 7

ESX(i) host Based on event Error Manual Link Aggregation Control
network uplink esx.problem.net.lacp.uplink.fail.duplex Protocol (LACP) is included
failure in IEEE specification as a
method to control the
Based on event
bundling of several physical
esx.problem.net.lacp.uplink.fail.speed
ports together to form a
single logical channel. LACP
Based on event allows a network device to
esx.problem.net.lacp.uplink.inactive negotiate an automatic
bundling of links by sending
LACP packets to the peer
(directly connected device
that also implements LACP).

ESX(i) host CPU Based on event Error Manual ESX(i) host has experienced
hardware error esx.problem.cpu.amd.mce.dram.disabled a CPU hardware error.

Based on event
esx.problem.cpu.intel.ioapic.listing.error

Based on event
esx.problem.cpu.mce.invalid

Based on event
esx.problem.cpu.smp.ht.invalid

Based on event
esx.problem.cpu.smp.ht.numpcpus.max

ESX(i) host Based on event Error Manual DHCP client lease issue has
network error esx.problem.dhclient.lease.none been detected.

ESX(i) host Based on event Warning Manual Link Aggregation Control

network uplink esx.problem.net.lacp.uplink.blocked Protocol (LACP) is included
problems in IEEE specification as a
method to control the
Based on event
bundling of several physical
esx.problem.net.lacp.uplink.disconnected
ports together to form a
single logical channel. LACP
allows a network device to
negotiate an automatic
bundling of links by sending
LACP packets to the peer
(directly connected device
that also implements LACP).

ESX(i) host Based on event Warning Manual DHCP client lease issue has
network warning esx.problem.dhclient.lease.offered.error been detected.

Based on event
esx.problem.dhclient.lease.persistent.non
e

ESX(i) host Based on event Error Manual Storage device becomes

storage error esx.problem.scsi.device.state.permanentl permanently lost while SCSI
oss.withreservationheld reservation is held by ESXi.

108 | Veeam ONE | Working with Alarms | REV 7

ESX(i) host Based on event Error Manual An operation on the root file
storage failure esx.problem.visorfs.failure system has failed.

ESX(i) host Based on event Warning Manual One of the host's ramdisks
storage warning esx.problem.visorfs.inodetable.full reached the limit for the
number of files it can
contain.
Based on event Warning
esx.problem.visorfs.ramdisk.full

Host available Average memory usage for 15 minutes is Warning Automatic This host is low on available
memory above 80% memory.

Average memory usage for 15 minutes is Error

above 90%

Host connection Host state equals Disconnected for 5 Warning Automatic This alarm monitors the
failure minutes and more. VMware vCenter Server API
for events indicating that a
host is disconnected.
Host state equals Not responding for 5
minutes and more.

Host connectivity Based on event Error Automatic This event indicates that
failure vprob.net.connectivity.lost one or more portgroups in
the host have lost
connectivity to the network,
Based on event
resulting in unavailability of
esx.problem.net.connectivity.lost
all physical connections to
the network from this
Based on event Resolve switch.
esx.clear.net.connectivity.restored

Host CPU ready Average CPU Ready for 15 minutes is Warning Automatic This Host has exceeded the
above 15% threshold for CPU Ready
Percent.
Average CPU Ready for 15 minutes is Error
above 25%

Host CPU usage Average CPU usage for 15 minutes is Warning Automatic This host has exceeded the
above 75% threshold for CPU usage.

Average CPU usage for 15 minutes is Error

above 95%

Host disk bus Average datastore bus resets for 15 Warning Automatic This host disk (vmhba) has
resets minutes is above 2 logged one or more SCSI
bus resets.
Average datastore bus resets for 15 Error
minutes is above 4

Host disk SCSI Average datastore command aborts for Warning Automatic This host disk (vmhba) has
aborts 15 minutes is above 2 logged one or more SCSI
aborts.
Average datastore command aborts for Error
15 minutes is above 4

109 | Veeam ONE | Working with Alarms | REV 7

Host failed to exit Based on event Error Automatic This event records that the
standby mode ExitStandbyModeFailedEvent host failed to exit standby
mode.
Based on event Resolve Standby Mode powers off a
ExitedStandbyMode host and allows it to be
powered back on again
through the Wake-on-LAN
protocol. It can be triggered
either manually or
automatically by vCenter
Server.

Host HA agent Based on event Error Manual Usually, such triggers

failure com.vmware.vc.HA.HostAgentErrorEvent indicate that a host has
actually failed, but failure
reports can sometimes be
incorrect. A failed host
reduces the available
capacity in the cluster and,
in the case of an incorrect
report, prevents vSphere HA
from protecting the virtual
machines running on the
host.

Host HA disabled Based on event Information Automatic This event records when HA
HostDasDisabledEvent has been disabled on a
host.

Host HA enabled Based on event Information Automatic This event records when the
HostDasEnabledEvent HA (high-availability) agent
has been enabled on a host.

Host hardware Hardware sensor equals Warning Warning Automatic One of the hosts' hardware
status sensors has changed its
status.
Hardware sensor equals Alert Error

Hardware sensor equals Unknown Warning

Host IP Based on event Warning Manual This event records that the
inconsistent HostIpInconsistentEvent IP address resolution
returned different addresses
on the host.

Host IP to short Based on event Warning Manual This event records that the
name failed HostIpToShortNameFailedEvent host's IP address could not
be resolved to a short
name.

Host Isolation IP Based on event Warning Manual This event records that the
not available HostIsolationIpPingFailedEvent isolation address could not
be pinged. The default
isolation address is the
service console's default
gateway.

110 | Veeam ONE | Working with Alarms | REV 7

Host license Based on event Error Manual This event records an
expired HostLicenseExpiredEvent expired host license.

Host memory Average memory pressure for 15 minutes Warning Automatic This host has exceeded the
pressure is above 150% threshold for memory
pressure.
Average memory pressure for 15 minutes Error
is above 250%

Host NIC Based on event Error Automatic Physical NIC linkstate is

connection state esx.problem.net.vmnic.linkstate.down down.

Based on event Resolve

esx.clear.net.vmnic.linkstate.up

Host not Based on event Warning Manual This event records that host
compliant HostNonCompliantEvent went out of compliance.

Host operation Based on event Information Automatic An operation performed on

cancelled CanceledHostOperationEvent the host was canceled.

Host operation Based on event Warning Manual This event indicates that an
timed out TimedOutHostOperationEvent operation performed on the
host timed out.

Host primary Based on event Warning Manual This event records that the
agent not in short HostPrimaryAgentNotShortNameEvent primary agent specified is
name not a short name.

Host reconnection Based on event Resolve Automatic This event records a failed
failed HostConnectedEvent attempt to re-establish a
host connection.
Based on event Error
HostReconnectionFailedEvent

Host redundancy Based on event Warning Automatic The event indicates that
failure vprob.net.redundancy.lost one or more portgroups in
the host has lost a
redundant uplink to the
Based on event
physical network.
vprob.net.redundancy.degraded
Portgroups are still
connected. However this
Based on event may be the last redundant
esx.problem.net.redundancy.lost uplink. Check the event
description and context to
confirm the status.
Based on event
esx.problem.net.redundancy.degraded

Based on event Resolve

esx.clear.net.redundancy.restored

Host short name Based on event Warning Manual This event records that host
inconsistent HostShortNameInconsistentEvent name resolution returned
different names on the host.

111 | Veeam ONE | Working with Alarms | REV 7

Host short name Based on event Warning Manual This event records that the
IP resolve failed HostShortNameToIpFailedEvent host's short name could not
be resolved to an IP
address.

Host swap Average memory swap used for 15 Warning Automatic This host is swapping too
memory minutes is above 64 MB much memory.

Average memory swap used for 15 Error

minutes is above 128 MB

Host Based on event Warning Manual This event records a failure

synchronization HostSyncFailedEvent to sync up with the vCenter
failed Server agent on the host.

Host upgrade Based on event Error Manual This event records a failure
connection failure HostUpgradeFailedEvent to connect to a host due to
an installation or upgrade
issue.

Incorrect host Based on event Warning Manual This event records if the
information IncorrectHostInformationEvent host did not provide the
information needed to
acquire the correct set of
licenses.

iSCSI target Based on event Error Manual The iSCSI initiator is unable
storage esx.problem.storage.iscsi.target.connecte to establish a connection to
connection failure d.error the target.

iSCSI targets are Based on event Error Manual The

permanently esx.problem.storage.iscsi.target.permane esx.problem.storage.iscsi.ta
removed from ntly.lost rget.permanently.removed
ESXi message is received when
an iSCSI target is no longer
presented to ESXi.

Isolation Based on event Warning Manual ESX(i) host is missing

addresses is com.vmware.vc.HA.HostHasNoIsolationA isolation addresses for
missing ddrsDefined isolation detection.

Network rollback Based on event Error Manual In vSphere 5.1, rollback is

detected NetworkRollbackEvent enabled by default.
However, you can enable or
disable rollbacks at the
vCenter Server level.
Several networking events
can trigger a rollback. The
events are grouped into
these categories:

 Host networking
rollbacks
(virtual switches
or network
system)
 Distributed
switch rollbacks

112 | Veeam ONE | Working with Alarms | REV 7

No host network Based on event Warning Manual This event records the fact
for HA available HostNoAvailableNetworksEvent that a host does not have
any available networks for
HA communication.

Non VI workload Based on event Error Manual A potential misconfiguration

detected on host EsxProblemIormNonViWorkload or I/O performance issue
caused by a non-ESX
workload has been
detected. This alarm is
triggered when Storage I/O
Control (SIOC) detects that
a workload that is not
managed by SIOC is
contributing to I/O
congestion on a datastore
that is managed by SIOC.

SCSI unsupported Based on event Warning Manual An invalid storage module

plugin warning esx.problem.scsi.unsupported.plugin.type attempted to configure a
SCSI device.

Storage Based on event Error Automatic The event indicates a loss in

connection failure vprob.storage.connectivity.lost connectivity to the specified
storage device. The path
indicated is the last path
Based on event that went down.
esx.problem.storage.connectivity.lost

Based on event Resolve

esx.clear.storage.connectivity.restored

Storage Based on event Warning Automatic A host has lost a path to

connection vprob.storage.redundancy.lost access the specified storage
redundancy and the path to storage is
failure either degraded, or no
Based on event
longer redundant. Check
vprob.storage.redundancy.degraded the event description and
context to confirm the
Based on event status.
esx.problem.storage.redundancy.degrade
d

Based on event
esx.problem.storage.redundancy.lost

Based on event Resolve

esx.clear.storage.redundancy.restored

Teaming Based on event Error Manual The teaming configuration

mismatch error TeamingMisMatchEvent of the uplink ports in the
DVS does not match
physical switch
configuration.

Uplink port MTU Based on event Error Manual MTU health check status of
error UplinkPortMtuNotSupportEvent an uplink port is changed.

113 | Veeam ONE | Working with Alarms | REV 7

Uplink port VLAN Based on event Error Manual Vlans health check status of
error UplinkPortVlanUntrunkedEvent an uplink port is changed.

vCenter Server Based on event Error Automatic vCenter Server has lost
lost connection to HostConnectionLostEvent connection to this host.
host
Based on event
HostCnxFailed

Based on event Resolve

HostConnectedEvent

vMotion license Based on event Error Manual This event records an

expired VMotionLicenseExpiredEvent expired vMotion license.

vSphere Based on event Error Manual A larger MTU (maximum

Distributed MtuMismatchEvent transmission unit) bring
Switch MTU greater efficiency because
mismatch each packet carries more
user data while protocol
overheads; the resulting
higher efficiency means a
slight improvement in bulk
protocol throughput. A
larger MTU also means
processing of fewer packets
for the same amount of
data. However, this gain is
not without some downside.
Large packets can occupy a
slow link for some time,
causing greater delays to
following packets and
increasing lag and minimum
latency.

114 | Veeam ONE | Working with Alarms | REV 7

Virtual Machine
Resolve
Alarm Name Event/Condition Severity Description
Action

Customization Based on event Warning Manual The customization sequence

unknown failure CustomizationUnknownFailure failed unexpectedly in the
guest.

Fault Tolerance Based on event Warning Manual This event records a

VM terminated VmFaultToleranceVmTerminatedEvent secondary or primary VM is
terminated.

FT VM Failover Based on event Error Manual This event records a fault

VmPrimaryFailoverEvent tolerance failover.

Guest Based on event Warning Manual The customization sequence

customization CustomizationFailed in the guest failed. Cannot
failure complete customization of
VM.

Guest disk space Guest disk free space space is below Warning Automatic Guest OS volume is low on
10% available guest disk space.

Guest disk free space space is below 5% Error

HA agent update Based on event Error Manual The event records an error
failed VmDasUpdateErrorEvent occurred when updating the
HA agents with the current
state of the VM.

Heartbeat is Heartbeat not detected for 15 minutes Error Automatic The heartbeat is the
missing for VM communication to the
VMware tools heartbeat
running inside the VM.

Heartbeat can only be

monitored when the
VMware tools are installed
in a VM. The heartbeat is
what vCenter Server uses to
determine the general
health and availability of a
running VM.

High balloon Average memory balloon percent for 15 Warning Automatic There is high utilization of
memory minutes is above 10% the VMware Tools memory
utilization controller, also known as
the 'balloon driver', within
Average memory balloon percent for 15 Error
this VM.
minutes is above 50%

High memory Average memory usage for 15 minutes is Warning Automatic There is high utilization of
usage above 90% memory within this Virtual

115 | Veeam ONE | Working with Alarms | REV 7

 Machine. The memory
Average memory usage for 15 minutes is Error active metric is the current
above 95% percentage of memory
active vs. memory
maximum for this VM.

Latest snapshot VM snapshot age is 48 hour or more Warning Automatic The age of the (latest)
age snapshot for this Virtual
Machine has exceeded the
configured threshold.

Latest snapshot VM snapshot size is above 10% Warning Automatic The VM has been running
size on a snapshot for extended
period of time, which
VM snapshot size is above 20% Error exceeded the configured
threshold for the snapshot
file size.

A snapshot preserves the

state and data of a VM at a
specific point in time, and is
typically used for backup of
running VMs or
maintenance activities (such
as patching).

Linux Based on event Warning Manual Failed to set Linux identity.

customization CustomizationLinuxIdentityFailed
identity failure

Network Based on event Warning Manual Network setup failed in the

customization CustomizationNetworkSetupFailed guest during customization.
setup failure

No compatible Based on event Warning Manual This event records that no

host for VmNoCompatibleHostForSecondaryEvent compatible host was found
Secondary VM to place a secondary VM. A
default alarm will be
triggered upon this event,
which by default, would
trigger a SNMP trap.

No host for a Based on event Warning Manual This event records a VM for
virtual machine VmOrphanedEvent which no host is
available responsible.

No maintenance Based on event Warning Manual This event records that DRS
mode DRS NoMaintenanceModeDrsRecommendation did not recommend a
recommendation ForVM migration for a powered on
for VM VM, even though its host is
going into maintenance
mode.

No network Based on event Warning Manual This event records a

access for VM VmNoNetworkAccessEvent migration failure when the
migration destination host is not on
the same network as the
source host.

116 | Veeam ONE | Working with Alarms | REV 7

Not enough Based on event Warning Manual This event records when the
resources for NotEnoughResourcesToStartVmEvent HA does not find sufficient
failover resources to failover a VM.

Orphaned VM Orphaned VM backup snapshot age is 60 Error Automatic This VM is running on the
backup snapshot minutes or more snapshot left by backup or
replication job.

Possible Average CPU Usage is above 70% Warning Automatic Veeam ONE detected
ransomware and suspicious activity on this
activity Datastore Write Rate is above 40 MB/s VM.
or
Network Transmit Rate is above 40 MB/s
for 5 minutes

Average CPU Usage is above 80% Error

and
Datastore Write Rate is above 60 MB/s
or
Network Transmit Rate is above 60 MB/s
for 5 minutes.

Secondary VM Based on event Warning Manual This event is recorded after

config update VmFailedUpdatingSecondaryConfig a failover of the new
failed primary VM failed to update
the config of the secondary
VM.

Secondary VM Based on event Warning Manual The Secondary VM cannot

failed to start VmFailedStartingSecondaryEvent be powered on as there are
no compatible hosts that
can accommodate it.

Secondary VM Based on event Warning Manual This event records timeout

start timeout VmTimedoutStartingSecondaryEvent when starting a secondary
VM.

Sysprep Based on event Warning Manual Sysprep failed to run in the

customization CustomizationSysprepFailed guest during customization.
failure This might have been
caused by the fact that the
wrong sysprep was used for
the guest or errors in the
sysprep file.

Too many Number of VM snapshots is 3 or more Warning Automatic An excessive number of

snapshots on the snapshots in a chain has
VM been detected on the VM
Number of VM snapshots is 5 or more Error
which may lead to
decreased virtual machine
and host performance.

Virtual disk Based on event Error Manual This event records a failure
creation failed VmDiskFailedEvent to create a virtual disk in a
VM.

VM clone Based on event Error Manual This event records a failure

operation failure VmCloneFailedEvent to clone a VM.

117 | Veeam ONE | Working with Alarms | REV 7

VM configuration Based on event Warning Manual This event records if the
file missing VmConfigMissingEvent configuration file (VMX file)
for a VM cannot be found.

VM connection Based on event Error Automatic This VM is 'Disconnected' in

failure VmDisconnectedEvent vCenter Server.

Based on event Resolve

VmConnectedEvent

VM consolidation Based on event Error Automatic When initiating Delete or

needed status com.vmware.vc.VmDiskConsolidationNee DeleteAll operations on
ded snapshots, the snapshot
details are deleted from
Snapshot Manager, then the
Based on event Resolve
snapshot files are
com.vmware.vc.VmDiskConsolidationNoL
consolidated and merged to
ongerNeeded
another snapshot file or to
the virtual machine parent
Based on event Resolve disk. If the consolidation
com.vmware.vc.VmDiskConsolidated fails, there were no
Event snapshots shown in the
Snapshot Manager, but the
snapshot files were still
being used on the
datastore. This can cause
the datastore to run out of
space.

VM CPU ready Average CPU ready all cores metric for Warning Automatic This VM has exceeded the
15 minutes is above 10% threshold for CPU Ready
Percent.
Average CPU ready all cores metric for Error
15 minutes is above 20%

VM CPU usage Average CPU usage for 15 minutes is Warning Automatic This VM has exceeded the
above 75% threshold for CPU usage.

Average CPU usage for 15 minutes is Error

above 90%

VM disk Based on event Error Automatic There is an issue with the

consolidation com.vmware.vc.VmDiskFailedToConsolid disk for this virtual machine.
failure ateEvent

Based on event Resolve

com.vmware.vc.VmDiskConsolidatedEvent

VM disk SCSI Average number of datastore command Warning Automatic This VMGuest disk
connection aborts for 15 minutes is above 2 connection (LUN) has
failures logged one or more SCSI
aborts.
Average number of datastore command Error
aborts for 15 minutes is above 6

VM disk SCSI Average number of datastore bus resets Warning Automatic This VMGuest disk
connection resets for 15 minutes is above 2 connection (LUN) has

118 | Veeam ONE | Working with Alarms | REV 7

 logged one or more SCSI
Average number of datastore bus resets Error bus resets.
for 15 minutes is above 6

VM generic error Based on event Error Manual This is a generic event for
VmMessageErrorEvent error messages from a VM
that do not fit into any
other specific vCenter
Server event.

VM generic Based on event Warning Manual This is a generic event for

warning VmMessageWarningEvent warning messages from a
VM that did not fit into any
other specific vCenter
Server event.

VM guest reboot Based on event Information Automatic This is a VM guest reboot

VmGuestRebootEvent request event.

VM guest Based on event Information Automatic This is a VM guest

shutdown VmGuestShutdownEvent shutdown request event.

VM HA error Based on event Error Manual vSphere HA has failed to

com.vmware.vc.HA.FailedRestartAfterIsol restart after a host isolation.
ationEvent

VM HA reset Based on event Warning Manual This event records when a

VmDasBeingResetEvent VM is reset by HA VM
Health Monitoring on hosts
that do not support the
create screenshot APIi or if
the create screenshot API
fails.

VM HA reset Based on event Warning Manual This event records when HA

failure VmDasResetFailedEvent VM health monitoring fails
to reset a VM after failure.

VM memory swap Average memory swapped for 15 Warning Automatic This VM has exceeded the
usage minutes is above 64 MB threshold for memory
swapping to disk within the
host.
Average memory swapped for 15 Error
minutes is above 128 MB

VM power status State not equals Running for 5 minutes Error Automatic The power state of a VM
or more indicates whether the VM is
active and functional.

VM resetting Based on event Information Automatic This event records a VM

VmResettingEvent resetting.

VM restart on Based on event Information Automatic This event records that the
alternate host VmRestartedOnAlternateHostEvent VM was restarted on a host,
since its original host had
failed.

119 | Veeam ONE | Working with Alarms | REV 7

VM Screenshot HA Based on event Warning Manual This event records when a
reset VmDasBeingResetWithScreenshotEvent VM is reset by HA VM health
monitoring on hosts that
support the create
screenshot API.

VM total disk Average datastore highest latency for 15 Warning Automatic Highest latency value across
latency minutes is above 50 milliseconds all disks used by the VM.

Average datastore highest latency for 15 Error

minutes is above 75 milliseconds

VM with no No backup restore points for the past 24 Warning Automatic This VM has not been
backups hours backed up within the
defined RPO (Recovery
Point Objective) interval.

VM with no No replica restore points for the past 24 Warning Automatic This VM has not been
replica hours replicated within the defined
RPO (Recovery Point
Objective) interval.

VM WWN conflict Based on event Error Manual This event records a conflict
VmWwnConflictEvent of VM WWNs (World Wide
Name).

VMware VM tools VMware VM tools state changes equals Warning Automatic There is a problem with
state Unknown VMware Tools in this Virtual
Machine.
VMware VM tools state changes equals Warning
Out-of-date

VMware VM tools state changes equals Error

Not installed

VMware VM tools state changes equals Error

Not running

Datastore
Resolve
Alarm Name Event/Condition Severity Description
Action

Datastore free Free space is below 10% Warning Automatic Datastore is low on
space available free space.
Free space is below 5% Error

Datastore is State not equals Accessible for 5 minutes Error Automatic The event indicates a loss in
inaccessible or more connectivity to the specified
storage device. The path
indicated is the last path
that went down.

120 | Veeam ONE | Working with Alarms | REV 7

Datastore over- Datastore provisioning rate is above Warning Automatic Datastore is over-allocated.
allocation 400%

Datastore provisioning rate is above Error

600%

Datastore read Maximum datastore read latency for 15 Warning Automatic Datastore latency has
latency minutes is above 100 milliseconds exceeded the threshold of
total read latency.
Maximum datastore read latency for 15 Error
minutes is above 250 milliseconds

Datastore write Maximum datastore write latency for 15 Warning Automatic Datastore latency has
latency minutes is above 100 milliseconds exceeded the threshold of
total write latency.
Maximum datastore write latency for 15 Error
minutes is above 250 milliseconds

Locker Based on event Warning Manual Locker has not been

misconfiguration LockerMisconfiguredEvent configured properly.
Datastore which is
configured to back the
locker does not exist.

Any VMware Object

Resolve
Alarm Name Event/Condition Severity Description
Action

Duplicate IP Based on event Warning Manual This event records that a

address detected DuplicateIpDetectedEvent duplicate IP address has
been observed, with conflict
between VM, and the
vMotion or IP storage
interface configured on the
host.

Host cluster Based on event Information Automatic This event records when a
destroyed ClusterDestroyedEvent cluster is destroyed.

Host failure Based on event Error Manual This event records when a
detected DasHostFailedEvent host failure has been
detected by HA.

Host isolation in Based on event Warning Manual This event records that a
HA cluster DasHostIsolatedEvent host has been isolated from
the network in a HA cluster.
Since an isolated host
cannot be distinguished
from a failed host except by
the isolated host itself, this
event is logged when the
isolated host regains
network connectivity.

121 | Veeam ONE | Working with Alarms | REV 7

No host Based on event Warning Manual This event records the fact
redundant HostNoRedundantManagementNetworkE that a host does not have a
management vent redundant management
network available network. It is recommended
that host management
networks be configured with
redundancy.

Primary host Based on event Information Automatic This event records that
connection re- DasAgentFoundEvent vCenter Server has re-
established established contact with a
primary host in this HA
cluster.

Primary host Based on event Error Automatic This event records that
unavailable DasAgentUnavailableEvent vCenter Server cannot
contact to any primary host
in this HA cluster. vCenter
Based on event Resolve Server has lost contact with
DasAgentFoundEvent all primary nodes with a
connected state. Attempts
to configure HA on a host in
this cluster will fail until a
DasAgentFoundEvent is
logged or unless this is the
first node to be configured.
For example, if all the other
hosts are disconnected first.

Resource pool Based on event Error Manual This event records when a
configuration ResourceViolatedEvent conflict with a resource
conflict pool's resource
configuration is detected.

Storage ATS Based on event Error Manual In a shared storage

support failure esx.problem.vmfs.ats.support.lost environment, when multiple
hosts access the same
VMFS datastore, specific
locking mechanisms are
used. These locking
mechanism prevent multiple
hosts from concurrently
writing to the metadata and
ensure that no data
corruption occurs. VMFS
supports SCSI reservations
and atomic test and set
(ATS) locking. For storage
devices that support
hardware acceleration,
VMFS uses the ATS
algorithm, also called
hardware assisted locking.
In contrast with SCSI
reservations, ATS supports
discrete locking per disk
sector.

122 | Veeam ONE | Working with Alarms | REV 7

Task timeout Based on event Warning Manual This event records when a
reached TaskTimeoutEvent task exceeds defined
timeout in vCenter Server.

Template Based on event Error Manual This event records a failure

deployment VmDeployFailedEvent to deploy a VM from a
failure template.

vCenter storage Based on event Error Manual The alarm indicates that a
availability error vprob.vmfs.error.volume.is.locked VMFS volume on the ESX(i)
host is locked due to an I/O
error.
Based on event Error
esx.problem.vmfs.error.volume.is.locked

Based on event Warning

vprob.vmfs.extent.offline

Based on event Warning

esx.problem.vmfs.extent.offline

VM instance UUID Based on event Warning Automatic This event records a conflict
conflict VmInstanceUuidConflictEvent of VM instance UUIDs.

Based on event Resolve

VmInstanceUuidChangedEvent

VM MAC address Based on event Error Automatic This event records a MAC
conflict VmMacConflictEvent address conflict for a VM.

Based on event
VmStaticMacConflictEvent

Based on event Resolve

VmMacChangedEvent

vSphere cluster Based on event Error Manual There is an issue with

HA error com.vmware.vc.HA.HostDasErrorEvent VMware high-availability
configuration for this host.

vSphere cluster Based on event Warning Manual There is an issue with

HA warning com.vmware.vc.HA.InvalidMaster VMware high-availability
protection for this cluster.
Based on event
com.vmware.vc.HA.UserHeartbeatDatast
oreRemoved

Based on event
com.vmware.vc.HA.VcCannotFindMasterE
vent

Based on event
com.vmware.vc.HA.HostPartitionedFrom
MasterEvent

123 | Veeam ONE | Working with Alarms | REV 7

 Based on event
com.vmware.vc.HA.HostUnconfiguredWit
hProtectedVms

Based on event
com.vmware.vc.HA.HostUnconfigureError

Based on event
com.vmware.vc.HA.NotAllHostAddrsPinga
ble

vCloud Director vApp

Resolve
Alarm Name Event/Condition Severity Description
Action

vApp health vCloud Director object task status equals Warning Automatic vApp health status has
status Alert changed.

vCloud Director object task status equals Error

Warning

vApp runtime vApp runtime lease timeout is 14 days Warning Automatic vApp runtime lease has
lease timeout expired. Once a vApp is
powered on for the first
vApp runtime lease timeout is 7 days Error
time, the clock starts for the
Maximum Runtime Lease.
The Maximum Runtime
Lease is how long a vApp
can be powered on before
its automatically suspended.

vApp storage vApp storage lease timeout is 14 days Warning Automatic vApp storage lease has
lease timeout expired. A vApp storage
lease begins when a user
vApp storage lease timeout is 7 days Error
stops the vApp. Storage
leases do not affect running
vApps.

vCloud Director Organization

Resolve
Alarm Name Rule Event Severity Description
Action

Organization Number of blocking tasks is 1 or more Warning Automatic Some tasks are in a pending
blocking task state as a result of blocking.
number
Number of blocking tasks is 5 or more Error

Organization Blocking tasks timeout is 5 minutes Warning Automatic One or more organization
blocking task blocking tasks has expired.
timeout
Blocking tasks timeout is 10 minutes Error

124 | Veeam ONE | Working with Alarms | REV 7

vCloud Director Org VDC
Resolve
Alarm Name Rule Event Severity Description
Action

Network pool Network pool usage is above 90% Warning Automatic Network pool usage has
usage exceeded the configured
threshold for this alarm.
Network pool usage is above 95% Error

Org VDC CPU Average CPU usage for 15 minutes is Warning Automatic This organization VDC has
usage above 80% exceeded the threshold for
CPU Usage.
Average CPU usage for 15 minutes is Error
above 90%

Org VDC health vCloud Director object task status equals Warning Automatic Org VDC health status has
status Warning changed.

vCloud Director object task status equals Error

Alert

Org VDC memory Average memory usage for 15 minutes is Warning Automatic This organization VDC has
usage above 80% exceeded the threshold for
Memory Usage.
Average memory usage for 15 minutes is Error
above 90%

Org VDC storage Average storage usage for 15 minutes is Warning Automatic This org VDC has exceeded
usage above 80% the threshold for Storage
Usage.
Average storage usage for 15 minutes is Error
above 90%

vCloud Director Provider VDC

Resolve
Alarm Name Rule Event Severity Description
Action

Provider VDC CPU Average CPU usage for 15 minutes is Warning Automatic This provider VDC has
usage above 80% exceeded the threshold for
CPU Usage.
Average CPU usage for 15 minutes is Error
above 90%

Provider VDC vCloud Director object task status equals Warning Automatic Provider VDC health status
health status Warning has changed.

vCloud Director object task status equals Error

Alert

125 | Veeam ONE | Working with Alarms | REV 7

Provider VDC Average memory usage for 15 minutes is Warning Automatic This provider VDC has
memory usage above 80% exceeded the threshold for
Memory Usage.
Average memory usage for 15 minutes is Error
above 90%

Provider VDC Average storage usage for 15 minutes is Warning Automatic This provider VDC has
storage usage above 80% exceeded the threshold for
Storage usage.
Average storage usage for 15 minutes is Error
above 90%

126 | Veeam ONE | Working with Alarms | REV 7

Microsoft Hyper-V Alarms
This section describes predefined alarms for Microsoft Hyper-V infrastructure components:

 Host

 Virtual Machine

 Cluster

 Cluster Shared Volume

 Local Storage

 Any Hyper-V Object

Host
Resolve
Alarm Name Event/Condition Severity Description
Action

Bad Hyper-V Based on event Error Manual This event records a failed
username logon 4625 Microsoft-Windows-Security- user logon attempt. The
attempt Auditing combination of username,
password and permissions
is the mechanism by which
Hyper-V server authenticate
a user for access and
authorize the user to
perform activities.

Cluster Based on event Error Manual Host mode failed to

communication 1570 Microsoft-Windows- establish a communication
session failed FailoverClustering session while joining the
cluster.

Cluster host node Based on event Error Manual This cluster node has no
network 1554 Microsoft-Windows- network connectivity. It
connectivity error FailoverClustering cannot participate in the
cluster until connectivity is
restored.

Cluster hosts Based on event Error Manual Host node has established a
update version 1548 Microsoft-Windows- communication session with
mismatch FailoverClustering another node and detected
that it is running a different
but compatible version of
the cluster service software.

Cluster network Based on event Warning Manual Cluster network interface

failure 1127 Microsoft-Windows- for cluster node has failed.
FailoverClustering

127 | Veeam ONE | Working with Alarms | REV 7

Cluster witness Based on event Error Manual The cluster service detected
resource failure 1558 Microsoft-Windows- a problem with the witness
FailoverClustering resource. The witness
resource will be failed over
to another node within the
cluster in an attempt to
reestablish access to cluster
configuration data.

Cluster witness Based on event Error Manual Cluster service failed to

resource update 1557 Microsoft-Windows- update the cluster
failure FailoverClustering configuration data on the
witness resource.

Host available Average Hyper-V Services memory usage Warning Automatic This host is low on available
memory for 15 minutes is above 80% memory.

Average Hyper-V Services memory usage Error

for 15 minutes is above 90%

Host average disk Average disk queue length for 15 Warning Automatic Average disk queue length
queue length minutes is above 1 on the host may report on
too many I/O requests. This
means that not all requests
Average disk queue length for 15 Error
are queued. Some requests
minutes is above 2
are completed and are on
their way back to where the
performance data is being
collected.

Host average Average pressure for 15 minutes is above Warning Automatic This host has exceeded the
memory pressure 90% threshold for memory
pressure.
Average pressure for 15 minutes is above Error
100%

Host cluster Based on event Error Manual The Cluster service cannot
membership 1093 Microsoft-Windows- identify host node as a
FailoverClustering member of failover cluster.

Host connection State not equals Connected for 5 minutes Error Automatic This alarm monitors Hyper-
failure or more V host connection state.

Host CPU time per Average host CPU wait time for 15 Warning Automatic The counter shows the
dispatch minutes is 60 microseconds average time Virtual
Machines running on the
host spent waiting for a
Average host CPU wait time for 15 Error
virtual processor to be
minutes is 100 microseconds dispatched onto a logical
processor. More vCPUs on
host means more things the
dispatcher has to schedule
thus wait time raises.

Host CPU usage Average Total Run Time value for 15 Warning Automatic This host has exceeded the
minutes is above 75% threshold for CPU usage.

128 | Veeam ONE | Working with Alarms | REV 7

 Average Total Run Time value for 15 Error
minutes is above 85%

Host failed to Based on event Error Manual Host node failed to form a
form a cluster 1546 Microsoft-Windows- failover cluster.
FailoverClustering

Host Image *Hyper-V Image Management* service is Error Automatic The service required to
Management not running for 5 minutes or more manage virtual storage is
service is not not running. No virtual
running storage management
operations can be
performed.

Host Memory Average pages/sec value for 15 minutes Warning Automatic The counter shows the rate
Pages Usage is above 500 at which pages are read
from or written to disk to
resolve hard page faults.
Average pages/sec value for 15 minutes Error
This counter is a primary
is above 1500
indicator of the types of
faults that cause system-
wide delays.

Host network Average network output queue length for Warning Automatic This host has exceeded the
average output 15 minutes is above 1 threshold for the length of
queue length the queue in packets. This
counter should be 0 at all
Average network output queue length for Error
times.
15 minutes is above 2

Host network Average network outbound errors Warning Automatic This host has exceeded the
outbound errors number for 15 minutes is above 1 threshold for the outbound
number packets that couldn't be
transmitted because of
Average network outbound errors Error
errors.
number for 15 minutes is above 2

Host Networking *Hyper-V Networking Management* Error Automatic The Hyper-V Networking
Management service is not running for 5 minutes or Management Service is not
service is not more configured to start
running automatically. Virtual
networks cannot be
managed until the service is
started.

Host node failed Based on event Error Manual Host node failed to form a
to form a cluster 1573 Microsoft-Windows- cluster.
FailoverClustering

Host node failed Based on event Error Manual Host node failed to join the
to join cluster 1572 Microsoft-Windows- cluster because it could not
FailoverClustering send and receive failure
detection network messages
with other cluster nodes.

Host node was Based on event Warning Manual Cluster host node has been
evicted from 1011 Microsoft-Windows- evicted from the failover
cluster FailoverClustering cluster.

129 | Veeam ONE | Working with Alarms | REV 7

Host node was Based on event Error Manual Cluster node was removed
removed from 1135 Microsoft-Windows- from the active failover
cluster FailoverClustering cluster membership. If the
Cluster service fails to start
on a failover cluster node,
the node cannot function as
part of the cluster.

Host restart Based on event Information Automatic Host operation system has
1074 User32 been restarted or shut
down.

Missing latest Based on event Error Manual The cluster service has
cluster 1561 Microsoft-Windows- determined that this node
configuration FailoverClustering does not have the latest
data copy of cluster configuration
data. Therefore, the cluster
service has prevented itself
from starting on this node.

Network Based on event Warning Manual Cluster node lost

communication 1592 Microsoft-Windows- communication with another
failure FailoverClustering cluster node. Network
communication was
reestablished.

Unreachable Based on event Warning Manual Cluster network interface

cluster network 1126 Microsoft-Windows- for cluster node is
interface FailoverClustering unreachable by at least one
other cluster node attached
to the network.

Virtual Machine *Hyper-V Virtual Machine Management* Error Automatic The service required to
Management service is not running manage virtual machines is
service is not not running. No virtual
running machine management
operations can be
performed.

Virtual Machine
Resolve
Alarm Name Event/Condition Severity Description
Action

Background disk Based on event Warning Manual The parent virtual hard
merge failed 19100 Microsoft-Windows-Hyper-V-VMMS disks associated with this
virtual machine may be in
an inconsistent state.

Background disk Based on event Warning Manual The snapshot merge

merge 19090 Microsoft-Windows-Hyper-V-VMMS operation was interrupted.
interruption

Checkpoint Based on event Error Manual The configuration of

configuration is 16420 Microsoft-Windows-Hyper-V-VMMS checkpoint is no longer
not accessible accessible.

130 | Veeam ONE | Working with Alarms | REV 7

Current memory Average memory pressure for 15 minutes Warning Automatic This VM has exceeded the
pressure is above 90% threshold for memory
pressure.
Average memory pressure for 15 minutes Error
is above 100%

Failed to assign Based on event Error Manual Dynamic MAC address for
dynamic MAC 12572 Microsoft-Windows-Hyper-V- VM network adapter was
address SynthNic not assigned.

Failed to create Based on event Error Manual Failed to create memory

memory contents 3320 Microsoft-Windows-Hyper-V-Worker contents file.
file

Failed to create Based on event Error Manual Failed to create or access

VM saved state 3080 Microsoft-Windows-Hyper-V-Worker VM saved state file.
file

Failed to delete Based on event Warning Manual Cannot delete VM directory.

VM directory 16150 Microsoft-Windows-Hyper-V-VMMS

Failed to initialize Based on event Error Manual Failed to initialize VM

VM memory 3050 Microsoft-Windows-Hyper-V-Worker memory.

Failed to merge Based on event Warning Manual Cannot merge disk file on
virtual disk 16210 Microsoft-Windows-Hyper-V-VMMS deletion. As a result, this
disk might be in inconsistent
state.

Failed to power Based on event Error Manual Failed to power on VM.

on VM 12010 Microsoft-Windows-Hyper-V-
Worker

Based on event
12030 Microsoft-Windows-Hyper-V-
Worker

Based on event
12040 Microsoft-Windows-Hyper-V-
Worker

Based on event
12050 Microsoft-Windows-Hyper-V-
Worker

Failed to restore Based on event Error Manual Failed to restore a VM.

VM 12080 Microsoft-Windows-Hyper-V-
Worker

Failed to save VM Based on event Error Manual Failed to save state for a
12054 Microsoft-Windows-Hyper-V- VM.
Worker

Guest disk space Guest disk free space is below 10% Warning Automatic Guest OS volume is low on

131 | Veeam ONE | Working with Alarms | REV 7

 available guest disk space.
Guest disk free space is below 5% Error

Hyper-V VM VM checkpoint age is 48 hours or more Warning Automatic The age of the checkpoint
checkpoint age (latest) for this VM has
exceeded the configured
threshold.

Hyper-V VM Hyper-V VM checkpoint size is above Warning Automatic The VM has been running
checkpoint size 10% of the VM size on a checkpoint for
extended period of time,
which exceeded the
Hyper-V VM checkpoint size is above Error
configured threshold for the
20% of the VM size
checkpoint size. A
checkpoint preserves the
state and data of a VM at a
specific point in time.

Incompatible Based on event Warning Manual The version of a component

version of 4010 Microsoft-Windows-Hyper-V- of integration services is
integration Integration incompatible with another
services version.

Insufficient disk Based on event Warning Manual Hyper-V disk space is low
space 16050 Microsoft-Windows-Hyper-V-VMMS on available free space.

Invalid static MAC Based on event Error Manual By default, new virtual
address 12560 Microsoft-Windows-Hyper-V- machines in Hyper-V are
SynthNic created with NICs that are
assigned dynamic MAC
addresses.
Based on event
12560 Microsoft-Windows-Hyper-V-
Worker

Based on event
12560 Microsoft-Windows-Hyper-V-VMMS

Machine remoting Based on event Warning Manual Failure in machine remoting

system failure 12480 Microsoft-Windows-Hyper-V- system has been detected.
Worker

No disk space to Based on event Error Manual VM has been paused

run this VM 16060 Microsoft-Windows-Hyper-V-VMMS because it has run out of
disk space.

Not enough Based on event Error Manual Hyper-V was unable to

memory to start a 3122 Microsoft-Windows-Hyper-V-Worker allocate RAM resources to
VM start this VM.
Based on event
3030 Microsoft-Windows-Hyper-V-Worker

Possible Total Run Time is above 70% Warning Automatic Veeam ONE detected
ransomware and suspicious activity on this
activity Virtual Storage Write is above 40 MB/s VM.
or
Virtual Network Bytes Sent/sec is above
40 MB/s for 5 minutes

132 | Veeam ONE | Working with Alarms | REV 7

 Total Run Time is above 80% Error
and
Virtual Storage Write is above 60 MB/s
or
Virtual Network Bytes Sent/sec is above
60 MB/s for 5 minutes

Static MAC Based on event Warning Manual By default, new virtual

address conflict 12562 Microsoft-Windows-Hyper-V- machines in Hyper-V are
SynthNic created with NICs that are
assigned dynamic MAC
addresses.
Based on event
12562 Microsoft-Windows-Hyper-V-
Worker

Unexpected VM Based on event Error Manual This VM has encountered an

error 16020 Microsoft-Windows-Hyper-V-VMMS unexpected error.

VM configuration Based on event Error Manual The configuration of virtual

is not accessible 16410 Microsoft-Windows-Hyper-V-VMMS machine is no longer
accessible.
Based on event
16400 Microsoft-Windows-Hyper-V-VMMS

VM configuration Based on event Error Manual The VM configuration is no

module error 4096 Microsoft-Windows-Hyper-V-Config longer accessible.

VM CPU usage Average guest run time for 15 minutes is Warning Automatic This VM has exceeded the
above 75% threshold for CPU usage.

Average guest run time for 15 minutes is Error

above 85%

VM disk errors Average number of errors/min for 15 Warning Automatic This VM has logged one or
minutes is above 4 more errors that have
occurred on its virtual
device.
Average number of errors/min for 15 Error
minutes is above 8

VM guest OS Based on event Information Warning Virtual Machine was

reboot 18514 Microsoft-Windows-Hyper-V- rebooted. This warning is
Worker applied only to Windows
Server 2012 and Windows
Server 2012 R2.

VM initialization Based on event Error Manual VM initialization has failed.

error 3040 Microsoft-Windows-Hyper-V-Worker

VM invalid switch Based on event Error Manual The virtual machine cannot
port reference 12570 Microsoft-Windows-Hyper-V- be started.
SynthNic

133 | Veeam ONE | Working with Alarms | REV 7

VM restart Based on event Information Automatic Virtual Machine was
18512 Microsoft-Windows-Hyper-V- rebooted. This warning is
Worker applied only to Windows
Server 2012 and Windows
Server 2012 R2.

VM shutdown by Based on event Information Automatic Virtual Machine was shut

guest 18508 Microsoft-Windows-Hyper-V- down. This warning is
Worker applied only to Windows
Server 2012 and newer
Windows server versions.

VM shutdown by Based on event Information Automatic Virtual Machine was shut

host 18504 Microsoft-Windows-Hyper-V- down. This warning is
Worker applied only to Windows
Server 2012 and newer
Windows server versions.

VM vCPU time per Average CPU wait time for 15 minutes is Warning Automatic The counter shows the
dispatch above 60 microseconds average time spent waiting
for a virtual processor to be
dispatched onto a logical
Average CPU wait time for 15 minutes is Error
processor.
above 100 microseconds

VM with no No backup restore points for the past 24 Warning Automatic This VM has not been
backups hours backed up within the
defined RPO (Recovery
Point Objective) interval.

VM with no No replica restore points for the past 24 Warning Automatic This VM has not been
replica hours replicated within the defined
RPO (Recovery Point
Objective) interval.

VSS checkpoint Based on event Error Manual Failed to create the backup
failure 10102 Microsoft-Windows-Hyper-V-VMMS of virtual machine.

Based on event Error

15252 Microsoft-Windows-Hyper-V-VMMS

Cluster
Resolve
Alarm Name Event/Condition Severity Description
Action

Cluster Based on event Error Manual An attempt to forcibly start

configuration 1575 Microsoft-Windows- the cluster service has failed
data is missing or FailoverClustering because the cluster
corrupt configuration data on host
node is either missing or
corrupt.

134 | Veeam ONE | Working with Alarms | REV 7

Cluster Based on event Error Manual The failover cluster
configuration 1593 Microsoft-Windows- database could not be
database cannot FailoverClustering unloaded and any
be unloaded potentially incorrect
changes in memory could
not be discarded. The
cluster service will attempt
to repair the database by
retrieving it from another
cluster node.

Cluster database Based on event Error Manual The cluster database could
could not be 1057 Microsoft-Windows- not be loaded. Ensure that
loaded FailoverClustering a good copy of the cluster
configuration is available to
the node.

Cluster memory Based on event Resolve Automatic When placing a virtual

overcommitment VeeamHvClusterReserveStateOkEvent machine in a failover
cluster, the placement
process calculates whether
Based on event Error
the new virtual machine will
VeeamHvClusterReserveStateErrorEvent
over-commit the cluster. If
the action will over-commit
the cluster, the
corresponding alarm will be
fired.

Cluster network is Based on event Warning Manual Cluster network is down.

down 1130 Microsoft-Windows-
FailoverClustering

Cluster resource Based on event Error Manual Cluster network name

cannot be 1207 Microsoft-Windows- resource cannot be brought
brought online FailoverClustering online. The computer object
associated with the
resource could not be
updated in domain.

Cluster resource Based on event Error Manual Cluster resource in

failure 1069 Microsoft-Windows- clustered service or
FailoverClustering application has failed.

Cluster service Based on event Error Manual The Cluster service cannot
cannot be started 1090 Microsoft-Windows- be started. An attempt to
FailoverClustering read configuration data
from the Windows registry
failed.

Cluster service Based on event Error Manual The Cluster service failed to
failed to start 1105 Microsoft-Windows- start because it was unable
FailoverClustering to register interface(s) with
the RPC service.

135 | Veeam ONE | Working with Alarms | REV 7

Cluster service Based on event Warning Manual Cluster service could not
failed to write 1080 Microsoft-Windows- write to a file. In a failover
data to a file FailoverClustering cluster, most clustered
services or applications use
at least one disk, also called
a disk resource, that you
assign when you configure
the clustered service or
application. Clients can use
the clustered service or
application only when the
disk is functioning correctly.

Cluster service Based on event Error Manual Cluster service suffered an

fatal error 1000 Microsoft-Windows- unexpected fatal error.
FailoverClustering

Cluster service Based on event Error Manual Cluster service was halted
interruption 1006 Microsoft-Windows- due to incomplete
FailoverClustering connectivity with other
cluster nodes.

Cluster service Based on event Error Manual The Cluster service is

shut down 1177 Microsoft-Windows- shutting down because
FailoverClustering quorum was lost.

Cluster Shared Based on event Warning Automatic Cluster Shared Volume is no

Volume is not 5120 Microsoft-Windows- longer available on this
available FailoverClustering node. All I/O will
temporarily be queued until
a path to the volume is
Based on event Resolve
reestablished.
5122 Microsoft-Windows-
FailoverClustering

Cluster Shared Based on event Warning Automatic Cluster Shared Volume is no

Volume is not 5121 Microsoft-Windows- longer directly accessible
directly accessible FailoverClustering from this cluster node. I/O
access will be redirected to
the storage device over the
Based on event Resolve network through the node
5122 Microsoft-Windows- that owns the volume. This
FailoverClustering may result in degraded
performance.

Failed to bring Based on event Error Manual Cluster IP address resource

cluster resource 1049 Microsoft-Windows- cannot be brought online.
online FailoverClustering

Failed to copy Based on event Warning Manual The restore request for the
cluster 1581 Microsoft-Windows- cluster configuration data
configuration FailoverClustering failed to make a copy of the
data file existing cluster
configuration data file
(ClusDB).

136 | Veeam ONE | Working with Alarms | REV 7

Failed to create Based on event Error Manual Cluster network name
cluster resource 1193 Microsoft-Windows- resource failed to create its
name in domain FailoverClustering associated computer object
in domain.

Failed to migrate Based on event Error Manual Live migration for this VM
virtual machine 22506 Microsoft-Windows-Hyper-V-High- did not succeed.
Availability

Based on event
22505 Microsoft-Windows-Hyper-V-High-
Availability

Based on event
21100 Microsoft-Windows-Hyper-V-High-
Availability

Failed to unload Based on event Error Manual The failover cluster

failover cluster 1574 Microsoft-Windows- database could not be
database FailoverClustering unloaded.

Inconsistency Based on event Error Manual The Cluster service was

within the failover 1073 Microsoft-Windows- halted to prevent an
cluster FailoverClustering inconsistency within the
failover cluster.

Invalid IP address Based on event Error Manual Cluster IP address resource

detected 1047 Microsoft-Windows- cannot be brought online
FailoverClustering because the address value
is invalid.

Invalid IP address Based on event Error Manual Cluster IP address resource

for cluster 1360 Microsoft-Windows- failed to come online.
resource FailoverClustering

Invalid subnet Based on event Error Manual Cluster IP address resource

mask detected 1046 Microsoft-Windows- cannot be brought online
FailoverClustering because the subnet mask
value is invalid.

Unexpected Based on event Error Manual The cluster service

cluster service 1556 Microsoft-Windows- encountered an unexpected
problem FailoverClustering problem and will be shut
down.

Cluster Shared Volume

Resolve
Alarm Name Event/Condition Severity Description
Action

Active filter Based on event Warning Manual Cluster Shared Volume has
drivers detected 5125 Microsoft-Windows- identified one or more
FailoverClustering active filter drivers on this

137 | Veeam ONE | Working with Alarms | REV 7

 device stack that could
Based on event interfere with CSV
5126 Microsoft-Windows- operations. I/O access will
FailoverClustering be redirected to the storage
device over the network
through another Cluster
node. This may result in
degraded performance.

Cluster Shared Average read latency for 15 minutes is Warning Automatic Cluster Shared Volume has
Volume 2012 read above 40 milliseconds exceeded the configured
latency threshold of total read
latency.
Average read latency for 15 minutes is Error
above 80 milliseconds

Cluster Shared Average write latency for 15 minutes is Warning Automatic Cluster Shared Volume has
Volume 2012 above 40 milliseconds exceeded the configured
write latency threshold of total write
latency.
Average write latency for 15 minutes is Error
above 80 milliseconds

Cluster Shared Free space is below 10% Warning Automatic Cluster Shared Volume is
Volume free space low on available free space.
Free space is below 5% Error

Redirected access Based on event Warning Manual Cluster Shared Volume

was turned on 5136 Microsoft-Windows- redirected access was
FailoverClustering turned on. Access to the
storage device will be
redirected over the network
from all cluster nodes that
are accessing this volume.
This may result in degraded
performance.

Volume snapshot Based on event Error Manual A backup application

preparation error 1584 Microsoft-Windows- initiated a VSS snapshot on
FailoverClustering Cluster Shared Volume
without properly preparing
the volume for snapshot.
This snapshot may be
invalid and the backup may
not be usable for restore
operations.

Local Storage
Resolve
Alarm Name Event/Condition Severity Description
Action

Datastore read Avg Disk sec/Read value for 15 minutes Warning Automatic This host local disk has
latency is 40 milliseconds exceeded the threshold for

138 | Veeam ONE | Working with Alarms | REV 7

 total read latency. This
Avg Disk sec/Read value for 15 minutes Error performance monitor
is 80 milliseconds counter measures the
amount of time that read
operations take to respond
to the operating system.

Datastore write Avg Disk sec/Write value for 15 minutes Warning Automatic This host disk has exceeded
latency is 40 milliseconds the threshold for total write
latency. This performance
monitor counter measures
Avg Disk sec/Write value for 15 minutes Error
the amount of time that
is 80 milliseconds
write operations take to
respond to the operating
system.

Local volume free Free space is below 10% Warning Automatic Local volume is low on
space available free space.
Free space is below 5% Error

Any Hyper-V Object

Resolve
Alarm Name Event/Condition Severity Description
Action

Cluster Shared Based on event Error Manual Cluster Shared Volume is no

Volume is no 5142 Microsoft-Windows- longer accessible from this
longer accessible FailoverClustering cluster node because of
error.

Failed to load VM Based on event Error Manual Cannot load a virtual

configuration 16300 Microsoft-Windows-Hyper-V-VMMS machine configuration

Failed to open VM Based on event Error Manual Cannot open VM

attachment 12290 Microsoft-Windows-Hyper-V- attachment.
Worker

Based on event
12290 Microsoft-Windows-Hyper-V-
SynthStor

Based on event
12290 Microsoft-Windows-Hyper-V-VMMS

Based on event
12140 Microsoft-Windows-Hyper-V-VMMS

Based on event
12140 Microsoft-Windows-Hyper-V-
Worker

Based on event
12140 Microsoft-Windows-Hyper-V-
SynthStor

139 | Veeam ONE | Working with Alarms | REV 7

 Based on event
12240 Microsoft-Windows-Hyper-V-VMMS

Based on event
12240 Microsoft-Windows-Hyper-V-
Worker

Based on event
12240 Microsoft-Windows-Hyper-V-
SynthStor

Failed to register Based on event Warning Manual The Hyper-V Virtual

VM configuration 20100 Microsoft-Windows-Hyper-V-VMMS Machine Management
file service failed to register the
configuration for the virtual
machine.

Failed to revert to Based on event Error Manual Failed to revert to VSS

VSS snapshot 10104 Microsoft-Windows-Hyper-V-VMMS snapshot on one or more
virtual hard disks of the
virtual machine.

Failed to Based on event Warning Manual The Hyper-V Virtual

unregister VM 20102 Microsoft-Windows-Hyper-V-VMMS Machine Management
configuration file service failed to unregister
the configuration for the
virtual machine.

Failed to verify Based on event Warning Manual The Hyper-V Virtual

VM configuration 20104 Microsoft-Windows-Hyper-V-VMMS Machine Management
file service failed to verify that
the configuration is
registered for the virtual
machine.

VM configuration Based on event Error Manual Cannot load the virtual

file is corrupt 16310 Microsoft-Windows-Hyper-V-VMMS machine because the
configuration is corrupt.

140 | Veeam ONE | Working with Alarms | REV 7

Internal Alarms
The following table describes internal Veeam ONE alarms.

Alarm Name Event/Condition Severity Description

Backup Based on event Error Veeam ONE failed to collect performance data
VeeamBpPerfCollectionFailedEvent from the specified backup server.
performance
data collection Based on event Resolve
failure VeeamMonitorServicesStartedEvent

Based on event Resolve

VeeamBpPerfCollectionFailedResolved
Event

Backup server Based on event Error Veeam ONE failed to collect data from a Veeam
data collection VeeamNoHostConnectionEvent Backup & Replication server.
problem
Based on event Resolve
VeeamNoHostConnectionResolvedEve
nt

Based on event Resolve

VeeamMonitorServicesStartedEvent

Disk cache error Based on event Warning Veeam ONE failed to write performance data to
VeeamDPCacheEvent the disk cache folder.

Based on event Resolve

VeeamDPCacheResolvedEvent

Based on event Resolve

VeeamMonitorServicesStartedEvent

Events data Based on event Error Veeam ONE failed to collect events data from the
collection failure VeeamEventCollectionFailedEvent objects specified.

Based on event Resolve

VeeamEventCollectionFailedResolvedE
vent

Based on event Resolve

VeeamMonitorServicesStartedEvent

Hardware sensors Based on event Error Veeam ONE failed to collect host hardware
collection failure VeeamHardwareSensorsCollectionEve information.
nt

Based on event Resolve

VeeamHardwareSensorsCollectionRes
olvedEvent

141 | Veeam ONE | Working with Alarms | REV 7

 Based on event Resolve
VeeamMonitorServicesStartedEvent

Performance data Based on event Error Veeam ONE failed to collect performance data
collection failure VeeamPerfCollectionFailedEvent from the objects specified.

Based on event Resolve

VeeamPerfCollectionFailedResolvedEv
ent

Based on event Resolve

VeeamMonitorServicesStartedEvent

SQL Server Based on event Warning Veeam ONE database size is close to maximum
Express database VeeamSqlLowDbFreeSpaceEvent database size supported by SQL Server Express
size Edition.
Based on event Resolve
VeeamSqlLowDbFreeSpaceResolvedEv
ent

Based on event Resolve

VeeamMonitorServicesStartedEvent

Topology Based on event Error Veeam ONE failed to collect infrastructure

collection failure VeeamInfCollectionFailedEvent topology.

Based on event Resolve

VeeamInfCollectionFailedResolvedEve
nt

Based on event Resolve

VeeamMonitorServicesStartedEvent

vCloud Director Based on event Error Veeam ONE failed to update vCloud Director
blocking tasks VeeamVcdBlockingTaskUpdateFailedE blocking tasks list.
update failure vent

Based on event Resolve

VeeamVcdBlockingTaskUpdateFailedR
esolvedEvent

vCloud Director Based on event Error Veeam ONE failed to collect performance and
connection failure VeeamNoVcdHostConnectionEvent configuration data from vCloud Director.

Based on event Resolve

VeeamNoVcdHostConnectionResolved
Event

Based on event Resolve

VeeamMonitorServicesStartedEvent

vCloud Director Based on event Error Veeam ONE failed to update vCloud Director
stranded items VeeamVcdStrandedItemUpdateFailedE stranded items list.
update failure vent

142 | Veeam ONE | Working with Alarms | REV 7

 Based on event Resolve
VeeamVcdStrandedItemUpdateFailedR
esolvedEvent

Veeam ONE Based on event Warning Veeam ONE license is going to expire soon.
license expiration VeeamLicenseExpirationWarningEvent
date
Based on event Error
VeeamLicenseExpirationErrorEvent

Based on event Resolve

VeeamLicenseChangedEvent

Based on event Resolve

VeeamLicenseExpirationResolvedEven
t

Based on event Resolve

VeeamMonitorServicesStartedEvent

Veeam ONE Based on event Error The number of licensed servers has been
license sockets VeeamSocketExceedEvent exceeded.
exceeded
Based on event Resolve
VeeamSocketExceedResolvedEvent

Based on event Resolve

VeeamMonitorServicesStartedEvent

Veeam ONE Based on event Warning License update failure can take place for a number
license update VeeamLicenseUpdateErrorEvent of reasons such as connection failure, invalid
failure identifier, expired contract, etc. In case of a
connection problem and licensing server key
Based on event Resolve generation error, Veeam ONE will retry to update
VeeamLicenseUpdateResolvedEvent the license key.

Based on event Resolve

VeeamMonitorServicesStartedEvent

Veeam ONE Based on event Error Your license limit has been exceeded. You need to
license VMs VeeamVMsExceedErrorEvent purchase additional VMs licensing before all VMs
exceeded exceeding the licensed amount will no longer be
monitored.
Based on event Warning
VeeamVMsExceedWarningEvent

Based on event Resolve

VeeamVMsExceedResolvedEvent

Based on event Resolve

VeeamMonitorServicesStartedEvent

Veeam ONE Job state equals Failed. Error Veeam ONE Reporter session task failed.
Reporter
collection job
Job state equals Warning. Warning

143 | Veeam ONE | Working with Alarms | REV 7

Veeam ONE Veeam ONE Server CPU Usage is Error Veeam ONE Server load is too high.
Server Load above 90%
(available since or
Veeam ONE 9.5 Veeam ONE Server Memory Usage is
Update 3) above 95%

Veeam ONE Server CPU Usage is Warning

above 75%
or
Veeam ONE Server Memory Usage is
above 85%

Veeam ONE Based on event Warning Veeam ONE support period is going to expire soon.
support VeeamLicenseSupportExpirationWarni
expiration date ngEvent

Based on event Error

VeeamLicenseSupportExpirationErrorE
vent

Based on event Resolve

VeeamLicenseChangedEvent

Based on event Resolve

VeeamLicenseSupportExpirationResolv
edEvent

Based on event Resolve

VeeamMonitorServicesStartedEvent

Virtual Server Based on event Error Connection to virtual server has failed.
connection failure VeeamNoHostConnectionEvent

Based on event Resolve

VeeamNoHostConnectionResolvedEve
nt

Based on event Resolve

VeeamMonitorServicesStartedEvent

144 | Veeam ONE | Working with Alarms | REV 7

Appendix B. Alarm Rules
This section describes rules that can be used to create alarms for virtual and backup infrastructures.

145 | Veeam ONE | Working with Alarms | REV 7

Alarm Rules for VMware vSphere
Veeam ONE offers the following types of alarm rules for VMware vSphere infrastructure objects:

 vCenter Server

 Cluster

 Host

 Virtual Machine

 Datastore

 Any Object

 vCloud Director vApp

 vCloud Director Organization

 vCloud Director Org VDC

 vCloud Director Provider VDC

 Resource Pool

vCenter Server
Rule Type Description

Event-based rule An alarm is triggered if some vCenter-related event is generated.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the vCenter Server state reports to be equal or not equal to a
changes specific state value (for example, if vCenter Server is not responding).

Cluster
Rule Type Description

Event-based rule An alarm is triggered if some cluster-related event is generated.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified threshold
allowed range value (for example, if the memory usage exceeds 80%).

146 | Veeam ONE | Working with Alarms | REV 7

Host
Rule Type Description

Event-based rule An alarm is triggered if some host-related event is generated.

Hardware sensor state An alarm is triggered if the sensor state reports to be equal or not equal to a specific state
changes value (Normal, Warning, Alert, Unknown).

Number of VMs is out of An alarm is triggered if the number of running, powered off or suspended VMs on the
allowed range ESX(i) host is above or below the specified threshold value. This type of alarm can be
configured if it is necessary to limit the number of VMs running on the ESX(i) host at the
same time to avoid the host overload.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the host state reports to be equal or not equal to a specific state
changes value (for example, if the ESX(i) host is not responding).

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified threshold
allowed range value (for example, if the CPU usage exceeds 75%).

Virtual Machine
Rule Type Description

Event-based rule An alarm is triggered if some VM-related event is generated (for example, if the MAC
address of the VM conflicts with the MAC address of another VM existing in the virtual
infrastructure).

Orphaned Veeam Backup & An alarm is triggered if a VM has a snapshot that Veeam Backup & Replication created (to
Replication snapshot has back up, replicate or perform another data protection operation for the VM) but was unable
been detected to remove when the operation was over.

Heartbeat is missing An alarm is triggered if a monitored virtual machine is not available or overloaded for a
specific period of time (for example, if heartbeat is missing for 5 minutes).

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the state of the VM reports to be equal or not equal to the specified
changes state value (for example, if the VM is suspended).

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified value (for
allowed range example, if the CPU ready level exceeds 5%).

Guest volumes are running An alarm is triggered if available disk space on guest volumes is above or below the
out of free disk space specified threshold value. You can choose to specify the amount of due free space as an
absolute value (for example, if free disk space falls below 1 GB) or a relative value (for
example, if free disk space falls below 10% of total space).

147 | Veeam ONE | Working with Alarms | REV 7

Snapshot age for VM has An alarm is triggered if the current snapshot is older than a specified number of hours. This
exceeded the configured rule helps monitor forgotten snapshots that are consuming valuable storage space and
threshold degrading performance of virtual machines.

VM snapshots number has An alarm is triggered if the number of snapshots created for the VM is greater than the
exceeded the configured specified threshold.
threshold

Snapshot size for VM is out An alarm is triggered if the size of the VM snapshot is above or below the specified
of allowed range threshold value. You can choose to specify the size of the snapshot as an absolute value
(for example, if the snapshot size exceeds 5 GB) or a relative value (for example, if the
snapshot size exceeds 10% of total available disk space).

VMware VM tools state An alarm is triggered if the state of the VMware Tools reports to be equal or not equal to
changes the specified state value (for example, if the VMware Tools is out of date).

VMs with no restore points An alarm is triggered if the age of the latest backup or replica restore point for the VM has
exceeded the threshold (that is, if there are no restore points for the specified RPO period).

Datastore
Rule Type Description

Event-based rule An alarm is triggered if some datastore-related event is generated.

Datastore is running out of An alarm is triggered if free space on the datastore is above or below the specified
free space threshold value. You can choose to specify the free space threshold as an absolute value
(for example, if the datastore space should not fall below 10 GB) or a relative value (for
example, if the datastore free space should not fall below 15% of total space).

Datastore provisioned An alarm is triggered if the provisioned disk space is above or below the specified threshold
space value. You can select to specify the threshold as an absolute value (for example, if the
provisioned disk space should not exceed 500 GB) or a relative value (for example, if the
provisioned disk space should not exceed 400% compared to the datastore capacity).

Datastore speed An alarm is triggered if the speed of datastore operations is above or below the specified
threshold value.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the state of the datastore reports to be equal or not equal to the
changes specified state value (for example, if the datastore is not accessible).

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified threshold
allowed range value (for example, if the datastore I\O threshold is violated).

148 | Veeam ONE | Working with Alarms | REV 7

Any Object
Rule Type Description

Event-based rule An alarm is triggered if some event is generated on any object in the infrastructure.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

vCloud Director vApp

Rule Type Description

Event-based rule An alarm is triggered if some vApp-related event in generated.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified threshold
allowed range value (for example, if the storage usage exceeds 80%).

vCloud Director object task An alarm is triggered if the vApp state reports to be equal or not equal to a specific state
status value (for example, if warnings are registered for the vApp).

System health status An alarm is triggered if the object health state changes.
change

vApp runtime lease An alarm is triggered in N days after the vApp runtime lease has expired.
timeout

vApp storage lease timeout An alarm is triggered in N days after the vApp storage lease has expired.

vCloud Director Organization

Rule Type Description

Event-based rule An alarm is triggered if some event is generated on the organization.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Organization VCD blocking An alarm is triggered if the number of pending blocking tasks has exceeded the specified
task number threshold.

Organization VCD blocking An alarm is triggered in N minutes after the blocking tasks has expired.
task timeout

vCloud Director object task An alarm is triggered if the organization state reports to be equal or not equal to a specific
status state value (for example, if warnings are registered for the organization).

149 | Veeam ONE | Working with Alarms | REV 7

System health state An alarm is triggered if the object health state changes.
change

vCloud Director Org VDC

Rule Type Description

Event-based rule An alarm is triggered if some event is generated on the organization VCD.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified value (for
allowed range example, if the CPU ready level exceeds 5%).

vCloud Director object task An alarm is triggered if the organization VCD state reports to be equal or not equal to a
status specific state value (for example, if warnings are registered for the organization VCD).

System health status An alarm is triggered if the object health state changes.
change

Network pool is running An alarm is triggered if the number of remaining IP addresses is above or below the
out of available IP specified threshold value. You can select to specify the threshold as an absolute value (for
addresses example, if the number of remaining IP addresses should not be lower than 5) or a relative
value (if the number of remaining IP addresses should not be lower than 10% of the total
number for the organization VCD network).

vCloud Director Provider VDC

Rule Type Description

Event-based rule An alarm is triggered if some event is generated on the provider VCD.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified value (for
allowed range example, if the storage usage exceeds 80%).

vCloud Director object task An alarm is triggered if the provider VCD state reports to be equal or not equal to a specific
status state value (for example, if warnings are registered for the provider VCD).

System health status An alarm is triggered if the object health state changes.
change

150 | Veeam ONE | Working with Alarms | REV 7

Resource Pool
Rule Type Description

Event-based rule An alarm is triggered if some event is generated on a resource pool.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified value (for
allowed range example, if the CPU usage exceeds 80%).

151 | Veeam ONE | Working with Alarms | REV 7

Alarm Rules for Microsoft Hyper-V
Veeam ONE offers the following types of alarm rules for Microsoft Hyper-V infrastructure objects:

 Host

 Virtual Machine

 Cluster

 CSV

 Local Storage

 Any Object

Host
Rule Type Description

Event-based rule An alarm is triggered if some host-related event is generated.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Windows Server service An alarm is triggered if the state of the specified service reports to be equal or not equal to
state a specific state value for a specified time (for example, if a service is paused for 10
minutes).

Power or connection state An alarm is triggered if the host state reports to be equal or not equal to a specific state
changes value (for example, if the Hyper-V host is not responding).

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified threshold
allowed range value (for example, if the Total Run Time exceeds 75%).

Virtual Machine
Rule Type Description

Event-based rule An alarm is triggered if some VM-related event is generated (for example, if the MAC
address of the VM conflicts with the MAC address of another VM existing in the virtual
infrastructure).

Guest volumes are running An alarm is triggered if available disk space on guest volumes is above or below the
out of free disk space specified threshold value. You can choose to specify the amount of due free space as an
absolute value (for example, if free disk space falls below 1 GB) or a relative value (for
example, if free disk space falls below 10% of total space).

Checkpoint age for Hyper- An alarm is triggered if the current checkpoint is older than a specified number of hours.
V VM has exceeded the This rule helps monitor forgotten checkpoints that are consuming valuable storage space
configured threshold and degrading performance of virtual machines.

152 | Veeam ONE | Working with Alarms | REV 7

Checkpoint size for Hyper- An alarm is triggered if the size of the VM checkpoint is above or below the specified
V VM is out of allowed threshold value. You can choose to specify the size of the checkpoint as an absolute value
range (for example, if the checkpoint size exceeds 5 GB) or a relative value (for example, if the
checkpoint size exceeds 10% of total available disk space).

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified threshold
allowed range value (for example, if the Guest Run Time level exceeds 5%).

VMs with no restore points An alarm is triggered if the age of the latest backup or replica restore point for the VM has
exceeded the threshold (that is, if there are no restore points for the specified RPO period).

Cluster
Rule Type Description

Event-based rule An alarm will be triggered if some cluster-related event is generated.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Cluster Shared Volumes (CSV)

Rule Type Description

Event-based rule An alarm is triggered if some event occurs on Cluster Shared Volumes level.

CSV is running out of free An alarm is triggered if free space on the CSV is above or below the specified threshold
space value. You can choose to specify the free space threshold as an absolute value (for
example, if the CSV space should not fall below 10 GB) or a relative value (for example, if
the CSV free space should not fall below 15% of total space).

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Resource usage is out of An alarm is triggered if the specified counter is above or below the specified threshold
allowed range value.

Local Storage
Rule Type Description

Event-based rule An alarm is triggered if some storage-related event is generated.

Hyper-V datastore is An alarm is triggered if free space on the datastore is above or below the specified
running out of free space threshold value. You can choose to specify the free space threshold as an absolute value
(for example, if the datastore space should not fall below 10 GB) or a relative value (for
example, if the datastore free space should not fall below 15% of total space).

153 | Veeam ONE | Working with Alarms | REV 7

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Resource usage is out of An alarm will be triggered if the specified counter is above or below the specified threshold
allowed range value (for example, the average disk queue length exceed the threshold).

Any Object
Rule Type Description

Event-based rule An alarm is triggered if some event is generated on any object.

Existing alarm An alarm is triggered if the status of another alarm specified in the settings is changed.

Windows Server service An alarm is triggered if the state of the specified service reports to be equal or not equal to
state a specific state value for a specified time (for example, if a service is paused for 10
minutes).

154 | Veeam ONE | Working with Alarms | REV 7

Alarm Rules for Veeam Backup &
Replication
Veeam ONE offers the following types of alarm rules for Veeam Backup & Replication infrastructure objects:

 Enterprise Manager

 Backup Server

 Repository

 Proxy

 WAN Accelerator

 Tape Server

 Cloud Repository

 Cloud Gateway

Enterprise Manager
Rule Type Description

Event-based rule An alarm is triggered if some Veeam Backup & Replication event is generated for the
Veeam Backup Enterprise Manager.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the state of Veeam Backup Enterprise Manager is equal or not equal
changes to the specified value (for example, if connection to the Enterprise Manager is lost).

Backup Server
Rule Type Description

Event-based rule An alarm is triggered if some Veeam Backup & Replication event is generated for the
backup server.

Disabled job An alarm is triggered if the time during which a job was disabled has exceeded the
specified.

Job duration exceeded the An alarm is triggered if duration of a backup or replication job has exceeded a threshold
allowed time period duration value (specified in minutes).

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the state of Veeam Backup server is equal or not equal to the
changes specified value (for example, if connection to the backup server is lost).

155 | Veeam ONE | Working with Alarms | REV 7

Repository
Rule Type Description

Event-based rule An alarm is triggered if some Veeam Backup & Replication event is generated for the
repository.

Out-of-date state An alarm is triggered if Veeam Backup & Replication software components installed on the
repository server are out of date.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Repository server is An alarm is triggered if free space on the repository is above or below the specified
running out of free space threshold value. You can select to specify the free space threshold as an absolute value (for
example, if the storage space should not fall below 10 GB) or a relative value (for example,
if the free space should not fall below 15% of total space).

Power or connection state An alarm is triggered if the state of the backup repository is equal or not equal to the
changes specified value (for example, if connection to the repository is lost).

Proxy
Rule Type Description

Event-based rule An alarm is triggered if some Veeam Backup & Replication event is generated for the
backup proxy.

Out-of-date state An alarm is triggered if Veeam Backup & Replication software components installed on the
proxy server are out of date.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the state of backup proxy is equal or not equal to the specified
changes value (for example, if connection to the proxy server is lost).

WAN Accelerator
Rule Type Description

Event-based rule An alarm is triggered if some Veeam Backup & Replication event is generated for the WAN
accelerator.

Out-of-date state An alarm is triggered if Veeam Backup & Replication software components installed on the
WAN accelerator server are out of date.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

156 | Veeam ONE | Working with Alarms | REV 7

Power or connection state An alarm is triggered if the state of the WAN accelerator is equal or not equal to the
changes specified value (for example, if connection to the WAN accelerator is lost).

Tape Server
Rule Type Description

Event-based rule An alarm is triggered if some Veeam Backup & Replication event is generated for the tape
server.

Out-of-date state An alarm is triggered if Veeam Backup & Replication software components installed on the
tape server are out of date.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the state of the backup repository is equal or not equal to the
changes specified value (for example, if connection to the server is lost).

Cloud Repository
Rule Type Description

Event-based rule An alarm is triggered if some Veeam Backup & Replication event is generated for the cloud
repository.

Cloud repository lease An alarm is triggered if cloud repository lease time will expire in the specified number of
expiration days.

Number of VMs stored in An alarm is triggered if the number of VMs stored in the backup repository has exceeded
repository the specified threshold.

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Repository server is An alarm is triggered if free space on the repository is above or below the specified
running out of free space threshold value. You can select to specify the free space threshold as an absolute value (for
example, if the storage space should not fall below 10 GB) or a relative value (for example,
if the free space should not fall below 15% of total space).

Cloud Gateway
Rule Type Description

Event-based rule An alarm is triggered if some Veeam Backup & Replication event is generated for the cloud
gateway.

Out-of-date state An alarm is triggered if Veeam Backup & Replication software components installed on the
cloud gateway server are out of date.

157 | Veeam ONE | Working with Alarms | REV 7

Existing alarm An alarm is triggered if the state of another selected alarm is changed.

Power or connection state An alarm is triggered if the state of the backup repository is equal or not equal to the
changes specified value (for example, if connection to the cloud gateway is lost).

158 | Veeam ONE | Working with Alarms | REV 7