Secondary storage editor

• US 10,168,924 B2
• Filed: 06/30/2016
• Issued: 01/01/2019
• Est. Priority Date: 12/03/2014
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Mutha, Manas Bhikchand, Bedadala, Pavan Kumar Reddy, Sinha, Prosenjit
• Primary Examiner(s): Le, Dieu Minh T
• Application Number:
  US15/199,355
• Publication Number:
  US 20170031617A1
• Time in Patent Office: 915 Days
• Field of Search: 714 46, 714 471, 714 15, 714 16, 714 42, 714718, 714719
• 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/1453 using de-duplication of the data
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3442 for planning or managing the needed capacity
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 12/1408 by using cryptography for digital transmission H04L9/00
• CPC Class Codes: G06F 2212/402 Encrypted data
• CPC Class Codes: G06F 3/06 Digital input from, or digital output to, record carriers , e.g. RAID, emulated record carriers or networked record carriers
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0629 Configuration or reconfiguration of storage systems
• CPC Class Codes: G06F 3/0638 Organizing or formatting or addressing of data
• 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: G06F 3/0683 Plurality of storage devices

Abstract

Systems and methods for storage pruning can enable users to delete, edit, or copy backed up data that matches a pattern. Storage pruning can enable fine-grain deletion or copying of these files from backups stored in secondary storage devices. Systems and methods can also enable editing of metadata associated with backups so that when the backups are restored or browsed, the logical edits to the metadata can then be performed physically on the data to create a custom restore or a custom view. A user may perform operations such as renaming, deleting, modifying flags, and modifying retention policies on backed up items. Although the underlying data in the backup may not change, the view of the backup data when the user browses the backup data can appear to include the user'"'"'s changes. A restore of the data can cause those changes to be performed on the backup data.

Claims

1. A method for editing indexing information associated with backup data in an information management system, the method comprising:

receiving a textual pattern by a secondary storage editor implemented on a computing device comprising one or more hardware processors;

searching for the textual pattern in an index, by a media agent component of the information management system,

wherein the index comprises information created during one or more backup operations,

wherein a given backup operation created backup data stored in secondary storage, and

wherein the media agent is implemented on a computing device comprising one or more hardware processors;

identifying, by the media agent, one or more files in the backup data that are represented in the index and match the textual pattern;

deleting from the index, by the media agent, entries corresponding to the one or more identified files without causing the one or more files to be physically deleted from the backup data in the secondary storage,

thereby logically deleting the one or more files from the secondary storage; and

after the logically deleting and when criteria for physical deletion of the one or more files from the secondary storage are met, causing by the media agent the one or more files to be physically deleted from the backup data in the secondary storage.

2. The method of claim 1, further comprising:

after the logically deleting and before the one or more files are physically deleted from the backup data in the secondary storage, receiving by the secondary storage editor a request from a user to view at least some of the backup data in the secondary storage; and

in response to the user request, providing by the secondary storage editor based on the index, a view of the at least some of the backup data that excludes the logically deleted one or more files.

3. The method of claim 1, further comprising:

after the logically deleting and before the one or more files are physically deleted from the backup data in the secondary storage, receiving by the secondary storage editor a request from an administrator of the information management system to view at least some of the backup data in the secondary storage; and

in response to the administrator request, providing by the secondary storage editor based on the index, a view of the at least some of the backup data that indicates that the logically deleted one or more files are deleted.

4. The method of claim 1, further comprising:

after the logically deleting and before the one or more files are physically deleted from the backup data in the secondary storage, preventing by the secondary storage editor using the index at the media agent, a user seeking to browse the backup data in the secondary storage from viewing the logically deleted one or more files.

5. The method of claim 1, further comprising:

after the logically deleting and before the one or more files are physically deleted from the backup data in the secondary storage, preventing by the media agent using the index, a user seeking to restore one of the logically deleted one or more files in the backup data from restoring the one file.

6. The method of claim 1, further comprising:

based on the one or more files being physically deleted from the backup data in the secondary storage, determining by the secondary storage editor whether versions of the one or more files are stored in primary storage; and

physically deleting the versions of one or more files that are stored in the primary storage from the primary storage.

7. The method of claim 1, further comprising:

based on the one or more files being physically deleted from the backup data in the secondary storage, determining by the secondary storage editor whether versions of the one or more files are stored in primary storage; and

physically deleting the versions of one or more files that are stored in the primary storage from the primary storage, based on a storage retention policy for the primary storage.

8. The method of claim 1, further comprising:

based on the one or more files being physically deleted from the backup data in the secondary storage, determining by the secondary storage editor whether versions of the one or more files are stored in primary storage; and

physically deleting the versions of one or more files that are stored in the primary storage from the primary storage, based on criteria for physical deletion of the one or more files from the primary storage.

9. The method of claim 1, further comprising:

based on the one or more files being physically deleted from the backup data in the secondary storage, determining by the secondary storage editor whether versions of the one or more files are stored in primary storage; and

physically deleting the versions of one or more files that are stored in the primary storage from the primary storage,

thereby preventing further backup data of the one or more files from being created in the information management system.

10. The method of claim 1, further comprising:

based on the logically deleting of the one or more files, determining by the secondary storage editor whether versions of the one or more files are stored in primary storage; and

physically deleting the versions of one or more files that are stored in the primary storage from the primary storage.

11. The method of claim 1, further comprising:

based on the logically deleting of the one or more files, determining by the secondary storage editor whether versions of the one or more files are stored in primary storage; and

physically deleting the versions of one or more files that are stored in the primary storage from the primary storage,

thereby preventing further backup data of the one or more files from being created in the information management system.

12. The method of claim 1, wherein a storage manager that managers storage operations in the information management system, including the one or more backup operations, comprises the secondary storage editor, which communicates the textual pattern to the media agent.

13. The method of claim 1, wherein the textual pattern is received from a user via a user interface.

14. The method of claim 1, wherein the textual pattern is a stored pattern associated with a scheduled backup job.

15. The method of claim 1, wherein the criteria for physical deletion of the one or more files from the secondary storage are based on whether a synthetic full backup is scheduled to be performed.

16. The method of claim 1, wherein the logical deleting is an end-user mode deletion that removes the one or more files from access by a user, wherein an administrator maintains access to the one or more files until a physical deletion is performed.

17. The method of claim 1, wherein logically deleting from the secondary storage a given file among the one or more files comprises deleting a pointer that points to the given file;

and

physically deleting the given file based on determining that no pointers point to the given file.

18. An information management system for editing metadata associated with backup data in the information management system, the system comprising:

a secondary storage editor implemented on a first computing device comprising one or more hardware processors;

a media agent implemented on a second computing device comprising one or more hardware processors;

a secondary storage system in communication with the media agent;

wherein the secondary storage editor is configured to;

receive a textual pattern for identifying files stored in the information management system; and

wherein the media agent is configured to;

search for the textual pattern in an index on the second computing device,

wherein the index comprises information created during one or more backup operations that created backup data stored in the secondary storage system,

identify one or more files in the backup data that are represented in the index and match the textual pattern,

delete entries in the index corresponding to the one or more identified files without causing the one or more files to be physically deleted from the backup data in the secondary storage system,

thereby logically deleting the one or more files from the secondary storage system, and

after the one or more files are logically deleted and when criteria for physical deletion of the one or more files from the secondary storage system are met, cause the one or more files to be physically deleted from the backup data in the secondary storage system.

19. The system of claim 18, wherein after the one or more files are logically deleted and before the one or more files are physically deleted from the backup data in the secondary storage system, the secondary storage editor is further configured to:

in response to a request from a user to browse the backup data in the secondary storage system, use the index to provide the user with a view of the backup data that excludes the logically deleted one or more files, and

in response to a request from an administrator to browse the backup data in the secondary storage system, use the index to provide the administrator with a view of the backup data that data that indicates that the one or more files are logically deleted.

20. The system of claim 18, further comprising:

a primary storage system storing data from which at least part of the backup data was created; and

wherein the secondary storage editor is further configured to;

based on the one or more files in the backup data in the secondary storage system being at least one of;

logically deleted and physically deleted, determine whether versions of the one or more files are stored in the primary storage system, and

physically delete the versions of one or more files that are stored in the primary storage system from the primary storage system,

thereby preventing further backup data of the one or more files from being created in the information management system.