# US 12,117,911 B2 · Remote data replication method and system

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

- Number: US 12,117,911 B2
- Document ID: US12117911B2
- Status: Granted
- Kind: B2
- Application number: 18/069,639
- Filed: 2022-12-21
- Published: 2023-04-20
- Granted: 2024-10-15
- Earliest claimed: 2016-09-05
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Ji Ouyang; Huabing Yan
- Web page: https://patentgrep.com/patent/US12117911B2

## CPC

- G06F 11/2069: {Management of state, configuration or failover}
- G06F 11/00: Error detection; Error correction; Monitoring (error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00)
- G06F 11/2035: {without idle spare hardware}
- G06F 11/2066: {Optimisation of the communication load}
- G06F 11/2074: {Asynchronous techniques}
- G06F 11/2082: {Data synchronisation}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 16/9017: {using directory or table look-up (use of a directory or look-up table in file systems G06F16/13)}
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- G06F 3/0646: {Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems}
- G06F 3/0647: {Migration mechanisms}
- G06F 3/065: {Replication mechanisms}
- G06F 11/2097: {maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups)}
- 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)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A remote data replication method and a storage system, where a production array sends a data replication request to a disaster recovery array. The data replication request includes an identifier of a source object and a data block corresponding to the source object. The data block is stored in physical space of a hard disk of the production array. The disaster recovery array receives the data replication request. The disaster recovery array creates a target object when the disaster recovery array does not include an object having a same identifier as the source object. An identifier of the target object is the same as the identifier of the source object, the disaster recovery array writes the data block into the physical space.

## Claims

### Claim 1

A method comprising:
providing, by a source site in an object-based storage system, a source object comprising a file;
storing, by a first target site in the object-based storage system, a first copy of the file;
receiving, by the source site and from a host, an object delete request requesting to delete the file;
deleting, by the source site, the file based on the object delete request;
writing, by the source site, a deleting mark corresponding to deleted file into the source site;
sending, by the source site and to the first target site, delete information that includes the deleting mark and that indicates the file has been deleted;
deleting, by the first target site, the first copy of the file based on the delete information;
and
providing, by the source site, a response to the host after the deletion of the first copy of the file.

### Claim 2 (depends on 1)

The method of claim 1, wherein the deleting mark indicates that data included in the deleted file needs to be released.

### Claim 3 (depends on 2)

The method of claim 2, wherein the delete information further includes a logical address of the deleted file.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
detecting, by the source site, incremental data to be written into the file to update the file;
sending, by the source site, the incremental data to the first target site; and
writing, by the first target site, the incremental data into the first copy of the file.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
sending, by the source site, the incremental data to a second target site; and
writing, by the second target site, the incremental data into a second copy of the file.

### Claim 6 (depends on 1)

The method of claim 1, further comprising storing, by the source site and in response to receiving the object delete request, a deletion log comprising an identification (ID) of the file and a logical address of the file.

### Claim 7 (depends on 1)

The method of claim 1, wherein the source object comprising a data bucket for containing the file.

### Claim 8 (depends on 1)

The method of claim 1, wherein the source object comprising a data bucket for containing a directory.

### Claim 9 (depends on 1)

The method of claim 1, wherein the source object comprising a data bucket for containing the file or a directory.

### Claim 10

An object-based storage system comprising:
a source site configured to:
provide a source object comprising a file;
receive, from a host, an object delete request requesting to delete the file;
delete the file based on the object delete request; and
write a deleting mark corresponding to deleted file; and
a first target site configured to:
store a first copy of the file;
receive delete information that includes the deleting mark and that indicates the file has been deleted; and
delete the first copy of the file based on the delete information,
wherein the source site is further configured to provide a response to the host after the deletion of the first copy of the file.

### Claim 11 (depends on 10)

The object-based storage system of claim 10, wherein the deleting mark indicates that data included in the deleted file needs to be released.

### Claim 12 (depends on 11)

The object-based storage system of claim 11, wherein the delete information further includes a logical address of the deleted file.

### Claim 13 (depends on 10)

The object-based storage system of claim 10, wherein the source site is further configured to:
detect incremental data to be written into the file to update the file; and
send the incremental data to the first target site, and
wherein the first target site is further configured to write the incremental data into the first copy of the file.

### Claim 14 (depends on 13)

The object-based storage system of claim 13, wherein the source site is further configured to send the incremental data to a second target site, and wherein the second target site is further configured to write the incremental data into a second copy of the file.

### Claim 15 (depends on 10)

The object-based storage system of claim 10, wherein the source site is further configured to store, in response to receiving the object delete request, a deletion log comprising an identification (ID) of the file and a logical address of the file.

### Claim 16

A computer program product comprising computer-executable instructions for storage on a non-transitory computer-readable storage medium that, when executed by a processor, cause an object-based storage system to:
provide, using a source site in the object-based storage system, a source object comprising a file;
generate, using a first target site in the object-based storage system, a first copy of the file;
store, using the first target site, the first copy of the file;
receive, using the source site and from a host, an object delete request requesting to delete the file;
delete, using the source site, the file based on the object delete request;
write, by the source site, a deleting mark corresponding to deleted file into the source site;
send, using the source site and to the first target site, delete information that includes the deleting mark and that indicates the file has been deleted;
delete, using the first target site, the first copy of the file based on the delete information;
and
provide a response to the host after the deletion of both the first copy of the file.

### Claim 17 (depends on 16)

The computer program product of claim 16, wherein the deleting mark indicates that data included in the deleted file needs to be released.

### Claim 18 (depends on 17)

The computer program product of claim 17, wherein the delete information further includes a logical address of the deleted file.

### Claim 19 (depends on 16)

The computer program product of claim 16, wherein the computer-executable instructions further cause the storage system to:
detect, using the source site, incremental data to be written into the file to update the file;
send, using the source site, the incremental data to the first target site; and
write, using the first target site, the incremental data into the first copy of the file.

### Claim 20 (depends on 16)

The computer program product of claim 16, wherein the computer-executable instructions further cause the storage system to store, using the source site and in response to receiving the object delete request, a deletion log comprising an identification (ID) of the file and a logical address of the file.