Management method, management program, and management device

Abstract

To provide a restoration pattern that is suited for data to be restored.SOLUTION: A management device for managing restoration of data backed up in a backup destination to a backup source of the data, stores a plurality of restoration rules that defines a plurality of restoration concerning patterns in a restoration configuration indicating data copy sources and data copy destinations, and backup configuration information about a data backup source and a data backup destination. The management device designates data to be restored, selects a specified one of the plurality of restoration rules, determines, as a copy destination, the backup source of the designated data to be restored while checking the backup configuration information, and generates a restoration pattern of the data to be restored in accordance with the selected specified restoration rule in the restoration configuration of the data to be restored in which the backup destination of the data to be restored is set as the copy source.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a management method for managing data, a management program, and a management device.

Background Art

[0002] When customers introduce backup or DR (Disaster Recovery), the number of cases where copy data is placed in the cloud to reduce costs is increasing. When configuring a backup between on-premises and the cloud, since public cloud usage fees are incurred during data recovery, it is difficult to determine an optimal recovery method considering costs.

[0003] Further, Patent Document 1 below discloses a computer system that facilitates a restore operation. In this computer system, a management server collects necessary information from at least a business server, a storage device in which a main volume is formed, and a storage device in which a secondary volume is formed. When a restore request is given from the outside, the management server calculates the restore time required when executing the restore process requested by each of a plurality of predetermined restore methods based on the information collected by the information collection unit, determines the restore method with the shortest restore time as the restore method at the time of the restore process for the restore request, notifies the determined restore method to the business server, and controls the storage device in which the main volume is provided and the storage device in which the secondary volume is provided so that the business server executes the restore process according to the restore method notified from the management server.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The existing recovery methods described above do not address the diversification and complexity of recovery methods that arise from using public cloud storage as a backup destination. Furthermore, the existing recovery methods described above do not take into account the estimation of recovery costs incurred during the recovery process.

[0006] The present invention aims to provide a recovery pattern suitable for the data to be recovered. [Means for solving the problem]

[0007] A management method that constitutes one aspect of the invention disclosed in this application is a management method performed by a management device that manages the restoration of data backed up to a backup destination to a backup source, comprising a processor that executes a program and a storage device that stores the program, wherein the storage device stores a plurality of recovery rules that define a plurality of patterns relating to the restoration in a recovery configuration indicating the source and destination of the data, and backup configuration information relating to the backup source and destination of the data. The recovery rule includes a recovery cost calculation formula that calculates the recovery cost of retrieving the data from the source and transferring it to the destination, based on the amount of data and the number of requests to retrieve the data from the source. The processor performs a selection process to select a specific recovery rule from among the plurality of recovery rules, and, referring to the backup configuration information, generates a recovery pattern for the data to be recovered according to the specific recovery rule selected by the selection process, in a recovery configuration for the data to be recovered in which the backup source of the data to be recovered specified by the designation process is the copy destination, and the backup destination of the data to be recovered is the copy source. Then, using the recovery cost calculation formula included in the specific recovery rule, the recovery cost of the data to be recovered is calculated based on the amount of data to be recovered and the number of requests to retrieve the data to be recovered from the source. It is characterized by performing a generation process and a subsequent process. [Effects of the Invention]

[0008] According to a typical embodiment of the present invention, it is possible to provide a recovery pattern suitable for the data to be recovered. Other issues, configurations, and effects not mentioned above will be clarified by the following description of the embodiments. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 is a block diagram showing an example of a hybrid cloud system configuration. [Figure 2] Figure 2 is a block diagram showing an example of the hardware configuration of the management server. [Figure 3] Figure 3 is an explanatory diagram showing an example of a business process table. [Figure 4] Figure 4 is an explanatory diagram showing an example of a backup configuration table. [Figure 5] Figure 5 is an explanatory diagram showing an example of a public cloud billing table. [Figure 6] Figure 6 is explanatory diagram 1, which shows the details of cost information in the public cloud billing table. [Figure 7] Figure 7 is explanatory diagram 2, which shows the details of the cost information in the public cloud billing table. [Figure 8] Figure 8 is an explanatory diagram showing an example of a recovery rule. [Figure 9] Figures 9 and 10 are explanatory diagrams showing an example of a recovery rule table. [Figure 10] Figures 9 and 10 are explanatory diagrams showing an example of a recovery rule table. [Figure 11] Figure 11 is a flowchart showing an example of the recovery support processing procedure performed by the management server. [Figure 12] Figure 12 is a flowchart showing a detailed example of the recovery pattern generation process (step S1103) shown in Figure 11. [Figure 13] Figure 13 is a flowchart showing a detailed example of the processing procedure for the recovery pattern generation process (step S1205) related to the business operations shown in Figure 12. [Figure 14] Figure 14 is a flowchart showing a detailed example of the recovery pattern generation process (step S1206) for the data shown in Figure 12. [Figure 15]FIG. 15 is a flowchart showing a detailed processing procedure example of a restoration pattern generation process (step S1403) for data based on the selection restoration rule shown in FIG. 14. [Figure 16] FIG. 16 is an explanatory diagram showing an example of a restoration support start screen. [Figure 17] FIG. 17 is an explanatory diagram showing an example of a restoration cost presentation screen.

Mode for Carrying Out the Invention

[0010] <Hybrid Cloud System> FIG. 1 is a block diagram showing a system configuration example of a hybrid cloud system. The hybrid cloud system 100 is a system that backs up data from the storage system 102 on the on-premises 101 to the public cloud 105 via a network such as the Internet, LAN (Local Area Network), or WAN (Wide Area Network).

[0011] The on-premises 101 has a storage system 102, a management device 103, and a host 104. The storage system 102 has a storage volume 120. The storage volume 120 is provided to the host 104 as a virtual storage volume 131.

