Information processing system and method

Abstract

To provide an information processing system capable of migrating a volume from a first storage system to a second storage system even when the first storage system is not compatible with the second storage system that is different from a default cloud storage service accessible by a cloud computing service to which the computing instance is migrated.SOLUTION: The information processing system migrates a system volume that stores an OS image for configuring a computer instance to be migrated and a data volume storing data used by the relevant OS to a cloud computer migration tool. The system causes the second storage system to create data volume migrated to the cloud computer by a migration tool and mapped mapping volume, and causes the computer instance to set the data input / output path from the computer instance to the mapping volume.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates generally to information processing, for example to supporting computer and volume migration. [Background technology]

[0002] There is known a technology for migrating a computer that uses a volume in a first storage system (e.g., an on-premise storage system) and a volume (a volume in the first storage system) used by the computer to a cloud environment (mainly a public cloud environment). According to this type of technology, the computer and the volume are migrated to the cloud environment by a cloud migration tool. The cloud migration tool is typically a system provided by a vendor of the cloud environment.

[0003] The computer is migrated to the cloud computer service as a computer instance, and the volume is migrated to a predetermined default cloud storage service (typically a cloud storage service provided by a vendor of the cloud environment) accessible by the cloud computer service.

[0004] Volumes used by a computer include a system volume (which may also be called a boot volume), which is a volume in which an image of the computer's OS (Operating System) is stored, and a data volume, which is a volume in which data input and output by the computer is stored.

[0005] There may be users who wish to migrate at least a data volume to a second storage system different from the default cloud storage service. The second storage system is typically a storage system with better reliability or functionality than the default cloud storage service. Specifically, for example, the second storage system is a cloud storage service of the same cloud environment but developed by a storage vendor rather than a cloud environment vendor.

[0006] According to the technology disclosed in Non-Patent Document 1, the migration destination of a data volume can be a cloud storage service as a second storage system (a migration destination storage system) provided by a storage vendor of a first storage system (a migration source storage system) instead of a default cloud storage service. A cloud migration tool is not used to migrate a data volume from the first storage system to the second storage system, but a unique tool provided by the storage vendor, specifically, a so-called remote copy function for migrating a volume between storage systems, is used.

[0007] According to the technology disclosed in Non-Patent Document 2, in an on-premise environment, a virtual machine in a virtual environment such as a hypervisor recognizes a volume (hereinafter, storage volume) in an on-premise storage system. The format of the storage volume conforms to the virtual environment. The virtual machine executes an application, and the storage volume has a volume for each application in the virtual machine. The volume for each application is migrated from the on-premise storage system to a cloud storage system provided by the same vendor as the vendor of the storage system. In the above migration, since the format of the storage volume in the on-premise environment conforms to the virtual environment of the on-premise environment, the data storage format of the storage volume is converted in advance in the on-premise environment, and then the storage volume is migrated to the cloud storage system. [Prior art documents] [Non-patent literature]

[0008] [Non-Patent Document 1] Pure Cloud Block Store vVol VM Migration to AWS with CloudEndurehttps: / / support.purestorage.com / Pure_Cloud_Block_Store / Pure_Cloud_Block_Store_vVol_VM_Migration_to_AWS_with_CloudEndure [Non-Patent Document 2] Transferring VMware data from an on-premises FlashArray to CBShttps: / / support.purestorage.com / Pure_Cloud_Block_Store / Transferring_VMware_data_from_an_on-premises_FlashArray_to_CBS Summary of the Invention [Problem to be solved by the invention]

[0009] However, in the technology disclosed in Non-Patent Document 1, the first storage system as the source of the data volume to be migrated to the second storage system is limited to a storage system compatible with the second storage system. Examples of storage systems that are not compatible with the second storage system include the following: A storage system provided by a storage vendor different from the storage vendor of the second storage system. A storage system provided by the storage vendor of the second storage system, but of a different type (eg, model) than the second storage system.

[0010] The technology disclosed in Non-Patent Document 2 also has the above-mentioned problems because migration is performed between storage systems of the same vendor. In the technology disclosed in Non-Patent Document 2, even when migration is performed between storage systems of the same vendor, in order for an application to be able to interpret data in the volume of the application at the migration destination without a virtual environment, it is necessary to prepare a volume that is independent of the format of the virtual environment in the on-premise storage system and copy data from a volume in the storage volume to the volume. For this reason, the on-premise storage system needs storage resources for a volume (a copy destination volume) that is independent of the format of the virtual environment for each application. [Means for solving the problem]

[0011] An information processing system capable of communicating with a cloud computer, a first storage system, and a second storage system is constructed. When a computer instance is migrated to the cloud computer and data used by the computer instance is migrated from the first storage system to the second storage system, the information processing system migrates a system volume in which an image of an OS (Operating System) for constituting the computer instance to be migrated is stored and a data volume in which data used by the OS is stored from the first storage system to the cloud computer to a migration tool of the cloud computer. The information processing system creates a mapping volume in the second storage system that is mapped to the data volume migrated to the cloud computer by the migration tool of the cloud computer, and sets a path for data input / output from the computer instance to the mapping volume in the computer instance. Effect of the Invention

[0012] Even if a first storage system is not compatible with a second storage system that is different from a default cloud storage service accessible by a cloud computing service to which a computing instance is migrated, a volume in the first storage system can be migrated to the second storage system without preparing a destination volume in the first storage system to which the volume to be migrated is to be copied. [Brief description of the drawings]

[0013] [Figure 1] 1 shows an overview of system migration according to a first embodiment. [Diagram 2] 1 shows the configuration of the cloud environment after the cloud migration process is completed. [Diagram 3] 1 shows the configuration of a cloud environment after a mapping volume is created. [Figure 4] 1 illustrates the migration of data from a mapping volume to a target volume. [Diagram 5] The flow of the system migration process is shown. [Figure 6] The flow of migration processing is shown. [Figure 7] 1 shows the flow of starting the cloud migration process. [Figure 8] 13 shows the flow of a process for confirming the completion of cloud migration processing. [Figure 9] 13 shows the flow of a process for determining an external connection method. [Figure 10] 1 shows the flow of a path switching process. [Figure 11] 13 shows an overview of system migration according to a second embodiment. [Figure 12] 13 shows an overview of system migration according to a third embodiment. [Figure 13] 13 shows an overview of system migration according to a fourth embodiment. [Figure 14] 13 shows an overview of system migration according to the fifth embodiment. [Figure 15] 13 shows an overview of system migration according to the sixth embodiment. [Figure 16]13 shows an overview of system migration according to the seventh embodiment. [Figure 17] 13 shows the configuration of a second storage system according to the seventh embodiment. [Figure 18] 13 shows the flow of processing performed in the eighth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] In the following description, an "interface unit" may be one or more interface devices. The one or more interface devices may be at least one of the following: One or more I / O (Input / Output) interface devices. The I / O (Input / Output) interface devices are interface devices to at least one of the I / O devices and a remote display computer. The I / O interface device to the display computer may be a communications interface device. The at least one I / O device may be a user interface device, e.g., either an input device such as a keyboard and pointing device, or an output device such as a display device. One or more communication interface devices. The one or more communication interface devices may be one or more homogeneous communication interface devices (e.g., one or more NICs (Network Interface Cards)) or two or more heterogeneous communication interface devices (e.g., a NIC and an HBA (Host Bus Adapter)).

[0015] In the following description, a "memory" refers to one or more memory devices, which are an example of one or more storage devices, and may typically be a primary storage device. At least one memory device in the memory may be a volatile memory device or a non-volatile memory device.

[0016] In the following description, a "persistent storage device" may be one or more persistent storage devices, which are an example of one or more persistent storage devices. A persistent storage device may typically be a non-volatile storage device (e.g., an auxiliary storage device), and more specifically, may be, for example, a hard disk drive (HDD), a solid state drive (SSD), a non-volatile memory express (NVME) drive, or a storage class memory (SCM).

[0017] Also, in the following description, "storage device" may be at least memory, including memory and persistent storage device.

