JP7413458B2 - Information processing system and method - Google Patents

Description

TECHNICAL FIELD The present invention relates generally to information processing, and, for example, to support migration of computers and volumes.

Migrate computers that use volumes in the first storage system (for example, on-premises storage system) and volumes used by the computer (volumes in the first storage system) to a cloud environment (mainly public cloud environment) There are known techniques to do this. According to this type of technology, migration of computers and volumes to a cloud environment is performed using a cloud migration tool. A cloud migration tool is a system typically provided by a cloud environment vendor.

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 that the cloud computer service has access to (typically a cloud storage service provided by the vendor of the cloud environment). will be migrated.

The volumes used by the computer include the system volume (also called the startup volume), which is the volume that stores the image of the computer's OS (Operating System), and the volume that stores the data input and output by the computer. There is a data volume.

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 that is more reliable or capable than the default cloud storage service. Specifically, for example, the second storage system is a cloud storage service in the same cloud environment, but is a cloud storage service developed by a storage vendor rather than a vendor of the cloud environment.

According to the technology disclosed in Non-Patent Document 1, the data volume migration destination is not the default cloud storage service but the second storage provided by the storage vendor of the first storage system (migration source storage system). It can be a cloud storage service as a system (transition destination storage system). Cloud migration tools are not used to migrate data volumes from a first storage system to a second storage system; rather, proprietary tools provided by the storage vendor in question are used to migrate volumes between storage systems. A so-called remote copy function is used.

According to the technology disclosed in Non-Patent Document 2, in an on-premises environment, a virtual machine in a virtual environment such as a hypervisor recognizes a volume (hereinafter referred to as a storage volume) in an on-premises storage system. The format of the storage volume follows the virtual environment. A virtual machine executes an application, and the storage volume includes a volume for each application in the virtual machine. Volumes for each application are migrated from an on-premises storage system to a cloud storage system provided by the same vendor as the storage system vendor. In the above migration, the format of the storage volume in the on-premises environment follows the virtual environment of the on-premises environment, so the data storage format of the storage volume is converted in advance in the on-premises environment before the storage volume is migrated to the cloud storage system. .

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 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

However, in the technology disclosed in Non-Patent Document 1, the first storage system as the migration source of the data volume to be migrated to the second storage system is limited to a storage system that is compatible with the second storage system. . Examples of storage systems that are incompatible 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 that is provided by the storage vendor of the second storage system, but whose type (for example, model) is different from that of the second storage system.

The technique disclosed in Non-Patent Document 2 also has the above-mentioned problem because migration is performed between storage systems of the same vendor. Even when migrating between storage systems of the same vendor, the technology disclosed in Non-Patent Document 2 requires on-premises It is necessary to prepare a volume in the storage system that does not depend on the format of the virtual environment, and copy data from the volume within the storage volume to the volume. For this reason, in an on-premises storage system, storage resources for volumes (copy destination volumes) that do not depend on the format of the virtual environment are required for each application.

An information processing system capable of communicating with a cloud computer, a first storage system, and a second storage system is constructed. When migrating a computer instance to a cloud computer and migrating data used by the computer instance from a first storage system to a second storage system, the information processing system uses the OS (OS) for configuring the computer instance to be migrated. A system volume in which an image of an operating system (OS) is stored and a data volume in which data used by the OS are stored are migrated from the first storage system to a cloud computer using a migration tool of the cloud computer. The information processing system causes the second storage system to create a mapping volume that is mapped to the data volume migrated to the cloud computer using the cloud computer migration tool, and creates a data input/output path from the computer instance to the mapping volume to the computer instance. Let it be set.

Even if the first storage system is not compatible with a second storage system that is different from the default cloud storage service that is accessible by the cloud computer service to which the computer instance is being migrated, the migration target is transferred to the first storage system. A volume in a first storage system can be migrated to a second storage system without preparing a copy destination volume for the volume.

An overview of system migration according to the first embodiment is shown. The configuration of the cloud environment after completion of cloud migration processing is shown. The configuration of the cloud environment after creating the mapping volume is shown. Shows the migration of data from a mapping volume to a target volume. The flow of system migration processing is shown. The flow of migration processing is shown. The flow of the start process of cloud migration process is shown. The flow of the process for confirming completion of cloud migration process is shown. The flow of the process for determining an external connection method is shown. The flow of path switching processing is shown. An overview of system migration according to the second embodiment is shown. An overview of system migration according to the third embodiment is shown. An overview of system migration according to the fourth embodiment is shown. An overview of system migration according to the fifth embodiment is shown. An overview of system migration according to the sixth embodiment is shown. An overview of system migration according to the seventh embodiment is shown. 7 shows the configuration of a second storage system according to a seventh embodiment. The flow of processing performed in the eighth embodiment is shown.

In the following description, an "interface device" 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 device is an interface device for at least one of an I/O device and a remote display computer. The I/O interface device for the display computer may be a communication interface device. The at least one I/O device may be a user interface device, eg, 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 communication interface devices of the same type (for example, one or more NICs (Network Interface Cards)) or two or more communication interface devices of different types (for example, one or more NICs). It may also be an HBA (Host Bus Adapter).

Also, in the following description, "memory" refers to one or more memory devices that are an example of one or more storage devices, and may typically be a main storage device. At least one memory device in the memory may be a volatile memory device or a non-volatile memory device.

Also, in the following description, "persistent storage" may be one or more persistent storage devices, which is an example of one or more storage devices. Persistent storage devices typically may be non-volatile storage devices (e.g. auxiliary storage devices), and specifically include, for example, HDDs (Hard Disk Drives), SSDs (Solid State Drives), NVMEs (Non-Volatile Memory Express) drive or SCM (Storage Class Memory).

Furthermore, in the following description, a "storage device" may be at least a memory and a persistent storage device.

