# US 2019/0294506 A1 · Copying data from multiple point-in-time copies to a log storage to use to roll-back a source storage

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

- Number: US 2019/0294506 A1
- Document ID: US20190294506A1
- Status: Published application
- Kind: A1
- Application number: 16/440,975
- Filed: 2019-06-13
- Published: 2019-09-26
- Earliest claimed: 2016-11-17
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Theresa M. Brown; Nicolas M. Clayton; Gregory E. McBride; Carol S. Mellgren; David C. Reed
- Web page: https://patentgrep.com/patent/US20190294506A1

## CPC

- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 11/1471: involving logging of persistent data for recovery
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Provided are a computer program product, system, and method for copying data from multiple point-in-time copies to a log storage to use to roll-back a source storage managing point-in-time copies of a source storage. A plurality of point-in-time copies of a source storage at different point-in-times are established. In response to receiving writes to the source storage after establishing each of the point-in-time copies, point-in-time data in the source storage is copied, before being updated by the received writes, to a log storage, wherein the log storage stores point-in-time data for multiple of the point-in-time copies. The log storage is used to roll-back the source storage to a selected point-in-time of one of the point-in-time copies.

## Claims

### Claim at position 1

1-23. (canceled)

### Claim 24

A computer program product for managing point-in-time copies of a source storage, wherein the computer program product comprises a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause operations, the operations comprising:
storing point-in-time data for multiple point-in-time copies of a source storage in a log storage;
receiving a write to the source storage having an active point-in-time copy;
copying point-in-time data in the source storage to be overwritten by the received write to the log storage; and so
using the log storage to roll-back the source storage to a selected point-in-time of one of the point-in-time copies.

### Claim 25 (depends on 24)

The computer program product of claim 24, wherein the operations further comprise:
determining whether point-in-time copy information for the source storage indicates a target storage or the log storage for the point-in-time data, wherein the point-in-time data is copied to the source storage in response to determining that the point-in-time copy information indicates the log storage for the point-in-time data; and
copying the point-in-time data to the target storage in response to determining that the point-in-time copy information indicates the target storage for the point-in-time data.

### Claim 26 (depends on 24)

The computer program product of claim 24, wherein the point-in-time data is written to the log storage at sequential storage locations in an order in which the point-in-time data was updated at the source storage.

### Claim 27 (depends on 24)

The computer program product of claim 24, wherein the operations further comprise:
for each of the point-in-time copies, maintaining recovery metadata indicating locations in the log storage having point-in-time data for a point-in-time copy, wherein the using the log storage to roll-back the source storage comprises copying the point-in-time data to the source storage from a first location through a last location in the log storage indicated in the recovery metadata for the selected point-in-time to roll-back the source storage.

### Claim 28 (depends on 24)

The computer program product of claim 24, wherein the selected point-in-time is for a previous point-in-time, wherein using the log storage to roll-back the source storage to the previous point-in-time comprises:
copying, to a recovery storage, the point-in-time data in the log storage from a most recent point-in-time copy to the selected point-in-time copy in sequential reverse order.

### Claim 29 (depends on 28)

The computer program product of claim 28, wherein the operations further comprise:
indicating, in a change recording data structure, that storage locations in the recovery storage to which the point-in-time data was applied have been updated.

### Claim 30 (depends on 24)

The computer program product of claim 24, wherein the operations further comprise:
iteratively creating recovery point-in-time copies of the source storage for recovery point-in-times by applying, to a recovery storage for each of the recovery point-in-time copies, the point-in-time data in the log storage from point-in-time copies for points-in-time greater than and equal to one of the recovery point-in-times to determine one of the recovery point-in-time copies having valid data in the recovery storage as of a determined recovery point-in-time between two recovery point-in-time copies having invalid data; and
applying the point-in-time data from the recovery storage for the determined recovery point-in-time copies to the source storage to return to the determined recovery point-in-time at which the source storage had valid data.

### Claim 31

A system for managing point-in-time copies of a source storage, comprising:
processor; and
a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause operations, the operations comprising:
storing point-in-time data for multiple point-in-time copies of a source storage in a log storage;
receiving a write to the source storage having an active point-in-time copy;
copying point-in-time data in the source storage to be overwritten by the received write to the log storage; and so
using the log storage to roll-back the source storage to a selected point-in-time of one of the point-in-time copies.

