IP Library Granted Patent US 8,572,434
Granted Patent B2
US 8,572,434 · App. 12/893,950 · Granted Oct 29, 2013

System health monitor

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,572,434
App. No.
12/893,950
Granted
Oct 29, 2013
Kind
B2
Abstract

Described are computer-based methods and apparatuses, including computer program products, for system health monitoring. Backup set metadata is received, wherein the backup set metadata comprises information about backup data sets that are received by a backup storage system. One or more processes that process the backup set metadata through an emulated processing flow path are executed, wherein the one or more processes are also implemented in the backup storage system. Two or more potential processing states are determined within the emulated processing flow path. A reason code is determined for each backup set metadata entry of the backup set metadata indicative of a reason that the backup set metadata entry is in a processing state of the two or more potential processing states. A problem with the manner in which the backup set metadata is flowing through the emulated processing flow path is identified based on the reason codes.

Claims (54)

1. A computerized method for system monitoring comprising:

receiving, by an emulating computing device, backup set metadata, wherein the backup set metadata comprises information about backup data sets that are received by a backup storage system that stores the backup data sets; and

emulating, by the software monitor computing device, the manner in which data within the backup data sets flow through a processing flow path of the backup storage system comprising:

executing, by the emulating computing device, one or more processes that process the backup set metadata through an emulated processing flow path, wherein the one or more processes are also implemented in the backup storage system to process the backup data sets through the processing flow path;

determining, by the emulating computing device, two or more potential processing states within the emulated processing flow path;

determining, by the emulating computing device, a reason code for each backup set metadata entry of the backup set metadata indicative of a reason that the backup set metadata entry is in a processing state of the two or more potential processing states; and

identifying, by the emulating computing device, a problem with the manner in which the backup set metadata is flowing through the emulated processing flow path based on the reason codes.

2. The method of claim 1 further comprising determining the reason codes based on one or more factors comprising at least one of (i) an expected quantity of data at the processing state, (ii) a processing error at the processing state, or (iii) a backup customer's configuration of the backup storage system.

3. The method of claim 2 further comprising processing the backup set metadata through the emulated processing flow path, wherein a plurality of backup set metadata entries of the backup set metadata are in a corresponding processing state of the emulated processing flow path before the plurality of backup set metadata entries are completely processed through the emulated processing flow path.

4. The method of claim 1 further comprising monitoring the manner in which backup set metadata entries of the backup set metadata are processed through a portion of the emulated processing flow path, wherein the emulated processing flow path is indicative of the manner in which backup data sets that correspond to the backup set metadata entries flow through the processing flow path of the backup storage system.

5. The method of claim 1 further comprising:

determining a plurality of backup set metadata entries of the backup set metadata are in a processing state of the two or more potential processing states;

determining one or more software agents operating on the plurality of backup set metadata entries at the potential processing state; and

determining which backup set metadata entries of the plurality of backup set metadata entries are being operated on by each of the one or more software agents.

6. The method of claim 5 further comprising determining a statistic for each of the one or more backup agents, wherein the statistic comprises at least one of (i) a number of backup set metadata entries of the backup set metadata associated with the backup agent, (ii) a compression statistic for the backup agent, (iii) a deduplication statistic for the backup agent, or (iv) logical data size for the backup agent.

7. The method of claim 5 further comprising:

determining a number of backup set metadata entries of backup set metadata associated with a software agent are above a predetermined threshold; and

identifying a fault with the number of backup set metadata entries based on a reason code associated with each of the number of backup set metadata entries, wherein the fault is indicative of why the number of backup set metadata entries are being slowly processed at a particular state in the emulated processing flow path.

8. The method of claim 1 further comprising:

storing historical data indicative of the manner in which the backup set metadata was processed through the emulated processing flow path;

identifying, based on the historical data, one or more growth factors for the emulating computing device; and

predicting a future characteristic of the backup storage system based on the one or more growth factors.

9. The method of claim 8 wherein the historical data comprises at least one of (i) one or more client specific settings or (ii) one or more performance metrics of the emulating computing device, wherein the one or more performance metrics are indicative of a performance of the backup storage system.

10. The method of claim 9 wherein the one or more client specific settings comprises an expiration time for one or more backup set metadata entries of the backup set metadata, wherein the expiration time is indicative of an expiration time for a corresponding backup data set stored by the backup storage system, and the one or more performance metrics comprises a deduplication performance metric indicative of a success rate for identifying duplicate data in new backup data sets that is already in stored backup data sets such that the duplicate data is not stored by the backup storage system.

11. An apparatus for system monitoring, the apparatus comprising an emulating computing device with a processor and memory configured to:

receive backup set metadata, wherein the backup set metadata comprises information about backup data sets that are received by a backup storage system that stores the backup data sets; and

emulate the manner in which data within the backup data sets flow through a processing flow path of the backup storage system comprising:

execute one or more processes that process the backup set metadata through an emulated processing flow path, wherein the one or more processes are also implemented in the backup storage system to process the backup data sets through the processing flow path;

determine two or more potential processing states within the emulated processing flow path;

determine a reason code for each backup set metadata entry of the backup set metadata indicative of reason that the backup set metadata entry is in a processing state of the two or more potential processing states; and

identify a problem with the manner in which the backup set metadata is flowing through the emulated processing flow path based on the reason codes.

12. The apparatus of claim 11 wherein the computing device is further configured to determine the reason codes based on one or more factors comprising at least one of (i) an expected quantity of data at the processing state, (ii) a processing error at the processing state, or (iii) a backup customer's configuration of the backup storage system.

13. The apparatus of claim 12 wherein the computing device is further configured to process the backup set metadata through the emulated processing flow path, wherein a plurality of backup set metadata entries of the backup set metadata are in a corresponding processing state of the emulated processing flow path before the plurality of backup set metadata entries are completely processed through the emulated processing flow path.

14. The apparatus of claim 11 wherein the computing device is further configured to monitor the manner in which backup set metadata entries of the backup set metadata are processed through a portion of the emulated processing flow path, wherein the emulated processing flow path is indicative of the manner in which backup data sets that correspond to the backup set metadata entries of the backup set metadata flow through the processing flow path of the backup storage system.

15. The apparatus of claim 11 wherein the computing device is further configured to:

determine a plurality of backup set metadata entries of backup set metadata are in a processing state of the two or more potential processing states;

determine one or more software agents operating on the plurality of backup set metadata entries at the potential processing state; and

determine which backup set metadata entries of the plurality of backup set metadata entries are being operated on by each of the one or more software agents.

16. The apparatus of claim 15 wherein the computing device is further configured to determine a statistic for each of the one or more software agents, wherein the statistic comprises at least one of (i) a number of backup set metadata entries of the backup set metadata associated with the software agent, (ii) a compression statistic for the software agent, or (iii) a deduplication statistic for the software agent.

17. The apparatus of claim 15 wherein the computing device is further configured to:

determine a number of backup set metadata entries of the backup set metadata associated with a software agent are above a predetermined threshold; and

identify a fault with the number of backup set metadata entries based on a reason code associated with each of the number of backup set metadata entries, wherein the fault is indicative of why the number of backup set metadata entries are being slowly processed at a particular state in the emulated processing flow path.

18. The apparatus of claim 11 wherein the computing device is further configured to:

store historical data indicative of the manner in which the backup set metadata was processed through the emulated processing flow path;

identify, based on the historical data, one or more growth factors for the emulating computing device; and

predict a future characteristic of the backup storage system based on the one or more growth factors.

19. The apparatus of claim 18 wherein the future characteristic comprises a future expected requirement of storage space to prevent the backup storage system from running out of storage space, a future required number of computer nodes for the backup storage system to support an expected processing requirement of the backup storage system, or any combination thereof.

20. A computer program product, tangibly embodied in a non-transitory computer readable medium, the computer program product including instructions being operable to cause a data processing apparatus to:

receive backup set metadata, wherein the backup set metadata comprises information about backup data sets that are received by a backup storage system that stores the backup data sets; and

emulate the manner in which data within the backup data sets flow through a processing flow path of the backup storage system comprising:

execute one or more processes that process the backup set metadata through an emulated processing flow path, wherein the one or more processes are also implemented in the backup storage system to process the backup data sets through the processing flow path;

determine two or more potential processing states within the emulated processing flow path;

determine a reason code for each backup set metadata entry of the backup set metadata indicative of reason that the backup set metadata entry is in a processing state of the two or more potential processing states; and

identify a problem with the manner in which the backup set metadata is flowing through the emulated processing flow path based on the reason codes.

Assignments (6)
MERGER Recorded Jan 28, 2020
From: HITACHI VANTARA CORPORATION
To: HITACHI VANTARA LLC
Reel/Frame 051719/0202 →
CHANGE OF NAME Recorded Feb 20, 2018
From: HITACHI DATA SYSTEMS CORPORATION
To: HITACHI VANTARA CORPORATION
Reel/Frame 045369/0785 →
MERGER Recorded Feb 9, 2017
From: SEPATON, INC.
To: HITACHI DATA SYSTEMS CORPORATION
Reel/Frame 041670/0829 →
RELEASE OF SECURITY INTEREST Recorded Aug 13, 2015
From: COMERICA BANK
To: SEPATON, INC.
Reel/Frame 036321/0462 →
SECURITY INTEREST Recorded Jun 19, 2014
From: SEPATON, INC.
To: COMERICA BANK
Reel/Frame 033202/0957 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 8, 2010
From: RIEGEL, JANE; CHERNOCH, JOHN
To: SEPATON, INC.
Reel/Frame 025479/0680 →