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
Cloning or migration of a virtual machine with I/O lter policy from one host to another requires the
destination host to have a compatible lter installed. This requirement applies to migrations initiated by
an administrator or by such functionalities as HA or DRS.
n
When you convert a template to a virtual machine, and the template is congured with I/O lter policy,
the destination host must have the compatible I/O lter installed.
n
If you use vCenter Site Recovery Manager to replicate virtual disks, the resulting disks on the recovery
site do not have I/O lter policies. You must create I/O lter policies in the recovery site and reaach
them to the replicated disks.
n
If your virtual machine has a snapshot tree associated with it, you cannot add, change, or remove the
I/O lter policy for the virtual machine.
For information about troubleshooting I/O lters, see the vSphere Troubleshooting documentation.
Migrating Virtual Machines with I/O Filters
When you migrate a virtual machine with I/O lters, specic considerations apply.
If you use Storage vMotion to migrate a virtual machine with I/O lters, a destination datastore must be
connected to hosts with compatible I/O lters installed.
You might need to migrate a virtual machine with I/O lters across dierent types of datastores, for example
between VMFS and Virtual Volumes, VMFS and Virtual SAN, and so on. If you do so, make sure that in
addition to common rules that describe the I/O lter policy, the VM storage policy includes rule sets for
every type of datastore you are planning to use. For example, if you migrate your virtual machine between
the VMFS and Virtual Volumes datastores, create a mixed VM storage policy that includes the following:
n
Common Rules for the I/O lters
n
Rule Set 1 for the VMFS datastore. Because Storage Policy Based Management does not oer an explicit
VMFS policy, the rule set must include tag-based rules for the VMFS datastore.
n
Rule Set 2 for the Virtual Volumes datastore
When Storage vMotion migrates the virtual machine, the correct rule set that corresponds to the target
datastore is selected. The I/O lter rules remain unchanged.
If you do not specify rules for datastores and dene only Common Rules for the I/O lters, default storage
policies will be selected for Virtual SAN, Virtual Volumes, and VMFS/NFS datastores.
Chapter 21 Filtering Virtual Machine I/O
VMware, Inc. 253