Data management device and DR cost calculation support method

Abstract

To provide a data management device for supporting operation by calculating cost at the time of a disaster of the volume of a DR site of a virtual environment, and a DR cost calculation support method.SOLUTION: A data management device being a restoration support device includes a DR operation phase determination part for executing DR operation phase determination processing on the basis of a copy situation table for managing copy configuration information for managing a pair configuration of an object task use volume and a copy volume, and copy situations in the object task use volume and the copy volume in acquiring object task specification information for specifying an object task, and a disaster correspondence cost calculation part for calculating a usage fee of a DR site of a cloud environment until calculating a disaster pattern corresponding to a disaster situation of the volume of an affected disaster object in accordance with the calculated operation phase and completing a system recovery of a use site with a use volume created from a fault occurrence in each disaster pattern.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a data management device and a DR cost calculation support method for generating information regarding a disaster-related event in a volume. [Background technology]

[0002] There is a technology called failover that uses an alternative server to take over the processing of the normally used server in an on-premises environment when a failure occurs in the server that is normally used. The alternative server is a copy of the normally used server. In many cases, it is cheaper to build an alternative server in a cloud environment than in an on-premises environment. Therefore, in many cases, the alternative server is built in a cloud environment. There is also technology that addresses the cost of the alternative server in the cloud environment used for failover.

[0003] For example, the technology described in Patent Document 1 uses a first server in an on-premise environment that executes a service, and a second server in a virtual environment to which the execution of the service of the first server is failed over in the event of a disaster (failure) occurring in the first server. Also, the technology described in Patent Document 1 creates the second server in the virtual environment using a spot instance in a cloud environment that can be used at low cost.

[0004] A second server created using a spot instance in a cloud environment can be used at a lower price than a server created using a regular instance, because the cloud provider may forcefully terminate the server. With the technology described in Patent Document 1, when it is detected that the second virtual server will become unavailable due to the cloud provider's forced termination, a third virtual server is created that copies and takes over the instance information of the second virtual server, and the third virtual server is used in place of the second virtual server. By using the technology described in Patent Document 1, it is possible to use a server in a virtual environment used for failover while keeping costs down when no failures occur. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2020-129184 Summary of the Invention [Problem to be solved by the invention]

[0006] By the way, when the technology described in Patent Document 1 is used, the cost that can be reduced is the cost (referred to as the "cost during normal operation") of the second server (alternative server) when no failure occurs in the first server (server in normal use). Also, the second server (alternative server) is a server provided at a DR site in a cloud environment that is used to prepare for failures (disasters). Data used by the server is stored in a volume.

[0007] When operating a DR site, it is advisable to consider the overall cost of the DR site. The overall cost of the DR site includes costs other than those incurred during normal operation. For example, the overall cost of a DR site for a virtual environment includes the costs of the following volumes 1 and 2 in the event of a disaster. 1. The cost of reading and writing data from the volume created at the DR site in the cloud environment during failover (referred to as "failover cost"). 2. The cost of reading data from the volumes created at the DR site to recover the servers that are normally in use (referred to as the "cost of reading data").

[0008] In many cases, the costs incurred in the event of disasters 1 and 2 vary depending on the capacity of the volumes created at the DR site, the amount of data read from the volumes created at the DR site, etc. Therefore, there is a need for technology that can easily calculate the costs incurred in the event of disasters 1 and 2.

[0009] When operating a DR site for a cloud environment, the decision on whether to use a volume for the DR site for a cloud environment may be made after taking into consideration the overall cost of the DR site for a cloud environment, including the costs incurred in the event of disasters 1 and 2. In particular, when using DR sites for multiple cloud environments while keeping costs down, it may be necessary to be able to easily calculate the costs incurred in the event of disasters 1 and 2.

[0010] Therefore, an object of the present invention is to provide a data management device and a DR cost calculation support method that support the operation of a DR site by calculating the cost of a volume at the DR site in a virtual environment in the event of a disaster. [Means for solving the problem]

[0011] In order to achieve the above object, one aspect of the DR cost calculation support method of the present invention is a DR cost calculation support method in a data management device that generates information on disaster damage to volumes, the data management device comprising a storage device and a processor, the storage device stores: task identification information that identifies a task; information on volumes in use used by the task; and information on volumes that form pairs of the volumes in use and backup or DR, in association with each other; and cloud cost information that associates and stores information on sites in a cloud environment and costs incurred for using volumes in the cloud environment, and when the processor acquires target task identification information that identifies a target task, it refers to the copy configuration information and calculates a copy volume for a target task-used volume used by the target task. a correspondence pattern calculation process that calculates a disaster pattern that may occur in the disaster-target volume according to the operation phase calculated by the DR operation phase determination unit, and calculates a volume copy pair of the disaster-target volume and a copy volume that stores data to be restored and copied to the disaster-target volume in response to the calculated disaster pattern; and a disaster response cost calculation process that uses the cloud cost information to calculate the usage fee for the DR site in the cloud environment from the occurrence of a failure in the disaster pattern calculated by the correspondence pattern calculation unit until system recovery is completed at the usage site where the usage volume is created.

[0012] Furthermore, one aspect of the data management device of the present invention is a data management device that generates information regarding damage to volumes, and includes a storage unit, a DR operation phase determination unit, a correspondence pattern calculation unit, and a disaster response cost calculation unit, wherein the storage unit stores: task identification information that identifies a task; copy configuration information that associates and stores information on volumes in use used for the task; and information on volumes that form pairs of the volumes in use with backup or DR; and cloud cost information that associates and stores information on sites in a cloud environment with information on costs required to use volumes in the cloud environment; and when the DR operation phase determination unit acquires target task identification information that identifies a target task, the DR operation phase determination unit references the copy configuration information and determines a target task usage phase based on information on copy volumes for target task usage volumes used by the target task. The correspondence pattern calculation unit executes a DR operation phase determination process to calculate the operation phase of the operation of the cloud DR copy volume of the cloud site for the volume, and the correspondence pattern calculation unit calculates a disaster pattern that may occur in the disaster-target volume according to the operation phase calculated by the DR operation phase determination unit, and executes a correspondence pattern calculation process to calculate a volume copy pair between the disaster-target volume and a copy volume that stores data to be restored and copied to the disaster-target volume in response to the calculated disaster pattern, and the disaster response cost calculation unit executes a disaster response cost calculation process using the cloud cost information to calculate the usage fee for the DR site of the cloud environment from the occurrence of a failure in the disaster pattern calculated by the correspondence pattern calculation unit to the completion of system recovery of the usage site where the usage volume is created. [Effects of the Invention]

[0013] According to a representative embodiment of the present invention, the operation of a DR site is supported by calculating the cost of a volume at a DR site in a virtual environment in the event of a disaster. Problems, configurations, and effects other than those described above will become clear from the description of the following embodiment. [Brief explanation of the drawings]

[0014] [Figure 1]FIG. 1 is a diagram illustrating an example of a functional block diagram of a data management device according to an embodiment. [Figure 2] FIG. 2 is an explanatory diagram illustrating damage to data. [Figure 3] FIG. 3 is an explanatory diagram illustrating a data recovery method. [Figure 4] FIG. 4 is a block diagram illustrating an example of a hardware configuration of the data management device. [Figure 5] FIG. 5 is a diagram showing an example of the volume group table 31. As shown in FIG. [Figure 6] FIG. 6 is a diagram showing an example of the service level management table 32. As shown in FIG. [Figure 7] FIG. 7 is a diagram showing an example of the main site disaster response pattern table 33. As shown in FIG. [Figure 8] FIG. 8 is a diagram showing an example of the copy configuration table 34. As shown in FIG. [Figure 9] FIG. 9 is a diagram showing an example of the copy status table 35. As shown in FIG. [Figure 10] FIG. 10 is a diagram showing an example of the business data usage status table 36. As shown in FIG. [Figure 11] FIG. 11 is a diagram illustrating an example of the public cloud cost table 37. As shown in FIG. [Figure 12A] FIG. 12A is a diagram showing an example of the disaster response cost table 38A. [Figure 12B] FIG. 12B is a diagram showing an example of disaster response cost table 38B. [Figure 12C] FIG. 12C is a diagram showing an example of disaster response cost table 38C. [Figure 13] FIG. 13 is a diagram showing an example of the cost analysis screen. [Figure 14] FIG. 14 is a flowchart illustrating an example of a DR operation phase determination process according to the embodiment. [Figure 15] FIG. 15 is a flowchart illustrating an example of a pre-operation correspondence pattern calculation process according to the embodiment. [Figure 16] FIG. 16 is a flowchart illustrating an example of a process for calculating a response pattern during normal operation according to the embodiment. [Figure 17] FIG. 17 is a flowchart illustrating an example of a process for calculating a response pattern to a disaster during operation according to the embodiment. [Figure 18] FIG. 18 is a flowchart illustrating an example of a disaster response cost calculation process according to the embodiment. [Figure 19] FIG. 19 is a diagram showing an example of the cost analysis screen. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will readily understand that the specific configuration can be changed without departing from the spirit or intent of the present invention.

