VMware Cloud Community
pjapk
Contributor
Contributor

Migration from 3.5 & 4.0 environment to 5.0

If you are unconcerned about retaining historical data from a vc4.0/32bit instance and happy to start afresh with a new vc5.x instance, is it simply a case of "removing" each (4.x) host in turn from the vc4 instance & then adding it to the vc5 instance?

If so, does such a change require a full restart of the VMs currently running or is it just a managment agent restart?

Also, if "migrating" the hosts to new boxes with different CPU architecture (going from Intel to AMD) is it just a case of having all the hosts managed by the same VC instance, then powering VMs off (on the Intel host) briefly prior migrating them to the new AMD box & powering them back on again?

Paul

(I'm aware that 3.5 hosts can't actually be migrated in-place)

Reply
0 Kudos
2 Replies
hpreyers
Contributor
Contributor

If you are unconcerned about retaining historical data from a vc4.0/32bit instance and happy to start afresh with a new vc5.x instance, is it simply a case of "removing" each (4.x) host in turn from the vc4 instance & then adding it to the vc5 instance?

If so, does such a change require a full restart of the VMs currently running or is it just a managment agent restart?

Yes, removing the host from the cluster will not require to move away the guest running on the host. The guests will continue to run on the host. Adding the host to the new vc5 instance will make your guests available in the new cluster.

Also, if "migrating" the hosts to new boxes with different CPU architecture (going from Intel to AMD) is it just a case of having all the hosts managed by the same VC instance, then powering VMs off (on the Intel host) briefly prior migrating them to the new AMD box & powering them back on again?

This is correct. It is not a requirement that all hosts are managed by the same VC instance. If your storage is visible from all hosts then you can move the guests.

Reply
0 Kudos
jhenry
Contributor
Contributor

hi

Reply
0 Kudos