Method and system for monitoring and analyzing quality of service in a storage system

US9542346B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9542346-B2
Application numberUS-201414154941-A
CountryUS
Kind codeB2
Filing dateJan 14, 2014
Priority dateJan 14, 2014
Publication dateJan 10, 2017
Grant dateJan 10, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Methods and systems for monitoring quality of service (QOS) data for a plurality of storage volumes from a storage operating system of a storage system are provided. A performance manager collects the QOS data from the storage operating system and the QOS data includes a response time in which each of the plurality of storage volumes respond to an input/output (I/O) request. An expected range for future QOS data is generated based on the collected QOS data. The QOS data is monitored for each storage volume for determining whether a current QOS data for each storage volume is within the expected range.

First claim

Opening claim text (preview).

What is claimed is: 1. A machine implemented method, comprising: collecting quality of service (QOS) data for a plurality of storage volumes from a storage operating system of a storage system having a plurality of resources; wherein a processor executable performance manager collects the QOS data from the storage operating system and the QOS data includes a response time in which each of the plurality of storage volumes respond to an input/output (I/O) request; a wait time for each I/O request at each of the resources of the storage system; and a number of visits for each I/O request at each of the resources of the storage system; generating an expected range for future QOS data based on the collected QOS data, where the expected range is a range of measured performance activity of a workload over a period of time for predicting future QOS data behavior of the storage volumes; monitoring QOS data for each storage volume for determining whether a currently collected QOS data for each storage volume is within the expected range; and determining that a resource of the storage system is in contention between any of the plurality of storage volumes resulting in a storage volume becoming a victim due to overuse by another storage volume based on a dynamic threshold value defined by the expected range. 2. The method of claim 1 , wherein the expected range provides the dynamic threshold value to the performance manager for predicting an incident associated with any of the plurality of storage volumes. 3. The method of claim 1 , wherein the resources at the storage system are categorized as a service center that services a request and QOS data for the service center includes a number of visits, wait time per visit and service time and a delay center that only moves the request to a next destination whose QOS data includes the number of visits and the wait time per visit. 4. The method of claim 3 , wherein the resources include a processor for a network module that interfaces with clients and operates as a service center. 5. The method of claim 3 , wherein the resources include a processor for a storage module that operates as a service center and manages storage devices where information is stored. 6. The method of claim 3 , wherein the performance manager tracks QOS data for each service center and delay center to predict the expected range. 7. A non-transitory machine readable storage medium storing executable instructions, which when executed by a machine, causes the machine to perform a method, the method comprising: collecting quality of service (QOS) data for a plurality of storage volumes from a storage operating system of a storage system having a plurality of resources; wherein a processor executable performance manager collects the QOS data from the storage operating system and the QOS data includes a response time in which each of the plurality of storage volumes respond to an input/output (I/O) request; a wait time for each I/O request at each of the resources of the storage system; and a number of visits for each I/O request at each of the resources of the storage system; generating an expected range for future QOS data based on the collected QOS data, where the expected range is a range of measured performance activity of a workload over a period of time for predicting future QOS data behavior of the storage volumes; monitoring QOS data for each storage volume for determining whether a current QOS data for each storage volume is within the expected range; and determining that a resource of the storage system is in contention between any of the plurality of storage volumes resulting in a storage volume becoming a victim due to overuse by another storage volume based on a dynamic threshold value that is defined by the expected range for the QOS data. 8. The storage medium of claim 7 , wherein the expected range provides the dynamic threshold value to the performance manager for predicting an incident associated with any of the plurality of storage volumes. 9. The storage medium of claim 7 , wherein the resources at the storage system are categorized as a service center that services a request and QOS data for the service center includes a number of visits, wait time per visit and service time and a delay center that only moves the request to a next destination whose QOS data includes the number of visits and the wait time per visit. 10. The storage medium of claim 9 , wherein the resources include a processor for a network module that interfaces with clients and operates as a service center. 11. The storage medium of claim 9 , wherein the resources include a processor for a storage module that operates as a service center and manages storage devices where information is stored. 12. The storage medium of claim 9 , wherein the performance manager tracks QOS data for each service center and delay center to predict the expected range. 13. A system, comprising: a processor of a storage system executing a storage operating system for managing access to a plurality of storage volumes for storing information at a plurality of storage devices; and a processor for a performance manager executing instructions out of a memory device for collecting quality of service (QOS) data for the plurality of storage volumes from the storage operating system; generating an expected range for future QOS data based on the collected QOS data where the expected range is a range of measured performance activity of a workload over a period of time for predicting future QOS data behavior of the storage volumes; and monitoring QOS data for each storage volume for determining whether a current QOS data for each storage volume is within the expected range; wherein QOS data includes a response time in which each of the plurality of storage volumes respond to an input/output (I/O) request; a wait time for each I/O request at each resource of the storage system; and a number of visits for each I/O request at each of the resources within the storage system; and wherein the expected range provides a dynamic threshold value to the performance manager for predicting an incident associated with any of the plurality of storage volumes and determining if any of the resources of the storage system is in contention between any of the plurality of storage volumes resulting in a storage volume becoming a victim due to overuse by another storage volume. 14. The system of claim 13 , wherein the resources at the storage system are categorized as a service center that services a request and QOS data for the service center includes a number of visits, wait time per visit and service time and a delay center that only moves the request to a next destination whose QOS data includes the number of visits and the wait time per visit. 15. The system of claim 13 , wherein the resources include a processor for a network module that interfaces with clients and operates as a service center. 16. The system of claim 13 , wherein the resources include a processor for a storage module that operates as a service center and manages storage devices where information is stored. 17. The system of claim 13 , wherein the performance manager tracks QOS data for each service center and delay center to predict the expected range.

Assignees

Inventors

Classifications

  • in relation to response time · CPC title

  • by facilitating the interaction with a user or administrator · CPC title

  • Monitoring storage devices or systems · CPC title

  • being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus · CPC title

  • G06F13/36Primary

    for access to common bus or bus system · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9542346B2 cover?
Methods and systems for monitoring quality of service (QOS) data for a plurality of storage volumes from a storage operating system of a storage system are provided. A performance manager collects the QOS data from the storage operating system and the QOS data includes a response time in which each of the plurality of storage volumes respond to an input/output (I/O) request. An expected range f…
Who is the assignee on this patent?
Netapp Inc
What technology area does this patent fall under?
Primary CPC classification G06F13/36. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jan 10 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).