What more do I need to say? vSphere 6.0 U1 was released today and it ships with Virtual SAN 6.1. By now you’ve all seen my posts on what’s new for VSAN 6.1 and you’ve hopefully seen the demo we created for stretched clustering. If you want to play with 6.1 yourself then you can find it here:
If you are in a stretched cluster configuration and want to vMotion a guest to another site, how do you ensure Read locality at that site(fault domain) afterwards?
“read locality” follows the “fault domain” it is in. Do note that the cache will need to be rewarded unfortunately at that point.
Thank you. We were looking into some Array stretched cluster solutions before 6.1 came out. We are now interested in this solution.
I have a 3 hosts cluster with vsan 6.0 but to version have a known problem with dual lsi3008 controllers per hosts.
With vsan 6.1 this issue is fixed.
My questions are: is 6.1 ready for a production environment? Is the upgrade safe if I have all in hcl? What’s the best practice for the safest upgrade? Is it better to move all VMs of the cluster outside VSAN datastore, upgrade and after that return them on datastore or is it useless?
Many thanks
Yes you are okay to upgrade, I would recommend in place upgrade as well in a rolling fashion. No need to move the data off when upgrading. In all my tests the upgrade process worked flawlessly!