IP Library Granted Patent US 10,579,490
Granted Patent B2
US 10,579,490 · App. 15/636,470 · Granted Mar 3, 2020

Fast geo recovery method for elastic cloud storage

Inventors: Mikhail Danilov (Saint Petersburg, RU); Konstantin Buinov (Kirovsk, RU); Sergey Karpenkov (Saint Petersburg, RU); Maxim S. Trusov (Saint Petersburg, RU); Kirill Zakharov (Saint Petersburg, RU)
Assignee: EMC IP Holding Company LLC
G06F11/2069G06F11/1076G06F11/1088G06F11/1402H03M13/154H03M13/373H03M13/3761H04L67/1095H04L67/1097G06F2201/805G06F2201/82
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,579,490
App. No.
15/636,470
Granted
Mar 3, 2020
Kind
B2
Abstract

One embodiment is related to a method for remote replication recovery, comprising: determining that a damaged data chunk at a first zone of a cloud storage system is not recoverable locally; determining one or more data fragments of the damaged data chunk that are to be recovered with remote replication recovery based on data stored at a second zone and at a third zone of the cloud storage system, wherein the damaged data chunk comprises a plurality of data fragments; recovering the one or more data fragments of the damaged data chunk with remote replication recovery based on the data stored at the second zone and at the third zone of the cloud storage system; and repairing the damaged data chunk with the recovered data fragments at the first zone.

Claims (38)

1. A method for remote replication recovery, comprising:

determining that a damaged data chunk at a first zone of a cloud storage system is not recoverable locally, wherein each data chunk corresponds to storage space of a predetermined fixed size and comprises a plurality of data fragments that are protected with one or more coding fragments generated based on erasure coding;

determining one or more data fragments of the damaged data chunk that are to be recovered with remote replication recovery based on data stored at a second zone and at a third zone of the cloud storage system;

recovering the one or more data fragments of the damaged data chunk with remote replication recovery based on the data stored at the second zone and at the third zone of the cloud storage system, wherein during the remote replication recovery the data fragments to be recovered are each identified within the respective data chunk with a fragment offset and a fragment size; and

subsequent to recovering the one or more data fragments of the damaged data chunk, repairing the damaged data chunk with the recovered data fragments at the first zone.

2. The method of claim 1 , wherein determining that the damaged data chunk at the first zone of the cloud storage system is not recoverable locally further comprises determining that the damaged data chunk is not recoverable using erasure coding based on data stored within the first zone.

3. The method of claim 1 , wherein the first, second, and third zones are geographically distributed.

4. The method of claim 1 , wherein the one or more data fragments that are to be recovered with remote replication recovery comprise all of invalid data fragments of the damaged data chunk.

5. The method of claim 1 , wherein the one or more data fragments that are to be recovered with remote replication recovery are determined so that remaining invalid data fragments not recovered with remote replication recovery are recoverable locally at the first zone with erasure coding.

6. The method of claim 5 , further comprising recovering the remaining invalid data fragments of the damaged data chunk locally at the first zone with erasure coding.

7. The method of claim 1 , wherein recovering the one or more data fragments of the damaged data chunk with remote replication recovery further comprises performing a bitwise exclusive or (XOR) operation on at least part of the data stored at the second zone and at the third zone of the cloud storage system.

8. The method of claim 1 , further comprising protecting the repaired data chunk with erasure coding at the first zone.

9. A non-transitory machine-readable medium having instructions stored therein which, when executed by a processor, cause the processor to perform testing operations, the operations comprising:

determining that a damaged data chunk at a first zone of a cloud storage system is not recoverable locally, wherein each data chunk corresponds to storage space of a predetermined fixed size and comprises a plurality of data fragments that are protected with one or more coding fragments generated based on erasure coding;

determining one or more data fragments of the damaged data chunk that are to be recovered with remote replication recovery based on data stored at a second zone and at a third zone of the cloud storage system;

recovering the one or more data fragments of the damaged data chunk with remote replication recovery based on the data stored at the second zone and at the third zone of the cloud storage system, wherein during the remote replication recovery the data fragments to be recovered are each identified within the respective data chunk with a fragment offset and a fragment size; and

subsequent to recovering the one or more data fragments of the damaged data chunk, repairing the damaged data chunk with the recovered data fragments at the first zone.

