Beruflich Dokumente
Kultur Dokumente
0
User Guide October 2010
Copyright 2005 - 2010 Veeam Software Inc. All rights reserved worldwide. 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 Inc (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.
Important!
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.
Page | 2
CONTENTS
ABOUT THIS GUIDE .......................................................................................................................................... 6 OVERVIEW ............................................................................................................................................... 6 CONVENTIONS .......................................................................................................................................... 6 ABOUT VEEAM SOFTWARE ............................................................................................................................. 7 CONTACTING VEEAM SOFTWARE ................................................................................................................. 7 CONTACTING VEEAM SUPPORT ................................................................................................................... 7 OVERVIEW ......................................................................................................................................................... 8 ARCHITECTURE ............................................................................................................................................... 10 VEEAM MONITOR VERSIONS ..................................................................................................................... 10 DATA DISPLAYING .................................................................................................................................. 12 FULL SCREEN MODE ................................................................................................................................ 13 ALARMS ................................................................................................................................................ 14 Alarm Rules ........................................................................................................................... 14 Alarm Severity ....................................................................................................................... 16 Advanced Alarm Options ...................................................................................................... 16 EVENTS ................................................................................................................................................. 17 REPORTS ............................................................................................................................................... 17 ADVANCED MONITORING OPTIONS ........................................................................................................... 18 PLANNING AND PREPARATION .................................................................................................................... 19 PREREQUISITES ....................................................................................................................................... 19 REQUIREMENTS....................................................................................................................................... 19 System Requirements ............................................................................................................ 19 Required Permissions ............................................................................................................ 20 DEPLOYMENT ................................................................................................................................................. 21 VEEAM MONITOR FOR VMWARE INSTALLATION ........................................................................................... 21 Full Installation ..................................................................................................................... 21 Client-Only Installation ......................................................................................................... 25 UPGRADING VEEAM MONITOR FOR VMWARE .............................................................................................. 27 FREE AND PAID VERSIONS OF VEEAM MONITOR ....................................................................................... 28 VEEAM MONITOR LICENSING ....................................................................................................................... 29 INSTALLING VEEAM MONITOR LICENSE ....................................................................................................... 29 ADMINISTRATION .......................................................................................................................................... 31 WORKING WITH MONITORED OBJECTS ..................................................................................................... 31 Adding Objects to Be Monitored............................................................................................ 31 Changing Connection Settings ............................................................................................. 32 Removing Monitored Objects................................................................................................ 32
Page | 3
WORKING WITH PERFORMANCE TABS ...................................................................................................... 33 Using the Summary Tab ........................................................................................................ 33 Using the Overview Tab ........................................................................................................ 42 Using the Overall Tab ............................................................................................................ 43 Using the CPU Tab................................................................................................................. 44 Using the Memory Tab .......................................................................................................... 45 Using the Network Tab .......................................................................................................... 47 Using the Disk Tab ................................................................................................................ 48 Using the Swap Tab .............................................................................................................. 50 Using the Datastore Tab ....................................................................................................... 51 Using the Storage Path Tab................................................................................................... 52 Using the Storage Adapter Tab ............................................................................................. 53 Using the Virtual Disks Tab.................................................................................................... 54 Using Top Load VMs, Top Load Hosts and Lowest Load Tabs ................................................ 55 Using the Alarms Tab ............................................................................................................ 56 Using the Hardware Tab ....................................................................................................... 57 Using the VM Console Tab..................................................................................................... 58 Using the Processes Tab ........................................................................................................ 59 Using the vSphere Client Tab................................................................................................. 60 Using the Disk Space Tab ...................................................................................................... 60 Using the Disk I/O Tab ........................................................................................................... 61 Using the Disk Issues Tab ...................................................................................................... 62 CUSTOMIZING PERFORMANCE CHARTS ....................................................................................................... 63 Selecting Objects to Chart ..................................................................................................... 63 Selecting Time Interval .......................................................................................................... 64 Selecting Performance Counters ........................................................................................... 64 MANAGING ALARMS ............................................................................................................................... 65 Adding Alarms ...................................................................................................................... 66 Unassigning Alarms .............................................................................................................. 71 Excluding Objects from Alarms Scope .................................................................................. 71 Editing and Deleting Alarms ................................................................................................. 72 Finding Necessary Alarms ..................................................................................................... 72 Viewing Alarms History ......................................................................................................... 73 Modelling Alarms Number .................................................................................................... 74 VIEWING EVENTS..................................................................................................................................... 75 Viewing Events in Performance Charts .................................................................................. 76 GENERATING REPORTS ........................................................................................................................... 77 Generating HTML Reports ..................................................................................................... 77
Page | 4
Generating Trend Reports ..................................................................................................... 81 Generating Performance Overview Reports .......................................................................... 85 Working with Scheduled Report Tasks .................................................................................. 87 SPECIFYING VEEAM MONITOR SETTINGS ................................................................................................... 88 ADJUSTING VEEAM CLIENT SETTINGS ......................................................................................................... 88 ADJUSTING VEEAM MONITOR SERVER SETTINGS .......................................................................................... 93 MONITORING BUSINESS GROUPS OF VMS ................................................................................................. 98 SPECIFYING VEEAM BUSINESS VIEW SETTINGS .............................................................................................. 99 MONITORING BUSINESS GROUPS ............................................................................................................. 100 WORKING WITH CUSTOM VIEWS .............................................................................................................. 101 TROUBLESHOOTING .................................................................................................................................... 102
Page | 5
Conventions
In order to help you get the most out of this guide, we have used the following formatting conventions, terms and abbreviations in the document: Convention Emphasis Italics Description This type of formatting is used to designate user interface elements (names of dialog windows, buttons and so on). This type of formatting is used to designate names of files, file paths, cross-references and options of choice (for example, in a drop-down list). This type of formatting is used for tips, notes and important information the user should pay attention to.
Notes
Description Transparent Page Sharing VMware vCenter Server VMware Virtual Infrastructure Virtual machine
Page | 6
Phone: Fax:
+1-614-339-8200 +1-614-675-9494
Page | 7
OVERVIEW
Veeam Monitor for VMware is an enterprise-level application dedicated to monitoring and alerting of your VMware Infrastructure environment. It provides detailed statistics on and monitoring of the parameters critical to health of the virtual environment such as CPU and memory usage, disk I/O, network I/O and swap usage within each ESX(i) host per resource pool, cluster or virtual machine. Veeam Monitor for VMware features the following options and functionality:
ESX(i) Host 3.x and 4.x, Virtual Center 2.x and vCenter Server 4.x Compatibility
Veeam Monitor for VMware is fully compatible with ESX(i) host 3.x and 4.x, Virtual Center 2.x and vCenter Server 4.x.
Datastore Monitoring
Veeam Monitor for VMware adds the level of datastore to virtual infrastructure monitoring. To trace the datastore state, it uses the disk space and disk I/O metrics, and alerts on all disk issues such as bus resets and aborts of commands sent to the disk.
Page | 8
Historical Reports
Veeam Monitor for VMware allows generating graphical reports reflecting performance data for any period of time. Reports represent detailed graphs on such metrics as CPU, memory, disk I/O, network I/O, etc. for the vCenter Server, ESX(i) host, resource pool, cluster, VM, etc. Performance graphs can be defined with several levels of granularity and can be viewed across a specified time interval. Together with general HTML reports, Veeam Monitor for VMware allows generating trend reports enabling data analysis for large infrastructure environments helpful to discover trends and perform proactive capacity planning.
Alarms
With the alarms feature of Veeam Monitor for VMware, you can easily set up e-mail notifications and SNMP traps for important events such as VM power off, CPU utilization level excess and so on. Alarms modelling allows you to estimate the number of alarms to be received and adjust the alarms settings in case important information is not received or too many false positive alarms are sent. The suppressing alarms feature makes it possible to eliminate sending multiple alarms at important virtual infrastructure activities (for example, backup).
Page | 9
ARCHITECTURE
This chapter provides a high-level overview of the Veeam Monitor for VMware architecture and functionality.
Page | 10
Client-Only installation presupposes that only the client component (enabling the user to view performance data via the user interface) is installed on the computer. To provide the performance data to the user, the client communicates with the server component installed remotely.
To be able to connect to the Veeam Monitor server running remotely and use collected data, the client should be a member of the Veeam Monitoring group on the Veeam Monitor server. The Veeam Monitoring group is created automatically at the installation and is to contain all users (that is, clients) that can communicate with the remote Veeam Monitor server. To learn more about the Veeam Monitoring group configuration, see the Adjusting Veeam Monitor Server Settings section.
Page | 11
Data Displaying
The main window of Veeam Monitor for VMware is logically split into panes, each responsible for performing a specific function.
The Inventory pane displays the hierarchy of objects added for monitoring vCenter Servers, ESX(i) hosts, resource pools, virtual machines, datastores and so on. It controls the view in the information pane and on the tabs depending on the currently selected object. The Information pane represents the main "working area" used for viewing performance data and accomplishing additional actions for monitoring your virtual environment (for example, viewing ESX(i) host hardware data and managing VM guest OS processes). Tabs in the information pane are used to view different performance metrics for virtual infrastructure objects. The set of tabs, view and metrics vary depending on the selected object. For more information, see to the Working with Performance Tabs section. To display parameters and status information on virtual infrastructure objects, Veeam Monitor for VMware uses performance charts. Every graph in the performance chart visualizes a specific parameter of a virtual infrastructure object (or an object instance) or, if you select to display summary data, the resource summary information. For example, graphs in the Network chart display information on each NIC instance of an ESX(i) host or virtual machine, as well as summary network data. A performance chart displays data across a particular time period (the horizontal axis) using two scales of measurement units (vertical axes). The displayed measurement units may vary depending on selected performance counters; however, the number of units is always limited to two. Please bear in mind this restriction: you will not be able to select counters using three or more measurement units. For your convenience, Veeam Monitor for VMware provides a choice of counters and object instances and allows setting a necessary time range for displayed data. The Performance chart legend helps you read the chart, informing about objects (or object instances) and counters graphs that are currently displayed. The information provided is: key
Page | 12
color, object name (or object instance name), list of measurement counters and respective units of measurement, as well as the latest, minimum, average, and maximum performance data of the object. To facilitate monitoring of your VMware virtual infrastructure, the icon of Veeam Monitor for VMware in the system tray is displayed as the status indicator. If the virtual environment is functioning properly, the indicator color will be green. If a warning or error is triggered, the indicator color will turn to yellow and red, correspondingly. As soon as the virtual infrastructure health state returns to normal, the indicator color changes back to green. To learn about the number of warnings and errors that have occurred, move the cursor over the icon.
In full screen mode the toolbar is not displayed at all and the inventory pane is hidden on the left allowing you to concentrate on monitoring the virtual environment state and have only the most crucial information displayed. You can use the arrow button in the top left corner of the screen to toggle the inventory pane. To exit full screen mode, click the Full Screen button in the top right corner.
Page | 13
Alarms
With Veeam Monitor for VMware, you can create and configure alarms that will inform you about important events and changes in the monitored virtual environment. Ability to be alerted of events allows for faster administrator response to critical issues, helping to maintain the overall health of the virtual infrastructure. Alarms can be applied to a single object within the virtual environment ESX(i) host, virtual machine, datastore, VM container, and to a group of objects for example, all virtual machines running on the same ESX(i) host or even in the whole virtual environment. Veeam Monitor for VMware offers an extended set of rules and different severity levels, allowing you to create a custom alarm scheme complying with specific requirements of your virtual environment.
Alarm Rules
According to the object selected for alerting, alarms are divided into several types. For each type, there is its own set of alarm rules conditions under which alarms are triggered. Veeam Monitor for VMware offers the next rules for different types of alarms.
vCenter Server
Certain event is received by vCenter Server. An alarm will be triggered if some event occurs on vCenter Server level. Power or connection state changes. An alarm will be triggered if the state of vCenter Server is equal or not equal to the specified condition (for example, if the vCenter Server is not responding).
Cluster
Certain event is received by vCenter Server. An alarm will be triggered if some event occurs on cluster level.
Host
Certain event is received by vCenter Server. An alarm will be triggered if some event occurs on host level. Power or connection state changes. An alarm will be triggered if the state of the host is equal or not equal to the specified condition (for example, if the ESX(i) host is not responding). Resource usage is out of allowed range. An alarm will be triggered if the specified counter is above or below the specified value (for example, if the CPU usage exceeds 75%). Number of VMs is out of allowed range. An alarm will be triggered if the number of VMs within the ESX(i) host exceeds the specified 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. Hardware sensor state changes. An alarm will be trigged if the sensor state is or is not in a specific state (Normal, Warning, Alert).
Virtual Machine
Certain event is received by vCenter Server. An alarm will be triggered if some event occurs on VM level (for example, if the MAC address of the VM conflicts with the MAC address of another VM existing in the virtual infrastructure). Power or connection state changes. An alarm will be triggered if the state of the VM is
Page | 14
equal or not equal to the specified condition (for example, if the VM is suspended). Resource usage is out of allowed range. An alarm will be triggered if the specified counter is above or below the specified value (for example, if the CPU ready level exceeds 5%). Heartbeat is missing. An alarm will be triggered if a monitored virtual machine is not available or overloaded for a specific period of time (for example, is missing for 5 minutes). Guest volumes are running out of free disk space. An alarm will be triggered if available disk space on guest volumes is below the specified value. You can select 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). Snapshot size for VM is out of allowed range. An alarm will be triggered if the size of the VM snapshot is above or below the specified value. You can select 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).
Datastore
Certain event is received by vCenter Server. An alarm will be triggered if some event occurs on datastore level. Datastore is running out of free space. An alarm will be triggered if the datastore free space is above or below the specified value. You can select to specify the amount of due free space 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 I/O load is out of allowed range. An alarm will be triggered if the datastore I/O counter thresholds are violated. Datastore experiences issues. An alarm will be triggered if the number of bus resets or command aborts for the datastore is above or below the specified value. Datastore over-provisioning. An alarm will be triggered if the difference between the provisioned disk space and the datastore capacity is above the specified value. You can select to specify the difference as an absolute value (for example, if the provisioned disk space should not exceed datastore capacity by more than 100 GB) or a relative value (for example, if the provisioned disk space should not exceed 400% compared to the datastore capacity).
Any Object
Certain event is received by vCenter Server. An alarm will be triggered if some event occurs on any object.
Page | 15
Alarm Severity
When alarms are configured, every rule is associated with one of alarm severity levels. The severity level defines the alarm criticality and its impact on the virtual infrastructure health. Veeam Monitor for VMware offers the following severity levels: Information, Warning, Error and Resolved. Different severity levels may be defined for conditions of different intensity. For example, if the level of memory usage should not exceed 75%, the following rules may be created: If the memory usage is 70% to 75%, an alarm with the Warning severity level will be triggered. If the memory usage is over 75%, an alarm with the Error severity level will be triggered. That is, if the memory usage level is constantly growing and exceeds 70%, a warning alarm will be triggered, notifying about a potentially dangerous situation. If the memory usage level keeps on growing and exceeds the level of 75%, an error alarm notifying about severe danger will be triggered.
Page | 16
Events
Along with parameters and statistics data on the virtual infrastructure objects, Veeam Monitor for VMware displays information about events that occur within your virtual environment for the monitored period. Thereto, Veeam Monitor for VMware works with vCenter/ESX(i) tasks: it loads all tasks from the ESX(i) host or vCenter Server and creates two events for each task one informing about the task start and the other informing about task end. The list of events is displayed on the Events tab of Veeam Monitor for VMware. For every event, detailed information is provided: its type, description, time of occurrence, target and so on. Events are displayed as a list of alerts but can also be viewed in the performance charts. Viewing events on the performance charts can be helpful if there is a necessity to learn the reasons for changes in the performance behavior. To learn more, see the Viewing Events in Performance Charts section.
Reports
Besides monitoring the virtual environment on the on-going basis, Veeam Monitor for VMware enables you to generate custom graphic reports containing information on the virtual environment performance. With the help of reports, you can check the status of your resources at any point of time, analyze and plan the growth of your virtual environment, as well as use reports for documenting purposes. Veeam Monitor for VMware allows generating three types of reports: graphic reports in the HTML format, trend and overview reports in the Microsoft Excel format. HTML reports mirror the custom monitoring view for a selected virtual infrastructure object across a specific period of time and are intended for analyzing real-time data. HTML reports contain a set of graphs describing virtual infrastructure object parameters and metrics from the selected standpoints: CPU, memory, network and so on. Microsoft Excel trend reports provide the user with a possibility to analyze general dynamics of changes in the virtual environment. In contrast to HTML reports, primarily generated for limited time intervals, trend reports may be created for significant periods of time for example, a year, or even contain all data ever collected. Trend reports are important for large virtual environments as they help trace and analyze the tendencies of the virtual environment growth and plan upgrades or migrations taking into consideration collected data. Overview report is a standard report with predefined data for analyzing and comparing resource usage, state and utilization of clusters and datastores within the VI. It provides a brief overview of the whole virtual environment with data which is crucial for administrators. Trend, HTML and overview reports can be generated on demand or scheduled to be generated automatically with some periodicity.
Page | 17
Page | 18
Prerequisites
Veeam Monitor for VMware uses firewall ports listed in the table below. Make sure these ports are opened: Purpose Used to collect data from ESX(i) host and vCenter Server Used by Veeam Monitor Client to communicate with Veeam Monitor Server Protocol SSL TCP UPD Port Number 443* 139**; 445**; 1039* 137**; 1434*
* These ports should be opened manually. ** Associated with the File and Printer Sharing service.
Requirements
The present chapter describes the list of system requirements to the VMware Infrastructure, Veeam Monitor console, as well as necessary rights and permissions necessary to work with Veeam Monitor for VMware.
System Requirements
To ensure successful usage of Veeam Monitor for VMware, the following system requirements should be met: Virtual Infrastructure VMware Infrastructure ESX(i) host 3.x or 4.x Virtual Center 2.x or vCenter Server 4.x (optional) Veeam Monitor Console SQL Database MS SQL Server 2005 Express, MS SQL Server 2005 or MS SQL Server 2008, MS SQL Server 2008 R2. If you do not have one, the Veeam Monitor Server setup will install Microsoft SQL Server 2005 Express Edition.
Page | 19
OS
32-bit and 64-bit versions of the following operating systems: Windows XP Windows Server 2003 Windows Server 2003 R2 Windows Vista Windows Server 2008 Windows Server 2008 R2 Windows 7 All the latest service packs and security updates should be
Hardware
Software
installed. Processor: Pentium III CPU or higher preferred Memory: 512MB RAM (1024MB or higher preferred) Free hard disk space: 20 MB (Client Only); 50 MB (Full installation); additional 260 MB for Microsoft SQL Server Express installation if applicable. Resolution: 1280x1024 or higher preferred Network adapter: 100 Mbit/sec or higher preferred All above hardware requirements depend on your virtual infrastructure. Microsoft .NET Framework 2.0 or higher installed Microsoft Installer 3.1 MS Excel 2007 or higher should be installed to enable trend and overview reports viewing
Note:
If the SQL database is installed remotely, with the SQL Server and Veeam Monitor for VMware residing in the same workgroup, SQL Server authentication will be required.
Required Permissions
To install Veeam Monitor for VMware, the user must have administrator privileges on the SQL Server. The Veeam Monitor service must be able to read from and write to the VeeamMonitor database. Make sure that the service has the following permissions on the database: dbreader and dbwriter. The account used for collecting data from vCenter Server/ESX(i) host requires the following permissions: Readonly, Datastore.Browse, VirtualMachine.Interact.AnswerQuestion. The latter two are necessary for using the VM Console and viewing snapshot information. The Named Pipes protocol on SQL must be enabled.
Page | 20
DEPLOYMENT
Before you begin, take the following steps to prepare for deployment: Check the system requirements. Make sure the computers on which Veeam Monitor for VMware will be installed meet the system requirements. Check required permissions. Make sure Microsoft .NET Framework version 2.0 or higher is installed on the computer on which Veeam Monitor for VMware will be deployed.
Full Installation
This section will guide you through the installation process of the full version of Veeam Monitor for VMware.
Page | 21
Page | 22
Page | 23
Note:
If the SQL database is installed remotely and the SQL Server resides in the same workgroup with Veeam Monitor for VMware, SQL Server authentication will be required.
Page | 24
Client-Only Installation
This section will guide you through the installation process of the client-only version of Veeam Monitor for VMware.
Page | 25
Page | 26
Important!
It is recommended to leave this check box blank to keep the existing database in case you will need to recover it in the future (unless you already made a backup of the database). 6. Follow the wizard from Step 5.
Page | 27
Alarm details are limited to Summary (Cause, Resolution and External info is hidden) Snapshot size and Disk space size alarms are disabled and cannot be enabled User can use the Alarm settings wizard (to evaluate capabilities) but cannot save any alarms Stacked VM I/O monitoring masked (Free version is displayed instead of actual VM name) Data in the Overview tab is visible but object names are substituted by Free version Process names are substituted by Free version Not available
Predefined alarms
Custom alarms
Storage monitoring
Fully functional
Overview
Processes
User can view and manage processes running on a vCenter Server, ESX(i) host or VM Full health check functionality using the alarm modelling feature All reports are fully functional
Alarm modelling
Management reports
Scheduled reports
Overview reports are generated with all the available data, but object names are substituted by Free version Scheduled reports are not available
Page | 28
Page | 29
To install a license after installation: Once Veeam Monitor for VMware is installed, open the Veeam Monitor Server Settings window: either select Programs > Veeam > Veeam Monitor Sever Settings from the Start menu or start Veeam Monitor for VMware, click the Options button and select the Server Settings... command. On the License tab, click the Browse button to select a license file. After the license is installed, the Veeam Data Collector service will be restarted.
Page | 30
ADMINISTRATION
Working with Monitored Objects
This section describes the first steps you should take to start working with Veeam Monitor for VMware: adding ESX(i) hosts and vCenter Servers, changing connection settings for the added objects, as well as removing monitored objects.
Important!
The user name for a vCenter Server should be specified in the DOMAIN\USERNAME format.
Page | 31
Besides removing ESX(i) hosts and vCenter Servers, you can remove VMs that have been deleted on the ESX(i) host from the monitoring console. When a VM is deleted on the host, it still remains in the hierarchy of virtual infrastructure objects in Veeam Monitor for VMware. To remove VMs that have been deleted and update the inventory view to its current state: Right-click a necessary virtual infrastructure level in the inventory panel and select Remove All Deleted VMs from the shortcut menu. As a result, all deleted VMs child to this virtual infrastructure object will be removed from the tree. Important! Please keep in mind that when you delete a vCenter Server, ESX(i) host or remove a deleted VM from the monitoring console, all collected statistical data for this virtual infrastructure object is lost.
Page | 32
Virtual Infrastructure
Resources: CPU Usage graphical representation of total level of CPU usage for the virtual infrastructure (in %) Memory Usage graphical representation of total memory usage for the virtual infrastructure (in %) Storage Usage graphical representation of total storage usage for the virtual infrastructure (in %)Overview: vCenter Servers total number of vCenter Servers in the virtual infrastructure
Page | 33
Datacenters total number of datacenters in the virtual infrastructure Clusters total number of clusters in the virtual infrastructure Hosts total number of hosts in the virtual infrastructure Virtual Machines total number of virtual machines in the virtual infrastructure Datastores total number of datastores in the virtual infrastructure Performance data period period of time for which performance data is presented Events count number of events that have occurred in the virtual infrastructure Past hour alarms: Errors number of error alarms triggered during the past hour Warnings number of warning alarms triggered during the past hour Last 5 alarms the last 5 alarms, including name and source of each alarm
vCenter Server
Top 5 clusters: CPU Usage graphical representation of level of CPU usage for the top five clusters (in Ghz) Memory Usage graphical representation of total memory usage for the top five clusers (in GB) Datastore Usage graphical representation of total datastore usage for the top five clusters (in TB) Overview Name vCenter Server name Datacenters total number of datacenters in vCenter Server Clusters total number of clusters in vCenter Server Hosts total number of hosts in vCenter Server Virtual Machines total number of virtual machines in vCenter Server
Page | 34
Datastores total number of datastores in vCenter Server Events count number of events that have occurred to the vCenter Server Performance data period period of time for which performance data is presented Past hour alarms: Errors number of error alarms triggered during the past hour Warnings number of warning alarms triggered during the past hour Last 5 alarms the last 5 alarms, including name and source of each alarm
Datacenter
Top 5 clusters: CPU Usage graphical representation of level of CPU usage for the top five clusters (in Ghz) Memory Usage graphical representation of total memory usage for the top five clusers (in GB) Datastore Usage graphical representation of total datastore usage for the top five clusters (in TB) Overview: Clusters total number of clusters in the datacenter Hosts total number of hosts in the datacenter Virtual Machines total number of virtual machines in the datacenter Datastores total number of datastores in the datacenter Events count number of events that have occurred in the datacenter Performance data period period of time for which performance data is presented Past hour alarms: Errors number of error alarms triggered during the past hour Warnings number of warning alarms triggered during the past hour
Page | 35
Last 5 alarms the last 5 alarms, including name and source of each alarm
Cluster
Top 5 hosts: CPU Usage graphical representation of level of CPU usage for the top five ESX(i) hosts (in Ghz) Memory Usage graphical representation of memory usage for the top five ESX(i) hosts (in GB) Datastore Usage graphical representation of datastore usage for the top five ESX(i) hosts (in TB) Overview: Hosts total number of hosts in the cluster Virtual Machines total number of virtual machines in the cluster VMware HA VMware HA state (Enabled/Disabled) VMware DRS VMware DRS state (Enabled/Disabled) Total CPU Resources total amount of CPU resources assigned to the cluster Total Memory total amount of memory assigned to the cluster Number of Hosts number of hosts in the cluster Total Processors number of processors in all hosts in the cluster Events count number of events that have occurred for the cluster Performance data period period of time for which performance data is presented Past hour alarms: Errors number of error alarms triggered during the past hour Warnings number of warning alarms triggered during the past hour Last 5 alarms the last 5 alarms, including name and source of each alarm
Page | 36
ESX(i) host
Resources: CPU Usage graphical representation of level of CPU usage for the server (in %) Memory Usage graphical representation of total memory usage for the server (in %) Storage Usage graphical representation of total storage usage for the server (in %) Overview: Manufacturer ESX(i) host manufacturer Model ESX(i) host model Version ESX(i) version Sockets count number of sockets for ESX(i) host Processors number and speed of ESX(i) host processors Processor Type manufacturer and type of processors Memory total amount of memory Number of NICs number of NICs installed on the host Number of HBAs number of HBAs on the host State ESX(i) host state Maintenance Mode defines if the maintenance mode is enabled or disabled for the host (Yes/No) vMotion Enabled defines if vMotion is enabled or disabled for the host (Yes/No) CPU Usage total level of CPU usage for this host (in Mhz) Memory Usage total memory usage for this host (in MB) Uptime period of time for which the server has been up and running Events count number of events that have occurred for the host
Page | 37
Performance data period period of time for which performance data is presented Past hour alarms: Errors number of error alarms triggered during the past hour Warnings number of warning alarms triggered during the past hour Last 5 alarms the last 5 alarms, including name and source of each alarm
Resource Pool
Resources: CPU Usage graphical representation of level of total CPU usage for the resource pool (in %) Memory Usage graphical representation of total memory usage for the resource pool (in %) VM power state graphical representation of total numbers of powered on, powered off, and suspended virtual machines Overview: CPU Shares relative metric for allocating CPU capacity with regard to the parent's total CPU Reservation guaranteed CPU allocation for the object CPU Type type of reserved CPU allocation (Expandable/Fixed) CPU Limit upper limit of CPU allocation for this resource pool CPU Unreserved amount of CPU resources that have not been reserved CPU Usage number of megahertz currently used by virtual machines in this resource pool Memory Shares relative metric for allocating memory capacity with regard to the parent's total Memory Reservation guaranteed memory allocation for the object
Page | 38
Memory Type type of reserved memory allocation (Expandable/Fixed) Memory Limit upper limit of memory allocation for this resource pool Memory Unreserved amount of memory resources that has not been reserved Memory Usage number of megabytes currently used by virtual machines in this resource pool Events count number of events that have occurred for the resource pool Performance data period period of time for which performance data is presented Past hour alarms: Errors number of error alarms triggered for the resource pool during the past hour Warnings number of warning alarms triggered for the resource pool during the past hour Last 5 alarms the last 5 alarms, triggered for the resource pool, including name and source of each alarm
vApp
Resources: CPU Usage graphical representation of level of total CPU usage for the virtual application (in %) Memory Usage graphical representation of total memory usage for the virtual application (in %) VM power state a table showing which VMs are powered on, powered off or suspended Overview: Product virtual application product Version version of the virtual application Vendor virtual application vendor Status virtual application state CPU Usage number of megahertz currently used by VMs in this virtual application
Page | 39
Memory Usage number of megabytes currently used by VMs in this virtual application Performance data period period of time for which performance data is presented Past hour alarms: Errors number of error alarms triggered for the virtual application during the past hour Warnings number of warning alarms triggered for the virtual application during the past hour Last 5 alarms the last 5 alarms, triggered for the virtual application, including name and source of each alarm
Virtual Machine
Resources: CPU Usage graphical representation of level of CPU usage for the VM (in %) Memory Usage graphical representation of total memory usage for the VM (in %) Storage Usage graphical representation of total storage usage for the VM (in %) Overview: Guest OS operating system installed on the virtual machine CPU number of processors on the virtual machine Memory amount of memory allocated to this virtual machine VMware Tools state of VMware tools installed on the virtual machine (Installed/Not Installed/Running/Not Running) IP Address IP address of the virtual machine DNS Name DNS name of the virtual machine State power state of the virtual machine Host name of the host on which the virtual machine is running Notes additional notes specified for the virtual machine
Page | 40
Uptime period of time for which the virtual machine has been up and running Events count number of events that have occurred for the virtual machine Performance data period period of time for which performance data is presented Top 5 guest disks Graphical representation of disk space usage for the top five guest disks (in GB)
Datastore
Provisioning Graphical representation of storage space usage (capacity, provisioned, free) (in GB) Latest disk latency Graphical representation of average disk read and write latency for the latest hour (Past Hour) and latest 5 minutes (Current Value) (in ms) Overview: Type datastore type (NFS/VMFS) Location datastore location Virtual Machines and Templates total number of VMs residing on the datastore Number of Hosts total number of ESX(i) hosts using the datastore Total Capacity total amount of the datastore capacity Free Space amount of free space on the datastore Events count number of events that have occurred on the datastore Performance data period period of time for which performance data is presented Past hour alarms: Errors number of error alarms triggered for the datastore during the past hour Warnings number of warning alarms triggered for the datastore during the past hour Last 5 alarms the last 5 alarms, triggered for the datastore, including name and source of each alarm
Page | 41
The tab is divided into four subtabs (you can switch between them at the bottom of the Overview tab). Summary contains graphical representations for comparing statistics on Cluster Resource Usage (CPU, Memory and Storage) and Health State (Error count, Warning count and Info count). At the bottom, there is also a graph, which allows you to compare average resource utilization levels for all clusters. Storage contains graphs for viewing and comparing the most critical data collected for datastores: Top 5 Over-Provisioned LUNs, Top 5 LUNs Read/Write Speed, Top 5 LUNs Problems and Top 10 Storage Consuming VMs. CPU contains graphs for viewing and comparing cluster statistics concerning CPU usage: CPU (total CPU resources compared to average consumed in each cluster), Peak CPU Usage (total CPU resources compared to peak CPU usage in each cluster) and Top VMs (top 10 VMs which consume the most CPU resources). Memory contains graphs for viewing and comparing cluster statistics concerning memory usage: Memory Allocation (total physical and allocated virtual memory compared to average consumed in each cluster), Peak Memory Usage (total physical memory compared to peak memory usage in each cluster) and Top VMs (top 10 VMs which consume the most memory resources).
Page | 42
Page | 43
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Average CPU System Average CPU Wait Percent Percent CPU time spent in VMkernel (available for Resources and VMs) CPU time spent waiting for hardware or VMkernel lock thread locks (available for Resources and VMs) Resources and VMs: CPU time that the VM was ready but could not get scheduled to run on physical CPU. ESX(i): Average CPU Ready value for all VMs on the host. Percentage of total CPU resources which is actively used Amount of CPU resources actively used Amount of a VMs CPU resources used beyond its reserved amount (available for Resources and VMs) Description
Percent
Page | 44
See the table below to learn more about counters that can be used to display data: Counter Unit of Measurement Memory Consumed (GB/MB/KB/s) VM: Amount of host memory consumed by the VM for guest memory. ESX(i): Amount of machine memory used on host. VM: Amount of host memory reclaimed from the VM through ballooning. ESX(i): Sum of all balloon values for powered-on VMs and the vSphere services on the host. VM: Amount of host memory shared with other VMs. ESX(i): Sum of all shared memory values for powered-on VMs and the vSphere services on the host. VM: Amount of machine memory used by the VMkernel to run the VM. ESX(i): Sum of all overhead memory values for powered-on VMs and the overhead of running vSphere services on the host. Description
Memory Balloon
(GB/MB/KB/s)
Memory Shared
(GB/MB/KB/s)
Memory Overhead
(GB/MB/KB/s)
Page | 45
Counter
Unit of Measurement
Description
Memory Active
(GB/MB/KB/s)
Memory Usage
Percentage
(GB/MB/KB/s) (GB/MB/KB/s)
Percent
(GB/MB/KB/s)
VM: Amount of host memory that is actively used (as estimated by VMkernel, based on recently touched memory pages). ESX(i): Sum of all active memory values for powered-on VMs and the vSphere services on the host. VM: Memory usage as a percentage of total allocated VM memory. ESX(i): Memory usage as a percentage of total available host memory. Amount of memory pages compressed by ESX(i) instead of swapping on disk Amount of memory saved due to memory zipping (available for Resources and VMs) Potential memory demand based on total allocated memory for powered-on VMs, memory overhead, effects of TPS and total available memory (available for ESX(i) hosts, datacenters and vCenter Servers) Amount of host memory shared by powered-on VMs and vSphere services on the host. Subtract the value from Memory Shared metric to evaluate how much host memory is saved due to sharing (available for ESX(i) hosts, datacenters and vCenter Servers).
Page | 46
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Network Receive Rate KB/s VM: Rate at which data is received via the VMs vNIC. ESX(i): Rate at which data is received via each physical NIC instance on the host. VM: Rate at which data is transmitted via the VMs vNIC. ESX(i): Rate at which data is transmitted via each physical NIC instance on the host. VM: Average number of packets received per second by each vNIC on the VM. ESX(i): Average number of packets received per second via each physical NIC instance on the host. VM: Average number of packets transmitted per second by each vNIC on the VM. ESX(i): Average number of packets transmitted per second via each physical NIC instance on the host. Description
KB/s
Numbers
Numbers
Page | 47
Counter
Unit of Measurement
Description
Network Usage
KB/s
VM: Sum of data received and transmitted via all vNIC instances on the VM. ESX(i): Sum of data received and transmitted via all physical NIC instances connected to the host.
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Disk Read Rate MB/s VM: Rate at which data is read from each virtual disk on the VM. ESX(i): Rate at which data is read from each LUN on the host. VM: Rate at which data is written to each virtual disk on the VM. ESX(i): Rate at which data is written to each LUN on the host. VM: Average number of write operations to the virtual disk of the VM per second. ESX(i): Average number of write operations to each LUN on the host per second. Description
MB/s
Number
Page | 48
Counter
Unit of Measurement
Description
Number
Disk Usage
MB/s
Millisecond
Millisecond
VM: Average number of read operations from the virtual disk of the VM per second. ESX(i): Average number of read operations from each LUN on the host per second. VM: Aggregated disk I/O rate for a VM. ESX(i): Sum of aggregated disk I/O rates for all VMs on the host. Number of SCSI bus reset commands issued Number of SCSI commands aborted VM: Average number of read and write operations for each virtual disk of the VM per second ESX(i): Average number of read and write operations for each LUN on the host per second Average amount of time taken to process a SCSI read command issued from the Guest OS to the VM Average amount of time taken to process a SCSI write command issued by the Guest OS to the VM
Page | 49
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Memory Swapped KB Current amount of guest physical memory swapped out to the VMs swap file by VMkernel (available for Resources and VMs) Sum of memory used by swap of all powered-on VMs and vSphere services on the host (available for hosts and clusters) Description
KB
Page | 50
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Datastore I/O Datastore Read I/O Datastore Write I/O Datastore Read Rate Datastore Write Rate Datastore Read Latency Datastore Write Latency Number Number Number KB/s KB/s Millisecond Millisecond Average number of read and write operations for a datastore per second Average number of read operations from a datastore per second Average number of write operations to a datastore per second Rate at which data is read from each datastore Rate at which data is written to each datastore Average amount of time taken to process a read command issued to the datastore Average amount of time taken to process a write command issued to the datastore Description
Page | 51
The name of each storage device connected to the storage adapter via the selected path is specified after the ESX(i) host address (separated by a forward slash) in the Object column of the chart legend. It is displayed in the following format: <HBA>:<SCSI target>:<SCSI LUN>:<disk partition> You can select an appropriate counter for each selected path using the middle drop-down list below the performance chart. To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Path I/O Path Read I/O Path Write I/O Path Read Rate Path Write Rate Path Read Latency Path Write Latency Number Number Number KBps KBps Millisecond Millisecond Average number of commands issued per second via the selected path Average number of read commands issued per second via the selected path Average number of write commands issued per second via the selected path Rate of reading data from the storage device via the selected path Rate of writing data to the storage device via the selected path Average amount of time taken to read data from the storage device via the selected path Average amount of time taken to write data to the storage device via the selected path Description
Page | 52
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Adapter I/O Adapter Read I/O Number Number Number Average number of commands issued per second to the storage device by the adapter Average number of read commands issued per second to the storage device by the adapter Average number of write commands issued per second to the storage device by the adapter Rate of reading data from the storage device Rate of writing data to the storage device Average amount of time taken to read data from the storage device Average amount of time taken to write data to the storage device Description
Adapter Read Rate Adapter Write Rate Adapter Read Latency Adapter Write Latency
Page | 53
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Read I/O Write I/O Read Rate Write Rate Read Latency Write Latency Number Number KBps KBps Millisecond Millisecond Average number of read commands issued per second to the virtual disk Average number of write commands issued per second to the virtual disk Rate of reading data from a virtual disk Rate of writing data to a virtual disk Average amount of time taken to read data from a virtual disk Average amount of time taken to write data to a virtual disk Description
Page | 54
Using Top Load VMs, Top Load Hosts and Lowest Load Tabs
Depending on the level of virtual infrastructure object currently selected in the inventory panel, Veeam Monitor for VMware allows you to define VMs or hosts consuming the most or the least resources at the moment. The Top Load Hosts tab displays the top host consumers of CPU, memory, disk, network, and swap. It provides statistics for a selected number of hosts taking most of the resources over the last N minutes. The Top Load VMs tab displays the top VM consumers of CPU, memory, disk, network, swap and top snapshot users. It provides statistics for a selected number of VMs taking most of the resources over the last N minutes. Similarly to the Top Load Hosts tab, the Lowest Load tab allows you to identify the least loaded ESX(i) hosts, taking into consideration consumed resources of CPU, memory, disk, network, and swap. This helps you to decide to which ESX(i) hosts you can place new VMs or move existing ones.
To define the number of top and lowest consumers and the time interval, click the Change Options... link at the lower right corner of the window.
Page | 55
In Triggered view you can use the Resolve button to manually resolve selected alarms and the Clear button to remove unnecessary triggered alarms from the list.
To add, delete or edit alarms, use the Alarms Management view (see Managing Alarms).
Page | 56
Page | 57
Page | 58
Every process is described with a set of counters that are presented as column headings. You can add or remove counters to monitor running processes: click the Select columns... link at the upper right corner of the Processes view. Then, in the Select columns window, select check boxes next to counters you want to display. To view a detailed description of a counter, click it in the Counters list, and a description will be displayed in the lower pane of the window. Using the Processes tab, you can end unwanted processes running on the VM or restart running service. Note: This option is available only for VMs on which VMware Tools are installed. To end a process, select it in the list and click the Kill process button or right-click a necessary process and select Kill process from the shortcut menu. To restart a service, click the Restart service button or right-click a necessary service and select Restart service from the shortcut menu.
Page | 59
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Datastore Free Space Datastore Provisioned Space Datastore Capacity MB Configured size of the datastore MB MB Amount of free space on the datastore Amount of storage allocated for use by a datastore or VM Description
Page | 60
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Disk Read Rate MB/s Amount of data read by all instances of VMs residing on the datastore in the defined interval Amount of data written to disk by all instances of VMs residing on the datastore in the defined interval Number of times data was written to the disk by all instances of VMs residing on the datastore in the defined interval Sum of disk commands to the datastore issued in the collection interval Description
MB/s
Number
Disk I/O
Number
Page | 61
Number
Number of times data was read from the disk by all instances of VMs residing on the datastore in the defined interval Average amount of time taken to read data from the disk from the perspective of an ESX(i) host Average amount of time taken to write data to the disk from the perspective of an ESX(i) host
Millisecond
Millisecond
To learn more about counters that can be used to display data, see the table below. Counter Unit of Measurement Disk Bus Resets Disk Command Aborts Number Number Number of SCSI bus reset commands issued Number of SCSI commands aborted in the defined interval Description
Page | 62
Once you have selected a corresponding option, click OK the chart and the chart legend will change respectively. Note: The legend pane displays only those objects for which data across the selected time interval is available.
Page | 63
3. 4. Tip:
In the left pane of the window, select available resource device(s) and/or the total of resources to be displayed on the chart. In the right pane of the window, select counter(s) to view.
When you select a counter, its description appears in the lower pane of the window.
Page | 64
Managing Alarms
Veeam Monitor for VMware comes with a set of predefined alarms, which makes it an out-ofthe box solution and allows for its fast deployment. Predefined alarms cover major levels of virtual infrastructure: vCenter Servers, clusters, ESX(i) hosts (hardware, connection state, CPU and memory usage), virtual machines (CPU ready time, CPU and memory usage), datastores and any objects. Depending on requirements to the virtual environment, you can adjust settings of predefined alarms, and create new alarms that will analyze performance and alert on errors at any level of virtual infrastructure. To see a list of alarms predefined for a specific level of the virtual infrastructure, to adjust alarm settings and create new alarms, click the Alarm Management button at the bottom of the inventory panel and select the necessary object from the tree:
The Alarm management view of Veeam Monitor for VMware is divided into two panes. The upper pane contains the list of predefined and custom alarms for the level, selected in the tree on the left. Every alarm is described with the following data: type, name, source, and state (Enabled or Disabled). The lower pane displays different data, depending on the button selected: Knowledge provides general information on the selected alarm, such as summary, cause, resolution and external sources of data Assignment shows the list of objects which this particular alarm is assigned to
Page | 65
Adding Alarms
To add a new alarm, complete the steps described below.
If you add an alarm for a virtual infrastructure object that has child objects, the alarm can be propagated to monitor all its child objects.
Note:
Make sure that the Enable this alarm check box is selected. If it is not, the alarm data will be saved, but the alarm will be disabled until you select this check box.
Page | 66
2.
3. Note:
After you have added a rule, make sure the Enabled check box is selected for all rules that should be used by the created alarm.
Page | 67
Note:
Be careful when specifying tolerance for alarms with more than one rule: if such alarm is triggered by one rule, it will not be triggered by this or ANY OTHER rule unless the metric exceeds or falls below the specified tolerance range. For example, an alarm has two rules: it is triggered when memory usage exceeds 60% and CPU usage exceeds 1500 MHz. If the tolerance level for this alarm is set to 10% then after being triggered by excess memory usage, the alarm will not repeat unless memory usage exceeds 66%. This way the user will not receive unnecessary repeats of the same alarm while memory usage stays in the safe range. However, since the alarm was already triggered by excess memory usage, CPU usage will also not trigger the alarm while it stays in the tolerance range and you may miss out on a potentially dangerous situation if CPU usage exceeds the 1500 MHz threshold but stays below 1650 MHz. 3. In the Frequency section, specify the interval of time after which the repeated alarm should be sent if the alarm condition is not eliminated.
Page | 68
Page | 69
Note.
To view details in the Alarm Management view, make sure that the Knowledge button is selected.
Page | 70
Note:
You can assign multiple alarms at the same time. To assign one or more alarms: 1. 2. 3. Select alarm(s) on the list and click the Assign button. To select multiple alarms, use the Ctrl and Shift keys. In the displayed window, browse for the target object in the infrastructure tree. In order to apply the same alarm to the objects child nodes, make sure that the Propagate alarms on child nodes check box is selected. The alarm will work for the child nodes that correspond to the alarms type. Click the Assign button. The object will appear in the assignment information in the lower pane.
4.
Unassigning Alarms
Alarm assigned to an object can be unassigned from it, which means that the object will no longer be monitored by this alarm. Note: An alarm cannot be unassigned from objects, to which it has not been assigned. For example, if an alarm was assigned to an object and propagated to its child nodes, you cannot unassign the alarm from any of the child nodes. Use the Exclude feature instead (see next section). To unassign an alarm from an object: Select the alarm in the upper pane of the Alarms Management view. In the lower pane, click the Assignment button. The objects to which this alarm is assigned will be listed in the lower pane. 3. Select the object, from which to unassign the alarm, in the lower pane and click the Unassign button, or right-click the object and choose Unassign from the context menu. Alternatively, you can unassign an alarm from the Alarms tab of the Infrastructure View: 1. 2. 3. Select the object from which to unassign the alarm in the inventory panel. In the Infrastructure View, open the Alarms tab. Right-click the alarm to unassign and choose Unassign alarm from the context menu. 1. 2.
2.
Page | 71
Page | 72
To resolve an alarm, select it in the Triggered Alarms list and click the Resolve button or right-click a necessary alarm and select Resolve in the shortcut menu. To remove an alarm, right-click it in the list and select Delete. To clear the Triggered Alarms list, click the Clear button and select which alarms you wish to delete: Resolved, Later than 1 day, Later than 1 week, Later than 1 month or All.
Page | 73
Veeam Monitor for VMware will display the number of alarms of different severity that will be sent within the selected period of time.
Page | 74
Viewing Events
The Events view of Veeam Monitor for VMware displays data on events that occurred at different levels of virtual environment. To view the list of events for a specific level, select it in the inventory panel and click the Events tab:
For every event, the following information is provided: event type (User, Info, Warning or Error), short description, time of occurrence, event target and the object that initiated the event. To view a detailed description of an event, click it in the list, and the event data will be displayed in the Event Details pane of the Events view. By default, the Events view contains data on the past hour. To change the time range for displayed event, select a necessary time interval in the Events from list. Besides viewing events for a specific virtual infrastructure object, you can also display events for all objects child to it: select the Include events from child objects check box at the bottom of the Event Details section.
Page | 75
To display recent events in the performance graph, select the Display known events check box below the performance chart.
Events are presented as vertical lines crossing the performance graphs. To learn more about an event, move the mouse cursor over it to see a tooltip, or click the corresponding line in the graph. As a result, the Event description window will be displayed.
Page | 76
Veeam Monitor for VMware regards the following types of events: live migration, snapshot creation events, snapshot removal events and Veeam Backup events. To select what type of events you want to display in the performance chart, click the Advanced... link next to the Display known events check box and select the events you need to view.
Note:
The Display known events option is available only for time intervals not greater than 3 days. You will not be able to view events in the performance graph if a longer time interval is selected.
Generating Reports
Veeam Monitor for VMware allows generating three types of reports containing virtual environment data: HTML reports containing real-time and past performance data for the specified time interval Trend reports intended for tracing the dynamics of retrieved data and generated for longer time intervals and large virtual environments Overview report for comparing resource usage, state, utilization and other performance data for clusters within the virtual infrastructure.
Page | 77
Page | 78
If you want to receive the created report by e-mail, select the E-mail report to the following addresses check box. Enter an e-mail address in the field below. To enter multiple addresses, use semicolon. Please note you should configure e-mail settings to be able to receive e-mails. To learn more, see the Mail Settings section. If you want to save the created report, select the Save report to the following folder or share check box and choose destination. Besides scheduling and saving the report, you can select to execute a script when the report is uploaded. Click the Advanced... button and in the displayed window select the Run the following script when report is uploaded check box. Use the Browse button to select an executable file. You can use two variables in the script: %reportname% full path to the report file and %reportfolder% full path to the report image subfolder.
Page | 79
Click Finish. Depending on your choice, Veeam Monitor for VMware will generate the report or schedule its generation and finish the work with the report wizard. Important! Generation of reports, execution of scripts and sending of e-mails is accomplished on the machine where the Veeam Monitor Server is installed.
Page | 80
Page | 81
Page | 82
If you want to receive the created report by e-mail, select the E-mail report to the following address check box and enter corresponding e-mail addresses in the field below. To enter multiple addresses, use semicolon. Please note that e-mail settings should be configured be able to receive e-mails. To learn more, see the Mail Settings section. If you want to save the created report, select the Save report to the following folder or share check box and choose destination. Beside scheduling and saving the report, you can select to execute a script when the report is uploaded. Click the Advanced... button and in the displayed window, select the Run the following script when report is uploaded check box. Use the Browse button to select an executable file. You can use two variables in the script: %reportname% full path to the report file and %reportfolder% full path to the report image subfolder.
Page | 83
Click Generate. Depending on your choice, Veeam Monitor for VMware will generate the report or schedule its generation and finish the work with the report wizard. Note: Generation of reports, execution of scripts and sending of e-mails is accomplished on the machine where the Veeam Monitor Server is installed.
Page | 84
Page | 85
If you want to receive the created report by e-mail, select the E-mail report to the following address check box and enter corresponding e-mail addresses in the field below. To enter multiple addresses, use semicolon. Please note that e-mail settings should be configured be able to receive e-mails. To learn more, see the Mail Settings section. If you want to save the created report, select the Save report to the following folder or share check box and choose destination. Beside scheduling and saving the report, you can select to execute a script when the report is uploaded. Click the Advanced... button and in the displayed window, select the Run the following script when report is uploaded check box. Use the Browse button to select an executable file. You can use two variables in the script: %reportname% full path to the report file and %reportfolder% full path to the report image subfolder.
Page | 86
Click Generate. Depending on your choice, Veeam Monitor for VMware will generate the report or schedule its generation and finish the work with the report wizard. Note: Generation of reports, execution of scripts and sending of e-mails is accomplished on the machine where the Veeam Monitor Server is installed.
Page | 87
General Settings
The General tab of the Options window allows you to change general application settings and select to use basic options. The Host settings section contains data on the used Veeam Monitor server. To change the server, enter a necessary server name in the Veeam Monitor Server field. The Chart options section allows customizing display preferences for performance graphs such as graphic type (2D or 3D), layer type (lines or filled areas), and selecting to use graph auto-scaling. The Miscellaneous section allows selecting additional application options: level of logging (Off, Low or High) and the Minimize to tray option.
Page | 88
Alarms Settings
The Alarms tab is intended for specifying trap notification settings that will be used for sending notifications about alarms. 1. 2. In the Receiver# field, specify the DNS name or IP address of the SNMP recipient. In the field on the right, enter the port number to be used. In the Community String field, enter the community identifier.
Next, you should configure SNMP service properties on the trap recipients computers: 1. 2. 3. 4. 5. Install a standard Microsoft SNMP agent from the Windows distribution. From the Start menu, select Control Panel > Administrative Tools > Services. Double-click SNMP Service to open the SNMP Service Properties window. Click the Traps tab. Add the public string to the Community name list and a necessary host name to the Trap destinations list. 6. Click the Security tab. 7. Make sure the Send authentication trap option is selected. 8. Add the public string to the Accepted community names list. 9. Select the Accept SNMP packets from any hosts option. 10. Click Apply and then OK to accept changes.
Note:
You can send trap notifications to 4 different destinations. Select the check box at the bottom if you wish to also send notifications when alarm metrics which triggered the alarm return back to normal.
Page | 89
Color Settings
The Colors tab allows you to create a custom color scheme that will be used to display graphs in the performance chart. You can add colors from the standard color palette, remove and edit existing colors, as well as sort them as required (the upper colors are used first).
Page | 90
Mail Settings
The Mail tab allows you to configure mail settings that will be used for sending generated reports and notifications about alarms. 1. 2. 3. 4. In the SMTP server field, enter the DNS name or IP address of the SMTP server that will be used for sending e-mail messages. In the From field, enter the e-mail address of the notifications sender. If your SMTP server requires SMTP authentication, select the Use authentication check box and specify authentication credentials: login and password. Select Enable SSL security if necessary.
Tip:
To test if e-mail settings have been configured correctly, click the Test button, enter the e-mail address to which a notification should be sent, and Veeam Monitor for VMware will send a test e-mail to the specified address. Test e-mails are sent by the Veeam Monitor Service.
Page | 91
Hosts Settings
The Hosts tab offers a possibility to select hosts that need to be monitored. Instead of buying licenses for all hosts running under vCenter Server, you can select hosts you want to work with and, therefore, apply licenses only to these hosts. Additionally, this option may be helpful if the ESX(i) host to which the license is applied does not require monitoring anymore (for example, if it is no longer used). To select hosts to be monitored: 1. 2. In the Options window, click the Hosts tab. Select check boxes next to necessary hosts.
Page | 92
Collector Settings
Using the Collector tab, you can view the service information, stop and restart its operation.
Page | 93
Database Settings
Using the Database tab, you may change the database authentication settings select the Windows user account that will be used to log on and work with the database or choose SQL Server authentication to the database.
To change the database authentication settings, on the Database tab click the Change Settings button. Then in the Authentication dialog box, do the following: Select the authentication type: Windows or SQL Server. If you chose Windows Authentication, choose the user account for connecting to the database. The selected account will be used to create, change or delete the Veeam Monitor database. 3. Provide the user name/login and password. The Check database, Change database and Delete database buttons can be used to manage the SQL database. To deploy a new database, click the Change database button and select a necessary SQL server to be used. Note: When changing the database, make sure the account specified in Service Database Connection has administrative privileges for the new database. 1. 2.
Page | 94
Security Settings
Using the Security tab, you can add or delete users to/from the Veeam Monitoring and Veeam Monitoring Trusted groups. The Veeam Monitoring group contains a list of users having a possibility to connect to the SQL database and work with the collected performance data. The Veeam Monitoring Trusted group contains a list of users who are allowed to automatically log on to the vSphere Client from Veeam Monitor for VMware. If the user is not in the list, when clicking the vSphere Client tab, it will be necessary to enter user credentials. If the user is in the list, at clicking the vSphere Client tab, automatic logon will be performed. To learn more about starting vSphere Client from the Veeam Monitor for VMware window, see Using the vSphere Client Tab. On the Security tab, use the Add and Remove buttons to add and remove users and groups to or from the list. Once the corresponding button is pressed, a user or a group of users will be added or deleted to/from the Veeam Monitoring group.
Page | 95
License Settings
The License tab displays information on the license that is currently installed. To change the license, click the Browse... button and select a necessary .lic file.
Page | 96
Log Settings
All errors that occur in the process of the Data Collector Service are stored in log files. To view log files, on the Logs tab, double click a necessary line in the table the selected log file will be opened. Veeam Monitor for VMware provides three levels of logging: no logging, low logging level and high logging level. To select a necessary level, choose a necessary value from the Logging level list. Besides viewing, you can delete unnecessary log files or open the folder where log files are stored: to this end, use the Delete and Open Logs Folder buttons.
Page | 97
Veeam Business View is an add-on that works with other Veeam products to provide business categorization for VMware vSphere environment. Unlike VMware vCenter Server that provides only technical view on the virtual infrastructure, Veeam Business View presents the hierarchy of VMs in business terms, as they are categorized in your virtual infrastructure. To learn more about Veeam Business View, see http://www.veeam.com/vmware-business-view.html.
Page | 98
4.
Tip:
Veeam Monitor for VMware provides a possibility to verify specified server settings. To check if you have entered correct settings, click the Test button. Veeam Monitor for VMware will display a notification informing if the data you provided is correct or not.
Page | 99
Besides, you can add custom alarms specific for a corresponding group of VMs (for example, set a more sensitive alarm monitoring resource consumption for a group of critical VMs), and generate HTML and trend reports for necessary VM groups.
Page | 100
Now you can monitor the created group as any other business group of VMs.
Page | 101
TROUBLESHOOTING
Issue The server is marked gray (connection failed) Cause Server connection settings Solution Right-click the server and select Get Error Message... from the shortcut menu to learn the error reason. Verify connection settings. Use another program to test connection to server (e.g. vSphere Client, Internet Explorer). Firewall considerations: Veeam Monitor for VMware uses the SSL port (443) to collect information from the ESX(i) host or vCenter Server. The ESX(i) host or vCenter Server is grayed out Performance graphs do not display and the database is reported disconnected Performance graphs do not display and the service is reported as disconnected Insufficient number of licenses Database host or SQL Server malfunction Ensure you have purchased enough licenses to support the number of CPUs. Verify the database host name or IP address and SQL Server instance name. Check for the SQL Server instance state and connection settings Veeam Data Collector Service malfunction (Re)start Veeam Data Collector Service
Page | 102