[0018] Furthermore, in the following description, a "processor" may be one or more processor devices. The at least one processor device may typically be a microprocessor device such as a CPU (Central Processing Unit), but may also be other types of processor devices such as a GPU (Graphics Processing Unit). The at least one processor device may be a single-core or multi-core. The at least one processor device may be a processor core. The at least one processor device may also be a processor device in a broader sense, such as a circuit that is a collection of gate arrays written in a hardware description language that performs part or all of the processing (e.g., a Field-Programmable Gate Array (FPGA), a Complex Programmable Logic Device (CPLD), or an Application Specific Integrated Circuit (ASIC)).

[0019] In the following description, functions may be described using the expression "yyy unit", but the functions may be realized by one or more computer programs being executed by a processor, or by one or more hardware circuits (e.g., FPGA or ASIC), or by a combination of these. When a function is realized by a program being executed by a processor, the function may be at least a part of the processor, since the defined processing is performed using a storage device and / or an interface device, etc., as appropriate. Processing described using a function as the subject may be processing performed by a processor or a device having the processor.

[0020] The program may be installed from a program source. The program source may be, for example, a program distribution computer or a computer-readable recording medium (for example, a non-transitory recording medium). The description of each function is an example, and multiple functions may be combined into one function, or one function may be divided into multiple functions.

[0021] Furthermore, any information (for example, at least one of an "ID", a "name", and a "number") may be adopted as information for identifying an element.

[0022] In the following description, a "volume" may be a logical storage space (address space). A volume may be a real volume (a volume based on a physical storage device (e.g., a persistent storage device)) or a virtual volume.

[0023] Hereinafter, several embodiments of the present invention will be described with reference to the drawings. In the drawings, a "volume" is written as a "VOL." Furthermore, migration of a volume refers to the migration of data stored in the volume. [First embodiment]

[0024] FIG. 1 shows an overview of system migration according to the first embodiment.

[0025] The migration source environment is an on-premise environment 100. The computer system in the on-premise environment 100 includes a computer 101 and a first storage system 102 to which the computer 101 is connected. The computer 101 may be a physical computer, and the first storage system 102 may be a physical storage system (for example, a so-called disk array device). The first storage system 102 corresponds to the migration source storage system. Of the computers 101 and the first storage systems 102, at least the computers 101 may exist multiple times. The first storage system 102 may have multiple volumes.

[0026] The destination environment is a cloud environment 106 (typically a public cloud environment). In the cloud environment 106, cloud computing services such as a cloud computing service 107 and a cloud storage service 109 are provided. The cloud computing service 107 may be an execution environment of an instance, and the cloud storage service 109 is a predetermined default cloud storage service that the cloud computing service 107 can access.

[0027] The second storage system 112 corresponds to a destination storage system. In this embodiment, the second storage system 112 is a cloud storage service provided in the cloud environment 106.

[0028] The cloud environment 106 is an environment (e.g., a cloud platform) provided by a cloud vendor, and the cloud computing service 107 and the cloud storage service 109 may be cloud computing services provided by the cloud vendor. For example, the cloud computing service 107 may be Amazon Elastic Compute Cloud (Amazon EC2), and the cloud storage service 109 may be Amazon Elastic Block Store (Amazon EBS) ("Amazon" is a registered trademark). The second storage system 112 may be a cloud storage service developed by a storage vendor. Preferably, the second storage system 112 may be more reliable or functional than the cloud storage service 109.

[0029] Migration of a computer or a volume in an environment other than the cloud environment 106 (for example, the on-premise environment 100, or a cloud environment other than the cloud environment 106) to the cloud environment 106 is performed by a cloud migration tool 190. That is, in this embodiment, migration of a migration target is performed from the on-premise environment 100 to the cloud environment 106, but the present invention may also be applied to migration from another cloud environment to the cloud environment 106. The cloud migration tool 190 is typically a system (function) provided by the vendor of the cloud environment 106.

[0030] An information processing system 105 is constructed. The information processing system 105 is a system that supports migration of a migration target (for example, a computer or a volume) from a migration source to a migration destination. The information processing system 105 may be called a management system. The information processing system 105 may be outside the on-premise environment 100 and the cloud environment 106 as shown in the figure, or may be in either the on-premise environment 100 or the cloud environment 106. In this embodiment, the information processing system 105 is a physical system (for example, a computer), but may be a logical system provided on a physical computing resource. The information processing system 105 can operate at least one of the computer 101, the first storage system 102, the cloud migration tool 190, the cloud computer service 107, the computer instance 108, the cloud storage service 109, and the second storage system 112 via a communication medium such as a network or a dedicated line. The information processing system 105 may operate the cloud storage service 109 by instructing the second storage system (or without going through another system, such as the second storage system 112).

[0031] The information processing system 105 includes an interface device 51, a storage device 52, and a processor 53 connected thereto.

[0032] The interface device 51 is connected to, for example, the above-mentioned communication medium (eg, a network).

[0033] The storage device 52 stores programs and information. An example of the information is management information 140. The management information 140 is information that is referred to or updated as appropriate for the system migration process (see FIG. 5) by the information processing system 105. The management information 140 may include information that indicates the progress of the system migration process, and may include, for example, the following information (a) to (c). (a) Computer migration management information, which is information about a computer to be migrated from the on-premise environment 100 to the cloud environment 106. The computer migration management information includes, for each computer to be migrated, identification information of the computer and information indicating the migration status of the computer (for example, migration not started, migration started, or migration completed). (b) Volume migration management information, which is information regarding volumes to be migrated from the on-premise environment 100 to the cloud environment 106. The volume migration management information includes, for each volume to be migrated, identification information of the volume and information indicating the migration status of the volume (e.g., migration not started, migration started, or migration completed). (c) intermediate volume management information, which is information relating to intermediate volumes 111 described below in the cloud storage service 109. The intermediate volume management information includes, for each intermediate volume 111, identification information of the intermediate volume 111, information indicating the migration status of the intermediate volume 111 (e.g., waiting for creation, creation completed, migration started, migration completed, deletion started or deletion completed), identification information of the mapping volume 113 which is the volume into which the intermediate volume 111 has been virtualized, and identification information of the target volume 114 which is the migration destination of the mapping volume 113.

[0034] By the processor 53 executing the program, functions such as a tool operation unit 151, a transfer completion confirmation unit 152, and a transfer control unit 153 are realized.

[0035] Now, the first storage system 102 provides volumes to the computer 101, and the volumes recognized by the computer 101 include a system volume 103 and a data volume 104. In other words, a path connecting the computer 101 and the system volume 103 and a path connecting the computer 101 and the data volume 104 are established (see the dashed arrow extending from the computer 101). The system volume 103 is a volume in which an image of the OS (Operating System) of the computer 101 is stored, and is typically a volume for starting up the computer 101. The data volume 104 is a volume in which data input / output by the computer 101 (for example, an application executed by the computer 101) after startup is stored.

[0036] The cloud migration tool 190 is a system (function) that migrates the computer 101 to a cloud computer service 107 as a computer instance 108 and migrates the system volume 103 of the computer 101 to a cloud storage service 109 .

[0037] In this embodiment, a system migration process for migrating a computer and a volume from the on-premise environment 100 to the cloud environment 106 is performed according to the following flow.

[0038] The tool operation unit 151 issues a migration instruction to the cloud migration tool 190, specifying the computer 101 to be migrated and the data volume 104 recognized by the computer 101 (S11). For example, identification information of the computer 101 and identification information of the data volume 104 (for example, volume identification information recognized by the computer 101) are specified. The system volume 103 recognized by the computer 101 may be specified to the cloud migration tool 190 as a migration target in the same manner as the data volume 104, or if the computer 101 is specified, it may be considered to be specified as a migration target without specifying the system volume 103. In any case, in this example, the computer 101, the system volume 103, and the data volume 104 shown in the figure are migration targets. Note that the specification of the data volume 104 to be migrated in S11 may be performed by applying another means, such as deleting (detaching) the data volume 104 that is not a migration target from the computer 101 before issuing a migration instruction to the cloud migration tool 190.

