In this post we will continue covering the storage objective from the blueprint.
In the previous post we setup our vSAN storage and now we will disucss the following:
- Collect vSAN Observer output
- Explain vSAN failure domains functionality
- Enable/Disable Virtual SAN Fault Domains
- Configure Storage Policies
- Explain VVOL architectural components
- Determine the role of storage providers in VVOLs
- Create/Modify VMware Virtual Volumes (VVOLs)
Virtual SAN Observer:
The VMware vSAN Observer is a Web-based tool that runs on RVC(Ruby vSphere Console) and is used for in-depth performance analysis and monitoring of the vSAN cluster. To Collect vSAN Observer output please refer to this KB: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2064240
Explain VSAN failure domains functionality and Enable/Disable Virtual SAN Fault Domains:
vSAN supports fault domains to protect hosts from rack or chassis failure when the vSAN cluster spans across multiple racks.You can also use fault domains to improve failure management.You must define at least three fault domains, each of which might consist of one or more hosts. vSAN applies the active virtual machine storage policy against the fault domains instead of against the individual hosts.
Calculate the number of fault domains in a cluster based on the number of failures to tolerate attribute from the storage policies that you plan to assign to virtual machines.
number of fault domains = 2 * number of failures to tolerate + 1
Management of fault domains can be done under the vSAN configuration (i cant really demo it in my lab)
Configure Storage Policies:
- With vSAN you can use policies to define vm’s storage requirements
- When you assign storage policy the policy is pushed down to the vm’s
- When creating vSAN cluster it creates vSAN datastore (as we seen in the previous post) and that datastore has default storage policies
- Virtual SAN requires that the virtual machines deployed on the Virtual SAN datastores are assigned at least one storage policy.
- Like other storage vendors vSAN has “Storage Providers” (storage providers are built-in software components that communicate datastore capabilities to vCenter Server.)
- Virtual SAN registers a separate storage provider for each host in the Virtual SAN cluster.
- You can also use tags to create user-defined storage capabilities and reference them when defining a storage policy for a virtual machine.
You can apply these storage policies when you create or edit virtual machines:
- Number of disk stripes per object – The number of capacity devices across which each replica of a virtual machine object is striped
- Flash read cache reservation – Flash capacity reserved as read cache for the virtual machine object.
- Number of failures to tolerate – Defines the number of host and device failures a virtual machine object can tolerate.
- Force provisioning – If the option is set to Yes, the object will be provisioned even if the policy specified in the storage policy is not satisfiable by the datastore.
- Object space reservation – Percentage of the logical size of the virtual machine disk (vmdk) object that should be reserved, or thick provisioned when deploying virtual machines.
Creating New Storage Policy:
From Vcenter home >> VM Storage Policies >> Create New VM Storage Policy
Choose Rules based on data service VSAN
After you created the rule you can check for compliance
Explain VVOL components
Short brief from the vSphere Storage document: (There is a lot to read)
Virtual volumes – Virtual volumes are encapsulations of virtual machine files, virtual disks, and their derivatives. .
Virtual Volumes and Storage Providers – A Virtual Volumes storage provider, also called a VASA provider, is a software component that acts as a storage awareness service for vSphere. The storage provider is implemented through VMware APIs for Storage Awareness (VASA) and is used to manage all aspects of Virtual Volumes storage.
Storage Containers – Virtual Volumes functionality does not require preconfigured volumes on a storage side. Instead, Virtual Volumes uses a storage container, which is a pool of raw storage capacity or an aggregation of storage capabilities that a storage system can provide to virtual volumes.
Protocol Endpoints – ESXi hosts have no direct access to virtual volumes on the storage side. Instead, ESXi hosts use a logical I/O proxy, called the protocol endpoint, to communicate with virtual volumes and virtual disk files that virtual volumes encapsulate. ESXi uses protocol endpoints to establish a data path on demand from virtual machines to their respective virtual volumes.
Virtual Datastores – A virtual datastore represents a storage container in vCenter Server and the vSphere Web Client.
Determine the role of storage providers in VVOLs
The storage provider delivers information from the underlying storage, or storage container in the case of Virtual Volumes, so that storage container capabilities can appear in vCenter Server and the vSphere Web Client. Then, in turn, the storage provider communicates virtual machine storage requirements, which you can define in the form of a storage policy, to the storage layer.
Create/Modify VMware Virtual Volumes (VVOLs)
To create and modify VVOLs we will need to do the followings:
- Configure Storage provider
- Configure Protocol endpoint
- Create new datastore with VVOL option
Since i am using a home lab i do not have a storage system that support VVOL’s .
Thanks for reading