[0016] In the configuration of the invention described below, the same or similar configurations or functions are denoted by the same reference numerals, and redundant explanations will be omitted.

[0017] In this specification, the terms "first," "second," "third," etc. are used to identify components and do not necessarily limit the number or order.

[0018] In this specification, various types of information may be described as an example using the expression "XX table," but may also be expressed as a data structure such as "XX list" or "XX queue." Furthermore, "XX table" may also be expressed as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable.

[0019] <System configuration> 1 is an explanatory diagram illustrating an outline of the functions of a data management device 1 according to an embodiment. As shown in FIG. 1, the data management device 1 is connected to an on-premise system 100, a cloud site 200, and a user terminal 500 via a network NW.

[0020] The on-premise system 100 includes a host device 110 and an on-premise storage system 120. The host device 110 stores a plurality of business programs 111. The host device 110 is accessed by a user terminal 500 via a network NW. A user of the user terminal 500 can operate the user terminal 500 to use the business programs 111 of the host device 110 via the user terminal 500.

[0021] Volumes are created in the on-premise storage system 120. In the on-premise storage system 120, a usage volume 121 that stores data created by a business program 111 of a host device 110, and a local backup volume 122 that is a backup of the usage volume 121 are created. A copy of the usage volume 121 is created as the local backup volume 122 at predetermined time intervals. The usage volume 121 is a usage volume used for business purposes.

[0022] Cloud site 200 is a site where cloud DR copy volume 221 is created, which is synchronized with usage volume 121. In the example of Figure 1, cloud site 200 has an alternative host device 210 that is an alternative to host device 110, and cloud DR copy volume 221 that is a copy of usage volume 121.

[0023] The alternative host device 210 is created for failover purposes. That is, when the host device 110 is damaged, the alternative host device 210 can take over the functions of the host device 110 by taking over the processing of the host device 110.

[0024] The network NW may be a wired network or a wireless network, or may be a global network such as the Internet.

[0025] As described above, a copy of the usage volume 121 in the on-premise storage system 120 is created in the local backup volume 122 and the cloud DR copy volume 221. When the usage volume 121 is damaged by a disaster, the usage volume 121 can be restored using the local backup volume 122 or the cloud DR copy volume 221.

[0026] The configuration may also be such that the local backup volume 122, cloud DR copy volume 221, and cloud site 200 do not exist. The data management device 1 is also able to accommodate configurations in which the local backup volume 122, cloud DR copy volume 221, and cloud site 200 do not exist.

[0027] As shown in Figure 1, the data management device 1 has a DR operation phase determination unit 11, a pre-operation response pattern calculation unit 12, a normal operation response pattern calculation unit 13, a disaster operation response pattern calculation unit 14, a disaster response cost calculation unit 15, a storage management unit 16, and a public cloud management unit 17.

[0028] The DR operation phase determination unit 11 calculates the operation phase of the cloud DR copy volume 221 of the cloud site 200 in the cloud environment for the used volume 121.

[0029] The operation phase is the state of the used volume 121 and the cloud DR copy volume 221. The operation phase includes three phases: "pre-operation," "normal operation," and "disaster operation." Operation phases may include phases other than these three.

[0030] "Before operation" is a state in which the cloud DR copy volume 221 has not been created. "Normal operation" is a state in which the cloud DR copy volume 221 has been created, and the used volumes 121 and the like have not been affected by a disaster and can be used normally. "Disaster during operation" is a state in which the cloud DR copy volume 221 has been created, and the used volumes 121 and the like cannot be used normally.

[0031] The pre-operation response pattern calculation unit 12 executes a pre-operation response pattern calculation process when the operation phase calculated by the DR operation phase determination unit 11 is "pre-operation." In the pre-operation response pattern calculation process, a disaster pattern is calculated in which a disaster-affected volume occurs in a state in which the cloud DR copy volume 221 has been created in the "pre-operation" state. The disaster pattern represents the level of failure (degree of damage) and the status of the volume to which data has been copied from the used volume and the used volume. Then, the disaster pattern pre-operation response pattern calculation process calculates a pair of volume copies, each pair consisting of a disaster-affected volume and a copy volume storing data to be restored and copied to the disaster-affected volume, in response to the calculated disaster pattern. Here, examples of the pair of volume copies include the pair of the used volume 121 and the local backup volume 122 (R1 in FIG. 1) and the pair of the used volume 121 and the cloud DR copy volume 221 (R2a and R2d in FIG. 1) shown in FIG. 1.

[0032] The normal operation response pattern calculation unit 13 executes a normal operation response pattern calculation process when the operation phase calculated by the DR operation phase determination unit 11 is "normal operation."

[0033] The disaster-during-operation response pattern calculation unit 14 executes a disaster-during-operation response pattern calculation process when the operation phase calculated by the DR operation phase determination unit 11 is "disaster-during-operation."

[0034] The pre-operation response pattern calculation unit 12, the normal operation response pattern calculation unit 13, and the disaster operation response pattern calculation unit 14 are response pattern calculation units that execute the response pattern calculation process.

[0035] The pre-operation response pattern calculation process, the normal operation response pattern calculation process, and the disaster operation response pattern calculation process are response pattern calculation processes. In the response pattern calculation process, the DR operation phase determination unit calculates a disaster pattern that may occur in a disaster-target volume according to the operation phase calculated by executing the DR operation phase determination process, and calculates a volume copy pair of the disaster-target volume and a copy volume storing data to be copied to the disaster-target volume for recovery purposes in response to the calculated disaster pattern.

[0036] The disaster response cost calculation unit 15 executes a disaster response cost calculation process to calculate and output the usage fee for the DR site in the cloud environment from the occurrence of a failure in the disaster pattern calculated by the response pattern calculation unit (pre-operation response pattern calculation unit 12, normal operation response pattern calculation unit 13, and disaster operation response pattern calculation unit 14) until system recovery is completed at the usage site where the usage volume is created.

[0037] The storage management unit 16 can monitor and operate resources such as volumes created in the on-premise storage system 120.

[0038] The public cloud management unit 17 can monitor and operate resources such as host instances and volumes created in the cloud site 200. Billing information for cloud usage is also managed here.

[0039] 2, there are various causes of damage to the used volume 121. There are also various methods for recovering data from the used volume 121. Furthermore, the length of the target recovery time for the system varies depending on the state of the damage.

[0040] As shown in Figure 3, there are various ways to copy data during recovery. The recovery pattern ID in Figure 3 indicates a set of volume copies, in response to a disaster pattern, between a disaster-affected volume and a copy volume that stores data to be copied to the disaster-affected volume. The recovery pattern IDs R1, R2a, and R2d are shown in Figure 1. The data management device 1 has the following configuration so that the cost of recovery can be calculated.

[0041] <Hardware configuration of data management device 1> Fig. 4 is a block diagram showing an example of the hardware configuration of the data management device 1. As shown in Fig. 4, the data management device 1 has a processor 21, a main memory device 22, a secondary memory device 23, an input device 24, an output device 25, a network I / F 26, and a bus 27 connecting these. The data management device 1 can be realized by a general information processing device such as a PC or a server computer.

[0042] The processor 21 reads data and programs stored in the secondary storage device 23 into the main storage device 22 and executes processing defined by the programs. The DR operation phase determination unit 11 described above with reference to FIG. 1 is realized by the processor 21 reading the DR operation phase determination program 11a stored in the secondary storage device 23 into the main storage device 22 and executing it. Similarly, the pre-operation response pattern calculation unit 12, the in-operation normal state response pattern calculation unit 13, the in-operation disaster response pattern calculation unit 14, the disaster response cost calculation unit 15, the storage management unit 16, and the public cloud management unit 17 are realized by the processor 21 reading the pre-operation response pattern calculation program 12a, the in-operation normal state response pattern calculation program 13a, the in-operation disaster response pattern calculation program 14a, the disaster response cost calculation program 15a, the storage management program 16a, and the public cloud management program 17a into the main storage device 22 and executing them, respectively.

