In a stretched vSAN cluster, how is Read Locality established after fail over to the secondary site?
In the event of a failure or maintenance event, the virtual machine is restarted on the remote site. The 100% rule continues in the event of a failure. This means that the virtual machine will now read from the replica on the site to which it has failed over. One consideration is that there is no cached data on this site, so cache will need to warm for the virtual machine to achieve its previous levels of performance.
Currently there are no comments in this discussion, be the first to comment!