Also, in the following discussion, a "processor" may refer to 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 another type of processor device such as a GPU (Graphics Processing Unit). At least one processor device may be single-core or multi-core. The at least one processor device may be a processor core. At least one processor device is a circuit that is a collection of gate arrays (for example, FPGA (Field-Programmable Gate Array), CPLD (Complex Programmable Logic Device), or ASIC (Application A processor device in a broad sense such as a specific integrated circuit (specific integrated circuit) may also be used.

In addition, in the following explanation, functions may be explained using the expression "yyy part", but functions may be realized by one or more computer programs being executed by a processor, or one or more computer programs may be executed by a processor. It may be realized by the above hardware circuit (for example, FPGA or ASIC), or a combination thereof. When a function is realized by a program being executed by a processor, the specified processing is performed using a storage device and/or an interface device as appropriate, so the function may be implemented as at least a part of the processor. good. A process described using a function as a subject may be a process performed by a processor or a device having the processor.

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

Moreover, arbitrary information (for example, at least one of "ID", "name", and "number") may be employed as information for identifying an element.

Furthermore, in the following description, a "volume" may be a logical storage space (address space). The volume may be a substantial volume (a volume based on a physical storage device (for example, a persistent storage device)) or a virtual volume.

Hereinafter, some embodiments of the present invention will be described using the drawings. Note that in the drawings, "volume" is written as "VOL". Further, volume migration means migration of data stored in a volume.
[First embodiment]

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

The migration source environment is the on-premises environment 100. The computer system in the on-premises 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. There may be at least a plurality of computers 101 among the computers 101 and the first storage system 102. Multiple volumes may exist in the first storage system 102.

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

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

The cloud environment 106 is an environment (for example, a cloud platform) provided by a cloud vendor, and the cloud computer service 107 and cloud storage service 109 may be cloud computing services provided by the cloud vendor. For example, the cloud computer service 107 may be Amazon EC2 (Amazon Elastic Compute Cloud), and the cloud storage service 109 may be Amazon EBS (Amazon Elastic Block Store) ("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.

Migration of computers and volumes in an environment other than the cloud environment 106 (for example, the on-premises environment 100 or a cloud environment different from the cloud environment 106) to the cloud environment 106 is performed by the cloud migration tool 190. That is, in this embodiment, the migration target is migrated from the on-premises 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. Cloud migration tool 190 is a system (feature) typically provided by the vendor of cloud environment 106.

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. Information processing system 105 may also be called a management system. The information processing system 105 may be located outside the on-premises environment 100 and the cloud environment 106 as illustrated, or may be located in either the on-premises environment 100 or the cloud environment 106. Although the information processing system 105 is a physical system (for example, a computer) in this embodiment, it may be a logical system provided on physical computing resources. The information processing system 105 connects a computer 101, a first storage system 102, a cloud migration tool 190, a cloud computer service 107, a computer instance 108, a cloud storage service 109, and a second computer via communication media such as a network or a dedicated line. At least one of the storage systems 112 can be operated. 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).

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

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

A storage device 52 stores programs and information. The information includes management information 140, for example. The management information 140 is information that is referenced or updated as appropriate for system migration processing (see FIG. 5) by the information processing system 105. The management information 140 may include information representing the progress of the system migration process, and may include, for example, the following information (a) to (c).
(a) Computer migration management information that is information regarding a computer to be migrated from the on-premises environment 100 to the cloud environment 106. The computer migration management information includes, for example, for each computer to be migrated, identification information of the computer and information indicating the migration status of the computer (for example, migration not yet started, migration started, or migration completed).
(b) Volume migration management information that is information regarding volumes to be migrated from the on-premises environment 100 to the cloud environment 106. The volume migration management information includes, for example, for each volume to be migrated, identification information of the volume and information indicating the migration status of the volume (for example, migration not yet started, migration started, or migration completed).
(c) Intermediate volume management information that is information regarding an intermediate volume 111 (described later) in the cloud storage service 109. For example, the intermediate volume management information includes, for each intermediate volume 111, the identification information of the intermediate volume 111 and the transition status of the intermediate volume 111 (for example, waiting for creation, completion of creation, start of migration, completion of migration, start of deletion, or completion of deletion). The intermediate volume 111 includes identification information of the mapping volume 113, which is a virtualized volume, and identification information of the target volume 114, which is the migration destination of the mapping volume 113.

When the processor 53 executes the program, functions such as the tool operation section 151, migration completion confirmation section 152, and migration control section 153 are realized.

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 broken line 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 the computer 101. The data volume 104 is a volume in which data input and output by the computer 101 (for example, an application executed on the computer 101) after startup is stored.

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

In this embodiment, system migration processing for migrating computers and volumes from the on-premises environment 100 to the cloud environment 106 is performed according to the following flow.

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 way as the data volume 104, or if the computer 101 is specified, the system volume 103 may be specified. may be considered to have been designated as a migration target. In any case, in this example, the illustrated computer 101, system volume 103, and data volume 104 are to be migrated. Note that the data volume 104 to be migrated in S11 is specified by applying another means, such as deleting (detaching) the data volume 104 that is not to be migrated from the computer 101 before issuing the migration instruction to the cloud migration tool 190. It's okay.

In response to the migration instruction, the cloud migration tool 190 performs cloud migration processing including migration of the computer 101, system volume 103, and 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, migrates from the volume 103 to the volume 110). Further, the cloud migration tool 190 migrates the data volume 104 as an intermediate volume 111 to the cloud storage service 109 (specifically, for example, migrates from the volume 104 to the volume 111). The intermediate volume 111 is a volume that has been migrated from the data volume 104 to the cloud storage service 109.

The migration completion confirmation unit 152 confirms that the cloud migration process described above has been completed by the cloud migration tool 190 in response to the 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 is started by referring to the system volume 110 (for example, reads the OS image).

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 virtualized volume of the intermediate volume 111, in the second storage system 112, and Data is migrated from the mapping volume 113, which is in an online state where I/O can be performed from the instance 108, to the target volume 114. Note that one volume may serve as both the mapping volume 113 and the target volume 114.

Specifically, for example, the migration control unit 153 causes the second storage system 112 to perform an external connection that associates 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.

Thereafter, the migration control unit 153 causes a mapping volume 113, which is a volume in which the externally connected intermediate volume 111 is virtualized (a volume to which the intermediate volume 111 is mapped), to be created in the second storage system 112. When the mapping volume 113 is created, the migration control unit 153 brings the mapping volume 113 into an online state where 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 The second storage system 112 starts accepting I/O requests specifying the 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 that has received the permission performs mapping as appropriate according to the processing of the computer instance 108. An I/O request specifying the volume 113 may be sent to the second storage system 112.

The migration control unit 153 causes the second storage system 112 to migrate data from the mapping volume 113 to the target volume 114 (S13). As a result, data is migrated 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 completed, I/O of data 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).

