Block-level live browsing and private writable backup copies using an ISCSI server

• US 10,740,022 B2
• Filed: 05/16/2018
• Issued: 08/11/2020
• Est. Priority Date: 02/14/2018
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Gutta, Sunil Kumar, Agrawal, Vijay H.
• Primary Examiner(s): Song, Hua J
• Application Number:
  US15/981,712
• Publication Number:
  US 20190250826A1
• Time in Patent Office: 818 Days
• Field of Search: 711162
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 13/1668 Details of memory controller
• CPC Class Codes: G06F 13/4221 being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 2213/0036 Small computer system interface [SCSI]
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/064 Management of blocks
• 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 illustrative ISCSI server computing device provides user computing devices with “private writable snapshots” of a desired volume of data and/or further provides “private writable backup copies.” The ISCSI service is provided without invoking snapshot limits imposed by storage arrays and further without specialized backup software and pseudo-disk drivers installed on the user computing devices. A user can browse as well as edit personal versions of any number and/or versions of block-level backup copies—the “private writable backup copies.” Likewise, a user can browse and edit personal versions of any number of snapshots of one or more versions of one or more desired data volumes—the “private writable snapshots.” A user can have any number of co-existing private writable snapshots and private writable backup copies. Sparse files, extent-files, software snapshots, and/or media agents co-residing on the ISCSI server are used in the illustrative embodiments.

Claims

1. A system for providing private writable backup copies to user computing devices, the system comprising:

a first computing device comprising an Internet Small Computer Systems Interface (ISCSI) service;

a data storage device in communication with the first computing device and comprising a block-level backup copy of data;

a second computing device in communication with the first computing device via ISCSI protocol; and

wherein the first computing device using the ISCSI service is configured to;

receive from the second computing device a first unique ID and a first request for a first private writable backup copy of the block-level backup copy of data,

if the first request is the first time system-wide that a private writable backup copy has been requested for the block-level backup copy of data, generate a first directory designated an archive store which corresponds to the block-level backup copy of data,

generate a second directory designated a private store having the first unique ID,

present the private store directory as a logical unit number (LUN) to the second computing device; and

wherein the second computing device is configured to mount the LUN, thereby acquiring access to the private store, which is based on the archive store and the block-level backup copy of data, and incorporates changes generated by the second computing device that are written to the private store without changing the block-level backup copy of data, thereby operating as the first private writable backup copy requested by the second computing device.

2. The system of claim 1 wherein the first computing device is further configured to store the archive store and the private store and to serve data therefrom to the second computing device.

3. The system of claim 1 wherein the first computing device is further configured to:

receive from the second computing device a first read request for a first data extent in the LUN,

check the private store to determine whether the first data extent is represented by a first extent-file in the private store, and if so, serve the first data extent from the first extent-file in the private store to the second computing device in response to the first read request, and

if the private store lacks the first extent-file, check to determine whether the first extent-file is present in the archive store, and if so, serve the first data extent from the first extent-file in the archive store to the second computing device in response to the first read request.

4. The system of claim 3 wherein the first computing device is further configured to:

if the private store lacks the first extent-file and the archive store also lacks the first extent-file, restoring the first data extent from the block-level backup copy of data in the storage device to a corresponding extent-file stored to the archive store, wherein the restoring is performed by a media agent that also executes on the first computing device.

5. The system of claim 1 wherein the first computing device is further configured to:

receive from the second computing device a first write request to write a first data extent to the LUN,

check whether the private store comprises a corresponding extent-file for the first data extent, and if so, write the first data extent as received from the second computing device to the private store, thereby overwriting the corresponding extent-file, and

if the private store lacks the corresponding extent-file for the first data extent, check whether the archive store comprises the corresponding extent-file, and if so, copy the corresponding extent-file from the archive store to the private store.

6. The system of claim 1 wherein the first computing device is further configured to:

receive from the second computing device a request to delete the private writable backup copy, and

in response, delete the private store without changing or deleting the archive store, and further without changing the block-level backup copy of data.

7. The system of claim 1 wherein the second computing device is configured to, by mounting the LUN, access the private store for browsing data extents obtained from the block-level backup copy of data and further for implementing changes to the data extents obtained from the block-level backup copy of data without changing the block-level backup copy of data.

8. The system of claim 1 further comprising:

a third computing device in communication with the first computing device via ISCSI protocol; and

wherein the first computing device using the ISCSI service is further configured to;

receive from the third computing device a second unique ID and a second request for a second private writable backup copy of the block-level backup copy of data,

generate a second private store having the second unique ID,

present the second private store as a second logical unit number (LUN) to the third computing device; and

wherein the third computing device is configured to mount the second LUN, thereby acquiring access to the second private store, which is based on the archive store and the block-level backup copy of data, and incorporates changes generated by the third computing device that are written to the second private store without changing the block-level backup copy of data, thereby operating as the second private writable backup copy requested by the third computing device.

9. The system of claim 8 wherein any number of second private writable backup copies are created with respect to any number of third computing devices and operate independently of each other and independently of the first private writable backup copy.

10. The system of claim 1 further comprising:

wherein the first computing device using the ISCSI service is further configured to;

receive from the second computing device a second unique ID and a second request for a second private writable backup copy of the block-level backup copy of data,

generate a second private store having the second unique ID,