[0039] In response to the migration instruction, the cloud migration tool 190 performs cloud migration processing including migration of the computer 101, the system volume 103, and the data volume 104. Specifically, the cloud migration tool 190 migrates the specified computer 101 to the cloud computer service 107 as a computer instance 108. The cloud migration tool 190 also migrates the system volume 103 to the cloud storage service 109 as the system volume 110 (specifically, for example, migration from volume 103 to volume 110). The cloud migration tool 190 also migrates the data volume 104 to the cloud storage service 109 as the intermediate volume 111 (specifically, for example, migration from volume 104 to volume 111). The intermediate volume 111 is the volume of the data volume 104 that has been migrated to the cloud storage service 109.

[0040] The migration completion confirmation unit 152 confirms that the above-mentioned cloud migration process has been completed by the cloud migration tool 190 in response to a migration instruction. When the cloud migration process is completed, the computer instance 108 can access the system volume 110 (see the dashed arrow extending from the computer instance 108 to the system volume 110). The computer instance 108 starts up by referencing the system volume 110 (for example, reading an OS image).

[0041] After the completion of the cloud migration process is confirmed by the migration completion confirmation unit 152, the migration control unit 153 creates a mapping volume 113, which is a volume in which the intermediate volume 111 has been virtualized, in the second storage system 112, and migrates data from the mapping volume 113, which has been made online so that I / O can be performed from the computer instance 108, to the target volume 114. Note that a single volume may serve as both the mapping volume 113 and the target volume 114.

[0042] Specifically, for example, the migration control unit 153 causes the second storage system 112 to execute an external connection, which is to associate the intermediate volume 111 with the second storage system 112 (S12). As a result, the intermediate volume 111 is recognized by the second storage system 112.

[0043] Thereafter, the migration control unit 153 creates a mapping volume 113 in the second storage system 112, which is a volume in which the externally connected intermediate volume 111 has been virtualized (a volume to which the intermediate volume 111 is mapped). When the mapping volume 113 has been created, the migration control unit 153 places the mapping volume 113 in an online state in which I / O can be performed from the computer instance 108. Specifically, for example, the migration control unit 153 causes the second storage system 112 to provide the mapping volume 113 to the computer instance 108 (for example, causes the computer instance 108 to recognize the mapping volume 113), and also causes the second storage system 112 to start accepting I / O requests that specify the mapping volume 113. The migration control unit 153 may permit the computer instance 108 to issue an I / O request to the mapping volume 113, and the computer instance 108, having received the permission, may send an I / O request to the second storage system 112 that appropriately specifies the mapping volume 113 in accordance with the processing of the computer instance 108.

[0044] The migration control unit 153 causes the second storage system 112 to execute data migration from the mapping volume 113 to the target volume 114 (S13). This causes data migration from the mapping volume 113 (specifically, the intermediate volume 111 mapped to the mapping volume 113) to the target volume 114. When this data migration is complete, data I / O to the target volume 114 of the computer instance 108 becomes possible (see the dashed arrow extending from the computer instance 108 to the target volume 114).

[0045] According to the above system migration process, migration from the source volume (data volume) 104 of the first storage system 102 to the target volume 114 of the second storage system 112 is realized without a function of remote copying data from the first storage system 102 to the second storage system 112 (for example, a function of performing remote copying on a volume-by-volume (volume recognized by a storage system) basis between storage systems). Therefore, even if the first storage system 102 does not have compatibility with the second storage system 112, the data volume 104 in the first storage system 102 can be migrated to the second storage system 112, which is a cloud storage service with better reliability or functionality than the default cloud storage service 109. The second storage system 112 may exist in an environment (for example, another cloud environment) different from the cloud environment 106.

[0046] 1, the volume to be migrated to the second storage system 112 is the data volume 104, but the system volume 103 may also be migrated to the second storage system 112. In other words, the system volume 110 may be migrated as an intermediate volume, a mapping volume in which the intermediate volume is virtualized is created in the second storage system 112, data is migrated from the mapping volume to the target volume, and as a result, the target volume may become the system volume migrated to the second storage system 112.

[0047] Furthermore, if there are multiple data volumes 104 recognized by the computer 101, all or some of the multiple data volumes 104 may be targeted for migration to the second storage system 112.

[0048] The above explanation regarding the system migration process will be supplemented below with reference to FIGS.

[0049] FIG. 2 shows the configuration of the cloud environment 106 after the cloud migration process is completed.

[0050] When cloud migration processing is completed by cloud migration tool 190, intermediate volume 111 is also connected to computer instance 108 in addition to system volume 110. That is, a path is established connecting computer instance 108 and intermediate volume 111 (see the dashed arrow extending from computer instance 108 to intermediate volume 111). At this time, I / O by computer instance 108 to intermediate volume 111 may be started.

[0051] However, in this embodiment, the migration control unit 153 prevents the computer instance 108 from starting I / O to the intermediate volume 111. Specifically, for example, the migration control unit 153 may perform at least one of the following. The computer instance 108 is not permitted to issue an I / O request that specifies the intermediate volume 111. (For example, the computer instance 108 is prohibited from issuing an I / O request that specifies the intermediate volume 111.) The cloud storage service 109 is not made to start accepting I / O requests that specify the intermediate volume 111. (For example, the cloud storage service 109 is prohibited from accepting I / O requests that specify the intermediate volume 111.)

[0052] FIG. 3 illustrates the configuration of the cloud environment 106 after the mapping volume 113 has been created.

[0053] The intermediate volume 111 is externally connected to a second storage system 112. The external connection method depends on the cloud storage service 109 in which the intermediate volume 111 resides. A specific example of the external connection method will be described later.

[0054] A mapping volume 113, which is a volume obtained by virtualizing the intermediate volume 111 externally connected to the second storage system 112, is created in the second storage system 112. I / O from the computer instance 108 to the created mapping volume 113 is started. For example, in response to an instruction from the migration control unit 153 to the second storage system 112, a path is established connecting the computer instance 108 and the mapping volume 113. An I / O request is issued from the computer instance 108 via the path, and in response to the I / O request, the second storage system 112 performs I / O to the mapping volume 113.

[0055] When a path connecting the computer instance 108 and the intermediate volume 111 is established, the migration control unit 153 may instruct the cloud storage service 109 (and / or the computer instance 108) to delete the path (for example, to take the path offline or to delete the path setting itself) before a path connecting the computer instance 108 and the mapping volume 113 is established. In response to the instruction, the path may be deleted. Note that, when the computer instance 108, the cloud storage service 109, and the second storage system 112 have a multipath function, there may be a time when the path connecting the computer instance 108 and the intermediate volume 111 and the path connecting the computer instance 108 and the mapping volume 113 coexist.

[0056] FIG. 4 illustrates the migration of data from a mapping volume 113 to a target volume 114 .

[0057] In migrating data from the mapping volume 113 to the target volume 114, it is possible to perform I / O to the mapping volume 113 (and the target volume 114) (accepting and processing an I / O request specifying the identification information of the mapping volume 113). Specifically, for example, when the second storage system 112 receives an I / O request specifying the identification information of the mapping volume 113, the following may be performed. The second storage system 112 judges whether or not the volume area (area in the volume) of the I / O destination is an area to which data migration has already been completed. If the result of the determination is false, the second storage system 112 performs I / O to the mapping volume 113 (that is, I / O to the intermediate volume 111). If the result of the determination is true, the second storage system 112 performs I / O to the target volume 114 .

[0058] That is, the computer instance 108 may recognize the mapping volume 113 and the target volume 114 as one volume without distinction. When the second storage system 112 receives an I / O request specifying the one volume, the second storage system 112 may perform I / O to the mapping volume 113 or the target volume 114 according to the I / O request, depending on whether the volume area (e.g., LBA (Logical Block Address)) specified in the I / O request is an area that has already been migrated.

