USING A MIGRATION CACHE TO CACHE TRACKS DURING MIGRATION

• US 20120059994A1
• Filed: 09/08/2010
• Published: 03/08/2012
• Est. Priority Date: 09/08/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Montgomery, David, Sorenson, Todd Charles
• Granted Patent: US 8,555,019 B2
• Time in Patent Office: Days
• US Class Current: 711/119
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 12/0888 using selective caching, e.g. bypass
• CPC Class Codes: G06F 3/0617 in relation to availability
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/0685 Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays

Abstract

Provided are a method, system, and computer program product for using a migration cache to cache tracks during migration. Indication is made in an extent list of tracks in an extent in a source storage subject to Input/Output (I/O) requests. A migration operation is initiated to migrate the extent from the source storage to a destination storage. In response to initiating the migration operation, a determination is made of a first set of tracks in the extent in the source storage indicated in the extent list. A determination is also made of a second set of tracks in the extent. The tracks in the source storage in the first set are copied to a migration cache, wherein updates to the tracks in the migration cache during the migration operation are applied to the migration cache. The tracks in the second set are copied directly from the source storage to the destination storage without buffering in the migration cache. The tracks in the first set are copied from the migration cache to the destination storage. The migration operation is completed in response to copying the first set of tracks from the migration cache to the destination storage and copying the second set of tracks from the source storage to the destination storage, wherein after the migration the tracks in the extent are located in the destination storage.

Claims

1. A computer program product for migrating data from a source storage to a destination storage, the computer program product comprising a computer readable storage medium having computer readable program code embodied therein that executes to perform operations, the operations comprising:

indicating in an extent list tracks in an extent in the source storage subject to Input/Output (I/O) requests;

initiating a migration operation to migrate the extent from the source storage to the destination storage;

in response to initiating the migration operation, performing;

determining a first set of tracks in the extent in the source storage indicated in the extent list;

determining a second set of tracks in the extent;

copying the tracks in the source storage in the first set to a migration cache, wherein updates to the tracks in the migration cache during the migration operation are applied to the migration cache; and

copying the tracks in the second set directly from the source storage to the destination storage without buffering in the migration cache;

copying the tracks in the first set from the migration cache to the destination storage; and

completing the migration operation in response to copying the first set of tracks from the migration cache to the destination storage and copying the second set of tracks from the source storage to the destination storage, wherein after the migration the tracks in the extent are located in the destination storage.

2. The computer program product of claim 1, wherein the second set of tracks includes tracks in the extent indicated in the extent list that are not in the first set of tracks and tracks in the extent not indicated in the extent list.

3. The computer program product of claim 1, wherein the extent list orders tracks according to last recently used, wherein the second set of tracks includes tracks in the extent indicated in the extent list that are not in the first set of tracks, and wherein the tracks in the first set have been more recently used according to the extent list ordering than the tracks in the second set.

4. The computer program product of claim 1, wherein the tracks in the migration cache are copied to the destination storage in response to copying all the tracks in the first set to the migration cache, and wherein the tracks in the migration cache and the source storage are copied in parallel to the destination storage.

5. The computer program product of claim 1, further performing during the migration operation:

receiving an update to one track in the extent during the migration operation;

determining whether the track is located in the migration cache;

writing the update to the migration cache in response to determining that the track is in the migration cache, wherein the updated track is copied from the migration cache to the destination storage;

writing the update to the source storage in response to determining that the track is not maintained in the migration cache.

6. The computer program product of claim 5, wherein the migration cache and a source cache are maintained in at least one memory device in a server in communication with the source storage and the destination storage, wherein writing the update to the source storage comprises writing the update to the source cache, wherein updated tracks in the source cache are destaged to the source storage and wherein updates to tracks in the migration cache are not destaged to the source storage.

7. The computer program product of claim 6, wherein the operations further comprise:

maintaining a destination cache in the server for tracks in the destination storage;

copying tracks in the migration cache for the extent to the destination cache in response to completing the migration of the extent to the destination storage.

8. The computer program product of claim 1, wherein the extent list indicates write requests to the source storage and not read requests, wherein the first set of tracks indicates only tracks in the source storage that have been updated prior to the migration operation.

9. The computer program product of claim 1, wherein the extent list comprises a write extent list indicating tracks in the extent subject to a write request and a read extent list indicating tracks in the extent subject to a read request, wherein the first set of tracks includes tracks indicated in the first and second extent lists, and wherein the second set of tracks includes tracks indicated in the first and second extent lists not included in the first set and tracks not indicated in the first and second extent lists.

10. The computer program product of claim 9, wherein the most recently accessed tracks indicated in the write and read extent lists are included in the first set according to a proportion of the tracks indicated in the write and read extent lists.

11. A method, comprising:

indicating in an extent list tracks in an extent in a source storage subject to Input/Output (I/O) requests;

initiating a migration operation to migrate the extent from the source storage to a destination storage;

in response to initiating the migration operation, performing;

determining a first set of tracks in the extent in the source storage indicated in the extent list;

determining a second set of tracks in the extent;

copying the tracks in the source storage in the first set to a migration cache, wherein updates to the tracks in the migration cache during the migration operation are applied to the migration cache; and

copying the tracks in the second set directly from the source storage to the destination storage without buffering in the migration cache;

copying the tracks in the first set from the migration cache to the destination storage; and

completing the migration operation in response to copying the first set of tracks from the migration cache to the destination storage and copying the second set of tracks from the source storage to the destination storage, wherein after the migration the tracks in the extent are located in the destination storage.

12. The method of claim 11, wherein the second set of tracks includes tracks in the extent indicated in the extent list that are not in the first set of tracks and tracks in the extent not indicated in the extent list.

13. The method of claim 11, further performing during the migration operation:

receiving an update to one track in the extent during the migration operation;

determining whether the track is located in the migration cache;

writing the update to the migration cache in response to determining that the track is in the migration cache, wherein the updated track is copied from the migration cache to the destination storage;

writing the update to the source storage in response to determining that the track is not maintained in the migration cache.

14. The method of claim 13, wherein the migration cache and a source cache are maintained in at least one memory device in a server in communication with the source storage and the destination storage, wherein writing the update to the source storage comprises writing the update to the source cache, wherein updated tracks in the source cache are destaged to the source storage and wherein updates to tracks in the migration cache are not destaged to the source storage.

15. The method of claim 14, further comprising:

maintaining a destination cache in the server for tracks in the destination storage;

copying tracks in the migration cache for the extent to the destination cache in response to completing the migration of the extent to the destination storage.

16. The method of claim 11, wherein the extent list comprises a write extent list indicating tracks in the extent subject to a write request and a read extent list indicating tracks in the extent subject to a read request, wherein the first set of tracks includes tracks indicated in the first and second extent lists, and wherein the second set of tracks includes tracks indicated in the first and second extent lists not included in the first set and tracks not indicated in the first and second extent lists.

17. A system for migrating data from a source storage to a destination storage, comprising:

a computer memory;

a migration manager executed to perform operations, the operations comprising;

indicating in an extent list in the computer memory tracks in an extent in the source storage subject to Input/Output (I/O) requests;

initiating a migration operation to migrate the extent from the source storage to the destination storage;

in response to initiating the migration operation, performing;

determining a first set of tracks in the extent in the source storage indicated in the extent list;

determining a second set of tracks in the extent;

copying the tracks in the source storage in the first set to a migration cache in the computer memory, wherein updates to the tracks in the migration cache during the migration operation are applied to the migration cache; and

copying the tracks in the second set directly from the source storage to the destination storage without buffering in the migration cache;

copying the tracks in the first set from the migration cache to the destination storage; and

completing the migration operation in response to copying the first set of tracks from the migration cache to the destination storage and copying the second set of tracks from the source storage to the destination storage, wherein after the migration the tracks in the extent are located in the destination storage.

18. The computer program product of claim 17, wherein the second set of tracks includes tracks in the extent indicated in the extent list that are not in the first set of tracks and tracks in the extent not indicated in the extent list.

19. The computer program product of claim 17, further performing during the migration operation:

receiving an update to one track in the extent during the migration operation;

determining whether the track is located in the migration cache;

writing the update to the migration cache in response to determining that the track is in the migration cache, wherein the updated track is copied from the migration cache to the destination storage;

writing the update to the source storage in response to determining that the track is not maintained in the migration cache.

20. The system of claim 19, wherein the migration cache and a source cache are maintained in at least one memory device in a server in communication with the source storage and the destination storage, wherein writing the update to the source storage comprises writing the update to the source cache, wherein updated tracks in the source cache are destaged to the source storage and wherein updates to tracks in the migration cache are not destaged to the source storage.

21. The system of claim 20, wherein the operations further comprise:

maintaining a destination cache in the server for tracks in the destination storage;

copying tracks in the migration cache for the extent to the destination cache in response to completing the migration of the extent to the destination storage.

22. The computer program product of claim 17, wherein the extent list comprises a write extent list indicating tracks in the extent subject to a write request and a read extent list indicating tracks in the extent subject to a read request, wherein the first set of tracks includes tracks indicated in the first and second extent lists, and wherein the second set of tracks includes tracks indicated in the first and second extent lists not included in the first set and tracks not indicated in the first and second extent lists.