Migration of primary and secondary storage systems

Data migration is realized through multi-storage volume switching technology between storage systems, and the problems of high CPU utilization and manual intervention in the data migration process in the prior art are solved, the migration efficiency and availability are improved, and the risk of data loss is reduced.

CN118901057APending Publication Date: 2024-11-05INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028951.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-22
Filing Date
2023-02-06
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

The prior art is difficult to maintain high availability and reduce CPU utilization during data migration, and often requires a lot of manual intervention, which can easily lead to data loss and long migration time.

Method used

Using multi-storage volume switching technology, data replication is realized between the first main storage device, the second main storage device and the auxiliary storage device, and multi-storage volume switching is enabled after reaching the full duplex state, the migration process is automated and labor is reduced. Intervention to reduce CPU utilization.

Benefits of technology

Implement data migration without losing high availability, reduce CPU utilization, reduce migration time, improve automation, and reduce the risk of data loss.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901057A_ABST
    Figure CN118901057A_ABST
Patent Text Reader

Abstract

A method for migrating from a first storage system to a second storage system is provided. A method includes receiving a command to migrate from a first storage system to a second storage system, where the first storage system includes a first primary storage device and a first secondary storage device, and where the second storage system includes a second primary storage device and a second secondary storage device. The method further includes, in response to receiving the command, initiating data replication between the first primary storage device and the second primary storage device. The method also includes initiating data replication between the first primary storage device and the second secondary storage device in response to receiving the command. The method also includes migrating from the first storage system to the second storage system.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] The present disclosure relates generally to the field of computer storage systems, and more particularly to migrating data to a replacement storage device using multiple storage volume swapping.

[0002] Data backup systems can provide continuous availability of production data in the event of a sudden catastrophic failure at a single point in time or data loss over a period of time. In one such disaster recovery system, production data is replicated from a local site to a remote site, which may be geographically separated by several miles from the local site. When the application system writes new data to the primary storage device, which is usually located at the local site, this dual, mirrored or shadow copy is usually made in the secondary storage device at the remote site. Different data replication technologies can be used to maintain a remote copy of the data at the secondary site, such as Metro mirror peer remote copy (PPRC), extended remote copy (XRC), coupled (Coupled) XRC (CXRC), global copy and global mirror copy. Summary of the invention

[0003] Embodiments of the present disclosure include methods, computer program products, and systems for migrating from a first storage system to a second storage system. The method includes receiving a command to migrate from the first storage system to the second storage system, wherein the first storage system includes a first primary storage device and a first secondary storage device, and wherein the second storage system includes a second primary storage device and a second secondary storage device. The method also includes, in response to receiving the command, initiating data replication between the first primary storage device and the second primary storage device. The method also includes, in response to receiving the command, initiating data replication between the first primary storage device and the second secondary storage device. The method also includes migrating from the first storage system to the second storage system.

[0004] This method can provide many advantages over the current migration process. For example, the embodiments of the present disclosure provide the ability to migrate without losing high availability, which has the multi-storage volume exchange function that can be achieved using software-based data migration products, but at the same time reduces or eliminates the additional CPU utilization inherent in software-based mirroring solutions. If the CPU capacity is not increased, reducing the CPU utilization can lead to lower software licensing costs and / or lower impact on business-critical work. When compared with existing solutions, the embodiments also reduce the amount of time required to perform migration exchanges. In addition, the embodiments of the present disclosure are flexible and can be used with any copy service management tool, such as the copy service management tool provided by EMC (e.g., Geographic Dispersed Disaster Restart (GDDR), Symmetrix Remote Data Facility (SRDF), and AutoSwap) and Hitachi (e.g., Hitachi Universal Replicator (HUR)). The embodiments of the present disclosure can also be substantially automated, while previous migration processes and operations often involve a large amount of manual intervention, which is usually time-consuming, error-prone, and may potentially cause some data loss.

[0005] In some preferred embodiments, prior to migrating from the first storage system to the second storage system, the second storage system may be prepared for migration. Preparing the second storage system may include converting the replication mode between the first primary storage device and the second primary storage device to synchronous, and converting the replication mode between the first primary storage device and the second auxiliary storage device to synchronous. This may advantageously allow replication to be initially in asynchronous mode when replicating large amounts of data, with the mode being switched to synchronous shortly before the migration. Because the asynchronous mode is less resource intensive (e.g., because fewer write operations are performed simultaneously), this reduces the impact of the migration on application performance. Additionally, using the asynchronous mode allows application I / O requests to complete without waiting for data to be sent to the target storage device and subsequent confirmation of copy completion, which is inherent to synchronous mirroring, which may otherwise add additional latency to the I / O requests. Although it may be desirable that all three synchronous I / O requests complete simultaneously, there are reasons why this may not be the case, such as congestion, link failures, etc., and therefore, waiting to switch provides better application performance.

[0006] In some preferred embodiments, multiple storage volume swapping is implemented between the first primary storage device and the second primary storage device. Once a full duplex state is achieved between the first primary storage device and the second primary storage device and the second auxiliary storage device, the multiple storage volume swapping can be enabled. Advantageously, in the event of an error in accessing the first primary storage device during migration, enabling the multiple storage volume swapping between the first primary storage device and the second primary storage device can allow the system to fail over to the second primary storage device instead of the first auxiliary storage device.

[0007] Further embodiments of the present disclosure include methods, computer program products, and systems for migrating from a first storage system to a second storage system. The method includes receiving a command to migrate from the first storage system to the second storage system. The first storage system includes a first primary storage device and a first secondary storage device, and the second storage system includes a second primary storage device and a second secondary storage device. The method also includes, in response to receiving the command, copying data between the first primary storage device and the second primary storage device. The method further includes, in response to receiving the command, copying data between the first primary storage device and the second secondary storage device. The method also includes, in response to reaching a full-duplex state between the first primary storage device and the second primary storage device and the second secondary storage device, pausing the received I / O operation for execution on the first storage system, storing the I / O operation in a queue, and enabling multi-storage volume exchange between the second primary storage device and the second secondary storage device. The method also includes migrating from the first storage system to the second storage system so that the newly received I / O operation is executed on the second storage system. The method also includes resuming the I / O operation and executing the queued I / O operation on the second storage system.

[0008] The above summary is not intended to describe each illustrated embodiment or every implementation of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings included in the present disclosure are incorporated into the specification and form a part of the specification. They illustrate embodiments of the present disclosure and, together with the specification, are used to explain the principles of the present disclosure. The accompanying drawings are only illustrations of typical embodiments and do not limit the present disclosure.

[0010] Figure 1 A diagram illustrating an example data migration process.

[0011] Figure 2 An example network computing environment employing a primary storage system and a secondary storage system according to an embodiment of the present disclosure is shown.

[0012] Figure 3A An example block diagram according to an embodiment of the present disclosure is shown, which depicts a storage state before migrating an old primary storage system and an old secondary storage system to a new primary storage system and a new secondary storage system.

[0013] Figure 3B An example block diagram is shown that depicts storage states during migration of an old primary storage system and an old secondary storage system to a new primary storage system and a new secondary storage system according to an embodiment of the present disclosure.

[0014] Figure 3CAn example block diagram according to an embodiment of the present disclosure is shown, which depicts the storage status after an old primary storage system and an old secondary storage system are migrated to a new primary storage system and a new secondary storage system.

[0015] Figure 4 A flowchart of an example method for migrating from an old storage system to a new storage system using multi-storage volume swap according to an embodiment of the present disclosure is shown.

[0016] Figure 5 A flowchart of an example method for migrating data from an old storage system to a new storage system according to an embodiment of the present disclosure is shown.

[0017] Figure 6 A high-level block diagram of an example computer system that can be used to implement one or more of the methods, tools, and modules described herein, and any related functionality, according to an embodiment of the present disclosure is shown.

[0018] Figure 7 A cloud computing environment according to an embodiment of the present disclosure is depicted.

[0019] Figure 8 Abstract model layers according to an embodiment of the present disclosure are depicted.

[0020] Although the embodiments described herein may have various modifications and alternative forms, the details thereof have been shown by way of example in the accompanying drawings and will be described in detail. However, it should be understood that the specific embodiments described should not be construed as limiting. On the contrary, the present invention covers all modifications, equivalents and substitutions that fall within the spirit and scope of the present invention. DETAILED DESCRIPTION

[0021] Aspects of the present disclosure generally relate to the field of computer storage systems, and more particularly to migrating data to replacement storage devices using multi-volume swapping. Although the present disclosure is not necessarily limited to such applications, various aspects of the present disclosure may be understood through discussion of various examples using this context.

[0022] For illustration purposes only, this article refers to Copy Services Manager (CSM) and Embodiments of the present disclosure are described. However, embodiments of the present invention are not limited to any one of these techniques, and contemplate all suitable alternatives (ie, those with similar input functionality).

[0023] In a data mirroring system, data is typically maintained in the form of volume pairs, including a primary volume in a primary storage device and a corresponding secondary volume in a secondary storage device, the secondary storage device including an identical copy of the data maintained in the primary volume. The primary volume and the secondary volume are identified by a copy relationship, where data from the primary volume (also referred to as the source volume) is copied to the secondary volume (also referred to as the target volume). The primary storage controller and the secondary storage controller may be used to control access to the primary storage device and the secondary storage device.

[0024] Copy Services Manager (CSM) is an example of an application that customers can use to manage planned and unplanned downtime. A solution that includes CSM can detect a failure at a primary storage system, which can be located, for example, at a local site. Such a failure can include a problem writing to or accessing a primary storage volume at the local site. When the solution detects that a failure has occurred, CSM can invoke a multi-storage volume swap function, an example of which is IBM Function (e.g., logical device swap). This function can be used to automatically swap the processing of all volumes in a mirrored configuration from the primary storage system to the secondary storage system (e.g., in some embodiments, it can include swapping from the local site to the remote site). In some embodiments, the CSM can initiate the swap even when no failure is detected. As a result of the swap, the storage volumes at the remote site that were originally configured as the secondary volumes of the original copy relationship are reconfigured as the primary volumes of the new copy relationship. Similarly, once the volumes at the local site are operational again, the storage volumes at the local site that were originally configured as the primary volumes of the original copy relationship can be reconfigured as the secondary volumes of the new copy relationship.

