Replication Error: No Proxy

[homerjnick]

I have a rather strange issue.

At our HQ I have my v7 B&R Server and another VM that is a Proxy.

At my DR site I have two VM's that are proxies.

My vCenter at my DR site got corrupted beyond repair so I removed it from Veeam by deleting all my replica jobs and just to get replicating going I added the DR ESXi host direct (we only have one anyway).

I removed the two proxies from Veeam (they were corrupted too...power outage), added 2 new VM's to the DR environment and made them Veeam proxies.

I have in my list of proxies 4 entries...my B&R Server, my VM at HQ and the two at my DR site.

In my replication job I set it to the source proxy be either proxies at the HQ site and the target proxies to be either of the two at the DR site, I then map the replica to the old replica VM at the DR site and run the job.

I get an error stating no proxy.

I am a bit confused...it is a very simple setup...worked a treat when the DR vCenter was there...anything obvious I am missing?

[foggy]

Nick, what are the transport mode settings for those proxies? What is the exact error text?

[homerjnick]

Error is:

"Failed to create processing task for VM: {VM NAME}: Error No Proxy.

All 4 proxies are set to Automatic Transport Mode.

[veremin]

Just out of curiosity - what happens if you set automatic proxy selection? Will it make any difference? Anyway, if this doesn't help, kindly, open a ticket with our support team and let them investigate it directly. Thanks.

[homerjnick]

If I set it to Automatic Proxy selection it doesn't use the proxies at the DR site but uses the proxy at HQ and therefore the job takes too long...

I'm going to reintroduce my vCenter at the DR site anyway so will see what happens...

[foggy]

For some reason it doesn't take the DR proxies as available. Debug logs will tell the reason why.

[homerjnick]

Adding the vCenter back in and DR proxies work a treat...

[foggy]

Great, thanks for the update.