Reservation and shares are important resource management settings in a vSphere DRS cluster. They can be set on cluster objects like VMs and resource pools to isolate resources, prioritize, and/or guarantee their availability.
To know when to set them for VMs and when to set them on resource pools, we need to understand:
What these settings mean.
How these settings can impact resource availability for a VM.
In this paper, VMware explains how these settings are different for a VM and resource pool while giving some general guidelines for using them.
Today VMware has released vSAN 6.6 to the public! 6.6 is a big step forward. While the base architecture of vSAN stays the same, it becomes more and more efficient. With the price of flash going down, it’s an even more compelling reason to look into HCI these days.
One of my favorite use cases for vSAN is with VMware Horizon Advanced/Enterprise editions. To me, it’s a no brainer. Simple, elastic scalability, much higher performance over traditional tiered storage and lower TCO. Not long ago storage in VDI environments would have given most of us nightmares.
Unicast – In vSAN 6.6, cluster communication has been redesigned to use unicast traffic. Multicast is no longer required on the physical switches to support the vSAN cluster.
Enhanced Stretched Clusters with Local Failure Protection – Previously, vSAN was able to provide a fully active-active, stretched cluster. vSAN 6.6 takes this a step further, allowing for storage redundancy within a site AND across sites at the same time.
Encryption – vSAN supports data-at-rest encryption of the vSAN datastore. When encryption is enabled, vSAN performs a rolling reformat of every disk group in the cluster.
Site Affinity for Stretched Clusters – A new feature for vSAN 6.6 Stretched Clusters is the ability to configure site affinity.
Configuration Assist and Updates – New Configuration Assist and Updates pages allows to check the configuration of your vSAN cluster, and resolve any issues.
Resynchronization throttling – IOPS used for cluster resynchronization can be throttled to prevent performance bottlenecks.
vSAN Health Command Line Tool – A new esxcli command allows to check vSAN health from the command line (esxcli vsan health).
Degraded Device Handling – vSAN 6.6 provides a more proactively stable environment with the detection of degraded and failing devices.
Altaro is a great blog sponsor of mine and reached out to me recently to see if there was interest in doing a separate project with them. A vSphere troubleshooting webinar. I’ve compiled a list of some of the most popular scenarios and put them together in an eBook. We’ll be discussing them April 25th! You can register at the link below.
Troubleshooting complex virtualization technology is something that system administrators have to face at some point, and it’s not always an easy fix to get things up and running again. We’re running a webinar that will cover the most common problems experiences in VMware vSphere. Register for the webinar here.
Andy Syrewcize and Ryan Birk will bring a wealth of experience in troubleshooting some of the most common issues admins face. Andy has spent the last 12 years providing technology solutions across a variety of industries, and has experience in troubleshooting VMware infrastructures for education, manufacturing, healthcare and other industries. Ryan is a VMware vExpert, and a VMware certified trainer, having consulted and engineered infrastructures for a variety of companies.
Here’s what you’ll learn:
Troubleshooting some of the most common vSphere problems
Quick and efficient issue fixing practices
Maintaining a smooth running vSphere environment to avoid future issues
Date: Tuesday April 25th, 2017 Time: For US registrants: 10am PDT/1pm EDT, for RoW registrants: 2pm CET
PS: We’re releasing an eBook by Ryan on the same topic soon as well. By registering for the webinar you will get early access automatically!
Before you begin it is important to realize that vSAN is a software based storage product that is entirely dependent on the proper functioning underlying hardware components, like network, storage I/O controller and the individual storage devices. You always need to follow the vSAN Compatibility Guide for all deployments. I often play with things in my homelab, just because you CAN do it, doesn’t mean it’s supported by VMware. 🙂
I’ve recently been playing with stretched clusters in my homelab and have finally had to fix some of the stuff I’ve been playing with. The beauty of the homelab, is I can break anything I want! I had not worked with the Ruby Console at all but it’s an amazing tool to check out.
Many vSAN errors can be traced back to faulty VMkernel ports, mismatched MTU sizes, etc. It’s far more than simple TCP/IP.
Some of the tools you can use to troubleshoot vSAN are:
vSphere Web Client
The primary tool to troubleshoot vSAN.
Provides overviews of individual virtual machine performance.
Can inspect underlying disk devices and how they are being used by vSAN.
With the rise in popularity of hybrid cloud computing, where VM-sensitive data leaves the traditional IT environment and traverses over the public networks, IT administrators and architects need a simple and secure way to protect critical VM data that traverses across clouds and over long distances.
The Encrypted vMotion feature available in VMware vSphere 6.5 addresses this challenge by introducing a software approach that provides end-to-end encryption for vMotion network traffic. The feature encrypts all the vMotion data inside the vmkernel by using the most widely used AES-GCM encryption standards, and thereby provides data confidentiality, integrity, and authenticity even if vMotion traffic traverses untrusted network links.