6.7
Table Of Contents
- vSphere Storage
- Contents
- About vSphere Storage
- Introduction to Storage
- Getting Started with a Traditional Storage Model
- 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 Recommendations and Restrictions
- Configuring iSCSI Parameters for Adapters
- Set Up Independent Hardware iSCSI Adapters
- Configure Dependent Hardware iSCSI Adapters
- Configure the Software iSCSI Adapter
- Configure iSER Adapters
- Modify General Properties for iSCSI or iSER Adapters
- Setting Up Network for iSCSI and iSER
- 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 Rescan Operations
- Identifying Device Connectivity Problems
- Enable or Disable the Locator LED on Storage Devices
- Erase Storage Devices
- Working with Flash Devices
- About VMware vSphere Flash Read Cache
- Working with Datastores
- Types of Datastores
- Understanding VMFS Datastores
- Upgrading VMFS Datastores
- Understanding Network File System Datastores
- Creating Datastores
- Managing Duplicate 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
- Failovers with Fibre Channel
- Host-Based Failover with iSCSI
- Array-Based Failover with iSCSI
- Path Failover and Virtual Machines
- Pluggable Storage Architecture and Path Management
- Viewing and Managing Paths
- Using Claim Rules
- Scheduling Queues for Virtual Machine I/Os
- Raw Device Mapping
- Storage Policy Based Management
- Virtual Machine Storage Policies
- Workflow for Virtual Machine Storage Policies
- Populating the VM Storage Policies Interface
- About Rules and Rule Sets
- Creating and Managing VM Storage Policies
- About Storage Policy Components
- Storage Policies and Virtual Machines
- Default Storage Policies
- Using Storage Providers
- Working with Virtual Volumes
- About Virtual Volumes
- Virtual Volumes Concepts
- Virtual Volumes and Storage Protocols
- Virtual Volumes Architecture
- Virtual Volumes and VMware Certificate Authority
- Snapshots and Virtual Volumes
- Before You Enable Virtual Volumes
- Configure Virtual Volumes
- Provision Virtual Machines on Virtual Volumes Datastores
- Virtual Volumes and Replication
- Best Practices for Working with vSphere Virtual Volumes
- Troubleshooting Virtual Volumes
- Filtering Virtual Machine I/O
- 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
- Thin Provisioning and Space Reclamation
- Using vmkfstools
- vmkfstools Command Syntax
- The vmkfstools Command Options
- -v Suboption
- File System Options
- Virtual Disk Options
- Supported Disk Formats
- Creating a Virtual Disk
- Initializing a Virtual Disk
- Inflating a Thin Virtual Disk
- Converting a Zeroedthick Virtual Disk to an Eagerzeroedthick Disk
- Removing Zeroed Blocks
- Deleting a Virtual Disk
- Renaming a Virtual Disk
- Cloning or Converting a Virtual Disk or RDM
- Extending a Virtual Disk
- Upgrading Virtual Disks
- Creating a Virtual Compatibility Mode Raw Device Mapping
- 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
This information is obtained from storage providers, also called VASA providers. Another source is
datastore tags.
Storage Capabilities
and Services
Certain datastores, for example, Virtual Volumes and vSAN, are
represented by the storage providers. Through the storage providers, the
datastores can advertise their capabilities in the VM Storage Policy
interface. These datastore capabilities, data services, and other
characteristics with ranges of values populate the VM Storage Policy
interface.
You use these characteristics when you define datastore-based placement
and service rules for your storage policy.
Data Services I/O filters on your hosts are also represented by the storage providers. The
storage provider delivers information about the data services of the filters to
the VM Storage Policy interface. You use this information when defining the
rules for host-based data services, also called common rules. Unlike the
datastore-specific rules, these rules do not define storage placement and
storage requirements for the virtual machine. Instead, they activate the
requested I/O filter data services for the virtual machine.
Tags Generally, VMFS and NFS datastores are not represented by a storage
provider. They do not display their capabilities and data services in the VM
Storage Polices interface. You can use tags to encode information about
these datastores. For example, you can tag your VMFS datastores as
VMFS-Gold and VMFS-Silver to represent different levels of service.
For VVols and vSAN datastores, you can use tags to encode information
that is not advertised by the storage provider, such as geographical location
(Palo Alto), or administrative group (Accounting).
Similar to the storage capabilities and characteristics, all tags associated
with the datastores appear in the VM Storage Policies interface. You can
use the tags when you define the tag-based placement rules.
Use Storage Providers to Populate the VM Storage Policies
Interface
For entities represented by storage (VASA) providers, verify that an appropriate provider is registered.
After the storage providers are registered, the VM Storage Policies interface becomes populated with
information about datastores and data services that the providers represent.
Entities that use the storage provider include vSAN, Virtual Volumes, and I/O filters. Depending on the
type of the entity, some providers are self-registered. Other providers, for example, the Virtual Volumes
storage provider, must be manually registered. After the storage providers are registered, they deliver the
following data to the VM Storage Policies interface:
n
Storage capabilities and characteristics for such datastores as Virtual Volumes and vSAN.
vSphere Storage
VMware, Inc. 243