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:
Systems and methods are disclosed for cross-system user-level management of data objects stored in one or more information management systems, and for user-level management of data storage quotas in information management systems, including data objects in secondary storage. An illustrative quota manager is associated with one or more information management systems. The quota manager comprises a quota value representing the maximum amount of data storage allowed for a given end-user's primary and secondary data in the one or more information management systems. The quota manager determines whether data associated with the end-user has exceeded the storage quota, and if so, prompts the end-user to select data for deletion, the deletion to be implemented globally, across the primary and secondary storage subsystems of the respective one or more information management systems. Meanwhile, so long as the quota is exceeded, the quota manager instructs storage managers to block backups of end-user's data.
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 according to certain aspects improves the process of sending emails containing attachments. The system can detect a request to send an email containing attachments to one or more recipients, create a copy of the attachments on a network storage device, replace the attachments contained in the email with links to the copies of the attachments, and send the email containing the links to the one or more recipients.
Abstract:
A system according to certain aspects improves the process of sending emails containing attachments. The system can detect a request to send an email containing attachments to one or more recipients, create a copy of the attachments on a network storage device, replace the attachments contained in the email with links to the copies of the attachments, and send the email containing the links to the one or more recipients.
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:
The data storage system according to certain aspects can filter secondary copies of data (e.g., backups, snapshots, archives, etc.) generated by multiple client computing devices into a single, filtered, global reference copy. A reference copy may be a filtered view or representation of secondary storage data in a data storage system. A reference copy may include a data structure that includes references to a subset of secondary storage data that meets certain filtering criteria. The filtering criteria may be specified by users according to user preference. Data included in a reference copy may be stored in native format (e.g., format of the application that generated the data) and be accessible through the application associated with the data.
Abstract:
Systems and methods are described herein for graphically representing an information management system based on the characteristics of within the system. The systems and methods interface with various components of the system (e.g., administrative components, index components, and so on) to identify data having certain characteristics (e.g., personal data), and generate or render information (e.g., a heat map or other visual display) that represents areas or locations within the system storing the data. Thus, the systems and methods, in some embodiments, generate or create a data-specific view into the information management system.
Abstract:
Systems and methods for providing and/or facilitating live browsing of granular mail or mailbox data, such as data stored within Exchange mailboxes, are described. For example, the systems and methods may provide mechanisms for browsing and/or restoring granular data (e.g., email data) from an Exchange database backup copy (or other secondary copy), without having to restore the entire database from the backup copy.
Abstract:
An improved content indexing (CI) system is disclosed herein. For example, the improved CI system may include a distributed architecture of client computing devices, media agents, a single backup and CI database, and a pool of servers. After a file backup occurs, the backup and CI database may include file metadata indices and other information associated with backed up files. Servers in the pool of servers may, in parallel, query the backup and CI database for a list of files assigned to the respective server that have not been content indexed. The servers may then request a media agent to restore the assigned files from secondary storage and provide the restored files to the servers. The servers may then content index the received restored files. Once the content indexing is complete, the servers can send the content index information to the backup and CI database for storage.