Good
asked on
host migration
hi team,
Scenario like this:
we have Vsphere 5.5 with multiple clusters, the cluster have multiple hosts, which is anyway common.
recently HP released a bug on few generation of Proliant server, http://kb.vmware.com/kb/2085618, this bug is not allowing migration, vmotion with the affected hosts, and unfortunately our clusters are with these affected physical machines.
New we wanted to patch these physical hosts, with very minimal impact to VM.
Problems:
So we thought we migrate VM to next host, and patch the server, and move back, but unfortunately cannot migrate the VMs to different host due to this bug. All the hosts in the cluster are same type of hardware, and all the hosts had same issue its not allowing migration.
So i need your advice to fix this issue with minimal impact.
Scenario like this:
we have Vsphere 5.5 with multiple clusters, the cluster have multiple hosts, which is anyway common.
recently HP released a bug on few generation of Proliant server, http://kb.vmware.com/kb/2085618, this bug is not allowing migration, vmotion with the affected hosts, and unfortunately our clusters are with these affected physical machines.
New we wanted to patch these physical hosts, with very minimal impact to VM.
Problems:
So we thought we migrate VM to next host, and patch the server, and move back, but unfortunately cannot migrate the VMs to different host due to this bug. All the hosts in the cluster are same type of hardware, and all the hosts had same issue its not allowing migration.
So i need your advice to fix this issue with minimal impact.
If you cannot patch the host, because of VMs issues, you will need to schedule VM downtime, and then either
1, Shutdown VM
2. Migrate VM (cold, when OFF)
3. Patch Host
4. Reboot
Patching does not take long, 15 minutes including reboot, so downtime for VMs 15-30 minutes, out of core hours.
I would not bother moving or migrating VMs.
1, Shutdown VM
2. Migrate VM (cold, when OFF)
3. Patch Host
4. Reboot
Patching does not take long, 15 minutes including reboot, so downtime for VMs 15-30 minutes, out of core hours.
I would not bother moving or migrating VMs.
ASKER
can we do live migration the VM on to different host of different cluster? so that VM downtime will be zero.
what is difference b/w moving and migrating?
what is difference b/w moving and migrating?
I didn't think you could do any vMotions e.g. Migrate when VM is ON, e.g. Live Migration?
Move/Migration when the VM is OFF, is not a vMotion.
Move/Migration when the VM is OFF, is not a vMotion.
ASKER
we have take the downtime, i guess we dont have option to migrate
if you right click the VM in vCenter Server, do you have a MIgrate option?
Are you using shared storage?
Are you using shared storage?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
my quick is asking for minimal downtime, and ppl are talking about process and steps to migrate and patch, nobody really understanding the downtime criteria
HP ProLiant Gen8 Servers – ESXi 5: The /var/log/hpHelper.log File Can Grow Very Large and Fill the ESXi 5 RAMDisk
VMware KB – RAM disk is full (2001550)