Hey vSAN fans, are you excited for the new vSAN 6.7 Update 1 release? We are! In fact, we love the new updates so much that we hosted a special Twitter #vSANchat event on Wednesday, October 24, so that we could ask questions, get answers, and talk about our favorite updates. We were joined by our vSAN experts, Jase McCarty, Myles Gray, and Pete Flecha who shared their unique insight as well as important resources. If you missed the action, then this wrap-up is for you.
Read below for the top resources and takeaways!
- Start with Tom Nagelmeyer’s blog announcement vSAN 6.7 Update 1 Is Now Generally Available to learn about the capabilities and features in Update 1.
- The blog What’s New in vSAN 6.7 Update 1 is your new vSAN Bible. Have a question about Cluster Quickstart? Jase McCarty answers it here. Want to know more about Capacity Reporting? We have you covered.
- Special guest Pete Koehler and the vSpeaking Podcast walk through the new features in vSAN 6.7. Give it a listen: vSpeaking Podcast Episode 90: What’s New in vSAN 6.7 U1.
- Take a close look at vSAN Maintenance Mode with Pete Flecha’s blog.
- Dive into TRIM/UNMAP with our blog VMware vSAN 6.7U1 Storage reclamation – TRIM/UNMAP.
- Dive even deeper with UNMAP/TRIM Space Reclamation on vSAN on Storage Hub.
vSAN 6.7 U1 #vSANchat Q&A
Q: I am in the process of upgrading to vSAN 6.7. What can I expect from the U1 update?
A: Check out the announcement updates, vSAN 6.7 Update 1 Is Now Generally Available, as well as the Virtual Speaking Podcast, vSpeaking Podcast Episode 90: What’s New in vSAN 6.7 U1. Check out the following tweets for a look at what our experts had to say!
Q: How does the new Cluster Quickstart wizard improve vSAN deployment & cluster expansion?
A: Jase McCarty swooped in with an answer highlighting the top features.
Q: How do I enable/configure guest operating systems for TRIM/UNMAP with vSAN 6.7 U1?
A: TRIM/UNMAP allows for space reclamation when files are deleted from the guest OS. VMware vSAN 6.7 U1 has introduced automated space reclamation support with TRIM and SCI UNMAP support. The experts divulge that this is a cluster-wide setting. The feature can be enabled or disabled via RVC command.
This is a cluster wide setting. The feature can be enabled or disabled via RVC command “vsan.unmap_support –enable or –disable”. See what our vExpert John Nicolson has to say on the topic in his blog post VMware vSAN 6.7U1 Storage reclamation – TRIM/UNMAP.
Q: Can you explain vSAN Private Beta?
A: There are some pretty awesome betas out at the moment, according to the experts. Take advantage of an inside look at the updates to data protection, file services, and cloud native storage. The File Services are going to be an outstanding enhancement to vSAN. Sign up here and here.
Q: How has capacity reporting improved in this update?
A: As Jase McCarty explained, you can determine free usable capacity based on policy, capacity needed if DD+C is disabled, and even historical capacity in vSAN 6.7 U1. The vSAN Capacity Overview quickly and easily shows the amount of capacity being consumed on a vSAN datastore.
In vSAN 6.7 U1, administrators now have the ability to estimate the amount of usable capacity based on a desired storage policy. Also new in vSAN 6.7 U1, administrators can see the Capacity History of the vSAN Cluster over time. Historical metrics such as changes in capacity used/free and deduplication ratios, can provide administrators better understanding of how changes in the environment impact storage consumption. and smarter decision making. Learn more on Storage Hub.
Q: What can we expect in the next update?
A: Stay tuned for the next announcement! 😉
Thank you to all who joined us during the hour! If you didn’t get your question answered, please continue to conversation on Twitter! Really, ask us anything! Follow us @VMwarevSAN.
See you at our next #vSANchat!