According to the above system migration process, the remote copy function of data from the first storage system 102 to the second storage system 112 (for example, remote copy in units of volumes (volumes recognized by the storage system) between storage systems) 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 achieved without the need for the ability to perform Therefore, even if the first storage system 102 is not compatible with the second storage system 112, data volumes 104 in the first storage system 102 can be stored more reliably than the default cloud storage service 109. Alternatively, it is possible to migrate to the second storage system 112, which is a cloud storage service with superior functionality. Note that the second storage system 112 may exist in an environment different from the cloud environment 106 (eg, another cloud environment).

Note that, according to the example shown in FIG. 1, the volume targeted for migration to the second storage system 112 is the data volume 104, but the system volume 103 is also targeted for migration to the second storage system 112. May be targeted. In other words, the system volume 110 is 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 be a system volume migrated to the second storage system 112.

Furthermore, if there are multiple data volumes 104 as data volumes recognized by the computer 101, all or some of the multiple data volumes 104 may be migrated to the second storage system 112. may be done.

Hereinafter, with reference to FIGS. 2 to 4, the above description regarding the system migration process will be supplemented.

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

When the cloud migration process is completed by the cloud migration tool 190, the intermediate volume 111 is also connected to the computer instance 108 in addition to the system volume 110. In other words, a path is created that connects the computer instance 108 and the intermediate volume 111 (see the broken line arrow extending from the computer instance 108 to the intermediate volume 111). At this time, I/O by the computer instance 108 to the intermediate volume 111 may be started.

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 transition control unit 153 may perform at least one of the following.
- The computer instance 108 is not allowed to issue an I/O request that specifies the intermediate volume 111. (For example, the computer instance 108 is prohibited from issuing I/O requests that specify the intermediate volume 111.)
- Prevent the cloud storage service 109 from starting 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.)

FIG. 3 shows the configuration of the cloud environment 106 after the mapping volume 113 is created.

An intermediate volume 111 is externally connected to a second storage system 112. The external connection method depends on the cloud storage service 109 where the intermediate volume 111 exists. A specific example of the external connection method will be described later.

A mapping volume 113, which is a virtualized volume of 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 connecting the computer instance 108 and the mapping volume 113 is established. 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.

If a path connecting the computer instance 108 and the intermediate volume 111 is established, before the path connecting the computer instance 108 and the mapping volume 113 is established, the migration control unit 153 connects the cloud storage service 109 (and/or instance 108) to delete the path (for example, take it offline or delete the path configuration itself). 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, 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 are There may be times when they coexist.

FIG. 4 shows the migration of data from mapping volume 113 to target volume 114.

When 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 target volume 114) (accepting and processing I/O requests that specify the identification information of the mapping volume 113). It is. 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 determines whether the I/O destination volume area (area in the volume) is an area to which data has been migrated.
- 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.

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 that specifies one volume, it determines whether the volume area (for example, LBA (Logical Block Address)) specified in the I/O request is a migrated area. Depending on the situation, the second storage system 112 may perform I/O to the mapping volume 113 or the target volume 114 in accordance with the I/O request.

Further, in the cloud migration process, the identification information of the data volume (source volume) 104 and recognized by the computer 101 may be inherited by the intermediate volume 111. The identification information may be inherited by the mapping volume 113 that is the virtualized intermediate volume 111. The identification information (identification information of the data volume (source volume) 104) inherited by the mapping volume 113 may be recognized by the computer instance 108. During data migration from the mapping volume 113 to the target volume 114, the second storage system 112 may receive an I/O request specifying the identification information from the computer instance 108. After the migration of data from the mapping volume 113 to the target volume 114 is completed, the identification information (identification information of the data volume (source volume) 104) may be inherited by the target volume 114. By taking over the identification information in this manner, after the 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.

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

FIG. 5 shows the flow of system migration processing.

Migration processing (S501) is performed for each migration target (computer and volume) in the migration source environment (in this embodiment, the on-premises environment 100). When all migration targets have been migrated from the migration source environment, the migration source environment may be deleted (S502).

In the system migration process, if 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 the data volume 104 is externally connected to the second storage system 112, and the intermediate volume 111 is connected externally to the second storage system 112. Creation of the mapping volume 113, which is virtualization, and data migration from the mapping volume 113 to the target volume 114 may be performed while the mapping volume 113 is online. In other words, the completion of the cloud migration process may be confirmed for each data volume 104. This can be expected to shorten the time required for system migration processing.

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

