Information processing system and information processing method

Abstract

To reduce operational costs of DRaaS by reducing excess computing resources of SDS in preparation for failing over.SOLUTION: An information processing system 1S comprises storage apparatuses 12Rx (12X1, 12X2, 12Y1, and 12Y2) installed in areas X and Y, SDS2Sy (2S1 and 2S2) installed in the cloud, and a management system 100. The management system 100 estimates a predetermined resources required when failing over volumes in each storage apparatus 12Rx using replicated volumes, based on configuration information and operation information of the volumes in each storage apparatus 12Rx. The management system 100 distributes the replicated volumes relating to the storage apparatus 12Rx located at the same location to SDS2Sy, and selects the replication destination of SDS2Sy so that the amount of required resources calculated for each installation location and for each storage system SDS2Sy is minimized.SELECTED DRAWING: Figure 1

Description

【Technical Field】 【0001】 The present invention relates to an information processing system and an information processing method. 【Background Art】 【0002】 There is Disaster Recovery (DR) that places the operation system and the standby system in different regions and transfers business processing from the operation system to the standby system when a disaster such as an earthquake occurs. In recent years, there has been an increasing interest in DRaaS (Disaster Recovery as a Service) that provides DR for on-premises systems in the cloud. For example, Software Defined Storage (SDS) disclosed in Patent Document 1 can be used as storage on the cloud to provide DR for on-premises systems. 【Prior Art Documents】 【Patent Documents】 【0003】 【Patent Document 1】 Japanese Unexamined Patent Application Publication No. 2019-101703 【Summary of the Invention】 【Problems to be Solved by the Invention】 【0004】 When providing DRaaS, the efficient operation of SDS on the cloud is closely related to suppressing the operation cost of DRaaS. The SDS in DRaaS has a small IO load during normal times, only for backup IO processing. On the other hand, when a failure occurs on the on-premises system side, the SDS has a sudden increase in IO load for the IO processing of the failover application. 【0005】 In SDS, to shorten the failover time (Recovery Time Objective (RTO)) in response to failover I / O load, it is desirable to reserve surplus computing resources in advance for failover, rather than scaling out the SDS, which takes time for processes such as rebalancing. However, the problem is that securing surplus computing resources becomes an operational cost for the SDS, leading to an increase in the operational cost of DRaaS. 【0006】 This invention has been made in consideration of the above points, and aims to provide an information processing system and information processing method that reduce the operating costs of DRaaS by reducing the surplus computing resources of SDS prepared for failover. [Means for solving the problem] 【0007】 To solve the above-mentioned problems, in one aspect of the present invention, there is an information processing system having a plurality of storage devices installed in a plurality of regions, a plurality of storage systems having a plurality of storage nodes provided in the cloud, and a management system, wherein the processor of the management system acquires configuration information and operational information of volumes having the plurality of storage devices from each of the storage devices, and estimates the amount of replication resources required in the storage system to create a replicated volume in the storage system that will failover the volume having the volume of each of the storage devices based on the configuration information and operational information, and estimates the amount of failover resources required in the storage system to failover the volume with the replicated volume, and simultaneously determines when failures occur based on the installation location The method is characterized by grouping the multiple storage devices for each possible installation location group of the storage devices, aggregating the amount of resources required for replication and the amount of resources required for failover for the volumes of each storage device for each installation location group and each storage system, selecting a storage system as the replication destination storage system to create the replicated volumes, while distributing the replicated volumes related to the multiple storage devices located at the same location across the multiple storage systems, such that the amount of resources required for failover aggregated for each installation location group and each storage system is minimized, and performing replication to create the replicated volumes on the selected replication destination storage system. [Effects of the Invention] 【0008】 According to the present invention, the operating costs of DRaaS can be reduced by reducing the surplus computing resources of SDS prepared for failover. [Brief explanation of the drawing] 【0009】 [Figure 1] A diagram showing the configuration of the information processing system according to Embodiment 1. [Figure 2] A diagram showing the hardware configuration of the information processing system according to Embodiment 1. [Figure 3] A diagram showing the memory configuration of a storage device according to Embodiment 1. [Figure 4] A diagram showing the memory configuration of a storage node according to Embodiment 1. [Figure 5] A diagram showing the memory configuration of the DR management system according to Embodiment 1. [Figure 6] A diagram showing volume configuration information related to Embodiment 1. [Figure 7] A diagram showing replication configuration information related to Embodiment 1. [Figure 8] A diagram showing the storage node configuration information according to Embodiment 1. [Figure 9] A diagram showing volume operation information according to Embodiment 1. [Figure 10] A diagram showing the storage node operation information according to Embodiment 1. [Figure 11] A diagram showing storage device management information according to Embodiment 1. [Figure 12] A diagram showing SDS management information related to Embodiment 1. [Figure 13] A diagram showing replication management information related to Embodiment 1. [Figure 14] A diagram showing the required resource management information related to Embodiment 1. [Figure 15] A flowchart illustrating the process of registering a new storage device to the DR management system according to Embodiment 1. [Figure 16] A flowchart illustrating the process for registering a new DR target volume according to Embodiment 1. [Figure 17] A flowchart illustrating the replication destination SDS selection process according to Embodiment 1. [Figure 18] A flowchart showing the pre-construction preparation process for replication according to Embodiment 1. [Figure 19] A flowchart illustrating the failover process for a failed volume according to Embodiment 1. [Figure 20]Flowchart showing the failback process for the failure occurrence volume according to Embodiment 1. [Figure 21] Diagram showing the configuration of the information processing system according to Embodiment 2. [Figure 22] Diagram showing the SDS installation location management information according to Embodiment 2. [Figure 23] Diagram showing the SDS management information according to Embodiment 2. [Figure 24] Flowchart showing the replication destination SDS selection process according to Embodiment 2. 【Modes for Carrying Out the Invention】 【0010】 Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. The following description and drawings are examples for explaining the present invention, and for the sake of clarity of explanation, appropriate omissions and simplifications are made. Also, not all combinations of features described in the embodiments are essential for the solution means of the invention. The present invention is not limited to the embodiments, and all application examples that conform to the idea of the present invention are included in the technical scope of the present invention. Those skilled in the art can make various additions and changes within the scope of the present invention. The present invention can also be implemented in various other forms. Unless otherwise limited, each component may be plural or singular. 【0011】 In the following description, various information may be described using expressions such as "table", "list", "queue", etc., but the various information may be represented by other data structures. To indicate independence from the data structure, "XX table", "XX list", etc. may be referred to as "XX information". When explaining the content of each information, expressions such as "identification information", "identifier", "name", "ID", "number", etc. are used, but these are mutually replaceable. 【0012】 Furthermore, in the following explanations, when describing similar elements without distinction, a reference code or a common number in the reference code will be used. When describing similar elements with distinction, the reference code of that element will be used, or the ID assigned to that element will be used instead of the reference code. 【0013】 Furthermore, the following explanation may describe the processes performed by executing a program. A program is executed by at least one processor (e.g., a CPU) to perform defined processes, using memory resources (e.g., memory) and / or interface devices (e.g., communication ports) as appropriate. For this reason, the processor may be the main entity performing the processes. Similarly, the main entity performing the processes by executing a program may be a controller, device, system, computer, node, storage system, storage device, server, management computer, client, or host having a processor. The main entity performing the processes by executing a program (e.g., a processor) may include hardware circuits that perform some or all of the processes. For example, the main entity performing the processes by executing a program may include hardware circuits that perform encryption and decryption, or compression and decompression. The processor operates as a functional unit that realizes predetermined functions by operating according to the program. Devices and systems including a processor are devices and systems that include these functional units. 【0014】 A program may be installed from its program source into a device such as a computer. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server includes a processor (e.g., a CPU) and memory resources, which may further store the distribution program and the program to be distributed. The processor of the program distribution server may then execute the distribution program, thereby distributing the program to other computers. Furthermore, in the following description, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs. 【0015】 [Embodiment 1] (Configuration of Information Processing System 1S according to Embodiment 1) Figure 1 shows the configuration of the information processing system 1S according to Embodiment 1. The information processing system 1S consists of storage devices 12Rx (12X1, 12X2, 12Y1, 12Y2), SDS (Software Defined Storage) 2Sy (2S1, 2S2), and a DR (Disaster Recovery) management system 100. The storage devices 12Rx (R=X,Y, x=1,2), SDS2Sy (y=1,2), and the DR management system 100 constitute a DR system built on the cloud by a DRaaS (Disaster Recovery as a Service) provider. 【0016】 In information processing system 1S, multiple storage devices 12Rx belonging to multiple customers are located in two geographically distant regions X and Y that will not be affected by the same disaster simultaneously. Storage devices 12X1 and 12X2 are operated in data centers in region X, each managed by a different customer. Storage devices 12Y1 and 12Y2 are operated in data centers in region Y, each managed by a different customer. 【0017】 In the information processing system 1S, the data stored in each volume 5VαR (5V1X, 5V2X, 5V3X, 5V4X, 5V1Y, 5V2Y, 5V3Y, 5V4Y) of the customer management storage device 12Rx is pre-replicated (copied) to SDS2Sy. 【0018】 In the information processing system 1S, if a failure occurs in the storage device 12Rx, I / O processing for volume 5VαR is failovered by volume 1Vβy (1V11, 1V21, 1V31, 1V41) of one of the replication destination SDS2Sy devices. 【0019】 Storage device 12X1 consists of CPUs (Central Processing Units) 6CX1 and 6CX2, and volumes 5V1X and 5V2X, which process I / O from applications 7A1X and 7A2X using CPUs 6CX1 and 6CX2. Similarly, storage device 12X2 consists of CPUs 6CX3 and 6CX4, and volumes 5V3X and 5V4X, which process I / O from applications 7A3X and 7A4X using CPUs 6CX3 and 6CX4. 【0020】 Storage device 12Y1 is configured to include CPUs 6CY1 and 6CY2, and volumes 5V1Y and 5V2Y, which process I / O from applications 7A1Y and 7A2Y by CPUs 6CY1 and 6CY2. Similarly, storage device 12Y2 is configured to include CPUs 6CY3 and 6CY4, and volumes 5V3Y and 5V4Y, which process I / O from applications 7A3Y and 7A4Y by CPUs 6CY3 and 6CY4. 【0021】 SDS2Sy is an SDS cluster on the cloud. SDS2Sy is connected to storage device 12Rx via network 250, and a replication of volume 5VαR on storage device 12Rx is established. 【0022】 The SDS2S1 consists of CPUs 4C11 and 4C21, and volumes 1V11, 1V21, 1V31, and 1V41, which are processed by CPUs 4C11 and 4C21. Each of volumes 1V11, 1V21, 1V31, and 1V41 has a pre-configured replication of volumes 5V1X, 5V2X, 5V3X, and 5V4X. 【0023】 SDS2S2 consists of CPUs 4C12 and 4C22, and volumes 1V12, 1V22, 1V32, and 1V42, which are processed by CPUs 4C12 and 4C22. Each of volumes 1V12, 1V22, 1V32, and 1V42 has a pre-configured replication of volumes 5V1Y, 5V2Y, 5V3Y, and 5V4Y. 【0024】 The number of CPUs in SDS2S1 is the minimum number of CPUs capable of handling I / O processing for volumes 5V1X, 5V2X in region X or volumes 5V1Y, 5V2Y in region Y, which could potentially fail over simultaneously in the event of a disaster. Similarly, the number of CPUs in SDS2S2 is the minimum number of CPUs capable of handling I / O processing for volumes 5V3X, 5V4X in region X or volumes 5V3Y, 5V4Y in region Y, which could potentially fail over simultaneously in the event of a disaster. 【0025】 In Figure 1, SDS2S1 and 2S2 each perform failover of two volumes simultaneously, so two CPUs, 4C11 and 4C21, are allocated for each volume. However, the correspondence between volumes and the CPUs that perform I / O operations on them is not limited to a 1:1 relationship; the number of CPUs allocated to a volume changes depending on the correspondence. Furthermore, the primary source of I / O operations on a volume is not limited to CPUs; other computing resources such as threads or virtual CPUs may also be used. 【0026】 In the example shown in Figure 1, storage devices 12X1 and 12X2 located in region X are simultaneously affected by a disaster and fail over. To prevent a concentration of I / O processing load on the failover destination SDS2Sy, volumes 5V1X and 5V2X of storage device 12X1 are failed over to volumes 1V11 and 1V21 of SDS2S1, respectively. Volumes 5V3X and 5V4X of storage device 12X2 are also failed over to volumes 1V12 and 1V22 of SDS2S2, respectively. 【0027】 Similarly, storage devices 12Y1 and 12Y2 located in region Y will be affected simultaneously and failover will occur in the event of a disaster. To prevent a concentration of I / O processing load on the failover destination SDS, volumes 5V1Y and 5V2Y of storage device 12Y1 will fail over to volumes 1V31 and 1V41 of SDS2S1, respectively. Volumes 5V3Y and 5V4Y of storage device 12Y2 will also fail over to volumes 1V32 and 1V42 of SDS2S2, respectively. 【0028】 In this way, the DR system is constructed so that the failover destinations are distributed between SDS2S1 and SDS2S2 for volumes 5V1X and 5V2X of storage device 12X1 and volumes 5V3X and 5V3X of storage device 12X2, respectively. Similarly, the DR system is constructed so that the failover destinations are distributed between SDS2S1 and SDS2S2 for volumes 5V1X and 5V2X of storage device 12Y1 and volumes 5V3X and 5V3X of storage device 12X2, respectively. 【0029】 In the example in Figure 1, if region X is affected by a disaster, volumes 1V11 and 1V21 of SDS2S1 will handle I / O from applications 3A11 and 3A21, thereby taking over I / O processing from applications 7A1X and 7A2X to volumes 5V1X and 5V2X. Also, if region X is affected by a disaster, volumes 1V12 and 1V22 of SDS2S2 will handle I / O from applications 3A12 and 3A22, thereby taking over I / O processing from applications 7A3X and 7A4X to volumes 5V3X and 5V4X. 【0030】 The DR management system 100 is connected to the storage devices 12Rx and SDS2Sy via the network 250, enabling communication between them. The DR management system 100 receives instructions from DRaaS users, such as instructions for building a DR configuration (concluding a DRaaS contract) and instructions for executing failover, and executes the operations related to the instructions on the storage devices 12Rx and SDS2Sy. 【0031】 The DR management system 100 stores various information in a predetermined storage area, including computing resources such as CPU and memory, as well as storage device management information 111, SDS management information 112, replication management information 113, and required resource management information 114. The DR management system 100 executes various processes based on instructions entered by the DRaaS user via a terminal (not shown). The various processes and the storage device management information 111, SDS management information 112, replication management information 113, and required resource management information 114 will be described later. 【0032】 (Hardware configuration of information processing system 1S according to Embodiment 1) Figure 2 is a diagram showing the hardware configuration of the information processing system 1S according to Embodiment 1. 【0033】 The DR management system 100, storage devices 12Rx,..., SDS2Sy,..., and application servers 210z,... each have their own processors and memory working together to perform various processes while communicating via communication ports and the network 250. 【0034】 Network 250 consists of multiple types or systems (Ethernet®, InfiniBand®, etc.) and includes network devices such as switches and routers. Network 250 may also be a virtual network using VPN (Virtual Private Network) or virtual switches. The connection relationships of Network 250 are just examples, and dedicated networks may exist between specific components. For example, the storage device 12Rx and the application server 210z may be connected by a dedicated storage network (Fibre Channel, etc.). 【0035】 The DR management system 100 comprises a CPU 14, memory 13, storage device 12, and communication port 11. 【0036】 SDS2Sy shows the hardware configuration of SDS2S1,2S2 (Figure 1). SDS2Sy is a storage cluster consisting of multiple storage nodes 23Sγy (23S1y,23S2y,...). Each of the storage nodes 23Sγy (γ=1,2,..., y=1,2) has a CPU 8Cγy, memory 8Mγy, storage device 8Sγy, and communication port 8Pγy connected via a bus. 【0037】 Application server 210z shows the hardware configuration of a server running applications 7A (7A1X, 7A2X, 7A3X, 7A4X, 7A1Y, 7A2Y, 7A3Y, 7A4Y) and 3A (3A11, 3A21, 3A12, 3A22) (Figure 1). Application server 210z has a CPU 21Cz, memory 21Mz, storage device 21Sz, and communication port 21Pz connected via a bus. Application server 210z is deployed in both the public cloud managed by the DRaaS provider and the data center managed by the DRaaS user. 【0038】 Storage device 12Rx shows the hardware configuration of storage devices 12X1, 12X2, 12Y1, and 12Y2 (Figure 1). Storage device 12Rx has a CPU 6CRx, memory 6MRx, storage device 6SRx, and communication port 6PRx connected via a bus. Storage device 12Rx is deployed in data centers, etc., managed by DRaaS users. 【0039】 While the DR management system 100 and SDS2Sy are assumed to be located in a public cloud managed by the DRaaS provider, they may also be located in a private cloud capable of communicating with the storage device 12Rx. 【0040】 The storage devices 12Rx and SDS2Sy are storage devices that provide logical storage areas, or volumes, composed of the installed storage devices 6SRx, 8S1y, and 8S2y to applications running on the application server 210z. The storage devices have a replication function that replicates the data of the volumes between storage devices (for example, between SDS2Sy and storage device 12Rx). 【0041】 For convenience, SDS2Sy will be referred to as the storage system, distinguishing it from the storage device 12Rx. 【0042】 SDS2Sy is configured by clustering multiple storage nodes 23Sγy (γ=1,2,…). SDS2Sy can accommodate excesses or deficiencies in storage capacity or data input / output performance (IO performance) by increasing or decreasing the number of storage nodes that make up the configuration. 【0043】 Under normal circumstances, application server 210z resides in the DRaaS user's data center and reads and writes data to storage device 12Rx within the data center according to application processing. In the event of a disaster or other situation where storage device 12Rx fails over, application server 210z located in the public cloud takes over the processing of application server 210z in the DRaaS user's data center. The application server 210z in the public cloud does not need to be present at all times; it only needs to exist when a failover occurs (for example, it can be deployed when a failover occurs and deleted after recovery). 【0044】 The DR management system 100, storage device 12Rx, SDS2Sy, and application server 210z do not need to be a single physical device; they may be configured using virtualization technologies such as virtual machines or containers. Alternatively, the devices may be configured as multiple virtual devices contained within a single physical device. Conversely, the devices may be configured as a single virtual device by clustering multiple physical devices. Furthermore, each device may reside in a physically separate location (region). 【0045】 The storage devices 12,6SRx,8Sγy,21Sz may be physical SSDs (Solid State Drives) or HDDs (Hard Disk Drives), or virtual storage devices provided by cloud vendors (e.g., AWS® S3, Amazon EBS®, etc.). 【0046】 (Configuration of the memory 6MRx of the storage device 12Rx according to Embodiment 1) Figure 3 shows the configuration of the memory 6MRx of the storage device 12xR according to Embodiment 1. The memory 6MRx of the storage device 12Rx stores the storage device control program 31Rx, storage device configuration information 32Rx, and storage device operation information 33Rx. The storage device configuration information 32Rx includes volume configuration information 321Rx and replication configuration information 322Rx. The storage device operation information 33Rx includes volume operation information 331Rx. 【0047】 The storage device control program 31Rx provides application 7A with volume 5VαR, which is a logical storage area, based on the storage device configuration information 32Rx. The storage device control program 31Rx has the function of receiving I / O requests issued by application 7A to volume 5VαR and processing I / O requests such as reading and writing data to the storage device 6SRx. 【0048】 Furthermore, the storage device control program 31Rx has the function of replicating data from volume 5VαR to other storage devices such as 12Rx or SDS2Sy, according to the replication configuration information 322Rx. 【0049】 Furthermore, the storage device control program 31Rx has a function to record statistical information such as IOPS (IO Per Second) and response time as storage device operation information. In addition, the storage device control program 31Rx has a function to refer to and update storage device configuration information 32Rx and a function to refer to storage device operation information 33Rx in accordance with requests from the DR management system 100. 【0050】 In addition to the functions described above, the storage device control program 31Rx may also have common storage system functions such as thin provisioning, tiering of storage devices 6SRx, snapshots, and compression / deduplication. 【0051】 (Configuration of the 8Mγy memory of the storage node 23SγR according to Embodiment 1) Figure 4 shows the configuration of the memory 8Mγy of the storage node 23Sγy (γ=1,2,…, y=1,2) according to Embodiment 1. The memory 8Mγy of the storage node 23S stores the SDS control program 41γy, SDS configuration information 42γy, and SDS operation information 43γy. The SDS configuration information 42γy includes storage node configuration information 421γy, volume configuration information 422γy, and replication configuration information 423γy. The SDS operation information 43γy includes storage node operation information 431γy and volume operation information 432γy. 【0052】 The SDS configuration information 42γy and SDS operation information 43γy are stored in the 8Mγy memory of each storage node 23Sγy that constitutes SDS2Sy. Based on the SDS configuration information 42γy and SDS operation information 43γy, information redundancy and consistency control are performed. 【0053】 The SDS control program 41γy provides volume 1Vβy, which is a logical memory area, to application 3A (3A11, 3A12, 3A21, 3A22) based on the SDS configuration information 42γy. 【0054】 The SDS control program 41γy has the function of receiving I / O requests issued by applications 3A (3A11, 3A12, 3A21, 3A22) to volume 1Vβy and processing I / O requests such as reading and writing data to storage device 8Sγy. The SDS control program 41γy also includes the function of coordinating processing with multiple storage nodes 23Sγy (23S1y, 23S2y, ...). 【0055】 Furthermore, the SDS control program 41γy has the function of replicating data from volume 1Vβy to other storage devices such as 12Rx or SDS2Sy, according to the replication configuration information 423γy. 【0056】 The I / O processing for volume 1Vβy is handled by the SDS control program 41γy, which runs on one of the storage nodes 23Sγy that make up the SDS cluster. If a failure occurs on one of the storage nodes 23Sγy, the I / O processing for volume 1Vβy is taken over by another storage node 23Sγy. 【0057】 The SDS control program 41γy has the function of recording operational information related to volume 1Vβy, such as IOPS and response time, and operational information related to storage node 23Sγy, such as CPU usage and memory usage, as SDS operational information 43γy. 【0058】 Furthermore, the SDS control program 41γy has the function of referencing and updating SDS configuration information 42γy and referencing SDS operation information 43γy in accordance with requests from the DR management system 100. In addition, the SDS control program 41γy has the function of adding and removing storage nodes 23Sγy that constitute SDS2Sy in accordance with requests from the DR management system 100. 【0059】 In addition, the SDS control program 41γy may have other common storage system functions such as thin provisioning, tiering of storage devices 8Sγy, snapshots, compression and deduplication, and load balancing and rebalancing among storage nodes 23Sγy. 【0060】 (Configuration of the memory 13 of the DR management system 100 according to Embodiment 1) Figure 5 shows the configuration of the memory 13 of the DR management system 100 according to Embodiment 1. The memory 13 of the DR management system 100 stores the DR management program 51 and the DR management information 52. The DR management program 51 includes the replication management program 511, the SDS management program 512, and the storage device management program 513. The DR management information 52 includes the storage device management information 111, the SDS management information 112, the replication management information 113, and the required resource management information 114. 【0061】 The replication management program 511 manages replication (DR configuration) using storage devices 12Rx and SDS2Sy. Specifically, the replication management program 511 selects the DR destination storage node 23Sγy (SDS2Sy) for a certain DR target volume 5VαR, and issues instructions to the storage devices 12Rx and SDS2Sy to build replication. The replication management program 511 also issues instructions to add or remove storage nodes 23Sγy of SDS2Sy according to the operating status of SDS2Sy. 【0062】 The replication management program 511 also performs DR failover and failback processing based on user instructions (the operation of returning the I / O processing of volume 1Vβy to volume 5VαR of the original storage device 12Rx). 【0063】 The SDS management program 512 performs tasks such as collecting information on the managed SDS2Sy, making configuration changes based on instructions from the replication management program 511, and building new SDS2Sy instances. 【0064】 The storage device management program 513 performs tasks such as registering storage devices 12Rx under the management of the DR management system 100, collecting information on storage devices 12Rx, and making configuration changes based on instructions from the replication management program 511. 【0065】 Storage device management information 111 is management information regarding the configuration and status of storage devices 12Rx under the management of the DR management system 100. Storage device management information 111 is referenced and updated by the replication management program 511 and the storage device management program 513. 【0066】 SDS management information 112 is management information that manages the configuration and status of SDS2Sy under the management of the DR management system 100. SDS management information 112 is referenced and updated by the replication management program 511 and the SDS management program 512. 【0067】 Replication management information 113 is management information that manages the replication relationship and status established between the storage device 12Rx and SDS2Sy. Replication management information 113 is referenced and updated by the replication management program 511. 【0068】 The required resource management information 114 is management information that manages the resources necessary for the operation of DRaaS. The required resource management information 114 is referenced and updated by the replication management program 511. 【0069】 In addition, configuration information and operational information of storage devices 12Rx and SDS2Sy collected by the SDS management program 512 and the storage device management program 513 may be stored in memory 13. Furthermore, a program for providing a management interface such as a GUI to customers using DRaaS may be provided. 【0070】 (Volume configuration information related to Embodiment 1: 321Rx, 422γy) Figure 6 shows volume configuration information 321Rx and 422γy according to Embodiment 1. Volume configuration information 321Rx indicates that volume 5VαR, with a volume capacity 63 identified by volume ID 61 and volume name 62, will be assigned to the application server 210z shown in connection information 64. Volume configuration information 321Rx is set by the customer via the DR management system 100. The same applies to volume configuration information 422γy. However, if the customer has not contracted for DRaaS, or if the volume existed before the contract, volume configuration information 321Rx can also be set by the customer directly operating the storage device 12Rx without going through the DR management system 100. 【0071】 (Replication configuration information related to Embodiment 1: 322Rx, 423γy) Figure 7 shows the replication configuration information 322Rx and 423γy according to Embodiment 1. Replication configuration information 322Rx indicates that the replication identified by replication ID 71 of volume 5VαR, identified by volume ID 72, is configured to volume 1Vβy of SDS2Sy, shown as the replication destination 73. The same applies to replication configuration information 423γy. 【0072】 Note that volume 5VαR, shown in volume configuration information 321Rx,422γy in Figure 6, does not necessarily have replication created. For example, volume 5VαR, where volume ID 61 is "2" in Figure 6, does not have a record corresponding to volume ID 72 in Figure 7. In other words, replication has not been created. 【0073】 (Storage node configuration information 421γy related to Embodiment 1) Figure 8 shows the storage node configuration information 421γx according to Embodiment 1. The storage node configuration information 421γx is a list of storage nodes 23Sγy that constitute SDS2Sy. The storage node configuration information 421γy indicates that SDS2Sy is configured to include storage nodes 23Sy that have the resources of a CPU 82, memory 83, storage capacity 84, and network 85, identified by node ID 81. 【0074】 (Volume operation information 331Rx, 432γx related to Embodiment 1) Figure 9 shows volume operation information 331Rx and 432γx according to Embodiment 1. Volume operation information 331Rx shows the average IOPS 92, average throughput 93, average response time 94, and used capacity 95 of volume 5VαR of storage device 12Rx identified by volume ID 91. The same applies to volume operation information 432γx. Volume operation information 331Rx is stored after the storage device control program 31Rx and SDS control program 41γy collect the operating status of volumes 5VαR and 1Vβy under their management. The same applies to volume operation information 432γx. 【0075】 (Storage node operation information 431γy related to Embodiment 1) Figure 10 shows the storage node operation information 431γy according to Embodiment 1. The storage node operation information 431γy shows the CPU usage 102, memory usage 103, average response time 94, and used capacity 95 of the storage node 23Sγy identified by node ID 101. The storage node operation information 431γy is stored by the SDS control program 41γy after it collects the operating status of the storage node 23Sγy under its management. 【0076】 (Storage device management information 111 related to Embodiment 1) Figure 11 shows the storage device management information 111 according to Embodiment 1. In response to a customer using DRaaS giving an instruction to register a new storage device 12Rx to the DR management system 100, the storage device management program 513 registers a new entry. 【0077】 The storage device management information 111 shows the customer information 1102, installation location information 1103, installation location group ID 1104, and IP address 1105 of the storage device 12Rx identified by the storage device ID 1101. 【0078】 The installation location information 1103 includes the installation location (address, etc.) of the storage device 12Rx, longitude and latitude information calculated from the installation location, and may also include more detailed location information (building, server rack, power supply system, etc.). The installation location group ID 1104 is the group ID when storage devices 12Rx that are likely to experience failures simultaneously are grouped (clustered) based on their proximity within a predetermined range. 【0079】 (SDS management information 112 related to Embodiment 1) Figure 12 shows the SDS management information 112 according to Embodiment 1. In response to a new construction instruction for SDS2Sy from the DRaaS provider, the SDS management program 512 registers a new entry in the SDS management information 112. 【0080】 SDS management information 112 shows the IP address 1202 of SDS2Sy identified by SDSID 1201, the number of storage nodes 1203, the total amount of resources 1204, the total amount of resources required for replication 1205, the total amount of resources required for failover 1206, and the worst-case total amount of resources required for failover 1207. 【0081】 The total required resources for replication, 1205, represent the amount of resources needed to create replication on the relevant SDS2Sy. This total required resources of 1205 is the sum of the total required resources of 1406 (Figure 14) for each SDSID1402. 【0082】 The total failover resource amount of 1206 is the amount of resources added to the total replication resource amount of 1205 in preparation for a failover. However, the amount of resources added to the storage capacity of the total replication resource amount of 1205 is 0, meaning the storage capacity remains unchanged. The total failover resource amount of 1206 is, for example, the maximum value for each SDSID 1402 of the total failover resource amount of 1407 (Figure 14). 【0083】 The worst-case total resource requirement of 1207 for failover is the sum of the total resource requirement of 1407 for failover shown in Figure 14 for each of the 1402 SDSIDs, i.e., the worst-case value assuming a failover occurs in all replications. This worst-case value may exceed the total resource amount of SDS2Sy at that time, as SDS2Sy will be expanded as needed. 【0084】 (Replication management information 113 related to Embodiment 1) Figure 13 shows the replication management information 113 according to Embodiment 1. The replication management information 113 is information for managing the replication configuration between volume 5VαR in the storage device 12Rx and volume 1Vβy in SDS2Sy. When volume 5VαR, which is a target for disaster recovery, is added, the replication relationship between volume 5VαR and volume 1Vβy is established in advance, and a new entry is registered in the replication management information 113. 【0085】 The replication management information 113 shows the required resources for replication 1306, the required resources for failover 1307, and the replication status 1308 for replication that has a correspondence between the storage device side volume ID 1303 of the storage device ID 1302 identified by replication ID 1301 and SDSID 1304 and SDS side volume ID 1305. 【0086】 Replication ID 1301 may be a different ID from Replication ID 71Rx in Figure 7. In this case, information for managing replication IDs within the storage device 12Rx will be required. 【0087】 SDSID1304 uses a single SDS2Sy as the replication destination for multiple volumes 5VαR on a single storage device 12Rx. This allows the use of consistency grouping, a function that maintains data consistency while replicating across multiple volumes 5VαR. However, the replication destination SDS2Sy is not limited to a single device; it can be multiple devices. 【0088】 The replication resource requirement of 1306 is an estimate of the SDS2Sy resources required for replication under normal conditions. The failover resource requirement of 1307 is an estimate of the SDS2Sy resources required for application I / O processing during failover. Computational resources such as CPU and memory differ between the replication resource requirement of 1306 and the failover resource requirement of 1307, but the storage capacity remains constant at the value for the replication resource requirement of 1306. 【0089】 Replication status 1308 "Normal" indicates normal operation, and "Failover" indicates failover. Although not shown in the diagram, replication management information 113 may include each element that constitutes SDS12Sy, such as the network (communication port). 【0090】 (Required resource management information 114 related to Embodiment 1) Figure 14 shows the required resource management information 114 according to Embodiment 1. The required resource management information 114 manages the amount of resources required for disaster recovery (DR) on a per-installation location group basis. The required resource management information 114 is created by aggregating the information of storage device management information 111 (Figure 11), SDS management information 112 (Figure 12), and replication management information 113 (Figure 13). New entries are registered when a new installation location group is created when a new SDS2Sy is built or when a volume to be targeted for DR is added. 【0091】 According to the required resource management information 114, one SDS2Sy is shared across multiple installation groupings. Furthermore, one SDS2Sy is responsible for the replication of one storage device 12Rx to ensure data consistency. 【0092】 The required resource management information 114 manages the required resources for replication 1404, the required resources for failover 1405, the total required resources for replication 1406, and the total required resources for failover 1407 for each combination of SDSID 1402 and storage device ID 1403, on a per-location group ID 1401 basis. 【0093】 In addition, the required resource management information 114 may include customer information (contract information, billing information, etc.) for using the DR management system 100, authentication information for customers to access the DR management system 100, information for the DR management system 100 to communicate with storage devices 12Rx and SDS2Sy, and account information for the public cloud (or private cloud) on which the SDS2Sy is running. 【0094】 (New registration process for storage device 12Rx according to Embodiment 1) Figure 15 is a flowchart illustrating the process of registering a storage device 12Rx to the DR management system 100 according to Embodiment 1. This new registration process is executed by the storage device management program 513 when a customer who has contracted for DRaaS registers their owned storage device 12Rx to the DR management system 100. When registering the storage device 12Rx to the DR management system 100, the customer specifies the installation location of the storage device 12Rx. 【0095】 First, in step S1501, the storage device management program 513 receives instructions from the customer to register a new storage device 12Rx with the DR management system 100 (including specifying the installation location of the storage device 12Rx). In step S1501, customer information and connection information (such as IP address and authentication information) for the DR management system 100 to communicate with the storage device 12Rx may be included in the instructions as needed. 【0096】 Next, in step S1502, the storage device management program 513 adds a new entry for the storage device 12Rx to be registered in the storage device management information 111. 【0097】 Next, in step S1503, the storage device management program 513 establishes communication with the storage device 12Rx that was registered in step S1502. Execution of step S1503 enables the storage device management program 513 to collect configuration and operational information through communication with the storage device 12Rx and to issue configuration change instructions for the storage device 12Rx. 【0098】 (New registration process for DR target volumes according to Embodiment 1) Figure 16 is a flowchart showing the process for registering a new DR target volume according to Embodiment 1. This process for registering a new DR target volume is executed when a customer who has a DRaaS contract registers a certain volume (on the storage device 12Rx side) as a DR target volume in the DR management system 100. 【0099】 The process of registering a new DR target volume is part of the process executed by the replication management program 511. When this process of registering a new DR target volume is executed, it is assumed that the DR target storage device 12Rx has already been registered with the DR management system 100 (see Figure 14). 【0100】 Furthermore, when executing the new registration process for this DR target volume, it is assumed that the DR source volume 5VαR on the storage device 12Rx side has already been created by the customer. The DR destination volume 1Vβy on the SDS2Sy side will be created by the new registration process for this DR target volume. 【0101】 First, in step S1601, the replication management program 511 receives instructions from the customer to the DR management system 100 for building a disaster recovery (including the specification of the storage device 12Rx and volume 5VαR to be targeted for disaster recovery). In addition, the customer may specify the replication mode (synchronous / asynchronous replication pair). 【0102】 Next, in step S1602, the replication management program 511 uses the storage device management program 513 to obtain configuration information and operational information for the DR target volume 5VαR. 【0103】 Next, in step S1603, the replication management program 511 uses the configuration and operational information of the DR target volume 5VαR obtained in step S1602 to estimate the amount of resources required for failover and the amount of resources required for replication for the DR target volume 5VαR. In other words, it estimates the resources (CPU, memory, capacity, etc.) of the SDS2Sy that will be required when normal replication and I / O processing are failed over to the SDS2Sy. 【0104】 Various methods can be used for estimation, but for example, resources whose required amount does not change before and after failover, such as capacity, are allocated 100% in advance. For resources whose required amount changes before and after failover, such as CPU and memory, the IO characteristics of the DR target volume 5VαR, such as IOPS, throughput, and read / write ratio, are estimated by applying them to a predefined calculation formula. The parameters of this calculation formula may be automatically adjusted based on the actual performance of the DR target volume 5VαR already registered in the DR management system 100 (such as the amount of resources actually required when failover occurred in the past). 【0105】 Next, in step S1604, the replication management program 511 selects an appropriate SDS2Sy as the replication destination for volume 5VαR, which is subject to disaster recovery. Details of step S1604 will be described later with reference to Figure 17. 【0106】 Next, in step S1605, the replication management program 511 performs preliminary preparations for replication construction based on the selection result of SDS2Sy in step SS1604. Details of step S1605 will be described later with reference to Figure 18. 【0107】 Next, in step S1606, the replication management program 511 uses the storage device management program 513 and the SDS management program 512 to establish a replication of the DR target volume 5VαR to the SDS2Sy selected in step SS1604. Step S1606 also establishes communication between the storage device 12Rx and the SDS2Sy, issues instructions to the storage device 12Rx and the SDS2Sy to establish a replication relationship, and updates various configuration information, adds new entries, and creates the replication destination volume. 【0108】 Next, in step S1607, the replication management program 511 adds a new entry to the replication management information 113. 【0109】 Although not shown in the diagram, it is also possible to periodically re-estimate the required resources for all volumes 5VαR (i.e., all replications) based on the latest operational information and change the SDS2Sy replication destination. Furthermore, when deleting a DR configuration (deleting volumes targeted for DR) at the customer's instruction, the required resources may also be re-estimated. 【0110】 (Details of the replication destination SDS selection process according to Embodiment 1) Figure 17 is a flowchart detailing the replication destination SDS selection process (Figure 16) according to Embodiment 1. 【0111】 In this replication destination SDS selection process, the replication destination SDS2Sy is selected so that the SDS2Sy of storage devices 12Rx belonging to the same installation location group, which are located close together within a predetermined range and therefore likely to experience simultaneous failures, are distributed. This ensures that when a disaster occurs in a certain region and multiple storage devices 12Rx belonging to a certain installation location group experience simultaneous failovers, the failover load on each SDS2Sy is distributed evenly. In other words, when all storage devices 12Rx belonging to the same installation location group experience a simultaneous failover, the increase in resource consumption due to the failover is distributed evenly across each SDS2Sy. 【0112】 When grouping multiple storage devices 12Rx into installation location groups, information such as the required resources for each replication in each storage device 12Rx may be considered in addition to the installation location information. For example, preferably, the total required resources 1407 for failover for each installation location group ID 1401 in Figure 14 are made uniform to a certain extent. By doing so, the required resources for SDS2Sy calculated in the replication construction pre-preparation process (Figure 18) can be suppressed as much as possible. 【0113】 First, in step S1701, the replication management program 511 determines whether a volume 5VαR for which replication has already been established already exists for the DR target storage device 12Rx. If a volume 5VαR for which replication has already been established already exists (step S1701 YES), the replication management program 511 proceeds to step S1702; otherwise, it proceeds to step S1703. 【0114】 In step S1702, the replication management program 511 selects the SDS2Sy used in the pre-configured replication of the DR target storage device 12Rx as the replication destination SDS2Sy. 【0115】 In step S1703, the replication management program 511 identifies and groups storage devices 12Rx that are likely to be affected simultaneously due to being in the same area or within a predetermined range of proximity. Grouping may be done based on the address, such as the "State" in the installation location information, or using clustering algorithms such as k-means based on coordinates (longitude, latitude). Furthermore, the grouping may also take into account information such as the required resources for each replication at each storage device 12Rx, in addition to the installation location information. 【0116】 Next, in step S1704, the replication management program 511 updates the location group ID 1104 of the storage device management information 111 based on the grouping results in step S1703. In step S1704, the location group ID of the storage device management information 111 is updated, and the required resource amount is updated according to the allocation of the new location group. 【0117】 Next, in step S1705, the replication management program 511 recalculates and updates the required resource management information 114 based on the results of the grouping by installation location group in step S1703. Note that even if the installation location group is updated, the correspondence between SDS2Sy and storage device 12Rx does not change, so the SDS management information 112 is not updated. 【0118】 Next, in step S1706, using the required resource management information 114 recalculated in step S1705, the SDS2Sy with the smallest total required resources 1407 for failover among the installation location group (installation location group ID 1401) to which the DR target storage device 12Rx belongs is selected as the replication destination SDS2Sy. 【0119】 In step S1706, the replication management program 511 distributes the replicated volumes related to the storage device 12Rx located at the same location to different SDS2Sy units, based on the replication relationship between the storage device 12Rx and the SDS2Sy unit predetermined in the replication management information 113. The replication management program 511 may also dynamically construct the replication relationship between the storage device 12Rx and the SDS2Sy unit to distribute the replicated volumes related to the storage device 12Rx unit at the same location to different SDS2Sy units. 【0120】 The algorithm for selecting the target SDS2Sy in this replication target SDS selection process is merely one example of a simplified implementation of the above concept, and the target SDS2Sy may be selected using a more advanced algorithm. For example, the above concept may be formulated as a constraint satisfaction problem or a mathematical programming problem, and a solution may be obtained using an existing optimization solver. 【0121】 In this replication destination SDS selection process, a single SDS2Sy is selected for all volumes 5VαR of a single storage device 12Rx. This is because a consistency group function is used to replicate data while maintaining data consistency across multiple volumes. 【0122】 However, it is not mandatory to select a single SDS2Sy for all volumes 5VαR of a single storage device 12Rx; different SDS2Sy devices may be assigned to each volume 5VαR of a given storage device 12Rx. In that case, during this replication destination SDS selection process, multiple volumes 5VαR of a given storage device 12Rx can be treated as volumes 5VαR of different storage devices 12Rx located in the same location. 【0123】 Alternatively, multiple volumes 5VαR of a certain storage device 12Rx may be grouped together, and a single SDS2Sy may be assigned to each volume 5VαR belonging to the same group. In that case, after adding information for managing the group, the replication destination SDS selection process can treat each group of multiple volumes 5VαR within a certain storage device 12Rx as a different storage device 12Rx located in the same place. 【0124】 (Pre-construction preparation process for replication according to Embodiment 1) Figure 18 is a flowchart showing the pre-construction preparation process for Embodiment 1. 【0125】 In this replication setup preparation process, the selected SDS2Sy is used as the replication destination to perform pre-checks and preparations for building the replication, and the replication destination SDS2Sy is changed according to the results of the pre-checks and preparations. 【0126】 First, in step S1801, the replication management program 511 calculates the total resource requirements for the SDS2Sy selected as the replication destination. 【0127】 Specifically, the replication management program 511 calculates the total required resources for replication (1205), the total required resources for failover (1206), and the worst-case total required resources for failover (1207), including the newly estimated DR target volumes (1206) in step S1603 of the new DR target volume registration process (Figure 16). 【0128】 Here, the total resource requirement for replication, 1205, is the sum of the total resource requirement for replication, 1406 (Figure 14), per SDS. Similarly, the total resource requirement for failover, 1206, is the maximum value for each SDS2Sy, based on the total resource requirement for failover, 1407 (Figure 14). This configuration ensures that, for example, even if a disaster occurs in the location group with the highest resource requirement, and all storage devices 12Rx in that location group fail over simultaneously, the system can handle the situation. 【0129】 Furthermore, the worst-case total resource requirement of 1207 for failover is the sum of the total resource requirement of 1407 (Figure 14) for failover for each SDS2Sy. The worst-case total resource requirement of 1207 for failover may be calculated according to the DRaaS operational policy, etc., so that even if a predetermined percentage of storage devices 12Rx in multiple regions fail over simultaneously due to a disaster, the SDS2Sy cluster does not reach its scalable limit and resource shortages do not become prolonged. 【0130】 Next, in step S1802, the replication management program 511 determines whether it is necessary to build a new SDS2Sy. In step S1802, the decision on whether to build a new SDS2Sy is based on whether the total required resources (especially the worst-case total required resources of 1207 for failover) can be satisfied by expanding the SDS2Sy cluster, as calculated in step S1801. Step S1802 checks whether the resources can be satisfied by expanding the SDS2Sy cluster, rather than whether they are currently satisfied. Other criteria may also be used to decide whether to build a new SDS2Sy. 【0131】 The replication management program 511 moves to step S1803 if it is necessary to build a new SDS2Sy (step S1802 YES), and moves to step S1806 if it is not necessary to build a new SDS2Sy (step S1802 NO). 【0132】 Next, in step S1803, the replication management program 511 uses the SDS management program 512 to construct a new SDS2Sy. The replication management program 511 constructs a new SDS2Sy if it has reached the limit of what can be expanded by the existing SDS2Sy. 【0133】 Next, in step S1804, the replication management program 511 changes the replication destination SDS2Sy to the new SDS2Sy created in step S1803. 【0134】 Next, in step S1805, the replication management program 511 changes the replication destination SDS for the DR target storage device 12Rx to the new SDS2Sy created in step S1803. In step S1805, the replication management program 511 performs configuration changes to the storage device 12Rx and SDS2Sy, and data migration between SDS2Sy devices as necessary. 【0135】 Next, in step S1806, the replication management program 511 determines whether cluster expansion of SDS2Sy is necessary. If the total required resources for replication (1205) or the total required resources for failover (1206) are less than the current total resources of SDS2Sy, cluster expansion will be performed. The storage node operation information 431αy is also referenced, and cluster expansion will be performed if there is no surplus in the total required resources for failover. If cluster expansion of SDS2Sy is necessary (step S1806 YES), the replication management program 511 moves to step S1807, and if cluster expansion is not necessary (step S1806 NO), it terminates this replication construction pre-preparation process. 【0136】 In step S1807, the replication management program 511 uses the SDS management program 512 to perform cluster expansion of the SDS2Sy selected as the replication destination. In step S1807, considering the worst-case scenario in which failover occurs on all volumes, the cluster expansion of SDS2Sy is configured to ensure that the total required resources in step S1802 (especially the worst-case total required resources of 1207 for failover) can be met by the cluster expansion of SDS2Sy in the event of failover on all volumes. If this is not possible, the system is changed to a newly constructed SDS2Sy. 【0137】 (Failover processing of a failed volume according to Embodiment 1) Figure 19 is a flowchart showing the failover process for a failed volume according to Embodiment 1. This failover process is executed by the replication management program 511 when the I / O processing that was being handled by the storage device 12Rx is failed over to the SDS2Sy based on instructions from the customer who has contracted for DRaaS. 【0138】 First, in step S1901, the replication management program 511 receives a failover instruction from the customer to the DR management system 100 (including the specification of the target storage device 12Rx and volume 5VαR). 【0139】 Next, in step S1902, the replication management program 511 uses the storage device management program 513 and the SDS management program 512 to switch the primary and secondary volumes of the replication (replication source and replication destination). During the processing of step S1902, the replication management program 511 updates the replication status 1308 of the corresponding replication ID 1301 in the replication management information 113 to "Failover". After the processing of step S1902, the I / O processing to volume 5VαR of the storage device Rx is taken over by SDS2Sy, and subsequent I / O requests are stored in volume 1Vαy on the SDS2Sy side. The primary and secondary volumes are switched in order to reflect the data from these I / O operations in volume 5VαR on the storage device 12Rx side. If a failure occurs in the storage device 12Rx and the data cannot be reflected immediately, it will be reflected when it is recovered. 【0140】 Next, in step S1903, the replication management program 511 determines whether cluster expansion of SDS2Sy is necessary. In step S1903, it determines whether cluster expansion is necessary to secure a predetermined amount of usable resources for SDS2Sy in preparation for the next failover. It also refers to the storage node operation information 431αR and performs cluster expansion if there is insufficient room to secure the total required resources of 1407 for failover. 【0141】 The replication management program 511 moves to step S1904 if cluster expansion of SDS2Sy is required (step S1903 YES), and terminates this failover process if cluster expansion of SDS2Sy is not required (step S1903 NO). In step S1904, the replication management program 511 performs cluster expansion of SDS2Sy. 【0142】 The registration of connection information between volume 1Vαy provided by SDS2Sy and the application server is performed in this failover process after the primary / secondary switchover in step S1902 is completed, based on customer instructions. Because failovers may occur in quick succession, after the failover in step S1902 is performed, step S1904 is immediately performed to add any insufficient resources. 【0143】 (Failback processing of a faulty volume according to Embodiment 1) Figure 20 is a flowchart showing the failback process for a failed volume according to Embodiment 1. This failback process is performed by the replication management program 511 when it fails back the I / O processing that was being handled by SDS2Sy to the storage device 12Rx, based on instructions from the customer who has contracted for DRaaS. 【0144】 First, in step S2001, the replication management program 511 receives a failback instruction from the customer to the DR management system 100 (including the specification of the target storage device 12Rx and volume 5VαR). 【0145】 Next, in step S2002, the replication management program 511 uses the storage device management program 513 and the SDS management program 512 to switch the primary and secondary volumes for replication (the source and destination volumes). During the processing in step S2002, the replication management program 511 updates the replication status 1308 of the corresponding replication ID 1301 in the replication management information 113 to "Normal". 【0146】 Next, in step S2003, the replication management program 511 determines whether it is necessary to reduce the SDS2Sy cluster size. In step S2003, if failback results in a surplus of resources, and reducing the cluster size (reducing the number of SDS2Sy nodes) still provides enough resources to meet the total failover resource requirement of 1407 for each SDSID 1402, then the surplus cluster size is reduced. By reducing the surplus cluster size, the operating costs of SDS2Sy are reduced. 【0147】 The replication management program 511 moves to step S2004 if cluster reduction of SDS2Sy is necessary (step S2003YES), and terminates this failback process if cluster reduction of SDS2Sy is not necessary (step S2003NO). In step S2004, the replication management program 511 performs cluster reduction of SDS2Sy. 【0148】 In the above-described embodiment 1, the failover destinations for storage devices 12Rx for multiple customers are distributed to multiple SDS2Sy devices, and a multi-tenant operation is performed in which multiple customers share the SDS2Sy devices. This allows the surplus resources of the SDS2Sy devices, which are reserved in advance of failover, to be shared among the multiple customers according to their maximum requirements, thereby reducing surplus computing resources and lowering the operating costs of DRaaS. 【0149】 Furthermore, the backup destination SDS2Sy is selected so that it is distributed across the installation locations (regions) of the storage devices 12Rx. While the backup destination SDS2Sy can be determined dynamically, a mapping is pre-established so that elements belonging to a predetermined group, such as a consistency group, do not distribute to the same SDS2Sy and instead use it as the failover destination. This reduces the operational costs of DRaaS while enabling rapid failover. 【0150】 [Embodiment 2] In Embodiment 1, it is assumed that the SDS2Sy, the disaster recovery destination for the storage device 12Rx, resides in a public cloud (or private cloud) managed by the DRaaS provider. However, there is a possibility that the area where the public cloud is located may be affected by a disaster, rendering the public cloud unusable. 【0151】 Therefore, in Embodiment 2, considering the possibility that the SDS2Sy itself at the disaster recovery destination may be affected by a disaster, a configuration is used in which the public cloud (or private cloud) where the SDS2Sy is installed exists in multiple regions. In Embodiment 2, when a new SDS2Sy is built, the SDS2Sy is built on the designated public cloud. 【0152】 Embodiment 2 will primarily describe the differences from Embodiment 1. 【0153】 (Configuration of Information Processing System 2S according to Embodiment 2) Figure 21 is a diagram showing the configuration of the information processing system 2S according to Embodiment 2. 【0154】 The information processing system 2S consists of storage devices 12Rx (12X1, 12X2, 12Y1, 12Y2, 12Z1, 12Z2), SDS2Sy (2S1, 2S2, 2S3), and a DR management system 100B. The SDS2Sy and the DR management system 100B constitute a DR system built on the cloud by the DRaaS provider. 【0155】 In the information processing system 2S, multiple storage devices 12Rx for multiple customers are located in geographically distant regions X, Y, and Z that will not be affected by the same disaster simultaneously. Compared to the information processing system 1S of Embodiment 1, the information processing system 2S further includes storage devices 12Z1 and 12Z2 operated in a customer-managed data center in region Z. 【0156】 Furthermore, in the information processing system 2S, multiple SDS2Sy instances are deployed in regions X, Y, and Z. SDS2S1 is operated in the data center in region Y. SDS2S2 is operated in the data center in region Z. SDS2S3 is operated in the data center in region X. 【0157】 In the information processing system 2S, the data stored in each volume 5VαR (5V1X, 5V2X, 5V3X, 5V4X, 5V1Y, 5V2Y, 5V3Y, 5V4Y, 5V1Z, 5V2Z, 5V3Z, 5V4Z) of the customer-managed storage device 12Rx is pre-replicated (copied) to one of the SDS2Sy devices. 【0158】 In the information processing system 2S, if a failure occurs in any of the storage devices 12Rx, the I / O processing for volume 5VαR will be taken over (failover) by volume 1Vβy (1V11, 1V21, 1V31, 1V41) of one of the replication destination SDS2Sy devices. 【0159】 Storage device 12Z1 comprises CPUs 6CZ1 and 6CZ2, and volumes 5V1Z and 5V2Z, which process I / O from applications 7A1Z and 7A2Z via CPUs 6CZ1 and 6CZ2. Similarly, storage device 12Z2 comprises CPUs 6CZ3 and 6CZ4, and volumes 5V3Z and 5V4Z, which process I / O from applications 7A3Z and 7A4Z via CPUs 6CZ3 and 6CZ4. SDS2S1 and 2S2 are SDS clusters on the cloud. SDS2S1 and 2S2 are connected to storage devices 12X1, 12X2, 12Y1, and 12Y2 via network 250, and constitute a disaster recovery (DR) system for storage devices 12X1, 12X2, 12Y1, and 12Y2. 【0160】 The SDS2S3 consists of CPUs 4C13 and 4C23, and volumes 1V13, 1V23, 1V33, and 1V43, which are processed by CPUs 4C13 and 4C23. 【0161】 SDS2S1 has the necessary number of CPUs 4C11, 4C21 to perform I / O on any of the volumes 5V1X, 5V2X in region X or volumes 5V3Z, 5V4Z in region Z, which SDS2S1 may fail over to simultaneously in the event of a disaster. Similarly, SDS2S2 has the necessary number of CPUs 4C12, 4C22 to perform I / O on any of the volumes 5V3X, 5V4X in region X or volumes 5V3Y, 5V4Y in region Y, which SDS2S2 may fail over to simultaneously in the event of a disaster. Similarly, SDS2S3 has the necessary number of CPUs 4C13, 4C23 to perform I / O on any of the volumes 5V1Y, 5V2Y in region Y or volumes 5V1Z, 5V2Z in region Z, which SDS2S3 may fail over to simultaneously in the event of a disaster. 【0162】 Compared to the DR management system 100 of Embodiment 1, the DR management system 100B further includes SDS installation location management information 115 (Figure 22) as DR management information 52 in the memory 13, and has SDS management information 112B (Figure 23) instead of SDS management information 112. 【0163】 In this way, the SDS2Sy disaster recovery (DR) destinations are distributed across the installation locations of the storage device 12Rx, and an SDS2Sy from a different region than the region where the storage device 12Rx is installed is selected as the DR destination. 【0164】 In the example in Figure 21, if region X is affected by a disaster, volumes 1V11 and 1V21 of SDS2S1 will handle I / O from applications 3A11 and 3A21, thereby taking over I / O processing from applications 7A1X and 7A2X to volumes 5V1X and 5V2X. Also, if region X is affected by a disaster, volumes 1V21 and 1V22 of SDS2S2 will handle I / O from applications 3A21 and 3A22, thereby taking over I / O processing from applications 7A3X and 7A4X to volumes 5V3X and 5V4X. 【0165】 Multiple SDS2Sy devices may be located in regions X1, Y1, and Z1 of the regions X, Y, Z, X1, Y1, and Z1, which are geographically distant from each other and will not be affected simultaneously. At least one of the following conditions may be met: region X1 = region X, region Y1 = region Y, and region Z1 = region Z. 【0166】 (SDS installation location management information 115 related to Embodiment 2) Figure 22 shows the SDS installation location management information 115 according to Embodiment 2. The SDS installation location management information 115 is information for managing the installation location of SDS2Sy (the public cloud which is the platform on which SDS2Sy is built). The SDS installation location management information 115 is information that is pre-registered by the DRaaS provider. 【0167】 The SDS installation location management information 115 manages, for example, an installation location code 2201 in association with installation location information 2202, which includes the location name and coordinate information. The SDS installation location management information 115 may also include authentication information for using the public cloud. 【0168】 When building a new SDS2Sy, the SDS management program 512 receives location code 2201 and builds the SDS on a public cloud (or private cloud) corresponding to location code 2201. 【0169】 (SDS management information 112B related to Embodiment 2) Figure 23 shows the SDS management information 112B according to Embodiment 2. In addition to the SDS management information 112 of Embodiment 1 (Figure 12), the SDS management information 112B includes information on the installation location code 2301 indicating the installation location of the SDS. 【0170】 (Replication destination SDS selection process according to Embodiment 2) Figure 24 is a flowchart showing the replication destination SDS selection process according to Embodiment 2. In Embodiment 2, in the new registration process for DR target volumes (Figure 16), the replication destination SDS selection process according to Embodiment 2 is executed instead of the replication destination SDS selection process according to Embodiment 1 (Figure 17). Also, in the replication construction preparation process according to Embodiment 1 (Figure 18), when constructing a new SDS2Sy, it is necessary to construct the SDS2Sy using the same installation location code as the originally selected SDS2Sy. 【0171】 The replication destination SDS selection process according to Embodiment 2 differs from the replication destination SDS selection process according to Embodiment 1 (Figure 17) in that step S1706B is executed instead of step S1706, but otherwise it is the same. 【0172】 In step S1706B, the replication management program 511 selects as the replication destination SDS2S1 from the installation location group (installation location group ID 1401) to which the DR target storage device 12Rx belongs, which is sufficiently far away from the DR target storage device 12Rx so as not to be affected simultaneously in the same disaster, and which has the smallest total failover resource requirement 1407. In other words, it excludes SDS2S1 located near the installation location group of the DR target storage device 12Rx from the selection. 【0173】 [Other embodiments] In the embodiment described above, the duplicate volumes of the storage device 12Rx are distributed across multiple SDS2Sy devices. However, the distribution is not limited to duplicate volumes. That is, the DR management systems 100 and 100B may also select equipment, including controllers and communication ports of the backup destination SDS2Sy devices where the duplicate volumes are located, so that these devices are distributed across the installation locations of the storage device 12Rx in units of 5VαR volumes. 【0174】 The present invention is not limited to the embodiments described above and includes various modifications. For example, the embodiments described above are explained in detail to make the present invention easier to understand and are not necessarily limited to those having all the configurations described. Furthermore, as long as it does not contradict the present invention, it is possible to replace some of the configurations of one embodiment with those of another embodiment, and to add configurations of other embodiments to the configuration of one embodiment. Furthermore, it is possible to add, delete, replace, integrate, or distribute some of the configurations of each embodiment. In addition, the configurations and processes shown in the embodiments can be distributed, integrated, or rearranged as appropriate based on processing efficiency or implementation efficiency. [Explanation of symbols] 【0175】 1S, 2S: Information processing system; 12Rx (12X1, 12X2, 12Y1, 12Y2): Storage device; 2Sy (2S1, 2S2): SDS; 5VαR (5V1X, 5V2X, 5V3X, 5V4X), 1Vβy (1V11, 1V21, 1V31, 1V41, 1V12, 1V22, 1V32, 1V42): Volume; 100: DR management system.

