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: Data protection resources are automatically scaled to the needs of data source(s) in an application orchestrator computing environment, such as a cluster in a Kubernetes deployment. The approach is adaptable to data sources in production clusters or application suites that are not application orchestrator deployments, such as a cloud-based database-as-a-service (DBaaS). A data storage management system protects cluster-based data with an elastic number of data protection resources (e.g., data agents, media agents), which are deployed on demand. The number of data protection resources deployed for a particular job are appropriate to the workload(s) at present and depend on a variety of scaling factors. In some embodiments, data protection resources are deployed within the same cluster as the data sources.

Abstract: An information management system includes a storage manager for managing backup and/or restore operations for one or more client computing devices. The storage manager may be in communication with a resource administrator of a computing resource cluster, wherein the resource administrator instantiates one or more computing pods using the computing resource cluster. The resource administrator may receive a request for computing resources from the storage manager and provision the computing pods based on the request. The resource administrator may then select a pre-configured container image from one or more pre-configured container images based on the computing resource request, wherein the pre-configured container image configures a computing pod to create secondary copies of primary data from a particular primary data source of the information management system.

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: 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: 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: 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.

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 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.

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 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 information management system includes a storage manager for managing backup and/or restore operations for one or more client computing devices. The storage manager may be in communication with a resource administrator of a computing resource cluster, wherein the resource administrator instantiates one or more computing pods using the computing resource cluster. The resource administrator may receive a request for computing resources from the storage manager and provision the computing pods based on the request. The resource administrator may then select a pre-configured container image from one or more pre-configured container images based on the computing resource request, wherein the pre-configured container image configures a computing pod to create secondary copies of primary data from a particular primary data source of the information management system.

Abstract: An improved content indexing system is disclosed herein that content indexing system combines the functionality of the backup metadata database and the content index database into a single backup and content index database to avoid the need to perform synchronization operations. By using a single backup and content index database, the content indexing system also reduces the computing performance costs that would be associated with the synchronization operations as the amount of indexed content increases, thereby solving scalability issues.

Abstract: Systems and methods for performing backup operations and other secondary copy operations for mail servers, such as Exchange servers, are described. In some cases, the systems and methods perform multi-streaming backup and other copy operations using a single mailbox agent, which launches backup streams via a coordinator that determines when to launch streams, at what mailboxes (or folders) to launch the streams, and so on. The coordinator communicates with controllers at different machines (e.g., servers) to be backed up, and may assign streams, mailboxes, and so on, to the different controllers, which perform the backup operations for their assigned mailboxes and/or clients.

Abstract: Data protection resources are automatically scaled to the needs of data source(s) in an application orchestrator computing environment, such as a cluster in a Kubernetes deployment. The approach is adaptable to data sources in production clusters or application suites that are not application orchestrator deployments, such as a cloud-based database-as-a-service (DBaaS). A data storage management system protects cluster-based data with an elastic number of data protection resources (e.g., data agents, media agents), which are deployed on demand. The number of data protection resources deployed for a particular job are appropriate to the workload(s) at present and depend on a variety of scaling factors. In some embodiments, data protection resources are deployed within the same cluster as the data sources.

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: An improved content indexing system is disclosed herein that content indexing system combines the functionality of the backup metadata database and the content index database into a single backup and content index database to avoid the need to perform synchronization operations. By using a single backup and content index database, the content indexing system also reduces the computing performance costs that would be associated with the synchronization operations as the amount of indexed content increases, thereby solving scalability issues.

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: 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.