I'm running B&R 9.5 with two Hyper-V guests (all Windows Server 2016). After applying the latest Windows updates, Veeam could no longer connect to one of the two Hyper-V guests via RPC (similar to the error described here: https://www.veeam.com/kb1230).
To fix this, I had to change the credentials being used by Veeam. Instead of using the local Administrator account to connect to the guest system, I had to use the domain Administrator account. This is now the only way to connect to the server's admin share.
I suspect this is not a bug in Veeam, and in fact has nothing to do with Veeam, so I don't think it's an issue to raise with support. But I have a few questions:
- Isn't it better to connect using the local Administator account for backups?
- If my domain controller is down during the backup, won't this make backups impossible?
- Does anyone know of a way to enable access to the admin share using the local Administator account, assuming this is "best practice"?