Synchronized change tracking in data storage volumes

• US 9,875,041 B1
• Filed: 09/30/2014
• Issued: 01/23/2018
• Est. Priority Date: 09/30/2014
• Status: Active Grant

• Current Assignee: MidCap Financial Trust
• Original Assignee: Acronis International GmbH (Acronis AG)
• Inventors: Redko, Andrei, Protasov, Stanislav, Beloussov, Serguei M., Lyadvinsky, Maxim V.
• Primary Examiner(s): Bradley, Matthew
• Application Number:
  US14/502,959
• Time in Patent Office: 1,211 Days
• Field of Search: 711161
• CPC Class Codes: G06F 11/14 Error detection or correction of the data by redundancy in operation G06F11/16 takes precedence
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/3037 where the computing system component is a memory, e.g. virtual memory, cache accessing, addressing or allocating within memory systems or architectures G06F12/00; checking stores for correct operation G11C29/00
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

Various examples are directed to systems and methods for backing up data. A tracking utility may receive a start request and then receive a write request directed towards the first volume. An address of the block of the volume to be modified by the write request may be recorded to a current changes list. The tracking utility may also receive a first lock request, wherein the lock request comprises an instruction to place the volume in a read-only mode. Upon receiving the first lock request, the tracking utility may copy the current changes list to a frozen changes list and clear the current changes list. Upon receiving a second lock request, the tracking utility may merge the current changes list and the frozen changes list.

Claims

1. A computer-implemented system for backing up data, the system comprising:

at least one processor and an operatively associated storage device, wherein the at least one processor is programmed to;

execute a tracking application;

execute a file system driver; and

execute a file system filter driver, wherein the file system filter driver is programmed to;

receive a start tracking request;

receive a plurality of write input/output (I/O) requests from the application;

record a set of current changes to an address of a block to be modified by the write I/O request for each of the plurality of I/O requests;

forward the write I/O request to the file system driver;

receive a lock request;

determine that the lock request is the first lock request received since receipt of the start tracking request; and

in response to receiving the second lock request after the first lock request,

copy the current changes to frozen changes,

clear the current changes,

receive a second lock request, and

discard current changes after initiating a merger of the current changes.

2. The system of claim 1, wherein the file system filter driver is further programmed to:

receive a request to view the frozen changes;

return the frozen changes; and

clear the frozen changes.

3. The system of claim 1, wherein the merger of the current changes comprises:

determining that the address of the block to be modified is not indicated in the frozen changes; and

indicating the address in the frozen changes.

4. The system of claim 1, wherein the lock request is received from a snapshot utility, and wherein the lock request indicates that the snapshot utility is to begin a snapshot of at least a portion of the storage device.

5. The system of claim 1, further comprising one or more memory devices wherein changes and frozen changes can be stored and accessed.

6. A computer-implemented system for backing up data, the system comprising:

at least one processor and an operatively associated storage device, wherein the storage device comprises a first volume, and wherein the at least one processor is programmed to;

execute a file system driver;

execute a tracking utility, wherein the tracking utility is programmed to;

receive a start tracking request;

receive a write request directed towards the first volume;

record to a current changes list an address at the volume to be modified by the write request;

receive a lock request;

determine that the lock request is the first lock request received since receipt of the start tracking request;

copy the current changes list to a frozen changes list;

clear the current changes list;

receive a second lock request; and

in response to receiving the second lock request after the first lock request, merge the current changes list and the frozen changes list.

7. The system of claim 6, wherein the tracking utility is further programmed to forward the write request to the file system driver associated with the first volume.

8. The system of claim 6, wherein the tracking utility is further programmed to, after clearing the current changes list and before receiving the second lock request:

receive a plurality of write requests directed towards the volume; and

for each of the plurality of write requests, record to the current changes list an address at the volume to be modified by the write request.

9. The system of claim 6, wherein the tracking utility is further programmed to:

receive from a backup client a request to view the frozen changes list;

In response to the request, return the frozen changes list; and

after returning the frozen changes list, clear the frozen changes list.

10. The system of claim 6, wherein merging the current changes list and the frozen changes list comprises:

comparing data block addresses from the current changes list to data block addresses from the frozen changes list; and

writing to the frozen changes list data block addresses from the current changes list that were not also on the frozen changes list.

11. The system of claim 6, wherein the lock request is received from a snapshot utility, and wherein the lock request indicates that the snapshot utility is to begin a snapshot of the volume.

12. The system of claim 6, further comprising one or more memory devices wherein changes and frozen changes can be stored and accessed.

13. A computer-implemented system for backing up data, the system comprising:

at least one processor and an operatively associated storage device, wherein the storage device comprises a first volume, and wherein the at least one processor is programmed to;

execute a backup client, wherein the backup client is programmed to;

detect lock requests;

initiate a tracking utility at a first time;

request a first snapshot of the first volume, the first snapshot having a first lock request;

generate a first backup copy of the first volume from the first snapshot;

determine that the lock request is the first lock request received;

request a second snapshot of the first volume, the second snapshot having a second lock request;

stop the tracking utility in response to detecting the second lock request;

receive from the tracking utility a list comprising changes to the first volume between the first time and a time of a last snapshot of the volume taken before the tracking utility is stopped; and

generate a second backup copy of the first volume from the second snapshot considering the list.

14. The system of claim 13, wherein the at least one processor is further programmed to execute the tracking utility, wherein the tracking utility is programmed to:

receive a start tracking request from the backup client at the first time;

after receiving the start tracking request, receive a plurality of write requests directed to the first volume;

for each of the plurality of write requests, record to a current changes list an address at the volume to be modified by the write request;

receive a first lock request after receiving the start tracking request;

after receiving the first lock request, copy the current changes list to a frozen changes list;

clear the current changes list;

receive a second lock request; and

merge the current changes list and the frozen changes list.

15. The system of claim 14, wherein the tracking utility is further programmed to provide the frozen changes list to the backup client as the list.

16. The system of claim 14, wherein the lock request is received from a snapshot utility, and wherein the lock request indicates that the snapshot utility is to begin a snapshot of the volume.

17. The system of claim 14, wherein the tracking utility is further programmed to forward each of the plurality of write requests to the file system driver associated with the first volume.

18. The system of claim 14, wherein the tracking utility comprises a file system filter driver.

19. The system of claim 14, wherein merging the current changes list and the frozen changes list comprises:

comparing data block addresses from the current changes list to data block addresses from the frozen changes list; and

writing to the frozen changes list data block addresses from the current changes list that were not also on the frozen changes list.