bunny101
Contributor
Contributor

vSphere 4.1 cold migration - how long should it take?

Jump to solution

Hello!

We're starting the process of upgrading our hosts and vSphere components from 4.1 to 5.5.  We need to upgrade RAM on the hosts and consequently need to move some VMs between hosts.

Some of these VMs do not have VM Tools installed, so they will need to be cold migrated.  Shut down, migrate, restart, rinse and repeat.

I'll do some testing, but my previous experience on this is a bit hazy.  We're not moving storage, just the VM.  I recall this operation only taking one or two minutes to complete.

What's your experience with how long this kind of cold migration takes?

Thanks in advance!

G

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
rcporto
Leadership
Leadership

Why not vMotion the VMs instead of Cold Migration ? vMotion does not requires VMware Tools installed on VMs: Virtual Machine Conditions and Limitations for vMotion in the vSphere Web Client

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto

View solution in original post

0 Kudos
2 Replies
rcporto
Leadership
Leadership

Why not vMotion the VMs instead of Cold Migration ? vMotion does not requires VMware Tools installed on VMs: Virtual Machine Conditions and Limitations for vMotion in the vSphere Web Client

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
ch1ta
Hot Shot
Hot Shot

And if vMotion can’t be used for whatever reason, you can always stick to free migration tools, such as Veeam Quick Migration or similar. Using those, you can migrate VMs between hosts, datastores or both with minimal downtime.

Cheers.

0 Kudos