6.0.1
Table Of Contents
- vSphere Storage
- Contents
- About vSphere Storage
- Updated Information
- Introduction to Storage
- Overview of Using ESXi with a SAN
- Using ESXi with Fibre Channel SAN
- Configuring Fibre Channel Storage
- Configuring Fibre Channel over Ethernet
- Booting ESXi from Fibre Channel SAN
- Booting ESXi with Software FCoE
- Best Practices for Fibre Channel Storage
- Using ESXi with iSCSI SAN
- Configuring iSCSI Adapters and Storage
- ESXi iSCSI SAN Requirements
- ESXi iSCSI SAN Restrictions
- Setting LUN Allocations for iSCSI
- Network Configuration and Authentication
- Set Up Independent Hardware iSCSI Adapters
- About Dependent Hardware iSCSI Adapters
- Dependent Hardware iSCSI Considerations
- Configure Dependent Hardware iSCSI Adapters
- About the Software iSCSI Adapter
- Modify General Properties for iSCSI Adapters
- Setting Up iSCSI Network
- Using Jumbo Frames with iSCSI
- Configuring Discovery Addresses for iSCSI Adapters
- Configuring CHAP Parameters for iSCSI Adapters
- Configuring Advanced Parameters for iSCSI
- iSCSI Session Management
- Booting from iSCSI SAN
- Best Practices for iSCSI Storage
- Managing Storage Devices
- Storage Device Characteristics
- Understanding Storage Device Naming
- Storage Refresh and Rescan Operations
- Identifying Device Connectivity Problems
- Edit Configuration File Parameters
- Enable or Disable the Locator LED on Storage Devices
- Working with Flash Devices
- About VMware vSphere Flash Read Cache
- Working with Datastores
- Understanding VMFS Datastores
- Understanding Network File System Datastores
- Creating Datastores
- Managing Duplicate VMFS Datastores
- Upgrading VMFS Datastores
- Increasing VMFS Datastore Capacity
- Administrative Operations for Datastores
- Set Up Dynamic Disk Mirroring
- Collecting Diagnostic Information for ESXi Hosts on a Storage Device
- Checking Metadata Consistency with VOMA
- Configuring VMFS Pointer Block Cache
- Understanding Multipathing and Failover
- Raw Device Mapping
- Working with Virtual Volumes
- Virtual Machine Storage Policies
- Upgrading Legacy Storage Profiles
- Understanding Virtual Machine Storage Policies
- Working with Virtual Machine Storage Policies
- Creating and Managing VM Storage Policies
- Storage Policies and Virtual Machines
- Default Storage Policies
- Assign Storage Policies to Virtual Machines
- Change Storage Policy Assignment for Virtual Machine Files and Disks
- Monitor Storage Compliance for Virtual Machines
- Check Compliance for a VM Storage Policy
- Find Compatible Storage Resource for Noncompliant Virtual Machine
- Reapply Virtual Machine Storage Policy
- Filtering Virtual Machine I/O
- VMkernel and Storage
- Storage Hardware Acceleration
- Hardware Acceleration Benefits
- Hardware Acceleration Requirements
- Hardware Acceleration Support Status
- Hardware Acceleration for Block Storage Devices
- Hardware Acceleration on NAS Devices
- Hardware Acceleration Considerations
- Storage Thick and Thin Provisioning
- Using Storage Providers
- Using vmkfstools
- vmkfstools Command Syntax
- vmkfstools Options
- -v Suboption
- File System Options
- Virtual Disk Options
- Supported Disk Formats
- Creating a Virtual Disk
- Example for Creating a Virtual Disk
- Initializing a Virtual Disk
- Inflating a Thin Virtual Disk
- Removing Zeroed Blocks
- Converting a Zeroedthick Virtual Disk to an Eagerzeroedthick Disk
- Deleting a Virtual Disk
- Renaming a Virtual Disk
- Cloning or Converting a Virtual Disk or RDM
- Example for Cloning or Converting a Virtual Disk
- Migrate Virtual Machines Between DifferentVMware Products
- Extending a Virtual Disk
- Upgrading Virtual Disks
- Creating a Virtual Compatibility Mode Raw Device Mapping
- Example for Creating a Virtual Compatibility Mode RDM
- Creating a Physical Compatibility Mode Raw Device Mapping
- Listing Attributes of an RDM
- Displaying Virtual Disk Geometry
- Checking and Repairing Virtual Disks
- Checking Disk Chain for Consistency
- Storage Device Options
- Index
Virtual Volumes Concepts
With Virtual Volumes, abstract storage containers replace traditional storage volumes based on LUNs or
NFS shares. In vCenter Server, the storage containers are represented by virtual datastores. Virtual
datastores remove articial boundaries of traditional datastores and are used to store virtual volumes,
objects that encapsulate virtual machine les.
Watch the video to learn more about dierent components of the Virtual Volumes functionality.
Virtual Volumes Part 1: Concepts
(hp://link.brightcove.com/services/player/bcpid2296383276001?
bctid=ref:video_vvols_part1_concepts)
n
Virtual Volumes on page 214
Virtual volumes are encapsulations of virtual machine les, virtual disks, and their derivatives.
n
Virtual Volumes and Storage Providers on page 215
A Virtual Volumes storage provider, also called a VASA provider, is a software component that acts as
a storage awareness service for vSphere. The provider mediates out-of-band communication between
vCenter Server and ESXi hosts on one side and a storage system on the other.
n
Storage Containers on page 215
Unlike traditional LUN and NFS based vSphere storage, the Virtual Volumes functionality does not
require precongured 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.
n
Protocol Endpoints on page 216
Although storage systems manage all aspects of virtual volumes, 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 les that virtual volumes
encapsulate. ESXi uses protocol endpoints to establish a data path on demand from virtual machines
to their respective virtual volumes.
n
Virtual Datastores on page 216
A virtual datastore represents a storage container in vCenter Server and the vSphere Web Client.
n
Virtual Volumes and VM Storage Policies on page 217
A virtual machine that runs on a virtual datastore requires a VM storage policy.
Virtual Volumes
Virtual volumes are encapsulations of virtual machine les, virtual disks, and their derivatives.
Virtual volumes are stored natively inside a storage system that is connected through Ethernet or SAN. They
are exported as objects by a compliant storage system and are managed entirely by hardware on the storage
side. Typically, a unique GUID identies a virtual volume. Virtual volumes are not preprovisioned, but
created automatically when you perform virtual machine management operations. These operations include
a VM creation, cloning, and snapshoing. ESXi and vCenter Server associate one or more virtual volumes to
a virtual machine. The system creates the following types of virtual volumes for the core elements that make
up the virtual machine:
n
A data virtual volume that corresponds directly to each virtual disk .vmdk le. As virtual disk les on
traditional datastores, virtual volumes are presented to virtual machines as SCSI disks.
vSphere Storage
214 VMware, Inc.