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
Understanding Virtual Machine Storage Policies
Virtual machine storage policies capture storage characteristics that virtual machine home les and virtual
disks require to run applications within the virtual machine. You can create several storage policies to dene
the types and classes of storage requirements.
Each storage policy is not only a set of constraints that apply simultaneously. A single policy can include
alternative sets of subpolicies, or rule sets, that are datastore-specic and represent equally acceptable
storage requirements. If you use vSphere APIs for I/O Filtering, the storage policy can include rules that are
common for all storage types. The policy can contain only common rules, or only datastore-specic rule sets,
or both.
When you create, clone, or migrate a virtual machine, you can apply the storage policy to the virtual
machine. You can place the virtual machine in one of the datastores that matches the policy requirements. To
match the policy requirement, the datastore must satisfy the following guidelines:
n
When I/O Filtering and common rules are not available, the datastore must satisfy all rules in at least
one of the datastore specic rule sets.
n
With common rules enabled, the datastore must satisfy all common rules and all rules in at least one of
the rule sets.
The virtual machine home les (.vmx, .vmsd, .nvram, .log, and so on) and the virtual disks (.vmdk) can have
separate storage policies.
Table 20‑2. Example Storage Policy for a Virtual Machine
Example Virtual Machine Files Example for a Storage Policy
Example for a Datastore Compliant with the
Storage Policy
windows_2008r2_test.vmx
Storage Policy 2 datastore02, datastore05, datastore10
windows_2008r2_test.vmxf
windows_2008r2_test.log
windows_2008r2_test.nvram
windows_2008r2_test.vmem
windows_2008r2_test.vmsd
windows_2008r2_test.vmdk
Storage Policy 3 datastore05
windows_2008r2_test_1.vmdk
Storage Policy 5 datastore10
Storage Policies and Rules
Rules that you include in a storage policy can be based on storage-specic data services and tags, or the
rules can be common.
n
Common Rules on page 229
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.
n
Rules Based on Storage-Specic Data Services on page 229
These rules are based on data services that storage entities such as Virtual SAN and Virtual Volumes
advertise.
vSphere Storage
228 VMware, Inc.