TRANSFORMATION OF LOGICAL DATA OBJECTS FOR STORAGE

• US 20110208789A1
• Filed: 01/13/2011
• Published: 08/25/2011
• Est. Priority Date: 01/13/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Koifman, Chaim, Raikhman, Rostislav, Amit, Jonathan
• Granted Patent: US 8,484,256 B2
• Time in Patent Office: Days
• US Class Current: 707/810
• CPC Class Codes: G06F 3/0611 in relation to response time
• CPC Class Codes: G06F 3/0667 at data level, e.g. file, record or object virtualisation
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

Various embodiments for operating a transformation system, capable of transforming a logical data object (LO) to a transformed logical data object (TLO), are provided. In one such embodiment, an open LO request to a certain LO and addressed by the at least one client to the at least one storage device, is intercepted. An identifier (ID) in a header of a TLO corresponding to the requested LO and stored in the at least one storage device, is obtained. The obtained ID is used to characterize the TLO and the LO. A determination is made whether the transformation system handles at least one open LO characterized by an ID with a same value as the obtained ID. The requested LO is opened if at least one open LO is not found. An instance corresponding to the intercepted open LO request is generated. The instance is associated to the obtained ID.

Claims

1. A method of operating a transformation system operatively coupled to at least one client and at least one storage device and capable of transforming a logical data object (LO) to a transformed logical data object (TLO) for storage in the at least one storage device operable with at least one storage protocol, comprising:

intercepting, by the transformation system, an open LO request to a certain LO and addressed by the at least one client to the at least one storage device;

responsive to the intercepted open LO request, obtaining an identifier (ID) in a header of a TLO corresponding to the requested LO and stored in the at least one storage device, thereby using the obtained ID to characterize the TLO and the LO;

determining if the transformation system handles at least one open LO characterized by an ID with a same value as the obtained ID;

opening the requested LO if the at least one open LO is not found;

generating an instance corresponding to the intercepted open LO request; and

associating the instance to the obtained ID.

2. The method of claim 1, further including:

determining if the requested LO is substantially identical to the at least one open LO, and

opening the requested LO if the at least one open LO is not substantially identical to the requested LO.

3. The method of claim 1, further including performing at least one of:

determining if the requested LO is substantially identical to the at least one open LO,

performing the generating the instance if the at least one open LO is substantially identical to the requested LO, and

performing the associating the instance to the ID of the at least one open LO.

4. The method of claim 1, further including implementing an ID map, operational in the transformation system, the ID map configured to:

retain information of at least one of the at least one open LO, and an open instance, and map the open instance to the ID characterizing the at least one open LO.

5. The method of claim 1, further including:

intercepting a first write request address to the obtained ID, and if the first write request meets an ID update criterion, performing at least one of;

suspending processing of the first write request,

generating a new ID, and updating the header of the TLO corresponding to the requested LO with the new ID,

upon successfully updating the header, re-associating the generated instance to the new ID, and

processing the suspended first write request.

6. The method of claim 1, further including:

intercepting a first write request addressed to the obtained ID, and if the first write request meets an ID update criterion, performing at least one of;

pending processing relating to all input/output (I/O) requests corresponding to each instance associated with the obtained ID,

generating a new ID, and updating the header of the TLO corresponding to the requested LO with the new ID,

upon successfully updating the header, re-associating the generated instance to the new ID and disconnecting a remainder of instances associated with the ID previously found in the header,

initiating read header requests for each of the disconnected instances, and

processing the I/O requests.

7. A transformation system, operatively coupled to at least one client and at least one storage device, and capable of transforming a logical data object (LO) to a transformed logical data object (TLO) for storage in the at least one storage device operable with at least one storage protocol, comprising:

a transformation unit, operable in the transformation system by at least one processor device, wherein the transformation unit is adapted for;

intercepting, by the transformation system, an open LO request to a certain LO and addressed by the at least one client to the at least one storage device,

responsive to the intercepted open LO request, obtaining an identifier (ID) in a header of a TLO corresponding to the requested LO and stored in the at least one storage device, thereby using the obtained ID to characterize the TLO and the LO,

determining if the transformation system handles at least one open LO characterized by an ID with a same value as the obtained ID,

opening the requested LO if the at least one open LO is not found,

generating an instance corresponding to the intercepted open LO request, and

associating the instance to the obtained ID.

