Granted Patent B2

US 9,841,909 · App. 15/352,545 · Granted Dec 12, 2017

Inventors: Shunhui Zhu (San Jose, CA); Boris Yanovsky (Saratoga, CA); William Dunn (Cupertino, CA); Matthew W. Cotton (Santa Clara, CA)

Assignee: SONICWALL INC.

G06F3/0617G06F3/065G06F3/067G06F3/0643

Abstract

Claims (74)

1. A method for backing up data stored at a computer, the method comprising:

receiving over a communication interface data regarding a first version of one or more files stored at a first computing device, wherein the one or more files are associated with a plurality of discrete data parts, and wherein each discrete data part is associated with one or more versions;

generating a first mapping of the received first version data;

coordinating storage of the plurality of discrete data parts according to the first mapping, wherein the plurality of discrete data parts are stored at a second computing device;

receiving over the communication interface in real-time data regarding a changed version of the one or more files, the changed version data including change data regarding one or more of the plurality of discrete data parts that have changed, wherein the one or more changed data parts are each assigned a new version subsequent to at least one of the one or more versions previously associated with each changed data part;

generating a second mapping associated with the changed data parts;

coordinating the storage of the changed data parts at the second computing device according to the second mapping;

receiving a restore request to restore data associated with the one or more files, wherein the restore request is associated with at least the first version of the one or more files or with the changed version of the one or more files; and

transmitting restore data according to the restore request over the data communication interface.

2. The method of claim 1 , further comprising:

receiving data over the communication interface in real-time, the received data regarding a second changed version of the one or more files, the second changed version data including a second set of change data regarding at least one discrete data part that has changed since the second mapping was generated, wherein the at least one discrete data part is assigned a version identifier that is different from a corresponding version identifier that is associated with a related discrete data part of the one or more discrete data parts that are associated with the second mapping;

generating a third mapping associated with the at least one discrete data part that has changed; and

coordinating the storage of the at least one discrete changed data part at the second computing device according to the third mapping.

3. The method of claim 2 , further comprising:

identifying that the changed data parts associated with the second mapping is to be trimmed from the second computing device;

identifying that one or more of the changed data parts associated with the second mapping is to be deleted from the second computing device based on the identification that the changed data parts associated with the second mapping is to be trimmed from the second computing device, wherein one or more data parts that is to be deleted from the second computing device are not required to re-build the second changed version based on the version identifier being different from the corresponding version identifier; and

deleting one or more of the changed data parts associated with the second mapping.

4. The method of claim 1 , wherein each of the one or more changed data parts correspond to one or more data blocks associated with one or more data storage devices.

5. The method of claim 1 , wherein the restore data transmitted over the data communication interface includes the one or more changed data parts when the restore request is associated with the changed version of the one or more files.

6. The method of claim 2 , further comprising:

hashing data associated with the first version of the one or more files;

hashing data associated with the one or more changed data parts;

identifying differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts; and

identifying that the data associated with the first version of the one or more files has changed corresponding to the data associated with the one or more changed data parts based on the identified differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts.

7. The method of claim 6 , wherein the differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts are identified using a field programmable gate array (FPGA) that compares the hashing data associated with the first version of the one or more files with the hashing data associated with the one or more changed data parts.

8. A non-transitory computer readable storage medium having embodied thereon a program executable by a processor for implementing a method for backing up data stored at a computer, the method comprising:

receiving data over a communication interface data regarding a first version of one or more files stored at a first computing device, wherein the one or more files are associated with a plurality of discrete data parts, and wherein each discrete data part is associated with one or more versions;

generating a first mapping of the received first version data;

coordinating storage of the plurality of discrete data parts according to the first mapping, wherein the plurality of discrete data parts are stored at a second computing device;

receiving data over the communication interface in real-time, the received data regarding a changed version of the one or more files, the changed version data including change data regarding one or more of the plurality of discrete data parts that have changed, wherein the one or more changed data parts are each assigned a new version subsequent to at least one of the one or more versions previously associated with each changed data part;

generating a second mapping associated with the changed data parts;

coordinating the storage of the changed data parts at the second computing device according to the second mapping;

receiving a restore request to restore data associated with the one or more files, wherein the restore request is associated with at least the first version of the one or more files or with the changed version of the one or more files; and

transmitting restore data according to the restore request over the data communication interface.

9. The non-transitory computer-readable storage medium of claim 8 , the program is further executable to:

receive data over the communication interface in real-time, the received data regarding a second changed version of the one or more files, the second changed version data including a second set of change data regarding at least one discrete data part that has changed since the second mapping was generated, wherein the at least one discrete data part is assigned a version identifier that is different from a corresponding version identifier that is associated with a related discrete data part of the one or more discrete data parts that are associated with the second mapping;

