Veeam ONEUp to version Veeam ONE 7 the account used for connecting Veeam ONE to a vCenter only required „Read-only“ permissions as a minimum.

This has changed with Veeam ONE v8.

For example, the software now uses the new CIM-SMASH protocol to collect hardware sensors data.

The account used for connection to vCenter must have at least the permissions as described in the How-to below.

How to edit a role with minimum rights for Veeam ONE v8:

  • open the vSphere Web Client
  • change to Home – Administration – Roles
  • right-click the Read-only role and choose „Clone…“
  • edit the role name (eg. Veeam_v8)


Now add the following permissions to the new role:

  • Host – CIM – CIM Interaction
  • Host – Configuration – Connection
  • VirtualMachine – Interaction – AnswerQuestion
  • VirtualMachine – Interaction – Console Interaction
  • Global – Manage custom attributes
  • Global – Set custom attributes
  • Global – Licenses
  • Datastore – Browse datastore

Save the settings and apply the new role to the vCenter User – done!

I just upgraded Veeam ONE from 7 to v8. The upgrade is as easy as it is known from Veeam.

There is only one scenario you should take care of: if your Veeam ONE 7 SQL database has grown over 10 GB.

During installation a procedure is triggered that rebuilds indexes in the database. They do this to boost the report generation performance and other database queries.

But if your database is larger than 10 GB, this procedure needs a lot of time to complete. In this case you will see this window for a longer time:

Installing Veeam ONE Monitor Server…


Veeam has published a Knowledge Base article (KB 1951) describing what you can do if your Veeam ONE SQL database is larger than 10 GB:

Upgrading Veeam ONE to version 8 in larger environments

If you start the upgrade without reading/taking into account the KB article, do not panic.

The time required for the script to complete depends on the database size.

All you need is time – when the rebuild of indexes is finished, you can proceed with the upgrade to Veeam ONE v8.

At Thursday, February 5th the first meeting of VMUG Austria will take place in Vienna. The location for our meeting will be the Mercure Hotel near the Westbahnhof.


  • Vorstellung VMUG Austria
  • Fujitsu Österreich – Software Defined Storage & Hyper Converged Solutions – PRIMEFLEX for VMware EVO:RAIL
    Portfolioüberblick und Erfahrungen aus der Praxis
  • VMware Österreich – vRealize Operations Manager 6.0 – What’s New
    Erfahrungen von Kunden aus der Praxis

Save the date and register today at


Registration is open and free of cost (included as part of member benefits for all VMUG members).

So if you are not a VMUG member up to now do not hesitate and register (free of cost) as a VMUG member and for the first meeting.

At the moment I am working on a design concept for two smaller branch offices. Only a handful of physical servers are running there and they should be virtualized.

Thinking about VMware licensing I noticed the “new”  license editions designed for Remote and Branch Offices (ROBO): vSphere Remote Office Branch Office Standard and Advanced Editions

This licensing model is different from the previous vSphere Essentials and Essentials Plus for Retail and Branch Office editions.

You can see the details in the Feature Comparison chart below.

But first of all I would like to point out the most important changes:

  • vSphere HA, vMotion, Replication, Fault Tolerance and Storage vMotion is included in both editions
  • vSphere ROBO Advanced additionaly includes Distributed Switch and Host Profiles/Auto-deploy
  • you can run up to 25 VMs per remote site (but more VMs per site are NOT possible with this license!)
  • Milestone: you can use your existing vCenter Server Standard for central management – no need for a seperate vCenter Server


The possiblity to use the existing vCenter for central management of the remote site is a key feature in my opinion. With the previous vSphere Essentials/Essential Plus Editions you had to host and maintain a seperate vCenter Server only for the three included ESXi Hosts (hard limit) per site.

A lot of work for the administrator (= high costs…)

Here you can find a feature comparison between the old and the new editions (click to enlarge):



With the previous versions you were only allowed to run three ESXi hosts per site.

With the new editions, this model has changed. No more restrictions to either the number of hosts per site nor the number of sites where ROBO can be deployed.

The only restriction you must take care of is that you can only deploy one ROBO pack per site. This means you can only run a maximum of 25 VMs per site using this licensing model.

If you need more VMs you should think about a vSphere Standard, Enterprise or Enterprise Plus license.

Please also note, that you cannot mix ROBO Editions and other vSphere licenses in the same site.

But an advantage: you can use one ROBO pack for eg. two smaller sites as long as you do not exceed the total amount of 25 VMs.