[0012] The storage system 102 on the on-premises 101 and the public cloud 105 are also communicably connected via a network. Note that the communication speed ([bps]) is set between the storage system 102 on the on-premises 101 and the public cloud 105 according to the bandwidth.

[0013] The management device 103 has a service portal 130. The service portal 130 provides services to the host 104. Specifically, for example, the service portal 130 has virtual storage volumes 131 to 133. Virtual storage volume 131 is a storage area that virtualizes storage volume 120. Virtual storage volume 132 is a storage area that virtualizes object storage service 151. Virtual storage volume 133 is a storage area that virtualizes block storage service 152.

[0014] Host 104 selects and executes tasks 140 from virtual storage volume 131, saves data generated by tasks 140 to virtual storage volume 131, and issues backup instructions to management device 103. Although host 104 is a computer that runs tasks 140 using virtual storage volumes 131-133, backup and recovery operations do not necessarily have to be performed via host 104. For example, a person (such as an administrator of a volume different from the person running tasks 140 on host 104) may issue an execution request to management device 103 via service portal 130.

[0015] The public cloud 105 consists of one or more computers having processors and memory, and provides the object storage service 151 as a virtual storage volume 132 and the block storage service 152 as a virtual storage volume 133 to the service portal 130.

[0016] Object storage service 151 is a service that provides object storage to the service portal 130 as a virtual storage volume 132. Object storage is a storage device that handles data in units called "objects". Block storage service 152 is a service that provides block storage to the service portal 130 as a virtual storage volume 133. Block storage is a storage device that handles data in units called "blocks".

[0017] In the hybrid cloud system 100, the management device 103 backs up data stored in the storage volume 120 corresponding to the virtual storage volume 131 to the public cloud 105, and restores data backed up in the public cloud 105 to the storage system 102.

[0018] Prior to backup and restore, the management device 103 determines a recovery pattern that meets the data recovery time requirements for each of the 140 business units. The management device 103 also calculates a recovery pattern that reduces recovery costs while meeting the requirements of users accessing the service portal 130 via the host 104. Furthermore, the management device 103 estimates the recovery cost and data copy time for each recovery pattern for each of the 140 business units, and outputs the results of multiple recovery patterns in a format viewable on the host 104. This allows users accessing the host 104 to understand the recovery costs, recovery times, and cost-benefit relationships between the presented recovery patterns.

[0019] <Example of hardware configuration for management device 103> Figure 2 is a block diagram showing an example of the hardware configuration of the management device 103. The management device 103 includes a processor 201, a storage device 202, an input device 203, an output device 204, and a communication interface (communication IF) 205. The processor 201, storage device 202, input device 203, output device 204, and communication IF 205 are connected by a bus 206. The processor 201 controls the management device 103. The storage device 202 serves as the work area for the processor 201. The storage device 202 is a non-temporary or temporary recording medium that stores various programs and data. Examples of storage devices 202 include ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), and flash memory. The input device 203 inputs data. Examples of input devices 203 include a keyboard, mouse, touch panel, numeric keypad, scanner, microphone, and sensor. The output device 204 outputs data. Output devices 204 include, for example, displays, printers, and speakers. The communication IF 205 connects to the network and sends and receives data.

[0020] Furthermore, the computers that make up the public cloud 105 and the computers that make up the host 104 have the same configuration as in Figure 2.

[0021] <Business Table> Figure 3 is an explanatory diagram showing an example of a business table. Business table 300 is a table that stores information about business 140 and is stored in the storage device 202 of the management device 103. Business table 300 has the following fields: business ID 301, business name 302, priority 303, requirements 304, and data name 305. A combination of values ​​from fields 301 to 305 in the same row constitutes an entry representing one business 140.

[0022] Task ID 301 is an identifier that uniquely identifies task 140. Note that task 140 may sometimes be referred to by the value of task ID 301. For example, task 140 with task ID 301 value "B1" may be referred to as task B1.

[0023] Task name 302 is the name that indicates task 140. Priority 303 is an indicator for when task 140 should be prioritized for recovery over other tasks 140. For example, when recovering task 140, the management device 103 recovers it in the order of priority 303 "high" → "medium" → "low".

[0024] Requirement 304 is a condition required for business 140 and has two subfields: recovery level 341 and requested recovery time 342. Recovery level 341 indicates the extent to which recovery should be performed. If it is "business," it indicates the recovery of applications related to business 140 and virtualized resources such as virtual storage volumes 131-133. If it is "data," it indicates copying data backed up to the storage of the public cloud 105 (the backup destination) to the backup source (storage volume 120, virtual storage volume 131, or other storage within the public cloud 105). Requested recovery time 342 is the recovery time required to restore business 140 to recovery level 341.

[0025] Data name 305 is the name of the data used in task 140. The data of data name 305 may be represented by the value of data name 305. For example, data with data name 305 "D1-1" may be written as "Data D1-1". Also, if data D1-1, D1-2, D2-1, etc. are not distinguished, they are simply written as Data D.

[0026] For each of the 140 tasks, there is at least one data point D. For example, if task 140 is an e-commerce site, then data points D1-1 and D1-2 may be data from different users of the e-commerce site, with data point D1-1 being data related to orders and receipts, and data point D1-2 being data related to payments.

[0027] <Backup configuration table> Figure 4 is an explanatory diagram showing an example of a backup configuration table. The backup configuration table 400 is a table that stores backup configuration information, is stored in the storage device 202 of the management device 103, and is updated periodically.

[0028] The backup configuration table 400 has the following fields: data name 305, data amount 401, business ID 301, backup source 402, and backup destination 403. A combination of values ​​for each field in the same row constitutes an entry representing a single backup configuration.