10. The non-transitory machine-readable medium of claim 9 , wherein determining that the damaged data chunk at the first zone of the cloud storage system is not recoverable locally further comprises determining that the damaged data chunk is not recoverable using erasure coding based on data stored within the first zone.

11. The non-transitory machine-readable medium of claim 9 , wherein the first, second, and third zones are geographically distributed.

12. The non-transitory machine-readable medium of claim 9 , wherein the one or more data fragments that are to be recovered with remote replication recovery comprise all of invalid data fragments of the damaged data chunk.

13. The non-transitory machine-readable medium of claim 9 , wherein the one or more data fragments that are to be recovered with remote replication recovery are determined so that remaining invalid data fragments not recovered with remote replication recovery are recoverable locally at the first zone with erasure coding.

14. The non-transitory machine-readable medium of claim 13 , wherein the operations further comprise recovering the remaining invalid data fragments of the damaged data chunk locally at the first zone with erasure coding.

15. The non-transitory machine-readable medium of claim 9 , wherein recovering the one or more data fragments of the damaged data chunk with remote replication recovery further comprises performing a bitwise exclusive or (XOR) operation on at least part of the data stored at the second zone and at the third zone of the cloud storage system.

16. The non-transitory machine-readable medium of claim 9 , wherein the operations further comprise protecting the repaired data chunk with erasure coding at the first zone.

17. A data processing system, comprising:

a processor; and

a memory coupled to the processor storing instructions which, when executed by the processor, cause the processor to perform testing operations, the operations including

determining that a damaged data chunk at a first zone of a cloud storage system is not recoverable locally, wherein each data chunk corresponds to storage space of a predetermined fixed size and comprises a plurality of data fragments that are protected with one or more coding fragments generated based on erasure coding;

determining one or more data fragments of the damaged data chunk that are to be recovered with remote replication recovery based on data stored at a second zone and at a third zone of the cloud storage system;

recovering the one or more data fragments of the damaged data chunk with remote replication recovery based on the data stored at the second zone and at the third zone of the cloud storage system, wherein during the remote replication recovery the data fragments to be recovered are each identified within the respective data chunk with a fragment offset and a fragment size; and

subsequent to recovering the one or more data fragments of the damaged data chunk, repairing the damaged data chunk with the recovered data fragments at the first zone.

18. The data processing system of claim 17 , wherein determining that the damaged data chunk at the first zone of the cloud storage system is not recoverable locally further comprises determining that the damaged data chunk is not recoverable using erasure coding based on data stored within the first zone.

19. The data processing system of claim 17 , wherein the first, second, and third zones are geographically distributed.

20. The data processing system of claim 17 , wherein the one or more data fragments that are to be recovered with remote replication recovery comprise all of invalid data fragments of the damaged data chunk.

21. The data processing system of claim 17 , wherein the one or more data fragments that are to be recovered with remote replication recovery are determined so that remaining invalid data fragments not recovered with remote replication recovery are recoverable locally at the first zone with erasure coding.

22. The data processing system of claim 21 , wherein the operations further comprise recovering the remaining invalid data fragments of the damaged data chunk locally at the first zone with erasure coding.

23. The data processing system of claim 17 , wherein recovering the one or more data fragments of the damaged data chunk with remote replication recovery further comprises performing a bitwise exclusive or (XOR) operation on at least part of the data stored at the second zone and at the third zone of the cloud storage system.

24. The data processing system of claim 17 , wherein the operations further comprise protecting the repaired data chunk with erasure coding at the first zone.

Assignments (8)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (047648/0422) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 060160/0862 →
RELEASE OF SECURITY INTEREST AT REEL 047648 FRAME 0346 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 058298/0510 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
PATENT SECURITY AGREEMENT (CREDIT) Recorded Oct 12, 2018
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047648/0346 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Oct 12, 2018
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 047648/0422 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 28, 2017
From: DANILOV, MIKHAIL; BUINOV, KONSTANTIN; KARPENKOV, SERGEY; TRUSOV, MAXIM S.; ZAKHAROV, KIRILL
To: EMC IP HOLDING COMPANY LLC
Reel/Frame 042854/0744 →
Priority Claims (1)
RU 2016150867 · Dec 23, 2016 · national
Continuity (1)
Related Publication 20180181475A1 · Jun 28, 2018