Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Troubleshooting vSphere Storage

You're reading from   Troubleshooting vSphere Storage All vSphere administrators will benefit big-time from this book because it gives you clear, practical instructions on troubleshooting a whole host of storage problems. From fundamental to advanced techniques, it's all here.

Arrow left icon
Product type Paperback
Published in Nov 2013
Publisher Packt
ISBN-13 9781782172062
Length 150 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Mike Preston Mike Preston
Author Profile Icon Mike Preston
Mike Preston
Arrow right icon
View More author details
Toc

My storage/virtual machine is slow


The following are some questions and tasks you can take to troubleshoot slow or poor storage performance.

Inspect latency values to further pinpoint where performance degradation is occurring

Tip

You can refer Chapter 4, Troubleshooting Storage Contention, for more information on this topic.

Using esxtop and thresholds in Appendix B, Statistics of esxtop, inspect latency statistics (DAVG, KAVG, QAVG, and GAVG).

  • High DAVG indicates a performance issue on the storage array or somewhere along the path to it.

  • High KAVG indicates a performance issue within the VMkernel. Possible causes could include queuing, drivers, and so on.

  • High QAVG indicates a performance issue is causing queue latency to go up. This could be an indicator of underperforming storage if higher DAVG numbers are experienced as well.

  • High GAVG is normally the total of the three previous counters. If experiencing high GAVG while other latency metrics seem sufficient, the issue could reside within the VM drivers or virtual hardware.

Ensure that your storage array is handling the demand

Tip

You can refer Chapter 4, Troubleshooting Storage Contention, and Chapter 5, Troubleshooting Storage Capacity and Overcommitment, for more information on this topic.

The following items need to be considered when dealing with storage arrays:

  • Using the formulas from Chapter 4, Troubleshooting Storage Contention, calculate on a per-LUN basis your functional IOPs requirements

  • Using esxtop and thresholds in Appendix B, Statistics of esxtop, inspect both ABORT and QUEUE statistics

    • Queuing and frequent command aborts could be a possible indicator of underperforming storage

  • Check to see if the VM has a storage profile attached to it that may have gone out of compliance

  • If possible, migrate your workload to a faster performing disk set or to a LUN with a different RAID type

  • Using esxtop and thresholds in Appendix B, Statistics of esxtop, check to see if the issue is being caused by SCSI reservation conflicts or queue depth

    • For SCSI reservation conflicts, monitor CONS/s

    • For queue depth issues, monitor QUED

  • If possible, enable Storage DRS to automatically balance your workloads

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime