Moving VMs from 4.3.9 to 4.4.4
What is the best way to move VMs from current 4.3.9 to a new 4.4.4. environment? The current environment is running oVirt 4.3.9 (started as 4.3.7). There is a single data domain using NFS on a single NAS. The future oVirt 4.4.4 environment will also have a single data domain using NFS on the same NAS as the current environment. What is the best way to move approximately 40 VMs from current 4.3.9 to a new 4.4.4. environment? Are there any caveats or considerations I need to take into account when moving the VMs? Your help, as always, is greatly appreciated.
Is it safe to attach my new 4.4 environment to an export domain at the same time my 4.3 environment is attached to it? I need to start moving VMs from my current 4.3 to my new 4.4 environment.
Keep the export domain attached only to 1 environment at a time... it's way more safer. Usually each engine updates some metafiles on the storage domain and when both try to do it ... you got a bad situation there. Attach to 4.3 , move VMs, power off them , detach the storage domain - so you can attach it to 4.4 and migrate those VMs. And don't forget the templates the VMs were created from. Best Regards, Strahil Nikolov В понеделник, 28 декември 2020 г., 13:10:01 Гринуич+2, Diggy Mc <d03@bornfree.org> написа: Is it safe to attach my new 4.4 environment to an export domain at the same time my 4.3 environment is attached to it? I need to start moving VMs from my current 4.3 to my new 4.4 environment. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/E4FQFIPVKJUGK5...
On Mon, Dec 28, 2020 at 12:26 PM Strahil Nikolov via Users <users@ovirt.org> wrote:
Keep the export domain attached only to 1 environment at a time... it's way more safer. Usually each engine updates some metafiles on the storage domain and when both try to do it ... you got a bad situation there.
Attach to 4.3 , move VMs, power off them , detach the storage domain - so you can attach it to 4.4 and migrate those VMs. And don't forget the templates the VMs were created from.
Best Regards, Strahil Nikolov
Trying to attach an export domain to a second infra should give you an error about being "already attached elsewhere" and prevent it. It often happens to me using the same export domain to share resources between 3 different environments. Not tried with heterogeneous env yet (eg activated on 4.3 and trying to activate in 4.4, or vice versa) but I think it should give the same error message. Gianluca
Templates? Aren't the VM's templates automatically copied to the export domain when the VM is copied to the export domain as part of the Export operation? Maybe I'm confused about how the export/import operations work and the purpose of the export domain. And noted, I will be sure to only have one environment at a time attached to the export domain.
On Mon, Dec 28, 2020 at 5:53 PM Diggy Mc <d03@bornfree.org> wrote:
Templates? Aren't the VM's templates automatically copied to the export domain when the VM is copied to the export domain as part of the Export operation? Maybe I'm confused about how the export/import operations work and the purpose of the export domain.
And noted, I will be sure to only have one environment at a time attached to the export domain.
I think Strahil is referring to the possible options when you create a VM from a template (clone vs thin) and the impact when you export them; see here (paragraph 6.13.1): https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/htm... HIH, Gianluca
I'm not sure if the templates are automatically transferred , but it's worth checking before detaching the storage. Best Regards, Strahil Nikolov В понеделник, 28 декември 2020 г., 18:53:27 Гринуич+2, Diggy Mc <d03@bornfree.org> написа: Templates? Aren't the VM's templates automatically copied to the export domain when the VM is copied to the export domain as part of the Export operation? Maybe I'm confused about how the export/import operations work and the purpose of the export domain. And noted, I will be sure to only have one environment at a time attached to the export domain. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IZ6OEZ7NODHNFA...
participants (3)
-
Diggy Mc -
Gianluca Cecchi -
Strahil Nikolov