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
Option Description
-t|--type=<type>
Type of matching to use for the operation. Valid values are the following.
Required.
n
vendor
n
location
n
driver
n
transport
n
device
n
target
-V|--vendor=<vendor>
Vendor of the paths to use. Valid only if --type is vendor.
Valid values are values of the vendor string from the SCSI inquiry string. Run
vicfg-scsidevs <conn_options> -l on each device to see vendor string
values.
--wwnn=<wwnn>
World-Wide Node Number for the target.
--wwpn=<wwpn>
World-Wide Port Number for the target.
-a|--xcopy-use-array-values
Use the array reported values to construct the XCOPY command to be sent to the
storage array. This applies to VAAI claim rules only.
-s|--xcopy-use-multi-segs
Use multiple segments when issuing an XCOPY request. Valid only if --xcopy-
use-array-values is specified.
-m|--xcopy-max-transfer-size
Maximum data transfer size in MB when you use a transfer size different than
array reported. Valid only if --xcopy-use-array-values is specified.
-k|--xcopy-max-transfer-size-kib
Maximum transfer size in KiB for the XCOPY commands when you use a transfer
size different than array reported. Valid only if --xcopy-use-array-values is
specified.
2 To load the new claim rule into your system, use the following command:
esxcli storage core claimrule load
This command loads all newly created multipathing claim rules from the esx.conf configuration file
into the VMkernel. The command has no options.
3 To apply claim rules that are loaded, use the following command:
esxcli storage core claimrule run
The command takes the following options:
Option Description
-A|--adapter=<adapter>
If --type is location, name of the HBA for the paths to run the claim rules on.
To run claim rules on paths from all adapters, omit this option.
-C|--channel=<channel>
If --type is location, value of the SCSI channel number for the paths to run the
claim rules on. To run claim rules on paths with any channel number, omit this
option.
-c|--claimrule-class=<cl>
Claim rule class to use in this operation.
-d|--device=<device_uid>
UID of the device.
-L|--lun=<lun_id>
If --type is location, value of the SCSI LUN for the paths to run claim rules on.
To run claim rules on paths with any LUN, omit this option.
vSphere Storage
VMware, Inc. 225