# US 2012/0254124 A1 · System, method, and computer program product for disaster recovery using asynchronous mirroring

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

- Number: US 2012/0254124 A1
- Document ID: US20120254124A1
- Status: Published application
- Kind: A1
- Application number: 13/076,024
- Filed: 2011-03-30
- Published: 2012-10-04
- Earliest claimed: 2011-03-30
- Assignees: International Business Machines Corporation
- Inventors: Lisa J. Gundy; Beth A. Peterson; Alfred E. Sanchez; David M. Shackelford; Warren K. Stanley; John G. Thompson
- Web page: https://patentgrep.com/patent/US20120254124A1

## CPC

- G06F 11/2074: {Asynchronous techniques}
- G06F 11/2064: {while ensuring consistency}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In one embodiment, a computer program product for handling a point-in-time copy (PITC) command includes a computer readable storage medium having computer readable program code embodied therewith. The computer readable program code is configured to: receive a PITC command at a local site, create a data representation that represents updates to make to the at least one target volume of the local target storage location, wherein the updates correspond to changes made to at least one source volume of the local source storage location since execution of an earlier PITC command, create a source data sidefile entry for the at least one source volume, create a target data sidefile entry for the at least one target volume, execute the PITC command at the local site, and create a PITC sidefile entry for the PITC command, the PITC sidefile entry including a timestamp that indicates when the PITC command was executed.

## Claims

### Claim 1

A computer program product for handling a point-in-time copy command, comprising a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to receive a point-in-time copy (PITC) command at a local site, the PITC command being for updating data on a local target storage location such that it represents data on a local source storage location;
computer readable program code configured to create a data representation that represents updates to be made to the at least one target volume of the local target storage location, wherein the updates correspond to changes made to at least one source volume of the local source storage location since execution of an earlier PITC command;
computer readable program code configured to create a source data sidefile entry for the at least one source volume;
computer readable program code configured to create a target data sidefile entry for the at least one target volume;
computer readable program code configured to execute the PITC command at the local site; and
computer readable program code configured to create a PITC sidefile entry for the PITC command, the PITC sidefile entry including a timestamp that indicates when the PITC command was executed.

### Claim 2 (depends on 1)

The computer program product as recited in claim 1, wherein the source data sidefile entry comprises:
the PITC command including parameters associated with the PITC command;
a timestamp indicating when the PITC command was executed;
one or more source data locations on the at least one source volume; and
one or more target data locations on the at least one target volume that correspond to the one or more source data locations.

### Claim 3 (depends on 1)

The computer program product as recited in claim 1, wherein the target data sidefile entry comprises:
the PITC command including parameters associated with the PITC command;
a timestamp indicating when the PITC command was executed;
a timestamp of a current time on the at least one target volume;
one or more source data locations on the at least one source volume; and
one or more target data locations on the at least one target volume that correspond to the one or more source data locations.

### Claim 4 (depends on 1)

The computer program product as recited in claim 1, further comprising computer readable program code configured to mark the target data sidefile entry and the source data sidefile entry as “in progress” prior to executing the PITC command.

### Claim 5 (depends on 1)

The computer program product as recited in claim 1, further comprising computer readable program code configured to mark the target data sidefile entry and the source data sidefile entry as “complete” after successfully executing the PITC command.

### Claim 6 (depends on 1)

The computer program product as recited in claim 1, wherein the data representation comprises at least one bitmap, wherein one bitmap for each target volume is used to represent updates that were made to a corresponding source volume, wherein each bit in the bitmap represents one track on the target volume.

### Claim 7 (depends on 1)

The computer program product as recited in claim 1, further comprising:
computer readable program code configured to receive information for mapping the local source storage location to a remote source storage location, wherein data and data locations on the remote source storage location correspond to data and data locations on the local source storage location;
computer readable program code configured to receive information for mapping the local target storage location to a remote target storage location, wherein data and data locations on the remote target storage location correspond to data and data locations on the local target storage location;
computer readable program code configured to map the local source storage location to the corresponding remote source storage location; and
computer readable program code configured to map the local target storage location to the remote target storage location.

### Claim 8

A method for handling a point-in-time copy command, the method comprising:
receiving a point-in-time copy (PITC) command at a local site, the PITC command being for updating data on a local target storage location such that it represents data on a local source storage location;
creating a PITC sidefile entry for the PITC command, the PITC sidefile entry including a timestamp that indicates when the PITC command was executed;
creating a data representation that represents updates to be made to the at least one target volume of the local target storage location, wherein the updates correspond to changes made to at least one source volume of the local source storage location since execution of an earlier PITC command;
creating a source data sidefile entry for the at least one source volume;
creating a target data sidefile entry for the at least one target volume; and
executing the PITC command at the local site.

