
上QQ阅读APP看书,第一时间看更新
Objective 3.2 – Configure software-defined storage
With a traditional storage, vSphere can abstract the underlying storage capacities from virtual machines. But with a software-defined storage (SDS), vSphere can also abstract storage capabilities and provide part of storage manageability and automation.
VMware provides two different approaches for an SDS approach with vSphere:
- Virtual SAN (vSAN): Implements a hyper-converged and SDS solution based on VMware software. Note that vSAN requires an additional license and has several editions. These features depend on the vSAN version and editions, and some of them are limited to the all-flash configuration only.
- Virtual volumes (vVOLs): Integrates existing external storage and have the SDS flexibility. To use vVOLs, you need a certified storage with vVOLs support and at least the ESXi standard edition:

Figure 3.15: VMware software-defined storage
With the SDS model, a virtual machine becomes a unit of storage provisioning and can be managed through a flexible policy-based mechanism using SPBM.
SPBM is a framework that provides a single control panel across various data services and storage solutions, including VMware vSAN and vVOLs.
Objective 3.2 for VCP65-DCV and VCP6-DCV is quite similar, both for the vSAN (also if vSAN 6.5 and 6.6 have more functions compared to vSAN 6.0) and vVOLs.
The topics covered in this objective are huge and covered in specific courses (at least for vSAN). Also, they are not fully necessary for the exam; you can understand just the basics and maybe learn more or make more practice later.
The topics covered in this objective are huge and covered in specific courses (at least for vSAN). Also, they are not fully necessary for the exam; you can understand just the basics and maybe learn more or make more practice later.
For more information and details, see the vSphere 6.5 Storage guide and the administering VMware vSAN 6.5 guide: