COMPUTER SYSTEM AND DATA MIGRATION METHOD

• US 20130339647A1
• Filed: 06/18/2012
• Published: 12/19/2013
• Est. Priority Date: 06/18/2012
• Status: Active Grant

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Jindo, Kazue, Sakaki, Hidetoshi, Muto, Junichi, Hiramatsu, Shinichi, Miyashita, Jun
• Granted Patent: US 9,213,490 B2
• Time in Patent Office: Days
• US Class Current: 711/165
• CPC Class Codes: G06F 11/1443 Transmit or communication errors
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: G06F 3/0617 in relation to availability
• CPC Class Codes: G06F 3/0635 by changing the path, e.g. traffic rerouting, path reconfiguration
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

The present invention continues host access and holds data of a migration source volume as the latest data even when a fault occurs in any of a plurality of access paths.

Upon receiving a first write command from a host computer via a first access path, the migration source controller writes first update data to the migration source volume and, upon receiving a second write command from the host computer via a second access path, the migration destination controller transfers second update data to the migration source controller via a storage path and, upon receiving the second update data from the migration destination controller, the migration source controller writes the second update data to the migration source volume.

Claims

1. A computer system, comprising:

a plurality of storage apparatuses which manage a plurality of storage devices; and

a host computer which exchanges information with each of the storage apparatuses,

wherein one storage apparatus among the plurality of storage apparatuses is managed as a migration source storage apparatus, the other storage apparatus is managed as a migration destination storage apparatus, a logical volume which is constructed in a storage area of a storage device of the migration source storage apparatus is managed as a migration source volume, a logical volume which is constructed in a storage area of a storage device of the migration destination storage apparatus is managed as a migration destination volume, and the migration source volume and the migration destination volume are interconnected via the storage path,

wherein the migration source storage apparatus comprises a migration source controller which manages the migration source volume as an access target of the host computer,

wherein the migration destination storage apparatus comprises a migration destination controller which virtualizes the migration destination volume as the migration source volume and manages the virtualized migration destination volume as an access target of the host computer,

wherein, in a case where a first access path linking the host computer to the migration source volume and a second access path linking the host computer to the migration destination volume are each online and where the migration destination volume is virtualized as the migration source volume, the host computer manages each of the first access path and the second access path as alternate paths for accessing the migration source volume,

wherein, in a case where a first write command is received from the host computer via the first access path during the period up until the first access path is offline after formation copy processing to migrate data of the migration source volume to the migration destination volume via the storage path has ended, the migration source controller writes first update data appended to the first write command to the migration source volume, and

wherein, in a case where a second write command is received from the host computer via the second access path during the period up until the first access path is offline after formation copy processing has ended, the migration destination controller transfers second update data appended to the second write command to the migration source controller via the storage path, and, under the condition that the second update data is stored in the migration source volume, writes the second update data to the migration destination volume, and wherein the migration source controller also writes the received second update data to the migration source volume in a case where the second update data transferred via the storage path from the migration destination controller is received.

2. The computer system according to claim 1,

wherein, after writing the second update data to the migration source volume, the migration source controller transfers the second update data stored in the migration source volume to the migration destination controller via the storage path, and

wherein, upon receiving the second update data from the migration source controller, the migration destination controller writes the received second update data to the migration destination volume.

3. The computer system according to claim 1,

wherein, after writing the received second update data to the migration source volume, the migration source controller transmits a write completion report to the migration destination controller, and

wherein, upon receiving the second write command from the host computer, the migration destination controller holds the second update data appended to the second write command and, under the condition that the write completion report is received from the migration source controller, writes the held second update data to the migration destination volume.

4. The computer system according to claim 1,

wherein, upon receiving the first write command, the migration source controller transfers first update data which is appended to the first write command to the migration destination controller via the storage path, wherein, upon receiving the first update data from the migration source controller, the migration destination controller writes the received first update data to the migration destination volume and, upon receiving the second write command from the host computer, the migration destination controller converts the second write command into a first update copy command, and transfers the converted first update copy command to the migration source controller via the storage path, and, upon receiving the second update data from the migration source controller, writes the received second update data to the migration destination volume, and

wherein, upon receiving the first update copy command, the migration source controller writes the second update data to the migration source volume and then transfers the second update data stored in the migration source volume to the transfer destination controller via the storage path.

5. The computer system according to claim 1,

wherein, upon receiving the first write command, the migration source controller transfers the first update data appended to the first write command to the migration destination controller via the storage path, wherein, upon receiving the first update data from the migration source controller, the migration destination controller writes the received first update data to the migration destination volume and, upon receiving the second write command from the host computer, the migration destination controller holds the second update data appended to the second write command, converts the second write command into a second update copy command, and transfers the converted second update copy command to the migration source controller via the storage path, and, under the condition that a write completion report is received from the migration source controller, writes the held second update data to the migration destination volume, and

wherein, upon receiving the second update copy command, the migration source controller writes the received second update data to the migration source volume and then transmits the write completion report to the migration destination controller.

