Specifically the following, because wouldn't the connection actually come from the source replication proxy rather than the backup server? If not, why not?
Error is unable to connect to the admin$ share on a VM which is on a separate network, which I'm assuming is related to VSS, as when I set VSS to 'ignore' the replication succeeds with a warning.
<NW-A>--------<NW-B>--------<NW-C>
Source proxies are on network-B, destination proxies and Veeam B&R Server on Network C, VM to be replicated is on network A. Trying to understand if the connection to the CIFS admin$ share is being initiated by the Source Proxy on Network-B or the B&R Server on Network C so I know which firewalls are involved.
I had thought that since the Source Proxies are repsonsible for communication with the ESXi hosts and the Guest VM that the CIFS connection would come directly from the Source Proxy on Network-B, but you're sure it comes from B&R Server on Network-C? Wouldn't this tie up the B&R server quite a bit, and what does it need this connectivity to the guest VM for?
Jim Mc wrote:I had thought that since the Source Proxies are repsonsible for communication with the ESXi hosts and the Guest VM that the CIFS connection would come directly from the Source Proxy on Network-B, but you're sure it comes from B&R Server on Network-C? Wouldn't this tie up the B&R server quite a bit, and what does it need this connectivity to the guest VM for?
This connectivity is required by our runtime that performs application-aware image processing. BTW, direct network connection is not required for this option, you can use VIX API (VMware Tools) to run this task as well.