[0025] In conjunction with the swap function, a failover function may be invoked. In the case of a solution that includes a CSM, the failover function may, in some cases, avoid performing a full copy when reestablishing data replication in the opposite direction (i.e., from the remote site to the local site). More specifically, the failover process resets or reconfigures the remote storage device (which was initially configured as a secondary storage device) as a primary storage device, which is in a "suspended" state, awaiting resumption of mirroring operations, but in the opposite direction. At the same time, the failover process begins recording changes for any subsequent data updates made by the host to the remote site.

[0026] Once the local site is operational, a failback process can be invoked to reset the storage device at the local site (which was originally configured as the primary storage device) to a secondary storage device. Mirroring can then be resumed (but in the opposite direction, i.e., remote to local rather than local to remote) to resynchronize the data updates stored on the secondary storage device at the local site (initially the primary storage device) with the primary storage device at the remote site (initially the secondary storage device). Once data synchronization is complete, The return operation can reestablish configuration management from the storage system at the local site (which was the original primary storage system) to the storage system at the remote site (which was the original secondary storage system). Now, in the event that mirroring and HyperSwap are reestablished in the opposite direction, the configuration can remain in this configuration where the remote storage device remains the primary device and the local device remains the secondary device, which is typically the case if the remote storage device is physically located in the same location. If necessary, a planned HyperSwap can be initiated to return to the original configuration after the above steps, but in the opposite direction and without the device failure. Of course, in the event that a device failure is detected, an unplanned HyperSwap will have the same result, moving the primary device from the remote location back to the local location.

[0027] In various situations, it may be appropriate to switch one or more volumes of a primary storage device or source storage device to corresponding volumes of a different source storage device without significantly affecting the production work of the user. For example, the user may want to migrate the source storage device to a new storage system, or to a different storage system, in order to improve overall performance or for reconfiguration purposes. Figure 1 An example of a typical data copy session is shown, wherein data on a volume 110 of a first storage control unit 120a (i.e., an old primary storage device) is copied to a corresponding volume 110 of a second data storage control unit 120b (i.e., an old secondary storage device) in an ongoing data copy process represented by arrow 130. Additionally, in an ongoing data migration process represented by arrow 140, data on a volume 110 of a first storage control unit 120a is being migrated to a corresponding volume 110 of a third data storage control unit 120c (i.e., a new primary storage device).

[0028] Various products are available for migrating data from an existing storage system to a new storage system with little or no disruption to ongoing input / output (I / O) operations or disaster recovery capabilities that can provide disaster recovery capabilities in the event of a failure during the data migration process. Examples of such data migration products include IBM Corporation's TDMF (Transparent Data Migration Facility) or Innovative Data Processing's FDRPAS. However, if the volumes 110 of storage control units 120a and 120b are part of an existing storage replication session such as data replication process 130, for example, a fourth control unit's volume 110, such as storage control unit 120d (i.e., a new secondary storage device), is typically provided to ensure that failover capabilities are maintained.

[0029] Thus, in a typical migration process of migrating data stored on a volume 110 of a storage control unit 120a from the storage control unit 120a to a corresponding volume 110 of a storage control unit 120c, a fourth storage control unit 120d is typically provided, and a data copy process as indicated by arrow 150 is initiated prior to the migration process 140 to copy data that may have been initially stored on the storage control unit 120c to the storage control unit 120d. The initial portion of the data copy process 150 includes configuring the volume 110 of the storage control unit 120d to correspond to the volume 110 of the storage control unit 120c, which in turn is configured to correspond to the volume 110 of the storage control unit 120a, i.e., the source of the data to be migrated.

[0030] Therefore, the entire migration process typically includes waiting for the two new storage control units 120c and 120d to reach a full-duplex state, that is, the configuration of the storage volume 110 of the storage control unit 120c with the copy relationship of the storage control units 120c and 120d has been copied in the volume 110 of the storage control unit 120d, and the data on those configured volumes 110 is the same as the initial data stored on the storage control unit 120c. At this point in the entire process, the migration process 140 is typically started using a migration product such as TDMF or FDRPAS. The migration product will start copying data from the storage control unit 120a to the storage control unit 120c. Once the data migration product has copied most of the data from the storage control unit 120a to the storage control unit 120c, it stops the I / O to the storage control unit 120a, copies the remaining changes (data writes) to the storage control unit 120a from the storage control unit 120a to the storage control unit 120c, and then exchanges the I / O request to go to the storage control unit 120c.

[0031] Data replication processes such as data replication process 130 may often involve many copy relationship pairs, typically numbered in the thousands. Therefore, in a typical data migration, a relatively small number of source volumes of control unit 120a are selected each time to migrate to a new storage control unit 120c. Therefore, the copy relationship pairs of those source volumes of the storage control unit 120a for migration are typically first manually added to an existing replication session represented by process 150. The replication session process 150 is started (or restarted), and a wait occurs until the added copy relationship pairs reach a full-duplex state in the replication process 150. Once the full-duplex state has been reached for the added copy relationship pairs, the migration process 140 is started (or restarted) for the selected source volumes of the control unit 120a, and typically the migration product is again waited for to swap the selected volumes 110 from the storage control unit 120a to the storage control unit 120c. Once the swap is completed, the selected copy relationship pairs of the volumes 110 in the storage control unit 120a and the storage control unit 120b are removed from the replication process 130, and their relationships are terminated. This process is repeated until all source volumes of the storage control unit 120a to be migrated have been selected and processed as described above.

[0032] For example, data can also be migrated to a new storage system without using a data migration product such as TDMF or FDRPAS. However, such a data migration process may cause an interruption of an ongoing data replication process or disaster recovery capabilities. An example of such a migration process may occur when a source storage device is being migrated to a new source device, but the target storage device has not changed.

[0033] In this example, the migration process may include selecting a source volume 110 of the storage control unit 120a to be migrated to the new storage control unit 120c, and first manually removing the copy relationship pairs of the selected volume 110 in the storage control unit 120a and the corresponding volume 110 of the storage control unit 120b from the replication process 130, and terminating those relationship pairs. Then, a new copy relationship pair corresponding to the terminated copy relationship pair may be manually established between the new source volume 110 in the storage control unit 120c and the original target volume 110 in the storage control unit 120b.

[0034] Alternatively, if the goal is to use CSM and HyperSwap to migrate to a new generation storage system for both the primary and secondary storage systems while maintaining disaster recovery capabilities and high availability, the user can go through a multi-step process where the primary storage system is first replaced and then the process is repeated for the secondary storage system. However, this process can be slow because it requires that all steps for migrating the secondary storage system be performed after the primary storage system is fully migrated, making the operation highly continuous.

