Good afternoon,
I'm trying to figure out why a Quick Migration between two standalone hosts (no shared storage) will only operate in cold migration mode. No matter what I try I cannot get it to run in a hot migration mode. The hosts are physically the same with identical CPU and ESXi builds and licensed with Essentials . Any ideas on why this is not working?
Regards,
Colin
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Feb 07, 2020 8:23 pm
- Full Name: Colin Howitt
- Contact:
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Quick Migration Issue
Hello Colin and welcome to the community!
In general quick migration type depends on CPU compatibility of source and target hosts. It is available with all VBR product licenses.
However, you need Essentials Plus vSphere license to leverage vMotion technology that is used by Veeam Quick Migration for the "hot switch".
Thanks
In general quick migration type depends on CPU compatibility of source and target hosts. It is available with all VBR product licenses.
However, you need Essentials Plus vSphere license to leverage vMotion technology that is used by Veeam Quick Migration for the "hot switch".
Thanks
-
- Veteran
- Posts: 266
- Liked: 30 times
- Joined: Apr 26, 2013 4:53 pm
- Full Name: Dan Swartzendruber
- Contact:
Re: Quick Migration Issue
I've also seen odd behavior from vcenter, when trying to hot-migrate a guest running on a sandy bridge host to a broadwell host. It *should* work in that direction, but at least once, it didn't. Anyway, try to eliminate veeam from the equation by trying to migrate the guest from host A => host B directly in vcenter.
Who is online
Users browsing this forum: Semrush [Bot] and 28 guests