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
5 Specify the VM storage policy for your virtual machine.
Option Description
Apply the same storage policy to all
virtual machine objects.
a Select the policy from the VM storage policy drop-down menu.
b Click Apply to all.
Apply different storage policies to
the VM home object and virtual
disks.
a Select the object.
b Select the policy from the VM storage policy drop-down menu for the
object.
6 Click OK.
The storage policy is assigned to the virtual machine and its disks.
Monitor Storage Compliance for Virtual Machines
When you associate a policy with virtual machine objects and select the datastores on which virtual
machines and virtual disks run, you can check whether virtual machines and virtual disks use datastores
that are compliant with the policy.
If you check the compliance of a virtual machine whose host or cluster has storage policies disabled, the
result of the check is Noncompliant because the feature is disabled.
Prerequisites
To perform a compliance check for a storage policy, associate the policy with at least one virtual machine or
virtual disk.
Procedure
1 From the vSphere Web Client Home, click Policies and > VM Storage Policies.
2 Double-click a storage policy.
3 Click the Monitor tab, and click VMs and Virtual Disks.
4 Click Trigger VM Storage Policy Compliance Check.
The Compliance Status column shows the storage compliance status for virtual machines and their
policies.
Compliance Status Description
Compliant The datastore that the virtual machine or virtual disk uses has the storage capabilities that are
required by the policy.
Noncompliant The datastore supports specied storage requirements, but cannot currently satisfy the
virtual machine storage policy. For example, the status might become Not Compliant when
physical resources that back up the datastore are unavailable or exhausted. You can bring the
datastore into compliance by making changes in the physical conguration, for example, by
adding hosts or disks to the cluster. If additional resources satisfy the virtual machine storage
policy, the status changes to Compliant.
Out of Date The status indicates that the policy has been edited, but the new requirements have not been
communicated to the datastore where the virtual machine objects reside. To communicate the
changes, reapply the policy to the objects that are out of date.
Not Applicable This storage policy references datastore capabilities that are not supported by the datastore
where the virtual machine resides.
What to do next
When you cannot bring the noncompliant datastore into compliance, migrate the les or virtual disks to a
compatible datastore. See “Find Compatible Storage Resource for Noncompliant Virtual Machine,” on
page 240.
Chapter 20 Virtual Machine Storage Policies
VMware, Inc. 239