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
n
Rules Based on Tags on page 229
Rules based on tags reference datastore tags that you associate with specic datastores. You can apply
more than one tag to a datastore.
Common Rules
Common rules are based on data services that are generic for all types of storage and do not depend on a
datastore. These additional services become available in the VM Storage Policies interface when you install
third-party I/O lters developed through vSphere APIs for I/O Filtering. You can reference these data
services in a VM storage policy.
Unlike storage-specic rules, common rules do not dene storage placement and storage requirements for a
virtual machine, but ensure that additional data services, such as I/O lters, become enabled for the virtual
machine. No maer which datastore the virtual machine runs on, the enabled lters can provide the
following services:
n
Caching. Congures a cache for virtual disk data. The lter can use a local cache or a ash storage
device to cache the data and increase the Input/Output Operations Per Second and hardware utilization
rates for the virtual disk.
n
Replication. Replicates virtual machine or virtual disks to external targets such as another host or
cluster.
For more information about I/O lters, see Chapter 21, “Filtering Virtual Machine I/O,” on page 243.
Rules Based on Storage-Specific Data Services
These rules are based on data services that storage entities such as Virtual SAN and Virtual Volumes
advertise.
To supply information about underlying storage to vCenter Server, Virtual SAN and Virtual Volumes use
storage providers, also called VASA providers. Storage information and datastore characteristics appear in
the VM Storage Policies interface of the vSphere Web Client as data services oered by the specic datastore
type.
A single datastore can oer multiple services. The data services are grouped in a datastore prole that
outlines the quality of service that the datastore can deliver.
When you create rules for a VM storage policy, you reference data services that a specic datastore
advertises. To the virtual machine that uses this policy, the datastore guarantees that it can satisfy the
storage requirements of the virtual machine. The datastore also can provide the virtual machine with a
specic set of characteristics for capacity, performance, availability, redundancy, and so on.
For more information about storage providers, see Chapter 25, “Using Storage Providers,” on page 277.
Rules Based on Tags
Rules based on tags reference datastore tags that you associate with specic datastores. You can apply more
than one tag to a datastore.
Typically, tags serve the following purposes:
n
Aach a broad storage-level denition to datastores that are not represented by any storage providers,
for example, VMFS and NFS datastores.
n
Encode policy-relevant information that is not advertised through vSphere API for Storage Awareness
(VASA), such as geographical location or administrative group.
Similar to storage-specic services, all tags associated with datastores appear in the VM Storage Policies
interface. You can use the tags when you dene rules for the storage policies.
Chapter 20 Virtual Machine Storage Policies
VMware, Inc. 229