Legal claims defining the scope of protection, as filed with the USPTO.
1. A method, comprising: generating, by a computational device, metadata that stores a correspondence between a source logical block of a thinly provisioned source logical unit and a target logical block of a thinly provisioned target logical unit, without physically moving data from the thinly provisioned source logical unit to the thinly provisioned target logical unit, wherein an application programming interface is used to remap physical storage, and wherein the application programming interface is comprised of parameters including a source logical unit number, a source logical block address, a target logical unit number, a target logical block address, and a size; and in response to a reconfiguration of the thinly provisioned source logical unit and the thinly provisioned target logical unit as fully provisioned, physically copying data stored in the source logical block of the thinly provisioned source logical unit that is now a fully provisioned source storage unit to the target logical block of the thinly provisioned target logical unit that is now a fully provisioned target storage unit.
2. The method of claim 1 , the method further comprising: providing, by a storage management application executing in the computational device, the application programming interface to swap physical storage that is currently assigned to the source logical block of the thinly provisioned source logical unit to be swapped with physical storage assigned to the target logical block of the thinly provisioned target logical unit, wherein execution of the application programming interface executes the swap atomically.
3. The method of claim 1 , wherein the application programming interface allows virtual data movement from the thinly provisioned source logical unit to the thinly provisioned target logical unit, without actually performing any physical movement of data from the thinly provisioned source logical unit to the thinly provisioned target logical unit, wherein the application programming interface is provided to exploit characteristics of thin provisioning systems to provide mappings between virtual and physical blocks.
4. The method of claim 1 , wherein: the thinly provisioned source logical unit and the thinly provision target logical unit are logical representations of storage maintained in one or more physical storage devices coupled to the computational device; and the source logical block is a logical subdivision of the thinly provisioned source logical unit; and the target logical block is a logical subdivision of the thinly provisioned target logical unit.
5. The method of claim 1 , the method further comprising: performing a read operation of the target logical block of the thinly provisioned target logical unit by accessing the source logical block of the thinly provisioned source logical unit from the correspondence maintained in the metadata.
6. The method of claim 1 , wherein the application programming interface allows physical storage currently mapped to the source logical unit's source logical block address to be mapped to a specified target logical unit's target logical block address without involving any data read or write operation by an application, and wherein the size parameter in the application programming interface corresponds to a size of a block that is mapped.
7. A system, comprising: a memory; and a processor coupled to the memory, wherein the processor performs operations, the operations comprising: generating metadata that stores a correspondence between a source logical block of a thinly provisioned source logical unit and a target logical block of a thinly provisioned target logical unit, without physically moving data from the thinly provisioned source logical unit to the thinly provisioned target logical unit, wherein an application programming interface is used to remap physical storage, and wherein the application programming interface is comprised of parameters including a source logical unit number, a source logical block address, a target logical unit number, a target logical block address, and a size; and in response to a reconfiguration of the thinly provisioned source logical unit and the thinly provisioned target logical unit as fully provisioned, physically copying data stored in the source logical block of the thinly provisioned source logical unit that is now a fully provisioned source storage unit to the target logical block of the thinly provisioned target logical unit that is now a fully provisioned target storage unit.
8. The system of claim 7 , wherein the system is a computational device, the operations further comprising: providing, by a storage management application executing in the computational device, the application programming interface to swap physical storage that is currently assigned to the source logical block of the thinly provisioned source logical unit to be swapped with physical storage assigned to the target logical block of the thinly provisioned target logical unit, wherein execution of the application programming interface executes the swap atomically.
9. The system of claim 7 , wherein the application programming interface allows virtual data movement from the thinly provisioned source logical unit to the thinly provisioned target logical unit, without actually performing any physical movement of data from the thinly provisioned source logical unit to the thinly provisioned target logical unit, wherein the application programming interface is provided to exploit characteristics of thin provisioning systems to provide mappings between virtual and physical blocks.
10. The system of claim 7 , wherein the system is a computational device, and wherein: the thinly provisioned source logical unit and the thinly provision target logical unit are logical representations of storage maintained in one or more physical storage devices coupled to the computational device; and the source logical block is a logical subdivision of the thinly provisioned source logical unit; and the target logical block is a logical subdivision of the thinly provisioned target logical unit.
11. The system of claim 7 , the operations further comprising: performing a read operation of the target logical block of the thinly provisioned target logical unit by accessing the source logical block of the thinly provisioned source logical unit from the correspondence maintained in the metadata.
12. The system of claim 7 , wherein the application programming interface allows physical storage currently mapped to the source logical unit's source logical block address to be mapped to a specified target logical unit's target logical block address without involving any data read or write operation by an application, and wherein the size parameter in the application programming interface corresponds to a size of a block that is mapped.
13. A computer program product, the computer program product comprising a non-transitory computer readable storage medium having computer readable program code embodied therewith, the computer readable program code configured to perform operations in a computational device, the operations comprising: generating metadata that stores a correspondence between a source logical block of a thinly provisioned source logical unit and a target logical block of a thinly provisioned target logical unit, without physically moving data from the thinly provisioned source logical unit to the thinly provisioned target logical unit, wherein an application programming interface is used to remap physical storage, and wherein the application programming interface is comprised of parameters including a source logical unit number, a source logical block address, a target logical unit number, a target logical block address, and a size; and in response to a reconfiguration of the thinly provisioned source logical unit and the thinly provisioned target logical unit as fully provisioned, physically copying data stored in the source logical block of the thinly provisioned source logical unit that is now a fully provisioned source storage unit to the target logical block of the thinly provisioned target logical unit that is now a fully provisioned target storage unit.
14. The computer program product of claim 13 , the operations further comprising: providing, by a storage management application executing in the computational device, the application programming interface to swap physical storage that is currently assigned to the source logical block of the thinly provisioned source logical unit to be swapped with physical storage assigned to the target logical block of the thinly provisioned target logical unit, wherein execution of the application programming interface executes the swap atomically.
15. The computer program product of claim 13 , wherein the application programming interface allows virtual data movement from the thinly provisioned source logical unit to the thinly provisioned target logical unit, without actually performing any physical movement of data from the thinly provisioned source logical unit to the thinly provisioned target logical unit, wherein the application programming interface is provided to exploit characteristics of thin provisioning systems to provide mappings between virtual and physical blocks.
16. The computer program product of claim 13 , wherein: the thinly provisioned source logical unit and the thinly provision target logical unit are logical representations of storage maintained in one or more physical storage devices coupled to the computational device; and the source logical block is a logical subdivision of the thinly provisioned source logical unit; and the target logical block is a logical subdivision of the thinly provisioned target logical unit.
17. The computer program product of claim 13 , the operations further comprising: performing a read operation of the target logical block of the thinly provisioned target logical unit by accessing the source logical block of the thinly provisioned source logical unit from the correspondence maintained in the metadata.
18. The computer program product of claim 13 , wherein the application programming interface allows physical storage currently mapped to the source logical unit's source logical block address to be mapped to a specified target logical unit's target logical block address without involving any data read or write operation by an application, and wherein the size parameter in the application programming interface corresponds to a size of a block that is mapped.
Unknown
February 9, 2016
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.