Abstract: Data storage services are provided for clients for backup of data objects from the clients. A data object is sent to a first location in a first storage device. A determination is made if the data object was successfully stored at the first location, and if so, meta data corresponding with the data object is stored, wherein the meta data includes first path information on a first data path of the data object to the first location. The data object is migrated from the first location to a second location in a second storage device. A determination is made if the data object was successfully stored at the second location, and if so, second path information on a second data path of the data object is added to the second location to the meta data corresponding with the data object, to update the meta data.

Abstract: Methods, computer systems, and computer program products for replicating data are provided. Meta-data and data associated with the meta-data are received at a first data server. A new portion of the data that is not already stored on the first data server is identified. The new portion of the data is stored on a second data server before the meta-data is stored on the second data server.

Abstract: Data objects are replicated from a source storage managed by a source server to a target storage managed by a target server. A source list is built of objects at the source server to replicate to the target server. The target server is queried to obtain a target list of objects at the target server. A replication list is built indicating objects on the source list not included on the target list to transfer to the target server. For each object in the replication list, data for the object not already at the target storage is sent to the target server and metadata on the object is sent to the target server to cause the target server to include the metadata in an entry for the object in a target server replication database. An entry for the object is added to a source server replication database.

Abstract: Data objects are replicated from a source storage managed by a source server to a target storage managed by a target server. A source list is built of objects at the source server to replicate to the target server. The target server is queried to obtain a target list of objects at the target server. A replication list is built indicating objects on the source list not included on the target list to transfer to the target server. For each object in the replication list, data for the object not already at the target storage is sent to the target server and metadata on the object is sent to the target server to cause the target server to include the metadata in an entry for the object in a target server replication database. An entry for the object is added to a source server replication database.

Abstract: A source server maintains a replication rule specifying a condition for a replication attribute and a replication action to take if the condition with respect to the replication attribute is satisfied, wherein the replication action indicates to include or exclude the object having an attribute value for the replication attribute that satisfies the condition. For each of the objects, the replication rule is applied by determining an attribute value of the object corresponding to the replication attribute in the replication rule and determining whether the determined attribute value satisfies the condition for the replication attribute defined in the determined replication rule. The replication action on the object in response to determining that the determined attribute value satisfies the condition for the replication attribute.

Abstract: In each of a number of passes to deduplicate a data object, a transaction is started. Where an offset into the object has previously been set, the offset is retrieved; otherwise, the offset is set to reference a beginning of the object. A portion of the object beginning at the offset is deduplicated until an end-of-transaction criterion has been satisfied. The transaction is ended to commit deduplication; where the object has not yet been completely deduplicated, the offset is moved just past where deduplication has already occurred. The object is locked during each pass; other processes cannot access the object during each pass, but can access the object between passes. Each pass is relatively short, so the length of time in which the object is inaccessible is relatively short. By comparison, deduplicating an object within a single pass prevents other processes from accessing the object for a longer time.

Abstract: Data storage services are provided for clients for backup of data objects from the clients. A data object is sent to a first location in a first storage device. A determination is made if the data object was successfully stored at the first location, and if so, meta data corresponding with the data object is stored, wherein the meta data includes first path information on a first data path of the data object to the first location. The data object is migrated from the first location to a second location in a second storage device. A determination is made if the data object was successfully stored at the second location, and if so, second path information on a second data path of the data object is added to the second location to the meta data corresponding with the data object, to update the meta data.

Abstract: Data storage services are provided for clients for backup of data objects from the clients. A data object is sent to a first location in a first storage device. A determination is made if the data object was successfully stored at the first location, and if so, meta data corresponding with the data object is stored, wherein the meta data includes first path information on a first data path of the data object to the first location. The data object is migrated from the first location to a second location in a second storage device. A determination is made if the data object was successfully stored at the second location, and if so, second path information on a second data path of the data object is added to the second location to the meta data corresponding with the data object, to update the meta data.

Abstract: Methods, computer systems, and computer program products for replicating data are provided. Meta-data and data associated with the meta-data are received at a first data server. A new portion of the data that is not already stored on the first data server is identified. The new portion of the data is stored on a second data server before the meta-data is stored on the second data server.

Abstract: Virtual tape libraries (VTLs) and methods for concurrently accessing a VTL are provided. One VTL includes memory partitioned into multiple volumes, multiple virtual drives, and a processor. The processor is configured to enable multiple applications to concurrently access a virtual storage volume in a first or second access mode. One method includes receiving a first request for a first application to access a virtual storage volume to write data to or read data from the virtual storage volume and granting the first request. The method further includes receiving a second request for a second application to concurrently access the virtual storage volume to write data to or read data from the virtual storage volume, determining if the first and second requests are compatible, and accepting or denying the second request based on the determination. Also provided are physical computer storage mediums including computer code for performing the above method.

Abstract: One aspect of the present invention includes an optimized simultaneous storage operation for data objects onto a combination of deduplicated and non-deduplicated storage pools. In one embodiment, a data object is provided for storage onto destination storage pools in a storage management system, and placed into a source buffer. The data object is first divided into data chunks if the data object has not previously been chunked within the storage management system. The data object is then simultaneously copied from the source buffer to each destination storage pool (deduplicating and non-deduplicating) with the following operation. If the destination pool utilizes deduplication, then the individual data chunks are only transferred if copies of the individual data chunks do not already exist on the destination storage pool. If the destination pool does not utilize deduplication, then all chunks of the data object are transferred to the destination storage pool.