[0059] Furthermore, in the cloud migration process, the identification information of the data volume (source volume) 104, which is recognized by the computer 101, may be handed over to the intermediate volume 111. The identification information may be handed over to the mapping volume 113 in which the intermediate volume 111 is virtualized. The identification information handed over to the mapping volume 113 (the identification information of the data volume (source volume) 104) may be recognized by the computer instance 108. During the data migration from the mapping volume 113 to the target volume 114, the second storage system 112 may receive an I / O request from the computer instance 108 specifying the identification information. After the data migration from the mapping volume 113 to the target volume 114 is completed, the identification information (the identification information of the data volume (source volume) 104) may be handed over to the target volume 114. By taking over the identification information in this way, after migration of the computer 101, the computer instance 108 can access the target volume 114 using the same identification information as the identification information of the data volume (source volume) 104.

[0060] The system migration process according to this embodiment will be described below.

[0061] FIG. 5 shows the flow of the system migration process.

[0062] A migration process (S501) is performed for each migration target (computer and volume) in the migration source environment (the on-premise environment 100 in this embodiment). When all migration targets have been migrated from the migration source environment, the migration source environment may be deleted (S502).

[0063] In the system migration process, when there are multiple data volumes 104, migration of the multiple data volumes 104 may be performed in parallel. That is, each time the completion of migration to the cloud storage service 109 is confirmed for each data volume 104, the intermediate volume 111 corresponding to that data volume 104 may be externally connected to the second storage system 112, a mapping volume 113 which is a virtualization of the intermediate volume 111 may be created, and data may be migrated from the mapping volume 113 to the target volume 114 with the mapping volume 113 online. That is, the completion of the cloud migration process may be confirmed for each data volume 104. This is expected to reduce the time required for the system migration process.

[0064] FIG. 6 shows the flow of the migration process (S501 in FIG. 5).

[0065] A process of starting the cloud migration process (S600) is performed. Specifically, as shown in FIG. 7, the tool operation unit 151 receives a designation of the computer 101 and the volume to be migrated from a user (for example, an operator of the information processing system 105), and the cloud migration process is started. Specifically, the tool operation unit 151 issues a migration instruction designating the designated computer 101 and the designated volume to the cloud migration tool 190. In response to the migration instruction, the cloud migration tool 190 starts migrating the designated computer 101 to the cloud computer service 107 as a computer instance 108 (S700), and also starts migrating the designated volume to the cloud storage service 109 (S701). In this embodiment, all or a part of the data volumes 104 among one or more data volumes 104 recognized by the designated computer 101 are designated. The migration of the system volume 103 to the cloud storage service 109 may be performed in S700 or in S701. In S701 (volume migration), the specified data volume 104 and the system volume 103 recognized by the computer 101 to be migrated are migrated. In S701, a volume in the first storage system 102 may be the migration source, and a volume in the cloud storage service 109 may be the migration destination. For example, an intermediate volume 111 is prepared in the cloud storage service 109 for each specified data volume 104, and data migration from the data volume 104 to the intermediate volume 111 is started. S700 and S701 may be performed in parallel. In addition, the tool operation unit 151 may add information about the specified computer 101 to the above-mentioned computer migration management information in the management information 140 (the migration state of the computer 101 is "migration started"). In addition, the tool operation unit 151 may add information about the volume to be migrated to the above-mentioned volume migration management information in the management information 140 (the migration state of the volume is "migration started"). Furthermore, the tool operation unit 151 may add information about the migration destination intermediate volume 111 to the above-mentioned intermediate volume management information in the management information 140 (the migration status of the intermediate volume is "waiting for creation").

[0066] Thereafter, as shown in Fig. 6, a completion confirmation process (S601) of the cloud migration process is performed. Specifically, as shown in Fig. 8, the migration completion confirmation unit 152 confirms the completion of migration of the migration target computer 101 (that the computer 101 has been migrated to the cloud computer service 107 as the computer instance 108) by communication with the cloud migration tool 190 (S800), and also confirms the completion of migration of the designated volume (that the volume has been migrated to the cloud storage service 109) (S801). S800 and S801 may be performed in parallel. The migration completion confirmation unit 152 may update the management information 140 (for example, the migration status of the computer 101 may be updated to "migration completed", the migration status of the volume may be updated to "migration completed", and the migration status of the intermediate volume 111 may be updated to "creation completed").

[0067] After completion of the cloud migration process is confirmed, the migration control unit 153 may put the intermediate volume 111 in an online state (S602). Specifically, for example, depending on the cloud migration tool 190, a path may be established connecting the created intermediate volume 111 and the computer instance 108, and the migration control unit 153 may put this path in an online state. However, S602 may be optional, and in this embodiment, S602 is not performed.

[0068] After the completion of the cloud migration process is confirmed, the migration control unit 153 performs a process of determining an external connection method (S603). For example, as shown in Fig. 9, the migration control unit 153 determines the location of the intermediate volume 111 (S900), and determines an external connection method according to the determined location. The management information 140 may have external connection management information (information including, for each location (e.g., cloud storage service) where the intermediate volume 111 may be located, identification information of the location and information indicating the external connection method), and the migration control unit 153 may perform S900 by referring to the external connection management information.

[0069] 9, when the placement location is cloud storage service A, the migration control unit 153 determines an external connection method for directly attaching the intermediate volume 111 to a predetermined instance in the second storage system 112 using a function of the cloud storage service A (S901). When the placement location is cloud storage service B, the migration control unit 153 determines an iSCSI connection of the intermediate volume 111 to the second storage system 112 as the external connection method (S902). When the placement location is cloud storage service C, the migration control unit 153 determines an external connection method for directly attaching the intermediate volume 111 to a predetermined instance in the second storage system 112 using a function of the cloud storage service C (S903). In order to virtualize the intermediate volume 111 (to create the mapping volume 113), it is necessary to externally connect the intermediate volume 111 to the second storage system 112, but since the external connection depends on the placement location of the intermediate volume 111, the process shown in Figure 9 makes it possible to externally connect the intermediate volume 111 to the second storage system 112 using an appropriate external connection method according to the placement location of the intermediate volume. Note that in the explanation referring to Figure 9, the "placement location" may also be referred to as the "type of cloud environment in which the intermediate volume is placed" or the "type of cloud storage service in which the intermediate volume is placed".

[0070] 6, the migration control unit 153 causes the second storage system 112 to execute the external connection using the external connection method determined in S603 (S604). As a result, the second storage system 112 externally connects the intermediate volume 111 to the second storage system 112.

[0071] Next, the migration control unit 153 causes the second storage system 112 to virtualize the externally connected intermediate volume 111 (S605). As a result, the second storage system 112 creates a mapping volume 113 in the second storage system 112, which is a volume into which the intermediate volume 111 has been virtualized.

[0072] Next, a path switching process is performed (S606). Specifically, as shown in FIG. 10, the migration control unit 153 judges whether or not all of the computer instance 108, the cloud storage service 109, and the second storage system 112 have a multipath function (S1000). For example, the management information 140 may include information indicating the presence or absence of a multipath function for each of the computer instance 108, the cloud storage service 109, and the second storage system 112, and the judgment in S1000 may be performed based on the management information 140. In addition, the "multipath function" is a function that allows multiple paths (for example, all of the multiple paths are online paths) for one volume identification information, and selects and uses one of the multiple paths. The "online path" is a path that can be used to send an I / O request.

[0073] When the result of the determination in S1000 is true (S1000: YES), since multipath is permitted, the migration control unit 153 adds a path connecting the computer instance 108 and the mapping volume 113 (for example, instructs at least one of the computer instance 108 and the second storage system 112 to add the path) (S1001). As a result, a path connecting the computer instance 108 and the mapping volume 113 is added. Thereafter, the migration control unit 153 deletes the path connecting the computer instance 108 and the intermediate volume 111 (for example, instructs at least one of the computer instance 108 and the second storage system 112 to delete the path) (S1002). As a result, the path connecting the computer instance 108 and the intermediate volume 111 is deleted. Note that, if I / O has been started via the path connecting the computer instance 108 and the intermediate volume 111 before the path switching process, I / O can be performed via either the path or the path added in S1001. If I / O has not been started via a path connecting the computer instance 108 and the intermediate volume 111 before the path switching process, and a path has been added by S1001, the migration control unit 153 may instruct the computer instance 108 and the second storage system 112 to start I / O via that path. If a path connecting the computer instance 108 and the intermediate volume 111 has not been established before the path switching process, S1002 is skipped.