[0035] Embodiments of the present disclosure provide a way to migrate data from one set of source volumes (i.e., primary volumes) and target volumes (i.e., secondary volumes) to another set while maintaining disaster recovery capabilities throughout the data migration and without having to perform the process twice. This is achieved by extending the multi-target support of some storage systems (e.g., System The invention is implemented by using a storage system in a series of storage devices to support at least three targets. Then, the expansion capability is used to allow the primary volume to be mirrored not only to the old secondary volume and the new primary volume, but also to the new secondary volume. By doing so, the global copy role pair between the new primary storage device and the new secondary storage device can be replaced by a metro mirror role pair between the old primary storage device and the new secondary storage device.

[0036] In some embodiments, a system can migrate from a first pair of storage devices (e.g., an old primary storage device and an old secondary storage device) to a second pair of storage devices (e.g., a new primary storage device and a new secondary storage device). This can be accomplished, for example, if a user is upgrading to a new storage solution to, for example, improve performance, capacity, functionality (or capabilities) of the storage. In a first operation, data stored in the old primary storage unit is mirrored from the old primary storage unit to the new primary storage unit and the new secondary storage unit. Software for performing the mirroring operation may include suitable copy service management tools, such as those provided by EMC (e.g., Geographically Dispersed Disaster Restart (GDDR), Symmetrix Remote Data Facility (SRDF), and AutoSwap) and Hitachi (e.g., Hitachi Universal Replicator (HUR)) or IBM (e.g., The Copy Services Manager (CSM) is a copy service management tool provided by the Copy Services Manager (CSM). Such a tool can be used by a storage manager according to the present specification, which can facilitate data migration as described herein. After mirroring the data to the new primary storage unit and the secondary storage unit, a failover operation can be performed to direct new I / O requests to the new primary storage unit.

[0037] This approach provides many advantages over current migration processes. For example, embodiments of the present disclosure provide the ability to migrate without losing high availability using multi-storage volume exchange (such as HyperSwap) capabilities that may be implemented using software-based data migration products (such as TDMF or FDRPAS), while reducing or eliminating the additional CPU utilization inherent in software-based mirroring solutions. If CPU capacity is not increased, reducing CPU utilization can result in lower software licensing costs and / or lower impact on business-critical work. When compared to existing solutions, embodiments also provide the ability to minimize the time required to perform migration exchanges. In addition, embodiments of the present disclosure are flexible and can be used with any copy service management tool, such as copy service management tools provided by EMC (e.g., Geographically Dispersed Disaster Restart (GDDR), Symmetrix Remote Data Facility (SRDF), and AutoSwap) and Hitachi (e.g., Hitachi Universal Replicator (HUR)).

[0038] In another aspect, many operations of the migration process according to the present disclosure can be automated. For example, operations such as terminating the copy relationship pair in the original source and target storage subsystems and re-establishing the copy relationship pair in the replacement source and target storage subsystems can be automatically completed. As explained in more detail below, such automation can be provided in the multi-volume swap function. In contrast, it should be understood that previous migration processes and operations often involve a large amount of manual intervention, which is usually time-consuming, error-prone, and may potentially result in some data loss.

[0039] It should be understood that the above advantages are exemplary advantages and should not be interpreted as limiting. Embodiments of the present disclosure may include all, some, or none of the above advantages while remaining within the spirit and scope of the present disclosure.

[0040] Although embodiments are described in conjunction with specific mirroring relationships, aspects of the present disclosure may be applied to other types of copy relationships, depending on the specific application. Additional features are discussed in this specification. It should be understood that, depending on the specific application, other features may be implemented to replace or supplement those discussed herein.

[0041] In the illustrated embodiment, a copy relationship identifies a source storage location (also referred to as a primary storage location) and a target storage location (also referred to as a secondary storage location), wherein data stored at the source storage location is to be mirrored or otherwise copied to the target storage location. Thus, as used herein, a primary storage location and a secondary storage location are storage locations that are related by a copy relationship.

[0042] Furthermore, as used herein, the term "storage location" refers to a storage location that contains one or more data storage units (e.g., one or more volumes, cylinders, tracks, segments, extents, or any portion thereof) or other data units suitable for storage. Thus, a source storage location and an associated target storage location may each be a storage volume, where the volumes are typically at different devices or sites. However, it is understood that the size of the source storage location and the target storage location may be different than the volume.

[0043] As used herein, the term "automatically" includes fully automatic, i.e., operations performed by one or more software-controlled machines without human intervention, such as user input to a graphical user interface. As used herein, the term "automatically" also includes predominantly automatic, i.e., most operations (e.g., greater than 50%) are performed by one or more software-controlled machines without human intervention, such as user input to a graphical user interface, while the remaining operations (e.g., less than 50%) are performed manually, i.e., manual operations are performed by one or more software-controlled machines with human intervention, such as user input to a graphical user interface to guide the performance of the operations.

[0044] Now turning to the attached figure, Figure 2 A block diagram of an example representation of a data storage environment 200 for storing host data is shown. The data storage environment 200 includes a host device 232, a primary control unit 202a including a first (e.g., primary) storage device 220a, and a secondary control unit 202b including a second (e.g., secondary) storage device 220b. The primary control unit and the secondary control unit can be, for example, separate computer systems (e.g., servers, network attached storage (NAS) devices, desktop computers, etc.), separate storage nodes, or components of a single device (e.g., separate components of a single storage node). The host device 232 is communicatively coupled to the primary control unit 202a and the secondary control unit 202b using a network 250. In some embodiments, the data storage environment 200 can be embodied as a storage attached network (SAN).

[0045] According to various embodiments, the host device 232 and the primary control unit 202a and the secondary control unit 202b may be computer systems. For example, in some embodiments, the host device 232 and the primary control unit 202a and the secondary control unit 202b may be storage server computers. The host device 232 includes a processor 236 and a memory 238. The memory 238 may include an operating system 240 and one or more applications 242, which are configured to utilize (e.g., access, read, write) data stored in the first and second storage devices 220a, 220b. Similarly, the primary control unit 202a and the secondary control unit 202b include one or more processors 206a, 206b and one or more memories 208a, 208b, respectively. The memories 208a, 208b of the primary control unit 202a and the secondary control unit 202b may include storage managers 210a, 210b and caches 212a, 212b.

[0046] Operating system 240 may include a multi-volume swap manager that provides a As explained in more detail below, a computer such as IBM can be modified according to the present disclosure. The multi-storage volume swap manager 232 is configured to facilitate a swap operation related to a migration operation, thereby replacing a primary storage system and a secondary storage system with a new storage system. Although in the illustrated embodiment, the multi-storage volume swap manager is part of the operating system 240 of the host 232, it is to be understood that the multi-storage volume swap manager may be implemented in the application software of the host, or in an operating system or application software of a storage control unit for storage management functions, for example.

[0047] The primary control unit 202a and the secondary control unit 202b and the host device 232 may be configured to communicate with each other via internal or external network interfaces 204a, 204b, and 234. The network interfaces 204a, 204b, and 234 may be, for example, modems or network interface cards. For example, the network interfaces 204a, 204b, and 234 may enable the host device 232 and the primary control unit 202a and the secondary control unit 202b to connect to the network 250 and communicate with each other.

[0048] The first storage device 220a and the second storage device 220b illustrate data storage nodes in the data storage environment 200. In some embodiments, the first storage device 220a includes a first set (i.e., one or more) of volumes 222a, where data is stored and / or retrieved by the host device 232. Similarly, the second storage device 220b includes a second set of volumes 222b. The volumes 222a, 222b may include a logical unit number (LUN), a logical subsystem (LSS), or any other track group, where a track may be a block, a track, or any other data unit. The data in the second storage device 220b (e.g., the second set of volumes 222b) may be a copy of the same data stored in the first storage device 220a (e.g., a copy of the first set of volumes 222a). The host device 232 may access the first volume 222a and the second volume 222b in the first storage device 220a and the second storage device 220b, respectively, through the network 250.

[0049] The host device 232 can direct input / output (I / O) requests to the primary control unit 202a used as a primary storage device to access tracks stored in the first storage device 220a. In the case where data cannot be accessed through the first control unit 202a, the auxiliary control unit 202b can be used as an auxiliary storage device or a backup storage device. The primary control unit 202a and the auxiliary control unit 202b can be in a synchronous mode so that data written to the primary control unit 202a is written to the auxiliary control unit 202b at the same time, thereby ensuring that the two control units 202a, 202b have the same copy of the data at all times. This is referred to herein as control units 202a, 202b (or, in some embodiments, separate storage devices 220 or volumes 222) having a mirror relationship or a mirror copy relationship. In the event that the host device 232 (or the first control unit 202a) detects that the first set of volumes 222a is unavailable, a failover event may occur, in which the secondary control unit 202b becomes the primary storage device and can retrieve a copy of the requested data (e.g., data being read or written) from the corresponding track or volume in the second set of volumes 222b.

[0050] The main control unit 202a and the auxiliary control unit 202b and / or the host device 232 may be equipped with a display or monitor. In addition, the main control unit 202a and the auxiliary control unit 202b and / or the host device 232 may include an optional input device (e.g., a keyboard, a mouse, a scanner, or other input devices), and / or any commercially available or customized software (e.g., browser software, communication software, server software, natural language processing software, search engine and / or web crawling software, a filtering module for filtering content based on predetermined parameters, etc.).

[0051] The primary control unit 202a and the secondary control unit 202b and the host device 232 may be remote from each other and communicate via the network 250. In some embodiments, the host device 232 may be a central hub from which the primary control unit 202a and the secondary control unit 202b may establish a communication connection, such as in a client-server networking model. Alternatively, the host device 232 and the primary control unit 202a and the secondary control unit 202b may be configured in any other suitable networking relationship (e.g., in a peer-to-peer configuration or using any other network topology).

[0052] In some embodiments, network 250 can be implemented using any number of any suitable communication media. For example, network 250 can be a wide area network (WAN), a local area network (LAN), a storage area network (SAN), the Internet, or an intranet. In some embodiments, the main control unit 202a and the auxiliary control unit 202b and the host device 232 can be local to each other and communicate via any suitable local communication medium. For example, the main control unit 202a and the auxiliary control unit 202b and the host device 232 can communicate using a SAN, one or more hardwired connections, switches such as a fiber channel switch or a FICON controller, a wireless link or a router, or an intranet. In some embodiments, the main control unit 202a and the auxiliary control unit 202b and the host device 232 can be coupled to the communication using a combination of one or more networks and / or one or more local connections. For example, the first control unit 202a can be hardwired to the host device 232 (e.g., connected to a fiber channel cable), and the second control unit 202b can use the network 250 (e.g., via the Internet) to communicate with the host device.

[0053] In some embodiments, the network 250 may be a telecommunications network. The telecommunications network may include one or more cellular communication towers, which may be fixed-position transceivers that directly wirelessly communicate with mobile communication terminals (e.g., the main control unit 202a and the auxiliary control unit 202b). In addition, the network may include one or more wireless communication links between the main control unit 202a and the auxiliary control unit 202b and the host device 232. The wireless communication link may include, for example, shortwave, high frequency, ultra-high frequency, microwave, wireless fidelity (Wi-Fi), Bluetooth technology, global system for mobile communications (GSM), code division multiple access (CDMA), second generation (2G), third generation (3G), fourth generation (4G), or any other wireless communication technology or standard to establish a wireless communication link.

[0054] In some embodiments, network 250 can be implemented within a cloud computing environment or using one or more cloud computing services. According to various embodiments, a cloud computing environment may include a network-based distributed data processing system that provides one or more cloud computing services. In addition, a cloud computing environment may include many computers (e.g., hundreds or thousands of computers or more) that are arranged in one or more data centers and configured to share resources through network 250.

[0055] In the illustrated embodiment, the communication hardware associated with the communication path between the devices includes switches, routers, cables, modems, adapters, power supplies, etc. The communication software associated with the communication path includes instructions and other software that controls the communication protocol and the operation of the communication hardware according to the communication protocol, if any. It should be understood that other communication path protocols may be utilized depending on the specific application.

[0056] The primary control unit 202a and the secondary control unit 202b may include storage managers 210a, 210b. The storage managers 210a, 210b may be modules (e.g., program instructions, hardware) in the data storage environment 200 configured to store and retrieve data. The storage managers 210a, 210b may include storage controllers. In some embodiments, the first storage manager 210a includes a set of instructions for processing I / O requests (e.g., reading, deleting, inserting, updating, and / or writing of data) received by the host device 232 on the first storage device 220a.

[0057] The storage managers 210a, 210b may also include a set of instructions to maintain a copy of the first storage device 220a on the second storage device 220b of the primary control unit and the secondary control unit, which may be considered as a separate storage system. The storage system may include an enterprise storage server, such as an IBM Enterprise Storage Server (ESS). The storage managers 210a, 210b that manage the first copy relationship may implement a synchronous copy operation, such as a peer-to-peer remote copy (PPRC) program. An example of a program that manages PPRC is Copy Services Manager (CSM) A copy program that enables updates to the primary storage device 220a to be switched to the secondary storage device 220b. The storage managers 210a, 210b may also implement asynchronous remote copy operations, where updates to the primary storage device 220a or the secondary storage device 220b are mirrored to corresponding locations at the remote site. Suitable asynchronous mirroring programs include Global Mirror and XRC (or zGM). The described operations may be implemented with other programs such as other copy programs or other global recovery programs.

[0058] In one illustrative example embodiment, the storage manager(s) 210a, 210b may monitor for migration commands. In response to receiving a migration command, the storage manager 210a, 210b may identify new primary and secondary storage devices (e.g., Figure 2 A new control unit not shown in FIG. 1 is provided, and the storage managers 210a, 210b can perform data migration. Figures 3A to 5 The specific steps for performing the data migration to the new storage device are discussed in more detail.

[0059] The first storage device 220a and the second storage device 220b may include storage devices of different types or categories. For example, the first storage device 220a and the second storage device 220b may include a magnetic hard disk drive, a solid-state storage device (SSD), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a flash disk, a random access memory (RAM), a storage class memory (SCM), a phase change memory (PCM), a resistive random access memory (RRAM), an optical disk, a magnetic tape, etc. In addition, the first storage device 220a and the second storage device 220b may be configured as a device array, such as a bunch of disks (JBOD), a direct access storage device (DASD), or a redundant array of independent disks (RAID) array.

[0060] Notice, Figure 2 The exemplary computing environment 200 is intended to depict representative major components. However, in some embodiments, the various components may have more Figure 2 The greater or lesser complexity represented in , may exist different from Figure 2 Components other than those shown in the figure or components in addition thereto, and the number, type, and configuration of these components may vary. Likewise, one or more components shown within computing environment 200 may not exist, and the arrangement of components may vary.

[0061] For example, although Figure 2 A computing environment 200 having a single host device 232 and two control units 202a, 202b is shown, but a suitable computing environment for implementing embodiments of the present disclosure may include any number of control units and host devices. For example, as discussed in more detail below, the computing environment 200 may include at least four control units. Figure 2 The various models, modules, systems, and components shown in may exist in multiple host devices and control units, if any.

[0062] For example, in some embodiments, the storage manager 210a, 210b may not be part of the primary control unit 202a and the secondary control unit 202b, or only one of the primary control unit 202a and the secondary control unit 202b may include a storage manager. In some embodiments, the storage manager may be an independent device different from the primary control unit and the secondary control unit. In these embodiments, the storage manager may be communicatively coupled to any one of the primary control unit 202a and the secondary control unit 202b and / or the first storage device 220a and the second storage device 220b (e.g., via the network 250). As another example, some embodiments may include two (or more) host devices. Each host device may be connected to two (or more) control units. Similarly, the primary control unit 202a and the secondary control unit 202b may be connected to two or more host devices and store data for them.

[0063] Reference now Figures 3A to 3C , a block diagram of a storage environment 300 is shown that describes an embodiment of the present disclosure during a migration from an old primary storage device and a secondary storage device (referred to as a first control unit 302a and a second control unit 302b, respectively, in the figure) to a new primary storage device and a secondary storage device (referred to as a third control unit 302c and a fourth control unit 302d, respectively, in the figure). In this example, we assume that the client currently has a HyperSwap-enabled dual-site storage replication solution that provides high availability and wishes to migrate to a newer storage system technology that is also a HyperSwap-enabled dual-site storage replication solution. However, it should be understood that this is for illustrative purposes only. If the starting solution is a three-site metropolitan global mirror solution or even a multi-target metropolitan mirror / global mirror solution, embodiments of the present disclosure can also be used, although the latter will require enhancement of the multi-target to support all four targets supported on the architecture.

[0064] from Figure 3A Initially, a block diagram of an environment 300 prior to migration is shown. In particular, Figure 3A As shown, environment 300 includes four control units 302a, 302b, 302c, and 302d (collectively and / or individually referred to as control units 302). Each control unit 302 includes a set of volumes 304. In particular, the first control unit 302a includes a first set of volumes 304a, the second control unit 302b includes a second set of volumes 304b, and so on. The first control unit 302a acts as a primary storage device for a client, while the second control unit 302b acts as a secondary storage device for the client.

[0065] As described above, the first control unit 302a and the second control unit 302b have a HyperSwap-enabled mirrored replication relationship, as indicated by arrow 306. Thus, each volume 304a in the first control unit 302a has an associated volume 304b in the second control unit 302b. This is indicated by arrow 307. In other words, each volume 302a has an identical copy 304b, and any data written to the first set of volumes 304a is also written to the second set of volumes 304b.

[0066] At the same time, at this stage, a new storage system is created to which the client is migrating. The new storage system includes the third and fourth control units 302c, 302d. The third control unit 302c will become the new primary storage system / device after the migration, and the fourth control unit 302d will become the new secondary storage system / device after the migration. Figure 3C As shown, the third and fourth control units 302c, 302d will have a mirror replication relationship with HyperSwap enabled after migration. Establishing a new storage system includes creating a third set of volumes 304c and a fourth set of volumes 304d on the third and fourth control units 302c, 302d, respectively.

[0067] Reference now Figure 3B , shows a storage environment 300 during migration from an old storage system to a new storage system according to an embodiment of the present disclosure. In particular, Figure 3B As shown, a replication relationship 308 is created between the first control unit 302a and the third control unit 302c. In addition, a replication relationship 310 is created between the first control unit 302a and the fourth control unit 302d. At the same time, a HyperSwap-enabled mirror replication relationship 306 is maintained between the first control unit 302a and the second control unit 302b.

[0068] Once the replication relationships 308, 310 between the first control unit 302a and the third and fourth control units 302c, 302d are established, data replication can begin. This is represented by arrows 309, 311 connecting the first set of volumes 304a to the third and fourth sets of volumes 304c, 304d, respectively. In some embodiments, data replication can begin automatically once the replication relationships 308, 310 are created (e.g., in response to a migration command) or at a specific time thereafter (e.g., when data operations on the first set of volumes 304a are low) to minimize the impact of replication. In other embodiments, a user (e.g., a client) can decide when to start replication (e.g., by providing a command to start replication using a graphical user interface (GUI)).

[0069] Regardless of whether the data replication is triggered by the computer system or by the user, the data replication between the first control unit 302a and the third and fourth control units 302c, 302d can initially be accomplished using asynchronous replication. This can help avoid the impact of replication on applications by reducing the total number of write operations occurring at any given time and allowing I / O to continue to the primary volume (even if the data has not yet been replicated to the secondary volume). In these embodiments, the time to replicate data may be higher. At the same time, the data can still be written to the second control unit 302b synchronously with the first control unit 302a to maintain high availability and data integrity between the control units 302a, 302b.

[0070] In some embodiments, data replication to one or both of the third and fourth control units 302c, 302d may be performed synchronously. This may be done based on, for example, the distance between the control units, the bandwidth capabilities between the control units, the amount of impact (predicted or actual) on application performance, and / or the quality of service (QoS), or acceptable performance level for the application. In some embodiments, data replication may switch from asynchronous to synchronous (or vice versa) as these factors change.

[0071] Once the data copied from the first control unit 302a and the third and fourth control units 302c, 302d reaches a state where the out-of-sync tracks between all relationships are within a threshold amount, the migration process can be initiated. The threshold amount can depend on the amount of I / O driven to the first control unit 302a. In some embodiments, the threshold amount can be close to 100%. The reason for the threshold is that embodiments of the present disclosure may require all storage systems to be in synchronous copy mode to ensure that they all have the same data to allow HyperSwap to occur. However, since work continues to update the main control unit 302a and the updates are out of sync, the system will usually never reach 100%. Therefore, at a certain point, the system will no longer be closer to 100%, and at this point, the system will have to switch to synchronous mirroring in order to reach 100%, and therefore move to the next step. The out-of-sync track should be low so that when the relationship switches from asynchronous replication to synchronization, the relationship can quickly reach a state of 100% copy, thereby allowing migration with the smallest possible application impact. In other words, by ensuring that the pair is as "synchronous" as possible, the amount of time required for synchronization and exchange can be minimized.

[0072] In some embodiments, how far this threshold is from 100% will depend on a number of things, including, but not limited to, how much I / O activity (particularly writes or updates) is occurring on the primary volume, and the bandwidth between the primary and secondary controllers. It may also vary based on the client and time of day (e.g., activity may be higher during trading hours at a financial firm).

[0073] In some embodiments, once the threshold is reached, the system may automatically initiate the migration process. In other embodiments, the user may have to trigger the start of the migration process. In some embodiments, the user may only be able to initiate the migration process after the threshold has been reached, while in other embodiments, the user may be able to override the threshold. In some embodiments, the system may not automatically migrate when the threshold is reached. For example, if the above-mentioned financial company reaches this "steady state" (e.g., 97%) during trading hours, they will often take a conservative approach and wait until the end of trading (if not 2:00 a.m.) before switching to the synchronous mirror to ensure safety. In any case, the system and / or user initiates the migration by issuing a command, which is referred to as the "prepare to migrate" command in this article.

[0074] Upon receiving a prepare-to-migrate command from a user or an automated system, if the replication type between the first control unit 302a and the third and fourth control units 302c, 302d is not yet synchronized, they are converted to synchronous replication. Data replication will then continue until all three role pairs have reached full-duplex status, at which point control software such as a CSM will load a HyperSwap configuration for the first control unit 302a to third control unit 302c relationship. The HyperSwap configuration may enable HyperSwap for unplanned swaps, or it may disable HyperSwap for unplanned swaps, making it available only for migration. In some embodiments, the default may be to disable unplanned swaps so that I / O is not moved to a new box until the user explicitly indicates that it should be moved.

[0075] In some embodiments, in the event of a problem, such as a problem mirroring data between the first control unit 302a and the second control unit 302b, migration may occur even before all three role pairs have reached full-duplex status. This may be the result of a problem or failure of the second control unit 302b itself or a communication failure (e.g., if the network connecting them fails). If such a failure occurs, the system may also continue to migrate to the new devices that are mirroring and have HyperSwap functionality (i.e., the third and fourth control units 302c, 302d) because the system is no longer mirroring between the old devices and therefore no longer has HyperSwap functionality. Depending on what caused the mirroring between the first and second control units 302a and 302b to stop, performing this unexpected early migration may be the most convenient way for the system to enable HyperSwap again.

[0076] When full duplex between the first control unit 302a and the third control unit 302c has been reached and HyperSwap has been enabled, and full duplex between the first control unit 302a and the fourth control unit 302d has been reached, the actual migration can be initiated by a migration command. The actual migration can be automatically initiated when the above conditions have been met, or it can be initiated by the user. Once the migration command is issued, the system will proceed to switch the primary storage system and the secondary storage system to the new storage system (for example, using a failover process such as HyperSwap).

[0077] However, unlike the current process for migrating to a new storage system, after executing the swap phase and before executing the restore I / O phase, the system executes a new phase. The new phase will fail over or terminate the relationship 310 of the first control unit 302a to the fourth control unit 302d and establish a replication relationship 312 of the third control unit 302c to the fourth control unit 302d in a synchronous mode, such as Figure 3C This can be accomplished using multi-target incremental failback support, which is available on a number of storage systems including IBM's DS8000 series storage systems. Alternatively, if multi-target support is not available, the third control unit 302c to fourth control unit 302d replication relationship 312 can also be established using the "no copy" option. In any case, creating the replication relationship 312 from the third control unit 302c to the fourth control unit 302d includes creating a relationship between the third set of volumes 304c and the fourth set of volumes 304d, as shown in FIG. Figure 3C As shown by arrow 313 in FIG.

[0078] In addition, before continuing with the recovery I / O phase, and after the third control unit 302c to the fourth control unit 302d replication has been successfully started, the system will replace the HyperSwap configuration between the first and second control units 302a, 302b with the corresponding HyperSwap configuration between the third and fourth control units 302c, 302d. This may include deleting the HyperSwap configuration between the first control unit 302a and the third control unit 302c, which is no longer needed.

[0079] Once HyperSwap is fully enabled between the third control unit 302c and the fourth control unit 302d, the system will then proceed to the resume I / O phase, where the I / O operations that have been queued during the migration are executed for the third control unit 302c and mirrored to the fourth control unit 302d. After the resume I / O is complete, work can continue on the new volume 304c (i.e., the volume 304c migrated to) on the third control unit 302c, which now acts as the primary control unit of the system, and the migration is complete, except for some cleanup operations.

[0080] After the migration is completed, the system may automatically or manually allow the user to terminate the relationship between the first and second control units 302a, 302b, such as Figure 3C Furthermore, after the migration is complete and the relationship between the first and second control units 302a, 302b has been terminated, the resulting configuration looks like Figure 3C The configuration shown in .

[0081] Reference now Figure 4 , a flow chart of an example method 400 for migrating from an old storage system to a new storage system using multi-storage volume swap according to an embodiment of the present disclosure is shown. The method 400 may be performed by hardware, firmware, software executed on a processor, or any combination thereof. For example, the method 400 may be performed by a processor (e.g., in a host device 232).

[0082] The method may begin at operation 402, where a system (e.g., a storage system / server) or a storage subsystem (e.g., if integrated with computer hardware in a server) may receive a request to migrate to a new primary storage system and a new secondary storage system (e.g., a new storage device, also referred to herein as a control unit). This may be done, for example, during a hardware upgrade where an old storage device is replaced with a new storage device.

[0083] In operation 404, the system begins copying data from the old primary storage system to the new primary and secondary storage systems. In some embodiments, operation 404 may include one or more sub-operations. The one or more sub-operations may include first identifying suitable storage devices to act as the new primary storage system and the new secondary storage system. One or more suitable replacement source storage devices in the replacement source storage subsystem may be automatically identified with little or no operator intervention. For example, in response to a command to initiate a change to a source storage unit, the copy management software may automatically identify a list of candidate replacement source storage devices and present the list of candidate replacement source storage devices to the operator in a suitable user interface. In response, the operator may select a suitable replacement source storage device from the list of candidate replacement source storage devices. In one embodiment, the candidate replacement source storage devices in the storage subsystem may have been defined as being managed by the storage management software.

[0084] In the above example, the copy management software can fully automatically identify a list of candidate replacement source storage devices and present the list of candidate replacement source storage units to an operator in a suitable user interface. In response, the operator can select a suitable replacement source storage device from the list of candidate replacement source storage devices. In this way, replacement source storage devices can be identified in a primarily automatic manner. In other embodiments, replacement source storage devices can be identified fully automatically, i.e., without human intervention, or can be identified manually by a human operator, and the selection manually entered into a graphical user interface.

[0085] Operation 404 may also include identifying the copy relationships to be migrated to the new primary storage system and the new secondary storage system. In some embodiments, the copy management software may fully automatically identify a list of candidate copy relationships to be migrated in response to a command to initiate a change in the primary and secondary storage devices, and present the list of candidate copy relationships to be migrated to an operator in a suitable user interface. In response, a human operator may select one or more suitable copy relationships to be migrated from the list of candidate replacement copy relationships to be migrated. In this way, replacement copy relationships to be migrated may be identified in a primarily automatic manner. In other embodiments, the copy relationships may be automatically identified by the system. For example, the system may determine that all copy relationships between the old primary storage system and the old secondary storage system may be migrated to the new primary storage system and the new secondary storage system.

[0086] Operation 404 may also include identifying a set of volumes on the new primary storage system and the new secondary storage system that will include the replicated data from the old storage system. In some embodiments, this may involve creating a new set of volumes on each of the new primary storage system and the new secondary storage system. A new set of volumes may be created so that the new primary storage system and the new secondary storage system have volumes corresponding to each volume being migrated. In other embodiments, a set of volumes may already exist on the new primary storage system and the new secondary storage system. In these embodiments, the storage manager may use a target volume matching algorithm to create a copy relationship pairing between the volumes of the old primary storage subsystem and the volumes of the new source storage system based on volume size and type. The system may then begin replicating data from the old primary storage system to the new primary and secondary storage systems.

[0087] At operation 406, once the migration threshold of the new primary storage system and the new secondary storage system has been reached, the old storage system and the new storage system can be placed in a migration mode. As discussed herein, the threshold can be an amount of data such that the amount of time required for the system to reach a full-duplex state is low enough so as not to significantly impact application performance. Additionally, at operation 408, the replication mode between the old primary storage system and the new primary storage system and the new secondary storage system is converted to synchronous. This ensures that new I / O writes executed against the old primary storage system are also executed against both the new primary storage system and the new secondary storage system, thereby ensuring data integrity.

[0088] In operation 410, once full-duplex mode or state is reached, multi-storage volume swap (e.g., HyperSwap) is enabled between the old primary storage system and the new primary storage system. As discussed herein, enabling multi-storage volume swap means that the applicable program (e.g., HyperSwap) is aware (e.g., from the CSM) of all volumes that are part of the multi-storage volume swap session and has confirmed that it can actually access those volumes. It may also include the multi-storage volume swap program confirming that all volume pairs are currently in full-duplex state and are mirrored.

[0089] At operation 412, migration is initiated. In some embodiments, once full duplex state for migration has been achieved and HyperSwap has been enabled, the storage management may automatically issue a migration command. For example, according to the present specification, a multi-volume swap command automatically issued by the storage management may be HyperSwap will first temporarily stop I / O operations while the swap occurs. In some embodiments, I / O operations that have already started when the multi-volume swap is initiated may be allowed to complete. Any subsequent I / O operations may be placed in a queue on the initiating host to await completion of the multi-volume swap operation. It will be appreciated that in other embodiments, the stopping of I / O operations may be performed manually.

[0090] Once the I / O operations have been stopped, a multi-storage volume swap is initiated from the old primary storage system to the new primary storage system and the new secondary storage system, and the old storage system is migrated to the new storage system, and the method 400 ends. Figure 5 The method 500 discussed is an illustrative example of sub-operations that may be performed to migrate from an old storage system to a new storage system at operation 412 .

[0091] Reference now Figure 5 , a flow chart of an example method 500 for migrating from an old storage system to a new storage system using multi-storage volume swap according to an embodiment of the present disclosure is shown. The method 500 may be performed by hardware, firmware, software executed on a processor, or any combination thereof. For example, the method 500 may be performed by a processor (e.g., in a host device 232).

[0092] Method 500 may begin at operation 502, where a swap phase may be performed. In some embodiments, a storage manager may automatically issue a swap start command. The swap start command may prepare the system to swap volumes from the old primary storage system to volumes of the new primary storage system and the new secondary storage system. In some embodiments, the swap start command may be automatically sent once full duplex of the copy relationship pair of the old primary storage system and the new primary storage system and the new secondary storage system has been reached.

[0093] In response to the swap start command, the system may freeze and stop I / O. This is shown in operation 504. Any unexecuted I / O commands, including new I / O commands received after I / O was frozen, may be stored in an I / O queue.

[0094] In operation 506, the relationship between the old primary storage system and the new primary storage system can be terminated. This action can be performed now because the old primary storage system and the new primary storage system have reached full-duplex state at this time, and because I / O operations have been frozen, it is ensured that they remain in full-duplex state.

[0095] At operation 508, the system switches to the new primary storage system. In some embodiments, the system may be modified according to the present specification such as The multi-storage volume swap function is provided to provide a swap of volumes from the original source storage subsystem to the volumes of the replacement source storage subsystem. function to facilitate migration operations.

[0096] At operation 510, the relationship between the old primary storage system and the new secondary storage system may be terminated. This may not be done until full duplex mode / state is reached. Once full duplex mode / state is reached and I / O operations have ceased, no further data need to be copied to the new secondary storage system before the migration is complete, at which point it will be in a copy relationship with the new primary data system. Thus, the relationship between the old primary storage system and the new secondary storage system is no longer needed.

[0097] In operation 512, a synchronous replication relationship is established between the new primary storage system and the new secondary storage system. In addition, a multi-storage swap configuration (e.g., a HyperSwap configuration) is created for the new primary storage system and the new secondary storage system. This is shown in operation 514. The creation of the synchronous replication relationship and the multi-storage swap configuration between the new primary storage system and the new secondary storage system implements high availability and failover functionality, and ensures data integrity between the new storage systems.

[0098] At operation 516, an I / O recovery operation is performed, and queued I / O operations are performed on the new primary storage system and the new secondary storage system. Then at operation 518, any necessary cleanup operations are performed on the new storage system, and the method 500 ends. The cleanup operations performed at operation 518 may include terminating the relationship between the old storage devices. For example, the synchronous mirror relationship between the old primary storage system and the old secondary storage system may be terminated. In addition, during the cleanup operation 518, a multi-storage swap configuration (e.g., a HyperSwap configuration) between the old primary storage system and the old secondary storage system is deleted.

[0099] As can be seen from the above, storage management according to the present specification can provide an automated process to migrate data from one source volume to another source volume while maintaining disaster recovery capabilities and substantially avoiding the extra data and data copies that typically result from using previous processes. Therefore, disaster recovery capabilities can be maintained throughout the data migration period. In addition, the migration operation can be completed with very short or no interruption to ongoing I / O operations. As a result, it is believed that users will be able to migrate data in situations that may have been impractical previously, such as when performing business-critical work.

[0100] Thus, in one aspect of the present specification, a storage system configured for disaster recovery can be migrated with little or no impact on the disaster recovery capabilities between the original primary volume and the secondary volume. The multi-storage volume swap function can be modified to automatically migrate data to a new source storage subsystem without the user having to manually remove existing copy relationships or create new copy relationships. It is believed that storage management according to this specification can save users considerable time while reducing the chance of errors that may occur when trying to manually create thousands of copy relationship pairs.

[0101] Reference now Figure 6 , shows a high-level block diagram of an example computer system 601 according to an embodiment of the present disclosure, which can be used to implement one or more of the methods, tools, and modules described herein and any related functionality (e.g., using one or more processor circuits of a computer or a computer processor). In some embodiments, the main components of the computer system 601 may include one or more CPUs 602, a memory subsystem 604, a terminal interface 612, a storage interface 616, an I / O (input / output) device interface 614, and a network interface 618, all of which can be directly or indirectly communicatively coupled for inter-component communication via a memory bus 603, an I / O bus 608, and an I / O bus interface unit 610.

[0102] Computer system 601 may include one or more general purpose programmable central processing units (CPUs) 602A, 602B, 602C, and 602D, generally referred to herein as CPU 602. In some embodiments, computer system 601 may include multiple processors typical of relatively large systems; however, in other embodiments, computer system 601 may instead be a single CPU system. Each CPU 602 may execute instructions stored in memory subsystem 604 and may include one or more levels of onboard cache.

[0103] System memory 604 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 622 or cache memory 624. Computer system 601 may also include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 626 may be provided for reading from and writing to non-removable, non-volatile magnetic media such as "hard drives". Although not shown, a disk drive for reading from and writing to a removable, non-volatile disk (e.g., "floppy disk") may be provided, or an optical drive or other optical medium for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM, etc. may be provided. In addition, memory 604 may include flash memory, such as a flash stick drive or a flash drive. The memory device may be connected to memory bus 603 via one or more data medium interfaces. Memory 604 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of different embodiments.

[0104] One or more programs / utilities 628 may be stored in memory 604, each having at least one set of program modules 630. Programs / utilities 628 may include a hypervisor (also referred to as a virtual machine monitor), one or more operating systems, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data, or some combination thereof, may include an implementation of a networking environment. Program modules 630 generally perform the functions or methods of various embodiments.

[0105] Although the memory bus 603 is Figure 6603 may include multiple different buses or communication paths, which may be arranged in any of a variety of forms, such as hierarchical point-to-point links, star or mesh configurations, multi-layer buses, parallel and redundant paths, or any other suitable type of configuration. In addition, although the I / O bus interface 610 and the I / O bus 608 are shown as a single corresponding unit, in some embodiments, the computer system 601 may include multiple I / O bus interface units 610, multiple I / O buses 608, or both. In addition, although multiple I / O interface units are shown to separate the I / O bus 608 from the various communication paths extending to various I / O devices, in other embodiments, some or all of the I / O devices may be directly connected to one or more system I / O buses.

[0106] In some embodiments, computer system 601 can be a multi-user mainframe computer system, a single-user system, or a server computer, or a similar device with little or no direct user interface but receiving requests from other computer systems (clients). In addition, in some embodiments, computer system 601 can be implemented as a desktop computer, a portable computer, a laptop or notebook computer, a tablet computer, a pocket computer, a phone, a smart phone, a network switch or router, or any other suitable type of electronic device.

[0107] Notice, Figure 6 The main components of the exemplary computer system 601 are intended to be depicted. However, in some embodiments, the various components may have more Figure 6 The greater or lesser complexity represented in , may exist different from Figure 6 Those components shown in or in addition to them, and the number, type and configuration of these components can vary. In addition, the modules are illustratively listed and described according to the embodiments, and the modules are not intended to indicate the necessity of a specific module or the exclusivity of other potential modules (or the function / purpose applied to a specific module).

[0108] It is understood in advance that although the present disclosure includes detailed descriptions about cloud computing, the implementation of the teachings recorded herein is not limited to a cloud computing environment. Instead, embodiments of the present invention can be implemented in conjunction with any other type of computing environment now known or later developed.

[0109] Cloud computing is a service delivery model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be quickly provisioned and released with minimal management effort or interaction with the provider of the service. The cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

[0110] Features are as follows:

[0111] On-demand self-service: Cloud consumers can unilaterally and automatically provision computing capabilities, such as server time and network storage, as needed without requiring manual interaction with the service provider.

[0112] Wide Area Network Access: Capabilities are available over the network and accessed through standard mechanisms that facilitate use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

[0113] Resource pooling: A provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, where different physical and virtual resources are dynamically allocated and reallocated based on demand. There is a sense of location independence, as consumers typically have no control or knowledge of the exact location of the resources provided, but can specify the location at a higher level of abstraction (e.g., country, state, or data center).

[0114] Rapid elasticity: In some cases, the ability to scale out quickly and in quickly can be provisioned quickly and elastically. To the consumer, the capacity available for provisioning often appears to be unlimited and can be purchased in any quantity at any time.

[0115] Metered Services: Cloud systems automatically control and optimize resource usage by leveraging metering capabilities at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to both providers and consumers of the utilized services.

[0116] The service model is as follows:

[0117] Software as a Service (SaaS): The capability provided to the consumer is to use the provider's applications running on the cloud infrastructure. The applications are accessible from a variety of client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including the network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

[0118] Platform as a Service (PaaS): The capability provided to consumers is to deploy consumer-created or acquired applications onto cloud infrastructure, where the applications are created using programming languages ​​and tools supported by the provider. Consumers do not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but have control over deployed applications and possible configuration of the application hosting environment.

[0119] Infrastructure as a Service (IaaS): The capabilities provided to consumers are processing, storage, networking, and other basic computing resources on which consumers can deploy and run arbitrary software, which may include operating systems and applications. Consumers do not manage or control the underlying cloud infrastructure, but have control over the operating system, storage, deployed applications, and possibly limited control over selected networking components (e.g., host firewalls).

[0120] The deployment model is as follows:

[0121] Private Cloud: The cloud infrastructure is operated only for the organization. It can be managed by the organization or a third party and can exist on-premises or off-premises.

[0122] Community cloud: The cloud infrastructure is shared by several organizations and supports a specific community with shared concerns (e.g., mission, security requirements, policies, and compliance considerations). It can be managed by the organization or a third party and can exist on-premises or off-premises.

[0123] Public cloud: Cloud infrastructure is available to the general public or large industrial groups and is owned by an organization that sells cloud services.

[0124] Hybrid cloud: A cloud infrastructure is a combination of two or more clouds (private, community or public) that remain a unique entity but are bound together by standardized or proprietary technologies that enable data and application portability (e.g., cloud bursting for load balancing between clouds).

[0125] The cloud computing environment is service-oriented, with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the core of cloud computing is an infrastructure consisting of a network of interconnected nodes.

[0126] Reference now Figure 7, depicts an illustrative cloud computing environment 50. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 10 with which a local computing device used by a cloud consumer can communicate, such as a personal digital assistant (PDA) or cellular phone 54A, a desktop computer 54B, a laptop computer 54C, and / or an automobile computer system 54N. The nodes 10 can communicate with each other. They can be physically or virtually grouped (not shown) in one or more networks, such as a private cloud, community cloud, public cloud, or hybrid cloud, or a combination thereof, as described above. This allows the cloud computing environment 50 to provide infrastructure, platform, and / or software as a service for which the cloud consumer does not need to maintain resources on a local computing device. It should be understood that Figure 7 The types of computing devices 54A-N shown in are intended to be illustrative only, and computing node 10 and cloud computing environment 50 may communicate with any type of computerized device over any type of network and / or network addressable connection (eg, using a web browser).

[0127] Reference now Figure 8 , showing the cloud computing environment 50 ( Figure 7 ) provides a set of functional abstraction layers. It should be understood in advance that Figure 8 The components, layers, and functions shown in are intended to be illustrative only, and embodiments of the present invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

[0128] The hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; servers based on RISC (Reduced Instruction Set Computer) architecture 62; servers 63; blade servers 64; storage devices 65; and networks and network components 66. In some embodiments, software components include network application server software 67 and database software 68.

[0129] Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities can be provided: virtual servers 71 ; virtual storage 72 ; virtual networks 73 , including virtual private networks; virtual applications and operating systems 74 ; and virtual clients 75 .

[0130] In one example, the management layer 80 may provide the functionality described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources for performing tasks within a cloud computing environment. Metering and pricing 82 provides cost tracking when resources are utilized within a cloud computing environment, and bills or invoices for the consumption of these resources. In one example, these resources may include application software licenses. Security provides authentication for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management so that the required service levels are met. Service level agreement (SLA) planning and fulfillment 85 provides pre-scheduling and procurement of cloud computing resources in anticipation of future demand for the cloud computing resources based on the SLA.

[0131] The workload layer 90 provides examples of functionality that can take advantage of a cloud computing environment. Examples of workloads and functionality that can be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and storage migration 96. Storage migration 96 may include instructions for performing various functions disclosed herein, such as enabling migration of an old primary storage system and an old secondary storage system to a new primary storage system and a new secondary storage system while maintaining high availability and Function.

[0132] The present invention may be a system, method and / or computer program product. The computer program product may include a computer-readable storage medium (or multiple media) having computer-readable program instructions thereon, the computer-readable program instructions being used to cause a processor to perform various aspects of the present invention.

[0133] Computer readable storage medium can be a tangible device that can retain and store instructions for use by instruction execution devices. Computer readable storage medium can be, for example but not limited to, electronic storage device, magnetic storage device, optical storage device, electromagnetic storage device, semiconductor storage device, or any suitable combination of the above. A non-exhaustive list of more specific examples of computer readable storage medium includes the following: portable computer disk, hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanical encoding device such as punch card or protruding structure in groove (with instructions recorded thereon), and any suitable combination of the above. Computer readable storage medium as used herein should not be interpreted as temporary signal itself, such as radio wave, or other free propagating electromagnetic wave, propagation through waveguide, or other transmission media (e.g., light pulse passing through fiber optic cable) electromagnetic wave, or electrical signal emitted by wire.

[0134] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device, or to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network, and forwards the computer-readable program instructions to be stored in a computer-readable storage medium in the corresponding computing / processing device.

[0135] The computer-readable program instructions for performing the operation of the present invention can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Smalltalk, C++, etc.) and traditional process programming languages ​​(such as "C" programming language or similar programming languages). The computer-readable program instructions can be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or executed completely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer through any type of network (including a local area network (LAN) or a wide area network (WAN)), or can be connected to an external computer (for example, using an Internet service provider through the Internet). In certain embodiments, the electronic circuit including, for example, a programmable logic circuit, a field programmable gate array (FPGA) or a programmable logic array (PLA) can be executed by using the state information of the computer-readable program instructions to personalize the electronic circuit to perform computer-readable program instructions, so as to perform various aspects of the present invention.

[0136] Various aspects of the present invention are described herein with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present invention. It should be understood that each frame of the flowchart and / or block diagram, and the combination of frames in the flowchart and / or block diagram, can be implemented by computer-readable program instructions.

[0137] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / actions specified in the box or multiple boxes of the flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium, which instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable storage medium having the instructions stored therein includes an article of manufacture, which includes instructions for implementing various aspects of the functions / actions specified in the box or multiple boxes of the flowchart and / or block diagram.

[0138] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce computer-implemented processing, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in the box or multiple boxes in the flowchart and / or block diagram.

[0139] The flow charts and block diagrams in the accompanying drawings show the architecture, functions and operations of the possible implementations of the system, method and computer program product according to different embodiments of the present invention. To this end, each frame in the flow chart or block diagram may represent a module, segment or part of an instruction, which includes one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the frame may not occur in the order marked in the figure. For example, the two frames shown in succession can actually be completed as a step, and are executed simultaneously, substantially simultaneously, in a partially or completely overlapping manner in time, or the frame can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each frame in the block diagram and / or flow chart, and the combination of frames in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or action or performs a combination of dedicated hardware and computer instructions.

[0140] The terms used herein are only used for the purpose of describing specific embodiments, and it is not intended to limit various embodiments. As used herein, the singular forms "one", "an" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "including" and / or "comprising" when used in this specification specify the existence of stated features, integers, steps, operations, elements and / or components, but do not exclude the existence or addition of one or more other features, integers, steps, operations, elements, components and / or their groups. In the previous detailed description of the example embodiments of various embodiments, reference is made to the accompanying drawings (wherein the same reference numerals represent the same elements), which form a part of the present invention, and wherein specific example embodiments in which various embodiments can be practiced are illustrated by way of illustration. These embodiments are described in sufficient detail to enable those skilled in the art to practice these embodiments, but other embodiments may be used, and logical, mechanical, electrical and other changes may be made without departing from the scope of the various embodiments. In the previous description, many specific details are set forth to provide a thorough understanding of the various embodiments. However, various embodiments may be implemented without these specific details. In other examples, in order not to obscure the embodiments, known circuits, structures and techniques are not shown in detail.

[0141] As used herein, "plurality" when used to refer to an item means one or more items. For example, "plurality of different types of networks" is one or more different types of networks.

[0142] When different reference numerals include a common numeral followed by different letters (e.g., 100a, 100b, 100c) or a punctuation mark followed by different numbers (e.g., 100-1, 100-2 or 100.1, 100.2), the reference character used alone without a letter or following number (e.g., 100) may refer to the group of elements as a whole, any subset of the group, or an example sample of the group.

[0143] Additionally, when used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items can be used, and only one of each item in the list may be required. In other words, "at least one of" refers to any combination of items, and multiple items from the list can be used, but not all items in the list are required. An item can be a specific object, thing, or category.

[0144] For example, but not limited to, "at least one of item A, item B, or item C" may include item A, item A and item B, or item B. This example may also include item A, item B, and item C, or item B and item C. Of course, there may be any combination of these items. In some illustrative examples, "at least one" may be, for example, but not limited to, two items A; one item B; and ten items C; four items B and seven items C; or other suitable combinations.

[0145] In the foregoing, reference has been made to various embodiments. However, it should be understood that the present disclosure is not limited to the specifically described embodiments. On the contrary, any combination of the described features and elements is contemplated to implement and practice the present disclosure, regardless of whether or not it relates to different embodiments. Many modifications, changes and variations are apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. In addition, although the embodiments of the present disclosure may achieve advantages that are superior to other possible solutions or superior to the prior art, whether a given embodiment achieves a specific advantage is not a limitation of the present disclosure. Therefore, the described aspects, features, embodiments and advantages are merely illustrative and are not considered to be elements or limitations of the appended claims unless explicitly stated in the claims. In addition, the following claims should be interpreted as covering all such changes and modifications that fall within the true spirit and scope of the present invention.

[0146] A non-limiting list of example embodiments is provided below to illustrate some aspects of the present disclosure.

[0147] Example embodiment 1 is a method. The method includes receiving a command to migrate from a first storage system to a second storage system, wherein the first storage system includes a first primary storage device and a first secondary storage device, and wherein the second storage system includes a second primary storage device and a second secondary storage device. The method also includes, in response to receiving the command, initiating data replication between the first primary storage device and the second primary storage device. The method also includes, in response to receiving the command, initiating data replication between the first primary storage device and the second secondary storage device. The method also includes migrating from the first storage system to the second storage system.

[0148] Example embodiment 2 includes the method of example embodiment 1, including or excluding optional features. In this example embodiment, initiating data replication between the first primary storage device and the second primary storage device includes: identifying a first set of volumes to be migrated on the first primary storage device, identifying a suitable second set of volumes on the second primary storage device for receiving the first set of volumes, and mirroring the data of the first set of volumes onto the second set of volumes. Optionally, the method further includes: initiating data replication between the first primary storage device and the second secondary storage device by identifying a suitable third set of volumes on the second secondary storage device for receiving the first set of volumes and mirroring the data of the first set of volumes onto the third set of volumes.

[0149] Example embodiment 3 includes the method of any one of example embodiments 1 to 2, including or excluding optional features. In this example embodiment, initiating data replication between the first primary storage device and the second secondary storage device includes: identifying a first set of volumes to be migrated on the first primary storage device. Initiating data replication also includes: creating a second set of volumes on the second primary storage device for receiving the first set of volumes. The second set of volumes has attributes suitable for receiving the data of the first set of volumes. Initiating data replication also includes: mirroring the data of the first set of volumes onto the second set of volumes. Optionally, the attributes include volume size and type. Optionally, the method also includes: initiating data replication between the first primary storage device and the second secondary storage device by creating a suitable third set of volumes on the second secondary storage device for receiving the first set of volumes. The third set of volumes has attributes suitable for receiving the data of the first set of volumes. Initiating data replication also includes: mirroring the data of the first set of volumes onto the third set of volumes.

[0150] Example embodiment 4 includes the method of any one of example embodiments 1 to 3, including or excluding optional features. In this example embodiment, the method includes: in response to data replication between the first primary storage device and both the second primary storage device and the secondary storage device reaching a threshold completion level, before migrating from the first storage system to the second storage system, preparing the second storage system for migration. Optionally, preparing the second storage system for migration includes: converting the replication mode between the first primary storage device and the second primary storage device to synchronization, and converting the replication mode between the first primary storage device and the second secondary storage device to synchronization. Optionally, preparing the second storage system for migration also includes: in response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second secondary storage device, enabling multi-storage volume swapping between the first primary storage device and the second primary storage device.

[0151] Example embodiment 5 includes the method of any one of example embodiments 1 to 4, including or excluding optional features. In this example embodiment, migrating from the first storage system to the second storage system is in response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device. Optionally, migrating from the first storage system to the second storage system includes pausing I / O operations and storing received I / O operations in a queue for subsequent processing. Optionally, migrating from the first storage system to the second storage system also includes: terminating the data replication relationship between the first primary storage device and the second auxiliary storage device, enabling a synchronous data replication relationship between the second primary storage device and the second auxiliary storage device, and enabling multi-storage volume exchange between the second primary storage device and the second auxiliary storage device. Optionally, migrating from the first storage system to the second storage system also includes: executing queued I / O operations on the second primary storage device.

[0152] Example embodiment 6 includes the method of any one of example embodiments 1 to 5, including or excluding optional features. In this example embodiment, the first primary storage device is initially configured to mirror data to the first secondary storage device. The method also includes: after migrating to the second storage system, terminating the relationship between the first primary storage device and the first secondary storage device, and performing new I / O operations on the second storage system. Optionally, data may not be mirrored between the first primary storage device and the first secondary storage device. This may be the result of an error in, for example, the first secondary storage device or a communication network between the first primary storage device and the first secondary storage device.

[0153] Example embodiment 7 is a system. The system includes a memory and a processor communicatively coupled to the memory, wherein the processor is configured to perform a method. The method includes: receiving a command to migrate from a first storage system to a second storage system, wherein the first storage system includes a first primary storage device and a first secondary storage device, and wherein the second storage system includes a second primary storage device and a second secondary storage device. The method also includes: in response to receiving the command, starting data replication between the first primary storage device and the second primary storage device. The method also includes: in response to receiving the command, starting data replication between the first primary storage device and the second secondary storage device. The method also includes: migrating from the first storage system to the second storage system.

[0154] Example embodiment 8 includes the system of example embodiment 7, including or excluding optional features. In this example embodiment, initiating data replication between the first primary storage device and the second primary storage device includes: identifying a first set of volumes on the first primary storage device to be migrated, identifying a suitable second set of volumes on the second primary storage device for receiving the first set of volumes, and mirroring data of the first set of volumes onto the second set of volumes.

[0155] Example embodiment 9 includes the system of any one of example embodiments 7 to 8, including or excluding optional features. In this example embodiment, the method further includes: in response to data replication between the first primary storage device and both the second primary storage device and the secondary storage device reaching a threshold completion level, before migrating from the first storage system to the second storage system, preparing the second storage system for migration. Optionally, preparing the second storage system for migration includes: converting the replication mode between the first primary storage device and the second primary storage device to synchronous, and converting the replication mode between the first primary storage device and the second secondary storage device to synchronous. Optionally, preparing the second storage system for migration also includes: in response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second secondary storage device, enabling multi-storage volume swapping between the first primary storage device and the second primary storage device.

[0156] Example embodiment 10 includes the system described in any one of example embodiments 7 to 9, including or excluding optional features. In this example embodiment, migration from the first storage system to the second storage system is in response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device. Optionally, migration from the first storage system to the second storage system includes: pausing I / O operations and storing received I / O operations in a queue for subsequent processing. Optionally, migration from the first storage system to the second storage system also includes: terminating the data replication relationship between the first primary storage device and the second auxiliary storage device, enabling a synchronous data replication relationship between the second primary storage device and the second auxiliary storage device, and enabling multi-storage volume exchange between the second primary storage device and the second auxiliary storage device.

[0157] Example embodiment 11 is a computer program product, which includes a computer-readable storage medium having program instructions contained therein. The computer-readable medium includes instructions for directing the processor to perform a method. The method includes: receiving a command to migrate from a first storage system to a second storage system, wherein the first storage system includes a first primary storage device and a first auxiliary storage device, and wherein the second storage system includes a second primary storage device and a second auxiliary storage device. The method also includes: in response to receiving the command, starting data replication between the first primary storage device and the second primary storage device. The method also includes: in response to receiving the command, starting data replication between the first primary storage device and the second auxiliary storage device. The method also includes: migrating from the first storage system to the second storage system.

[0158] Example embodiment 12 includes the computer-readable medium of example embodiment 11, including or excluding optional features. In this example embodiment, the method further includes preparing the second storage system for migration before migrating from the first storage system to the second storage system in response to the data replication between the first primary storage device and both the second primary storage device and the secondary storage device reaching a threshold completion level.

[0159] Example embodiment 13 includes the computer-readable medium of any one of example embodiments 11 to 12, including or excluding the optional features. In this example embodiment, preparing the second storage system for migration includes: converting the replication mode between the first primary storage device and the second primary storage device to synchronization, converting the replication mode between the first primary storage device and the second auxiliary storage device to synchronization, and in response to reaching a full-duplex state between the first primary storage device and the second primary storage device and the second auxiliary storage device, enabling multiple storage volume swapping between the first primary storage device and the second primary storage device.

[0160] Example embodiment 14 is a method. The method includes receiving a command to migrate from a first storage system to a second storage system. The first storage system includes a first primary storage device and a first auxiliary storage device, and the second storage system includes a second primary storage device and a second auxiliary storage device. The method also includes, in response to receiving the command, copying data between the first primary storage device and the second primary storage device. The method also includes, in response to receiving the command, copying data between the first primary storage device and the second auxiliary storage device. The method also includes, in response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device, suspending the received I / O operation for execution on the first storage system, storing the I / O operation in a queue, and enabling multi-storage volume exchange between the second primary storage device and the second auxiliary storage device. The method also includes migrating from the first storage system to the second storage system so that the newly received I / O operation is executed on the second storage system. The method also includes resuming the I / O operation and executing the queued I / O operation on the second storage system.

[0161] Example embodiment 15 is a system. The system includes a memory and a processor communicatively coupled to the memory. The processor is configured to perform a method. The method includes: receiving a command to migrate from a first storage system to a second storage system. The first storage system includes a first primary storage device and a first auxiliary storage device, and the second storage system includes a second primary storage device and a second auxiliary storage device. The method also includes, in response to receiving the command, copying data between the first primary storage device and the second primary storage device. The method also includes: in response to receiving the command, copying data between the first primary storage device and the second auxiliary storage device. The method also includes: in response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device, suspending the received I / O operation for execution on the first storage system, storing the I / O operation in a queue, and enabling multi-storage volume exchange between the second primary storage device and the second auxiliary storage device. The method also includes: migrating from the first storage system to the second storage system so that the newly received I / O operation is executed on the second storage system. The method also includes resuming the I / O operations and executing the queued I / O operations on the second storage system.

Claims

1. A method, include: receiving a command to migrate from a first storage system to a second storage system, wherein the first storage system includes a first primary storage device and a first secondary storage device, and wherein the second storage system includes a second primary storage device and a second secondary storage device; In response to receiving the command, starting data replication between the first primary storage device and the second primary storage device; In response to receiving the command, starting data replication between the first primary storage device and the second secondary storage device; and Migrate from the first storage system to the second storage system.

2. The method according to claim 1, in, Initiating data replication between the first main storage device and the second main storage device includes: identifying, on the first primary storage device, a first set of volumes to be migrated; identifying, on the second primary storage device, a suitable second set of volumes for receiving the first set of volumes; and The data of the first set of volumes is mirrored onto the second set of volumes.

3. The method according to claim 1, in, Starting data replication between the first primary storage device and the second auxiliary storage device includes: identifying, on the first primary storage device, a first set of volumes to be migrated; creating a second set of volumes on the second primary storage device for receiving the first set of volumes, the second set of volumes having properties suitable for receiving the data of the first set of volumes; and The data of the first set of volumes is mirrored onto the second set of volumes.

4. The method according to claim 3, in, The attributes include volume size and type.

5. The method according to claim 1, further comprising: include: In response to the data replication between the first primary storage device and both the second primary storage device and the second secondary storage device reaching a threshold completion level, prior to migrating from the first storage system to the second storage system, preparing the second storage system for migration.

6. The method according to claim 5, in, Preparing the second storage system for migration includes: converting a replication mode between the first primary storage device and the second primary storage device into synchronization; and The replication mode between the first primary storage device and the second secondary storage device is converted to synchronization.

7. The method according to claim 6, in, Preparing the second storage system for migration further includes: In response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device, multi-storage volume swapping between the first primary storage device and the second primary storage device is enabled.

8. The method according to claim 1, in, Migrating from the first storage system to the second storage system is in response to achieving a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device.

9. The method according to claim 8, in, Migrating from the first storage system to the second storage system includes: Suspend I / O operations; and The received I / O operations are stored in a queue for subsequent processing.

10. The method according to claim 9, in, Migrating from the first storage system to the second storage system further includes: terminating the data replication relationship between the first primary storage device and the second auxiliary storage device; enabling a synchronous data replication relationship between the second primary storage device and the second secondary storage device; and Multi-storage volume swapping between the second primary storage device and the second secondary storage device is enabled.

11. The method according to claim 10, in, Migrating from the first storage system to the second storage system further includes: The queued I / O operation is performed on the second primary storage device.

12. The method according to claim 1, in, The first primary storage device is initially configured to mirror data to the first secondary storage device, the method further comprising: After migrating to the second storage system, terminating the relationship between the first primary storage device and the first auxiliary storage device; and A new I / O operation is performed on the second storage system.

13. A system, include: Memory; as well as a processor communicatively coupled to the memory, wherein the processor is configured to perform a method comprising: receiving a command to migrate from a first storage system to a second storage system, wherein the first storage system includes a first primary storage device and a first secondary storage device, and wherein the second storage system includes a second primary storage device and a second secondary storage device; In response to receiving the command, starting data replication between the first primary storage device and the second primary storage device; In response to receiving the command, starting data replication between the first primary storage device and the second secondary storage device; and Migrate from the first storage system to the second storage system.

14. The system according to claim 13, in, Initiating data replication between the first main storage device and the second main storage device includes: identifying, on the first primary storage device, a first set of volumes to be migrated; identifying, on the second primary storage device, a suitable second set of volumes for receiving the first set of volumes; and The data of the first set of volumes is mirrored onto the second set of volumes.

15. The system according to claim 13, in, The method further comprises: In response to the data replication between the first primary storage device and both the second primary storage device and the second secondary storage device reaching a threshold completion level, prior to migrating from the first storage system to the second storage system, preparing the second storage system for migration.

16. The system according to claim 15, in, Preparing the second storage system for migration includes: converting a replication mode between the first primary storage device and the second primary storage device into synchronization; and The replication mode between the first primary storage device and the second secondary storage device is converted to synchronization.

17. The system according to claim 16, in, Preparing the second storage system for migration further includes: In response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device, multi-storage volume swapping between the first primary storage device and the second primary storage device is enabled.

18. The system according to claim 13, in, Migrating from the first storage system to the second storage system is in response to achieving a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device.

19. The system according to claim 18, in, Migrating from the first storage system to the second storage system includes: Suspend I / O operations; and The received I / O operations are stored in a queue for subsequent processing.

20. The system according to claim 19, in, Migrating from the first storage system to the second storage system further includes: terminating the data replication relationship between the first primary storage device and the second auxiliary storage device; enabling a synchronous data replication relationship between the second primary storage device and the second secondary storage device; and Multi-storage volume swapping between the second primary storage device and the second secondary storage device is enabled.

21. A computer program product comprising a computer-readable storage medium having program instructions, wherein the program instructions are executable by a computer to perform a method, wherein the method include: receiving a command to migrate from a first storage system to a second storage system, wherein the first storage system includes a first primary storage device and a first secondary storage device, and wherein the second storage system includes a second primary storage device and a second secondary storage device; In response to receiving the command, starting data replication between the first primary storage device and the second primary storage device; In response to receiving the command, starting data replication between the first primary storage device and the second secondary storage device; and Migrate from the first storage system to the second storage system.

22. The computer program product according to claim 21, in, The method further comprises: In response to the data replication between the first primary storage device and both the second primary storage device and the second secondary storage device reaching a threshold completion level, prior to migrating from the first storage system to the second storage system, preparing the second storage system for migration.

23. The computer program product according to claim 21, in, Preparing the second storage system for migration includes: converting a replication mode between the first primary storage device and the second primary storage device into synchronization; converting a replication mode between the first primary storage device and the second secondary storage device to synchronization; and In response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device, multi-storage volume swapping between the first primary storage device and the second primary storage device is enabled.

24. A method, include: receiving a command to migrate from a first storage system to a second storage system, wherein the first storage system includes a first primary storage device and a first secondary storage device, and wherein the second storage system includes a second primary storage device and a second secondary storage device; In response to receiving the command, copying data between the first primary storage device and the second primary storage device; In response to receiving the command, copying data between the first primary storage device and the second secondary storage device; In response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device: pausing the received I / O operation for execution on the first storage system; storing the I / O operations in a queue; and enabling multi-storage volume exchange between the second primary storage device and the second auxiliary storage device; Migrating from the first storage system to the second storage system so that a newly received I / O operation is performed on the second storage system; Resuming I / O operations; and The queued I / O operation is performed on the second storage system.

25. A system, include: Memory; as well as a processor communicatively coupled to the memory, wherein the processor is configured to perform a method comprising: receiving a command to migrate from a first storage system to a second storage system, wherein the first storage system includes a first primary storage device and a first secondary storage device, and wherein the second storage system includes a second primary storage device and a second secondary storage device; In response to receiving the command, copying data between the first primary storage device and the second primary storage device; In response to receiving the command, copying data between the first primary storage device and the second secondary storage device; In response to reaching a full-duplex state between the first primary storage device and both the second primary storage device and the second auxiliary storage device: pausing the received I / O operation for execution on the first storage system; storing the I / O operations in a queue; and enabling multi-storage volume exchange between the second primary storage device and the second auxiliary storage device; Migrating from the first storage system to the second storage system so that a newly received I / O operation is performed on the second storage system; Resuming I / O operations; and The queued I / O operation is performed on the second storage system.