6.5.1
Table Of Contents
- vSphere Resource Management
- Contents
- About vSphere Resource Management
- Getting Started with Resource Management
- Configuring Resource Allocation Settings
- CPU Virtualization Basics
- Administering CPU Resources
- Memory Virtualization Basics
- Administering Memory Resources
- Configuring Virtual Graphics
- Managing Storage I/O Resources
- Managing Resource Pools
- Creating a DRS Cluster
- Using DRS Clusters to Manage Resources
- Creating a Datastore Cluster
- Initial Placement and Ongoing Balancing
- Storage Migration Recommendations
- Create a Datastore Cluster
- Enable and Disable Storage DRS
- Set the Automation Level for Datastore Clusters
- Setting the Aggressiveness Level for Storage DRS
- Datastore Cluster Requirements
- Adding and Removing Datastores from a Datastore Cluster
- Using Datastore Clusters to Manage Storage Resources
- Using NUMA Systems with ESXi
- Advanced Attributes
- Fault Definitions
- Virtual Machine is Pinned
- Virtual Machine not Compatible with any Host
- VM/VM DRS Rule Violated when Moving to another Host
- Host Incompatible with Virtual Machine
- Host Has Virtual Machine That Violates VM/VM DRS Rules
- Host has Insufficient Capacity for Virtual Machine
- Host in Incorrect State
- Host Has Insufficient Number of Physical CPUs for Virtual Machine
- Host has Insufficient Capacity for Each Virtual Machine CPU
- The Virtual Machine Is in vMotion
- No Active Host in Cluster
- Insufficient Resources
- Insufficient Resources to Satisfy Configured Failover Level for HA
- No Compatible Hard Affinity Host
- No Compatible Soft Affinity Host
- Soft Rule Violation Correction Disallowed
- Soft Rule Violation Correction Impact
- DRS Troubleshooting Information
- Cluster Problems
- Load Imbalance on Cluster
- Cluster is Yellow
- Cluster is Red Because of Inconsistent Resource Pool
- Cluster Is Red Because Failover Capacity Is Violated
- No Hosts are Powered Off When Total Cluster Load is Low
- Hosts Are Powered-off When Total Cluster Load Is High
- DRS Seldom or Never Performs vMotion Migrations
- Host Problems
- DRS Recommends Host Be Powered on to Increase Capacity When Total Cluster Load Is Low
- Total Cluster Load Is High
- Total Cluster Load Is Low
- DRS Does Not Evacuate a Host Requested to Enter Maintenance or Standby Mode
- DRS Does Not Move Any Virtual Machines onto a Host
- DRS Does Not Move Any Virtual Machines from a Host
- Virtual Machine Problems
- Cluster Problems
- Index
2 (Optional) Set Storage DRS thresholds.
You set the aggressiveness level of Storage DRS by specifying thresholds for used space and I/O latency.
n
Use the Utilized Space slider to indicate the maximum percentage of consumed space allowed
before Storage DRS is triggered. Storage DRS makes recommendations and performs migrations
when space use on the datastores is higher than the threshold.
n
Use the I/O Latency slider to indicate the maximum I/O latency allowed before Storage DRS is
triggered. Storage DRS makes recommendations and performs migrations when latency is higher
than the threshold.
N The Storage DRS I/O Latency threshold for the datastore cluster should be lower than or
equal to the Storage I/O Control congestion threshold.
3 (Optional) Congure advanced options.
n
No recommendations until utilization dierence between source and destination is: Use the slider
to specify the space utilization dierence threshold. Utilization is usage * 100/capacity.
This threshold ensures that there is some minimum dierence between the space utilization of the
source and the destination. For example, if the space used on datastore A is 82% and datastore B is
79%, the dierence is 3. If the threshold is 5, Storage DRS will not make migration
recommendations from datastore A to datastore B.
n
Check imbalances every: Specify how often Storage DRS should assess space and I/O load
balancing.
n
I/O imbalance threshold: Use the slider to indicate the aggressiveness of I/O load balancing.
Lowering this value makes I/O load balancing less aggressive. Storage DRS computes an I/O
fairness metric between 0 and 1, which 1 being the fairest distribution. I/O load balancing runs only
if the computed metric is less than 1 - (I/O imbalance threshold / 100).
4 Click OK.
Datastore Cluster Requirements
Datastores and hosts that are associated with a datastore cluster must meet certain requirements to use
datastore cluster features successfully.
Follow these guidelines when you create a datastore cluster.
n
Datastore clusters must contain similar or interchangeable datastores.
A datastore cluster can contain a mix of datastores with dierent sizes and I/O capacities, and can be
from dierent arrays and vendors. However, the following types of datastores cannot coexist in a
datastore cluster.
n
NFS and VMFS datastores cannot be combined in the same datastore cluster.
n
Replicated datastores cannot be combined with non-replicated datastores in the same Storage-DRS-
enabled datastore cluster.
n
All hosts aached to the datastores in a datastore cluster must be ESXi 5.0 and later. If datastores in the
datastore cluster are connected to ESX/ESXi 4.x and earlier hosts, Storage DRS does not run.
n
Datastores shared across multiple data centers cannot be included in a datastore cluster.
n
As a best practice, do not include datastores that have hardware acceleration enabled in the same
datastore cluster as datastores that do not have hardware acceleration enabled. Datastores in a datastore
cluster must be homogeneous to guarantee hardware acceleration-supported behavior.
Chapter 12 Creating a Datastore Cluster
VMware, Inc. 95