A cloud migration process start process (S600) is performed. Specifically, as shown in FIG. 7, the tool operation unit 151 receives designation of the computer 101 and volume to be migrated from a user (for example, an operator of the information processing system 105), and cloud migration processing is started. Specifically, the tool operation unit 151 issues a migration instruction specifying the specified computer 101 and the specified volume to the cloud migration tool 190. In response to the migration instruction, the cloud migration tool 190 starts migrating the specified computer 101 as a computer instance 108 to the cloud computer service 107 (S700), and also transfers the specified volume to the cloud storage service 109. (S701). In this embodiment, all or some of the data volumes 104 out of one or more data volumes 104 recognized by the designated computer 101 are designated. 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 migration target computer 101 are migrated. In S701, the volume in the first storage system 102 may be the migration source, and the 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. Further, 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"). Further, 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 status of the volume is "migration started"). Additionally, the tool operation unit 151 may add information about the intermediate volume 111 as the migration destination to the above-mentioned intermediate volume management information in the management information 140 (the migration status of the intermediate volume is "waiting for creation").

After that, 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 communicates with the cloud migration tool 190 to confirm that the migration of the migration target computer 101 is completed (the computer 101 is migrated to the cloud computer service 107 as the computer instance 108). (S800), and also confirms that migration of the specified volume has been completed (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 state of the computer 101 is changed to "migration completed", the migration state of the volume is changed to "migration completed", and the migration state of the intermediate volume 111 is changed to "created"). (may be updated to "Completed" respectively).

After confirming the completion of the cloud migration process, the migration control unit 153 may place the intermediate volume 111 in an online state (S602). Specifically, for example, the cloud migration tool 190 may establish a path connecting the created intermediate volume 111 and the computer instance 108, and the migration control unit 153 may bring this path into an online state. However, S602 may be optional, and in this embodiment, S602 is not performed.

After confirming the completion of the cloud migration process, 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 placement location of the intermediate volume 111 (S900), and determines an external connection method according to the determined location. The management information 140 includes external connection management information (information that includes identification information for each location (for example, a cloud storage service) where the intermediate volume 111 can be located and information representing an external connection method). Often, the migration control unit 153 may refer to external connection management information and perform S900.

According to the example shown in FIG. 9, when the location is cloud storage service A, the migration control unit 153 transfers the intermediate volume to a predetermined instance in the second storage system 112 using the functions of cloud storage service A. 111 is determined (S901). If the location is cloud storage service B, the migration control unit 153 determines iSCSI connection of the intermediate volume 111 to the second storage system 112 as the external connection method (S902). If the placement location is cloud storage service C, the migration control unit 153 establishes an external connection method that directly attaches the intermediate volume 111 to a predetermined instance in the second storage system 112 using the functions of the cloud storage service C. Determine (S903). In order to virtualize the intermediate volume 111 (create the mapping volume 113), it is necessary to externally connect the intermediate volume 111 to the second storage system 112, but the external connection depends on the location where the intermediate volume 111 is located. Through the process shown in FIG. 9, the intermediate volume 111 can be externally connected to the second storage system 112 using an appropriate external connection method depending on the location of the intermediate volume. Note that in the explanation with reference to FIG. 9, the "placement location" may also be referred to as "the type of cloud environment where the intermediate volume is located" or "the type of cloud storage service where the intermediate volume is located". good.

As shown in FIG. 6, the migration control unit 153 causes the second storage system 112 to perform external connection using the external connection method determined in S603 (S604). Thereby, the second storage system 112 externally connects the intermediate volume 111 to the second storage system 112.

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, which is a virtualized volume of the intermediate volume 111, in the second storage system 112.

Next, path switching processing is performed (S606). Specifically, as shown in FIG. 10, the migration control unit 153 determines whether the computer instance 108, cloud storage service 109, and second storage system 112 all have a multipath function (S1000). . For example, the management information 140 includes 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 determination in S1000 is performed based on the management information 140. It's fine. In addition, "multipath function" means that multiple paths (for example, all of the multiple paths must be online) are allowed for one volume identification information, and one of the multiple paths is selected. This is a function that can be used as An "online path" is a path that can be used to send I/O requests.

If the result of the determination in S1000 is true (S1000: YES), multipath is allowed, so the migration control unit 153 adds a path connecting the computer instance 108 and the mapping volume 113 (for example, if the computer instance 108 and instructs at least one of the second storage systems 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 causes the path connecting the computer instance 108 and the intermediate volume 111 to be deleted (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 via the path connecting the computer instance 108 and the intermediate volume 111 has been started before the path switching process, either the said path or the path added in S1001. I/O may occur via the path. If I/O via the path connecting the computer instance 108 and the intermediate volume 111 has not been started before the path switching process, and if the path is added in S1001, I/O via the path will not be started. , the migration control unit 153 may instruct the computer instance 108 and the second storage system 112. If the path connecting the computer instance 108 and the intermediate volume 111 is not established before the path switching process, S1002 is skipped.

If the result of the determination in S1000 is false (S1000: NO), multipath is not allowed, so the migration control unit 153 deletes the path connecting the computer instance 108 and the intermediate volume 111 (S1003). After that, the migration control unit 153 adds a path connecting the computer instance 108 and the mapping volume 113, and brings the path online (S1004). As a result, a path connecting the computer instance 108 and the mapping volume 113 is added, and I/O via this path is started. Note that if the path connecting the computer instance 108 and the intermediate volume 111 is not established before the path switching process, S1003 is skipped.

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

Furthermore, if multipath is not allowed, S1003 is required before S1004. Therefore, if I/O is started via the path to the intermediate volume 111, processing such as stopping the I/O is required. In this embodiment, since I/O to the intermediate volume 111 is not started, I/O stop processing can be made unnecessary.

Note that if it is known in advance that multipath is allowed (for example, if S1000, S1003, and S1004 are always unnecessary among S1000 to S1004), the process to the intermediate volume 111 before the mapping volume 113 is created. I/O may have been started via the path. This is because I/O stop processing is not necessary.

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). As a result, the second storage system 112 starts migrating data from the mapping volume 113 to the target volume 114. Note that 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 a volume specified by the migration control unit 153 from a plurality of volumes in the second storage system 112. It may be the volume that was created. Furthermore, as described above, if 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 transferred to the mapped volume 113 or the data This is done for the volume 104. I/O to the mapping volume 113 is actually performed to the intermediate volume 111. Further, 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 "start migration").