Claims

[Claim 1] An information processing system comprising multiple storage systems having multiple storage devices installed in multiple regions and multiple storage nodes located in the cloud, and a management system, The processor in the aforementioned management system is The configuration information and operational information of the volumes possessed by the plurality of storage devices are obtained from each of the storage devices. Based on the configuration information and the operational information, the amount of replication resources required in the storage system to create a replicated volume in the storage system that will failover the volume owned by each storage device, and the amount of failover resources required in the storage system to failover the volume using the replicated volume are estimated. For each group of installation locations where a failure may occur simultaneously based on the installation location, the plurality of storage devices are grouped together. For each installation location group and each storage system, the amount of resources required for replication and the amount of resources required for failover pertaining to the volume of each storage device are aggregated. As the storage system to which the replicated volume is created, the storage system is selected such that the amount of failover resources aggregated for each installation location group and each storage system is minimized, while distributing the replicated volume relating to the multiple storage devices located in the same region across the multiple storage systems. Perform replication to create the replicated volume on the selected replication destination storage system. An information processing system characterized by the following: [Claim 2] The information processing system according to claim 1, The aforementioned processor, The amount of resources required for replication is estimated by estimating the required resources of the processor, memory, and storage capacity of the storage system. The amount of resources required for failover is estimated by estimating the required resources for the processor and memory of the storage system. An information processing system characterized by the following: [Claim 3] The information processing system according to claim 1, The aforementioned processor, The total required resources are calculated based on the amount of resources required for replication and the amount of resources required for failover in the storage system that is the replication destination. Determine whether the storage system that is the replication destination can meet the total required resources. If the storage system that is the replication destination determines that it cannot meet the total required resources, the cluster expansion of the storage system will be performed. An information processing system characterized by the following: [Claim 4] The information processing system according to claim 3, The aforementioned processor, If the storage system that is the replication destination determines that it cannot meet the total required resources even after performing the cluster expansion, a new storage system is constructed. The new storage system is changed to the storage system that is the replication destination. An information processing system characterized by the following: [Claim 5] The information processing system according to claim 1, The aforementioned processor, When a failover of the volume on the storage device is performed, it is determined whether it is necessary to secure the amount of usable resources of the storage system. When it is determined that securing the aforementioned amount of resources is necessary, the storage system cluster expansion will be performed. An information processing system characterized by the following: [Claim 6] The information processing system according to claim 5, The aforementioned processor, When failback is performed on the volume of the storage device, it is determined whether the required resources for failover can be secured even if the storage system cluster is reduced. When it is determined that the aforementioned resource amount is secured, the cluster reduction of the storage system is performed. An information processing system characterized by the following: [Claim 7] The information processing system according to claim 1, The aforementioned processor, The duplicate volumes of the multiple volumes of one storage device are constructed on the same storage system. An information processing system characterized by the following: [Claim 8] The information processing system according to claim 1, The aforementioned processor, The duplicate volumes of the multiple volumes of one storage device are constructed on multiple storage systems. An information processing system characterized by the following: [Claim 9] The information processing system according to claim 1, The aforementioned processor, The equipment, including the controller and communication ports, related to the storage system that is the replication destination for creating the replicated volume is selected to be distributed among the volumes. An information processing system characterized by the following: [Claim 10] The information processing system according to claim 1, The aforementioned multiple storage systems are installed in the aforementioned multiple regions, The aforementioned processor, The storage system to which the replication destination is selected is such that the multiple replicated volumes relating to the multiple storage devices located in the same region are distributed among the multiple storage systems located at locations other than that location. An information processing system characterized by the following: [Claim 11] An information processing method in an information processing system having multiple storage devices installed in multiple regions, multiple storage systems having multiple storage nodes located in the cloud, and a management system, The processor in the aforementioned management system The configuration information and operational information of the volumes possessed by the plurality of storage devices are obtained from each of the storage devices. Based on the configuration information and the operational information, the amount of replication resources required in the storage system to create a replicated volume in the storage system that will failover the volume owned by each storage device, and the amount of failover resources required in the storage system to failover the volume using the replicated volume are estimated. For each group of installation locations where a failure may occur simultaneously based on the installation location, the plurality of storage devices are grouped together. For each installation location group and each storage system, the amount of resources required for replication and the amount of resources required for failover pertaining to the volume of each storage device are aggregated. As the storage system to which the replicated volume is created, the storage system is selected such that the amount of failover resources aggregated for each installation location group and each storage system is minimized, while distributing the replicated volume relating to the multiple storage devices located in the same region across the multiple storage systems. Perform replication to create the replicated volume on the selected replication destination storage system. An information processing method characterized by including each of the processes.

Images