Abstract: An illustrative cloud-based air-gapped data storage management (destination) system obtains authorized access to other (source) systems' backup copies, replicates those copies within the destination system, parses supplemental metadata included in the source backup copies, and integrates the replica copies into the destination system as though natively created there. Replica copies are integrated as backup copies without first restoring the source backup copies to a native data format. The source system lacks knowledge of or connectivity with the destination system, thus maintaining an “air gap” between the systems. The destination system preferably operates in a cloud computing environment. The destination system uses supplemental metadata from the replica copies to re-create or mimic the source's computing environment and to restore backed up data from the replica copies.

Abstract: An exemplary system preserves the autonomy of two or more distinct storage management systems all the while enabling backed up data to be restored from a first storage management system (the “local system”) to a specially-configured client in a second storage management system (the “remote system”). For example, backed up data in the local system (e.g., a secondary copy of production data) may be transferred, in a restore operation, from secondary storage in the local storage management system, which originated the data, to a client of the remote storage management system (the “remote client”). As a specially-configured “restore-only client,” the remote client is limited to receiving backed up data from the local storage management system, via restore operation(s) managed by the local storage manager. The remote client remains a full-fledged client in its home system, the remote storage management system.

Abstract: A storage manager for an information management system determines whether one or more predetermined conditions have been met for transferring metadata of previously performed backup jobs stored in a first management database. A backup job may correspond to a backup operation of a primary storage device of a first client computing device. In response to a determination that one or more of the predetermined conditions have been met, the storage manager may transfer metadata for a second plurality of backup jobs to a second management database of a recovery manager. The recovery manager may receive a request to restore data to the primary storage device of the first client computing device based on the metadata of the second plurality of backup jobs. A media agent managed by the recovery manager may then restore the requested data to the primary storage device of the first client computing device.

Abstract: Systems and methods are disclosed for cross-system storage management for transferring data across autonomous information management systems. Data may be transferred from one information management system to another information management system without interfering with or overriding each system's autonomy. For example, a secondary copy of production data (e.g., backed up data) is transferred from a first information management system that originated the data to a component of another “foreign” information management system. A first storage manager that manages the first information management system also manages the cross-system data transfer operation to a “foreign” client computing device, which remains under autonomous management as a component of the foreign information management system.

Abstract: Systems and methods that facilitate an information management system to store sets of data, such as backup or secondary copies of production data, to cloud storage libraries in a format native to the cloud storage library are disclosed. The systems and methods create storage policies for the sets of data that identify the cloud storage libraries to which the sets of data are to be stored. Via the storage policies, one or more media agents or servers transfer data blocks of the sets of data to software development kits (SDKs) associated with the cloud storage libraries. The SDKs add external metadata, such as metadata associated with a native format for the cloud library (e.g., Microsoft Azure or other cloud computing service), to the data blocks, before the data blocks are stored to the cloud storage library.

Abstract: A deduplicated storage system is provided according to certain embodiments that uses one or more mechanisms to assign the deduplication databases based on the type of the client device and automatically create a new deduplication database when critical thresholds are reached. In other embodiments, deduplication databases are further split into multiple database partitions. Based on a data block distribution policy, each data block is then further assigned to a particular database partition within the deduplication database to further improve efficiency and speed of the deduplication process.

Abstract: A deduplicated storage system is provided according to certain embodiments that uses one or more mechanisms to assign the deduplication databases based on the type of the client device and automatically create a new deduplication database when critical thresholds are reached. In other embodiments, deduplication databases are further split into multiple database partitions. Based on a data block distribution policy, each data block is then further assigned to a particular database partition within the deduplication database to further improve efficiency and speed of the deduplication process.

Abstract: A deduplicated storage system is provided according to certain embodiments that uses one or more mechanisms to assign the deduplication databases based on the type of the client device and automatically create a new deduplication database when critical thresholds are reached. In other embodiments, deduplication databases are further split into multiple database partitions. Based on a data block distribution policy, each data block is then further assigned to a particular database partition within the deduplication database to further improve efficiency and speed of the deduplication process.

Abstract: Systems and methods are disclosed for cross-system storage management for transferring data across autonomous information management systems. Data may be transferred from one information management system to another information management system without interfering with or overriding each system's autonomy. For example, a secondary copy of production data (e.g., backed up data) is transferred from a first information management system that originated the data to a component of another “foreign” information management system. A first storage manager that manages the first information management system also manages the cross-system data transfer operation to a “foreign” client computing device, which remains under autonomous management as a component of the foreign information management system.

Abstract: Systems and methods that facilitate an information management system to store sets of data, such as backup or secondary copies of production data, to cloud storage libraries in a format native to the cloud storage library are disclosed. The systems and methods create storage policies for the sets of data that identify the cloud storage libraries to which the sets of data are to be stored. Via the storage policies, one or more media agents or servers transfer data blocks of the sets of data to cloud storage SDKs associated with the cloud storage libraries. The cloud storage SDKs then add external metadata, such as metadata associated with a native format for the cloud library to the data blocks, before the data blocks are stored to the cloud storage library.