Abstract: In each of a number of passes to deduplicate a data object, a transaction is started. Where an offset into the object has previously been set, the offset is retrieved; otherwise, the offset is set to reference a beginning of the object. A portion of the object beginning at the offset is deduplicated until an end-of-transaction criterion has been satisfied. The transaction is ended to commit deduplication; where the object has not yet been completely deduplicated, the offset is moved just past where deduplication has already occurred. The object is locked during each pass; other processes cannot access the object during each pass, but can access the object between passes. Each pass is relatively short, so the length of time in which the object is inaccessible is relatively short. By comparison, deduplicating an object within a single pass prevents other processes from accessing the object for a longer time.

Abstract: An agent installed on a server reclaims one or more reclaimable off-site copy storage volumes and one or more reclaimable on-site copy storage volumes. To this end, the agent identifies each reclaimable off-site copy storage volume, runs a plurality of threads to collectively copy each data object of the identified reclaimable off-site copy storage volume(s) that is stored within one or more primary storage volumes to one or more one on-site target copy storage volumes, identifies each reclaimable on-site copy storage volume, and runs the plurality of threads to collectively transfer each data object of the identified reclaimable on-site copy storage volume(s) to the on-site copy target copy storage volume(s).

Abstract: Data storage services are provided for clients for backup of data objects from the clients. A data object is sent to a first location in a first storage device. A determination is made if the data object was successfully stored at the first location, and if so, meta data corresponding with the data object is stored, wherein the meta data includes first path information on a first data path of the data object to the first location. The data object is migrated from the first location to a second location in a second storage device. A determination is made if the data object was successfully stored at the second location, and if so, second path information on a second data path of the data object is added to the second location to the meta data corresponding with the data object, to update the meta data.

Abstract: An example of a method for error tracking includes sending a data object to a first location. This example also includes determining if the data object was successfully stored at the first location, and if so, storing meta data corresponding with the data object, wherein the meta data includes first path information. This example of the method also includes sending the data object to a second location. This example further includes determining if the data object was successfully stored at the second location, and if so, adding second path information to the meta data corresponding with the data object, to update the meta data. Some examples of the invention may be called a data centric error tracking and problem analysis method (and system), because the error tracking is generally based on the path traveled by the data.

Abstract: One aspect of the present invention includes an optimized simultaneous storage operation for data objects onto a combination of deduplicated and non-deduplicated storage pools. In one embodiment, a data object is provided for storage onto destination storage pools in a storage management system, and placed into a source buffer. The data object is first divided into data chunks if the data object has not previously been chunked within the storage management system. The data object is then simultaneously copied from the source buffer to each destination storage pool (deduplicating and non-deduplicating) with the following operation. If the destination pool utilizes deduplication, then the individual data chunks are only transferred if copies of the individual data chunks do not already exist on the destination storage pool. If the destination pool does not utilize deduplication, then all chunks of the data object are transferred to the destination storage pool.

Abstract: One aspect of the present invention includes enabling the efficient transfer of deduplicated data between storage pools in a storage management system without unnecessary reassembly and deduplication of data objects. In one embodiment, the storage management system tracks deduplication information for the data chunks of data objects within an index at the storage management system level, in addition to tracking storage information for each data object within another index at the storage management system level. The data chunk deduplication information is then accessible by any storage pool. Accordingly, transfers of the data objects and data chunks of the data object are easily facilitated, even between non-deduplicating and deduplicating storage pools.

Abstract: The present invention provides for a method, system, and computer program for the application of data deduplication according to a policy-based strategy of tiered data. The method operates by defining a plurality of data storage policies for data in a deduplication system, policies which may be arranged in tiers. Data objects are classified according to a selected data storage policy and are split into data chunks. If the selected data storage policy for the data object does not allow deduplication, the data chunks are stored in a deduplication pool. If the selected data storage policy for the data object allows deduplication, deduplication is performed. The data storage policy may specify a maximum number of references to data chunks, facilitating storage of new copies of the data chunks when the maximum number of references is met.

Abstract: The present invention provides for a method and a computer system for managing the retention of data on WORM disk media employing an event-based scheme of retaining data. The protection of the files is accomplished by establishing a retention period for the WORM disk media file volume containing the data files, followed by a reclamation period. The retention and reclamation periods are managed by comparing the amount of reclaimable space on the file volume to a threshold value, and if the threshold is not exceeded, the retention period of the file volume is extended by a default retention extension value. If the threshold value is exceeded, the files are moved to another file volume, and the retention period of this target file volume is extended based on the longer of the default retention extension value and the latest expiration date of the file contained within the file volume.

Abstract: Systems and methods for retrieving data from a storage system having a plurality of storage pools are provided. The method comprises processing configurable data retrieval instructions to determine a first storage pool from which target backup data is to be retrieved, in response to a data restore request; and retrieving the target backup data from the first storage pool to satisfy the restore request. The configurable data retrieval instructions are managed by a source external to the storage system with administrative authority to change the configurable data retrieval instructions to optimize data restoration from the storage system.