Veeam One and Backup Servers : HRESULT: 0x80070005 (E_ACCESSDENIED)

One of the nicest thing Veeam One 6.5 added is the support to monitor and report on your backup infrastructure. In Veeam One 7 the possibilities are now expanded. For example a lot of reports for Backup & Replication has been added. For the monitoring part, you can now really monitor CPU/MEM/Network via One console. One will collect the data via WMI so it is a pretty standard approach.

It is really interesting as I often have customers telling me that B&R reporting is limited. Then I will show them Veeam One reporting and they will be blown away. Sometimes it even happens that the customer has a Veeam Essentials license and that he is unaware of the fact that he already has the licenses for One. Basically Veeam Essentials is the Veeam Backup Management Suite but limited to 6 sockets.

To start using it just go to the Data Protection View, right-click the Backup Infrastructure node in the inventory pane and choose Add Server from the shortcut menu. I would recommended adding the enterprise manager so that all your backup servers are automatically added.

When you add Veeam Backup & Replication to the Veeam One server you will use a certain user to connect to the backup server. Most cases it will be a separate service user. In my case I use "vlab\srvone".

Following the docs this "srvone" user should have local administrator rights on the backup server:
The account must have local Administrator permissions on the backup server and on all servers that run backup infrastructure components. For details on required permissions for Veeam backup servers

However I was getting an error on some of the proxies ( HRESULT: 0x80070005 (E_ACCESSDENIED) ). Basically One is unable to connect via WMI:

This make sense as Veeam One uses the same credentials you specified when adding the enterprise manager. You can check the credentials used by right clicking the enterprise manager and clicking "Change Connection Settings"

So if you are in this case, it probably means that srvone is not added to the local administrator group on your proxy servers. There are 2 things you can do. First of all you can right click the component and override the credentials for that certain proxy or repository. I had to do this for a remote repository / wan accelerator that is not in the domain.

You could also of course add the user to the local administrator group. However I have some core servers in demo. So here is the oneliner you can use to add the user to the local admin group via cli
 net localgroup Administrators /add vlab\srvone

After this is done, you can resolve the alarm on the server. After 15m you should see WMI data flow in on the Network tab for example

For my lab I also have this oneliner I always use to disable the firewall. Might be irrelevant to this article but still in demo setups I always use it to make sure it is not a firewall issue I'm running into
 netsh advfirewall set allprofiles state off

1 comment:

Note: Only a member of this blog may post a comment.