Abstract: A system and method for data storage management is disclosed. The method includes determining, by an access tracking component, a quantity of access requests for at least one data block, and determining a quantity of current copies of the data block. The method also includes creating, by a duplication component, at least one additional copy of the data block when the quantity of the access requests exceeds an access request threshold. Additionally, a deduplication component removes at least one current copy of the data block when the quantity of the access requests falls below the access request threshold. The access request threshold can be a threshold number of access requests for the data block, the presence of an input/output bottleneck, or a given length of a read latency when accessing the data block. Further, data coloring techniques can be used to distribute current copies of the data block.

Abstract: Various embodiments are provided for identifying matching tape volumes for data deduplication in an automated data storage library by a processor. A weak hash function on a selected block of streamed data from a host such that the selected block of streamed data with the weak hash function is further compressed to a reduced block of compressed data. N most similar tape volumes in a tape library may be matched according to the weak hash function for performing a data deduplication operation on the reduced block of compressed data between the N most similar tape volumes, wherein N is a positive integer.

Abstract: Various embodiments are provided for identifying matching tape volumes for data deduplication in an automated data storage library by a processor. N most similar tape volumes in a tape library may be matched according to a data indication provided in each volume header of the N most similar tape volumes for performing a data deduplication operation on a reduced block of compressed data between the N most similar tape volumes, wherein N is a positive integer.

Abstract: Various embodiments for scrubbing data within a data storage subsystem are disclosed. An event is detected in which utilization of the data storage subsystem has fallen below a dynamically adjusted threshold value. A storage element is selected from a plurality of storage elements within the data storage subsystem. Data modifications are temporarily suspended on the selected storage element while simultaneously maintaining read access to the selected storage element. A scrubbing operation is performed on the selected storage element after the temporary designation, wherein the scrubbing operation automatically initiates when a quantity of active data to be scrubbed reaches a predetermined quantity threshold, the predetermined quantity threshold of active data comprising a total threshold number of bytes or blocks corresponding to a greatest frequency of access thereof.

Abstract: For maintaining a context stack, a processor monitors a stack size for a stack of a plurality of existing contexts that are not associated to a process of a plurality of processes. Each context is associable and reusable with a plurality of processes and includes a pathway to a data set when not associated to any process of the plurality of processes. The pathway includes a logical volume identifier for the data set, a logical address of the data set within the logical volume, and a logical address of an intervening device. The context defines communications between the process and the data set through the pathway when associated to the process, and each context is returned to the stack when not associated to the process.

Abstract: Various embodiments for scrubbing data within a data storage subsystem are disclosed. According to one embodiment, a method is provided for scrubbing data of a storage element within a data storage subsystem, the method comprising: selecting a storage element from the plurality of storage events; determining that a quantity of active data has reached a predetermined quantity threshold; and temporarily suspending data modifications on a portion of the selected storage element while maintaining read access to the selected storage element in response to the determination.

Abstract: An apparatus, system, and method are disclosed for maintaining a context stack. A monitor module monitors a stack size after each monitor interval for a stack of a plurality of contexts. Each context defines communications between a process and a data set and comprises a pathway for communicating with the data set and a process identifier. A stack module deallocates a context that satisfies a stack policy from the stack if the stack size is within a buffer threshold of a maximum threshold.

Abstract: For efficient Flashcopy backup and mount, clone, or restore collision avoidance with reuse using dynamic volume allocation, performing at least one attempt to reuse an existing FlashCopy target volume that is not currently being used for at least one of a mount task, a clone task, and a restore task at the same time for a FlashCopy backup. If the at least one attempt to reuse the existing FlashCopy target volume fails, dynamically allocate a new Flashcopy target volume for the Flashcopy backup.

Abstract: For efficient Flashcopy backup and a mount, clone, instant restore, and/or file level restore task collision avoidance using dynamic volume allocation with reuse and from a shared resource pool, performing at least one attempt to reuse an existing FlashCopy target volume in a Flashcopy chain of target volumes that is not currently being used for at least one of the mount task, the clone task, instant restore task, and/or file level restore task at the same time for a FlashCopy backup. If the at least one attempt to reuse the existing FlashCopy target volume fails, dynamically allocate a new Flashcopy target volume for the Flashcopy backup from a global pool of Flashcopy backup target volumes shared by a plurality of device classes.

Abstract: For efficient Flashcopy backup and a mount, clone, or restore task collision avoidance using dynamic volume allocation with reuse and from a shared resource pool, dynamically using a Flashcopy target volume for the Flashcopy backup from a global pool of Flashcopy backup target volumes shared by a plurality of device classes for avoiding a collision between the Flashcopy backup and the mount, the clone, or the restore task.

