
vSAN Datastores
Learner Objectives
After completing this lesson, you should be able to meet the following objectives:
- Explain the purpose of a vSAN datastore
- Describe the architecture and requirements of vSAN configuration
- Explain the purpose of vSAN storage policies
About vSAN Datastores
vSAN is a software-defined storage solution providing shared storage for vSphere clusters without using traditional external storage. A vSAN cluster requires:
- A minimum of three hosts to be part of the vSphere cluster and enabled for vSAN
- A vSAN network
- Local disks on each host that are pooled to create a virtual shared vSAN datastore
Disk Groups
Disk groups are vSAN management constructs on all ESXi hosts in a vSAN cluster. A host can include a maximum of five disk groups.
The disk groups are combined to create a single vSAN datastore.
A disk group requires:
- One flash device for caching
- One to seven capacity devices for storage
vSAN Hardware Requirements
vSAN capabilities are native to ESXi and require no additional software.
Viewing the vSAN Datastore Summary
The Summary tab of the vSAN datastore shows the general vSAN configuration information.
Objects in vSAN Datastores
vSAN storage is object-based and policy-driven.
vSAN Object | Traditional VM Files |
VM home namespace | .nvram, .vmsd, .vmx, vmx-*.vswp, .log, .hlog |
VMDK | -flat.vmdk |
VM swap | .vswp |
VM memory | .vmem |
Snapshot delta | -00000#-delta.vmdk, -00000#-sesparse.vmdk |
VMs created on a vSAN datastore include the following objects:
- One VM home namespace
- One or more VMDK objects
- Thin-provisioned VM swap object
- One or more VM memory objects
- vSAN performance data objects
- iSCSI LUN objects
VM Storage Policies
Storage policies define how objects that are included in a VM are stored. Storage policies have the following characteristics:
- Based on storage capabilities
- Defined for a VM or disk at the time of deployment
- Can be applied later
- Can be changed at any time
- Cannot be deleted if they are in use
Viewing VM Settings for vSAN Information
The consumption of vSAN storage is based on the VM’s storage policy. The VM’s hard disk view provides the following information:
- A display of the VM storage policy
- The location of disk files on a vSAN datastore
Review of Learner Objectives
After completing this vSAN Datastores lesson, you should be able to meet the following objectives:
- Explain the purpose of a vSAN datastore
- Describe the architecture and requirements of vSAN configuration
- Explain the purpose of vSAN storage policies
Virtual Beans: Storage
As a Virtual Beans administrator, you are planning how to use NAS and iSCSI storage with vSphere:
- For NAS storage, you can create one or more NFS datastores and share them across ESXi hosts:
- Use the datastores to hold templates, VMs, and vCenter Server Appliance backups.
- For iSCSI storage, you can create one or more iSCSI datastores and share them across ESXi hosts:
- Use the datastores to hold templates and VMs.
What are the benefits to Virtual Beans of using vSAN storage? Benefits include (but are not limited to):
- You can use the vSphere Client to manage the vSAN configuration. No separate user interface is necessary.
- vSphere administrators do not need special storage hardware training.
- You can use vSAN storage policies to define specific levels of service for a VM.
- You can expand the vSAN capacity by adding one or more hosts to the vSAN cluster (also known as scale out).
Key Points
- ESXi hosts support various storage technologies: Direct-attached storage, Fibre Channel, FCoE, iSCSI, and NAS.
- You use VMFS and NFS datastores to hold VM files.
- Shared storage is integral to vSphere features such as vSphere vMotion, vSphere HA, and vSphere DRS.
- vSAN clusters direct-attached server disks to create shared storage designed for VMs.