[0043] In this specification, when a process is described using a sentence with the DR operation phase determination unit 11, which is a functional unit, as the subject, it means that the processor 21 is executing a program (DR operation phase determination program 11a) that realizes the functional unit. Similarly, when a process is described using a sentence with the pre-operation response pattern calculation unit 12, the in-operation normal state response pattern calculation unit 13, the in-operation disaster response pattern calculation unit 14, the disaster response cost calculation unit 15, the storage management unit 16, or the public cloud management unit 17, which are functional units, as the subject, it means that the processor 21 is executing the programs (pre-operation response pattern calculation program 12a, the in-operation normal state response pattern calculation program 13a, the in-operation disaster response pattern calculation program 14a, the disaster response cost calculation program 15a, the storage management program 16a, and the public cloud management program 17a) that realize the functional units.

[0044] The main storage device 22 has a volatile storage element such as a RAM, and stores the programs executed by the processor 21 and data.

[0045] The secondary storage device 23 has nonvolatile storage elements such as HDDs (Hard Disk Drives) and SSDs (Solid State Drives) and stores programs, data, etc. The secondary storage device 23 has installed therein a DR operation phase determination program 11a, a pre-operation response pattern calculation program 12a, a normal operation response pattern calculation program 13a, a disaster operation response pattern calculation program 14a, a disaster response cost calculation program 15a, a storage management program 16a, a public cloud management program 17a, and an operation monitoring program 18a. The secondary storage device 23 also stores a volume group table 31, a service level management table 32, a primary site disaster response pattern table 33, a copy configuration table 34, a copy status table 35, a business data usage status table 36, a public cloud cost table 37, and a disaster response cost table 38 (disaster response cost tables 38A to 38C).

[0046] The storage management program 16a is a program used for managing storage. The public cloud management program 17a is a program used for managing public clouds. The processor 21 reads the storage management program 16a and the public cloud management program 17a into the main storage device 22 and executes them to create a copy configuration table 34. The operation monitoring program 18a is a program that acquires information on the volume configuration and the reading and writing of volume data. The processor 21 reads the operation monitoring program 18a into the main storage device 22 and executes it to create a copy status table 35 and a business data usage status table 36.

[0047] The volume group table 31, details of which will be described later with reference to FIG. 5, stores information on the volume IDs of the volumes included in a volume group. A volume group is a group of volumes that brings together multiple volumes. Multiple volumes are associated with one volume group. The data management device 1 can refer to the volume group table 31 to obtain the volume IDs of the volumes included in a volume group.

[0048] The service level management table 32, the details of which will be described later with reference to FIG. 6, stores information relating to the target time interval required for the recovery of business-related data.

[0049] The main site disaster response pattern table 33, the details of which will be described later with reference to FIG. 7, stores information on the disaster status of volumes and recovery patterns.

[0050] The copy configuration table 34, details of which will be described later using Fig. 8, stores information about copy volumes for volumes. The copy configuration table 34 stores copy configuration information that associates a business name (business identification information) that identifies a business, information about the volumes used in the business, and information about the copy volumes that are copies of the volumes used.

[0051] The copy status table 35, the details of which will be described later with reference to FIG. 9, stores information relating to volumes and the status of the copied volumes.

[0052] The business data usage status table 36, the details of which will be described later with reference to FIG. 10, stores information relating to the usage status of data used in business.

[0053] The public cloud cost table 37, the details of which will be described later with reference to FIG. 11, stores information on the costs incurred to use volumes on a site in a cloud environment.

[0054] Disaster response cost table 38 (disaster response cost tables 38A to 38C), details of which will be described later using Figures 12A to 12C, stores information regarding the usage fees for the DR site in the cloud environment during the recovery time required for data recovery, which involves copying data using a set of volume copies.

[0055] The input device 24 is a device such as a keyboard or mouse that accepts user operations and acquires information input by the user's operations. The output device 25 is a device such as a display that outputs information and presents information to the user by displaying it on a screen, for example. The data management device 1 may also be equipped with a touch panel that serves as both the input device 24 and the output device 25.

[0056] The network I / F 26 is an interface (transmitting / receiving device) that can transmit and receive data via the network NW with devices such as the on-premise system 100 and the cloud site 200. The data management device 1 can use the network I / F 26 to transmit and receive data with devices such as the on-premise system 100 and the cloud site 200 that are connected to the network NW.

[0057] Like the data management device 1, the host device 110 and the user terminal 500 can be realized by a general information processing device such as a PC or a server computer.

[0058] <Various data structures> Next, we will explain the data configurations of various data used in the data management device 1 using Figures 5 to 12C. Note that the field configurations of the volume group table 31, service level management table 32, main site disaster response pattern table 33, copy configuration table 34, copy status table 35, business data usage status table 36, public cloud cost table 37, and disaster response cost table 38 (disaster response cost tables 38A to 38C) shown in Figures 5 to 12C and explained below are examples and can be changed as appropriate.

[0059] Fig. 5 is a diagram showing an example of the data configuration of the volume group table 31. The volume group table 31 shown in Fig. 5 stores records having a volume group name 501 and a volume ID 502 as fields.

[0060] The volume group name 501 is a field for storing the name of the volume group. The volume ID 502 is a field for storing the ID of the volume that belongs to the volume group of the volume group name 501.

[0061] Fig. 6 is a diagram showing an example of the data configuration of the service level management table 32. The service level management table 32 shown in Fig. 6 stores records having fields of a task name 601, importance 602, a recovery point objective RPO 603, a task recovery time objective RTO 604, and a system recovery time objective 605. The task name 601 is a field that stores the name of the task. The importance 602 is a field that stores the importance of the task of the task name 601.

[0062] The recovery point objective RPO 603 is a field for storing the recovery point objective (RPO) when a volume used in the business of the business name 601 (referred to as a "used volume") is damaged.

[0063] The business recovery time objective RTO 604 is a field for storing the recovery time objective (RTO) when a volume used in the business of the business name 601 is damaged.

[0064] The system recovery time target 605 is a field for storing the system recovery time target when a volume used in the business of the business name 601 is damaged.

[0065] Fig. 7 is a diagram showing an example of the data configuration of the primary site disaster response pattern table 33. The primary site disaster response pattern table 33 shown in Fig. 7 stores records having fields of a disaster pattern ID 701, a disaster status 702, and a recovery pattern 703.

[0066] The disaster pattern ID 701 is a field for storing the ID of a disaster pattern.

[0067] The Disaster Status 702 is a field that stores information about the disaster status of the Used Volume and the Local Backup Volume. The Disaster Status 702 includes fields for Used Volume 702a and Local Backup Volume 702b. The values ​​for Used Volume 702a and Local Backup Volume 702b are "0" if the volume is not damaged and is normal, and "X" if the volume is damaged and is abnormal.

[0068] The recovery pattern 703 is a field that stores information about the recovery pattern. The recovery pattern 703 includes fields for a recovery pattern ID 703a, a location of the copy volume used for recovery 703b, and a copy method 703c. The recovery pattern ID 703a is a field that stores the ID of the recovery pattern. The location of the copy volume used for recovery 703b is a field that stores the location of the copy volume used for recovery. The copy method 703c is a field that stores the copy method.

[0069] Fig. 8 is a diagram showing an example of the data configuration of the copy configuration table 34. The copy configuration table 34 shown in Fig. 8 stores records having fields of a business name 801, a copy pair name 802a, a copy name 802b, used volume information 803, copy volume information 804, a copy method 805, and a recovery pattern ID 806.

[0070] The business name 801 is a field for storing the name of the business. The copy pair name 802a is a field for storing the name of the volume copy pair in data recovery. Furthermore, the copy name 802b is a field for storing the name of the volume copy in data recovery.

[0071] Used volume information 803 is a field that stores information about used volumes. Used volume information 803 includes fields for used volume ID, used volume group ID 803a, storage ID 803b, and site name 803c. Used volume ID and used volume group ID 803a are fields that store the ID of a used volume or the ID of a used volume group. A used volume group is a volume group made up of multiple used volumes. Storage ID 803b is the ID of the storage in which the used volume is created. Site name 803c is the name of the site in which the used volume is created.

[0072] The copy volume information 804 is a field that stores information about the copy volume. The copy volume information 804 includes fields for a copy volume ID, a copy volume group ID 804a, a storage ID or vendor name 804b, and a site name 804c. The copy volume ID and copy volume group ID 804a are fields that store the ID of the copy volume or the ID of the copy volume group. A copy volume group is a volume group made up of multiple copy volumes. The storage ID 804b is the ID of the storage in which the copy volume is created. The site name 804c is the name of the site in which the copy volume is created.

[0073] The copy method 805 is a field that stores the method of copying data during recovery. The recovery pattern ID 806 is a field that stores the ID of the recovery pattern.

