Method and system for performing data protection services using a grouped subsystem level feedback mechanism

US11892915B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11892915-B2
Application numberUS-202217972145-A
CountryUS
Kind codeB2
Filing dateOct 24, 2022
Priority dateJun 10, 2021
Publication dateFeb 6, 2024
Grant dateFeb 6, 2024

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.

In general, in one aspect, the invention relates to a method for managing performances of services, the method comprising: generating subsystem groups, wherein each subsystem group of the subsystem groups comprises a plurality of subsystems, wherein each subsystem group is associated with one a plurality of services, wherein the subsystem groups are generated using per-service subsystem requirements; and performing at least one of the plurality of services using a subsystem group of the subsystem groups.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for managing performances of services, the method comprising: generating subsystem groups, wherein each subsystem group of the subsystem groups comprises a plurality of subsystems, wherein each subsystem group is associated with one of a plurality of services, wherein the subsystem groups are generated using per-service subsystem requirements, wherein the plurality of services are performed based on policies and service priorities specified by the policies; performing, based on each subsystem's assigned concurrency, at least one of the plurality of services using a subsystem group of the subsystem groups, wherein a subsystem's concurrency specifies a number of concurrent services that the subsystem is able to perform; and obtaining subsystem statistics for each of the plurality of subsystems, wherein the subsystem statistics specify at least one selected from a group consisting of a number of operations per policy performed by each of the plurality of subsystems, and a resource allocation for each of the plurality of subsystems, wherein the subsystem statistics and the service priorities are used to generate a feedback with respect to a service performance level of each of the plurality of subsystems by managing each subsystem's concurrency. 2. The method of claim 1 , wherein the plurality of subsystems comprises one selected from a group consisting of: a host data subsystem, a storages data subsystem, a network subsystem, a metadata subsystem, and a compute subsystem. 3. The method of claim 2 , wherein the plurality of services comprises at least one selected from a group consisting of: a backup service; a replication service; a tiering service; and a disaster recovery service. 4. The method of claim 1 , further comprising: determining a per-service performance metric for each service based on the subsystem statistics. 5. The method of claim 4 , wherein the per-service performance metric for a service of the plurality of services indicates that the service is operating below an expected performance level; further comprising: sending, a notification to a user, when the per-service performance metric for a service of the plurality of services indicates that the service is operating below an expected performance level. 6. The method of claim 5 , wherein the notification specifies a cause of the service is operating below an expected performance level. 7. The method of claim 6 , further comprising: removing a subsystem from a subsystem group associated with the service, wherein the subsystem group is specified as the cause in the notification; and allocating another subsystem to the subsystem group. 8. A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for managing performances of services, the method comprising: generating subsystem groups, wherein each subsystem group of the subsystem groups comprises a plurality of subsystems, wherein each subsystem group is associated with one of a plurality of services, wherein the subsystem groups are generated using per-service subsystem requirements, wherein the plurality of services are performed based on policies and service priorities specified by the policies; performing, based on each subsystem's assigned concurrency, at least one of the plurality of services using a subsystem group of the subsystem groups, wherein a subsystem's concurrency specifies a number of concurrent services that the subsystem is able to perform; and obtaining subsystem statistics for each of the plurality of subsystems, wherein the subsystem statistics specify at least one selected from a group consisting of a number of operations per policy performed by each of the plurality of subsystems, and a resource allocation for each of the plurality of subsystems, wherein the subsystem statistics and the service priorities are used to generate a feedback with respect to a service performance level of each of the plurality of subsystems by managing each subsystem's concurrency. 9. The non-transitory computer readable medium of claim 8 , wherein the plurality of subsystems comprises one selected from a group consisting of: a host data subsystem, a storages data subsystem, a network subsystem, a metadata subsystem, and a compute subsystem. 10. The non-transitory computer readable medium of claim 9 , wherein the plurality of services comprises at least one selected from a group consisting of: a backup service; a replication service; a tiering service; and a disaster recovery service. 11. The non-transitory computer readable medium of claim 8 , the method further comprising: determining a per-service performance metric for each service based on the subsystem statistics. 12. The non-transitory computer readable medium of claim 11 , wherein the per-service performance metric for a service of the plurality of services indicates that the service is operating below an expected performance level; where the method further comprises: sending, a notification to a user, when the per-service performance metric for a service of the plurality of services indicates that the service is operating below an expected performance level. 13. The non-transitory computer readable medium of claim 12 , wherein the notification specifies a cause of the service is operating below an expected performance level. 14. The non-transitory computer readable medium of claim 13 , further comprising: removing a subsystem from a subsystem group associated with the service, wherein the subsystem group is specified as the cause in the notification; and allocating another subsystem to the subsystem group. 15. A data protection manager, comprising: a processor and memory, and configured to: generate subsystem groups, wherein each subsystem group of the subsystem groups comprises a plurality of subsystems, wherein each subsystem group is associated with one of a plurality of services, wherein the subsystem groups are generated using per-service subsystem requirements, wherein the plurality of services are performed based on policies and service priorities specified by the policies; perform, based on each subsystem's assigned concurrency, at least one of the plurality of services using a subsystem group of the subsystem groups, wherein a subsystem's concurrency specifies a number of concurrent services that the subsystem is able to perform; and obtaining subsystem statistics for each of the plurality of subsystems, wherein the subsystem statistics specify at least one selected from a group consisting of a number of operations per policy performed by each of the plurality of subsystems, and a resource allocation for each of the plurality of subsystems, wherein the subsystem statistics and the service priorities are used to generate a feedback with respect to a service performance level of each of the plurality of subsystems by managing each subsystem's concurrency. 16. The data protection manager of claim 15 , wherein the plurality of subsystems comprises one selected from a group consisting of: a host data subsystem, a storages data subsystem, a network subsystem, a metadata subsystem, and a compute subsystem. 17. The data protection manager of claim 16 , wherein the plurality of services comprises at least one selected from a group consisting of: a backup service; a replication service; a tiering service; and a disaster recovery service.

Assignees

Inventors

Classifications

  • Backup restoration techniques · CPC title

  • by reconfiguration of node membership · CPC title

  • Backup scheduling policy · CPC title

  • for performance assessment · CPC title

  • Performance evaluation by statistical analysis · 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 US11892915B2 cover?
In general, in one aspect, the invention relates to a method for managing performances of services, the method comprising: generating subsystem groups, wherein each subsystem group of the subsystem groups comprises a plurality of subsystems, wherein each subsystem group is associated with one a plurality of services, wherein the subsystem groups are generated using per-service subsystem require…
Who is the assignee on this patent?
Emc Ip Holding Co Llc
What technology area does this patent fall under?
Primary CPC classification G06F11/1469. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 06 2024 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 9 related publications on this page (citations in our corpus or others sharing the same primary CPC).