Snapshot storage and management system with indexing and user interface

• US 8,140,794 B2
• Filed: 01/18/2011
• Issued: 03/20/2012
• Est. Priority Date: 10/07/2002
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Prahlad, Anand, May, Andreas, Lunde, Norman R., Zhou, Lixin, Kumar, Avinash, Ngo, David
• Primary Examiner(s): RUTZ, JARED IAN
• Application Number:
  US13/008,713
• Publication Number:
  US 20110131187A1
• Time in Patent Office: 427 Days
• Field of Search: 711/162, 707/639
• US Class Current: 711/162
• 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/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 2003/0697 device management, e.g. handlers, drivers, I/O schedulers
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/0601 Interfaces specially adapted for storage systems
• 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/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A system and method of managing stored data in a storage management system. The storage management system includes a storage manager, a media agent connected to the storage manager, and a primary volume connected to the media agent. A plurality of snapshots are taken of the primary volume. The snapshots are indexed by associating respective information with the snapshot. The indexed snapshots are copied to a recovery volume. In this way, browsing features are enabled for the user. The user may view the snapshots in a hierarchical format, and may even view snapshot data in association with the corresponding application. The resultant recovery volume may be used to replace a primary volume.

Claims

1. A method for replacing data in a primary volume with data in a recovery volume, the method comprising:

updating a memory to indicate that the primary volume is no longer identified by a first logical unit number,

wherein the primary volume is stored at a first device identified by the first logical unit number;

updating the memory to indicate that the recovery volume is no longer identified by a second logical unit number,

wherein the recovery volume is stored at a second device identified by the second logical unit number; and

after updating the memory to indicate that the primary volume is no longer identified by a first logical unit number and the recovery volume is no longer identified by the second logical unit number, updating the memory to indicate that the recovery volume is identified by the first logical unit number,

wherein the recovery volume is now usable as the primary volume,

wherein the recovery volume comprises multiple snapshots of the primary volume, and

wherein the recovery volume includes information about one or more applications that created data stored in the primary volume.

2. The method as recited in claim 1, wherein metadata associated with primary volume is maintained in association with the first logical unit number.

3. The method as recited in claim 1, where input and output to both the recovery and primary volumes is suspended during the updating steps.

4. The method of in claim 1, further comprising:

displaying at least a first snapshot to a user, wherein displaying the snapshot includes displaying information associated with an application that created data tracked by the first snapshot, wherein displaying the first snapshot includes displaying at least a date of creation of the first snapshot, a persistence of the first snapshot, or a logical location of the first snapshot.

5. The method of claim 1, further comprising:

displaying at least a first snapshot to a user, wherein displaying the first snapshot includes displaying information associated with an application that created data tracked by the first snapshot.

6. The method of claim 1, further comprising:

displaying at least a first snapshot of the recovery volume to a user via a screen corresponding to the application that created the data of the primary volume.

7. The method of claim 1, further comprising:

creating a second snapshot of the primary volume of data, wherein the second snapshot only tracks changes to the primary volume of data after a first snapshot was created; and

selecting the second snapshot as a source of data changed after the first snapshot was created to copy to the recovery volume.

8. One or more non-transitory, computer-readable memories storing instructions that when executed by at least one data processor perform a method for replacing data in a primary volume with data in a recovery volume, the method comprising:

updating a memory to indicate that the primary volume is no longer identified by a first logical unit number,

wherein the primary volume is stored at a first device identified by the first logical unit number;

updating the memory to indicate that the recovery volume is no longer identified by a second logical unit number,

wherein the recovery volume is stored at a second device identified by the second logical unit number; and

after updating the memory to indicate that the primary volume is no longer identified by a first logical unit number and the recovery volume is no longer identified by the second logical unit number, updating the memory to indicate that the recovery volume is identified by the first logical unit number,

wherein the recovery volume is now usable as the primary volume,

wherein the recovery volume comprises multiple snapshots of the primary volume, and

wherein the recovery volume includes information about one or more applications that created data stored in the primary volume.

9. One or more non-transitory, computer-readable memories of claim 8, wherein metadata associated with primary volume is maintained in association with the first logical unit number.

10. One or more non-transitory, computer-readable memories of claim 8, where input and output to both the recovery and primary volumes is suspended during the updating.

11. One or more non-transitory, computer-readable memories of claim 8, further comprising:

displaying at least a first snapshot to a user, wherein displaying the snapshot includes displaying information associated with an application that created data tracked by the first snapshot, wherein displaying the first snapshot includes displaying at least a date of creation of the first snapshot, a persistence of the first snapshot, or a logical location of the first snapshot.

12. One or more non-transitory, computer-readable memories of claim 8, further comprising:

displaying at least a first snapshot to a user, wherein displaying the first snapshot includes displaying information associated with an application that created data tracked by the first snapshot.

13. One or more non-transitory, computer-readable memories of claim 8 further comprising:

displaying at least a first snapshot of the recovery volume to a user via a screen corresponding to the application that created the data of the primary volume.

14. One or more non-transitory, computer-readable memories of claim 8, further comprising:

creating a second snapshot of the primary volume of data, wherein the second snapshot only tracks changes to the primary volume of data after a first snapshot was created; and

selecting the second snapshot as a source of data changed after the first snapshot was created to copy to the recovery volume.

15. A system for replacing data in a primary volume with data in a recovery volume, the system comprising:

a first data storage device;

a second data storage device;

at least one memory, wherein the memory and first and second data storage devices are coupled via at least one network;

means for updating the memory to indicate that the primary volume is no longer identified by a first logical unit number,

wherein the primary volume is stored at the first data storage device identified by the first logical unit number;

means for updating the memory to indicate that the recovery volume is no longer identified by a second logical unit number,

wherein the recovery volume is stored at the second data storage device identified by the second logical unit number; and

means for updating the memory to indicate that the recovery volume is identified by the first logical unit number after updating the memory to indicate that the primary volume is no longer identified by a first logical unit number and the recovery volume is no longer identified by the second logical unit number,

wherein the recovery volume is now usable as the primary volume,

wherein the recovery volume comprises multiple snapshots of the primary volume, and

wherein the recovery volume includes information about one or more applications that created data stored in the primary volume.

16. The system of claim 15 wherein metadata associated with primary volume is maintained in association with the first logical unit number.

17. The system of claim 15 where input and output to both the recovery and primary volumes is suspended during the updating.