[0074] Fig. 9 is a diagram showing an example of the data configuration of the copy status table 35. The copy status table 35 shown in Fig. 9 stores records having fields of a business name 901, a copy pair name a 902, a copy name 902b, used volume information 903, copy volume information 904, a pair status 905, and a latest time 906.

[0075] The business name 901 is a field for storing the name of the business. The copy pair name 902a is a field for storing the name of the copy pair (a pair of a copy source volume and a copy destination volume) in volume data recovery. The copy name 902b is a field for storing the name of the copy in data recovery.

[0076] Used volume information 903 is a field for storing information about used volumes. Used volume information 903 includes fields for used volume ID, used volume group ID 903a, site name 903b, and status 903c. Used volume ID and used volume group ID 903a are fields for storing the ID of the used volume or the ID of the used volume group. Site name 903b is the name of the site where the used volume is created. Status 903c is a field for storing the status of the used volume. If the used volume is normal, the value of status 903c is "normal". If the used volume is abnormal for some reason, such as if it has been damaged in a disaster, the value of status 903c is "abnormal".

[0077] The copy volume information 904 is a field for storing information related to the copy volume, and includes fields for a copy volume ID, a copy volume group ID 904a, a site name 904b, and a status 904c.

[0078] The copied volume ID and copied volume group ID 904a are fields that store the ID of the copied volume or the ID of the copied volume group. The site name 904b is the name of the site where the copied volume is created. The status 904c is a field that stores the status of the copied volume. If the copied volume is normal, the value of the status 904c is "normal." If the copied volume is abnormal for some reason, such as if it has been damaged in a disaster, the value of the status 904c is "abnormal."

[0079] Pair status 905 is a field that stores the pair status between the used volume and the copied volume. The values ​​of pair status 905 include "synchronizing", which indicates that synchronization is being achieved in the copy process, and "failover", which indicates that there is an abnormality in the used volume and that the copied volume is being used.

[0080] The latest time 906 is a field for storing the time when the most recent copy was performed. The value of the status 903c of the used volume information 903, the value of the status 904c of the copied volume information 904, and the value of the pair status 905 are the values ​​at the latest time 906.

[0081] Fig. 10 is a diagram showing an example of the data configuration of the business data usage status table 36. The business data usage status table 36 shown in Fig. 10 stores records having fields of business name 1001, volume data amount used 1002, and amount of data written per unit time 1003.

[0082] The business name 1001 is a field for storing the name of the business. The used volume data amount 1002 is a field for storing the amount of data used by the business having the business name 1001 (the total amount of data stored in the used volume). The written data amount per unit time 1003 is a field for storing the written data amount per unit time in the business having the business name 1001.

[0083] Fig. 11 is a diagram showing an example of the data configuration of the public cloud cost table 37. The public cloud cost table 37 shown in Fig. 11 stores records having fields of a vendor name 1101, a service name 1102, a site operation fee 1103, and a data read cost 1104.

[0084] The vendor name 1101 is a field that stores the name of the cloud vendor. The service name 1102 is a field that stores the name of the cloud service.

[0085] The site operation fee 1103 is a field for storing the operation fee of the cloud site.

[0086] The data read cost 1104 is a field that stores the cost required to read data from a cloud site. The data read cost 1104 includes fields for a data retrieval request 1104a and an external data transfer 1104b. The data retrieval request 1104a is a field that stores the cost required for a data retrieval request.

[0087] External data transfer 1104b is a field that stores the cost of reading data and transferring it outside the cloud site. External data transfer 1104b includes fields for data volume range 1104b1 and data transfer fee 1104b2. Data transfer fee 1104b2 is a field that stores the data transfer fee per unit data volume.

[0088] 12A to 12C are diagrams showing examples of the data configurations of disaster response cost tables 38A to 38C. Disaster response cost table 38A shown in FIG. 12A is a disaster response cost table 38 created when the operation phase is "pre-operation." Disaster response cost table 38B shown in FIG. 12B is a disaster response cost table 38 created when the operation phase is "in operation during normal times." Disaster response cost table 38C shown in FIG. 12C is a disaster response cost table 38 created when the operation phase is "in operation during a disaster."

[0089] Disaster response cost tables 38A to 38C shown in Figures 12A to 12C store records with the following fields: business name 1201, disaster pattern ID 1202, disaster status 1203, recovery pattern 1204, DR site operation time 1205, recovery copy pattern ID 1206, and DR site usage fee 1207.

[0090] The business name 1201 is a field for storing the name of the business. The disaster pattern ID 1202 is a field for storing the ID of the disaster pattern. As described above with reference to FIG. 3, the recovery pattern ID indicates a volume copy pair, in response to the disaster pattern, between a disaster-affected volume and a copy volume that stores data to be copied to the disaster-affected volume.

[0091] The disaster status 1203 is a field that stores information about the disaster status of the used volume and local backup volume. The disaster status 1203 includes fields for the used volume 1203a and the local backup volume 1203b. The values ​​of the used volume 1203a and the local backup volume 1203b are "0" if the volume has not been damaged and is normal, and "X" if the volume has been damaged and is abnormal.

[0092] The recovery pattern 1204 is a field that stores information related to the recovery pattern. The recovery pattern 1204 includes fields for a recovery pattern ID 1204a and a copy name 1204b. The recovery pattern ID 1204a is a field that stores the ID of the recovery pattern. The copy name 1204b is a field that stores the name of the volume copy in data recovery.

[0093] The DR site operation time 1205 is a field for storing the time required to restore data using the cloud DR copy volume at the cloud site (restoration time).

[0094] The restoration copy pattern ID 1206 is a field for storing an ID that identifies a pair of a volume to be restored and a copy volume that stores data to be copied to the volume to be restored.

[0095] The DR site usage fee 1207 is a field that stores the usage fee for the cloud site (DR site in a cloud environment) for data recovery during the recovery time required for data recovery to copy data using a volume copy pair. Here, the usage fee for the cloud site for data recovery includes the following two usage fees: 1. Usage fees for the cloud DR copy volume 221 when used in place of the on-premises environment usage volume 121 in the event that the on-premises environment usage volume 121 is affected by a disaster, and usage fees for the alternative host device 210 that takes over the functions of the host device 110. 2. The usage fee for the cloud DR copy volume 221 incurred for reading data from the cloud DR copy volume 221 while copying data from the cloud DR copy volume 221 to the usage volume 121 in the on-premise environment. The value of the DR site usage fee 1207 may be a cloud usage fee calculation formula corresponding to the recovery copy pattern 1206. The value of the DR site usage fee 1207, which is the value of the usage fee calculated for each copy pair, may be managed as data separate from the disaster response cost tables 38A to 38C.

[0096] The primary site disaster response pattern table 33 is primary site disaster response pattern information that associates the disaster status of the volume at the usage site where the usage volume is created with whether or not a DR site in the cloud environment is being used for data recovery.

[0097] The public cloud cost table 37 is cloud cost information that stores information on the cost required to use the sites in the cloud environment and the volumes in the sites in the cloud environment in association with each other.

[0098] <Processing Procedure> Next, we will explain the processing procedure of the data management device 1. The data management device 1 displays a cost analysis screen on a monitor (output device 25). As will be explained below, the cost analysis screen is a screen that displays the analysis conditions and analysis results for analyzing the costs involved in recovering from a disaster to a business-related volume.

[0099] Fig. 13 is an explanatory diagram showing an example of a cost analysis screen 1300 displayed on the output device 25 (monitor) of the data management device 1. The cost analysis screen 1300 shown in Fig. 13 includes a business selection button 1310 and an analysis execution button 1620, which are used to input the name of a business.

[0100] When the task selection button 1310 is pressed, a list of task names is displayed, allowing the task to be analyzed (referred to as a "target task") to be selected.

[0101] When the analysis execution button 1320 is clicked, the DR operation phase determination unit 11 of the data management device 1 executes the DR operation phase determination process using the business name (target business name) input using the business selection button 1310 as an input.

[0102] <1. DR operation phase determination process, Figure 14> FIG. 14 is a flowchart showing an example of a DR operation phase determination process according to the embodiment. The DR operation phase determination unit 11 of the data management device 1 determines the target business as the business whose business name is input using the cost analysis screen 1300 (see FIG. 13), and calculates the operation phase of the volume used by the target business. Here, the business name is target business identification information that identifies the target business. The target business identification information may be any information that can identify the target business, and other than the business name, for example, a business ID may be used. When the business ID is used as the target business identification information, the business ID may be input using the cost analysis screen 1300, and the DR operation phase determination process may be performed using the business ID as an input.