Abstract: A new target volume for a new FlashCopy backup is dynamically allocated by performing at least one attempt to reuse an existing FlashCopy target volume containing older FlashCopy backups that have been previously ingested into a repository and are not currently being used as a source for at least one of a mount task, a clone task, and a restore task. If the at least one attempt to reuse the existing FlashCopy target volume fails, the new target volume is dynamically allocated from a global pool of FlashCopy backup target volumes.

Abstract: A mechanism is provided for reducing the backup time of data files from a memory. Data files are pre-staged by identifying the data files in the memory to be backed up to a backup storage system, sorting the data files by size thereby forming a set of small data files and a set of large data files, and copying the set of small data files to a cache while leaving the set of large data files in a disk subsystem. The set of small data files are then backed-up from the cache and the set of large data files are backed-up from the disk subsystem to a backup storage system. Thus, the time required to backup the set of small data files from the cache is performed at a faster rate as compared to backing up the set of large data files from the disk subsystem.

Abstract: A mechanism is provided for reducing the backup time of data files from a memory. Data files are pre-staged by identifying the data files in the memory to be backed up to a backup storage system, sorting the data files by size thereby forming a set of small data files and a set of large data files, and copying the set of small data files to a cache while leaving the set of large data files in a disk subsystem. The set of small data files are then backed-up from the cache and the set of large data files are backed-up from the disk subsystem to a backup storage system. Thus, the time required to backup the set of small data files from the cache is performed at a faster rate as compared to backing up the set of large data files from the disk subsystem.

Abstract: For similarity based deduplication of remote data repositories, a parse module generates a rolling hash value based on a portion of an incoming stream of backup data. A comparison module compares the rolling hash value with entries stored in a rolling hash index, and in response to matching the rolling hash value with an entry in the rolling hash index, generates a strong hash value and determines if a match of the strong hash value exists in a first strong hash index. The comparison module, in response to a determination that the match does not exist in the first strong hash index, compares the strong hash value with entries in a second strong hash index in the remote data repository. A migration module, in response to a determination that the strong hash value does not match any hash entries, stores the portion of backup data as new data.

Abstract: Various embodiments for managing data in a data deduplication repository in a computing storage environment, by a processor device, are provided. In one embodiment, a method comprises issuing an application programming interface (API) command to scan metadata of a subset of entities in a local deduplication repository for identifying candidate data to offload from the local deduplication repository to an object storage, offloading the candidate data to the object storage, and returning a status result using the API command.

Abstract: Various embodiments for managing data in a data deduplication repository in a computing storage environment, by a processor device, are provided. In one embodiment, a method comprises migrating certain deduplication repository data from a host to an object storage by integrating a data offload process with an existing backup management application, for reducing unnecessary deduplication repository data stored on the host.

Abstract: For offloading data to secondary storage, a criteria module checks a migration criteria of a data segment stored in a first data repository. The data segment may be associated with one or more entities. A threshold module determines whether the migration criteria of the data segment satisfies a migration threshold. A migration module migrates the data segment to a second data repository in response to the migration criteria of the data segment satisfying the migration threshold.

Abstract: For similarity based deduplication of remote data repositories, a parse module generates a rolling hash value based on a portion of an incoming stream of backup data. A comparison module compares the rolling hash value with entries stored in a rolling hash index, and in response to matching the rolling hash value with an entry in the rolling hash index, generates a strong hash value and determines if a match of the strong hash value exists in a first strong hash index. The comparison module, in response to a determination that the match does not exist in the first strong hash index, compares the strong hash value with entries in a second strong hash index in the remote data repository. A migration module, in response to a determination that the strong hash value does not match any hash entries, stores the portion of backup data as new data.

Abstract: An apparatus for data replication is disclosed. A method and computer program product also perform the functions of the apparatus. In one embodiment, an apparatus includes a replication module configured for replicating, in response to a determination that a received object corresponds to a storage policy, the received object to a data storage node. The apparatus also includes a tagging module configured for marking the received object with a file attribute indicative of the received object being excluded from migration to a cold storage device during the replicating, and removing the file attribute after the replicating. The apparatus may also include a migration module configured for migrating, in response to a determination that the file attribute has been removed, the received object to the cold storage device.

Abstract: Dynamically allocates a new Flashcopy backup target volume within the single repository for executing a new Flashcopy backup to avoid a collision with one of a mount operation, a restore operation, and a clone operation when dynamically allocating the new Flashcopy target volume for the new Flashcopy backup.