Win32 error: The network path was not found. Code 53

Networkless Guest Processing in vSphere Environments

When working with vSphere environments, it is possible for Veeam Backup & Replication to use a network-less connection method (VIX) if direct communication fails. This method uses VMware VIX/vSphere Web Services to push the runtime components into the machine and manage them. If the VM being protected is in a DMZ or other network-isolated configuration, it may not be possible to get RPC working and require that connectivity via VIX be investigated. Reference: https://www.veeam.com/kb1788.

Forcing VMware VIX in Isolated Environments

If Veeam Backup & Replication will be operating in a vSphere environment where the Veeam server and its components will never have direct network connectivity to the Guest OS of the Virtual Machines, it is possible to force network-less guest processing connection (VIX) to be attempted first.

For all Veeam Backup & Replication Versions:

Create the following registry value on the Veeam Backup & Replication server:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: InverseVssProtocolOrder
Value Type: DWORD (32-Bit) Value
Value Data: 1

0 = Try RPC (admin$ share) first, then failover to VIX. (Default behavior)
1 = Try VIX first, then failover to RPC (admin$ share)

Note: Veeam Services do not need to be restarted. The registry setting will go into effect on the next job run.

For Veeam Backup & Replication versions 9.x through 10a:

For older versions, the registry value must also be created on each Guest Interaction Proxy that the Backup Job will use.
_{Note that the Key Location is different.}

Key Location: HKLM\SOFTWARE\Wow6432Node\Veeam\Veeam Backup and Replication\
Value Name: InverseVssProtocolOrder
Value Type: DWORD (32-Bit) Value
Value Data: 1

0 = Try RPC (admin$ share) first, then failover to VIX. (Default behavior)
1 = Try VIX first, then failover to RPC (admin$ share)

Note: Veeam Services do not need to be restarted. The registry setting will go into effect on the next job run.

Networkless Guest Processing in Hyper-V Environments

When working with Hyper-V environments, it is possible for Veeam Backup & Replication to use a network-less connection method (PS Direct) if direct RPC communication fails. This method uses PowerShell Direct to push the guest processing runtime components into the machine and manage them.

Forcing PowerShell Direct in Isolated Environments

If Veeam Backup & Replication will be operating in a Hyper-V environment where the Veeam server and its components will never have direct network connectivity to the Guest OS of the Virtual Machines, it is possible to force network-less guest processing connection (PS Direct) to be attempted first.

For all Veeam Backup & Replication Versions:

Create the following registry value on the Veeam Backup & Replication server:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: HvVssPowerShellDirectPriorityOverNetwork
Value Type: DWORD (32-Bit) Value
Value Data: 1

0 = Try RPC (admin$ share) first, then failover to PowerShell Direct. (Default behavior)
1 = Try PowerShell Direct first, then failover to RPC (admin$ share).

Note: Veeam Services do not need to be restarted. The registry setting will go into effect on the next job run.