Great explanation indeed. When HA is enabled while vSAN is disabled, it uses management network for heartbeat. However as per my understanding it needs shared storage to function correctly. So in that case for HA to work there should be some kind of shared storage configured if not vSAN right?
Yes. If you are using vSAN Enable vSAN first, then HA.. HA will use the vSAN network as the agent Heart Best network.. Thanks for watching and have a great day
While I generally stay away from licensing, because sometimes it changes so often. This blog may help you out.. www.nakivo.com/blog/a-guide-to-vmware-vsphere-editions-and-licensing-which-one-do-you-need/ Keep in mind, When Broadcom aqired VMware, they changed the licensing to a subscription model.. I hope they change it back.. Thanks for watching. have a good one.
Hello Steve: I was wondering what is the best approach, in a VMware HA environment, to apply a Microsoft Windows Update or an application software upgrade with minimal loss of services?
Ok Nothing really to do with vSPhere HA. The down time will depend on the patch it self. Does it require a reboot? How long will it take to install and so one.. General rule of thumb before applying patches / updates is to take a full backup of the VM and before applying the patch take a snapshot of the VM. With the snap shot you can always roll back if things don;t work out.. You could always test the patch prior to applying it, by making a copy of the VM and put it on an isolated network for testing. Hope this help and have a great day
@@TechUnGlued Thanks Steve. So, I am guessing when applying a patch, one has to assume (and be prepared) for an implied "short" downtime? The restart would also be needed for those updates having such requirements. I know that VMware HA running on multi-nodes would share the same image of the VM on the active node to restart in one of the passive node(s) if the active node fails. So, would I be correct in assuming the following procedure?: 1. Take a clone of the VM, apply the update and test it on an isolated network to ensure that the patch itself works 2. Take a snapshot of the live active node, to be used for recovery if something goes wrong. 3. Apply the update on the active node. Restart the VM if needed. 4. Revert using the snapshot if the update installation did not go well.
All you points are valid. I am not sure what you are referring to here when you say. " I know that VMware HA running on multi-nodes would share the same image of the VM on the active node to restart in one of the passive node(s) if the active node fails" Are you referring to vSphere Fault Tolerance? Thanks again for watching and have a great day
@@TechUnGlued I might have used the wrong terminology. I was referring to the VMware running in HA mode, across multiple nodes. Unlike in a Microsoft Windows Cluster, where the VM on each node is a distinct image/executable, my understanding is that VMware, uses the only one image and switches the node, when a hardware failure is detected. Did I misunderstand how VMware HA works?
Yes. With vSphere HA one ESXi will have the lock on the files that make up the VM (the image), when that ESXi host fails another host int he cluster will obtain the lock and run the VM.. Hope this helps.
We are grateful Steve. This is how you demystify the complexities of VMware. Thankyou very much.
My pleasure. You have a great day
Your way of explanation is really good and easy. Request to update more videos related to Troubleshooting of all the Vmware components. Thanks.
Sure I will. working on a few things now. Have a great day
Thank you so much! I read a lot of the Vmware docs on HA but actually having you go through all the options and talking about them helped way more!
Glad I could help! You have a good one.
Easy way to learn and understand the complex topics......thank you.
Glad it was helpful! You have a great day
This one and the DRS video really cleared up a lot of questions I had. Thank you!
Thanks. You have a great day
Excellent presentation, as usual. @27:48 The vSAN Datastore is not used to store the heartbeat lock file.
Thanks for watching. Yes you are correct. I did not see me mention that at that time stamp. Have a great day..
I would love to see another video outlining redundancy techniques in greater detail.
Are you referring to doing stuff like RAID1, RAID5, redundant power supplies and Fans?? Let me know. Thanks again and have a great day
Great explanation indeed. When HA is enabled while vSAN is disabled, it uses management network for heartbeat. However as per my understanding it needs shared storage to function correctly. So in that case for HA to work there should be some kind of shared storage configured if not vSAN right?
Yes. If you are using vSAN Enable vSAN first, then HA.. HA will use the vSAN network as the agent Heart Best network.. Thanks for watching and have a great day
Congrats on getting over 1000 subscribers!
Thank you so much 😀 You have a good one. Next Target 10,000 :)
Great work Steve - thank you
Very welcome. Thanks for watching and have a good one
Have you considered doing a deep dive on licensing VMware's features and software? I would greatly appreciate your expertise!
While I generally stay away from licensing, because sometimes it changes so often. This blog may help you out..
www.nakivo.com/blog/a-guide-to-vmware-vsphere-editions-and-licensing-which-one-do-you-need/
Keep in mind, When Broadcom aqired VMware, they changed the licensing to a subscription model.. I hope they change it back..
Thanks for watching. have a good one.
Hello Steve: I was wondering what is the best approach, in a VMware HA environment, to apply a Microsoft Windows Update or an application software upgrade with minimal loss of services?
Ok Nothing really to do with vSPhere HA. The down time will depend on the patch it self. Does it require a reboot? How long will it take to install and so one.. General rule of thumb before applying patches / updates is to take a full backup of the VM and before applying the patch take a snapshot of the VM. With the snap shot you can always roll back if things don;t work out.. You could always test the patch prior to applying it, by making a copy of the VM and put it on an isolated network for testing. Hope this help and have a great day
@@TechUnGlued Thanks Steve. So, I am guessing when applying a patch, one has to assume (and be prepared) for an implied "short" downtime? The restart would also be needed for those updates having such requirements. I know that VMware HA running on multi-nodes would share the same image of the VM on the active node to restart in one of the passive node(s) if the active node fails. So, would I be correct in assuming the following procedure?:
1. Take a clone of the VM, apply the update and test it on an isolated network to ensure that the patch itself works
2. Take a snapshot of the live active node, to be used for recovery if something goes wrong.
3. Apply the update on the active node. Restart the VM if needed.
4. Revert using the snapshot if the update installation did not go well.
All you points are valid. I am not sure what you are referring to here when you say.
" I know that VMware HA running on multi-nodes would share the same image of the VM on the active node to restart in one of the passive node(s) if the active node fails" Are you referring to vSphere Fault Tolerance? Thanks again for watching and have a great day
@@TechUnGlued I might have used the wrong terminology. I was referring to the VMware running in HA mode, across multiple nodes. Unlike in a Microsoft Windows Cluster, where the VM on each node is a distinct image/executable, my understanding is that VMware, uses the only one image and switches the node, when a hardware failure is detected. Did I misunderstand how VMware HA works?
Yes. With vSphere HA one ESXi will have the lock on the files that make up the VM (the image), when that ESXi host fails another host int he cluster will obtain the lock and run the VM.. Hope this helps.
You’re the man!
Thanks for the kind comment. You have a great day.