[0029] Data size 401 is the capacity of the data with data name 305. Backup source 402 is the storage that held the data identified by data name 305 and data size 401. Backup source 402 has the following subfields: site ID 421, disk type 422, and data storage location 423.

[0030] Site ID 421 is identification information that uniquely identifies the site (for example, storage system 102) that will be the backup source 402. Disk type 422 is the type of storage device that the site identified by site ID 421 possesses. Disk types 422 include, for example, HDD, SDS (Software Defined Storage), and SSD (Solid State Drive). Data storage location 423 indicates the location where data D, identified by its data name 305 and data amount 401, is stored as the backup source 402.

[0031] The backup destination 403 is a storage device that holds data D, identified by its data name 305 and data volume 401, as a result of a backup from the backup source 402. The backup destination 403 has the following subfields: vendor name 431, service name 432, and data storage location 433.

[0032] Vendor name 431 is the name of the vendor operating public cloud 105. Service name 432 is the name of the service provided by the vendor of vendor name 431. Data storage location 423 indicates the location within public cloud 105 where data D, identified by its data name 305 and data volume 401, is stored as backup location 403.

[0033] <Public Cloud Billing Table> The public cloud billing table will be explained using Figures 5 to 7.

[0034] Figure 5 is an explanatory diagram showing an example of a public cloud billing table. The public cloud billing table 500 is a table that stores public cloud billing information, is stored in the storage device 202 of the management device 103, and is updated periodically.

[0035] The public cloud billing table 500 has the following fields: vendor name 431, service name 432, type 501, cost information 502, and free tier 503. A combination of values ​​for each field in the same row constitutes an entry representing one piece of public cloud billing information.

[0036] Form 501 indicates the hardware or software used in the service identified by service name 432. Cost information 502 is the information used to calculate the cost incurred when the vendor of vendor name 431 provides the service of service name 432 in form 501. Free tier 503 indicates the scope of services that are free of charge when the vendor of vendor name 431 provides the service of service name 432 in form 501, and for which cost information 502 is not incurred.

[0037] Figure 6 is explanatory diagram 1 showing the details of cost information 502 in public cloud billing table 500, and Figure 7 is explanatory diagram 2 showing the details of cost information 502 in public cloud billing table 500. Figure 6 explains the values ​​C1 to C3 of cost information 502, and Figure 7 explains the values ​​C4 to C6 of cost information 502.

[0038] In Figures 6 and 7, the cost information 502 has the following subfields: provisioning 601, IOPS (Input / Output Per Second) 602, throughput 603, data retrieval request 604, external data transfer 605, and inter-service data transfer 606.

[0039] Provisioning 601 is cost information 502 (per GB per month) required to secure resources when creating storage and server instances, regardless of the service usage of service name 432. IOPS 602 indicates cost information 502 per data read / write operation for service name 432. Throughput 603 indicates cost information 502 per unit data transfer rate ([MB / sec]).

[0040] Data retrieval request 604 is cost information 502 for retrieving data stored in public cloud 105 using the service with service name 432.

[0041] External data transfer 605 is cost information 502 for transferring data outside the public cloud 105 (for example, on-premises 101). Inter-service data transfer 606 is cost information 502 for transferring data between services within the same public cloud 105.

[0042] <Recovery Rules> Figure 8 is an explanatory diagram illustrating an example of a recovery rule. A recovery rule is a set of rules for recovering data or business operations.

[0043] Recovery Rule R1 is a rule for copying all data to be backed up from public cloud 105 to on-premises 101. Recovery Rule R2 is a rule for copying all data to be backed up to on-premises 101, starting with the data of business processes 140 with the highest priority of 303.

[0044] Recovery Rule R3 is a rule for copying data to on-premises 101 in units that fit within the free tier 503 of the storage in the public cloud 105 that serves as the backup destination. Recovery Rule R4 is a rule for migrating the data to be recovered from the storage in public cloud 105 where it is stored to storage in another public cloud 105 with lower retrieval costs, and then copying the data to on-premises 101.

[0045] Recovery Rule R5 is a rule for migrating the data to be recovered to block storage provided by the block storage service 152 of the public cloud 105, setting up a virtual server instance, and using the data to perform a provisional recovery of business 140. Recovery Rule R5 applies to data in business table 300 where recovery level 341 is set to "Business".

[0046] Figures 9 and 10 are explanatory diagrams illustrating an example of a recovery rule table. Figure 9 shows recovery rules R1 to R3, and Figure 10 shows recovery rules R4 and R5. Note that the recovery rules in Figures 9 and 10 are not limited to R1 to R5. Additions and modifications may be made as needed. When recovery rules R1 to R5 are not distinguished, they are referred to as "recovery rule R".

[0047] The application unit 901 indicates the data unit to which the recovery rule R applies (all data or data grouped by business 140). The recovery rule table 900 is stored in the storage device 202 of the management device 103. "All data" refers to all data D that are to be recovered.

[0048] "Data grouped by task 140" refers to data D classified by task 140. For example, in Figure 3, if the data to be recovered is data D1-1 and D1-2 from tasks B1 and B3, data D1-1 and D3-1 from task B3, and data D4-2 from task B4, then data D1-1 and D1-2 from task B1 become "data D grouped by task B1". Similarly, data D1-1 and D3-1 from task B3 become "data D grouped by task B3". And data D4-2 from task B4 becomes "data D grouped by task B4". The task 140 that groups the data to be recovered is referred to as the "grouped task".

[0049] Note that while the application unit 901 for recovery rule R4 is "all data / data grouped by business," this means that either "all data" or "data grouped by business" can be set as the application unit 901. For example, if there are multiple types of recovery rule R4, the application unit 901 for one recovery rule R4 may be set to "all data," while the application unit 901 for another recovery rule R4 may be set to "data grouped by business."

