# US 2021/0342179 A1 · Application recovery using a memory image

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

- Number: US 2021/0342179 A1
- Document ID: US20210342179A1
- Status: Published application
- Kind: A1
- Application number: 17/067,370
- Filed: 2020-10-09
- Published: 2021-11-04
- Earliest claimed: 2020-04-29
- Assignees: Memverge, Inc.
- Applicants: MemVerge, Inc.
- Inventors: Ronald S. Niles; Yue Li; Jun Gan; Chenggong Fan; Robert W. Beauchamp; Dahong Li
- Web page: https://patentgrep.com/patent/US20210342179A1

## CPC

- G06F 11/1438: {Restarting or rejuvenating}
- G06F 11/1469: {Backup restoration techniques}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/0655: {Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices}
- G06F 3/0656: {Data buffering arrangements}
- G06F 3/0667: {at data level, e.g. file, record or object virtualisation}
- G06F 3/0676: {Magnetic disk device}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F 9/461: {Saving or restoring of program or task context}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1471: involving logging of persistent data for recovery
- G06F 11/1474: in transactions (updating of structured data in databases G06F16/23)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A memory image can be captured by generating metadata indicative of a state of volatile memory and/or byte-addressable PMEM at a particular time during execution of a process by an application. This memory image can be persisted without copying the in-memory data into a separate persistent storage by storing the metadata and safekeeping the in-memory data in the volatile memory and/or PMEM. Metadata associated with multiple time-evolved memory images captured can be stored and managed using a linked index scheme. A linked index scheme can be configured in various ways including a full index and a difference-only index. The memory images can be used for various purposes including suspending and later resuming execution of the application process, restoring a failed application to a previous point in time, cloning an application, and recovering an application process to a most recent state in an application log.

## Claims

### Claim 1

A method for recovering an application process, the method comprising:
accessing a memory image, the memory image captured at a first time during execution of the application process;
restoring the application process to a restore point based on the memory image;
generating a catch-up log based on a full log associated with the application process, the full log including records indicative of the execution of the application process up to a second time that is later than the first time, the catch-up log including a subset of the records from the full log that are beyond the restore point; and
causing the application process to replay the catch-up log.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
generating a restore log based on the full log, the restore log including a second subset of the records from the full log up to the first time.

### Claim 3 (depends on 2)

The method of claim 2, wherein the application process is restored to the restore point based on the restore log.

### Claim 4 (depends on 2)

The method of claim 2, wherein restoring the application to the restore point includes:
restoring the application to an initial restore point using the memory image and the restore log;
enabling the application process to execute from the initial restore point to a quiesced state; and
updating the restore log based on the execution of the application process to the quiesced state.

### Claim 5 (depends on 2)

The method of claim 2, wherein generating the restore log includes:
copying the full log at the first time when the memory image is captured; and/or
copying the full log after the memory image is captured and truncating the full log to include only the second subset of the records up to the first time.

### Claim 6 (depends on 2)

The method of claim 2, wherein the restore point is at the quiesced state.

### Claim 7 (depends on 2)

The method of claim 2, wherein enabling the application process to execute to the quiesced state includes:
enabling the application to complete execution of an operation that was in-progress and/or in a queue at the time the memory image was captured.

### Claim 8 (depends on 7)

The method of claim 7, wherein updating the restore log includes:
adding a record indicative of execution of the operation to the restore log.

### Claim 9 (depends on 1)

The method of claim 1, wherein generating the catch-up log includes:
copying the subset of records from the full log into the catch-up log.

### Claim 10 (depends on 1)

The method of claim 1, wherein causing the application process to replay the catch-up log includes causing the application process to execute one or more operations indicated in the subset of records included in the catch-up log.

### Claim 11 (depends on 1)

The method of claim 1, wherein causing the application process to replay the catch-up log does not include causing the application to replay any operations indicated in records in the full log that are before the restore point.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
isolating the application process from one or more network connections before restoring the application process to the restore point;
determining that the application process has completed replaying the catch-up log; and
reconnecting the application process to the one or more network connections in response to determining that the application process has completed replaying the catch-up log.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
enabling an application to use persistent memory (PMEM) as volatile-mode memory to store and access in-memory data during execution of the application process;
wherein the memory image is captured by safekeeping, in the PMEM, a particular state of the in-memory data as it exists at the first time.

### Claim 14 (depends on 13)

The method of claim 13, wherein safekeeping the particular state of the in-memory data includes preventing modification of the in-memory data from the particular state to a new state until at least the application process has completed execution.

### Claim 15 (depends on 14)

The method of claim 14, wherein preventing modification of the in-memory data includes setting write protection in mappings between a logical address space of the application and the PMEM.

### Claim 16 (depends on 13)

The method of claim 13, wherein enabling the application to use the PMEM as volatile-mode memory includes:
virtualizing a memory object as anonymous byte-addressable memory for use by the application.

### Claim 17 (depends on 16)

The method of claim 16, wherein the memory object is a distributed memory object.

### Claim 18 (depends on 1)

The method of claim 1,
wherein the memory image is one of a plurality of memory images captured at different times during execution of the application process; and
wherein the plurality of memory images are managed using a linked difference-only index and/or a linked full-index.

### Claim 19

A non-transitory computer-readable medium storing instructions, execution of which in a computer system, causes the computer system to perform operations including:
accessing a memory image, the memory image captured at a first time during execution of an application process;
restoring the application process to a restore point based on the memory image;
generating a catch-up log based on a full log associated with the application process, the full log including records indicative of the execution of the application process up to a second time that is later than the first time, the catch-up log including a subset of the records from the full log that are beyond the restore point; and
causing the application process to replay the catch-up log.

### Claim 20

A system comprising:
a processor; and
a memory having instructions stored thereon, which when executed by the processor, cause the computer system to:
access a memory image, the memory image captured at a first time during execution of an application process;
restore the application process to a restore point based on the memory image;
generate a catch-up log based on a full log associated with the application process, the full log including records indicative of the execution of the application process up to a second time that is later than the first time, the catch-up log including a subset of the records from the full log that are beyond the restore point; and
cause the application process to replay the catch-up log.
