6.5.1
Table Of Contents
- vSphere Storage
- Contents
- About vSphere Storage
- Updated Information
- 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 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
- 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 Rescan Operations
- Identifying Device Connectivity Problems
- Edit Configuration File Parameters
- 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
- 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
- Raw Device Mapping
- Software-Defined Storage and Storage Policy Based Management
- About Storage Policy Based Management
- Virtual Machine Storage Policies
- Working with Virtual Machine Storage Policies
- Populating the VM Storage Policies Interface
- Default Storage Policies
- Creating and Managing VM Storage Policies
- Storage Policies and Virtual Machines
- 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
- 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
- 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
About Datastore-Specific and Common Rule Sets
After the VM Storage Policies interface is populated with the appropriate data, you can start defining your
storage policies. A basic element of a VM storage policy is a rule. Each individual rule is a statement that
describes a single requirement for virtual machine storage and data services. Within the policy, rules are
grouped in collections of rules. Two types of collections exist, regular rule sets and common rule sets.
Regular Rule Sets Regular rule sets are datastore-specific. Each rule set must include
placement rules that describe requirements for virtual machine storage
resources. All placement rules within a single rule set represent a single
storage entity. These rules can be based on tags or storage capabilities. In
addition, the regular rule set can include optional storage policy
components that describe data services to provide for the virtual machine.
To define the storage policy, one regular rule set is required. Additional rule
sets are optional. A single policy can use multiple sets of rules to define
alternative storage placement parameters, often from several storage
providers.
Common Rule Sets Unlike datastore-specific regular rule sets, common rule sets do not define
storage placement for the virtual machine, and do not include placement
rules. Common rule sets are generic for all types of storage and do not
depend on the datastore. These rule sets activate data services for the
virtual machine. Common rule sets include rules or storage policy
components that describe particular data services, such as encryption or
replication.
Table 20‑1. Structure of a VM Storage Policy
Common Rules Regular Rule Sets
Rules or predefined storage policy components to activate data
services installed on ESXi hosts. For example, replication by I/O
filters.
Placement rules that describe requirements for virtual machine
storage resources. For example, Virtual Volumes placement.
Rules or predefined storage policy components that activate
data services provided by storage. For example, caching by
Virtual Volumes.
Relationships Between Rules and Rule Sets
The boolean operator OR defines the relationship between the regular rule sets within the policy. The AND
operator defines the relationship between all rules within a single rule set. The policy can contain only
common rules, or only datastore-specific rule sets, or both. If common rules are not present, meeting all
the rules of a single regular rule set is sufficient to satisfy the entire policy. If common rules are present,
the policy matches the datastore that satisfies the common rules and all rules in one of the regular rule
sets.
vSphere Storage
VMware, Inc. 243