[0103] The data management device 1 refers to the copy configuration table 34 and determines whether copy volumes have been created for all used volumes used in the target business (step S101). If it is determined that copy volumes have not been created for the used volumes used in the target business (step S101: No), the process proceeds to step S102 and executes pre-operation correspondence pattern calculation processing. On the other hand, if it is determined that copy volumes have been created for the used volumes used in the target business (step S101: Yes), the process proceeds to step S103.

[0104] The copy configuration table 34 stores, in association with each other, the business name, the used volume ID or used volume group ID of the used volume used in the business with the business name (the used volume ID or used volume group ID 803a in the used volume information 803), and the copy volume ID or copy volume group ID of the copy volume of the used volume (the copy volume ID or copy volume group ID 804a in the copy volume information 804). If the copy configuration table 34 does not contain a record storing the target business name, there is no copy volume for the used volume, and therefore no cloud DR copy volume at the DR site in the cloud environment has been created for the used volume. Therefore, if the copy configuration table 34 does not contain a record storing the target business name, the operation phase for the used volume of the target business is "pre-operation."

[0105] Therefore, the data management device 1 determines whether or not a record storing the target business name exists in the copy configuration table 34. If a record storing the target business name exists in the copy configuration table 34, the data management device 1 determines that a copy volume has been created for the usage volume used by the target business (step S101: Yes). On the other hand, if a record storing the target business name does not exist in the copy configuration table 34, the data management device 1 determines that a copy volume has not been created for the usage volume used by the target business (step S101: No).

[0106] Next, the data management device 1 executes the pre-operation correspondence pattern calculation process (see FIG. 18) using the target business name and the value of the operation phase "pre-operation" as input (step S102).

[0107] Next, the data management device 1 refers to the copy configuration table 34 and determines whether cloud DR copy volumes have been created for all used volumes (step S103). If it is determined that cloud DR copy volumes have not been created for all used volumes (step S103: No), the data management device 1 proceeds to step S102 and executes pre-operation correspondence pattern calculation processing. On the other hand, if it is determined that cloud DR copy volumes have been created for all used volumes (step S103: Yes), the data management device 1 proceeds to step S104.

[0108] Cloud DR copy volumes have been created for all used volumes when cloud DR copy volumes at the DR site in the cloud environment correspond to all used volumes in the record storing the target business name in the copy configuration table 34. Therefore, if the site name of the cloud site is stored in the site name 804c of the copy volume information 804 for all used volume IDs or used volume group IDs (used volume IDs, used volume group IDs 803a of the used volume information 803) in the record storing the target business name in the copy configuration table 34, the data management device 1 determines that cloud DR copy volumes have been created for all used volumes (step S103: Yes).

[0109] On the other hand, if the site name of the cloud site is not stored in the site name 804c of the copy volume information 804 for at least one used volume ID or used volume group ID (used volume ID, used volume group ID 803a of the used volume information 803) in the record storing the target business name in the copy configuration table 34, the data management device 1 determines that cloud DR copy volumes have not been created for all used volumes (step S103: No). In this case, since a cloud DR copy volume has not been created for at least one used volume, the data management device 1 executes the pre-operation correspondence pattern calculation process in step S102.

[0110] Next, the data management device 1 refers to the copy status table 35 to determine whether all of the used volumes and copy volumes of the used volumes are normal (step S104). If it is determined that all of the used volumes and copy volumes of the used volumes are normal (step S104: Yes), the process proceeds to step S105 and executes a process for calculating a response pattern for normal operation. On the other hand, if it is determined that at least one of the used volumes and copy volumes of the used volumes is not normal (step S104: No), the process proceeds to step S106 and executes a process for calculating a response pattern for disaster during operation.

[0111] Here, information on whether the status of the used volume is normal or not is stored in the status 903c of the used volume information 903 of the copy status table 35. Also, information on whether the status of the copied volume for the used volume is normal or not is stored in the status 904c of the copied volume information 904 of the copy status table 35.

[0112] Therefore, if all values ​​of the status 903c of the used volume information 903 are "normal" and all values ​​of the status 904c of the copied volume information 904 are "normal" in the record in which the target business name is saved in the copy status table 35, the data management device 1 determines that the used volumes and the volumes of copies of the used volumes are all normal (step S104: Yes).On the other hand, if at least one value of the status 903c of the used volume information 903 and the status 904c of the copied volume information 904 is "abnormal" in the record in which the target business name is saved in the copy status table 35, the data management device 1 determines that at least one of the used volumes and the volumes of copies of the used volumes is not normal (step S104: No).

[0113] Next, the data management device 1 executes the in-operation normal time response pattern calculation process (see FIG. 16) using the target business name and the operation phase value "in-operation normal time" as input, and ends the process (step S105).

[0114] Next, the data management device 1 executes the process of calculating a response pattern for disaster during operation (see FIG. 17) using the target business name and the value of the operation phase "disaster during operation" as input, and ends the process (step S106).

[0115] <2. Pre-operation response pattern calculation process, Figure 15> 15 is a flowchart showing an example of a pre-operation response pattern calculation process. The pre-operation response pattern calculation unit 12 of the data management device 1 executes the pre-operation response pattern calculation process using the target business name and the operation phase value “pre-operation” as input.

[0116] The data management device 1 uses the primary site disaster response pattern table 33 to generate records of all hypothetical recovery patterns that use the local backup volume and the cloud DR copy volume of the DR site in the cloud environment, and saves these records in the disaster response cost table 38A (see FIG. 12A) (step S201). For each record in the primary site disaster response pattern table 33, the data management device 1 generates and saves a record that associates the target business name, the copy name "Null," and the value of the DR site operation time.

[0117] Here, if the value of the recovery pattern ID is "R1," the value of the cloud DR site operation time is set to "0." In this case, the copy volume from which data is read during data recovery is created at the local site, and the cloud DR copy volume at the cloud site is not used for data recovery. On the other hand, if the value of the recovery pattern ID is "R2a" or "R2d," the value of the system recovery time target 605 for the record in the service level management table 32 whose business name 601 is the target business name is set to the DR site operation time. Here, it is assumed that data recovery will take the time equivalent to the system recovery time target 605.

[0118] Next, the data management device 1 assigns recovery copy pattern IDs to all records stored in step S201 in the order in which the records were created (step S202). Here, the values ​​of the recovery copy pattern IDs are C1, C2, ..., Cn. The value of the recovery copy pattern ID is a combination of "C" and a number (the order in which the records were created).

[0119] Next, the data management device 1 executes the disaster response cost calculation process (see FIG. 18) using the target business name, the operation phase value "pre-operation", and the disaster response cost table 38A as input, and ends the process (step S203).

[0120] <3. Calculation process of response patterns during normal operation, Figure 16> 16 is a flowchart showing an example of a process for calculating a response pattern during normal operation. The process for calculating a response pattern during normal operation in the data management device 1 executes the process for calculating a response pattern during normal operation using the target task name and the value of the operation phase “normal operation.”

[0121] The data management device 1 acquires and saves all pairs of copy name 802b in copy pair name 802a and recovery pattern ID 806 from the record storing the target business name in copy configuration table 34 (step S301). Here, if the DR recovery support device recovery pattern ID 806 is R2d (differential copy), it is expected that differential management will not function depending on the disaster situation and differential copying will not be possible. Therefore, the data management device 1 adds a pair of copy name 802, which is a full copy, and recovery pattern ID 806 value "R2a" to the pair of copy name 802 and recovery pattern ID 806 value "R2d", and creates and saves these two pairs.

[0122] Next, the data management device 1 obtains the value of the system target recovery time 605 of the record in the service level management table 32 where the business name 601 is the target business name, and saves it as the value of the DR site operation time when the recovery pattern ID value is "R2a" or "R2d" (step S302).

[0123] Next, the data management device 1 starts a loop process in which it generates recovery pattern records for all pairs of copy names and recovery pattern ID values ​​saved in step S301 and saves them in the disaster response cost table 38B (step S303). The process shown from step S303, which starts the loop, to step S306, which ends the loop, is repeated for each pair of copy names and recovery pattern ID values ​​saved in step S301. In step S303, the data management device 1 selects one pair of copy names and recovery pattern ID values ​​from among the pairs of unprocessed copy names and recovery pattern ID values ​​saved in step S301.

[0124] Next, the data management device 1 acquires and saves a pair of the disaster pattern ID 701 associated with the value of the recovery pattern ID selected in step S303 and the disaster status 702 (including the value of the used volume 702a and the value of the local backup volume 702b) in the primary site disaster response pattern table 33 (step S304).

