Solved

Hyper V 2019 standalone host replication job fails


Userlevel 5

I have recently added a standalone Hyper V 2019 host to Veeam infrastructure. It added successfully. SO i created a HWP for my customer, see the host and the network. When the customer creates his job, he see his plan however when he runs the replication job  it fails:

“Failed to process replication task Error: Cloud gate has rejected connection. Reason: Unable to establish target connection. All aliases have failed….”

 

My VMware replications are running fine.

Please help!!

icon

Best answer by MicoolPaul 6 June 2022, 13:38

View original

13 comments

Userlevel 7
Badge +1

Can you share the screenshot of the error?

Userlevel 7
Badge +20

Hi @Nolzzz.

 

So you’re supplying Veeam Cloud Connect services to a customer with Hyper-V hosts available for replication services is that correct?

 

The key information is missing here as we need to see the logs from the customer’s VBR server AND the VCC cloud gateway/gateway pool to see if the problem is communication from customer to VCC or your gateway speaking to the Hyper-V server.

 

As this is a new host standup, have you checked that the cloud gateway server can ping the Hyper-V host and resolve any DNS records successfully? I’d start with the basic network connectivity tests and build up from there.

Userlevel 5

Error attached

Userlevel 5

Yes, the cloud gateway can ping the Hyper V host. Support has reviewed the logs and saw no issues, but i am still talking to them.

 

Userlevel 7
Badge +20

Thanks, is this a single cloud gateway or a gateway pool?

 

This is a communication issue error, so the likely culprits are DNS or firewall if ping is working.

Userlevel 5

Thank you. Its always something small that you miss.

I have 2 NICs - one with a gateway and 1 without.

needed to define how to get to the network on the NIC with no gateway.

 

Userlevel 7
Badge +20

Thank you. Its always something small that you miss.

I have 2 NICs - one with a gateway and 1 without.

needed to define how to get to the network on the NIC with no gateway.

 

Yeah having this setup needs a static route for your non gateway NIC.  Hopefully that resolves your issue.

Userlevel 5

Thanks guys, you are all stars. 😀

Userlevel 7
Badge +7

Thank you. Its always something small that you miss.

I have 2 NICs - one with a gateway and 1 without.

needed to define how to get to the network on the NIC with no gateway.

 

Hi @Nolzzz

the classic problem of multihomed servers.😀
Static route fix the problem as mentioned by  @Chris.Childerhose 

regards

Userlevel 7
Badge +20

Thanks guys, you are all stars. 😀

Happy to help, don’t forget to mark the best response as the answer to help the next person please! 🙂

Userlevel 7
Badge +10

Thanks guys, you are all stars. 😀

Heck yeah they are!

Userlevel 7
Badge +9

Thank you. Its always something small that you miss.

I have 2 NICs - one with a gateway and 1 without.

needed to define how to get to the network on the NIC with no gateway.

 

Hi @Nolzzz

the classic problem of multihomed servers.😀
Static route fix the problem as mentioned by  @Chris.Childerhose 

regards

But a different answer has been marked! I think both are driving us in the right direction.

Userlevel 7
Badge +20

Thank you. Its always something small that you miss.

I have 2 NICs - one with a gateway and 1 without.

needed to define how to get to the network on the NIC with no gateway.

 

Hi @Nolzzz

the classic problem of multihomed servers.😀
Static route fix the problem as mentioned by  @Chris.Childerhose 

regards

But a different answer has been marked! I think both are driving us in the right direction.

Yeah was sad to not see my answer. Oh well it is there for all. 😁

Comment