Application level support for selectively accessing files in cloud-based storage

• US 9,753,814 B1
• Filed: 12/19/2014
• Issued: 09/05/2017
• Est. Priority Date: 12/19/2014
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Whitmer, Ray David
• Primary Examiner(s): Arjomandi, Noosha
• Application Number:
  US14/578,168
• Time in Patent Office: 991 Days
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 2201/83 the solution involving signatures
• CPC Class Codes: G06F 2201/855 Details of asynchronous mirroring using a journal to transfer not-yet-mirrored changes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

In one example, a method is provided for backing up client data at a datacenter. Initially, an incremental backup is received from a client and stored at the datacenter. Next, a table of contents for the incremental backup is created, and differences identified between the incremental backup and a dataset previously stored at the datacenter. The offsets imposed by any new or modified blocks present in the incremental backup can then be identified and recorded, and used to identify respective data ranges in the incremental backup for any new and modified blocks, which data ranges can then be recorded. Next, a reference block can be created for each block of the previously stored dataset that was not modified in the incremental backup. The reference block can then be stored at the datacenter in association with the incremental backup.

Claims

1. A method for data backup, comprising:

receiving, at a datacenter, an incremental backup from a client, wherein any new and modified blocks of the incremental backup are received at the datacenter from the client in an encrypted form;

storing the incremental backup at the datacenter;

creating a table of contents relating to the incremental backup;

identifying differences between the incremental backup and a dataset previously stored at the datacenter;

identifying and recording offsets imposed by any new or modified blocks present in the incremental backup;

using the offsets to identify respective data ranges in the incremental backup for any new and modified blocks, and recording the data ranges, wherein, for one of the new or modified blocks of the incremental backup, one of the offsets identifies a difference between an incremental backup data range that is associated with that block and a previously stored dataset data range that is associated with that block;

creating a reference block for each block of the previously stored dataset that was not modified in the incremental backup; and

storing the reference blocks at the datacenter in association with the incremental backup.

2. The method as recited in claim 1, wherein the previously stored dataset is a baseline data set, or an incremental backup.

3. The method as recited in claim 1, wherein each reference block points to another reference block or to a block of the previously stored dataset.

4. The method as recited in claim 1, wherein the table of contents for the incremental backup includes a listing of any new and modified blocks that are included in the incremental backup.

5. The method as recited in claim 1, wherein a size of one of the offsets is based upon a relative difference between a modified block of the incremental backup and a corresponding block of the previously stored dataset.

6. The method as recited in claim 1, wherein a modified block of the incremental update has a size that is different than a corresponding block of the previously stored dataset.

7. The method as recited in claim 1, further comprising listing the reference blocks in the table of contents.

8. The method as recited in claim 1, wherein the incremental backup comprises an incremental backup of one of a database, an email repository, or a virtual machine disk file.

9. The method as recited in claim 1, further comprising returning one or more stored blocks to the client in response to a request from the client, and the returned blocks are transmitted to the client in an encrypted form.

10. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, creates a data backup by performing the following:

receiving, at a datacenter, an incremental backup from a client, wherein any new and modified blocks of the incremental backup are received at the datacenter from the client in an encrypted form;

storing the incremental backup at the datacenter;

creating a table of contents relating to the incremental backup;

identifying differences between the incremental backup and a dataset previously stored at the datacenter;

identifying and recording offsets imposed by any new or modified blocks present in the incremental backup;

using the offsets to identify respective data ranges in the incremental backup for any new and modified blocks, and recording the data ranges, wherein, for one of the new or modified blocks of the incremental backup, one of the offsets identifies a difference between an incremental backup data range that is associated with that block and a previously stored dataset data range that is associated with that block;

creating a reference block for each block of the previously stored dataset that was not modified in the incremental backup; and

storing the reference blocks at the datacenter in association with the incremental backup.

11. The non-transitory storage medium as recited in claim 10, wherein the previously stored dataset is a baseline data set, or an incremental backup.

12. The non-transitory storage medium as recited in claim 10, wherein each reference block points to another reference block or to a block of the previously stored dataset.

13. The non-transitory storage medium as recited in claim 10, wherein the table of contents for the incremental backup includes a listing of any new and modified blocks that are included in the incremental backup.

14. The non-transitory storage medium as recited in claim 10, wherein a size of one of the offsets is based upon a relative difference between a modified block of the incremental backup and a corresponding block of the previously stored dataset.

15. The non-transitory storage medium as recited in claim 10, wherein a modified block of the incremental update has a size that is different than a corresponding block of the previously stored dataset.

16. The non-transitory storage medium as recited in claim 10, wherein creating a data backup further comprises listing the reference blocks in the table of contents.

17. The non-transitory storage medium as recited in claim 10, wherein the incremental backup comprises an incremental backup of one of a database, an email repository, or a virtual machine disk file.

18. The non-transitory storage medium as recited in claim 10, further comprising returning one or more stored blocks to the client in response to a request from the client, and the returned blocks are transmitted to the client in an encrypted form.

19. A physical device, wherein the physical device comprises:

one or more hardware processors; and

a non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, creates a data backup by performing the following;

receiving, at a datacenter, an incremental backup from a client, wherein any new and modified blocks of the incremental backup are received at the datacenter from the client in an encrypted form;

storing the incremental backup at the datacenter;

creating a table of contents relating to the incremental backup;

identifying differences between the incremental backup and a dataset previously stored at the datacenter;

identifying and recording offsets imposed by any new or modified blocks present in the incremental backup;

using the offsets to identify respective data ranges in the incremental backup for any new and modified blocks, and recording the data ranges, wherein, for one of the new or modified blocks of the incremental backup, one of the offsets identifies a difference between an incremental backup data range that is associated with that block and a previously stored dataset data range that is associated with that block;

creating a reference block for each block of the previously stored dataset that was not modified in the incremental backup; and

storing the reference blocks at the datacenter in association with the incremental backup.

20. A cloud based datacenter that includes the physical device as recited in claim 19.