Abstract: An application programming interface (API), functioning as an interface between a storage controller and an owning application, is used to migrate, from a specified source LUN to a specified target LUN, at least one specified sub-LUN data chunk, the at least one specified sub-LUN data chunk having a predefined chunk size fixed by the storage controller. A specified total migration size is incrementally reduced by each completed migration of the at least one specified sub-LUN data chunk until the total migration size is zero and the migration is completed.

Abstract: An application programming interface (API) is used to migrate, from a specified source LUN to a specified target LUN, at least one specified sub-LUN data chunk, the API functioning as an interface between a storage controller and an owning application.

Abstract: A source code-based specification is implemented for use as an interface between a storage controller and an owning application to migrate a specified size of data from physical storage behind the LUN to a new physical location.

Abstract: Various embodiments for preserving data redundancy in a data deduplication system in a computing environment are provided. A write command is received for writing a selected data segment to a physical storage location. A determination is made as to whether the write command includes an indicator including at least one of a bit and a flag, the indicator designating that the selected data segment must not be subject to a deduplication operation. An indicator is configured by providing a system call with an extended attribute indicating that the selected data segment must be written to physical memory notwithstanding the selected data segment matching data written to the physical memory earlier in time.

Abstract: Various embodiments for preserving data redundancy in a data deduplication system in a computing environment are provided. In one embodiment, a method for such preservation is disclosed in a multi-device file system. At least one virtual device out of a volume set is designated as not subject to a deduplication operation.

Abstract: A system and non-transitory computer program product for preserving data redundancy in a data deduplication system in a computing environment is provided. A selected data segment, to be written through the data deduplication system, is encrypted such that the selected data segment is not subject to a deduplication operation. Copies of the data segment that are to be precluded from data deduplication are determined and identified. A unique encryption key is used to encrypt the selected data segment to be written through the data deduplication system such that the selected data segment is not subject to a deduplication operation. The data deduplication system is tricked to recognize the encrypted, selected data segment as new, undeduplicated data by the encrypting thereby skipping steps of the deduplication operation that includes fingerprint generation and matching. The encrypted, selected data segment is directly written to a new physical storage location.

Abstract: Various embodiments for preserving data redundancy in a data deduplication system in a computing environment are provided. A write command is received for writing a selected data segment to a physical storage location. A determination is made as to whether the write command includes an indicator including at least one of a bit and a flag, the indicator designating that the selected data segment must not be subject to a deduplication operation. An indicator is configured by providing a system call with an extended attribute indicating that the selected data segment must be written to physical memory notwithstanding the selected data segment matching data written to the physical memory earlier in time.

Abstract: Various embodiments for preserving data redundancy in a data deduplication system in a computing environment are provided. In one embodiment, a method for such preservation is disclosed. An indicator is configured. The indicator is provided with a selected data segment to be written through the data deduplication system to designate that the selected data segment must not be subject to a deduplication operation, such that repetitive data can be written and stored on physical locations despite being identical.

Abstract: A method for preserving data redundancy in a data deduplication system in a computing environment is provided. A selected data segment, to be written through the data deduplication system, is encrypted such that the selected data segment is not subject to a deduplication operation. The method determines and identifies copies of the data segment that are to be precluded from data deduplication. A unique encryption key is used to encrypt the selected data segment to be written through the data deduplication system such that the selected data segment is not subject to a deduplication operation. The data deduplication system is tricked to recognize the encrypted, selected data segment as new, undeduplicated data by the encrypting thereby skipping steps of the deduplication operation that includes fingerprint generation and matching. The encrypted, selected data segment is directly written to a new physical storage location.

Abstract: Various embodiments for preserving data redundancy of identical data in a data deduplication system in a computing environment are provided. In one embodiment, a method for such preservation is disclosed. A selected range of virtual addresses of a virtual storage device in the computing environment is designated as not subject to a deduplication operation. Other system and computer program product embodiments are disclosed and provide related advantages.

Abstract: Mechanisms identify one or more first storage devices in a first tier of the tiered storage system that may be placed in a minimal power consumption state and identify one or more data segments stored on the one or more first storage devices that are most likely to be accessed during a period of time in which the one or more first storage devices are in the minimal power consumption state. The mechanisms migrate the one or more data segments to one or more second storage devices in one of the first tier or a second tier of the storage system and place the one or more first storage devices in the minimal power consumption state. Access requests to the one or more data segments are serviced by the one or more second storage devices while the one or more first storage devices are in the minimal power consumption state.

