Discussions specific to the VMware vSphere hypervisor
Post Reply
larry
Expert
Posts: 387
Liked: 92 times
Joined: Mar 24, 2010 5:47 pm
Full Name: Larry Walker
Contact:

Quick Migration

Post by larry »

Quick Migration Version 7
I used quick migration and now my backup jobs fail with VM not found. The VM is running and never went down during migration. The migration job reported as successful. Is this expected?

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

Re: Quick Migration

Post by veremin »

You mean, you’ve migrated a Virtual Machine between hosts or datastores, and, then, backup job (that includes this VM) starts to fail with corresponding error message, right?

larry
Expert
Posts: 387
Liked: 92 times
Joined: Mar 24, 2010 5:47 pm
Full Name: Larry Walker
Contact:

Re: Quick Migration

Post by larry »

yes I migrated the vm, both host and datastore.

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

Re: Quick Migration

Post by veremin »

It seems that VM migration has resulted in VM morefID change. Veeam B&R tracks VMs by their unique moref ID. Every VM re-registeration in the virtual infrastructure (such as moving VM between standalone hosts) changes this identifier and causes the VM to be treated as a new VM.

You can re-add a given VM to a backup job and see whether it solves the issue.

Thanks.

larry
Expert
Posts: 387
Liked: 92 times
Joined: Mar 24, 2010 5:47 pm
Full Name: Larry Walker
Contact:

Re: Quick Migration

Post by larry »

It does. thanks

Seems a quick fix to update veeam database with new ID when health check is done at end of job this way veeam knows it is the same. Unless you could change the ID of the vm back on the vc.

Post Reply

Who is online

Users browsing this forum: markg, stevetNOVUS and 38 guests