Collaborative restore in a networked storage system

• US 10,176,053 B2
• Filed: 03/11/2016
• Issued: 01/08/2019
• Est. Priority Date: 06/13/2012
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Muller, Marcus S., Ngo, David
• Primary Examiner(s): Ruiz, Angelica
• Application Number:
  US15/067,766
• Publication Number:
  US 20160266980A1
• Time in Patent Office: 1,033 Days
• Field of Search: 707600-831, 707899, 707999001-999206
• CPC Class Codes: G06F 11/1415 at system level
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1453 using de-duplication of the data
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/137 Hash-based content-based indexing of textual data G06F16/31
• CPC Class Codes: G06F 16/16 File or folder operations, e.g. details of user interfaces specifically adapted to file systems
• CPC Class Codes: G06F 16/1748 De-duplication implemented within the file system, e.g. based on file segments de-duplication techniques in storage systems for the management of data blocks G06F3/0641
• CPC Class Codes: G06F 16/1752 based on file chunks
• CPC Class Codes: G06F 16/176 Support for shared access to files; File sharing support
• CPC Class Codes: G06F 16/1847 specifically adapted to static storage, e.g. adapted to flash memory or SSD
• CPC Class Codes: G06F 16/185 Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof details of archiving G06F16/11
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/24 Querying
• 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 16/275 : Synchronous replication
• CPC Class Codes: G06F 16/90 : Details of database functions independent of the retrieved data types
• CPC Class Codes: G06F 16/95 : Retrieval from the web
• CPC Class Codes: G06F 2201/80 : Database-specific techniques

Abstract

A storage system according to certain embodiments includes a client-side signature repository that includes information representative of a set of data blocks stored in primary storage. During restore operations, the system can use the client-side signature repository to identify data blocks located in primary storage. The system can also use the client-side signature repository to identify multiple locations within primary storage where instances of some of the data blocks to be restored are located. Accordingly, during a restore operation of one client computing device, the system can source a data block to be restored to the client computing device from another client computing device that is in primary storage.

Claims

1. A method of restoring data to a first client computing device located in a primary storage subsystem using data blocks residing in a data store associated with a second client computing device located in the primary storage subsystem, the method comprising:

maintaining in a signature repository data block, signatures corresponding to data blocks of primary data, and location information of the data blocks within the primary storage subsystem, the data blocks of primary data stored in a native format associated with one or more corresponding source applications, wherein the data blocks of primary data are copied to a secondary memory subsystem during a backup operation to create secondary copy data blocks, the secondary copy data blocks stored in a non-native format that is different than the native format;

receiving a set of data block signatures associated with a request to restore a set of the secondary copy data blocks stored in the secondary storage subsystem;

querying, using one or more processors, the signature repository with the set of data block signatures to identify at least a first group of data block signatures that reside in the signature repository, the first group of data block signatures corresponding to a first group of data blocks stored in the primary storage subsystem;

retrieving at least some of the first group of data blocks stored in the primary storage system;

identifying a second group of data blocks of the set of secondary copy data blocks that do not reside in the primary storage subsystem; and

restoring the set of the secondary copy data blocks using the first group of data blocks retrieved from primary memory and the second group of data blocks retrieved from the secondary storage subsystem.

2. The method of claim 1, wherein the signature repository further includes, for each copy of a data block referenced by a signature in the signature repository:

an indication as to which respective client computing device of a plurality of client computing devices stores the data block; and

location information indicating where the data block is located in a data store of the respective client computing device.

3. The method of claim 1, wherein the signature repository further includes, for each respective signature referenced in the signature repository, an indication as to the number of copies of the data block corresponding to the respective signature that are stored in the primary storage subsystem.

4. The method of claim 1, wherein copies of at least a first data block having a corresponding signature included signature repository reside in data stores associated with multiple ones of a plurality of client computing devices, and wherein the signature repository further includes a sourcing order indicator usable to determine which of the copies of the first data block is to be used in the restore of the set of secondary copy data blocks.

5. The method of claim 1, wherein the secondary copy data blocks are accessible using an information management system that is configured to manage the creation of the secondary copy data blocks, and wherein the primary data is accessible by the applications executing on the client computing devices without use of the information management system.

6. The method of claim 1, wherein the data block signatures are generated using a hash algorithm.

7. The method of claim 1, wherein the data blocks of primary data are generated by one or more applications executing on a first computing device and the first group of data blocks correspond to data generated by one or more applications executing on at least a second computing device.

8. The method of claim 1, wherein the secondary storage subsystem contains deduplicated data.

9. The method of claim 1, wherein the first group of data blocks comprises deduplicated data.

10. The method of claim 1 further comprising converting the second group of data blocks stored in the non-native format into the native format.

11. A storage system for restoring data to a primary storage subsystem using data blocks residing in the primary storage subsystem, the storage system comprising:

a signature repository including one or more data block signatures corresponding to data blocks of primary data, and location information of the data blocks within the primary storage subsystem, the data blocks of primary data stored in a native format associated with one or more corresponding source applications, wherein the data blocks of primary data are copied to a secondary memory subsystem during a backup operation to create secondary copy data blocks, the secondary copy data blocks stored in a non-native format that is different than the native format; and

a repository agent executing on a computing device that is separate from the plurality of client computing devices, the repository agent configured to;

maintain the signature repository in one or more storage devices;

receive a set of data block signatures associated with a request to restore a set of the secondary copy data blocks stored in the secondary storage subsystem;

query the signature repository with the set of data block signatures to identify at least a first group of data block signatures corresponding to a first group of data blocks stored in the primary storage subsystem; and

wherein the first group of data blocks are retrieved from the primary storage subsystem;

wherein a second group of data blocks that do not reside in the primary storage subsystem are retrieved from the secondary storage subsystem; and

wherein the set of secondary copy data blocks is restored using the first group of data blocks retrieved from the primary storage subsystem, and the second group of data blocks retrieved from the secondary storage subsystem.

12. The system of claim 11, wherein the signature repository further includes, for each data copy of a data block referenced in the signature repository:

an indication as to which respective client computing device of a plurality of client computing devices stores the data block; and

location information indicating where the data block is located in a data store of the respective client computing device.

13. The system of claim 11, wherein the signature repository further includes, for each respective signature referenced in the signature repository, an indication as to the number of copies of the data block corresponding to the respective signature that are stored in the primary storage subsystem.

14. The system of claim 11, wherein copies of at least a first data block having a corresponding signature included signature repository reside in data stores associated with multiple ones of a plurality of client computing devices, and wherein the signature repository further includes a sourcing order indicator usable to determine which of the copies of the first data block is to be used in the restore of the set of secondary copy data blocks.

15. The system of claim 11, wherein the secondary copy data blocks are accessible using an information management system that is configured to manage the creation of the secondary copy data blocks, and wherein the primary data is accessible by the applications executing on the client computing devices without use of the information management system.

16. The system of claim 11, wherein the data block signatures are generated using a hash algorithm.

17. The system of claim 11, wherein the data blocks of primary data are generated by one or more applications executing on a first computing device and the first group of data blocks correspond to data generated by one or more applications executing on at least a second computing device.

18. The system of claim 11, wherein the secondary storage subsystem comprises deduplicated data.

19. The system of claim 11, wherein the first group of data blocks comprises deduplicated data.

20. The system of claim 11 further wherein the second group of data blocks stored in the non-native format are converted into the native format.