Abstract: A method for preserving data availability and I/O performance when creating a virtual RAID volume includes exposing a set of backend virtual volumes. The backend virtual volumes are implemented on a set of physical storage devices (e.g., physical disks or solid state drives) residing on a storage system. The method further enables selection of the set of backend virtual volumes to create a virtual RAID volume having a selected RAID level. The method further provides verification that the backend virtual volumes will be implemented on the physical storage devices in a way that preserves the data availability and I/O performance associated with the selected RAID level.

Abstract: A storage system receives an anticipatory write command corresponding to a potential subsequent write command to be received by the storage system, wherein the anticipatory write command indicates an anticipated region of logical address space that may be written to by the potential subsequent write command. The storage system determines that physical storage is not allocated to the anticipated region of logical address space. The storage system allocates physical storage to the anticipated region of logical address space from a pool of available storage managed by the storage system. The storage system creates an association between the anticipated region of logical address space and the allocated physical storage in a virtual-to-physical mapping.

Abstract: For efficient handing of semi-asynchronous RAID write failures using a processor device in a computing environment, a write operation is committed on a primary copy of data on a primary entity while sending the data to a secondary entity while awaiting an acknowledgment by the secondary entity. The acknowledgment indicates to the primary entity that metadata for the write operation has arrived at the secondary entity without necessarily indicating the data has arrived at the secondary entity.

Abstract: A mechanism is provided for optimizing and enhancing performance for parity based storage, particularly redundant array of independent disk (RAID) storage. The mechanism optimizes a repetitive pattern write command for performance for storage configurations that require parity calculations. The mechanism eliminates the need for laborious parity calculations that are resource intensive and add to IO latency. For repetitive write commands that span across the full stripe of a RAID5 or similar volume, the mechanism calculates parity by looking at the pattern and the number of columns in the volume. The mechanism may avoid the XOR operation altogether for repetitive pattern write commands. The mechanism may enhance secure delete operations that use repetitive pattern write commands by eliminating data reliability operations like parity generation and writing altogether.

Abstract: A first server system identifies a first storage area of the first server system, the first storage area being associated with a first heat value and storing at least a portion of a file. The first server system determines an identifier corresponding to the portion of the file. The first server system associates the portion of the file with the first heat value. The first server system sends the identifier corresponding to the portion of the file and the associated heat value to a second server system, wherein the second server system includes a duplicate copy of the portion of the file.

Abstract: For efficient handing of semi-asynchronous RAID write failures using a processor device in a computing environment, a write operation is committed on a primary copy of data on a primary entity while sending the data to a secondary entity while awaiting an acknowledgment by the secondary entity. The acknowledgment indicates to the primary entity that metadata for the write operation has arrived at the secondary entity without necessarily indicating the data has arrived at the secondary entity.

Abstract: Various embodiments for preserving data redundancy of identical data in a data deduplication system in a computing environment are provided. In one embodiment, a method for such preservation is disclosed. A selected range of virtual addresses of a virtual storage device in the computing environment is designated as not subject to a deduplication operation. Other system and computer program product embodiments are disclosed and provide related advantages.

Abstract: A first server system identifies a first storage area of the first server system, the first storage area being associated with a first heat value and storing at least a portion of a file. The first server system determines an identifier corresponding to the portion of the file. The first server system associates the portion of the file with the first heat value. The first server system sends the identifier corresponding to the portion of the file and the associated heat value to a second server system, wherein the second server system includes a duplicate copy of the portion of the file.

Abstract: For efficient handing of semi-asynchronous RAID write failures using a processor device in a computing environment, a write operation is committed on a primary copy of data on a primary entity while sending the data to a secondary entity while awaiting an acknowledgment by the secondary entity. The acknowledgment indicates to the primary entity that metadata for the write operation has arrived at the secondary entity without necessarily indicating the data has arrived at the secondary entity. The acknowledgment is sent from the secondary entity regardless of a write failure and allowing the secondary entity to perform a recovery operation if a write failure occurs.