Self-healing for data protection systems using automatic macro recording and playback

Patent metadata

Field	Value
Publication number	US-12530268-B2
Application number	US-202217751344-A
Country	US
Kind code	B2
Filing date	May 23, 2022
Priority date	Apr 21, 2021
Publication date	Jan 20, 2026
Grant date	Jan 20, 2026

Abstract

Embodiments for executing selected remediation scripts to remedy issues in a data storage system through an API/script recorder component or process that presents a DVR (digital video recorder)-like interface and capability to capture scripts and API calls as they are used when navigating a graphical user interface (GUI). Internal components of this function perform the recording and macro creation to allow constant playback of these recorded and selected scripts. By easily generating and managing scripts macros, system administrators can easily re-execute customer workflows to apply known fixes to current issues in the data storage system.

First claim

What is claimed is:

1 . A method of recording and playing back command scripts for correcting issues in a data protection system, comprising:
storing, in a remediation database, scripts comprising command sequences correcting one or more issues previously encountered in the data protection system; analyzing metadata associated with a present issue of the data protection system; selecting a script from among the stored scripts to correct the present issue, wherein the issues comprise at least one of: a problem associated with identifying a data asset to be backed up, a problem associated with identifying a storage target to store backed up data, a problem associated with a source of the data to be backed up, or a problem associated with a backup or restore command operating on the data asset to be backed up; and allowing automated playback of the selected script by the data protection system, wherein the metadata provides appropriate values for a current execution of the selected script, wherein the metadata comprises initial metadata describing at least one of the data source, storage target, or data asset, and further comprises second metadata for backup console metrics including error messages, device and asset identifiers, and log entries for previous issues, and further wherein the initial and second metadata are used to select the script from among the stored scripts to correct the present issue, and further wherein the selected script substitutes one or more parameters specifying information unique to the data protection system into an application program interface (API) recording and playback process.

2 . The method of claim 1 wherein the present issue comprises at least one of: specifying a non-existent device, specifying a non-accessible device, attempting execution of a non-existent command, or specifying a mis-typed command.

3 . The method of claim 1 wherein the API recording and playback process comprises:
capturing all API function calls of one or more APIs of a target product sequence upon initiation of a recording operation by a user;
storing a recorded macro in a macro store;
generating, in response to a user request to playback the recorded macro, a call graph defining an execution sequence of one or more APIs of the recorded macro;
prompting the user to input any missing or required API values; and
executing the recorded macro using the call graph and user input values.

4 . The method of claim 3 wherein the call graph comprises calls between the one or more APIs that depend upon inputs which are derived from one or more outputs of the higher level API calls in a hierarchy, and wherein the call graph further comprises a set of connected vertices, wherein all the edges are directed from one vertex to another, each graph vertex describes each function call while each graph edge describes how to map output data from a parent API call to input data into each subsequent API call, and further wherein inputs for APIs subsequent to the root API are determined using current state inputs to each API, or a walk back through earlier APIs using the call graph.

5 . The method of claim 1 wherein the present issue is identified by one of a user entry of an encountered problem, or automatic detection of the encountered problem by an issue detection process.

6 . A method of remedying problems in a data protection system, comprising:
detecting a current problem occurring while processing a dataset operated on by the data protection system; deriving attributes associated with a present operation causing the current problem from metadata associated with data assets and data processing components processing the dataset; comparing the derived attributes with attributes stored in a remediation database for previous problems encountered in the data protection system, wherein the attributes are provided as part of a command execution script; determining a most closely matching script from the mediation database for the current problem based on a comparison of respective attributes; and executing the most closely matching script in a command execution process.

7 . The method of claim 6 further comprising associating a list of attributes with each of the present operation and past operations causing the previous problems, and wherein the remediation database stores an entry for each remediation script that includes a list of attributes that the respective script affects.

8 . The method of claim 7 further comprising:
comparing respective attributes of the present operation against scripts for each of the past operations;
calculating an affinity score for each of the past operations based on a number of matching attributes in the comparing step; and
selecting a script with the highest affinity score to be the most closely matching script.

9 . The method of claim 6 wherein the current and previous problems comprise at least one of: a problem associated with identifying a data asset to be backed up, a problem associated with identifying a storage target to store backed up data, a problem associated with a source of the data to be backed up, or a problem associated with a backup or restore command operating on the data asset to be backed up, and further wherein the current problem comprises at least one of: specifying a non-existent device, specifying a non-accessible device, attempting execution of a non-existent command, or specifying a mis-typed command.

10 . A method of recording and playing back issue remediation scripts in an application program interface (API) recording and playback process in a data protection system, comprising:
capturing all API function calls of one or more APIs of a target product sequence upon initiation of a recording operation by a user; storing a recorded macro in a macro store; generating, in response to a user request to playback the recorded macro, a call graph defining an execution sequence of one or more APIs of the recorded macro; storing, in a remediation database, scripts comprising command sequences correcting one or more issues previously encountered in the data protection system; selecting a script from among the stored scripts to correct a present issue; substituting one or more parameters specifying information unique to the data protection system in place of the API function calls; and allowing automated playback of the selected script by the data protection system.

11 . The method of claim 10 wherein the one or more parameters comprise identifiers for at least one of: datasets to be protected, and devices sourcing or storing the datasets to be protected.

12 . The method of claim 11 wherein the one or more issues comprise at least one of: a problem associated with identifying a data asset to be backed up, a problem associated with identifying a storage target to store backed up data, a problem associated with a source of the data to be backed up, or a problem associated with a backup or restore command operating on the data asset to be backed up.

13 . The method of claim 12 wherein the present issue is identified by one of: an automated issue detection process or user specified issue, and wherein the present issue comprises at least one of: specifying a non-existent device, specifying a non-accessible device, attempting execution of a non-existent command, or specifying a mis-typed command.

14 . The method of claim 11 wherein the selecting step comprises utilizing metadata including metadata describing at least one of the data source, storage target, or data asset, and metadata
for backup console metrics including error messages, device and

Assignees

• Dell Products Lp

Inventors

• Minarik Jennifer M
• Malamut Mark
• Freeman Brian E
• Brenner Adam
• Murti Arun

Classifications

• G06F9/544

  Buffers; Shared memory; Pipes · CPC title

• G06F16/215

  Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors · CPC title

• G06F2201/84

  Using snapshots, i.e. a logical point-in-time copy of the data · CPC title

• G06F2201/865

  Monitoring of software · CPC title

• G06F11/3466

  Performance evaluation by tracing or monitoring · CPC title