Agent backup of Veeam backup server itself

Hello ​@Nikks! Hope everything is going well.

This error usually indicates an authentication or administrative access issue when Veeam tries to deploy the agent via ADMIN$ share.

Based on similar cases, I would recommend checking:

• Antivirus or endpoint protection blocking remote installation;
• Windows Firewall, especially SMB/WMI rules;
• UAC remote restrictions;
• Local security policies;
• User permissions, must be local admin on the target machine;
• Authentication format, DOMAIN\user or SERVER\user for local account.

Also, check the path in the error, it seems there might be a typo in the IP address 10.1.0.2.1.

You can install the agent on VBR yes just need to determine from Matheus list which is blocking you.  But if you are using v13, then you might want to look into the VSA as you can use HA Clustering with it for DR purposes.

To me though, I would not install the agent as the configuration backup is enough to bring the VBR back in a disaster as long as it is saved in multiple places including offsite.

Thanks @matheusgiovanini

As checked server is part of workgroup  we are able to access ADMIN$ share inside that server

Through run -->\\10.1.0.2.1\ADMIN$.

Thanks ​@matheusgiovanini 

As checked server is part of workgroup but admin share we are able to access inside that server

Through run -->\\10.1.0.2.1\ADMIN$  . I want to know if Agent backup of Veeam server iitself supported and we are seeing this error?

Hi ​@Nikks -

Are you attempting to install the VAW agent on the VBR server itself? No...that isn’t a recommended backup method, though it “should” work.

Usually, you need the actual local admin used to install the OS to connect to admin shares. The UAC may need to be configured as Matheus states to allow other local Admin accounts to connect. I provided the steps on how to do this in the below post who had a similar issue, but when needing to connect HV hosts to VBR:

See if that helps.

Also, is there a reason you wouldn’t use the config backup to do a restore? Is this a physical VBR server?

Thanks. Yes this is a physical server

There is nothing in the VAW Guide in System Requirements that states using it for Windows VBR isn’t supported, but isn’t recommended. Veeam recommends just doing a config DB backup restore. Although, if you want to backup files you have on the server...I get it. 

My 2 VBRs are VMs and I actually use VBR to do image backups of them in case there’s a file I need to reestore. Otherwise, to recover the VBR server itself, I use my config backups (have performed that task once...flawlessly).

Anyway, try implementing the UAC ‘fix’ and see if that resolves your issue. Keep us posted.

Thanks for confirming the details!

Since the server is in a workgroup and you can access ADMIN$ manually, this is very likely related to UAC remote restrictions, especially when using a non-built-in Administrator account.

Also, just to double-check, the IP shown in the error 10.1.0.2.1 looks incorrect, worth validating that as well.
And I agree with Shane, while agent-based backup is supported, configuration backup is the recommended approach for VBR recovery.