Have you checked that $ADMIN share is accessible using the account you'd specified?
v.Eremin wrote:Can you also try to install required packages manually and, then, re-add proxy? Required package (VeeamTransport.msi) can be found under the Backup/Packages/. Thanks.
Please open explorer on your VBR server and type in \\yourproxyhostname\admin$. It will either prompt you for username and password (use admin account) or let you in using your current account. Then try to create a folder in that share. If you manage to create a folder then use the same account to install proxy on that server. If installation still fails then please check if port 6160 is allowed. If that does not help then kindly open a ticket with support and post case ID herewhere can I find that $ADMIN, and how to setup that?
No, it's not a good practice because both proxy and Exchange servers typically experience a significant load, so it would be better to have a dedicated VM as a proxy placed on the same host where your exchange server reside for hot-add mode. If your Exchange VM resides on a datastore that is connected to ESXi vis iSCSI or FC then even the better option would be to use direct SAN approach.by the way, is it right if I make the exchange server as a proxy to backup exchange (itself) from Veeam?
mobdoc wrote:by the way, is it right if I make the exchange server as a proxy to backup exchange (itself) from Veeam?
Users browsing this forum: DGrinev and 27 guests