[0125] Next, the data management device 1 generates a record that associates the target business name, the disaster pattern ID saved in step S304, the disaster situation saved in step S304, the value of the recovery pattern ID and copy name selected in step S303, and the value of the operating time of the DR site, and saves it in the disaster response cost table 38B (see Figure 12B) (step S305).

[0126] Here, if the value of the recovery pattern ID is "R1," the value of the DR site operation time is set to "0." In this case, the copy volume from which data is read during data recovery is created at the local site, and the cloud DR copy volume at the cloud site is not used for data recovery. On the other hand, if the value of the recovery pattern ID is "R2a" or "R2d," the value of the "system target recovery time" saved in step S302 is set to the value of the DR site operation time.

[0127] In addition, when the data management device 1 saves the generated record in the disaster response cost table 38B, if a record with the same set of disaster pattern ID and disaster status is already saved in the disaster response cost table 38B, the data management device 1 adds the information of the record to be saved in step S305 to the record that already saves the set of disaster pattern ID and disaster status.

[0128] Next, the data management device 1 determines whether processing has been completed for all pairs of copy names and recovery pattern ID values ​​saved in step S301 (step S306). If the data management device 1 determines in step S306 that processing has not been completed for all pairs of copy names and recovery pattern ID values ​​saved in step S301, the data management device 1 returns to step S303 and continues processing. On the other hand, if the data management device 1 determines that processing has been completed for all pairs of copy names and recovery pattern ID values ​​saved in step S301, the data management device 1 executes the processing of step S307.

[0129] Next, in step S307, the data management device 1 assigns a recovery copy pattern ID to all records stored in the disaster response cost table 38B, starting from the top of the record (step S307). Here, the values ​​of the recovery copy pattern IDs are C1, C2, ..., Cn, and are values ​​that combine "C" and a number (the order at the top of the record).

[0130] Next, the data management device 1 executes the disaster response cost calculation process (see FIG. 18) using the target business name, the operation phase value "normal operation", and the disaster response cost table 38B as input, and terminates the process (step S308).

[0131] <4. Calculation process of response patterns in case of disaster during operation, Figure 17> 17 is a flowchart showing an example of a process for calculating a response pattern when a disaster occurs during operation. The response pattern calculation unit 14 of the data management device 1 executes the process for calculating a response pattern when a disaster occurs during operation, using the target business name and the operation phase value “when a disaster occurs during operation” as input.

[0132] The data management device 1 saves as an abnormal record any record in the copy status table 35 that is associated with the target business name and in which the value of the status 903c of the volume usage information 903 is "abnormal" or the value of the pair status 905 is "abnormal" or "failover" (step S401). Furthermore, if the operation monitoring program 18a detects an abnormality in the copy status table 35, such as an abnormal end of copying, for a record associated with the target business name, the copy status table 35 determines that the record is abnormal even if the above conditions are not met, and saves the record as an abnormal record.

[0133] Next, the data management device 1 obtains the value of the system target recovery time 605 of the record in the service level management table 32 where the business name 601 is the target business name, and saves it as the value of the DR site operation time when the recovery pattern ID value is "R2a" or "R2d" (step S402).

[0134] Next, the data management device 1 starts a loop process of generating recovery pattern records for all abnormal records saved in step S401 and saving them in the disaster response cost table 38C (step S403). The process shown from step S403, which starts the loop, to step S408, which ends the loop, is repeated for each abnormal record saved in step S401. In step S403, the data management device 1 selects one abnormal record from the unprocessed abnormal records among all the abnormal records saved in step S401.

[0135] Next, the data management device 1 obtains and saves the used volume as "o" or "x" in the damage status 1203 of the disaster response cost table 38C for the abnormal record selected in step S403 (step S404). If the status value of the used volume information of the abnormal record is "o", the data management device 1 saves "o", which indicates normality, as the value for the used volume of the abnormal record. For example, an abnormal record resulting from an abnormal termination of copying due to a network failure is an example of this "o" because the volume itself is normal. On the other hand, if the status value of the used volume information of the abnormal record is "x", the data management device 1 saves "x", which indicates abnormality, as the value for the used volume of the abnormal record.

[0136] Next, the data management device 1 obtains and stores the local backup volume value of "◯" or "X" in the damage status 1203 of the disaster response cost table 38C for the abnormal record selected in step S403 (step S405). If all of the following conditions 1 to 4 are met, the data management device 1 stores "◯" as the value for the local backup volume. On the other hand, if at least one of the following conditions 1 to 4 is not met, the data management device 1 stores "X" as the value for the local backup volume. Condition 1: The site name in the used volume information of the abnormal record is the same as the site name in the copied volume information. In other words, the used volume and the copied volume are created at the same site in the on-premise environment. Condition 2: The status value of the copy volume information of the abnormal record is "0". Condition 3: The following formula is satisfied. If this formula is satisfied, the volume in use has sufficiently recent data (within the recovery point objective RPO) copied to the local backup volume. Current time - The latest copy time of the relevant copy pair (corresponding to the abnormal record) in the copy status table 35 < the objective recovery point RPO of the record storing the target business name in the service level management table 32 Condition 4: The pair status value of the abnormal record is not "failover." This is because if the pair status value is "failover," alternative operation is already being performed at the DR site, and recovery using a local backup is not expected to be performed.

[0137] Next, the data management device 1 calculates and stores a disaster status value in the main site disaster response pattern table 33, consisting of the value for the volume used for the abnormal record obtained in step S404 and the value for the local backup volume for the abnormal record obtained in step S405, and obtains and stores a pair of a disaster pattern ID and a recovery pattern ID that correspond to the stored disaster status value (step S406).

[0138] Then, the data management device 1 acquires and stores in the main site disaster response pattern table 33 a pair of a disaster pattern ID and a recovery pattern ID that correspond to the disaster status value calculated as described above (a pair of the value of the volume in use and the value of the local backup volume).

[0139] Next, the data management device 1 generates a record that associates the target business name, the disaster situation, disaster pattern ID, recovery pattern ID saved in step S406, the copy name of the abnormal record, and the value of the operating time of the DR site, and saves it in the disaster response cost table 38C (see Figure 12C) (step S407).

[0140] Here, if the value of the recovery pattern ID is "R1," the value of the DR site operation time is set to "0." In this case, the copy volume from which data is read during data recovery is created at the local site, and the cloud DR copy volume at the cloud site is not used for data recovery. On the other hand, if the value of the recovery pattern ID is "R2a" or "R2d," the target recovery time value saved in step S402 is set to the value of the DR site operation time.

[0141] In addition, when the data management device 1 saves the generated record in the disaster response cost table 38C, if a record with the same set of disaster pattern ID and disaster status is already saved in the disaster response cost table 38C, the data management device 1 adds the information of the record to be saved in step S407 to the record that already saves the set of disaster pattern ID and disaster status.

[0142] Next, the data management device 1 determines whether processing has been completed for all abnormal records saved in step S401 (step S408). If the data management device 1 determines in step S408 that processing has not been completed for all abnormal records saved in step S401, the data management device 1 returns to step S403 and continues processing. On the other hand, if the data management device 1 determines that processing has been completed for all abnormal records saved in step S401, the data management device 1 executes the processing of step S409.

[0143] Next, in step S407, the data management device 1 assigns a recovery copy pattern ID to all records stored in the disaster response cost table 38C, starting from the top of the record (step S409). Here, the values ​​of the recovery copy pattern IDs are C1, C2, ..., Cn, and are values ​​that combine "C" and a number (the order at the top of the record).

[0144] Next, the data management device 1 executes the disaster response cost calculation process (see FIG. 17) using the target business name, the operation phase value "disaster during operation," and the disaster response cost table 38C as input, and terminates the process (step S410).

[0145] <5. Disaster response cost calculation process, Figure 18> 18 is a flowchart showing an example of a disaster response cost calculation process. The disaster response cost calculation unit 15 of the data management device 1 executes the disaster response cost calculation process using as input the target business name, the operation phase value ("Before operation," "Normal operation," "Disaster during operation"), and the disaster response cost table 38 (one of the disaster response cost tables 38A to 38C).

[0146] The data management device 1 starts a loop process for calculating the usage fee of the DR site in the cloud environment for the recovery copy pattern ID stored in the input disaster response cost table 38 (one of the disaster response cost tables 38A to 38C) (step S501). The process shown from step S501, which starts the loop for calculating the usage fee of the DR site in the cloud environment for the recovery copy pattern ID stored in the input disaster response cost table 38 (one of the disaster response cost tables 38A to 38C), to step S503, which ends the loop, is repeated for each record that stores the recovery copy pattern ID stored in the disaster response cost table 38 (one of the disaster response cost tables 38A to 38C). In step S501, the data management device 1 selects one recovery copy pattern ID from the recovery copy pattern IDs stored in the disaster response cost table 38 (one of the disaster response cost tables 38A to 38C).