[0074] If the result of the determination in S1000 is false (S1000: NO), since multipath is not permitted, the migration control unit 153 deletes the path connecting the computer instance 108 and the intermediate volume 111 (S1003). Thereafter, the migration control unit 153 adds a path connecting the computer instance 108 and the mapping volume 113, and sets the path to an online state (S1004). As a result, a path connecting the computer instance 108 and the mapping volume 113 is added, and I / O via the path is started. Note that if a path connecting the computer instance 108 and the intermediate volume 111 is not established before the path switching process, S1003 is skipped.

[0075] As described above, it is possible to appropriately add and delete paths depending on whether or not multipath is permitted.

[0076] Furthermore, if multipathing is not permitted, S1003 is required before S1004. For this reason, if I / O is started via a path to the intermediate volume 111, processing such as stopping that I / O is required. In this embodiment, I / O to the intermediate volume 111 is not started, so processing to stop I / O can be made unnecessary.

[0077] Furthermore, if it is known in advance that multipathing is permitted (for example, if S1000, S1003 and S1004 are always unnecessary among S1000 to S1004), I / O may be started via a path to the intermediate volume 111 before the mapping volume 113 is created. This is because there is no need to perform processing to stop I / O.

[0078] After the path switching process (S606), as shown in FIG. 6, the migration control unit 153 causes the second storage system 112 to start data migration from the mapping volume 113 to the target volume 114 (S607). This causes the second storage system 112 to start data migration from the mapping volume 113 to the target volume 114. The target volume 114 may be a volume created in the second storage system 112 in response to an instruction from the migration control unit 153, or may be a volume designated by the migration control unit 153 from among multiple volumes in the second storage system 112. Also, as described above, when the second storage system 112 receives an I / O request from the computer instance 108 during this migration, the I / O according to the I / O request is performed on the mapping volume 113 or the data volume 104. The I / O to the mapping volume 113 is actually performed on the intermediate volume 111. Furthermore, in S607, the migration control unit 153 may update the management information 140 (for example, the migration status of the intermediate volume 111 may be set to "migration started").

[0079] The migration control unit 153 confirms the completion of data migration from the mapping volume 113 to the data volume 104 (S608). For example, the migration control unit 153 receives a notification of the completion of migration from the second storage system 112. In S608, the migration control unit 153 may update the management information 140 (for example, the migration status of the intermediate volume 111 may be set to "migration completed").

[0080] The migration control unit 153 causes the second storage system 112 to execute external connection release based on the external connection method determined in S603 (S610). As a result, the second storage system 112 releases the external connection of the intermediate volume 111 to the second storage system 112.

[0081] The migration control unit 153 causes the cloud storage service 109 to delete the intermediate volume 111 for which data migration has been completed (S611). As a result, the cloud storage service 109 deletes the intermediate volume 111. As a result, unnecessary consumption of resources of the cloud storage service 109 is avoided. In S611, the migration control unit 153 may update the management information 140 (for example, the migration status of the intermediate volume 111 may be set to "deletion started or deletion completed").

[0082] The migration control unit 153 may cause the first storage system 102 to delete the data volume (source volume) 104 (S612).

[0083] In addition, a processing logic that executes at least a part of a series of processes after confirmation of completion of the cloud migration process (e.g., external connection of the intermediate volume 111, creation of the mapping volume 113, and data migration from the mapping volume 113 to the target volume 114) is provided in, for example, the second storage system 112, and the migration control unit 153 may give an instruction to the processing logic specifying necessary parameters (e.g., identification information of the intermediate volume, identification information of the target volume 114), so that at least a part of the series of processes described above is performed automatically. [Second embodiment]

[0084] The second embodiment will be described. In this case, differences from the first embodiment will be mainly described, and explanations of commonalities with the first embodiment will be omitted or simplified. This point also applies to the third embodiment and other embodiments thereafter.

[0085] FIG. 11 shows an overview of system migration according to the second embodiment.

[0086] In the on-premise environment 100, a hypervisor 120, which is a system that virtualizes a computer, is executed in a physical system (for example, a physical computer). The hypervisor 120 executes a computer VM (Virtual Machine) 121, which is a virtualized computer.

[0087] The volumes provided by the first storage system 102 include, for example, volumes 811 and 814 .

[0088] In the volume 811, a data store 123 for the hypervisor 120 (for example, a file system space that can be interpreted by the hypervisor) is created, for example, by the hypervisor 120. In the data store 123, a system VM volume 124 that is a system volume recognized by the computer VM 121 is stored.

[0089] A data store 125 for the hypervisor 120 is also created in volume 814. A data VM volume 127, which is a data volume recognized by the computer VM 121, is stored in the data store 125. Multiple data VM volumes 127 may exist in one data store 125. I / O from the computer VM 121 to the data VM volume 127 is performed via the hypervisor 120, and therefore data exists in the data VM volume 127 in a data arrangement that can be interpreted by the hypervisor 120. A "VM volume" is a virtual disk that is a block device seen from the computer VM 121. A "data store" is a storage area for VM volumes.

[0090] As described above, when the computer is computer VM 121, I / O is performed to a VM volume (VM volume in a data store) via hypervisor 120, but the data arrangement in the VM volume is for hypervisor 120. In other words, the arrangement of the VM volume and the data arrangement of the VM volume (data in the VM volume) cannot be interpreted without hypervisor 120.

[0091] According to a comparative example based on Non-Patent Document 1, it is possible to migrate the volume 814 from the first storage system 102 to the second storage system 112 by using the above-mentioned remote copy function (i.e., not via the cloud storage service 109). However, if the cloud computer service 107 does not have the same hypervisor 120 as the on-premise environment 100, there is no means for interpreting data structures such as data stores, VM volume arrangement, and data arrangement of the VM volume in the volume migrated to the second storage system 112. Therefore, the computer instance 108 in the cloud computer service 107 cannot interpret the data arrangement of the VM volume migrated to the second storage system 112. In other words, migration cannot be performed while maintaining a state in which the computer instance 108 can interpret the VM volume.

[0092] According to a comparative example based on Non-Patent Document 1, the remote copy function performs migration in units of volumes recognized by the storage system. Therefore, if there are multiple data VM volumes 127 in the volume 814 provided by the first storage system 102, all of the multiple data VM volumes 127 are migrated. In other words, migration cannot be performed in units of data VM volumes.

[0093] Also, according to a comparative example based on Non-Patent Document 2, before migration to the cloud environment 106, the data storage format is changed in the on-premise environment 100, and then migration is performed by the remote copy function. In the change of the data storage format, the data stored in the data VM volume 127 is copied to a volume provided by the first storage system 102 (a volume in which the data store 125 is not created). This change of the data storage format allows the computer VM 121 to interpret the data VM volume (copy destination volume) without the hypervisor 120. Thereafter, the data VM volume (copy destination volume) is migrated to the second storage system 112 by the above-mentioned remote copy function. Since the on-premise environment 100 allows the computer VM 121 to interpret the data VM volume (copy destination volume) without the hypervisor 120, it is possible to interpret the data VM volume migrated to the second storage system 112 from the computer instance 108 even after the data VM volume is migrated to the second storage system 112. However, when changing the data storage format in the on-premise environment 100, additional space is used for copying data (additional storage capacity is required for the destination volume), so migration is not possible if there is insufficient free space in the first storage system 102.

[0094] In this embodiment, the data VM volume (and the system VM volume) is migrated to the cloud storage service 109 by the cloud migration tool 190. The cloud migration tool 190 converts the data arrangement in the VM volume into a data arrangement that can be interpreted by the computer instance 108 and migrates the VM volume to the cloud storage service 109. Therefore, the data arrangement of the system VM volume 128 migrated to the cloud storage service 109 of the system VM volume 124 can be interpreted by the computer instance 108 even without the hypervisor 120. Similarly, the data arrangement of the data VM volume 129 migrated to the cloud storage service 109 of the data VM volume 127 can be interpreted by the computer instance 108 even without the hypervisor 120. This data VM volume 129 is an intermediate volume, and is virtualized in the second storage system 112, and data migration is performed from the mapping volume 130 (the volume in which the data VM volume 129 is virtualized) to the target volume 114. Thus, the data placement of the target volume 114 is interpretable by the computer instance 108 .

