First steps for Veeam ONE configuration

In the previous article we covered the installation steps for Veeam ONE. In this one we follow up with the review of the main settings for the Veeam ONE configuration. There are two types of settings we can configure. The Client and Server Settings. In particular this article will show the Server Settings for Veeam ONE. At a later stage with the installation of a standalone client we’ll cover such settings in a separate article.

Veeam ONE consists of three major components:

  • Veeam ONE Monitor
  • Veeam ONE Business View
  • Veeam ONE Reporter

The Monitor component is the “brain”. This is also the main one we access through the console login. This console also provides the links to access the Business View and Reporter. The Monitor shows the entire virtual infrastructure including access to all functionalities and reports as we’ll see later on.

The Business View component has the capability to categorise all monitored objects (eg, Hosts, Cluster, VMs and Datastores) into custom groups and categories with the aim to present the virtual infrastructure data more appealing from a Business point of view. For example automatically run a report showing resources consumption and charge-back for all Web Applications used by a particular department or sitting on a particular storage. Really there are plenty of combinations.

The Reporter component is the “brawn”. In fact this component is the one running the reports against the collected data and it is also possible to choose between the large number of canned reports and create custom once depending on requirements. Another great feature is the option to customise reports branding to target for example different departments within the organisation, offices or even separate tenants making this solution palatable also for Service Providers.

At this point we are ready to start exploring Veeam ONE configuration settings!

 

Veeam ONE Configuration settings

From the desktop where we installed the Veeam ONE Server we have the links to start the main console with access to the Veeam ONE Monitor. Let’s make sure the details are correct and click connect. Should we need to install additional standalone consoles the user experience is exactly the same. Also this will prevent us to connect to RDP session to the main server itself. In such can I would recommend to control the ports required for connectivity to the console. More information about ports on this link.

Veeam One Configuration login

We are now logged into the Veeam ONE Monitor console from where we have access to all the configuration settings. Before adding any new virtual infrastructure to monitor let’s take a look on the global settings.

Veeam One Configuration console

From the ribbon let’s go for Options > Server Settings.

Veeam One Configuration settings

In the Server Settings we can control various aspects. The first one of course is the main configuration for the email settings. The options here are pretty much straight forward.

Veeam One Configuration SMTP Settings

Next is the Notification Policy. From the Configure button we can setup recipients or groups which will automatically receive emails based on Errors, warnings or any state. In addition the option to edit the templates including different tokens like:

  • Alarm name
  • Time
  • Status
  • Old Status
  • Objects
  • Object type

What I particularly like is the ability to automatically include also a link to the pertinent KB articles!

Veeam One Configuration Notification Policy

In the SNMP tab the option to configure the settings on where to send the SNMP traps and relative version. All versions v1, v2 and v3 are supported.

Veeam One Configuration SNMP settings

In the monitored Datastores we can simply choose which ones we want to collect the data from. This view will be populated as soon as we add virtual infrastructures.

Veeam One Configuration Monitored Datastore

In the case of Monitored Objects we can simply create inclusion or exclusion rule for specific Virtual Machines. For example we might want to exclude VMs created for testing or used by Developers and destined to be deleted.

Veeam One Configuration Monitored Objects

In the last tab we have other main settings for the Business View component and the vCloud Director integration. Very interestingly the ability to launch a Support utility for even deeper configuration details.

Veeam One Configuration other settings

The Veeam ONE configuration utility gives us the option to setup:

  • Database connectivity
  • Retention Policy Period
  • User Credentials to access the Database
  • Full URL to access the Business View and Reporter components

Veeam One Configuration Database settings

From the Reporter Tab we can control:

  • Te status of Service with other info as well
  • The option to clean-up data relative to objects we do not need to monitor anymore
  • Full URL to access the Reporter website

Veeam One Configuration Reporter settings

From the Monitor Tab we can control:

  • Te status of Service with other info as well
  • The option to configure the location Veeam ONE Monitor will use to cache temporary data whilst working and optimise operations.

Generally speaking this location doesn’t have to be big or super fast. 1000 VMs can generate up to 6 GB of data in the Cache folder.

Veeam One Configuration Monitor settings

From the Scalability Tab we can control:

  • The deployment type. This means we can change this to be adherent to current requirements

This link shows more info about the different Data Collection Modes.

Veeam One Configuration scalability settings

And finally we also have the option to pick and choose which performance counters Veeam ONE will collect information from. This includes:

  • vSphere Counters
  • Hyper-V Counter
  • Backup Counters
  • vCloud Counters

Veeam One Configuration performance metrics

And this concludes a quick overview on the main Veeam ONE configuration settings. Now that we have a better understanding how these operates it is time to start adding objects to our virtual infrastructure as we’ll cover in the next article of this series.

Hopefully this was informative and looking forward to comments and feedback!

Michele Domanico

Passionate about Virtualization, Storage, Data Availability and Software Defined Data Center technologies. The aim of Domalab.com is sharing with the Community the knowledge and experience gained with customers, industry leaders and like minded peers. Always open to constructive feedback and new challenges.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: