Global in-line extent-based deduplication
US-2015193169-A1 · Jul 9, 2015 · US
US11934260B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11934260-B2 |
| Application number | US-202318104659-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 1, 2023 |
| Priority date | Oct 23, 2015 |
| Publication date | Mar 19, 2024 |
| Grant date | Mar 19, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method may include detecting, by a computing device based on a problem signature, that a system has experienced a problem that is associated with the problem signature, wherein the problem signature comprises a specification of a pattern of events indicative of the particular problem experienced by at least one other system; determining that the particular problem violates an operational policy of the system; and deploying, without user intervention, one or more corrective measures that modify the system to resolve the problem.
Opening claim text (preview).
What is claimed is: 1. A method comprising: detecting, by a cloud based storage system services module based on a problem signature, that a system has experienced a problem that is associated with the problem signature, wherein the problem signature comprises a specification of a pattern of events indicative of the particular problem experienced by at least one other system; determining that the particular problem violates an operational policy of the system; and deploying, without user intervention, one or more corrective measures that modify the system to resolve the problem. 2. The method of claim 1 , wherein the operational policy specifies at least one requirement for an operational metric of the system, and wherein the operational policy of the system further comprises a specification of a requirement for high availability. 3. The method of claim 1 , wherein the operational policy specifies at least one requirement for an operational metric of the system, and wherein the operational policy of the system further comprises a specification of a requirement for failover availability. 4. The method of claim 1 , wherein the operational policy specifies at least one requirement for an operational metric of the system, and wherein the operational policy of the system further comprises a specification of a requirement for a minimum data reduction ratio. 5. The method of claim 1 , wherein the operational policy specifies at least one requirement for an operational metric of the system, and wherein the operational policy of the system further comprises a specification of a requirement for a minimum input/output latency. 6. The method of claim 1 , wherein the operational policy specifies at least one requirement for an operational metric of the system, and wherein the operational policy of the system further comprises a specification of a requirement for a minimum replication throughput. 7. The method of claim 1 , wherein the operational policy specifies at least one requirement for an operational metric of the system, and wherein the operational policy of the system further comprises a specification of a requirement for data retention. 8. An apparatus, the apparatus comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of: detecting, by a cloud based storage system services module based on a problem signature, that a system has experienced a problem that is associated with the problem signature, wherein the problem signature comprises a specification of a pattern of events indicative of the problem experienced by at least one other system; determining that the problem violates an operational policy of the system; and deploying, without user intervention and based on the detecting and the determining, one or more corrective measures that modify the system to resolve the problem. 9. The apparatus of claim 8 , wherein the operational policy of the system further comprises a specification of a requirement for high availability. 10. The apparatus of claim 8 , wherein the operational policy of the system further comprises a specification of a requirement for failover availability. 11. The apparatus of claim 8 , wherein the operational policy of the system further comprises a specification of a requirement for a minimum data reduction ratio. 12. The apparatus of claim 8 , wherein the operational policy of the system further comprises a specification of a requirement for a minimum input/output latency. 13. The apparatus of claim 8 , wherein the operational policy of the system further comprises a specification of a requirement for a minimum replication throughput. 14. The apparatus of claim 8 , wherein the operational policy of the system further comprises a specification of a requirement for data retention. 15. A non-transitory computer-readable medium storing a cloud based storage system services module that comprises instructions that, when executed, direct a processor to carry out the steps of: detecting that a system has experienced a problem that is associated with a problem signature, wherein the problem signature comprises a specification of a pattern of events indicative of the problem experienced by at least one other system; determining that the problem violates an operational policy of the system; and deploying, without user intervention, one or more corrective measures that modify the system to resolve the problem. 16. The non-transitory computer-readable medium of claim 15 , wherein the operational policy of the system further comprises a specification of a requirement for high availability. 17. The non-transitory computer-readable medium of claim 15 , wherein the operational policy of the system further comprises a specification of a requirement for failover availability. 18. The non-transitory computer-readable medium of claim 15 , wherein the operational policy of the system further comprises a specification of a requirement for a minimum data reduction ratio. 19. The non-transitory computer-readable medium of claim 15 , wherein the operational policy of the system further comprises a specification of a requirement for a minimum input/output latency. 20. The non-transitory computer-readable medium of claim 15 , wherein the operational policy of the system further comprises a specification of a requirement for a minimum replication throughput.
Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title
Reliability or availability analysis · CPC title
in a storage system, e.g. in a DASD or network based storage system (drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097) · CPC title
Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06) · CPC title
Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.