The migration control unit 153 confirms completion of data migration from the mapping volume 113 to the data volume 104 (S608). For example, the migration control unit 153 receives notification of migration completion 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 complete").

The migration control unit 153 causes the second storage system 112 to perform 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.

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, wasteful consumption of the 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 state of the intermediate volume 111 may be set to "deletion start or deletion completed").

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

Furthermore, after confirming the completion of the cloud migration process, at least a part of a series of processes (for example, 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 executed. For example, a processing logic is provided in the second storage system 112, and the migration control unit 153 specifies necessary parameters (for example, identification information of the intermediate volume, identification information of the target volume 114) to the processing logic. At least a part of the series of processes described above may be automatically performed by giving such an instruction.
[Second embodiment]

A second embodiment will be described. At that time, differences with the first embodiment will be mainly explained, and explanations of common points with the first embodiment will be omitted or simplified. Note that this point also applies to the third embodiment below and other embodiments thereafter.

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

In the on-premises environment 100, a hypervisor 120, which is a system for virtualizing computers, 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.

Examples of volumes provided by the first storage system 102 include volumes 811 and 814.

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

A data store 125 for the hypervisor 120 is also created in the 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. A plurality of 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 viewed from the computer VM121. “Data store” is a storage area for VM volumes.

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

According to the comparative example based on Non-Patent Document 1, the volume 814 is transferred from the first storage system 102 to the second storage system 112 using the remote copy function described above (that is, not via the cloud storage service 109). It is conceivable that there will be a transition. However, if the cloud computer service 107 does not have the same hypervisor 120 as the on-premises environment 100, the data structure such as the data store, VM volume arrangement, and VM volume data arrangement in the volume migrated to the second storage system 112 is interpreted. I don't have the means. 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, it is not possible to perform migration while maintaining a state in which the computer instance 108 can interpret the VM volume.

Furthermore, according to a comparative example based on Non-Patent Document 1, the remote copy function is migrated 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, data VM volume cannot be migrated.

Furthermore, 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-premises environment 100, and then migration is performed using the remote copy function. In changing 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 for which no data store 125 has been created). By changing the data storage format, the data VM volume (copy destination volume) can be interpreted from the computer VM 121 without going through the hypervisor 120. Thereafter, the data VM volume (copy destination volume) is migrated to the second storage system 112 using the remote copy function described above. Since the data VM volume (copy destination volume) can be interpreted from the computer VM 121 without the hypervisor 120 in the on-premises environment 100, even after the data VM volume has been migrated to the second storage system 112, the data VM volume (copy destination volume) can be interpreted from the computer instance 108. It becomes possible to interpret the data VM volumes migrated to the storage system 112 of No. 2. However, when changing the data storage format in the on-premises environment 100, because additional space is used for data copy (additional storage capacity for the copy destination volume is required), there is no free space in the first storage system 102. Migration is not possible if there is not enough space.

In this embodiment, the data VM volume (and 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 within 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 that has been migrated to the cloud storage service 109 of the system VM volume 124 can be interpreted from 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 is migrated from the mapping volume 130 (the volume to which the data VM volume 129 is virtualized) to the target volume 114. . Therefore, the data arrangement of the target volume 114 can be interpreted by the computer instance 108.

Further, the volume migrated by the cloud migration tool 190 is a unit recognized by the computer VM 121. Therefore, even if a plurality of data VM volumes 127 exist in the volume 814, migration to the cloud storage service 109 is possible in units of VM volumes. In other words, some of the data VM volumes 127 among the plurality of 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 among the plurality of data VM volumes 127 in one volume 814 can be excluded from migration targets.

In addition, during the migration, the area of the cloud storage service 109 is used as the data VM volume (intermediate volume) 129, but unlike on-premises, which has resource constraints, the cloud has surplus resources, so the data VM volume (intermediate volume) ) 129 capacity is required in the cloud is not a practical problem.
[Third embodiment]

FIG. 12 shows an overview of system migration according to the third embodiment. Note that due to space constraints, the information processing system 105 is not shown in FIG. 12.

In the third embodiment, virtualization is performed in 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, the computer 101 executes LVM (Logical Volume Manager). LVM is an example of an element that performs virtualization. The volume in the first storage system 102 recognized from the computer 101 is virtualized by the LVM function.

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

A physical volume is all or part of the storage space provided by a physical storage device. That is, one or more physical volumes are provided from a physical storage device. According to the example shown in FIG. 12, there are multiple physical volumes 145, 146, 147 and 148.

According to the example shown in FIG. 12, volumes 71 and 72 are volumes recognized as units 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. ” is. These physical volumes 145 and 146 are used for LVM.

A volume group (VG) is created by LVM as a collection of one or more physical volumes. According to the example shown in FIG. 12, a volume group 12 is created from physical volumes 145 to 148.

A logical volume is all or part of a storage space as a volume group. That is, one or more logical volumes from a volume group are provided by LVM. According to the example shown in FIG. 12, logical volumes 143 and 144 are provided from volume group 12.

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