[0095] Furthermore, the volume migrated by the cloud migration tool 190 is a unit recognized by the computer VM 121. Therefore, even if multiple data VM volumes 127 exist in the volume 814, migration to the cloud storage service 109 is possible in VM volume units. In other words, some of the multiple data VM volumes 127 in one volume 814 can be migrated to the second storage system 112 via the cloud storage service 109. In other words, the remaining data VM volumes 127 of the multiple data VM volumes 127 in one volume 814 can be excluded from the migration target.

[0096] In addition, during the migration, an area of ​​the cloud storage service 109 is used as a data VM volume (intermediate volume) 129. However, unlike on-premise, which has resource constraints, the cloud has surplus resources, so the fact that the cloud needs capacity for the data VM volume (intermediate volume) 129 is not actually a problem. [Third embodiment]

[0097] Fig. 12 shows an overview of system migration according to the third embodiment. Note that, due to space limitations, the information processing system 105 is omitted from Fig. 12.

[0098] In the third embodiment, virtualization is performed at a layer different from that in the second embodiment. That is, in the second embodiment, virtualization is performed in the hypervisor 120, but in the third embodiment, virtualization is performed in the OS (Operating System) of the computer 101. For example, an LVM (Logical Volume Manager) is executed in the computer 101. The LVM is an example of an element that performs virtualization. A volume in the first storage system 102 that is recognized by the computer 101 is virtualized by the function of the LVM.

[0099] According to LVM, volumes in the first storage system 102 include physical volumes (PV) and logical volumes (LV).

[0100] A physical volume is all or a part of the storage space provided by a physical storage device. In other words, one or more physical volumes are provided from a physical storage device. In the example shown in FIG. 12, there are multiple physical volumes 145, 146, 147, and 148.

[0101] 12, volumes 71 and 72 are volumes that are units recognized by the storage system. For example, if volume 71 is recognized as "sdb" by computer 101, physical volumes 145 and 146 are storage spaces (devices) "sdb1" and "sdb2" obtained by partitioning volume 71. These physical volumes 145 and 146 are used for LVM.

[0102] A volume group (VG) is generated by the LVM as a collection of one or more physical volumes. In the example shown in Fig. 12, a volume group 12 is generated from physical volumes 145 to 148.

[0103] A logical volume is all or a part of the storage space of a volume group. In other words, one or more logical volumes are provided from a volume group by the LVM. In the example shown in Figure 12, logical volumes 143 and 144 are provided from the volume group 12.

[0104] In this embodiment, the computer 101 is a physical computer, but may be the computer VM described above. That is, the third embodiment may be combined with the second embodiment. The computer 101 recognizes the logical volumes 143 and 144, respectively.

[0105] According to the comparative example, when migrating a logical volume, the following processes are performed: I / O to the mount points of the logical volumes 143 and 144 is stopped in the first storage system 102, the mount points of the logical volumes 143 and 144 are unmounted from the first storage system 102, the volume group 12 is disabled, the volume group 12 is exported, the volumes 71 and 72 constituting the exported volume group are migrated between storage systems in units of volumes (migration using the above-mentioned remote copy function), the volume group 12 is imported into the second storage system 112 (the configuration of the volume group 12 composed of the migrated volumes 71 and 72), the volume group 12 is enabled, the logical volumes 143 and 144 are mounted, and I / O to the logical volumes 143 and 144 is started. In this case, the I / O stop time is a problem.

[0106] Furthermore, according to the comparative example, volumes are migrated in units of volumes 71 and 72. In other words, migration cannot be performed in units of logical volumes.

[0107] In this embodiment, the volume migrated by the cloud migration tool 190 is a unit recognized by the computer 101. For this reason, even if multiple logical volumes are provided from the volume group 12, migration to the cloud storage service 109 is possible in logical volume units. In other words, some of the multiple logical volumes provided from one volume group 12 can be migrated to the second storage system 112 via the cloud storage service 109. In other words, the remaining logical volumes of the multiple logical volumes provided from one volume group 12 can be excluded from the migration target.

[0108] Furthermore, in this embodiment, migration can be performed in logical volume units, so there is no need to suspend I / O.

[0109] According to the example shown in FIG. 12, the following transitions are made: The logical volume 143 is migrated to the cloud storage service 109 as an intermediate volume 1149, a mapping volume 1151 which is a virtualized volume of the intermediate volume 1149 is created, and data is migrated from the mapping volume 1151 which has been brought online to the target volume 1152. The logical volume 144 is migrated to the cloud storage service 109 as an intermediate volume 1150, a mapping volume 1153 which is a virtualized volume of the intermediate volume 1150 is created, and data is migrated from the mapping volume 1153 which has been brought online to the target volume 1154. [Fourth embodiment]

[0110] FIG. 13 shows an overview of system migration according to the fourth embodiment.

[0111] In the fourth embodiment, the second storage system 1302 is a storage system in the near-cloud environment 160. The "near-cloud environment" is an environment (e.g., a data center) connected to the cloud environment 106 via a dedicated line (e.g., a high-speed line), and therefore, for convenience, the name "near-cloud" is adopted in the description of this embodiment. The present invention can also be applied to such a second storage system 1302. [Fifth embodiment]

[0112] FIG. 14 shows an overview of system migration according to the fifth embodiment.

[0113] In the fifth embodiment, the data volume 104 of the on-premise environment 100 is migrated to the second storage system 1302 of the near cloud environment 160 without using an intermediate volume. The timing of I / O start of the computer instance 108 may be managed using the computer migration management information and volume migration management information described above.

[0114] In this embodiment, migration from the source volume (data volume) 104 of the first storage system 102 to the target volume 114 of the second storage system 1302 is realized without a function of remotely copying data from the first storage system 102 to the second storage system 1302. Therefore, even if the first storage system 102 does not have compatibility with the second storage system 1302, the data volume 104 in the first storage system 102 can be migrated to the second storage system 1302, which has better reliability or functions than the default cloud storage service 109. In addition, since the data volume 104 of the on-premise environment 100 is migrated to the second storage system 1302 of the near cloud environment 160 without going through an intermediate volume, it is expected to shorten the migration time and improve the reliability. [Sixth embodiment]

[0115] FIG. 15 shows an overview of system migration according to the sixth embodiment.

[0116] In a sixth embodiment, the data volume 104 of the on-premise environment 100 is migrated to the second storage system 112 of the cloud environment 106 without using an intermediate volume. The timing of I / O start of the computer instance 108 may be managed using the computer migration management information and volume migration management information described above.

[0117] In this embodiment as well, the same effects as in the fifth embodiment can be expected. [Seventh embodiment]

[0118] Fig. 16 shows an overview of system migration according to the seventh embodiment. Note that, due to space limitations, the on-premise environment 100, the cloud migration tool 190, and the information processing system 105 are omitted from Fig. 16.

[0119] In the seventh embodiment, when migrating data of the second storage system 112 to the target volume 114, the second storage system 112 adds storage control-oriented data 116 to the data to be migrated to the target volume 114 (data to be migrated to the target volume 114), and redundantly stores the data to be migrated and the added storage control-oriented data 116. For example, the second storage system 112 creates a redundant volume 115 for the target volume 114. Redundant data (e.g., replicated data) of the data in the target volume 114 and the storage control-oriented data 116 is stored in the redundant volume 115. Note that the "data to be migrated" in this paragraph may be all data to be migrated to the target volume 114, or may be data in units of a predetermined size.

[0120] The storage control data 116 is data used for control in the second storage system 112. An example of the storage control data 116 is a consistency check code. The consistency check code is a value that is added to data in order to detect whether or not there is a loss or error in the data when the data is transferred, stored, or read. The consistency check code is, for example, an ECC (Error Correcting Code).