[0050] Recovery configuration 902 represents a backup configuration for recovering to recovery level 341 and includes a source 921 and a destination 922. The "backup destination cloud storage" is the storage within the public cloud 105 where the data to be recovered, which will be the source 921, is stored. The "on-premises backup source cloud storage" is the storage system 102 within the on-premises 101, which will be the destination 922 for the data to be recovered.

[0051] "Cloud storage different from the backup destination" refers to storage within another public cloud 105 that is different from the "backup destination cloud storage."

[0052] Applicability condition 903 is the condition under which recovery rule R is applied. Recovery procedure 904 shows the order of recovery according to recovery rule R. Recovery cost calculation formula 905 is the formula for calculating the recovery cost when recovery rule R is applied. "Copy data retrieval cost" is the cost required to retrieve the copy data (i.e., the data to be recovered) from the copy source 921 (backup destination 403). Specifically, it is a formula that adds, for example, the data retrieval request 604 and the data transfer to an external source 605 or inter-service data transfer 606.

[0053] Furthermore, for recovery rule R4, the recovery cost calculation formula 905 includes "cloud storage provisioning costs" and "data migration costs between cloud storage." "Cloud storage provisioning costs" are the costs of provisioning storage within the public cloud 105 (hereinafter referred to as cloud storage) so that it can provide object storage service 151 or block storage service 152, and are determined by the public cloud 105 and transmitted to the management device 103.

[0054] Furthermore, the "data migration cost between cloud storage" is the cost incurred when migrating data between cloud storage systems, which is determined by the public cloud 105 and transmitted to the management device 103.

[0055] Furthermore, for recovery rule R5, the recovery cost calculation formula 905 includes "server instance provisioning cost" and "cloud storage provisioning cost." As shown in Figure 8, the "server instance provisioning cost" is the cost required to launch the virtual server instances necessary to perform temporary recovery of business operations 140 using data in the public cloud 105, and is determined by the public cloud 105 and transmitted to the management device 103.

[0056] Recovery time calculation formula 906 is a formula for calculating the recovery time when applying recovery rule R. For example, the "data copy time from destination to source" for recovery rules R1 to R5 is calculated by dividing the amount of data (401) from the destination to the source by the pre-set communication speed between the destination and the source. If the destination is on-premises 101, the source is public cloud 105, and if the destination is public cloud 105, the source is on-premises 101.

[0057] Also, "data copy time between cloud storage," "cloud storage provisioning time," and " Server instance "Provisioning time" refers to the operation time in Public Cloud 105 and is calculated within Public Cloud 105.

[0058] <Recovery support processing> Figure 11 is a flowchart showing an example of a recovery support processing procedure by the management device 103. The management device 103 determines whether there is a recovery execution request or a recovery pattern generation request (step S1101). A recovery execution request is a request to the management device 103 to perform data or business recovery. A user of the management device 103 may make a recovery execution request to the management device 103 via the management portal, or the host 104 may send a recovery execution request to the management device 103. A recovery pattern generation request is a request from the host 104 to the management device 103 to calculate a recovery pattern. A recovery pattern includes at least one of the recovery procedure, recovery cost, and recovery time in the recovery rule R.

[0059] When a recovery execution request is received (step S1101: recovery execution request), the management device 103 performs recovery based on the recovery procedure 904 of the basic recovery rule R (step S1102). The basic recovery rule R is a pre-configured recovery rule R that is applied when a recovery execution request is received (step S1101: recovery execution request), for example, recovery rule R2.

[0060] When a recovery pattern generation request is received (step S1101: recovery pattern generation request), the management device 103 executes the recovery pattern generation process (step S1103). This calculates a recovery pattern for each task 140. The management device 103 sends the recovery pattern calculated for each task 140 to the host 104 (step S1104). This allows the user of the host 104 or the user of the management device 103 to access the recovery pattern for each task 140. Each The recovery pattern can be checked.

[0061] Next, the management device 103 waits for a recovery execution request (step S1105: No), and if a recovery execution request is received (step S1105: Yes), it performs recovery on the business 140 selected in the recovery execution request using the recovery pattern selected in the recovery execution request (step S1106).

[0062] [Recovery pattern generation process (step S1103)] Figure 12 is a flowchart showing a detailed example of the recovery pattern generation process (step S1103) shown in Figure 11. The management device 103 receives the specification of the data to be recovered from the host 104 or the user of the management device 103 (step S1201). The information specifying the data to be recovered is assumed to be included in the recovery pattern generation request.

[0063] The management device 103 selects an unselected task 140 from the task table 300 (step S1202). The management device 103 determines whether the value of the recovery level 341 of requirement 304 is "task" in the entry for the selected task 140 in step S1202 (step S1203).

[0064] If the value of recovery level 341 is "business" (step S1203: Yes), the management device 103 performs a recovery pattern generation process related to the business for the selected business 140 (step S1204) and proceeds to step S1206. On the other hand, if the value of recovery level 341 is "data" (step S1203: No), the management device 103 performs a recovery pattern generation process related to data for the selected business 140 (step S1205) and proceeds to step S1206.

[0065] In step S1206, the management device 103 determines whether or not there is an unselected task 140 in the task table 300. If there is an unselected task 140, it returns to step S1202. On the other hand, if there is no unselected task 140, it terminates the recovery pattern generation process (step S1103) and proceeds to step S1104.

[0066] [Recovery pattern generation process related to business operations (Step S1205)] Figure 13 is a flowchart showing a detailed example of the processing procedure for the recovery pattern generation process (step S1205) related to the business operations shown in Figure 12.