[0147] Next, the data management device 1 calculates and saves the usage fee for the DR site in the cloud environment for the record that stores the recovery copy pattern ID selected in step S501 (step S502). The data management device 1 calculates the usage fee for the DR site in the cloud environment according to the recovery pattern ID of the record that stores the recovery copy pattern ID selected in step S501 using one of the following calculation methods 1 to 3, and adds the calculated usage fee for the DR site in the cloud environment to the record that stores the recovery copy pattern ID selected in step S501 in the disaster response cost table 38 (one of the disaster response cost tables 38A to 38C).

[0148] Calculation method 1: When the recovery pattern ID is "R1" (when a copy volume is created at the local site and a full copy is performed), the data management device 1 calculates the usage fee for the DR site in the cloud environment as "0". This is because the copy volume is a volume created at the local site, not at the site in the cloud environment. Since the site in the cloud environment is not used for recovery, the usage fee for the DR site in the cloud environment is "0".

[0149] Calculation method 2: When the recovery pattern ID is "R2a" (when the cloud DR copy volume is used as the copy volume at the DR site in the cloud environment and all data is copied), the data management device 1 calculates the usage fee for the DR site in the cloud environment as follows. Cloud environment DR site usage fee = Cloud environment DR site operation fee during recovery time + Data retrieval cost for retrieving data from the cloud DR copy volume

[0150] The usage fee for the DR site in the cloud environment is the usage fee for the DR site in the cloud environment from the occurrence of a failure in the disaster pattern calculated by the response pattern calculation unit (pre-operation response pattern calculation unit 12, normal operation response pattern calculation unit 13, operation disaster response pattern calculation unit 14) using cloud cost information until system recovery is completed at the usage site where the usage volume is created.

[0151] First, we will explain the "operating fee for a DR site in a cloud environment during recovery time." Cloud environment DR site operation fee during recovery time = DR site operation time x IO usage fee Here, the DR site operation time is the value of the DR site operation time of the record that stores the recovery copy pattern ID selected in step S501. The IO usage cost is acquired as follows. The data management device 1 acquires a record that stores the target business name and the recovery copy pattern ID selected in step S501 in the copy configuration table 34. Then, the data management device 1 acquires the copy pair name and the storage ID or vendor name 804b (vendor name) of the copy volume information 804 from the acquired record. Then, the data management device 1 acquires a record (hereinafter referred to as the "cost record") that stores the acquired storage ID or vendor name 804b (vendor name) in the public cloud cost table 37. Then, the data management device 1 acquires the value of the site operation fee (IO usage cost) 1103 of the cost record as the value of the IO usage cost.

[0152] Next, the "data read cost required to read data from the cloud DR copy volume" will be explained. Data read cost for reading data from the cloud DR copy volume = (volume data volume in use + data volume written during recovery time) x data transfer fee per unit of data volume Here, the volume data amount in use is the value of "volume data amount in use" of the record that stores the target business name in the business data usage status table 36. The data management device 1 refers to the business data usage status table 36 to obtain the value of "volume data amount in use".

[0153] In addition, the "amount of data written during recovery time" is calculated using the following formula. Amount of data written during recovery time = Operation time of DR site x Amount of data written per unit time Here, the operation time of the DR site (the value of the record storing the recovery copy pattern ID selected in step S501) is considered to be the recovery time. The amount of data written per unit time is the value of "amount of data written per unit time" of the record storing the target business name in the business data usage status table 36. The data management device 1 references the business data usage status table 36 to obtain the value of "amount of data written per unit time". Furthermore, the "data transfer fee per unit data amount" is the value of the data transfer fee 1104b2 corresponding to the range 1104b1 that includes the value of (volume data amount in use + data amount written during recovery time) in the cost record of the public cloud cost table 37. The data management device 1 references the cost record of the public cloud cost table 37 to acquire the value of the data transfer fee per unit data amount. Calculation method 3: When the recovery pattern ID is "R2d" (when a cloud DR copy volume is used as a copy volume at a DR site in a cloud environment and a differential copy is performed), the data management device 1 calculates the usage fee for the DR site in a cloud environment as follows. Cloud environment DR site usage fee = Cloud environment DR site operation fee during recovery time + Data retrieval cost for retrieving data from the cloud DR copy volume The "operational fee for the DR site in a cloud environment during the recovery time" is calculated in the same way as the "operational fee for the DR site in a cloud environment during the recovery time" in calculation method 2 above, so the explanation will be omitted.

[0154] Next, the "data read cost required to read data from the cloud DR copy volume" will be explained. Data read cost to read data from the cloud DR copy volume = (amount of data written during recovery time) x data transfer fee per unit of data Here, the "amount of data written during recovery time" and "data transfer fee per unit amount of data" are calculated in the same manner as in the calculation method 2 above, and therefore explanations thereof will be omitted.

[0155] Next, the data management device 1 determines whether processing has been completed for all recovery copy pattern IDs stored in the disaster response cost table 38 (one of the disaster response cost tables 38A to 38C) (step S503). If the data management device 1 determines that processing has not been completed for all recovery copy pattern IDs, the data management device 1 returns to step S501 and continues processing. On the other hand, if the data management device 1 determines that processing has been completed for all recovery copy pattern IDs, the data management device 1 executes the processing of step S504.

[0156] Next, the data management device 1 outputs the disaster response cost table 38 (one of the disaster response cost tables 38A to 38C) and ends the process (step S504). Here, the data management device 1 outputs the information of the cost analysis screen, to which the contents of the disaster response cost table 38 (one of the disaster response cost tables 38A to 38C) have been added, to the output device 25 (monitor), and presents the contents of the disaster response cost table 38 (one of the disaster response cost tables 38A to 38C) to the user. Fig. 19 is an explanatory diagram showing an example of a cost analysis screen 1900 displayed on the output device 25 (monitor) of the data management device 1. A cost list 1930 (part of the disaster response cost table 38) is displayed on the cost analysis screen 1900 shown in Fig. 19.

[0157] <Effects of the invention> The DR cost calculation support method of the data management device 1 calculates the usage fee for a DR site in a cloud environment from the occurrence of a failure in a disaster pattern until system recovery is completed at the usage site where the usage volume is created. The usage fee for a DR site in a cloud environment is the cost of the volumes at the DR site in a virtual environment in the event of a disaster. In many cases, when operating a DR site, users use information about the cost of the volumes at the DR site in a virtual environment to determine whether to use the volumes at the DR site in a virtual environment. Then, by referring to the cost of the volumes at the DR site in a virtual environment calculated by the data management device 1 in the event of a disaster, users can more easily make a more appropriate decision about whether to use the volumes at the DR site in a virtual environment. Therefore, the data management device 1 and the DR cost calculation support method of the data management device 1 support the operation of a DR site by calculating the usage fee for the DR site in a cloud environment.

[0158] In addition, by calculating the usage fee for the DR site in the cloud environment in this way, recovery methods, recovery times, and recovery costs can be estimated and presented in the event of unexpected data loss, making it easier to introduce an appropriate disaster recovery system, and ultimately making it easier to use the disaster recovery system to perform appropriate and prompt recovery in the event of unexpected data loss.

[0159] Furthermore, the DR cost calculation support method of the data management device 1 calculates the sum of the operating fee for the DR site in the cloud environment during the recovery time and the data reading cost required to read data from the cloud DR copy volume as the usage fee for the DR site in the cloud environment from the occurrence of the failure to the completion of system recovery (step S502 in the flowchart of the disaster response cost calculation process in FIG. 18). This allows the usage fee for the DR site in the cloud environment to be calculated appropriately.

[0160] Furthermore, the DR cost calculation support method of the data management device 1 uses the primary site disaster response pattern table 33 (primary site disaster response pattern information) to calculate a pair of volume copies, in response to a disaster pattern, between a volume to be affected by the disaster and a copy volume that stores data to be copied to the volume to be affected by the disaster (step S201 in the flowchart of the pre-operation response pattern calculation process in FIG. 15, step S304 in the flowchart of the normal operation response pattern calculation process in FIG. 16, and step S406 in the flowchart of the disaster response pattern calculation process in operation in FIG. 17). This makes it easier to calculate the usage fee for the DR site in a cloud environment during the recovery time.

