VMware ESXi 5 - Behavior when VM OS gets corrupted

Hi,

I have a question on how the VMware will behave on this scenario:

I have one VM that can run in two diferent hosts. - HA running

Lets say the OS of the VM gets corrupted and the VM crahses, so it will failover to the other host, but since the OS is corrupted, it will fail to start on the other host as well right?

How would VMware behave? Is there anything to be done to prevent this?

Tks,
Joao
joaotellesAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
If the VM OS gets corrupted it's corrupted.

VMware will start the VM, but if the VM OS is corrupted, the OS will not BOOT or function.

No, there is nothing that can be done to prevent this, VMware does not prevent VM (Operating Systems from getting corrupted).

Ensure you have Good Backups for restore.

We've been working with VMware technologies for many years, and we've not seen many VMs get corrupted, unless your datastore (RAID array breaks!)
0
 
jhyieslaCommented:
No, if the guest VM OS fails, it fails; period. It will not fail over assuming that the reason for the failure was NOT the host having difficulty.

There are several things you can do to help avoid this scenario though.  There is a Fault Tolerant option that is available, though there are some caveats with using it. If this is a critical VM, you could create a clone of it and just have it sitting there. The "best" option is to have a good backup of each VM in your environment. Look at something like VEEAM as a viable backup.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you are using VMware FT which mirrors the OS, the secondary copy will also be FAULTY!

because all changes committed in the Primary VM, are SYNC LOCKED and MIRROED to the secondary VM.

VMware FT is not going to help with a Corrupted OS.

e.g. you patch VM1 which is in FT with VM2, the patch causes VM1 to Blue Screen, VM2 will also Blue Screen!

To Avoid or Risk Against Corruption

1. Use a UPS
2. Use a good Storage Controller
3. Use RAID 10,6 or 5.
4. Take regularly Backups.
0
 
jhyieslaCommented:
Sorry...you're right about FT :)
0
 
compdigit44Commented:
If you have a Vm that runs a mission critical app, and you need a way to recover the VM/OS, you could create a powershell script to take a snapshot everyday then create  another script to remove the previous days snapshot. This will allow you to recover the VM very fast if need by and still be able to use HA to protect again host hardware failure.
0
 
joaotellesAuthor Commented:
tks
0
All Courses

From novice to tech pro — start learning today.