Where did my FTT go?


VMware has launched the latest generation of vSphere and VSAN and this comes with a nice list of new features and options for VSAN6.7. From this list I will highlight something new for the HTML5 client.
  • 4Kn drive support.
  • vSphere and vSAN FIPS 140-2 validation.
  • HTML5 interface.
  • vRealize Operations within vCenter Server.
  • Windows Server Failover Clustering support.
  • Intelligent site continuity for stretched clusters.
  • Witness traffic separation for stretched clusters.
  • Efficient inter-site resync for stretched clusters.
  • Fast failovers when using redundant vSAN networks.
  • Adaptive resync for dynamic management of resynchronization traffic.
  • Consolidation of replica components.
  • vSAN destaging optimizations.
  • Health check additions and improvements.
  • vSAN Support insight.
  • Swap object thin provisioning and policy inheritance improvements.

Where did my FTT go?

In the lastest edition of vSphere / VSAN and the HTML 5 client,  VMware has changed some of the terminology.  For example, the feature called Failure to Tolerate which came in two different flavors, a Primary (PFTT) and a Secondary (SFTT) has disappeared. Likewise, the Failures to Tolerate Method (FTM – RAID 1/5-6) has disappeared as well. What happened to them? Well, I believe we moved to a better understandable flow of defining policies. To illustrate this I have made a small video where I compare the Flex client to the HTML 5 client, using the latest vSphere and VSAN 6.7 code.


Be the first to comment

Leave a Reply

Your email address will not be published.


*


This site uses Akismet to reduce spam. Learn how your comment data is processed.