### Claim 32 (depends on 31)

The system of claim 31, wherein the operations further comprise:
determining whether point-in-time copy information for the source storage indicates a target storage or the log storage for the point-in-time data, wherein the point-in-time data is copied to the source storage in response to determining that the point-in-time copy information indicates the log storage for the point-in-time data; and
copying the point-in-time data to the target storage in response to determining that the point-in-time copy information indicates the target storage for the point-in-time data.

### Claim 33 (depends on 31)

The system of claim 31, wherein the point-in-time data is written to the log storage at sequential storage locations in an order in which the point-in-time data was updated at the source storage.

### Claim 34 (depends on 31)

The system of claim 31, wherein the operations further comprise:
for each of the point-in-time copies, maintaining recovery metadata indicating locations in the log storage having point-in-time data for a point-in-time copy, wherein the using the log storage to roll-back the source storage comprises copying the point-in-time data to the source storage from a first location through a last location in the log storage indicated in the recovery metadata for the selected point-in-time to roll-back the source storage.

### Claim 35 (depends on 31)

The system of claim 31, wherein the selected point-in-time is for a previous point-in-time, wherein using the log storage to roll-back the source storage to the previous point-in-time comprises:
copying, to a recovery storage, the point-in-time data in the log storage from a most recent point-in-time copy to the selected point-in-time copy in sequential reverse order.

### Claim 36 (depends on 35)

The system of claim 35, wherein the operations further comprise:
indicating, in a change recording data structure, that storage locations in the recovery storage to which the point-in-time data was applied have been updated.

### Claim 37 (depends on 31)

The system of claim 31, wherein the operations further comprise:
iteratively creating recovery point-in-time copies of the source storage for recovery point-in-times by applying, to a recovery storage for each of the recovery point-in-time copies, the point-in-time data in the log storage from point-in-time copies for points-in-time greater than and equal to one of the recovery point-in-times to determine one of the recovery point-in-time copies having valid data in the recovery storage as of a determined recovery point-in-time between two recovery point-in-time copies having invalid data; and
applying the point-in-time data from the recovery storage for the determined recovery point-in-time copies to the source storage to return to the determined recovery point-in-time at which the source storage had valid data.

### Claim 38

A method for managing point-in-time copies of a source storage, comprising:
storing point-in-time data for multiple point-in-time copies of a source storage in a log storage;
receiving a write to the source storage having an active point-in-time copy;
copying point-in-time data in the source storage to be overwritten by the received write to the log storage; and so
using the log storage to roll-back the source storage to a selected point-in-time of one of the point-in-time copies.

### Claim 39 (depends on 38)

The method of claim 38, further comprising:
determining whether point-in-time copy information for the source storage indicates a target storage or the log storage for the point-in-time data, wherein the point-in-time data is copied to the source storage in response to determining that the point-in-time copy information indicates the log storage for the point-in-time data; and
copying the point-in-time data to the target storage in response to determining that the point-in-time copy information indicates the target storage for the point-in-time data.

### Claim 40 (depends on 38)

The method of claim 38, further comprising, wherein the point-in-time data is written to the log storage at sequential storage locations in an order in which the point-in-time data was updated at the source storage.

### Claim 41 (depends on 38)

The method of claim 38, further comprising, further comprising:
for each of the point-in-time copies, maintaining recovery metadata indicating locations in the log storage having point-in-time data for a point-in-time copy, wherein the using the log storage to roll-back the source storage comprises copying the point-in-time data to the source storage from a first location through a last location in the log storage indicated in the recovery metadata for the selected point-in-time to roll-back the source storage.

### Claim 42 (depends on 38)

The method of claim 38, further comprising wherein the selected point-in-time is for a previous point-in-time, wherein using the log storage to roll-back the source storage to the previous point-in-time comprises:
copying, to a recovery storage, the point-in-time data in the log storage from a most recent point-in-time copy to the selected point-in-time copy in sequential reverse order.

### Claim 43 (depends on 42)

The method of claim 42, further comprising:
indicating, in a change recording data structure, that storage locations in the recovery storage to which the point-in-time data was applied have been updated.
