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?
-
- Veteran
- Posts: 387
- Liked: 97 times
- Joined: Mar 24, 2010 5:47 pm
- Full Name: Larry Walker
- Contact:
-
- Product Manager
- Posts: 20411
- Liked: 2300 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Quick Migration
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?
-
- Veteran
- Posts: 387
- Liked: 97 times
- Joined: Mar 24, 2010 5:47 pm
- Full Name: Larry Walker
- Contact:
Re: Quick Migration
yes I migrated the vm, both host and datastore.
-
- Product Manager
- Posts: 20411
- Liked: 2300 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Quick Migration
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.
You can re-add a given VM to a backup job and see whether it solves the issue.
Thanks.
-
- Veteran
- Posts: 387
- Liked: 97 times
- Joined: Mar 24, 2010 5:47 pm
- Full Name: Larry Walker
- Contact:
Re: Quick Migration
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.
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.
Who is online
Users browsing this forum: No registered users and 56 guests