Discussions specific to the VMware vSphere hypervisor
Post Reply
Kazz
Influencer
Posts: 10
Liked: 1 time
Joined: Feb 08, 2018 3:47 am
Full Name: Kazz Beck
Contact:

Broken replication jobs after vCenter replacment [BUG]

Post by Kazz » Nov 03, 2018 12:36 am

All of our replication jobs seem to be broken after vCenter was replaced with an appliance.

I didn't expect veeam to know how to find the VMs in the new vcenter since it was not a straight upgrade. So I took the time to go though all jobs, remove the VMs that were added via the old vcenter and re-add them using the new vcenter. When highlighting the vm inside the replication job it does show the correct path to the VM. New-vcenter\DataCenter\Cluster\VM

When I start the updated job it fails with the following error " Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond "

Looking at the log for the job, I am still seeing references to the old vcenter

Gostev
SVP, Product Management
Posts: 24940
Liked: 3622 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Broken replication jobs after vCenter replacment [BUG]

Post by Gostev » Nov 03, 2018 4:18 pm

Normally you should use vCenter migration script to update VM references in the configuration database (search Veeam KB for the script).

However, I believe the error you're getting is generic and unrelated anyway. Try creating a new job with one VM and see if it works?

Kazz
Influencer
Posts: 10
Liked: 1 time
Joined: Feb 08, 2018 3:47 am
Full Name: Kazz Beck
Contact:

Re: Broken replication jobs after vCenter replacment [BUG]

Post by Kazz » Nov 03, 2018 6:30 pm

Yes, new replication jobs work fine.

What I am trying to say is GUI does not have the old vcenter listed anywhere in the job, however it's trying to get the info for the VM via the removed vcenter

veremin
Product Manager
Posts: 17005
Liked: 1455 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Broken replication jobs after vCenter replacment [BUG]

Post by veremin » Nov 05, 2018 11:30 am

There might be some stalled references to old vCenter in product database. If you want to double check that, kindly, open a ticket with our support team and let them investigate that directly. Thanks!

Post Reply

Who is online

Users browsing this forum: No registered users and 24 guests