Trying to add server to B&R console: RPC server unavailable

[john-kennex]

Hi all,

I am trying to add several Azure servers to my B&R console. I either get "the username or password is incorrect - failed to connect to admin share" or "the RPC server is unavailable". If I browse from the Veeam server to the remote admin share, it works fine. I've quadruple checked the username/password saved in the Credentials section. Those are correct. Majority of the time, I get the RPC error. I've went through and made sure the services were started on the remote server. I can't seem to figure out what is causing this error. The servers are on the same subnet, so no firewall in between them. What is weird is, the Veeam server can install the agent, and works with the 3 domain controllers I have setup. Those are actually in 3 different subscriptions, along with 3 different subnets. But can't seem to get any of my other servers into a "protection group" or just adding them individually.

Any help with this would be greatly appreciated! I've worked with support, during our trial period, and he made it work at one point, but we installed the agent manually on the test server and did an agent backup, which is not what I want to do. I want to control the backups from the backup server. I do realize that there is a product -Veeam Backup for Azure, but we purchased Veeam Backup and Replication, which is what our Veeam rep recommended to us, since we are backing up file shares, and other stuff. If I missed anything in this description, please feel free to ask. I will clarify anything that I need to. Thanks in advance!

[nielsengelen]

Hi,

Can you clarify what you mean by adding Azure servers? Are you adding Windows servers or the direct file share?

Veeam Backup for Azure does support Azure File Shares protection with FLR recovery options.

[john-kennex]

Hi, sorry, I mean Azure VMs (Windows servers).

[nielsengelen]

Then I would suggest you open a support case for this and let us know the case ID for future reference. While the agent will most likely always work, it should be possible to add the server if everything is configured correctly (firewall, ports, share access).

If this does not work, you can also look at VB for Azure which supports VUL licenses and can be integrated with your VBR deployment (you can deploy VB for Azure from the VBR console).