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
Storage Policies and Virtual Machines
After you dene a VM storage policy, you can apply it to a virtual machine. You apply the storage policy
when provisioning the virtual machine or conguring its virtual disks. Depending on its type and
conguration, the policy might serve dierent purposes. It can select the most appropriate datastore for the
virtual machine and enforce the required level of service, or it can enable specic data services for the
virtual machine and its disks.
If you do not specify the storage policy, the system uses a default storage policy that is associated with the
datastore. If your storage requirements for the applications on the virtual machine change, you can modify
the storage policy that was originally applied to the virtual machine.
Default Storage Policies
When you provision a virtual machine on an object-based datastore, such as Virtual SAN or Virtual
Volumes, you must assign to the virtual machine an appropriate virtual machine storage policy that is
compatible with the datastore. This assignment guarantees the optimum placement for virtual machine
objects within the object-based storage. If you do not explicitly assign a storage policy to the virtual
machine, the system uses a default storage policy that is associated with the datastore. The default policy is
also used when the policy that you assign does not include rules specic to Virtual Volumes or Virtual SAN.
The default storage policies for Virtual SAN and Virtual Volumes can be provided by VMware and user-
dened. VMFS and NFS datastores do not have default policies.
Default Policies Provided by VMware
VMware provides default storage policies for Virtual SAN and virtual datastores.
Virtual SAN Default Storage Policy
The default storage policy that VMware provides is applied to all virtual machine objects that are
provisioned on a Virtual SAN datastore when you do not select any other Virtual SAN policy.
The policy that VMware provides has the following characteristics:
n
You cannot delete the policy.
n
The policy is editable. To edit the policy, you must have the storage policy privileges that include the
view and update privileges.
n
When editing the policy, you cannot change the name of the policy or the Virtual SAN storage provider
specication. All other parameters including rules are editable.
n
You can clone the default policy and use it as a template to create a storage policy.
n
The Virtual SAN default policy is compatible only with Virtual SAN datastores.
n
You can create a VM storage policy for Virtual SAN and designate it as the default.
Virtual Volumes Default Storage Policy
For Virtual Volumes, VMware provides a default storage policy that contains no rules or storage
requirements. As with Virtual SAN, this policy is applied to virtual machine objects when you do not
specify another policy for the virtual machine that you place on the virtual datastore. With the No
Requirements policy, storage arrays can determine the optimum placement for the VM objects.
The default Virtual Volumes policy that VMware provides has the following characteristics:
n
You cannot delete, edit, or clone this policy.
n
The Virtual Volumes default policy is compatible only with virtual datastores.
n
You can create a VM storage policy for Virtual Volumes and designate it as the default.
vSphere Storage
236 VMware, Inc.