# US 2005/0240632 A1 · System and method for facilitating a consistent point-in time copy

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

- Number: US 2005/0240632 A1
- Document ID: US20050240632A1
- Status: Published application
- Kind: A1
- Application number: 10/831,096
- Filed: 2004-04-23
- Published: 2005-10-27
- Earliest claimed: 2004-04-23
- Assignees: Oracle America, Inc.
- Inventors: Brian Wong; David Robinson; Richard McDougall; Spencer Shepler
- Web page: https://patentgrep.com/patent/US20050240632A1

## CPC

- G06F 16/128: {Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system and method for facilitating a consistent point-in-time copy (PITC). A data provider offers access to data by one or more clients. A client issues a PITC request for a set of data to the data provider, or the provider initiates its own request. The data provider instructs one or more clients, particularly clients accessing the set of data, to flush any pending updates involving the files. The clients acknowledge the flush request, flush their data, and notify the data provider when their flushes are complete. Post-consistency updates are deferred (e.g., using a write-aside buffer). If a client fails to acknowledge the flush request or notify of flush completion, the data provider may abort the PITC or continue because the data may not be consistent or consistency may not be assured. If not aborted, the PITC may be marked to indicate that it is incomplete.

## Claims

### Claim 1

An automated method of facilitating a consistent point-in-time copy of a set of data, the method comprising:
receiving from an issuing client a request to perform a point-in-time copy of a specified dataset;
requesting a set of clients, including the issuing client, to flush updates to the dataset that were pending as of a specified consistency point;
receiving from a first client a first notification that the flushing of pending updates has been completed;
deferring one or more updates to the dataset that were generated after said consistency point; and
if notifications of completion of the flushing of pending updates are not received from each client in the set of clients within a threshold period of time, determining whether to abort the point-in-time copy.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving from the first client a first acknowledgement of the request to flush pending updates to the dataset.

### Claim 3 (depends on 1)

The method of claim 1, wherein the request to perform a point-in-time copy indicates behavior to be applied if one or more clients fail to send notifications of completion of the flushing of pending updates to the dataset.

### Claim 4 (depends on 1)

The method of claim 1, wherein the request to perform a point-in-time copy indicates behavior to be applied if one or more clients fail to acknowledge the request to flush pending updates to the dataset.

### Claim 5 (depends on 1)

The method of claim 1, wherein the request to perform a point-in-time copy identifies the specified consistency point.

### Claim 6 (depends on 1)

The method of claim 1, wherein the specified consistency point is specified by the issuing client.

### Claim 7 (depends on 1)

The method of claim 1, wherein the specified consistency point is selected by a data provider that receives said request to perform a point-in-time copy.

### Claim 8 (depends on 1)

The method of claim 1, wherein the set of clients includes some or all clients that have the dataset open at the time of the request to perform a point-in-time copy.

### Claim 9 (depends on 1)

The method of claim 1, wherein said deferring comprises, at a client:
receiving an update to the dataset after the specified consistency point; and
storing said update until notification of completion of the flushing of pending updates is sent.

### Claim 10 (depends on 1)

The method of claim 1, wherein said deferring comprises, at a data provider configured to receive the request to perform a point-in-time copy:
receiving an update to the dataset after said first notification from the first client is received; and
storing said update until the point-in-time copy is performed.

### Claim 11 (depends on 1)

The method of claim 1, wherein the point-in-time copy is performed on a data provider providing a means of access to the dataset by the set of clients.

### Claim 12 (depends on 1)

The method of claim 1, wherein the point-in-time copy is performed by a service operating on multiple data providers providing access to the dataset by the set of clients.

### Claim 13 (depends on 1)

The method of claim 1, further comprising acknowledging said first notification.

### Claim 14

A computer readable medium storing instructions that, when executed by a computer, cause the computer to perform a method of facilitating a consistent point-in-time copy of a set of data, the method comprising:
receiving from an issuing client a request to perform a point-in-time copy of a specified dataset;
requesting a set of clients, including the issuing client, to flush updates to the dataset that were pending as of a specified consistency point;
receiving from a first client a first notification that the flushing of pending updates has been completed;
deferring one or more updates to the dataset that were generated after said consistency point; and
if notifications of completion of the flushing of pending updates are not received from each client in the set of clients within a threshold period of time, determining whether to abort the point-in-time copy.

### Claim 15

A computer-implemented method of facilitating a consistent point-in-time copy, the method comprising:
receiving from a computing device a request to create a point-in-time copy of a set of data objects;
issuing a request for pending updates to the set of data objects to be flushed;
receiving one or more acknowledgements of the request for pending updates;
if any pending updates were flushed, receiving one or more notifications of the completion of flushing of the pending updates; and
determining whether the set of data objects is consistent with respect to all computing devices to which the request to flush pending updates was sent.

### Claim 16 (depends on 15)

The method of claim 15, wherein said receiving one or more acknowledgements comprises:
receiving acknowledgements from a subset of the computing devices to which the request to flush pending updates was sent.

### Claim 17 (depends on 15)

The method of claim 15, wherein said receiving one or more notifications comprises:
receiving notifications from a subset of the computing devices to which the request to flush pending updates was sent.

### Claim 18 (depends on 15)

The method of claim 15, further comprising, at a first computing device:
receiving an update to a first data object in the set of data objects after sending acknowledgement of the request to flush pending updates; and
deferring said update.

### Claim 19 (depends on 15)

The method of claim 15, further comprising, at a data provider that received the request to create a point-in-time copy:
receiving an update to a first data object in the set of data objects after receiving said notification; and
deferring said update.

### Claim 20 (depends on 15)

The method of claim 15, wherein said determining comprises:
determining whether all computing devices to which the request to flush pending updates was sent have acknowledged the request to flush pending updates.

### Claim 21 (depends on 15)

The method of claim 15, wherein said determining comprises:
determining whether all computing devices to which the request to flush pending updates was sent have sent notification that any pending updates have been flushed.

### Claim 22 (depends on 15)

The method of claim 15, wherein the set of data objects is considered consistent with respect to all computing devices to which the request to flush pending updates was sent if the computing devices have sent notifications that any pending updates have been flushed.

### Claim 23 (depends on 15)

The method of claim 15, wherein the set of data objects comprises a file stored in a single location.

### Claim 24 (depends on 15)

The method of claim 15, wherein the set of data objects comprises a file shared among multiple storage locations.

### Claim 25

A computer readable medium storing instructions that, when executed by a computer, cause the computer to perform a method of facilitating a consistent point-in-time copy, the method comprising:
receiving from a computing device a request to create a point-in-time copy of a set of data objects;
issuing a request for pending updates to the set of data objects to be flushed;
receiving one or more acknowledgements of the request for pending updates;
if any pending updates were flushed, receiving one or more notifications of the completion of flushing of the pending updates; and
determining whether the set of data objects is consistent with respect to all computing devices to which the request to flush pending updates was sent.

### Claim 26

A computer-implemented method of facilitating a consistent point-in-time copy of a set of data, the method comprising:
issuing a first request for a point-in-time copy of a specified dataset;
receiving a second request to flush any updates to the dataset that are pending;
flushing any said pending updates to the dataset; and
sending notification that said flushing is complete.

### Claim 27 (depends on 26)

The method of claim 26, further comprising: acknowledging the second request.

### Claim 28 (depends on 27)

The method of claim 27, further comprising:
receiving an update to the dataset after acknowledging said second request; and
deferring said update.

### Claim 29 (depends on 26)

The method of claim 26, wherein said first request for a point-in-time copy is configured to:
identify the dataset; and
indicate action to take if not all computing devices having pending updates to the dataset send notification that said flushing is complete.

### Claim 30 (depends on 29)

The method of claim 29, wherein said request for a point-in-time copy is further configured to:
indicate action to take if not all computing devices to which the second request is sent acknowledge the second request.

### Claim 31 (depends on 29)

The method of claim 29, wherein said request for a point-in-time copy is further configured to:
identify a desired consistency point.

### Claim 32

A computer readable medium storing instructions that, when executed by a computer, cause the computer to perform a method of facilitating a consistent point-in-time copy of a set of data, the method comprising:
issuing a first request for a point-in-time copy of a specified dataset;
receiving a second request to flush any updates to the dataset that are pending;
flushing any pending updates to the dataset; and
sending notification that said flushing is complete.

### Claim 33

An automated method of facilitating a consistent point-in-time copy of a set of data, the method comprising:
issuing a request to a set of client computing devices to flush pending updates to the set of data;
receiving notification from a first subset of the client computing devices that pending updates to the set of data have been flushed; and
determining whether the set of data is consistent with regard to the set of client computing devices.

### Claim 34 (depends on 33)

The method of claim 33, further comprising:
determining whether to abort the point-in-time copy; and
determining whether to mark the point-in-time copy as incomplete.

### Claim 35 (depends on 33)

The method of claim 33, further comprising:
receiving acknowledgement of the request from a second subset of the client computing devices.

### Claim 36 (depends on 33)

The method of claim 33, further comprising:
receiving an update to the set of data after a first notification is received from a first client; and
deferring the update.

### Claim 37

A network of computer systems configured to facilitate a consistent point-in-time copy of a set of data, comprising:
a data provider configured to provide access to the set of data by a client;
a set of clients configured to access the set of data through said data provider; and
a data exchange protocol executing on said data provider and said clients, wherein said data exchange protocol is configured to:
convey a request, from the data provider to the set of clients, to flush pending updates to the set of data; and
convey a notification, from a client to the data provider, that the client has completed flushing updates to the set of data.

### Claim 38 (depends on 37)

The network of claim 37, further comprising:
a first client in the set of clients, wherein the first client is configured to issue a request for a point-in-time copy of the set of data.

### Claim 39 (depends on 37)

The network of claim 37, wherein said data exchange protocol is further configured to convey acknowledgement of the request from the client to the data provider.

### Claim 40 (depends on 37)

The network of claim 37, wherein the data provider comprises:
a point-in-time copy module configured to initiate a point-in-time copy of the set of data.

### Claim 41 (depends on 40)

The network of claim 40, wherein the data provider further comprises:
a memory configured to store an update to the set of data received after a first notification is received from a first client that the first client has completed flushing updates to the set of data.

### Claim 42 (depends on 37)

The network of claim 37, wherein a first client comprises:
an application configured to access the set of data; and
a memory configured to store an update to the set of data generated by the application after the first client acknowledges said request to flush pending updates to the set of data.

### Claim 43

A client computing device for facilitating a consistent point-in-time copy of a set of data, the device comprising:
an application configured to generate updates to the set of data; and
a data exchange protocol configured to enable data sharing between the client computing device and a data provider;
wherein the client computing device is configured to flush updates to the set of data in response to a flush request from the data provider; and
wherein the client computing device is further configured to notify the data provider when the flushing of said updates to the set of data is completed.

### Claim 44 (depends on 43)

The client computing device of claim 43, wherein the client computing device is further configured to issue a request to the data provider to perform the point-in-time copy of the set of data.

### Claim 45 (depends on 44)

The client computing device of claim 44, wherein said request to perform the point-in-time copy specifies a consistency point.

### Claim 46 (depends on 44)

The client computing device of claim 44, wherein said request to perform the point-in-time copy specifies how the data provider should respond if a period for responding to the flush request expires before the client computing device notifies the data provider of completion of the flushing of said updates.

### Claim 47 (depends on 43)

The client computing device of claim 43, wherein the client computing device is further configured to acknowledge said flush request.

### Claim 48 (depends on 47)

The client computing device of claim 47, wherein the client computing device is further configured to defer an update to the set of data received from the application after said flush request is acknowledged.

### Claim 49

A computer system configured to facilitate a consistent point-in-time copy of a dataset, comprising:
a point-in-time copy module configured to perform a point-in-time copy of a specified dataset; and
a data exchange protocol configured to enable data sharing between the computer system and one or more client devices configured to access the dataset;
wherein the computer system is configured to request the client devices to flush any pending updates to the dataset; and
wherein the computer system is further configured to determine whether the dataset is consistent in relation to the client devices.

### Claim 50 (depends on 49)

The computer system of claim 49, wherein the computer system is further configured to receive a request for the point-in-time copy from one of the client devices.

### Claim 51 (depends on 49)

The computer system of claim 49, wherein the computer system is further configured to receive an acknowledgement of said request to flush pending updates from a client device.

### Claim 52 (depends on 49)

The computer system of claim 49, wherein the computer system is further configured to receive notification from a client device that the client device has completed flushing updates to the set of data that were pending on the client device.

### Claim 53 (depends on 52)

The computer system of claim 52, wherein the computer system is further configured to acknowledge said notification.

### Claim 54 (depends on 49)

The computer system of claim 49, wherein the dataset is considered consistent in relation to the client devices if each client device notifies the computer system that the client device has completed flushing updates to the set of data that were pending on the client device.

### Claim 55 (depends on 49)

The computer system of claim 49, wherein the dataset is considered inconsistent in relation to the client devices if one or more client devices fail to notify the computer system, within a threshold period of time, that the client device has completed flushing updates to the set of data that were pending on the client device.

### Claim 56 (depends on 49)

The computer system of claim 49, wherein the dataset is considered inconsistent in relation to the client devices if one or more client devices fail to acknowledge request to flush pending updates to the dataset within a threshold period of time.