8. The system of claim 7, wherein the transformation unit is further adapted for:

determining if the requested LO is substantially identical to the at least one open LO, and

opening the requested LO if the at least one open LO is not substantially identical to the requested LO.

9. The system of claim 7, wherein the transformation unit is further adapted for performing at least one of:

determining if the requested LO is substantially identical to the at least one open LO,

performing the generating the instance if the at least one open LO is substantially identical to the requested LO, and

performing the associating the instance to the ID of the at least one open LO.

10. The system of claim 7, further including an ID map, operatively coupled to the transformation unit, the ID map configured to:

retain information of at least one of the at least one open LO, and an open instance, and map the open instance to the ID characterizing the at least one open LO.

11. The system of claim 7, wherein the instance is a single open instance associated with the obtained ID.

12. The system of claim 11, wherein the transformation unit is further adapted for:

intercepting a first write request address to the obtained ID, and if the first write request meets an ID update criterion, performing at least one of;

suspending processing of the first write request,

generating a new ID, and updating the header of the TLO corresponding to the requested LO with the new ID,

upon successfully updating the header, re-associating the generated instance to the new ID, and

processing the suspended first write request.

13. The system of claim 7, wherein the instance is not a single open instance associated with the obtained ID.

14. The system of claim 13, wherein the transformation unit is further adapted for:

intercepting a first write request addressed to the obtained ID, and if the first write request meets an ID update criterion, performing at least one of;

pending processing relating to all input/output (I/O) requests corresponding to each instance associated with the obtained ID,

generating a new ID, and updating the header of the TLO corresponding to the requested LO with the new ID,

upon successfully updating the header, re-associating the generated instance to the new ID and disconnecting a remainder of instances associated with the ID previously found in the header,

initiating read header requests for each of the disconnected instances, and

processing the I/O requests.

15. A computer program product for operating a transformation system operatively coupled to at least one client and at least one storage device and capable of transforming a logical data object (LO) to a transformed logical data object (TLO) for storage in the at least one storage device operable with at least one storage protocol, the computer program product comprising a computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion for intercepting, by the transformation system, an open LO request to a certain LO and addressed by the at least one client to the at least one storage device;

a second executable portion for, responsive to the intercepted open LO request, obtaining an identifier (ID) in a header of a TLO corresponding to the requested LO and stored in the at least one storage device, thereby using the obtained ID to characterize the TLO and the LO;

a third executable portion for determining if the transformation system handles at least one open LO characterized by an ID with a same value as the obtained ID;

a fourth executable portion for opening the requested LO if the at least one open LO is not found;

a fifth executable portion for generating an instance corresponding to the intercepted open LO request; and

a sixth executable portion for associating the instance to the obtained ID.

16. The computer program product of claim 15, further including a seventh executable portion for:

determining if the requested LO is substantially identical to the at least one open LO, and

opening the requested LO if the at least one open LO is not substantially identical to the requested LO.

17. The computer program product of claim 15, further including a seventh executable portion for performing at least one of:

determining if the requested LO is substantially identical to the at least one open LO,

performing the generating the instance if the at least one open LO is substantially identical to the requested LO, and

performing the associating the instance to the ID of the at least one open LO.

18. The computer program product of claim 15, further including a seventh executable portion for implementing an ID map, operational in the transformation system, the ID map configured to:

retain information of at least one of the at least one open LO, and an open instance, and map the open instance to the ID characterizing the at least one open LO.

19. The computer program product of claim 15, further including a seventh executable portion for:

intercepting a first write request address to the obtained ID, and if the first write request meets an ID update criterion, performing at least one of;

suspending processing of the first write request,

generating a new ID, and updating the header of the TLO corresponding to the requested LO with the new ID,

upon successfully updating the header, re-associating the generated instance to the new ID, and

processing the suspended first write request.

20. The computer program product of claim 15, further including a seventh executable portion for:

intercepting a first write request addressed to the obtained ID, and if the first write request meets an ID update criterion, performing at least one of;

pending processing relating to all input/output (I/O) requests corresponding to each instance associated with the obtained ID,

generating a new ID, and updating the header of the TLO corresponding to the requested LO with the new ID,

upon successfully updating the header, re-associating the generated instance to the new ID and disconnecting a remainder of instances associated with the ID previously found in the header,

initiating read header requests for each of the disconnected instances, and

processing the I/O requests.