If using Fault Tolerance the virtual disk for the VM needs to be FT enabled, i.e. eager zeroed. I am wondering what the reason for this is?
Would it be that the FT enabled VM needs that little bit higher disk IO or is it any other reason?
Hello.
If using Fault Tolerance the virtual disk for the VM needs to be FT enabled, i.e. eager zeroed. I am wondering what the reason for this is?
Would it be that the FT enabled VM needs that little bit higher disk IO or is it any other reason?
Eager zeroed disks are simply the best performing disk type, as there is no overhead for writes.
Good Luck!
So there is just the extra performance of the eager-disk that is interesting, no other technical issue?
As far as I know, the performance factor is it.
>Eager zeroed disks are simply the best performing disk type, as there is no overhead for writes.
To be more exact: there is no overhead for writes from the very beginning, but situation is absolutely the same for "thick" disks, without zeroing. So we can add here "security" reason.
---
MCITP: SA, MCTS Hyper-V, VCP 3/4, VMware vExpert
Thanks for your answers. I was just curious since it is a requierment for using FT.
Eagered Zeroed thick disks are needed because if they are thin or thick, there will be a lot of logging data to be send from primary to secondary VM. So to avoid the logging link from getting saturared, we commit the entire provisioned space and zero it. This is for performance reasons.
Eagered Zeroed thick disks are needed because if they are thin or thick, there will be a lot of logging data to be send from primary to secondary VM. So to avoid the logging link from getting saturared, we commit the entire provisioned space and zero it.
Why would the zeroing be sent over the FT logging network? Is not the zeroing done by the vmkernel and the guest OS does not know it? Is that kind of low level "behind-the-scenes" commands sent over the FT network?