Problem with backups after adding new host to vcenter

[choldings]

I added a new host to a vcenter cluster. I migrated a couple machines to the new host and when their jobs ran for the first time, they failed with the following error(s):

Job Error:

Failed to create processing task for VM machinename Error: Host 'hostname' with type 'ESX' and parentId '8b837b85-05e1-4c5b-ae2c-18d1a84c06ba' not found.

Machine in job error:

Task failed Error: Host 'hostname' with type 'ESX' and parentId '8b837b85-05e1-4c5b-ae2c-18d1a84c06ba' not found.

What could cause this?

[nefes]

Colin, have you tried to rescan your VCenter under Backup Infrastructure node?

[Vitaliy S.]

Colin, with all technical issues please contact support directly, as it is advised when you click New Topic. Thanks.

[choldings]

Colin, with all technical issues please contact support directly, as it is advised when you click New Topic. Thanks.

Sorry. I get a little fuzzy on what is acceptable and what isn't in the forums when it comes to asking for help.

I'll open a case.

[choldings]

Support case ID: 00453086

[choldings]

Colin, have you tried to rescan your VCenter under Backup Infrastructure node?

The host does show up under vcenter in the veeam console. I am running a rescan anyway now.

[veremin]

Also, you can try to re-add given VMs to the backup job and see whether it helps or not. Thanks.

[choldings]

Also, you can try to re-add given VMs to the backup job and see whether it helps or not. Thanks.

I did this for one of the failed jobs and it seems to have worked. My only concern now is will I need to remove and re add any virtual machine that has been migrated to this new host from its existing Veeam job and re add it.

I'm going to see what happens when they run tonight.

The rescan was a success and Veeam appears to be aware of the host.

[veremin]

As long as VMs are added to backup console via vCenter, backup server should be vMotion aware and you shouldn’t encounter any issues after VM migration. However, it seems that vCenter added to backup console didn't know about the new host and about the fact that certain VMs had been migrated to it, thus, backup jobs failed. So, now, when the rescan is done, everything should be ok, even without manual re-adding of VMs.

Thanks.

[choldings]

Thanks! I verified this morning that another virtual machine that was migrated to the new host did in fact backup successfully without the need to remove and re add it from the job.

[veremin]

Glad to hear that you’ve finally nailed it down. Should any additional help be needed, don’t hesitate to let us know. Thanks.

[rreed]

Morning, all. Looks like in v9 this might still be happening. We've rolled a new vCenter, removed a few hosts from the old, added to the new. One of our hosts w/ its VMs worked fine the first day or two. Last night it's throwing "PhysicalHost with id 'blah' was not found." I've removed the host, re-added to the vcenter, rescanned the vcenter, rescanned all vcenters, even the rescanning throws the error. If I scan the individual host, it seems perfectly fine and happy and sees it. I can move VMs back to it, remove/re-add, it picks up the VMs on the host. But scanning the vcenter or especially backups keeps returning this error and the backups of course fail for any VMs on that host.

[foggy]

I'd approach support with this, logs review is required.