generate a third mapping associated with the at least one discrete data part that has changed; and

coordinate the storage of the at least one discrete changed data part at the second computing device according to the third mapping.

10. The non-transitory computer-readable storage medium of claim 9 , wherein the program comprises further instructions executable to:

identify that the changed data parts associated with the second mapping is to be trimmed from the second computing device;

identify that one or more of the changed data parts associated with the second mapping is to be deleted from the second computing device based on the identification that the changed data parts associated with the second mapping is to be trimmed from the second computing device, wherein one or more data parts that is to be deleted from the second computing device are not required to re-build the second changed version based on the version identifier being different from the corresponding version identifier; and

delete one or more of the changed data parts associated with the second mapping.

11. The non-transitory computer-readable storage medium of claim 8 , wherein each of the one or more changed data parts correspond to one or data blocks associated with one or more data storage devices.

12. The non-transitory computer-readable storage medium of claim 8 , wherein the restore data transmitted over the data communication interface includes the one or more changed data parts when the restore request is associated with the changed version of the one or more files.

13. The non-transitory computer-readable storage medium of claim 9 , wherein the program comprises further instructions executable to:

hash data associated with the first version of the one or more files;

hash data associated with the one or more changed data parts;

identify differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts; and

identify that the data associated with the first version of the one or more files has changed corresponds to the data associated with the one or more changed data parts based on the identified differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts.

14. The non-transitory computer-readable storage medium of claim 13 , wherein the differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts are identified using a field programmable gate array (FPGA) that compares the hashing data associated with the first version of the one or more files with the hashing data associated with the one or more changed data parts.

15. An apparatus having embodied thereon a program executable by a processor for implementing a method for backing up data stored at a computer, the apparatus comprising:

a communication interface that receives data regarding a first version of one or more files stored at a first computing device, wherein the one or more files are associated with a plurality of discrete data parts, and wherein each discrete data part of the plurality of discrete data parts is associated with one or more versions;

a memory; and

a processor that executes instructions out of the memory to:

generate a first mapping of the received first version data,

coordinate storage of the plurality of discrete data parts according to the first mapping, wherein the plurality of discrete data parts are stored at a second computing device, the communication interface receives data in real-time, the received data regarding a changed version of the one or more files, and the changed version data including change data regarding one or more of the plurality of discrete data parts that have changed, and the one or more changed data parts are each assigned a new version subsequent to at least one of the one or more versions previously associated with each changed data part,

generate a second mapping associated with the changed data parts,

coordinate the storage of the changed data parts at the second computing device according to the second mapping, and

receives a restore request to restore data associated with the one or more files, wherein the restore request is associated with at least the first version of the one or more files or with the changed version of the one or more files, wherein restore data is transmitted according to the restore request over the data communication interface.

16. The apparatus of claim 15 , wherein the communication interface receives in real-time data regarding a second changed version of the one or more files, the second changed version data including a second set of change data regarding at least one discrete data part that has changed since the second mapping was generated, and wherein the processor executes further instructions to:

assign the at least one discrete data part a version identifier that is different from a corresponding version identifier that is associated with a related discrete data part of the one or more discrete data parts that are associated with the second mapping,

generate a third mapping associated with the at least one discrete data part that has changed; and

coordinate the storage of the at least one discrete changed data part at the second computing device according to the third mapping.

17. The apparatus of claim 16 , wherein the processor executes further instructions to:

identify the changed data parts associated with the second mapping that is to be trimmed from the second computing device;

identify one or more of the changed data parts associated with the second mapping that is to be deleted from the second computing device based on the identification that the changed data parts associated with the second mapping is to be trimmed from the second computing device, wherein one or more data parts that is to be deleted from the second computing device are not required to re-build the second changed version based on the version identifier being different from the corresponding version identifier; and

delete one or more of the changed data parts associated with the second mapping.

18. The apparatus of claim 15 , wherein each of the one or more changed data parts correspond to one or data blocks associated with one or more data storage devices.

19. The apparatus of claim 16 , wherein the processor executes further instructions to:

hash data associated with the first version of the one or more files;

hash data associated with the one or more changed data parts;

identify differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts; and

identify that the data associated with the first version of the one or more files has changed corresponds to the data associated with the one or more changed data parts based on the identified differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts.

20. The apparatus of claim 19 , further comprising a field programmable gate array (FPGA), wherein the differences in the hashing data associated with the first version of the one or more files and the hashing data associated with the one or more changed data parts are identified using the FPGA that compares the hashing data associated with the first version of the one or more files with the hashing data associated with the one or more changed data parts.

Assignments (10)

Continuity (3)