Snapshot copy facility maintaining read performance and write performance

• US 20060143412A1
• Filed: 12/28/2004
• Published: 06/29/2006
• Est. Priority Date: 12/28/2004
• Status: Abandoned Application

• Current Assignee: EMC Corporation (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Armangau, Philippe
• Application Number:
  US11/023,761
• Publication Number:
  US 20060143412A1
• Time in Patent Office: Days
• US Class Current: 711/162
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 2212/222 Non-volatile memory
• CPC Class Codes: G06F 3/0611 in relation to response time
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0656 Data buffering arrangements
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

To make a snapshot copy of a production dataset concurrent with read/write access, a record is kept of the blocks in the production dataset that have been written to since the point-in-time of the snapshot. The first write to each data block is done as a “fast write” to a non-volatile staging block resulting in an immediate acknowledgement to the application writing to the production dataset. In background, the original contents of the block in the production dataset are copied to a save block, and then the new data is copied from the staging block to the production dataset. This method maintains read and write performance because the background copy operations need not be done on the input-output data path.

Claims

1. A method of creating a snapshot copy of a production dataset concurrent with read-write access to the production dataset, the snapshot copy being the state of the production dataset at a certain point in time, the method comprising:

(a) keeping a record of blocks of the production dataset that have been modified since said point in time; and

(b) responding to a request for write access to a specified block in the production dataset by checking said record of blocks of the production dataset that have been modified since said point in time and finding that the specified block in the production dataset has not been modified since said point in time, and upon finding that the specified block in the production dataset has not been modified since said point in time, writing new data for the specified block to a non-volatile staging block and returning an acknowledgement of the write operation, and thereafter copying original data from the specified block of the production dataset to a save block, and then copying the new data for the specified block from the staging block to the production dataset.

2. The method as claimed in claim 1, wherein the staging block is a dynamically-allocated block of cache memory.

3. The method as claimed in claim 1, wherein the staging block is a block of disk storage.

4. The method as claimed in claim 1, wherein the production dataset is stored in a first disk drive, and the staging block and the save block are dynamically allocated storage blocks in a second disk drive.

5. The method as claimed in claim 1, which includes queuing another request for write access to the specified block in a respective queue for the specified block when the new data for the specified block is being written to the staging block.

6. The method as claimed in claim 1, wherein the specified block of the production dataset and the save block are stored in disk storage, and the copying of the original data from the specified block of the production dataset to the save block is initiated by sending a disk copy command to the disk storage.

7. The method as claimed in claim 1, wherein the specified block of the production dataset and the save block are stored in disk storage of a redundant disk array, and the copying of original data from the specified block of the production dataset to the save block includes reading the original data from the specified block of the production dataset concurrent with reading original data from the save block and reading original parity associated with the original data read from the save block.

8. The method as claimed in claim 1, wherein the copying of the original data from the specified block of the production dataset to the save block is performed by a background copy process.

9. The method as claimed in claim 8, wherein the background copy process services a list of blocks to be copied.

10. The method as claimed in claim 8, wherein the background copy process initiates a block staging task for the specified block after copying the original data from the specified block of the production dataset to the save block, the block staging task for the specified block performing the copying of the new data for the specified block from the staging block to the production dataset.

11. The method as claimed in claim 10, which includes deferring the block staging task for the specified block when the staging block is being accessed in response to another request for write access to the specified block at the time of completion of the copying of the original data from the specified block of the production dataset to the save block, the block staging task being deferred until the staging block is no longer being accessed in response to another request for write access to the specified block.

12. The method as claimed in claimed in claim 1, which includes activating a copy counter each time that new data is first received for a first write to any block of the production dataset since said point in time, and activating the copy counter when the block staging task copies new data for any block of the production dataset to the production dataset, and deferring the creation of a new snapshot copy of the production dataset upon inspecting the copy counter and finding that the copy counter indicates that at least one block of new data has been received for writing to any block of the production dataset since said point in time and has not yet been written to the production dataset.

13. A method of operating a server for creating a snapshot copy of a production dataset concurrent with read-write client access to the production dataset, the snapshot copy being the state of the production dataset at a certain point in time, the method comprising:

(a) keeping a record of blocks of the production dataset that have been modified since said point in time; and

(b) responding to a request from a client for write access to a specified block in the production dataset by checking said record of blocks of the production dataset that have been modified since said point in time and finding that the specified block in the production dataset has not been modified since said point in time, and upon finding that the specified block in the production dataset has not been modified since said point in time, allocating a block of non-volatile memory to the specified block and writing new data for the specified block from the client to the allocated block of non-volatile memory and returning an acknowledgement of completion of the write operation to the client, and thereafter a background copy process copying original data from the specified block of the production dataset to a save block allocated to the specified block and then initiating a block staging task for copying the new data for the specified block from the allocated block of non-volatile memory to the production dataset.

14. The method as claimed in claim 13, which includes queuing another client request for write access to the specified block in a respective queue for the specified block when the new data for the specified block is being written to the allocated block of non-volatile memory.

15. The method as claimed in claim 13, wherein the specified block of the production dataset and the save block are stored in disk storage, and the copying of the original data from the specified block of the production dataset to the save block is initiated by sending a disk copy command to the disk storage.

16. The method as claimed in claim 13, wherein the specified block of the production dataset and the save block are stored in disk storage of a redundant disk array, and the copying of original data from the specified block of the production dataset to the save block includes reading the original data from the specified block of the production dataset concurrent with reading original data from the save block and reading original parity associated with the original data read from the save block.

17. The method as claimed in claim 13, which includes deferring the block staging task for the specified block when the allocated block of non-volatile memory is being accessed in response to another client request for write access to the specified bock at the time of completion of the copying of the original data from the specified block of the production dataset to the save block, the block staging task being deferred until the allocated block of non-volatile memory is no longer being accessed in response to another request for write access.

18. The method as claimed in claimed in claim 13, which includes activating a copy counter each time that new data is first received for a first write to any block of the production dataset since said point in time, activating the copy counter when the block staging task writes new data for any block of the production dataset to the production dataset, and deferring the creation of a new snapshot copy of the production dataset upon inspecting the copy counter and finding that the copy counter indicates that at least one block of new data has been received for writing to any block of the production dataset since said point in time and has not yet been written to the production dataset.

19. A server comprising:

storage for storing a production dataset; and

at least one processor for creating a snapshot copy of a production dataset concurrent with read-write client access to the production dataset, the snapshot copy being the state of the production dataset at a certain point in time;

said at least one processor being programmed for;

(a) keeping a record of blocks of the production dataset that have been modified since said point in time; and

(b) responding to a request from a client for write access to a specified block in the production dataset by checking said record of blocks of the production dataset that have been modified since said point in time and finding that the specified block in the production dataset has not been modified since said point in time, and upon finding that the specified block in the production dataset has not been modified since said point in time, allocating a block of non-volatile memory to the specified block and writing new data for the specified block from the client to the allocated block of non-volatile memory and returning an acknowledgement of completion of the write operation to the client, and thereafter a background copy process copying original data from the specified block of the production dataset to a save block allocated to the specified block and then initiating a block staging task for copying the new data for the specified block from the allocated block of non-volatile memory to the production dataset.

20. The server as claimed in claim 19, wherein said at least one processor is programmed for queuing another request for client write access to the specified block in a respective queue for the specified block when the new data for the specified block is being written to the staging block.

21. The server as claimed in claim 19, wherein said storage includes disk storage, and said at least one processor is programmed for storing the specified block of the production dataset and the save block in the disk storage, and initiating the copying of the original data from the specified block of the production dataset to the save block by sending a disk copy command to the disk storage.

22. The server as claimed in claim 19, wherein said storage includes a redundant disk array for storing the specified block of the production dataset and the save block, and wherein the copying of the original data from the specified block of the production dataset to the save block includes reading the original data from the specified block of the production dataset concurrent with reading original data from the save block and reading original parity associated with the original data read from the save block.

23. The server as claimed in claim 19, wherein said at least one processor is programmed for deferring the block staging task for the specified block when the allocated block of non-volatile memory is being accessed in response to another request for write access to the specified block at the time of completion of the copying of the original data from the specified block of the production dataset to the save block, the block staging task being deferred until the allocated block of non-volatile memory is no longer being accessed in response to another request for write access to the specified block.

24. The server as claimed in claimed in claim 19, wherein said at least one processor is programmed for activating a copy counter each time that new data is first received for a first write to any block of the production dataset since said point in time, activating the copy counter when the block staging task writes new data for any block of the production dataset to the production dataset, and deferring the creation of a new snapshot copy of the production dataset upon inspecting the copy counter and finding that the copy counter indicates that at least one block of new data has been received for writing to any block of the production dataset since said point in time and has not yet been written to the production dataset.