Abstract:
According to certain aspects, a system can include a client computing device configured to: in response to user interaction, store an identifier associated with a first tag in association with a first file; and in response to instructions to perform a secondary copy operation, forward the first file, a second file, and the identifier associated with the first tag. The system may also include a secondary storage controller computer(s) configured to: based on a review of the identifier associated with the first tag, identify the first file as having been tagged with the first tag; electronically obtain rules associated with the first tag; perform on the first file at least a first secondary storage operation specified by the rules associated with the first tag; and perform on the second file at least a second secondary storage operation, wherein the first and second secondary storage operations are different.
Abstract:
A information management system allows a user to search through a secondary copy of data, such as a back up, archive, or snapshot without first retrieving the secondary copy of data. Instead, the system constructs lightweight data that can be displayed to a user as a representation of the search results. Lightweight data may include metadata or other information that identifies data included in the secondary copy of data. The lightweight data may be perceived as being the secondary copy of data and allow a user to browse through search results. Once the user identifies a search result that is of interest, information in the lightweight data can be used to retrieve the secondary copy of data. Because lightweight data may have a smaller file size than the file size of the secondary copy of data, the latency of performing a search may be reduced.
Abstract:
An information management system according certain aspects may be configured to generate a snapshot of data relating to a plurality of applications. The system may include first and second data agents associated with first and second applications, respectively. The system may also include a snapshot manager configured to: in response to receiving notifications from the first and second data agents that the first and second applications are in consistent states: obtain a snapshot of the logical volume including data generated by the first and second applications; generate mapping information between the first application and a portion of the snapshot relating to the first application based at least in part on metadata obtained by the first data agent; and generate mapping information between the second application and a portion of the snapshot relating to the second application based at least in part on metadata obtained by the second data agent.
Abstract:
According to certain aspects, systems and methods for archiving and/or backing up PST files or other mail or calendar data, or the like (“off-line mail data”) are provided. Off-line mail data can be searched for in a client computer system, a copy of which may be transferred to secondary storage. Further, emails, contacts, calendar data, and/or the like (e.g., Microsoft Outlook data) contained in the transferred off-line mail data may be extracted, wherein it is determined whether copies of the data already exist backup data. Off-line mail data that already exists in backup can be deleted from the PST file. Following back-up of the off-line mail data, the backed up file may be deleted from the client system and/or the creation of future off-line mail files may be disabled.
Abstract:
An information management system according to certain aspects may be configured to generate a snapshot of data relating to a plurality of applications. The system may include a plurality of data agents, wherein each data agent is associated with at least one of a plurality of applications, and data generated by the plurality of applications is stored in a logical volume in primary storage. The system may also include a snapshot manager configured to detect the plurality of applications; check with the plurality of data agents whether the associated applications are in consistent states; obtain a snapshot of the logical volume in response to receiving notifications from the plurality of data agents that the associated applications are in consistent states; and generate mapping information between a particular one of the plurality of applications and a portion of the snapshot relating to the particular one of the plurality of applications.
Abstract:
An information management system allows a user to search through a secondary copy of data, such as a backup, archive, or snapshot without first retrieving the secondary copy of data. Instead, the system constructs lightweight data that can be displayed to a user as a representation of the search results. Lightweight data may include metadata or other information that identifies data included in the secondary copy of data. The lightweight data may be perceived as being the secondary copy of data and allow a user to browse through search results. Once the user identifies a search result that is of interest, information in the lightweight data can be used to retrieve the secondary copy of data. Because lightweight data may have a smaller file size than the file size of the secondary copy of data, the latency of performing a search may be reduced.
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.
Abstract:
A system for providing user access to electronic mail includes an email client and an email server. The email client receives and communicates a user interaction with an email message The email server that receives the communication, determines whether the email message stored in a live database or in a backup storage. Upon determination that the email message is stored in a backup storage, the email server performs a message exchange with a backup storage system to perform the user-requested action.
Abstract:
A information management system allows a user to search through a secondary copy of data, such as a back up, archive, or snapshot without first retrieving the secondary copy of data. Instead, the system constructs lightweight data that can be displayed to a user as a representation of the search results. Lightweight data may include metadata or other information that identifies data included in the secondary copy of data. The lightweight data may be perceived as being the secondary copy of data and allow a user to browse through search results. Once the user identifies a search result that is of interest, information in the lightweight data can be used to retrieve the secondary copy of data. Because lightweight data may have a smaller file size than the file size of the secondary copy of data, the latency of performing a search may be reduced.
Abstract:
According to certain aspects, a system can include a client computing device configured to: in response to user interaction, store an identifier associated with a first tag in association with a first file; and in response to instructions to perform a secondary copy operation, forward the first file, a second file, and the identifier associated with the first tag. The system may also include a secondary storage controller computer(s) configured to: based on a review of the identifier associated with the first tag, identify the first file as having been tagged with the first tag; electronically obtain rules associated with the first tag; perform on the first file at least a first secondary storage operation specified by the rules associated with the first tag; and perform on the second file at least a second secondary storage operation, wherein the first and second secondary storage operations are different.