[0067] The management device 103 groups the data to be recovered by selected business 140 (step S1300). If the data to be recovered includes data D of business B1, B3, and B4, the management device 103 groups the data to be recovered for each of business B1, B3, and B4. Specifically, for example, if the data is D1-1 and D1-2 of business B1, D1-1 and D3-1 of business B3, and D4-2 of business B4, the management device 103 will, as described above, group data D1-1 and D1-2 of business B1 as "data D grouped by business B1", data D1-1 and D3-1 of business B3 as "data D grouped by business B3", and data D4-2 of business B4 as "data D grouped by business B4".

[0068] The management device 103 selects from the recovery rule table 900 (step S1301). The management device 103 refers to recovery rule R5 and calculates the recovery procedure, recovery cost, and recovery time based on the backup configuration information and public cloud billing information (step S1302).

[0069] Specifically, for example, the management device 103 refers to the backup configuration table 400 to identify the backup source 402 and backup destination 403 of the data to be recovered, and generates at least one of the recovery procedure, recovery cost, and recovery time as a recovery pattern for a recovery configuration in which the backup source 402 of the data to be recovered is the copy destination 922 of recovery rule R5 and the backup destination 403 of the data to be recovered is the copy source 921 of recovery rule R5.

[0070] Regarding the recovery procedure, the management device 103 extracts the recovery procedure 904 from the recovery rule R5.

[0071] Regarding recovery costs, the management device 103 extracts the recovery cost calculation formula 905 from recovery rule R5. In the case of recovery rule R5, "server instance provisioning cost + cloud storage provisioning cost + copy data retrieval cost" is extracted as the recovery cost calculation formula 905.

[0072] The management device 103 retrieves backup configuration information for the data grouped by the selection grouping task 140 from the backup configuration table 400. For example, if the data to be recovered includes data D1-1 and D1-2, and the selection grouping task 140 is task B1, then the backup configuration information retrieves the entry for data D1-1 and the entry for data D1-2.

[0073] Furthermore, the management device 103 identifies the backup destination 403 (vendor name 431, service name 432, data storage destination 433) from the acquired backup configuration information. In the example above, the entry in data D1-1 identifies "CV1" as the vendor name 431, "Object Storage Service 1" as the service name 432, and "bucket1" as the data storage destination 433 (the same applies to data D1-2).

[0074] The management device 103 identifies entries from the public cloud billing table 500 that correspond to the vendor name 431 and service name 432 of the backup destination 403 identified from the backup configuration information, and identifies them as public cloud billing information. In the example above, since the vendor name 431 is "CV1" and the service name 432 is "Object Storage Service 1", entry 511 (including cost information C1) is identified as public cloud billing information.

[0075] The management device 103 calculates the recovery cost for the selected grouped operations 140 by substituting the public cloud billing information into the recovery cost calculation formula 905. In the example above, since provisioning 601 is "Null" in the cost information C1 shown in Figure 6, the server instance provisioning cost and cloud storage provisioning cost in the recovery cost calculation formula 905 of recovery rule R5 are "0".

[0076] On the other hand, in the service for entry 511 (including cost information C1), the data retrieval request 604 specifies "0.005 USD / 1000 requests". Therefore, for each of the data D1-1 and D1-2, the cost of retrieving the copied data in the recovery cost calculation formula 905 of recovery rule R5 is calculated by multiplying the number of requests to the copy source 921 by 0.005 USD per 1000 requests to retrieve from "vol 2", which is the data storage location 423 of the backup source 402.

[0077] The management device 103 predicts the number of requests required to retrieve data from the source 921 based on the data volume 401. Specifically, for example, the management device 103 may calculate the number of requests using a function that calculates the number of requests from the data volume 401, or it may determine the number of requests by referring to a table (not shown) that defines the number of requests corresponding to the data volume 401. This allows the recovery cost for grouped business B1 to be calculated.

[0078] Regarding recovery time, the management device 103 extracts the recovery time calculation formula 906 from recovery rule R5. In the case of recovery rule R5, "data copy time from destination to source + server instance provisioning time + cloud storage provisioning time" is extracted as the recovery time calculation formula 906.

[0079] The management device 103 calculates the "data copy time from the destination to the source" by dividing the amount of data transferred from the backup destination cloud storage (backup destination 403) to a different cloud storage (block) that is also the backup destination 403 by the bandwidth between the source and the destination.

[0080] As described above, if the backup configuration information is, for example, data D1-1 and data D1-2, then the site ID 421 of the backup source 402 is "DC1", the disk type 422 is "HDD", and the data storage destination 423 is "vol 2". Also, the vendor name 431 of the backup destination 403 is "CV1", the service name 432 is "Object Storage Service 1", and the data storage destination 433 is "bucket1". Furthermore, the data volume 401 of data D1-1 is "800 (GB)", and the data volume 401 of data D1-2 is "1200 (GB)". In other words, the "data copy time from the destination to the source" can be calculated by dividing the total data volume 401 of data D1-1 and data D1-2, which is 2000 GB, by the communication speed within the public cloud 105.

[0081] Furthermore, the management device 103 obtains backup configuration information from the public cloud 105, such as the "server instance provisioning time" and "cloud storage provisioning time" measured in the public cloud 105 when backing up data D1-1 and data D1-2.

[0082] The management device 103 calculates the recovery time for recovery rule R5 by adding the calculated "data copy time from the destination to the source" and the "server instance provisioning time" and "cloud storage provisioning time" obtained from the public cloud 105.

[0083] The management device 103 stores the recovery procedure, recovery cost, and recovery time obtained in step S1302 as a recovery pattern (step S1303), and in step S120 6 It will transition to [this].

