Book Image

Mastering VMware vSphere Storage

By : Victor Wu, Eagle Huang
Book Image

Mastering VMware vSphere Storage

By: Victor Wu, Eagle Huang

Overview of this book

<p>vSphere Storage is one of the three main infrastructure components of a vSphere deployment (Compute, Storage, and Network).</p> <p>Mastering VMware vSphere Storage begins with an insightful introduction to virtualization and creating your own virtual machines. We then talk about VMware vCenter Server and virtual machine management, as well as managing vSphere 5 using vSphere Management Assistant (vMA) and esxcli and vmware-cmd commands. We then swiftly move on to a very interesting topic, reviewing the vSphere performance and troubleshooting methodology. We then configure VM storage profiles, Storage DRS, and Storage I/O control. More significantly, we will troubleshoot and analyze storage using the VMware CLI and learn how to configure iSCSI storage.</p> <p>By the end of the book, you will be able to identify useful information to make virtual machine and virtual data center design decisions.</p>
Table of Contents (21 chapters)
Mastering VMware vSphere Storage
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

VMware vSphere Storage I/O Control


What is VMware vSphere Storage I/O Control? It is used to control in order to share and limit the storage of I/O resources, for example, the IOPS. You can control the number of storage IOPs allocated to the virtual machine. If a certain virtual machine is required to get more storage I/O resources, vSphere Storage I/O Control can ensure that that virtual machine can get more storage I/O than other virtual machines. The following table shows example of the difference between vSphere Storage I/O Control enabled and without vSphere Storage I/O Control:

In this diagram, the VMware ESXi Host Cluster does not have vSphere Storage I/O Control. VM 2 and VM 5 need to get more IOPs, but they can allocate only a small amount of I/O resources. On the contrary, VM 1 and VM 3 can allocate a large amount of I/O resources. Actually, both VMs are required to allocate a small amount of IOPs. In this case, it wastes and overprovisions the storage resources.

In the diagram...