# US 10,481,807 B2 · Status for generated data image

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,481,807 B2
- Document ID: US10481807B2
- Status: Granted
- Kind: B2
- Application number: 15/535,828
- Filed: 2014-12-22
- Published: 2017-12-07
- Granted: 2019-11-19
- Earliest claimed: 2014-12-22
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Melvin K. Benedict; Lidia Warnes
- Web page: https://patentgrep.com/patent/US10481807B2

## CPC

- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 1/30: Means for acting in the event of power-supply failure or interruption, e.g. power-supply fluctuations (for resetting only G06F1/24)
- G06F 11/1441: {Resetting or repowering}
- G06F 11/1469: {Backup restoration techniques}
- G06F 11/3058: {Monitoring arrangements for monitoring environmental properties or parameters of the computing system or of the computing system component, e.g. monitoring of power, currents, temperature, humidity, position, vibrations (thermal management in cooling arrangements of a computing system G06F1/206)}
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F 2201/86: Event-based monitoring
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Example implementations relate to generating statuses for data images. In example implementations, an event, in response to which a save operation is initiated on a memory module, may be identified. A data image may be generated during the save operation. A status may be generated for the generated data mage. The status may include an event portion indicative of the identified event, and a completion portion indicative of whether the save operation was completed.

## Claims

### Claim 1

A system comprising:
a save operation initiator to initiate save operations on a memory module, wherein a respective data image is generated during each save operation;
an event identifier to identify a respective event in response to which each save operation is initiated;
a status generator to generate a respective status for each generated data image, each status comprising:
an event portion indicative of the respective event in response to which the respective save operation, during which the respective data image was generated, was initiated; and
a completion portion indicative of whether the respective save operation, during which the respective data image was generated, was completed; and
a non-volatile memory to store each respective generated status and data image; and wherein:
the non-volatile memory is a first non-volatile memory; and
generated data images are generated based on a second non-volatile memory on the memory module.

### Claim 2 (depends on 1)

The system of claim 1, further comprising a verifier to verify self-consistency of each status.

### Claim 3 (depends on 1)

The system of claim 1, wherein the respective status for a generated data image is embedded in the generated data image.

### Claim 4 (depends on 1)

The system of claim 1, wherein the respective status for a generated data image is stored in a first region of the non-volatile memory, and the generated data image is stored in a second region of the non-volatile memory.

### Claim 5 (depends on 1)

The system of claim 1, wherein generated data images are generated based on a volatile memory on the memory module.

### Claim 6 (depends on 1)

The system of claim 1, wherein each event portion is further indicative of whether data in the respective data image is valid.

### Claim 7

A non-transitory machine-readable storage medium encoded with instructions executable by a processor, the machine-readable storage medium comprising:
instructions to identify an event in response to which a save operation is initiated on a memory module, wherein a data image is generated during the save operation based on a first non-volatile memory on the memory module; and
instructions to generate a status for the generated data image, the status comprising:
an event portion indicative of the identified event; and
a completion portion indicative of whether the save operation was completed; and
instructions to store the generated status and data image in a second non-volatile memory.

### Claim 8 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein the event portion is further indicative of whether data in the data image is valid.

### Claim 9

A method comprising:
identifying an event in response to which a save operation is initiated on a memory module, wherein a data image is generated during the save operation based on a first non-volatile memory on the memory module;
generating a status for the generated data image, the status comprising:
an event portion indicative of the identified event; and
a completion portion indicative of whether the save operation was completed; and
storing the generated status and data image in a second non-volatile memory.

### Claim 10 (depends on 9)

The method of claim 9, further comprising embedding the status in the data image.

### Claim 11 (depends on 9)

The method of claim 9, further comprising:
retrieving the status when the memory module is rebooted;
determining, based on the completion portion, whether the save operation was completed;
identifying, if it is determined that the save operation was not completed, a previous data image that was generated during a previous save operation that was completed; and
restore, based on the identified previous data image, a state of the memory module.

### Claim 12 (depends on 9)

The method of claim 9, wherein the event portion is further indicative of whether data in the data image is valid.