[0084] [Data recovery pattern generation process (step S120) 5 )] Figure 14 shows the recovery pattern generation process (step S120) for the data shown in Figure 12. 5 This is a flowchart showing a detailed example of the processing procedure.

[0085] The management device 103 selects an unselected recovery rule R from the recovery rule table 900, excluding recovery rule R5 (step S1401). The management device 103 refers to the application unit 901 of the selected recovery rule R (step S1402). If the application unit 901 is "all data" (step S1402: all data), the selected recovery rule R is recovery rule R1 or R4. In this case, the process proceeds to step S1404.

[0086] If the application unit 901 is "data grouped by business" (step S1402: data grouped by business), then the selected recovery rule R is recovery rule R2 or R3. In this case, the management device 103 groups the data to be recovered by the selected business 140, as in step S1300 (step S1403), and proceeds to step S1404.

[0087] The management device 103 determines whether the data to be recovered satisfies the application conditions 903 of recovery rule R4 when the selected recovery rule R is recovery rule R4 (step S1404).

[0088] If the conditions are met (step S1404: Yes), the management device 103 executes a recovery pattern generation process for the data based on the selective recovery rule (step S1405) and proceeds to step S1408. If the conditions are not met, or if the selective recovery rule R is not recovery rule R4 (step S1404: No), the management device 103 determines whether there is a free tier 503 at the backup destination 403 for the data to be recovered (step S1406). Specifically, for example, the management device 103 refers to the public cloud billing table 500 to determine whether there is a free tier 503 at the vendor of the backup destination 403.

[0089] For example, if the backup configuration information is data D1-1 and data D1-2, the vendor name 431 of the backup destination 403 is "CV1" and the service name 432 is "Object Storage 1". That is, it is entry 511. Entry 511 has a free tier 503 with "up to 5GB of stored files" and "20,000 get requests".

[0090] If there is no free tier 503 (step S1406: No), the selective recovery rule R is recovery rule R1 or R2. In this case, the management device 103 performs a recovery pattern generation process for the data based on the selective recovery rule (step S1405) and proceeds to step S1408.

[0091] On the other hand, if there is a free tier 503 (step S1404: Yes), the management device 103 determines whether it is possible to split the data to be recovered, which has been grouped to fit within the free tier 503 (step S1407). For example, in the case of data D (data D1-1, data D1-2) grouped in business B1, the management device 103 splits data D (data D1-1, data D1-2) grouped in business B1 so that the split data satisfies the conditions of "up to 5GB of stored files" and "20000 get requests".

[0092] If the data can be split (step S1407: Yes), the selective recovery rule R is recovery rule R3. In this case, the management device 103 performs a recovery pattern generation process for the data based on the selective recovery rule (step S1405) and proceeds to step S1408.

[0093] On the other hand, if the partitioning is not possible (step S1407: No), the selected recovery rule R does not correspond to any of the recovery rules R1 to R4, and no recovery pattern is generated, and step S140 8 It will transition to [this].

[0094] Step S140 8 Then, if there is an unselected recovery rule R, the management device 103 returns to step S1401, and if there is no unselected recovery rule R, it proceeds with the data recovery pattern generation process (step S120). 5 ) complete step S120 6 It will transition to [this].

[0095] [Data recovery pattern generation process based on selective recovery rules (step S1405)] Figure 15 is a flowchart showing a detailed example of the processing procedure for generating recovery patterns for data based on the selective recovery rules shown in Figure 14 (step S1405). The management device 103 refers to the backup configuration table 400 to identify the backup source 402 and backup destination 403 of the data to be recovered, identifies a recovery configuration in which the backup source 402 of the data to be recovered becomes the copy destination 922 of recovery rules R1 to R4, and the backup destination 403 of the data to be recovered becomes the copy source 921 of recovery rules R1 to R4 (step S1500), and then executes steps S1501 to S1505.

[0096] The management device 103 calculates the recovery time based on the selected recovery rule R, using the amount of backup data and public cloud billing information (step S1501). The calculation of the recovery time (step S1501) is performed in the same manner as in step S1302.

[0097] The management device 103 determines whether the calculated recovery time is within the requested recovery time (step S1502). If the calculated recovery time is not within the requested recovery time (step S1502No), the management device 103 terminates the recovery pattern generation process for data based on the selected recovery rule (step S1403) and proceeds to step S1407.

[0098] On the other hand, if the calculated recovery time is within the required recovery time (step S1502: Yes), the management device 103 refers to the backup source 402 and backup destination 403 of the backup configuration information and extracts the recovery procedure 904 of the selected recovery rule R from the recovery rule table 900 (step S1503).

[0099] The management device 103 calculates the recovery cost from the amount of backup data and public cloud billing information (step S1504). The calculation of the recovery cost (step S1504) is performed in the same manner as in step S1302.

[0100] The management device 103 stores the recovery procedure, recovery cost, and recovery time obtained in steps S1501, S1503, and S1504 as a recovery pattern (step S1505), and performs a recovery pattern generation process for the data based on the selected recovery rule (step S140 5 ) ends and proceeds to step S1408.

[0101] <Screen for starting recovery support> Figure 16 is an explanatory diagram showing an example of the recovery support start screen. The recovery support start screen 1600 is used when you want to check the cost of recovery during backup operation or when you want to check the recovery procedure in the event of a failure. The recovery support start screen 1600 is displayed on a display device, which is an example of an output device 204 of the management device 103 or host 104. The recovery support start screen 1600 has a recovery pattern generation start button 1601 and a recovery specification button 1602. The recovery pattern generation start button 1601 is a user interface that accepts the start of recovery pattern calculation when pressed. The recovery specification button 1602 is a user interface that accepts the specification of recovery start when pressed. When the recovery specification button 1602 is pressed, the recovery selection screen 1610 is displayed.

