Integrated snapshot interface for a data storage system

• US 9,928,002 B2
• Filed: 04/15/2016
• Issued: 03/27/2018
• Est. Priority Date: 04/23/2012
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Kumarasamy, Paramasivam, Mitkar, Amit, Zakharkin, Dmitriy Borisovich
• Primary Examiner(s): Chau, Dung K
• Application Number:
  US15/099,865
• Publication Number:
  US 20160334995A1
• Time in Patent Office: 711 Days
• Field of Search: 707649, 707672, 707610, 707641, 707655, 7079992
• 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/2089 Redundant storage control functionality
• 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 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• 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/0683 Plurality of storage devices
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD

Abstract

A data storage system includes a generic snapshot interface, allowing for integration with a wide variety of snapshot-capable storage devices. The generic interface can be a programming interface (e.g., an application programming interface [API]). Using the snapshot interface, storage device vendors can integrate their particular snapshot technology with the data storage system. For instance, the data storage system can access a shared library of functions (e.g., a dynamically linked library [DLL]) provided by the vendor (or another by appropriate entity) and that complies with the specifications of the common programming interface. And by invoking the appropriate functions in the library, the data storage system implements the snapshot operation on the storage device.

Claims

1. A data storage system, comprising:

a source system in communication with a destination system comprising a first storage device, the first storage device configured to perform snapshot operations;

at least one software application executing on the source system and generating production data;

a snapshot management module executing on one or more processors and configured to;

receive a request to perform a snapshot operation involving a stored version of at least a portion of the production data that resides on the first storage device;

determine that the first storage device is a first type of storage device which corresponds to a particular vendor and/or a particular product from the particular vendor;

determine that the source system does not include pre-configured functionality for causing the first storage device to perform the snapshot operation;

communicate with the destination system to identify one or more functions for performing the requested snapshot operation that are compatible with a programming interface residing on the source system; and

invoke an instance of the one or more identified functions using the programming interface,

wherein a snapshot engine residing on the destination system is responsive to the invoking of the instance of the one or more identified functions to perform the requested snapshot operation.

2. The data storage system of claim 1, wherein the instance of the one or more identified functions is accessed from a shared library associated with the first storage device.

3. The data storage system of claim 2, wherein the shared library is located at the destination system and is accessed by the source system.

4. The data storage system of claim 1, wherein the first storage device is configured to perform hardware snapshots.

5. The data storage system of claim 1, wherein the requested snapshot operation includes one or more of a snapshot creation operation, a snapshot mount operation, and a snapshot revert operation.

6. The data storage system of claim 1, wherein the snapshot management module resides on the source system.

7. The data storage system of claim 1, wherein the source system is in communication with a second storage device of a second type that is configured to perform snapshot operations, and wherein the snapshot management module is further configured to:

receive a request to perform a second snapshot operation involving a stored version of at least a portion of the production data that resides on the second storage device;

determine that the second storage device is a second type of storage device different from the first type of storage device;

determine that the source system includes one or more pre-configured functions for causing the second storage device to perform the second snapshot operation; and

instruct a snapshot engine residing on the second storage device to perform the requested second snapshot operation based at least in part on the one or more pre-configured functions.

8. The data storage system of claim 7, wherein the one or more identified functions are provided by a first vendor and the one or more pre-configured functions provided by a second vendor.

9. The data storage system of claim 1, wherein the snapshot management module includes pre-configured functionality for causing storage devices of another type to perform snapshot operations without using the programming interface.

10. The data storage system of claim 9, wherein the pre-configured functionality includes one or more functions that are not compatible with the programming interface.

11. The data storage system of claim 1, wherein the snapshot management module resides on one or more processors of the source system.

12. The data storage system of claim 1, wherein the snapshot management module resides on one or more processors of a proxy computing device that is separate from the source system.

13. A method of performing one or more snapshot operations on production data generated in a data storage system, the method comprising:

receiving a request to perform a snapshot operation involving a stored version of at least a portion of production data that resides on a first storage device of a destination system, the production data generated by at least one software application executing on a source system that is in communication with the first storage device, the first storage device configured to perform snapshot operations;

determining that the first storage device is a first type of storage device which corresponds to a particular vendor and/or a particular product from the particular vendor;

determining that the source system does not include pre-configured functionality for causing the first storage device to perform the snapshot operation;

communicating with the destination system to identify one or more functions for performing the requested snapshot operation that are compatible with a programming interface residing on the source system; and

invoking, using one or more computer processors, an instance of the one or more identified functions using the programming interface,

wherein a snapshot engine residing on the destination system is responsive to the invoking of the instances of the one or more identified functions to perform the requested snapshot operation.

14. The method of claim 13, further comprising accessing the instance of the one or more identified functions from a shared library associated with the first storage device.

15. The method of claim 14, wherein the shared library is located at the destination system and is accessed by the source system.

16. The method of claim 13, wherein the first storage device is configured to perform hardware snapshots.

17. The method of claim 13, wherein the requested snapshot operation includes one or more of a snapshot creation operation, a snapshot mount operation, and a snapshot revert operation.

18. The method of claim 13, wherein the source system is in communication with a second storage device of a second type and that is configured to perform snapshot operations, the method further comprising:

receiving a request to perform a second snapshot operation involving a stored version of at least a portion of the production data that resides on the second storage device;

determining that the second storage device is a second type of storage device different from the first type of storage device;

determining that the source system includes one or more pre-configured functions for causing the second storage device to perform the second snapshot operation; and

instructing a snapshot engine residing on the second storage device to perform the requested second snapshot operation based at least in part on the one or more pre-configured functions.

19. The method of claim 18, wherein the one or more identified functions are provided by a first vendor and the one or more pre-configured functions provided by a second vendor.

20. The method of claim 13, wherein the source system includes pre-configured functionality for causing storage devices of another type to perform snapshot operations without using the programming interface.