According to the comparative example, when migrating logical volumes, I/O to the mount points of the logical volumes 143 and 144 is stopped in the first storage system 102, and the mount points of the logical volumes 143 and 144 are transferred to the first storage system 102. unmounting, disabling volume group 12, exporting volume group 12, migrating volumes 71 and 72 that make up the exported volume group between storage systems in volume units (migration using the remote copy function described above), Importing the volume group 12 into the storage system 112 of No. 2 (configuration of volume group 12 consisting of migrated volumes 71 and 72), enabling volume group 12, mounting logical volumes 143 and 144, and logical volume 143 Processing such as starting I/O to and 144 is performed. In this case, I/O stop time is a problem.

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

In this embodiment, the volume migrated by the cloud migration tool 190 is a unit recognized by the computer 101. Therefore, even if a plurality of logical volumes are provided from the volume group 12, migration to the cloud storage service 109 is possible in units of logical volumes. In other words, some of the logical volumes provided by 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 among the plurality of logical volumes provided by one volume group 12 can be excluded from migration targets.

Furthermore, in this embodiment, since migration is possible in units of logical volumes, there is no need to stop I/O.

According to the example shown in FIG. 12, the following transition is performed.
- 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 transferred from the online mapping volume 1151 to the target volume 1152. A transition takes place.
- 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 transferred from the online mapping volume 1153 to the target volume 1154. A transition takes place.
[Fourth embodiment]

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

In the fourth embodiment, second storage system 1302 is a storage system in near cloud environment 160. A "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). Therefore, for convenience, the name "near cloud" is used in the description of this embodiment. It has been adopted in The present invention can also be applied to such a second storage system 1302.
[Fifth embodiment]

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

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

In this embodiment, the source volume (data volume) 104 of the first storage system 102 is transferred from the source volume (data volume) 104 of the first storage system 102 to the second storage system 1302 without the remote copy function of data from the first storage system 102 to the second storage system 1302. Migration to target volume 114 is achieved. Therefore, even if the first storage system 102 is not compatible with the second storage system 1302, data volumes 104 in the first storage system 102 can be stored more reliably than the default cloud storage service 109. Alternatively, it is possible to migrate to a second storage system 1302 with superior functionality. Furthermore, since the data volume 104 of the on-premises environment 100 is migrated to the second storage system 1302 of the near cloud environment 160 without going through an intermediate volume, it can be expected that migration time will be shortened and reliability will be improved.
[Sixth embodiment]

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

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

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

FIG. 16 shows an overview of system migration according to the seventh embodiment. Note that due to space limitations, the on-premises environment 100, cloud migration tool 190, and information processing system 105 are not illustrated in FIG.

In the seventh embodiment, when the second storage system 112 migrates to the target volume 114, the second storage system 112 transfers the data to be migrated to the target volume 114 (data to be migrated to the target volume 114). The data 116 for storage control is added to the data 116 for storage control, and the data to be migrated and the added data 116 for storage control are redundantly stored. For example, the second storage system 112 creates a redundant volume 115 for the target volume 114. The redundant volume 115 stores redundant data (for example, replicated data) of the data in the target volume 114 and the storage control data 116 . Note that the "data to be migrated" in this paragraph may be all the data to be migrated to the target volume 114, or may be data in units of a predetermined size.

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 given to data in order to detect whether or not data is missing or has errors when it is transferred, stored, or read. The consistency check code is, for example, ECC (Error Correcting Code).

Instead of or in addition to the consistency check code, management data for realizing storage functions (for example, thin provisioning, tier control, snapshots, compression, deduplication, remote copy, etc.) is added as storage control data 116. It's okay to be.

Although FIG. 16 shows an example of redundant storage in which data in the target volume 114 is duplicated, the redundancy may be triple or more, or may be erasure coding. The size of redundant volume 115 may be different from target volume 114.

FIG. 17 shows the configuration of the second storage system 112.

The second storage system 112 includes some computer instances 1702 provided by the cloud computer service 107 and some volumes 1701 (indicated as "VOL" in FIG. 17) provided by the cloud storage service 109. . The computer instance 1702 is composed of multiple (or one) computer instances. The computer instance 1702 in the second storage system 112 has the control software 1750, but the application does not need to be running (on the other hand, the migrated computer instance may have the application). The volume 1701 is composed of a plurality of volumes (or one volume).

The configuration shown in FIG. 17 is an example, and the number of computer instances 1702 and the number of volumes 1701 may differ from those shown. Further, the second storage system 112 may be configured only with the computer instance 1702, or may include other components provided by the cloud environment 106.

Control software 1750 operates on computer instance 1702 . Control software 1750 forms storage pool 1700 using volume 1701 of second storage system 112. The storage pool 1700 may be a logical space (address space) based on multiple (or one) volumes 1701.

The control software 1750 also creates a target volume 114 and a redundant volume 115 using the storage pool 1700. In preparation for a failure, the target volume 114 and 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 separate computer instance from the first computer instance 108. As a result, even if a failure occurs in either the first or second computer instance 1702, I/O to the volume 114 or 115 managed by the remaining computer instance among the first and second computer instances 1702 is maintained. Continuation is possible.

One of the plurality of computer instances 1702 is the master, and the control software 1750 of the master computer instance 1702 (hereinafter referred to as master control software 1750) is the control software 1750 other than the master control software 1750 (master computer instance). Instructions may be issued to control software 1750) of computer instances 1702 other than computer instance 1702. The master control software 1750 and the control software 1750 that received instructions from the master control software 1750 independently or in cooperation with each other form the storage pool 1700 and transfer the target volume 114 to the first computer instance 1702. Alternatively, a redundant volume 115 of the target volume 114 may be created in the second computer instance 1702.

[Eighth embodiment]

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

FIG. 18 shows the flow of processing performed in the eighth embodiment.