[0102] The recovery selection screen 1610 includes an immediate recovery start button 1611, a selected task recovery start button 1612, and a target task selection checkbox field 1613. Immediate recovery start Button 1611 is a user interface that, when pressed, initiates the recovery process. Immediate recovery. start If button 1611 is pressed, recovery will be performed according to recovery procedure 904 of recovery rule R1.

[0103] The Selected Task Recovery Start button 1612 is a user interface that accepts the start of recovery for the target task selected in the Target Task Selection check box field 1613 when pressed. The Target Task Selection check box field 1613 is a user interface that accepts the selection of a target task. When the Target Task Selection check box field 1613 is pressed, recovery is performed according to recovery procedure 904 of recovery rule R2.

[0104] <Screen showing recovery costs> Figure 17 is an explanatory diagram showing an example of a recovery cost presentation screen. The recovery cost presentation screen 1700 includes a recovery pattern list 1701 and recovery pattern details 1702. The recovery cost presentation screen 1700 is displayed for each business operation. The recovery pattern list 1701 displays the recovery cost and recovery time for each recovery pattern calculated by the management device 103. The recovery pattern details 1702 is a graph showing the relationship between the recovery cost and recovery time for each recovery pattern calculated by the management device 103.

[0105] When a recovery pattern is selected in the recovery pattern list 1701 or the recovery pattern details 1702, the recovery procedure display screen 1710 is displayed. The recovery procedure display screen 1710 displays the recovery procedure for the recovery pattern selected on the recovery cost presentation screen 1700. Specifically, for example, the recovery procedure display screen 1710 includes recovery procedure information 1711 and a recovery execution button 1712. The recovery procedure information 1711 is information indicating the recovery procedure for the recovery pattern selected on the recovery cost presentation screen 1700. The recovery execution button 1712 is a user interface that, when pressed, executes the recovery using the recovery pattern selected on the recovery cost presentation screen 1700.

[0106] Thus, according to this embodiment, it is possible to provide recovery patterns suitable for the data to be recovered. Furthermore, by grouping the data to be recovered by business process, recovery patterns can be provided on a business process basis. In addition, since the application unit 901 is defined in the recovery rule R, the data to be recovered can be automatically grouped. Furthermore, since the recovery pattern includes the recovery cost, the user can check how much the recovery will cost. Furthermore, since the recovery pattern includes the recovery time, the user can check how long the recovery will take. In addition, the user can check whether the recovery time for the data to be recovered is within the requested recovery time 342 before recovery, thereby preventing situations where the recovery process exceeds the requested recovery time 342. Furthermore, since the recovery pattern includes the recovery procedure, the user can check the order in which the recovery will be performed.

[0107] Furthermore, by associating the recovery cost and recovery time of the data to be recovered, it is possible to determine which recovery pattern corresponds to what recovery cost and recovery time. Additionally, by associating the recovery cost, recovery time, and recovery procedure of the data to be recovered, it is possible to determine which recovery pattern corresponds to what recovery cost, recovery time, and recovery procedure. Moreover, the management device 103 can generate recovery patterns for backup configurations spanning on-premises 101 and public cloud 105, and can also generate recovery patterns for storage within the public cloud 105.

[0108] It should be noted that the present invention is not limited to the embodiments described above, but includes various modifications and equivalent configurations within the spirit of the attached claims. For example, the embodiments described above are described in detail to make the present invention easier to understand, and the present invention is not necessarily limited to having all of the described configurations. Furthermore, some of the configurations of one embodiment may be replaced with those of another embodiment. Furthermore, some of the configurations of one embodiment may be added to those of another embodiment. Furthermore, some of the configurations of each embodiment may be added, deleted, or replaced with other configurations.

[0109] Furthermore, each of the aforementioned configurations, functions, processing units, and processing means may be implemented in hardware, for example, by designing them as integrated circuits, or they may be implemented in software by having a processor interpret and execute programs that realize each function.

[0110] Information such as programs, tables, and files that implement each function can be stored in memory, hard disks, SSDs (Solid State Drives), or on recording media such as IC (Integrated Circuit) cards, SD cards, and DVDs (Digital Versatile Discs).

[0111] Furthermore, the control lines and information lines shown are those deemed necessary for explanation purposes and do not necessarily represent all control lines and information lines required for implementation. In reality, it can be assumed that almost all components are interconnected. [Explanation of Symbols]

[0112] 100 Hybrid Cloud Systems 101 On-Premise 102 Storage Systems 103 Management device 104 Hosts 105 Public Cloud 201 Processor 202 Storage Devices 300 Business Tables 400 Backup Configuration Tables 500 Public Cloud Billing Table 900 Recovery Rule Table

Claims

1. A management method performed by a management device that manages the restoration of data backed up to a backup destination to the backup source, The management device comprises a processor that executes a program and a storage device that stores the program. The storage device stores multiple recovery rules that define multiple recovery patterns in a recovery configuration indicating the source and destination of the data, and backup configuration information relating to the backup source and destination of the data. The recovery rule includes a recovery cost calculation formula that calculates the recovery cost of retrieving the data from the source and transferring it to the destination, based on the amount of data and the number of requests to retrieve the data from the source. In the aforementioned management method, The aforementioned processor, A specification process to specify the data to be recovered, A selection process for selecting a specific recovery rule from among the aforementioned multiple recovery rules, A generation process that, by referring to the backup configuration information, sets the backup source of the data to be recovered specified by the designation process as the copy destination, and sets the backup destination of the data to be recovered as the copy source, generates a recovery pattern for the data to be recovered according to a specific recovery rule selected by the selection process, and calculates the recovery cost of the data to be recovered based on the amount of data of the data to be recovered and the number of requests to retrieve the data to be recovered from the copy source, using the recovery cost calculation formula included in the specific recovery rule. A management method characterized by performing the following actions.