Abstract: A system for performing continuous transaction log backups with minimal resource usage of the client computing devices that are processing the transactions is disclosed. The system detects at least one input/output (I/O) activity at a client computing device. The I/O activity can be associated with at least one database operation performed via the client computing device. The system then executes one or more native commands to backup transactions log data associated with the detected I/O activity to a virtualized location. Backing-up the transactions log data comprises dynamically identifying a mount path location corresponding to the virtualized location, and transferring the transactions log data to the dynamically identified mount path using the one or more native commands. The system can then perform data processing operations (for example, data chunking and deduplicating) on the transactions log data after it is received at the dynamically identified mount path location.

Abstract: An exemplary system preserves the autonomy of two or more distinct storage management systems all the while enabling backed up data to be restored from a first storage management system (the “local system”) to a specially-configured client in a second storage management system (the “remote system”). For example, backed up data in the local system (e.g., a secondary copy of production data) may be transferred, in a restore operation, from secondary storage in the local storage management system, which originated the data, to a client of the remote storage management system (the “remote client”). As a specially-configured “restore-only client,” the remote client is limited to receiving backed up data from the local storage management system, via restore operation(s) managed by the local storage manager. The remote client remains a full-fledged client in its home system, the remote storage management system.

Abstract: Systems and methods are disclosed for cross-system storage management for transferring data across autonomous information management systems. Data may be transferred from one information management system to another information management system without interfering with or overriding each system's autonomy. For example, a secondary copy of production data (e.g., backed up data) is transferred from a first information management system that originated the data to a component of another “foreign” information management system. A first storage manager that manages the first information management system also manages the cross-system data transfer operation to a “foreign” client computing device, which remains under autonomous management as a component of the foreign information management system.

Abstract: Systems and methods that facilitate an information management system to store sets of data, such as backup or secondary copies of production data, to cloud storage libraries in a format native to the cloud storage library are disclosed. The systems and methods create storage policies for the sets of data that identify the cloud storage libraries to which the sets of data are to be stored. Via the storage policies, one or more media agents or servers transfer data blocks of the sets of data to cloud storage SDKs associated with the cloud storage libraries. The cloud storage SDKs then add external metadata, such as metadata associated with a native format for the cloud library to the data blocks, before the data blocks are stored to the cloud storage library.

Abstract: Systems and methods are disclosed for cross-system storage management for transferring data across autonomous information management systems. Data may be transferred from one information management system to another information management system without interfering with or overriding each system's autonomy. For example, a secondary copy of production data (e.g., backed up data) is transferred from a first information management system that originated the data to a component of another “foreign” information management system. A first storage manager that manages the first information management system also manages the cross-system data transfer operation to a “foreign” client computing device, which remains under autonomous management as a component of the foreign information management system.

Abstract: An exemplary system preserves the autonomy of two or more distinct storage management systems all the while enabling backed up data to be restored from a first storage management system (the “local system”) to a specially-configured client in a second storage management system (the “remote system”). For example, backed up data in the local system (e.g., a secondary copy of production data) may be transferred, in a restore operation, from secondary storage in the local storage management system, which originated the data, to a client of the remote storage management system (the “remote client”). As a specially-configured “restore-only client,” the remote client is limited to receiving backed up data from the local storage management system, via restore operation(s) managed by the local storage manager. The remote client remains a full-fledged client in its home system, the remote storage management system.

Abstract: Systems and methods are disclosed for cross-system storage management for transferring data across autonomous information management systems. Data may be transferred from one information management system to another information management system without interfering with or overriding each system's autonomy. For example, a secondary copy of production data (e.g., backed up data) is transferred from a first information management system that originated the data to a component of another “foreign” information management system. A first storage manager that manages the first information management system also manages the cross-system data transfer operation to a “foreign” client computing device, which remains under autonomous management as a component of the foreign information management system.

Abstract: Systems and methods are disclosed for cross-system storage management for transferring data across autonomous information management systems. Data may be transferred from one information management system to another information management system without interfering with or overriding each system's autonomy. For example, a secondary copy of production data (e.g., backed up data) is transferred from a first information management system that originated the data to a component of another “foreign” information management system. A first storage manager that manages the first information management system also manages the cross-system data transfer operation to a “foreign” client computing device, which remains under autonomous management as a component of the foreign information management system.

Abstract: Systems and methods for managing pod cells using a global repository cell (GRC), as well as providing cloud-based storage to the pod cells and the GRC, are described. In some embodiments, the cloud-based storage enables an enterprise, or multiple enterprises to sync the operations between a master cell (e.g. the GRC) and one or more pod cells. For example, when there is no network connectivity between the GRC and its pod cells (e.g., the GRC and the pod cells are part of different enterprises or otherwise not under a common enterprise or organization), the cloud-based storage may act as an intermediate storage device or system between the GRC and its associated pod cells.

Abstract: An exemplary system preserves the autonomy of two or more distinct storage management systems all the while enabling backed up data to be restored from a first storage management system (the “local system”) to a specially-configured client in a second storage management system (the “remote system”). For example, backed up data in the local system (e.g., a secondary copy of production data) may be transferred, in a restore operation, from secondary storage in the local storage management system, which originated the data, to a client of the remote storage management system (the “remote client”). As a specially-configured “restore-only client,” the remote client is limited to receiving backed up data from the local storage management system, via restore operation(s) managed by the local storage manager. The remote client remains a full-fledged client in its home system, the remote storage management system.