[0121] Instead of or in addition to the consistency check code, management data for implementing storage functions (eg, thin provisioning, hierarchical control, snapshots, compression, deduplication, remote copy, etc.) may be added as storage control data 116.

[0122] 16 shows an example of redundant storage in which the data of the target volume 114 is duplicated, but the redundancy may be tripled or more, or erasure coding may be used. The size of the redundant volume 115 may be different from that of the target volume 114.

[0123] FIG. 17 shows the configuration of the second storage system 112.

[0124] The second storage system 112 has some computer instances 1702 provided from the cloud computer service 107, and some volumes 1701 (shown as "VOL" in FIG. 17) provided from the cloud storage service 109. There are multiple computer instances 1702 (or one). The computer instances 1702 in the second storage system 112 have control software 1750, but no applications may be running (on the other hand, the migrated computer instance may have an application). There are multiple volumes 1701 (or one).

[0125] 17 is an example, and the number of computer instances 1702 and the number of volumes 1701 may be different from those shown in the figure. In addition, the second storage system 112 may be composed of only computer instances 1702, or may have other components provided by the cloud environment 106.

[0126] Control software 1750 runs on a computer instance 1702. The control software 1750 forms a storage pool 1700 by using a volume 1701 in the second storage system 112. The storage pool 1700 may be a logical space (address space) based on a plurality of volumes 1701 (or one).

[0127] Furthermore, the control software 1750 uses the storage pool 1700 to create the target volume 114 and the redundant volume 115. In preparation for failure, the target volume 114 and the redundant volume 115 are managed by different computer instances 1702. Specifically, the control software 1750 of the first computer instance 1702 may manage the target volume 114 associated with the storage pool 1700. The control software 1750 of the second computer instance 1702 may manage the redundant volume 115 associated with the storage pool 1700. The second computer instance 1702 is a computer instance different from the first computer instance 108. This allows I / O to be continued to the volume 114 or 115 managed by the remaining computer instance of the first and second computer instances 1702 even if a failure occurs in either the first or second computer instance 1702.

[0128] Any one of the multiple computer instances 1702 may be a master, and the control software 1750 of the master computer instance 1702 (hereinafter, the master control software 1750) may issue instructions to control software 1750 other than the master control software 1750 (control software 1750 of computer instances 1702 other than the master computer instance 1702). The master control software 1750 and the control software 1750 that has received instructions from the master control software 1750 may form a storage pool 1700, create a target volume 114 in the first computer instance 1702, or create a redundant volume 115 of the target volume 114 in the second computer instance 1702, either independently or in cooperation with each other.

[0129] [Eighth embodiment]

[0130] Next, an eighth embodiment will be described. The eighth embodiment is an embodiment in which different migration methods are used depending on the compatibility of the migration source and migration destination storage systems. The system configuration of the eighth embodiment can be the same as that of the first to seventh embodiments or prior art documents.

[0131] FIG. 18 shows the flow of processing carried out in the eighth embodiment.

[0132] In the eighth embodiment, first, it is checked whether the first storage system 102, which is the migration source, and the second storage system 112, which is the migration destination, are compatible (S1801). This check may be performed, for example, by any of the following methods. The information processing system 105 (e.g., the migration control unit 153) may collect system information (e.g., information indicating the vendor and model of the storage system) from each of the first and second storage systems 102 and 112, and determine whether the system information of the first storage system 102 and the system information of the second storage system 112 satisfy the compatibility rules indicated by the compatibility rule information. The compatibility rule information may be stored in the storage device 52 of the information processing system 105. Information indicating the presence or absence of compatibility may be input in advance to the information processing system 105 by a user who has checked the presence or absence of compatibility, and stored in the storage device 52. Based on the information, the information processing system 105 (for example, the migration control unit 153) performs S1801.

[0133] If the investigation shows that there is compatibility (S1802: Yes), the data volume is directly migrated from the first storage system 102, which is the migration source, to the second storage system 112, which is the migration destination, without going through the cloud storage service 109 (S1803). In other words, if there is compatibility, migration can be performed using a method described in the prior art document.

[0134] If the investigation shows that there is no compatibility (S1802: No), the data volume is migrated from the first storage system 102, which is the migration source, to the second storage system 112, which is the migration destination, via the cloud storage service 109 (S1804). That is, the data volume is migrated in the manner described in the first to seventh embodiments. In the manner of the fifth or sixth embodiment, the data volume may be migrated without going through the cloud storage service 109.

[0135] According to this embodiment, it is possible to check the compatibility of the migration source and migration destination storage systems and select an appropriate migration method.

[0136] Although several embodiments have been described above, these are merely examples for explaining the present invention, and the scope of the present invention is not limited to these embodiments. For example, any two or more of the first to seventh embodiments described above may be combined. Also, a part or all of the processing in response to an instruction from the information processing system 105 may be executed manually without going through an instruction from the information processing system 105. Also, the "cloud storage service" may be called "cloud storage" or "cloud storage system."

[0137] Also, in the above description, the volume to be migrated is a logical volume. Data stored in the logical volume (data stored in the physical volume) is also moved, in principle, along with the logical volume between the physical volumes (drives) of the first storage system, the cloud storage service, and the second storage system. During data migration, a portion of the data temporarily exists in the migration source and the remaining data exists in the migration destination. For this reason, for example, when the I / O request is a read request, data is read from the one of the migration source and migration destination where the data to be read exists. Also, for example, when the I / O request is a write request, data may be written to both the migration source and migration destination. This allows access to the data even during migration.

[0138] Moreover, the above description can be summarized, for example, as follows. The following summary may include supplementary and modified explanations of the above description.

[0139] An information processing system 105 is constructed that has a processor 53 and is capable of communicating with a cloud computer, a first storage system 102, and a second storage system 112. When a computer instance 108 as the computer 101 is migrated to the cloud computer and data used by the computer instance 108 is migrated from the first storage system 102 to the second storage system 112, the information processing system 105 performs the following (A) and (B). (A) A system volume 103 storing an image of an OS (Operating System) for configuring a computer instance to be migrated, and a data volume 104 storing data used by the OS, are migrated from a first storage system 102 to a cloud computer using a migration tool 190 of the cloud computer. (B) A mapping volume 113 is created in the second storage system 112, which is mapped to the intermediate volume 111, which is a data volume migrated to the cloud computer by the migration tool 190, and a data input / output path from the computer instance 108 to the mapping volume 113 is set in the computer instance 108.

[0140] (A) is performed by the tool operation unit 151. (B) is performed by the migration control unit 153. In (B), for example, a path is set by the computer instance 108 based on an instruction issued from the migration control unit 153. At least one of (A) and (B) may be performed in response to a manual instruction to the information processing system 105, or may be performed automatically without such an instruction.

[0141] The information processing system 105 may further include a migration completion confirmation unit 152 that confirms that the migration by the migration tool 190 has been completed. The migration control unit 153 may create a mapping volume 113 in the second storage system 112 after the completion of the migration by the migration tool 190 has been confirmed.

[0142] The migration tool 190 may be configured to migrate the data volume 104 to the cloud computer in a data arrangement that can be interpreted by the computer instance 108. The second storage system 112 may map the intermediate volume 111, which is a data volume in the data arrangement that can be interpreted by the computer instance 108, to a mapping volume 113 in the second storage system. The migration tool 190 may also be configured to convert the data arrangement into one that can be interpreted by the computer instance 108 and migrate the data volume 104 to the cloud computer.

[0143] The migration control unit 153 may migrate data from the mapping volume 113 of the second storage system 112 to the target volume 114 in the second storage system 112, and set a path to the target volume 114 instead of setting a path from the computer instance 108 to the mapping volume 113.

[0144] After completing the data migration from the mapping volume 113 to the target volume 114 in the second storage system 112, the migration control unit 153 may delete the intermediate volume 111 from the cloud computer.

[0145] A computer instance may use multiple data volumes at the migration source. The tool operation unit 151 may specify multiple data volumes used by the computer instance as migration targets (e.g., to the migration tool 190). For each specified data volume, it may be migrated to the cloud computer and a mapping volume may be created.

