always on SQL restore

[hnhn99]

When I try restore in my always on SQL environment, the sql agent seems to want to connect with the replication network that is private and no routing to. How to control this?
DCOM was unable to communicate with the computer xxxx using any of the configured protocols; requested by PID 49f8 (D:\Veeam\Backup & replication\Explorers\SQL\Veeam.SQL.Explorer.exe).
case:07015228

[Andreas Neufert]

Maybe try to address this by changing the DNS records on the server where the explorer and the mount server + Veeam backup server is located and point it to the correct address. Maybe by hosts file edit on the 3 servers.

[marina.skobeleva]

Hi Hakan,

First of all, you need to make sure that Veeam Explorer for Microsoft SQL Server can access all nodes in the availability group. More details are here.

When you create an Always on Availability Group there is a setting for EndPoint URLs. Probably Microsoft guide will be helpful for this case. The main idea that IP addresses to which these endpoints are resolved should be available for Veeam Explorer for Microsoft SQL Server.

Thanks!

[hnhn99]

So just to verify veeam dosen't support SQL cluster with an private unrouted replication network?

[Andreas Neufert]

Why do you think this is the case? The above indicates that the EndPoint URLs are not bound to "public" accessible interfaces or DNS goes to the wrong IPs.