Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By : Kevin Elder, Christopher Kusek, Prasenjit Sarkar
Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By: Kevin Elder, Christopher Kusek, Prasenjit Sarkar

Overview of this book

vSphere is a mission-critical piece of software for many businesses. It is a complex tool, and incorrect design and deployment can create performance related issues that can negatively affect the business. This book is focused on solving these problems as well as providing best practices and performance-enhancing techniques. This edition is fully updated to include all the new features in version 6.5 as well as the latest tools and techniques to keep vSphere performing at its best. This book starts with interesting recipes, such as the interaction of vSphere 6.5 components with physical layers such as CPU, memory, and networking. Then we focus on DRS, resource control design, and vSphere cluster design. Next, you’ll learn about storage performance design and how it works with VMware vSphere 6.5. Moving on, you will learn about the two types of vCenter installation and the benefits of each. Lastly, the book covers performance tools that help you get the most out of your vSphere installation. By the end of this book, you will be able to identify, diagnose, and troubleshoot operational faults and critical performance issues in vSphere 6.5.
Table of Contents (17 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Setting up VVols


Virtual Volumes (VVols) were introduced in vSphere 6.0. Normally, when using iSCSI, NFS, or Fibre Channel storage, the VMware administrator creates a small number of large LUNs that hold many VMs. Administrators are forced to manage these datastores and decide which VMs reside in them. Policy-based metrics, such as QoS, can only be applied at the datastore level so all the VMs in the datastore get the same service level. Furthermore, LUNs and datastore sizes are over-provisioned, which wastes space on the storage array. Creating a new datastore often involves both the storage administrator to create the LUN and the VMware administrator to turn that LUN into a datastore.

All of these issues are solved by VVols. When you create a VM and target VVol storage, each component of the VM that requires storage is given a VVol on the storage array. vCenter and the storage array use a VASA provider in order to communicate.

On the storage array, compatibility profiles are created and...