In the eighth embodiment, first, it is investigated whether the first storage system 102 that is the migration source and the second storage system 112 that is the migration destination are compatible (S1801). This investigation may be conducted, for example, by any of the following methods.
- The information processing system 105 (for example, the migration control unit 153) collects system information (for example, information indicating the vendor and model of the storage system) from each of the first and second storage systems 102 and 112, and It may be determined whether the system information of the second storage system 102 and the system information of the second storage system 112 satisfy the compatibility rule represented 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 into the information processing system 105 and stored in the storage device 52 in advance by the user who has checked the presence or absence of compatibility. Based on the information, the information processing system 105 (for example, the migration control unit 153) performs S1801.

As a result of the investigation, if there is compatibility (S1802: Yes), from the first storage system 102 that is the migration source to the second storage system 112 that is the migration destination, without going through the cloud storage service 109, The data volume is directly migrated (S1803). That is, if there is compatibility, migration can be performed using the method described in the prior art document.

As a result of the investigation, if there is no compatibility (S1802: No), the data volume is transferred from the first storage system 102 as the migration source to the second storage system 112 as the migration destination via the cloud storage service 109. is transferred (S1804). That is, data volumes are migrated using the methods described in the first to seventh embodiments. If the method of the fifth or sixth embodiment is used, the data volume may be migrated without going through the cloud storage service 109.

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

Although several embodiments have been described above, these are illustrative examples for explaining the present invention, and are not intended to limit the scope of the present invention only to these embodiments. For example, any two or more of the first to seventh embodiments described above may be combined. Further, part or all of the processing according to instructions from the information processing system 105 may be performed manually without using instructions from the information processing system 105. Furthermore, the "cloud storage service" may also be referred to as "cloud storage" or "cloud storage system."

Furthermore, in the above description, the volume to be migrated is a logical volume. In principle, data stored in a logical volume (data stored in a physical volume) is moved between the physical volumes (drives) of the first storage system, cloud storage service, and second storage system together with the logical volume. do. While data is being moved, some data will temporarily exist on the source and the remaining data will exist on the destination. For this reason, for example, when the I/O request is a read request, data is read out from the migration source and the migration destination, from whichever data to be read exists. Further, for example, if the I/O request is a write request, data may be written to both the migration source and the migration destination. This allows data to be accessed even during migration.

Further, the above explanation can be summarized, for example, as follows. The following summary may include supplements to the above description and descriptions of variations.

An information processing system 105 having a processor 53 and capable of communicating with a cloud computer, a first storage system 102, and a second storage system 112 is constructed. When migrating the computer instance 108 as the computer 101 to a cloud computer and migrating data used by the computer instance 108 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 that stores an image of an OS (Operating System) for configuring a computer instance to be migrated and a data volume 104 that stores data used by the OS are installed in a first storage system 102. to the cloud computer using the cloud computer migration tool 190.
(B) Create the mapping volume 113 mapped to the intermediate volume 111, which is the data volume migrated to the cloud computer by the migration tool 190, in the second storage system 112, and transfer data input/output from the computer instance 108 to the mapping volume 113. The path is set in the computer instance 108.

(A) is performed by the tool operation section 151. (B) is performed by the transition 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.

The information processing system 105 may further include a migration completion confirmation unit 152 that confirms that migration by the migration tool 190 has been completed. The migration control unit 153 may cause the second storage system 112 to create the mapping volume 113 after confirming that the migration tool 190 has completed the migration.

Migration tool 190 may be configured to migrate data volume 104 to a cloud computer in a data arrangement that computer instance 108 can interpret. The second storage system 112 may map an intermediate volume 111, which is a data volume with a data arrangement that can be interpreted by the computer instance 108, to a mapping volume 113 within the second storage system. Furthermore, the migration tool 190 may be configured to convert the data arrangement into a data arrangement that can be interpreted by the computer instance 108 and migrate the data volume 104 to the cloud computer.

The migration control unit 153 migrates data from the mapped volume 113 of the second storage system 112 to the target volume 114 in the second storage system 112, and instead of setting a path from the computer instance 108 to the mapped volume 113, the data is transferred to the target volume 114. You can set the path to

The migration control unit 153 may delete the intermediate volume 111 from the cloud computer after the data migration from the mapping volume 113 to the target volume 114 in the second storage system 112 is completed.

A computer instance at the migration source may use multiple data volumes. The tool operation unit 151 may specify a plurality of data volumes used by a computer instance as migration targets (for example, may be specified to the migration tool 190). Each designated data volume may be migrated to a cloud computer and a mapping volume may be created.

The migration control unit 153 determines an external connection method according to the cloud computer in which the data volume (intermediate volume 111) exists among the plurality of external connection methods, and transfers the data volume (intermediate volume 111) to the second storage system. The external connection to be associated is executed in accordance with the determined external connection method, and a mapping volume 113 is created 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. good.

The migration control unit 153 may determine whether the cloud computer and the second storage system 112 both support the multipath function. If the result of the determination is true, the migration control unit 153 adds a path connecting the computer instance 108 and the mapping volume 113, followed by a path connecting the data volume (intermediate volume 111) and the computer instance 108. If so, you can delete the path. If the result of the determination is false, the migration control unit 153 deletes the path connecting the data volume (intermediate volume 111) and the computer instance 108, and then adds a path connecting the computer instance 108 and the mapping volume 113. You may do so. Note that the migration control unit 153 may bring the path to the mapping volume 113 online without bringing the path to the data volume (intermediate volume 111) online.

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

A computer instance may manage one or more logical volumes making up the volume group 12 for the first storage system 122. A volume group may be one logical space made up of multiple physical volumes of the first storage system 102. Each of the plurality of physical volumes may be a logical space. The data volume recognized by the computer instance may be a logical volume recognized by the computer instance.

A cloud computer has a computing function and a storage function, and may be provided as a cloud service. The compute function may be a function of the 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 service's cloud environment. Further, the second storage system 112 may be a storage system connected to a cloud computer of a cloud service.