present the second private store as a second logical unit number (LUN) to the second computing device; and

wherein the second computing device is configured to mount the LUN, thereby acquiring access to the second private store, which is based on the archive store and the block-level backup copy of data, and incorporates changes generated by the second computing device that are written to the second private store without changing the block-level backup copy of data, thereby operating as the second private writable backup copy requested by the second computing device, and independent of the first private writable backup copy of data also accessed by the second computing device.

11. The system of claim 10 wherein any number of second private writable backup copies are created and operate independently of each other and independently of the first private writable backup copy.

12. A computer-readable medium, excluding transitory propagating signals, storing instructions that, when executed by at least one computing device comprising one or more processors and computer memory, cause the computing device to perform operations comprising:

executing an Internet Small Computer Systems Interface (ISCSI) service and a media agent in communication with a data storage device,

receiving from a second computing device in communication with the first computing device via ISCSI protocol,

a first unique ID and a first request for a first private writable backup copy of a block-level backup copy of data stored in a data storage device in communication with the media agent;

if an archive store directory corresponding to the block-level backup copy of data was not previously created, generating the archive store directory corresponding to the block-level backup copy of data;

generating a private store directory having the first unique ID received from the second computing device;

presenting the private sparse file as a logical unit number (LUN) to the second computing device, thereby granting the second computing device access to the private store directory operating as the requested private writable backup copy for browsing data extents obtained from the block-level backup copy of data and further for implementing changes to the data extents obtained from the block-level backup copy of data without changing the block-level backup copy of data, and wherein the private store directory is based on the archive store directory, and incorporates changes generated by the second computing device.

13. The computer-readable media of claim 12 wherein the first computing device stores the archive store directory and the private store directory.

14. The computer-readable media of claim 12 wherein the operations further comprise:

receiving from the second computing device a first read request for a first data extent in the LUN,

checking whether the first data extent is represented by a first extent-file in the private store directory, and if so, serving the first data extent from the first extent-file in the private store directory to the second computing device in response to the first read request,

if a private bitmap indicates that the first extent-file is not present in the private store directory, checking whether the first extent-file is present in the archive store directory, and if so, serving the first data extent from the first extent-file in the archive store directory to the second computing device in response to the first read request, and

if the first extent-file is not present in the private store directory and is also not present in the archive store directory, restoring by the media agent executing on the first computing device the first data extent from a first snapshot to the first extent-file stored to the archive store directory.

15. The computer-readable media of claim 12 wherein the operations further comprise:

receiving from the second computing device a first write request to write a first data extent to the LUN;

checking whether the private store comprises a corresponding extent-file for the first data extent, and if so, write the first data extent as received from the second computing device to the private store, thereby overwriting the corresponding extent-file, and

if the private store lacks the corresponding extent-file for the first data extent, checking whether the archive store comprises the corresponding extent-file, and if so, copying the corresponding extent-file from the archive store to the private store, thereby causing the requested private writable backup copy to differ from the block-level backup copy of data upon which the private writable backup copy is based.

16. A method for providing private writable backup copies to user computing devices, the method comprising:

receiving,

by a first computing device that executes an Internet Small Computer Systems Interface (ISCSI) service and a media agent in communication with a data storage device,

from a second computing device in communication with the first computing device via ISCSI protocol,

a first unique ID and a first request for a first private writable backup copy of a block-level backup copy of data in the data storage device;

if an archive store directory corresponding to the block-level backup copy of data was not previously created, generating by the first computing device the archive store directory corresponding to the block-level backup copy of data;

generating by the first computing device a private store directory having the first unique ID received from the second computing device;

presenting by the first computing device the private sparse file as a logical unit number (LUN) to the second computing device; and

mounting the LUN by the second computing device, thereby acquiring access to the private store directory operating as the requested private writable backup copy for browsing data extents obtained from the block-level backup copy of data and further for implementing changes to the data extents obtained from the block-level backup copy of data without changing the block-level backup copy of data, and wherein the private store directory is based on the archive store directory, and incorporates changes generated by the second computing device.

17. The method of claim 16 wherein the first computing device stores the archive store directory and the private store directory.

18. The method of claim 16 further comprising:

receiving by the first computing device from the second computing device a first read request for a first data extent in the LUN,

checking by the first computing device whether the first data extent is represented by a first extent-file in the private store directory, and if so, serving the first data extent from the first extent-file in the private store directory to the second computing device in response to the first read request,

if a private bitmap indicates that the first extent-file is not present in the private store directory, checking by the first computing device whether the first extent-file is present in the archive store directory, and if so, serving the first data extent from the first extent-file in the archive store directory to the second computing device in response to the first read request, and

if the first extent-file is not present in the private store directory and is also not present in the archive store directory, restoring by the media agent executing on the first computing device the first data extent from a first snapshot to the first extent-file stored to the archive store directory.

19. The method of claim 16 further comprising:

receiving by the first computing device from the second computing device a first write request to write a first data extent to the LUN; and

checking by the first computing device whether the private store comprises a corresponding extent-file for the first data extent, and if so, write the first data extent as received from the second computing device to the private store, thereby overwriting the corresponding extent-file.

20. The method of claim 19 further comprising:

if the private store lacks the corresponding extent-file for the first data extent, check whether the archive store comprises the corresponding extent-file, and if so, copy the corresponding extent-file from the archive store to the private store.