Managing copy-on-writes to snapshots

• US 9,176,853 B2
• Filed: 01/29/2010
• Issued: 11/03/2015
• Est. Priority Date: 01/29/2010
• Status: Active Grant

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Narayanan, Priyesh
• Primary Examiner(s): Rigol, Yaima
• Application Number:
  US12/697,074
• Publication Number:
  US 20110191555A1
• Time in Patent Office: 2,104 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1466 to make the backup process non-disruptive
• CPC Class Codes: G06F 12/00 Accessing, addressing or allocating within memory systems or architectures digital input from, or digital output to record carriers, e.g. to disk storage units, G06F3/06
• CPC Class Codes: G06F 12/16 Protection against loss of memory contents contains no material, see G06F11/00
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/0614 Improving the reliability of storage systems
• 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

An attempt to write to a block of data in a main volume of data is detected. An indicator associated with the block of data is accessed before a copy-on-write operation to a snapshot volume is performed for the block of data. The indicator is used to determine whether the copy-on-write operation is to be performed for the block of data.

Claims

1. A computer memory that stores computer-executable instructions that, when executed, cause a computer system to perform a method comprising:

detecting an attempt to write to a block of data in a first volume of data by a first application, wherein a copy-on-write snapshot volume is associated with said first volume, wherein said snapshot volume does not include a copy of said block of data, and wherein said snapshot volume includes a pointer that points to said block of data in said first volume;

prior to performing a copy-on-write operation by a snapshot driver to said snapshot volume for said block of data, accessing an indicator associated with said block of data in response to said attempt to write to said block of data by said first application, wherein a value of said indicator is set to a first value by a second application via said snapshot driver when said block of data is not of interest to said second application or said block of data was read by said second application prior to said attempt to write to said block of data by said first application; and

determining, based on said value of said indicator, whether said copy-on-write operation is to be performed by said first application for said block of data in response to said attempt to write by said first application, wherein said copy-on-write operation is not performed by said first application if said indicator is set to said first value.

2. The computer memory of claim 1 wherein said snapshot volume is for a portion of said first volume and said block of data is not in said portion, and wherein said copy-on-write operation is therefore not performed for said block of data.

3. The computer memory of claim 1 wherein said snapshot volume is for a file spanning a subset of blocks of data and said block of data is not in said subset, and wherein said copy-on-write operation is therefore not performed for said block of data.

4. The computer memory of claim 1 wherein said method further comprises maintaining a first bitmap of said first volume, and wherein said indicator comprises a bit value in said first bitmap.

5. The computer memory of claim 4 wherein said method further comprises maintaining a second bitmap of said first volume, and wherein said second bitmap tracks blocks of data that have been written to said snapshot volume.

6. The computer memory of claim 1, wherein the value of said indicator is set to a first value by the second application via said snapshot driver when said block of data is not of interest to said second application or said block of data was read by said second application prior to said attempt to write to said block of data by said first application comprises an indication that said block was previously backed up by said second application.

7. The computer memory of claim 1, wherein the value of said indicator is set to a first value by the second application via said snapshot driver when said block of data is not of interest to said second application or said block of data was read by said second application prior to said attempt to write to said block of data by said first application comprises an indication that said block was previously replicated by said second application.

8. A computer memory that stores computer-executable instructions that, when executed, cause a computer system to perform a method comprising:

attempting, by a first application, to write to a block of data in a volume of data comprising a plurality of blocks of data, wherein a copy-on-write snapshot is associated with said volume;

designating, by a second application, a subset of said blocks of data as blocks not of interest to said second application or as having been read by said second application prior to said attempt to write to said block of data, wherein said snapshot does not include a copy of blocks of data in said subset, said designating comprising setting a respective bit in a data structure maintained by a snapshot driver for a block of data in said subset; and

in response to said attempt to write to said block of data by said first application, preventing a copy-on-write operation by said snapshot driver to said snapshot for said block of data, and allowing a copy-on-write operation by said snapshot driver to said snapshot for a block of data not included in said subset.

9. The computer memory of claim 8 wherein said snapshot is for a portion of said volume and said subset is not in said portion.

10. The computer memory of claim 8 wherein said snapshot is for a file spanning multiple blocks and said subset is not part of said file.

11. The computer memory of claim 8 wherein said data structure comprises a bitmap for said volume.

12. The computer memory of claim 11 wherein said method further comprises updating said bitmap each time a block of data in said volume is successfully read before a copy-on-write operation to said snapshot is performed for said block of data.

13. The computer memory of claim 8, wherein designating, by the second application, the subset of said blocks of data as blocks not of interest to said second application or as having been read by said second application prior to said attempt to write to said block of data, comprises an indication that said second application previously backed up the subset of said blocks of data.

14. The computer memory of claim 8, wherein designating, by the second application, the subset of said blocks of data as blocks not of interest to said second application or as having been read by said second application prior to said attempt to write to said block of data comprises an indication that said second application previously replicated the subset of said blocks of data.

15. A non-transitory computer storage medium that stores computer-executable components comprising:

a first application configured to write data to a volume comprising a plurality of blocks of data;

a snapshot driver configured to create a snapshot for said volume and maintain a bitmap having bits corresponding to said plurality of blocks of data; and

a second application configured to read data from said volume and from said snapshot, wherein said second application designates a subset of said blocks of data as blocks not of interest, wherein said snapshot does not include a copy of blocks of data in said subset, wherein said bitmap for said volume is used to track which of said blocks is in said subset, wherein a block of data in said volume that is read by said second application is added to said subset by said second application via said snapshot driver and said bitmap is updated by said second application via the snapshot driver in response to the read of said block of data, wherein a copy-on-write operation to said snapshot by said snapshot driver for said block of data is not performed in response to a write to said block of data by said first application after said bitmap is updated, and wherein a copy-on-write operation to said snapshot by said snapshot driver for a block of data not in said subset is performed in response to a write to said block of data not in said subset by said first application.

16. The non-transitory computer storage medium of claim 15 wherein said snapshot is for a portion of said volume and said subset is not in said portion.

17. The non-transitory computer storage medium of claim 15 wherein said snapshot is for a file that spans a portion of said volume and said subset is not in said portion.

18. The non-transitory computer storage medium of claim 15 wherein a second bitmap of said volume is used to track which blocks of data have been written to said snapshot after having been written to in said volume.

19. The non-transitory computer storage medium of claim 15, wherein the designation of the subset of said blocks of data as blocks not of interest by said second application comprises an indication that the subset of said blocks was previously backed up.

20. The non-transitory computer storage medium of claim 15, wherein the designation of the subset of said blocks of data as blocks not of interest by said second application comprises an indication that the subset of said blocks was previously replicated.