6. The computer system according to claim 1,

wherein, if the first access path, the second access path, and the storage path are each formed in a plurality, the host computer accesses the migration destination volume via any second access path of the plurality of second access paths and, under the condition that an abnormal response to the effect that a path fault has occurred in the plurality of storage paths is received from the migration destination controller, the host computer accesses the migration source volume via any first access path among the plurality of first access paths.

7. The computer system according to claim 1,

wherein, if the first access path, the second access path, and the storage path are each formed in a plurality, the host computer accesses the migration destination volume via any second access path of the plurality of second access paths under the condition that a fault in the plurality of first access paths is detected.

8. The computer system according to claim 1,

wherein, if the first access path, the second access path, and the storage path are each formed in a plurality, the host computer accesses the migration source volume via any first access path of the plurality of first access paths under the condition that a fault in the plurality of second access paths is detected.

9. A data migration method for a computer system which comprises:

a plurality of storage apparatuses which manage a plurality of storage devices; and

a host computer which exchanges information with each of the storage apparatuses,

wherein one storage apparatus among the plurality of storage apparatuses is managed as a migration source storage apparatus, the other storage apparatus is managed as a migration destination storage apparatus, a logical volume which is constructed in a storage area of a storage device of the migration source storage apparatus is managed as a migration source volume, a logical volume which is constructed in a storage area of a storage device of the migration destination storage apparatus is managed as a migration destination volume, and the migration source volume and the migration destination volume are interconnected via the storage path,

wherein the migration source storage apparatus comprises a migration source controller which manages the migration source volume as an access target of the host computer,

wherein the migration destination storage apparatus comprises a migration destination controller which virtualizes the migration destination volume as the migration source volume and manages the virtualized migration destination volume as an access target of the host computer,

wherein, in a case where a first access path linking the host computer to the migration source volume and a second access path linking the host computer to the migration destination volume are each online and

where the migration destination volume is virtualized as the migration source volume, the host computer manages each of the first access path and the second access path as alternate paths for accessing the migration source volume,

the data migration method comprising;

a step in which, in a case where a first write command is received from the host computer via the first access path during the period up until the first access path is offline after formation copy processing to migrate data of the migration source volume to the migration destination volume via the storage path has ended, the migration source controller writes first update data appended to the first write command to the migration source volume;

a step in which, in a case where a second write command is received from the host computer via the second access path during the period up until the first access path is offline after formation copy processing has ended, the migration destination controller transfers second update data appended to the second write command to the migration source controller via the storage path;

a step in which, under the condition that the second update data is stored in the migration source volume, the migration destination controller writes the second update data to the migration destination volume; and

a step in which the migration source controller also writes the received second update data to the migration source volume in a case where the second update data transferred via the storage path from the migration destination controller is received.

10. The data migration method according to claim 9, further comprising:

a step in which, after writing the second update data to the migration source volume, the migration source controller transfers second update data which is stored in the migration source volume to the transfer destination controller via the storage path; and

a step in which, upon receiving the second update data from the migration source controller, the migration destination controller writes the received second update data to the migration destination volume.

11. The data migration method according to claim 9, comprising:

a step in which, after writing the received second update data to the migration source volume, the migration source controller transmits a write completion report to the migration destination controller;

a step in which, upon receiving the second write command from the host computer, the migration destination controller holds the second update data appended to the second write command; and

a step in which, under the condition that the write completion report is received from the migration source controller, the migration destination controller writes the held second update data to the migration destination volume.

12. The data migration method according to claim 9, comprising:

a step in which, upon receiving the first write command, the migration source controller transfers first update data which is appended to the first write command to the migration destination controller via the storage path;

a step in which, upon receiving the first update data from the migration source controller, the migration destination controller writes the received first update data to the migration destination volume;

a step in which, upon receiving the second write command from the host computer, the migration destination controller converts the second write command into a first update copy command, and transfers the converted first update copy command to the migration source controller via the storage path;

a step in which, upon receiving the second update data from the migration source controller, the migration destination controller writes the received second update data to the migration destination volume; and

a step in which, upon receiving the first update copy command, the migration source controller writes the second update data to the migration source volume and then transfers the second update data stored in the migration source volume to the transfer destination controller via the storage path.

13. The data migration method according to claim 9, comprising:

a step in which, upon receiving the first write command, the migration source controller transfers the first update data appended to the first write command to the migration destination controller via the storage path;

a step in which, upon receiving the first update data from the migration source controller, the migration destination controller writes the received first update data to the migration destination volume;

a step in which, upon receiving the second write command from the host computer, the migration destination controller holds the second update data appended to the second write command, converts the second write command into a second update copy command, and transfers the converted second update copy command to the migration source controller via the storage path;

a step in which, under the condition that a write completion report is received from the migration source controller, the migration destination controller writes the held second update data to the migration destination volume; and

a step in which, upon receiving the second update copy command, the migration source controller writes the received second update data to the migration source volume and then transmits the write completion report to the migration destination controller.