2. A management method according to claim 1, The storage device stores business information that associates the data with the business to which the data is applied. In the aforementioned management method, The aforementioned processor, Referencing the aforementioned business information, a grouping process is executed to group multiple recovery target data for the same business operation. In the generation process, the processor refers to the backup configuration information and uses the backup source of the grouped plurality of recovery target data as the copy destination, and in a recovery configuration of the grouped plurality of recovery target data where the backup destination of the grouped plurality of recovery target data is the copy source, it generates a recovery pattern for the grouped plurality of recovery target data according to the specific recovery rule. A management method characterized by the following features.

3. A management method according to claim 2, The recovery rule specifies an application unit, which is the unit of data to which the recovery rule applies. In the aforementioned management method, The aforementioned processor, If the unit to which the aforementioned specific recovery rule is applied is multiple data sets grouped under the same business, the grouping process is executed. A management method characterized by the following features.

4. The management method according to Claim 1, The recovery rule includes a recovery time calculation formula that calculates the recovery time, which is the time required for the recovery, based on the amount of data and the data communication speed between the source and destination of the copy. In the generation process, the processor uses the recovery time calculation formula included in the specific recovery rule to calculate the recovery time for the data to be recovered, based on the amount of data to be recovered and the communication speed. A management method characterized by the following features.

5. The management method according to Claim 4, In the generation process, the processor determines whether the recovery time of the data to be recovered is within a predetermined requested recovery time, and if the recovery time of the data to be recovered is within a predetermined requested recovery time, it outputs the recovery time of the data to be recovered. A management method characterized by the following features.

6. The management method according to Claim 1, The recovery rule has a recovery procedure that indicates the order of recovery, In the generation process, the processor extracts specific recovery procedures included in the specific recovery rule. A management method characterized by the following features.

7. The management method according to Claim 1, The recovery rule includes a recovery time calculation formula that calculates the recovery time, which is the time required for the recovery, based on the amount of data and the data communication speed between the source and destination of the copy. In the generation process, the processor uses the recovery time calculation formula included in the specific recovery rule to calculate the recovery time for the data to be recovered based on the amount of data to be recovered and the communication speed, and generates the recovery pattern by relating the recovery cost of the data to be recovered and the recovery time of the data to be recovered. A management method characterized by the following features.

8. The management method according to claim 7, The recovery rule has a recovery procedure that indicates the order of recovery, In the generation process, the processor extracts specific recovery procedures included in the specific recovery rule, and generates the recovery pattern by associating the specific recovery procedures with the recovery cost and recovery time of the data to be recovered. A management method characterized by the following features.

9. The management method according to claim 7, In the selection process, the processor selects a plurality of the specific recovery rules, In the generation process, the processor generates the recovery pattern for each of the plurality of specific recovery rules. A management method characterized by the following features.

10. A management method according to Claim 1, The aforementioned backup destination is a public cloud, and the aforementioned backup source is on-premises. A management method characterized by the following features.

11. A management method according to Claim 1, The source of the copy is a first storage within the public cloud, and the destination of the copy is a second storage within the public cloud. A management method characterized by the following features.

12. A management method according to Claim 1, The aforementioned processor, A recovery process is performed based on the recovery pattern of the data to be recovered generated by the generation process, A management method characterized by performing the following actions.

13. A management program that causes a processor to execute a process for managing the restoration of data backed up to a backup destination to a backup source, The aforementioned processor is capable of accessing the memory device, The storage device stores multiple recovery rules that define multiple recovery patterns in a recovery configuration indicating the source and destination of the data, and backup configuration information relating to the backup source and destination of the data. The recovery rule includes a recovery cost calculation formula that calculates the recovery cost of retrieving the data from the source and transferring it to the destination, based on the amount of data and the number of requests to retrieve the data from the source. The management program is, The aforementioned processor, A specification process to specify the data to be recovered, A selection process for selecting a specific recovery rule from among the aforementioned multiple recovery rules, A generation process that, by referring to the backup configuration information, sets the backup source of the data to be recovered specified by the designation process as the copy destination, and sets the backup destination of the data to be recovered as the copy source, generates a recovery pattern for the data to be recovered according to a specific recovery rule selected by the selection process, and calculates the recovery cost of the data to be recovered based on the amount of data of the data to be recovered and the number of requests to retrieve the data to be recovered from the copy source, using the recovery cost calculation formula included in the specific recovery rule. A management program characterized by causing the execution of a command.

14. A management device for managing the restoration of data backed up to a backup destination to a backup source, It comprises a processor that executes a program and a storage device that stores the program, The storage device stores multiple recovery rules that define multiple recovery patterns in a recovery configuration indicating the source and destination of the data, and backup configuration information relating to the backup source and destination of the data. The recovery rule includes a recovery cost calculation formula that calculates the recovery cost of retrieving the data from the source and transferring it to the destination, based on the amount of data and the number of requests to retrieve the data from the source. The aforementioned processor, A selection process for selecting a specific recovery rule from among the aforementioned multiple recovery rules, A generation process that, by referring to the backup configuration information, sets the backup source of the data to be recovered specified by the designation process as the copy destination, and sets the backup destination of the data to be recovered as the copy source, generates a recovery pattern for the data to be recovered according to a specific recovery rule selected by the selection process, and calculates the recovery cost of the data to be recovered based on the amount of data of the data to be recovered and the number of requests to retrieve the data to be recovered from the copy source, using the recovery cost calculation formula included in the specific recovery rule. A management device characterized by performing the following actions.

Images