Proxy Transporter Connection Problem (ActionException)

Product version: 11.0

Last modified: 17 October 2024

Question

I have two proxy transporters (the source and the target) added to Side B and an ESXi host (with the Direct Connect enabled) on Transporter B. A new repository is created on Transporter B.

I created the backup job for the VM located on the ESXi host with Direct Connect enabled and added to Transporter B.

When I try to run this job, it fails with the following error:

Connection to X transporter has been lost. Reason: Proxy transporter connection problem (ActionException)

How can I resolve this connection issue?

Answer

Source and target transporters cannot establish a connection trying to reach each other by the inner IP:port because of the following:

  • The transporters’ IPS are mapped on their sides

  • The Director located in an isolated network, can connect to both transporters by external IPs only.

As a result, backups from Side B to Side B fail.

Solution

To successfully run the job, configure the network on the transporter's side where the Director, the source transporter with the added vCenter, and the target transporter with the repository are located on three different networks:

  • Director on Side A

  • Source transporter with the vCenter on Side B

  • Target transporter with the repository on Side C

Notes

  • Both transporters are added to the Director through port forwarding.

  • Port forwarding may not work correctly within the same network.

In this configuration backing up from Side B to Side C is successful.