Note that instead of or in addition to the information processing system 105, an information processing system including a cloud computer, the first storage system 102, and the second storage system 112 may be constructed. A cloud computer may have a computing function and a storage function. When migrating a computer instance to a cloud computer and migrating data used by the computer instance from the first storage system 102 to the second storage system 112, the cloud computer migration tool 190 uses A system volume that stores an image of an OS (Operating System) for running an instance and a data volume that stores data used by the OS are migrated from the first storage system 102 to the storage function of the cloud computer. It's fine. The second storage system causes 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 migration tool 190, and maps it from the computer instance 108. A data input/output path to the volume 130 may be set in the computer instance 108.

105...Information processing system

Claims (18)

In an information processing system that has a processor and can communicate with a cloud computer, a first storage system, and a second storage system,
When migrating a computer instance to a cloud computer and migrating data used by the computer instance from a first storage system to a second storage system,
A system volume that stores an image of an OS (Operating System) for configuring a computer instance to be migrated, and a data volume that stores data used by the OS from the first storage system to the cloud computer, a tool operation unit for migrating to the migration tool of the cloud computer;
Creating a mapping volume mapped to the data volume migrated to the cloud computer by the cloud computer migration tool in a second storage system, and setting a data input/output path from the computer instance to the mapping volume in the computer instance. A transition control unit;
An information processing system equipped with. Further comprising a migration completion confirmation unit that confirms that the migration by the migration tool is completed,
The migration control unit causes the second storage system to create the mapping volume after confirming completion of the migration by the migration tool.
The information processing system according to claim 1. The migration tool migrates the data volume to the cloud computer in a data arrangement that can be interpreted by the computer instance;
The second storage system maps a data volume of a data arrangement that can be interpreted by the computer instance to a mapping volume in the second storage system.
The information processing system according to claim 1. The migration tool converts the data volume into a data arrangement that can be interpreted by the computer instance and migrates the data volume to the cloud computer.
The information processing system according to claim 3. The migration control unit migrates data from the mapping volume of the second storage system to the target volume in the second storage system, and sets a path to the target volume instead of setting a path from the computer instance to the mapping volume. set,
The information processing system according to claim 1. After completing the migration of data from the mapping volume to the target volume in the second storage system, the migration control unit deletes, from the cloud computer, an intermediate volume that is a volume of the data volume migrated to the cloud computer. ,
The information processing system according to claim 1. The computer instance uses multiple data volumes,
The tool operation unit specifies a plurality of data volumes used by the computer instance as migration targets;
Each of the specified data volumes is migrated to the cloud computer and a mapping volume is created.
The information processing system according to claim 1. The migration control unit determines an external connection method according to a cloud computer in which the data volume exists, from among a plurality of external connection methods, and determines an external connection method that associates the data volume with the second storage system. causing execution according to the determined external connection method to create the mapping volume in the second storage system for the data volume of the cloud computer to which the external connection has been made;
The information processing system according to claim 1. The transition control section includes:
determining whether the cloud computer and the second storage system both support a multipath function;
If the result of the determination is true, add a path connecting the computer instance and the mapping volume, and then, if there is a path connecting the data volume and the computer instance, delete that path;
If the result of the determination is false, delete a path connecting the data volume and the computer instance, and then add a path connecting the computer instance and the mapping volume;
The information processing system according to claim 1. The migration control unit brings the path to the mapping volume online without bringing the path to the data volume online.
The information processing system according to claim 9. The computer instance is running on a virtual computer generated by a hypervisor executed by a physical computer before migration,
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 data arrangement within the data volume is a data arrangement for the hypervisor,
The migration tool converts the data arrangement within the data volume into a data arrangement that can be interpreted by the computer instance, and migrates the data volume to the cloud computer.
The information processing system according to claim 1. The computer instance manages one or more logical volumes constituting a volume group for a first storage system,
The volume group is one logical space composed of 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. The cloud computer has a computing function and a storage function and is provided as a cloud service,
The second storage system is a storage service in a cloud environment different from the cloud environment of the cloud service.
The information processing system according to claim 1. The cloud computer has a computing function and a storage function and is provided as a cloud service,
The second storage system is a storage system connected to a cloud computer of the cloud service,
The information processing system according to claim 1. In an information processing system including a cloud computer, a first storage system, and a second storage system,
The cloud computer has a computing function and a storage function,
When migrating a computer instance to a cloud computer and migrating data used by the computer instance from a first storage system to a second storage system,
The migration tool for the cloud computer allows the compute function to store a system volume that stores an image of an OS (Operating System) for operating a computer instance to be migrated, and a data volume that stores data used by the OS. , transferring from the first storage system to the storage function of the cloud computer,
The second storage system causes the second storage system to create a mapping volume mapped to the data volume migrated to the cloud computer by the migration tool of the cloud computer, and performs data input/output from the computer instance to the mapping volume. Set the path to the computer instance,
Information processing system. When migrating a computer instance to a cloud computer and migrating data used by the computer instance from a first storage system to a second storage system,
The tool operation unit transfers a system volume that stores an image of an OS (Operating System) for configuring a computer instance to be migrated and a data volume that stores data used by the OS from the first storage system. Migrate to the cloud computer using a migration tool of the cloud computer,
The migration control unit causes a second storage system to create a mapping volume mapped to the data volume migrated to the cloud computer by the migration tool of the cloud computer, and creates a data input/output path from the computer instance to the mapping volume. Set it on the computer instance,
Information processing method. the second storage system,
adding storage control data, which is data used for controlling the second storage system, to data to be migrated to the target volume in the second storage system;
redundantly storing the data to be migrated and data for storage control;
The information processing system according to claim 5 or 6 . The redundant storage of the data to be migrated and the data for storage control is the 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,
The computer instance that manages the redundant volume is a different computer instance from the computer instance that manages the target volume.
The information processing system according to claim 17.

Images