### Claim 9 (depends on 8)

The method as recited in claim 8, wherein the source data sidefile entry comprises:
the PITC command including parameters associated with the PITC command;
a timestamp indicating when the PITC command was executed;
one or more source data locations on the at least one source volume; and
one or more target data locations on the at least one target volume that correspond to the one or more source data locations.

### Claim 10 (depends on 8)

The method as recited in claim 8, wherein the target data sidefile entry comprises:
the PITC command including parameters associated with the PITC command;
a timestamp indicating when the PITC command was executed;
a timestamp of a current time on the at least one target volume;
one or more source data locations on the at least one source volume; and
one or more target data locations on the at least one target volume that correspond to the one or more source data locations.

### Claim 11 (depends on 8)

The method as recited in claim 8, further comprising marking the target data sidefile entry and the source data sidefile entry as “in progress” prior to executing the PITC command.

### Claim 12 (depends on 8)

The method as recited in claim 8, further comprising marking the target data sidefile entry and the source data sidefile entry as “complete” after successfully executing the PITC command.

### Claim 13 (depends on 8)

The method as recited in claim 8, wherein the data representation comprises at least one bitmap.

### Claim 14 (depends on 13)

The method as recited in claim 13, wherein one bitmap for each target volume is used to represent updates that were made to a corresponding source volume, wherein each bit in the bitmap represents one track on the target volume.

### Claim 15 (depends on 8)

The method as recited in claim 8, further comprising:
receiving information for mapping the local source storage location to a remote source storage location, wherein data and data locations on the remote source storage location correspond to data and data locations on the local source storage location; and
receiving information for mapping the local target storage location to a remote target storage location, wherein data and data locations on the remote target storage location correspond to data and data locations on the local target storage location.

### Claim 16 (depends on 15)

The method as recited in claim 15, further comprising:
mapping the local source storage location to the corresponding remote source storage location; and
mapping the local target storage location to the remote target storage location.

### Claim 17

A system for storing disaster recovery data, the system comprising:
logic adapted for gathering source sidefile entries from one or more source sidefiles at a local site, wherein the one or more source sidefiles correspond to one or more local source storage locations;
logic adapted for detecting a point-in-time copy (PITC) command entry in one of the source sidefiles;
logic adapted for sorting the gathered source sidefile entries chronologically by timestamp, wherein source sidefile entries having an earlier timestamp are arranged prior to source sidefile entries having a later timestamp;
logic adapted for forming a first consistency group (CG) based on sidefile entries that have a timestamp prior to a timestamp of the PITC command entry;
logic adapted for forming a second CG based on the PITC command entry;
logic adapted for applying the first CG to one or more remote source storage locations at a remote site, wherein the one or more remote source storage locations correspond to the one or more local source storage locations; and
logic adapted for applying the second CG to one or more remote target storage locations at the remote site after applying the first CG, wherein the one or more remote target storage locations correspond to the one or more local target storage locations.

### Claim 18 (depends on 17)

The system as recited in claim 17, wherein the first CG is split into several smaller CGs, each smaller CG being based on chronological portions of the sidefile entries that have a timestamp prior to a timestamp of the PITC command entry, and wherein the smaller CGs are applied to the one or more remote source storage locations chronologically.

### Claim 19 (depends on 17)

The system as recited in claim 17, wherein the first CG is applied to the one or more remote source storage locations in parallel processes.

### Claim 20

A method for storing disaster recovery data, the method comprising:
gathering source sidefile entries from one or more source sidefiles at a local site, wherein the one or more source sidefiles correspond to one or more local source storage locations;
detecting a point-in-time copy (PITC) command entry in one of the source sidefiles;
sorting the gathered source sidefile entries chronologically by timestamp, wherein source sidefile entries having an earlier timestamp are arranged prior to source sidefile entries having a later timestamp;
forming a first consistency group (CG) based on sidefile entries that have a timestamp prior to a timestamp of the PITC command entry;
forming a second CG based on the PITC command entry;
applying the first CG to one or more remote source storage locations at a remote site, wherein the one or more remote source storage locations correspond to the one or more local source storage locations; and
applying the second CG to one or more remote target storage locations at the remote site after applying the first CG, wherein the one or more remote target storage locations correspond to the one or more local target storage locations.

### Claim 21 (depends on 20)

The method as recited in claim 20, wherein the first CG is split into several smaller CGs, each smaller CG being based on chronological portions of the sidefile entries that have a timestamp prior to a timestamp of the PITC command entry, and wherein the smaller CGs are applied to the one or more remote source storage locations chronologically.

### Claim 22 (depends on 20)

The method as recited in claim 20, wherein the first CG is applied to the one or more remote source storage locations in parallel processes.