[0146] The migration control unit 153 may determine, from among a plurality of external connection methods, an external connection method that corresponds to the cloud computer in which the data volume (intermediate volume 111) resides, execute the external connection, which is to associate the data volume (intermediate volume 111) with the second storage system, in accordance with the determined external connection method, and create a mapping volume 113 in the second storage system 112 for the data volume (intermediate volume 111) of the cloud computer to which the external connection has been made.

[0147] The migration control unit 153 may determine whether or not both the cloud computer and the second storage system 112 support a multipath function. If the result of the determination is true, the migration control unit 153 may add a path connecting the computer instance 108 and the mapping volume 113, and thereafter, if there is a path connecting the data volume (intermediate volume 111) and the computer instance 108, delete the path. If the result of the determination is false, the migration control unit 153 may delete the path connecting the data volume (intermediate volume 111) and the computer instance 108, and thereafter, add a path connecting the computer instance 108 and the mapping volume 113. Note that the migration control unit 153 may bring the path to the mapping volume 113 into an online state without bringing the path to the data volume (intermediate volume 111) into an online state.

[0148] Before migration, the computer instance may run on a virtual computer (e.g., computer VM 121) generated by a hypervisor 120 executed by a physical computer (e.g., computer 101). The data volume recognized by the computer instance may be a volume stored in a virtual disk, which is a data store 123 created by the hypervisor 120, and may be a volume recognized by the virtual computer. Data placement in the data volume may be data placement for the hypervisor 120. The migration tool 190 may convert the data placement in the data volume into a data placement that can be interpreted by the computer instance, and migrate the data volume to the cloud computer.

[0149] A computer instance may manage one or more logical volumes constituting a volume group 12 for the first storage system 122. A volume group may be one logical space composed of multiple physical volumes of the first storage system 102. Each of the multiple physical volumes may be a logical space. A data volume recognized by a computer instance may be a logical volume recognized by the computer instance.

[0150] The cloud computer may have a computing function and a storage function and may be provided as a cloud service. The computing function may be a function as a cloud computer service 107. The storage function may be a function as a cloud storage service 109. The second storage system 112 may be a storage service in a cloud environment different from the cloud environment of the cloud service. Also, the second storage system 112 may be a storage system connected to the cloud computer of the cloud service.

[0151] In addition, instead of or in addition to the information processing system 105, an information processing system including a cloud computer, a first storage system 102, and a second storage system 112 may be constructed. The cloud computer may have a compute function and a storage function. When a computer instance is migrated to the cloud computer and data used by the computer instance is migrated from the first storage system 102 to the second storage system 112, a migration tool 190 of the cloud computer may migrate a system volume in which an image of an OS (Operating System) for operating the computer instance to be migrated by the compute function is stored, and a data volume in which data used by the OS is stored, from the first storage system 102 to the storage function of the cloud computer. The second storage system may cause the second storage system 112 to create a mapping volume 130 that is mapped to the data volume (intermediate volume 111) migrated to the cloud computer by the cloud computer's migration tool 190, and set up a data input / output path from the computer instance 108 to the mapping volume 130 in the computer instance 108. [Explanation of symbols]

[0152] 105...Information processing systems

Claims

1. an interface device capable of communicating with a cloud computer, a cloud storage, a first storage system, and a second storage system; a processor connected to the interface device; Equipped with There is no compatibility between the first storage system and the second storage system, The processor, Migrate the computing instance to a cloud computing system; Migrating a system volume of the computer instance to the cloud storage; migrate a data volume storing data used by the computer instance from the first storage system to the cloud storage by converting a first data arrangement, which is a data arrangement in the data volume in the first storage system and is interpretable by the computer instance before the migration, into a second data arrangement, which is a data arrangement in the data volume in the cloud storage and is interpretable by the computer instance after the migration; Copying data of the migrated data volume in the cloud storage to a target volume in the second storage system; setting a path for data input / output from the computer instance to the target volume in the computer instance after migration; Information processing system.

2. The processor causes the second storage system to create a mapping volume that is mapped to the migrated data volume in the cloud storage, and causes data of the migrated data volume in the cloud storage to be copied to the target volume in the second storage system through the mapping volume in the second storage system. The information processing system according to claim 1 .

3. The processor creates the mapping volume in the second storage system after confirming that a migration by a cloud migration tool that migrates the computer instance to the cloud computer and migrates the system volume and the data volume to the cloud storage is completed. The information processing system according to claim 2 .

4. The processor sets a path for data input / output from the computer instance to the mapping volume in the computer instance after migration. The information processing system according to claim 3 .

5. after copying data to the target volume, the processor sets the path from the migrated computer instance to the target volume instead of the path from the migrated computer instance to the mapping volume, 5. The information processing system according to claim 4.

6. The processor causes the migrated data volume in the cloud storage to be deleted from the cloud storage after copying the data to the target volume. The information processing system according to claim 1 .

7. The computer instance uses multiple data volumes, The processor, Specifying a plurality of data volumes used by the computer instance as migration targets; migrates, for each of the specified data volumes, the data volume to the cloud storage, and creates, in the second storage system, the mapping volume that is mapped to the data volume; The information processing system according to claim 2 .

8. The processor determines, from among a plurality of external connection methods, an external connection method corresponding to the cloud storage in which the migrated data volume exists, executes an external connection that is to map the migrated data volume to the second storage system in accordance with the determined external connection method, and creates, in the second storage system, the mapping volume for the migrated data volume of the cloud storage to which the external connection has been made. The information processing system according to claim 2 .

9. The processor, Determining whether the cloud storage and the second storage system both support a multipath function; If the result of the determination is true, a path is added that connects the computer instance after the migration and the mapping volume, and then, if there is a path that connects the data volume after the migration and the computer instance, the path is deleted; If the result of the determination is false, delete the path connecting the post-migration data volume and the post-migration computer instance, and then add a path connecting the post-migration computer instance and the mapping volume. The information processing system according to claim 2 .

10. The processor sets a path to the mapping volume in an online state without setting a path to the migrated data volume in an online state. The information processing system according to claim 9.

11. Before the migration, the computer instance is running on a virtual computer generated by a hypervisor executed by a physical computer; The data volume recognized by the computer instance is a volume stored in a virtual disk that is a data store created by the hypervisor, and is a volume recognized by the virtual computer, The first data arrangement is a data arrangement for the hypervisor. The information processing system according to claim 1 .

12. The computer instance manages one or more logical volumes constituting a volume group for a first storage system; The volume group is a single logical space configured from a plurality of physical volumes of the first storage system, each of the plurality of physical volumes is a logical space; The data volume recognized by the computer instance is a logical volume recognized by the computer instance. The information processing system according to claim 1 .

13. The second storage system, adding storage control data, which is data used in controlling the second storage system, to the data to be migrated to the target volume in the second storage system; The data to be migrated and the data for storage control are redundantly stored; The information processing system according to claim 1 .

14. The redundant storage of the data to be migrated and the data for storage control is a creation of a redundant volume of the target volume, the plurality of computer instances that are components of the second storage system are computer instances provided by the cloud computer; a computer instance that manages the redundant volume is a computer instance different from a computer instance that manages the target volume; The information processing system according to claim 13.

15. The system volume is a volume in which an image of an OS (Operating System) for configuring the computer instance is stored. The information processing system according to claim 1 .

16. Migrating a computer instance to a cloud computer; Migrating a system volume of the computer instance to cloud storage; migrate a data volume storing data used by the computer instance from a first storage system to the cloud storage by converting a first data arrangement, which is a data arrangement in the data volume in the first storage system and is interpretable by the computer instance before the migration, into a second data arrangement, which is a data arrangement in the data volume in the cloud storage and is interpretable by the computer instance after the migration; Copying data of the migrated data volume in the cloud storage to a target volume in a second storage system that is incompatible with the first storage system; setting a path for data input / output from the computer instance to the target volume in the computer instance after migration; An information processing method performed by a computer.

Images