[0161] Furthermore, when the operation phase is pre-operation, the DR cost calculation support method of the data management device 1 calculates a disaster pattern in which a disaster-affected volume will occur when a cloud DR copy volume at a DR site in a cloud environment is temporarily used, and calculates a volume copy pair of the disaster-affected volume and a copy volume storing copy data of the disaster-affected volume in response to the calculated disaster pattern (see the flowchart of the pre-operation response pattern calculation process in FIG. 15). This makes it easy for users to know the cost required for recovery when a cloud DR copy volume is used when the operation phase is "pre-operation."

[0162] Furthermore, when the DR cost calculation support method of the data management device 1 determines that there is a disaster-affected volume among the used volume and the copy volume of the used volume, it calculates a pair of volume copies of the affected volume and the copy volume storing the copy data of the affected volume in data recovery for the disaster-affected volume among the used volume and the copy volume of the used volume (see the flowchart of the disaster response pattern calculation process during operation in FIG. 17), and calculates the usage fee for the DR site in the cloud environment (see step S410 of the flowchart of the disaster response pattern calculation process during operation in FIG. 17 and the flowchart of the disaster response cost calculation process in FIG. 18). This allows the user to select a pair of used volume and copy volume to which data is copied more quickly in the event of a disaster, and perform recovery.

[0163] Furthermore, the DR cost calculation support method of the data management device 1 outputs the usage fee for the DR site in the cloud environment, thereby enabling the user to easily know the usage fee for the DR site in the cloud environment.

[0164] Furthermore, the DR cost calculation support method of the data management device 1 uses a used volume group name (used volume group identification information) that identifies a used volume group (see the volume group table 31 in FIG. 5 and the copy configuration table 34 in FIG. 8). This makes it possible to easily set a used volume.

[0165] <Variation 1> In the above-described embodiment, the usage volume 121 is created in the on-premise system 100. In the first modification, the usage volume 121 is created in the on-premise system 100 or in a site in a cloud environment. In the first modification, not only the usage volume 121 but also an alternative host device 210 and a local backup volume 122 may be created in the site in the cloud environment.

[0166] As a result, the DR cost calculation support method of the data management device 1 can create a usage volume not only at an on-premise environment site (embodiment) but also at a cloud environment site (variation 1). This allows the user to easily know the usage fee for the DR site in the cloud environment in more cases (including when the usage volume is stored at a cloud environment site).

[0167] The present invention is not limited to the above-described embodiments, but includes various modifications. For example, the above-described embodiments are provided to explain the present invention in detail, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, some of the configurations of each embodiment can be added to, deleted from, or replaced with other configurations.

[0168] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that implements the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media for providing such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, solid-state drives (SSDs), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, and ROMs.

[0169] Furthermore, the program code that realizes the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, Python, and Java (registered trademark).

[0170] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read and execute the program code stored in the storage means or storage medium.

[0171] In the above-described embodiment, the control lines and information lines are shown as those considered necessary for the explanation, and not all control lines and information lines are necessarily shown in the product. All components may be interconnected. [Explanation of symbols]

[0172] 1. Recovery support device 11: Operation phase determination unit 12: Pre-operational response pattern calculation section 13: Normal operation response pattern calculation section 14: Operational disaster response pattern calculation section 15. Disaster Response Cost Calculation Department 21;Processor 22; Main memory 23; Secondary storage device 24. Input device 25; Output device 26;Network I / F 27; Bus 31;Volume Group Table 32;Service Level Management Table 33: Main site disaster response pattern table 34: Copy configuration management table 35: Copy status management table 36;Business data usage table 37; Public Cloud Cost Table 38;Recovery cost management information 5. On-premise environment storage management device 6. Cloud site management device 100;On-premise systems 110; Host device 120;On-premise storage systems 121; Volume used 122;Local backup volume 200;Cloud Site 210; Alternate host device 221; Copy Volume 500;User terminal NW; Network

Claims

1. A DR cost calculation support method in a data management device that generates information about a volume affected by a disaster, comprising: the data management device includes a storage device and a processor; The storage device includes: copy configuration information that associates and stores business identification information that identifies a business, information on volumes used in the business, and information on copy volumes that configure pairs of the volumes used and backup or DR; storing cloud cost information that associates and stores information on the cost required to use a site in a cloud environment and a volume in the site in the cloud environment; The processor: Once the target business specific information that identifies the target business is acquired, a DR operation phase determination process that refers to the copy configuration information and calculates an operation phase of the cloud DR copy volume of the cloud site for the target business use volume based on information on the copy volume for the target business use volume used in the target business; calculating a disaster pattern that may occur in the volume that is the target of disaster according to the operation phase calculated by the DR operation phase determination unit; a correspondence pattern calculation process for calculating a set of volume copies between the volume to be affected by the disaster and a copy volume storing data to be copied for recovery to the volume to be affected by the disaster in response to the calculated disaster pattern; A DR cost calculation support method that uses the cloud cost information to execute a disaster response cost calculation process that calculates the usage fee for the DR site of the cloud environment from the occurrence of a failure in the disaster pattern calculated by the response pattern calculation unit until system recovery of the usage site where the usage volume is created is completed.

2. The DR cost calculation support method according to claim 1, The disaster response cost calculation process includes: a process of calculating the sum of an operating fee for the DR site in the cloud environment during the recovery time and a data reading cost required to read data from the cloud DR copy volume as a usage fee for the DR site in the cloud environment during the recovery time; DR cost calculation support method.

3. The DR cost calculation support method according to claim 1, The storage unit further storing primary site disaster response pattern information that associates a disaster situation of a volume at a usage site where the usage volume is created with whether or not a DR site in the cloud environment is used for the data recovery; The response pattern calculation process uses the main site disaster response pattern information, a process for calculating a set of volume copies between the volume to be affected by the disaster and a copy volume storing data to be copied for recovery to the volume to be affected by the disaster in response to the disaster pattern; DR cost calculation support method.

4. The DR cost calculation support method according to claim 1, When the operation phase calculated by the DR operation phase determination unit is before operation, The corresponding pattern calculation process includes: Calculating a disaster pattern in a state where the cloud DR copy volume of the DR site in the cloud environment is temporarily used; DR cost calculation support method.

5. The DR cost calculation support method according to claim 1, The DR operation phase determination process includes: a process of determining whether or not there is a volume to be affected by a disaster among the used volume and the copy volume of the used volume, If it is determined that the volume to be affected by the disaster exists among the used volume and the copy volume of the used volume, The corresponding pattern calculation process includes: In data recovery for the affected volume among the used volume and the copy volume of the used volume, a volume copy pair is calculated between the affected volume and a copy volume storing data to be restored and copied to the affected volume. DR cost calculation support method.

6. The DR cost calculation support method according to claim 1, The disaster response cost calculation process includes a process of outputting a usage fee for the DR site in the cloud environment from the occurrence of a failure in the set of volume copies calculated by the response pattern calculation unit until system recovery of the usage site where the usage volume is created is completed. DR cost calculation support method.

7. The DR cost calculation support method according to claim 1, the information on the volumes used in the business in the copy configuration information includes used volume group specification information that specifies a used volume group consisting of a plurality of volumes used in the business; DR cost calculation support method.

8. The DR cost calculation support method according to claim 1, The DR cost calculation support method, wherein the used volume is at least one of a volume created in a site of an on-premise environment and a volume created in a site of a cloud environment.

9. A data management device that generates information about a disaster occurring to a volume, The system includes a storage unit, a DR operation phase determination unit, a response pattern calculation unit, and a disaster response cost calculation unit, The storage unit copy configuration information that associates and stores business identification information that identifies a business, information on volumes used in the business, and information on copy volumes that configure pairs of the volumes used and backup or DR; storing cloud cost information that associates and stores information on the cost required to use a site in a cloud environment and a volume in the site in the cloud environment; The DR operation phase determination unit Once the target business specific information that identifies the target business is acquired, executes a DR operation phase determination process that calculates an operation phase of the cloud DR copy volume of the cloud site for the target business use volume based on information on the copy volume for the target business use volume used by the target business, by referring to the copy configuration information; The corresponding pattern calculation unit calculating a disaster pattern that may occur in the volume that is the target of disaster according to the operation phase calculated by the DR operation phase determination unit; Execute a correspondence pattern calculation process for calculating a pair of volume copies between the volume to be affected by the disaster and a copy volume storing data to be copied for recovery to the volume to be affected by the disaster in response to the calculated disaster pattern; The disaster response cost calculation unit using the cloud cost information, execute a disaster response cost calculation process to calculate a usage fee for the DR site of the cloud environment from the occurrence of a failure in the disaster pattern calculated by the response pattern calculation unit until the completion of system recovery of the usage site where the usage volume is created; Data management device.

Images