Backup management system, management computer, and management program

Abstract

To provide a backup management system that uses a backup requirement as a constraint and designs a cost-effective backup configuration and a backup data storage destination so that scale of the backup data storage destination is reduced.SOLUTION: A backup management system, on the basis of information on a configuration of a management target business system server, information on a configuration of a repository server that stores backup data, input backup settings information, and an arrangement constraint rule for determining an arrangement of the backup data according to a purpose of the backup, calculates a combination of backup repository arrangement that satisfies an arrangement constraint rule, estimates processing time for a predetermined backup for the backup repository arrangement, estimates processing time for a predetermined restore for the backup repository arrangement and a restore object, and derives a combination of the backup processing time and the restore processing time that satisfies target backup completion time and target restore processing time of the input backup settings information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a backup management system, a management computer, and a management program.

Background Art

[0002] In recent years, in the field of IT (Information Technology), from the viewpoint of effectively utilizing the resources of a computer system, virtualization technology of a server that divides the computing resources of one computer into a plurality of virtual machines (VM: Virtual Machine) and uses them is known.

[0003] In addition to this, the case of using a public cloud instead of building an IT system in a data center (on-premises) owned by a company has been increasing. A general public cloud is a service in which a data center operator pools computing resources such as servers, disks (also called storage), and networks, and divides them for each user using virtualization technology. In a public cloud, usage-based billing based on the performance of the used computing resources (the amount of computing resources such as the number of CPU cores of the server and the quality such as the type of disk) and the usage time is common.

[0004] In the management of an IT system, in case an abnormality occurs in the data processed by the IT system or a failure occurs in the devices or software constituting the IT system, backups of the data processed by the IT system are often taken. A plurality of storage destinations for these backup data may be prepared according to the purpose of the backup and the availability required by the IT system.

[0005] As such a technique, for example, there is the technique described in Patent Document 1. In Patent Document 1, a technique for determining a storage destination of backup data is disclosed based on the requirement of storing backup data at a location as geographically distant as possible for disaster countermeasures.

Prior Art Documents

[0006] [Patent Document 1] WO2004 / 053696 publication [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] While there are conventional technologies, such as Patent Document 1, that determine the configuration of backup jobs based on backup or restore requirements, virtualization technology and public clouds have made it possible to immediately build backup system configurations, starting from a small scale. Therefore, when building a system, it is more cost-effective to adopt a small configuration in the initial stages and then increase the scale of the backup system as the amount of data that needs to be backed up increases or as changes are made to improve the availability of the system through backups.

[0008] Therefore, when building a backup system or adding or modifying backup execution processes (hereinafter sometimes referred to as backup jobs), it is necessary to design a cost-effective backup configuration and backup data storage location that minimizes the size of the backup data storage location, while taking into account the backup requirements of each IT system.

[0009] This invention has been made in view of the above circumstances, and its purpose is to provide a cost-effective backup configuration that reduces the size of the backup data storage location while being constrained by the requirements for backing up IT systems, and a technology that enables the design of a backup data storage location. [Means for solving the problem]

[0010] To achieve the above objective, the backup management system relating to one perspective is a backup management system that uses a computer having a processor and memory to perform backup and restore of managed items and manage backup data, wherein the processor calculates combinations of backup repository placements that satisfy the placement constraint rules based on business system configuration information which is information about the configuration of business system servers included in the managed items, backup repository configuration information which is information about the configuration of repository servers that store the backup data, input backup setting information and placement constraint rules for determining the placement of backup data according to the purpose of the backup, predicts a predetermined backup processing time for the backup repository placement, predicts a predetermined restore processing time for the backup repository placement and the purpose of the restore, and derives a combination from the backup repository placement combinations in which the backup processing time and the restore processing time satisfy the target backup completion time and target restore processing time included in the input backup setting information. [Effects of the Invention]

[0011] According to the present invention, it is possible to design a cost-effective backup configuration and backup data storage location that reduces the size of the backup data storage location while being constrained by the requirements for backing up IT systems. [Brief explanation of the drawing]

[0012] [Figure 1] Figure 1 is a logical overall configuration diagram of the backup management system according to the first embodiment. [Figure 2] Figure 2 is an overall configuration diagram including the physical configuration of the backup management system according to the first embodiment. [Figure 3] Figure 3 is a diagram showing the configuration of the business system configuration information table according to the first embodiment. [Figure 4]FIG. 4 is a configuration diagram of a table of backup repository configuration information according to the first embodiment. [Figure 5] FIG. 5 is a configuration diagram of a table of placement constraint rules according to the first embodiment. [Figure 6] FIG. 6 is a diagram showing an example of a backup setting input screen according to the first embodiment. [Figure 7] FIG. 7 is a flowchart of a backup placement calculation program according to the first embodiment. [Figure 8] FIG. 8 is a flowchart of an additional resource calculation process according to the first embodiment. [Figure 9A] FIG. 9A is a diagram showing an example of learning data of a backup processing calculation program according to the first embodiment. [Figure 9B] FIG. 9B is a diagram showing an example of learning data of a backup processing calculation program according to the first embodiment. [Figure 9C] FIG. 9C is a diagram showing an example of learning data of a backup processing calculation program according to the first embodiment. [Figure 10A] FIG. 10A is a diagram showing an example of learning data of a restore processing calculation program according to the first embodiment. [Figure 10B] FIG. 10B is a diagram showing an example of learning data of a restore processing calculation program according to the first embodiment. [Figure 10C] FIG. 10C is a diagram showing an example of learning data of a restore processing calculation program according to the first embodiment. [Figure 11A] FIG. 11A is a diagram showing an example of learning data of a backup processing calculation program according to the first embodiment. [Figure 11B] FIG. 11B is a diagram showing an example of learning data of a backup processing calculation program according to the first embodiment. [Figure 11C] FIG. 11C is a diagram showing an example of learning data of a backup processing calculation program according to the first embodiment. [Figure 11D]FIG. 11D is a diagram showing an example of learning data of a backup process calculation program according to the first embodiment. [Figure 11E] FIG. 11E is a diagram showing an example of learning data of a backup process calculation program according to the first embodiment. [Figure 11F] FIG. 11F is a diagram showing an example of learning data of a backup process calculation program according to the first embodiment. [Figure 12A] FIG. 12A is a diagram showing an example of learning data of a restore process calculation program according to the first embodiment. [Figure 12B] FIG. 12B is a diagram showing an example of learning data of a restore process calculation program according to the first embodiment. [Figure 12C] FIG. 12C is a diagram showing an example of learning data of a restore process calculation program according to the first embodiment. [Figure 12D] FIG. 12D is a diagram showing an example of learning data of a restore process calculation program according to the first embodiment. [Figure 12E] FIG. 12E is a diagram showing an example of learning data of a restore process calculation program according to the first embodiment. [Figure 12F] FIG. 12F is a diagram showing an example of learning data of a restore process calculation program according to the first embodiment. [Figure 13] FIG. 13 is a diagram showing an example of an arrangement plan selection screen according to the first embodiment. [Figure 14] FIG. 14 is a configuration diagram of a table of backup job information according to the first embodiment. [Figure 15A] FIG. 15A is a flowchart of a backup configuration change program according to the first embodiment. [Figure 15B] FIG. 15B is a flowchart of a backup job registration program according to the first embodiment. [Figure 15C] FIG. 15C is a flowchart of a backup job execution program according to the first embodiment. [Figure 16]Figure 16 is a diagram showing the configuration of the backup data information table according to the first embodiment. [Figure 17] Figure 17 is a flowchart of the additional resource calculation process according to the second embodiment. [Figure 18] Figure 18 shows an example of the backup settings input screen according to the third embodiment. [Figure 19] Figure 19 shows an example of the restore execution screen according to the fourth embodiment. [Figure 20] Figure 20 is a flowchart of the restore execution program according to the fourth embodiment. [Figure 21] Figure 21 shows an example of the restore execution screen according to the fourth embodiment. [Modes for carrying out the invention]

[0013] In the following description of the present invention, reference is made to the accompanying drawings, which form part of the disclosure. These drawings illustrate exemplary embodiments of the present invention and do not limit it. In these drawings, the same reference numerals indicate the same components across multiple figures. Furthermore, while the detailed description provides various exemplary embodiments, it should be noted that the present invention is not limited to the embodiments described and illustrated herein and can be extended to other embodiments known or to be known to those skilled in the art, as described and illustrated below. Unless otherwise specified, each component may be singular or plural. The positions, sizes, shapes, and extents of the components shown in the drawings may not represent their actual positions, sizes, shapes, and extents in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the positions, sizes, shapes, and extents disclosed in the drawings.

[0014] Furthermore, the following description discloses many specific details to ensure a full understanding of the present invention. However, as will be apparent to those skilled in the art, not all of these specific details are necessary to carry out the present invention. In other circumstances, known structures, materials, circuits, processes, and interfaces may not be described in detail and / or may be shown in the form of block diagrams, so as not to unnecessarily complicate the present invention.

[0015] Furthermore, in the following explanation, processing may be described with "program" as the operating entity. However, since a program is executed by a processor (e.g., a CPU (Central Processing Unit)) to perform defined processing using storage devices (e.g., memory) and / or interface devices as appropriate, the processor (or a device or system having such a processor) may be the entity performing the processing. Also, the processor may include hardware circuits that perform some or all of the processing, and the entity performing the processing by executing the program may be a controller, device, system, computer, or node having a processor. The entity performing the processing by executing the program may be an arithmetic program, and may include dedicated circuits that perform specific processing (e.g., FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)).

[0016] The program may be installed from the program source into a device such as a computer. The program source may be, for example, a program distribution server or a computer-readable storage medium. Also, in the following description, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs.

[0017] Furthermore, in the following description, when we refer to a computer, server, or other computer, it may refer to a physical computer, or to a virtual machine or container created by virtualizing a physical computer using virtualization technology. One or more of these computers, servers, computers, virtual machines, or containers can provide the services related to this system by running one or more programs. Users of this system can reduce costs by effectively utilizing hardware resources through the provision of these services.

[0018] Furthermore, in the following explanation, when describing similar elements separately, the reference code of that element will be used; when describing similar elements without distinction, the common parent code among the reference codes of those elements will be used. For example, when describing repository servers without distinction, they will be written as repository server 204; when describing individual repository servers separately, they will be written as repository server 204aa, 204ab, and so on.

[0019] Furthermore, the physical or virtual computers, networks, storage, operating systems (OS), middleware, and other components that make up an IT system are sometimes collectively referred to as IT infrastructure.

[0020] Furthermore, while the following explanation may use the term "AAA table" to describe information, the information may be represented in any data structure. In other words, to show that the information is independent of the data structure, "AAA table" can be called "AAA information." Also, when describing identification information, if terms such as "identification information," "identifier," "name," "ID," or "number" are used, these terms are interchangeable.

[0021] ≪First Embodiment≫ Figure 1 is a logical overall configuration diagram of the backup management system according to the first embodiment. The backup management system 100 is an example of a management system and manages managed systems 200 that have a backup system equipped with the function of backing up and restoring IT systems and data specified by the system administrator.

[0022] The managed system 200 is an example of an IT system and backup system, and comprises one or more business system servers 201 that perform business operations and one or more repository servers 202 that store backup data of the data processed by the business system servers.

[0023] The business system server 201 has data 203 stored in a storage device, etc., and a backup program 204. The data 203 is processed or stored on the business system server 201 in order to execute business operations. The backup program 204 is a program that copies and stores the data 203 as backup data on the repository server 202, or restores the backup data to a designated server according to the instructions of the system administrator. In addition to copying the data 203, the backup program 204 may perform data processing such as compression to reduce data size or splitting the data to improve transfer efficiency. In this embodiment, the configuration of the backup program on the business system server 201 is given as an example, but the backup program may run on a server other than the business system server 201 and perform backup and restore processing of data 203 via a network. Alternatively, the backup program may run on the business system server 201, another server, or both, and perform and manage backup and restore of multiple business system servers 201 together.

[0024] The repository server 202 has a backup repository 205. The backup repository 205 is a storage device of the repository server 202 where data 203 is copied as backup data by the backup program 204 and stored.

[0025] For example, the business system server 201 and the backup repository 202 are connected via network 170 (see Figure 2). The backup program 204 transfers data 203 to the repository server 202 via network 170 and saves it to the backup repository 205. When the restore process is executed, the backup program 204 copies the backup data stored in the backup repository 205 via network 170 and transfers it to the specified business system server 201.

[0026] The managed system 200 has IT infrastructure (for example, servers including business system servers 201 and repository servers 202) in one or more regions and areas. A region 206 is defined as an area where data centers where the IT infrastructure is installed are geographically clustered. A zone 207 is defined as a collection of one or more data centers within region 206 that are physically and software autonomous. Regions 206 and zones 207 are connected by networks 170, allowing for data transfer between them. Therefore, even though data transfer is possible between zones and regions, if equipment or software operating independently in each zone or region fails, the failure will not spread to other zones or regions.

[0027] The backup management system 100 includes, as data, business system configuration information 111, backup repository 112, placement constraint rules 113, backup job information 121, and backup data information 122. It also includes business system load information 131, backup repository load information 132, and backup data information 122 for executing the processing of the second, third, and fourth embodiments.

[0028] The business system configuration information 111 stores the configuration information of the IT infrastructure of the business system server 201. The backup repository configuration information 112 stores the configuration information of the IT infrastructure of the repository server 202. The placement constraint rules 113 store rules that define whether backup data can be placed in the same zone, other zones, or other regions for the purpose of the backup entered by the system administrator. The backup job information 121 stores the configuration information of the backup job set by the system administrator. The backup data information 122 stores the results of the backup process executed by the backup program 204.

[0029] The business system load information 131 processed in the second embodiment stores time-series data of the load on the IT infrastructure constituting the business system server 201 (e.g., CPU usage, disk transfer bandwidth usage, disk I / O volume, network I / F bandwidth usage). The backup repository load information 132 processed in the second embodiment stores time-series data of the load on the IT infrastructure constituting the repository server 202 (e.g., CPU usage, disk transfer bandwidth usage, disk I / O volume, network I / F bandwidth usage).

[0030] The business system configuration information 111, backup repository configuration information 112, and business system load information 131 and backup repository load information 132 store information collected by the managed information collection program 146 from the managed system 200 via the network 170. This information may be updated periodically, when the configuration of the managed system 200 is updated, or at any time.

[0031] Next, an overview of the processing of the backup management system 100 of the first embodiment will be described. When a system administrator enters configuration information regarding backup jobs for data 203 of the business system server 201 from the backup configuration input screen 11000, the backup management system 100 starts and executes the backup placement calculation program 140. The backup placement calculation program 140 (more precisely, the processor 161 of the management computer 160 that executes the backup placement calculation program 140 (see Figure 2)) derives all repository servers 202 that satisfy the backup requirements, or a combination of one program (including the case where there is only one repository server 202), as backup data storage locations, based on the backup purpose, number of backups, region 206 and zone 207 of the business system server 201 to be backed up, and placement constraint rule 113 specified on the backup configuration input screen 11000. Next, the combination of repository servers 202 that satisfy the target backup completion time and target restore time specified on the backup configuration input screen 11000 are narrowed down based on the backup job completion time and restore processing time predicted by the backup processing performance calculation program 141 and the restore processing performance calculation program 142. Next, for each of the narrowed-down combinations of repository servers 202, the program determines whether additional IT infrastructure resources are needed for the repository servers, and if so, calculates the necessary additional resources and the costs incurred. The backup placement calculation program 140 then displays the combinations of repository servers 202 on the placement selection screen 12000. The placement selection screen 12000 may display additional costs, the number of repository servers, the estimated backup completion time, and the estimated restore time for each combination of repository servers 202. This allows the system administrator to determine the most cost-effective backup data storage location.

[0032] When the system administrator selects a combination of repository servers 202 from the deployment selection screen 12000 and completes the backup job settings, the backup configuration change program 143 is launched. The backup configuration change program 143 executes a configuration change process on the managed system 202, adding the additional resources derived by the backup deployment calculation program 140.

[0033] Furthermore, the backup configuration change program 143 starts the backup job registration program 144. The backup job registration program 144 registers the backup job configuration information in the backup job information 121 based on the information entered on the backup setting input screen 11000 and the layout selection screen 12000. The backup execution program 145 executes the backup job triggered by the backup start time registered in the backup job information 121 and registers the execution result in the backup data information 122.

[0034] The restore execution program 150 and the restore execution screen 13000 will be described in the third embodiment.

[0035] According to the backup management system 100, the combination of repository servers 202 is derived based on the purpose of the backup, availability, backup completion time, and restore processing time. It also displays information indicating the most cost-effective combination. The backup system configuration can be modified as needed. This enables the construction of a cost-effective backup system and the configuration of backup jobs.

[0036] This section describes the more specific configuration of backup management system 100.

[0037] Figure 2 is an overall configuration diagram including the physical configuration of the backup management system 100 and the managed system 200 according to the first embodiment. The management computer 160, which constitutes the backup management system 100, is, for example, a general-purpose computer and includes a processor 161 as an example of a processor, main memory 162, secondary memory 163, input device 164, network interface device (network I / F) 165, and output device 166. These devices are connected via a system bus 167. The management computer 160 may be composed of multiple computers, and distribution and integration are optional depending on processing efficiency and other factors.

[0038] The processor 161 executes various processes according to the programs stored in the main memory 162 and / or sub-memory 163.

[0039] The secondary storage device 163 is an example of a storage device, such as a non-volatile storage device like an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The secondary storage device 163 contains business system configuration information 111, backup repository configuration information 112, placement constraint rules 113, backup job information 121, backup data information 122, business system load information 131, and backup repository load information 132. At least one of these pieces of information may be stored in another suitable storage area accessible to the processor 161.

[0040] The main memory 162 is an example of a storage device, such as RAM (Random Access Memory), and stores programs executed by the processor 161 and necessary information. The main memory 162 stores the backup placement calculation program 140, the backup processing performance calculation program 141, the restore processing performance calculation program 142, the backup configuration change program 143, the backup job registration program 144, the managed information collection program 146, and the restore execution program 150. At least one of these programs may be stored in another suitable storage area accessible by the processor 161. Each program may also be stored on a computer-readable non-volatile recording medium and read by a reader or retrieved from an external device via the network interface 165.

[0041] The network interface 165 communicates with other devices (business system server 201, repository server 202) via network 170. The network interface 165 receives various information such as configuration information and load information from devices managed by the backup management system 100, such as the business system server 201 and the repository server 202. It also transmits instruction information to the backup program 204.

[0042] The output device 167 is, for example, a device such as a display or printer, and outputs (typically displays) various information derived by each program or stored in the sub-memory 163. The input device 164 is, for example, a device such as a keyboard or pointer device, and accepts user input.

[0043] The managed system 200 includes one or more business system servers 201 and one or more repository servers 202. The business system servers 201 and the repository servers 202 are connected via a network 170 so that they can communicate with each other.

[0044] The business system server 201 and the repository server 202 are, for example, general-purpose computers and include a processor 211, main memory 212, secondary memory 213, and a network interface 214. The processor 211 performs various processes according to programs stored in the main memory 212 and / or secondary memory 213. The main memory 212 is, for example, RAM and stores programs executed by the processor 211 and necessary information. The network interface 214 communicates with other devices via the network 170.

[0045] The main memory 212a of the business system server 201 stores the business system program 221 that executes business processes and the backup program 204 that performs backup and restore processes for data 203. The secondary memory 213a stores the data 203 processed by the business system program 221. The business system server 201 has a function to transmit configuration information, load information, etc., of the business system server 201 via the network 170 when requested, for example, from the backup management system 100.

[0046] The main memory 212 of the repository server 202 stores a repository processing program 222 that performs the processing and storage of backup data as a repository. The secondary memory 213b is a device that constitutes a backup repository 205 that stores the backup data 223 copied and saved by the backup program 204. The repository server 202 has a function to transmit configuration information, load information, etc. of the repository server 202 via the network 170 when requested by, for example, the backup management system 100.

[0047] <Business System Configuration Information 111> Figure 3 is a diagram showing the table configuration of the business system configuration information 111 according to the first embodiment. The business system configuration information 111 stores information about the configuration of the IT infrastructure that constitutes the business system server 201. The business system configuration information 111 includes fields for server ID 301, data ID 302, data capacity 303, maximum network bandwidth 304, maximum disk transfer bandwidth 305, maximum disk IOPS 306, and placement 307. There is one entry for each data 203 of the business system server 201. For example, in this embodiment, backup in volume units obtained by logically dividing the secondary storage device 213 will be described as an example. Therefore, there is one entry for each volume of the business system server 201. Note that the fields included in the entry are not limited to those described above. It may not include any of the fields described above, or it may include other fields.

[0048] Server ID 301 stores a value that uniquely identifies the business system server 201. Data ID 302 stores a value that uniquely identifies the data 203 of the business system server 201 that is the target of the backup. Data capacity 303 stores the value of the capacity of the data to be backed up. Maximum network bandwidth 304 stores the value of the maximum bandwidth of the network I / F 214a of the business system server 201 used during backup and restore processing. Maximum disk transfer bandwidth 305 stores the maximum transfer speed of the secondary storage device 213 that stores the data 203, or volumes that are logically divided therefrom. Maximum disk IOPS 306 stores the maximum transaction speed of the secondary storage device 213 that stores the data 203, or volumes that are logically divided therefrom. Placement 307 stores a value that uniquely identifies the region and zone in which the business system server 201 is located.

[0049] <Backup Repository Configuration Information 112> Figure 4 is a diagram showing the table configuration of the backup repository configuration information 112 according to the first embodiment. The backup repository configuration information 112 stores information about the configuration of the IT infrastructure that constitutes the repository server 202. The backup repository configuration information 112 includes fields for server ID 401, repository ID 402, repository capacity 403, free capacity 404, placement 405, maximum network bandwidth 406, maximum disk transfer bandwidth 407, and maximum disk IOPS 408. There is one entry for the backup repository 205 of the repository server 202. Note that the fields included in the entry are not limited to those described above. It may not include any of the fields described above, or it may include other fields.

[0050] Server ID 401 stores a value that uniquely identifies repository server 202. Repository ID 402 stores a value that uniquely identifies backup repository 205. Repository capacity 403 stores the maximum amount of data that can be stored in backup repository 205. Free space 404 stores the current free space of backup repository 205. Location 405 stores a value that uniquely identifies the region and zone where repository server 202 is located. Maximum network bandwidth 406 stores the maximum bandwidth of the network I / F 214b of repository server 202 used during backup and restore processing. Maximum disk transfer bandwidth 407 stores the maximum transfer speed of backup repository 205 that stores backup data 223. Maximum disk IOPS 408 stores the maximum transaction speed of backup repository 205 that stores backup data 223.

[0051] <Placement Rule 113> Figure 5 is a diagram showing the configuration of the table for the placement constraint rule 113 according to the first embodiment. The placement constraint rule 113 is information for managing the placement rules of the repository server where backup data 223 will be stored, for the purpose of backing up data 203 specified by the system administrator. The placement constraint rule 113 includes fields for the same zone 501, other zones 502, and other regions 503. There is one entry for each type of backup purpose. Note that the fields included in the entry are not limited to those mentioned above. It may not include any of the fields mentioned above, or it may include other fields.

[0052] Zone 501 stores a value that determines whether or not backup data can be placed in the same zone for the purpose of backup. Zone 502 stores a value that determines whether or not backup data can be placed in the same region but in a different zone for the purpose of backup. Region 503 stores a value that determines whether or not backup data can be placed in a different region for the purpose of backup. In this embodiment, each field stores the identifier "Y" if placement is possible and "N" if placement is not possible.

[0053] For example, entry 511 indicates that if the system administrator enters "zone failure" as the purpose of backing up data 203 (see Figure 6 for the input screen), the backup data cannot be stored in the repository server 202 in the same zone. On the other hand, it indicates that it can be stored in another zone in the same region, or in a repository server 202 in another region.

[0054] <Backup settings input screen> Figure 6 shows an example of a backup settings input screen according to the first embodiment. The input screen in Figure 6 shows an example of an implementation using a GUI (Graphical User Interface).

[0055] The backup setting input screen 11000 in the first embodiment is an input screen for a system administrator to input the information necessary to execute a backup job. The backup setting input screen has backup target server 601, backup target data 602, backup purpose 603, number of backups 604, target backup completion time 605, backup schedule 606, target restore time 607, and backup retention period 608. Backup target server 601 is an area that defines the business system server 201 whose data will be backed up. Backup target data 602 is an area that defines the data 203 of the business system server 201 that will be backed up. Backup purpose 603 is an area that defines the purpose of the backup data. The value defined in backup purpose 603 is equivalent to the value stored in entry 511 of the placement constraint rule 113, and multiple values ​​may be selected. Number of backups 604 is an area that defines the number of backup data when storing multiple backup data at the same time to improve the availability of backup data. Target backup completion time 605 is an area that defines the target value of the time from the start to the end of the backup job. Backup schedule 606 is an area that defines the frequency and time at which backup jobs are executed. Target restore time 607 is an area that defines the target value of the time from the start to the end of the restore. The target restore time may be defined for each value specified in the backup purpose 603, or one may be defined for each backup job. Backup retention period 608 defines the period for which stored backup data will continue to be stored. In this embodiment, it is defined by the number of generations (how many to save in reverse chronological order from the most recent backup data), but it may also be specified as a period such as "3 months", or one of these may be selected.

[0056] For example, the backup job information input screen in Figure 6 indicates that the backup job targets the data / dev / sda on server Srv1, the purpose of the backup is to address logical and zone failures, two backup data sets are stored when a backup job is executed, the target backup completion time is 200 minutes, the backup job is executed daily at 10 PM, the target restore processing time is 200 minutes, and backup data is stored up to 7 generations prior to the most recent data. In this way, the backup settings input screen is used to input backup settings information, which is information related to the backup settings.

[0057] Next, we will explain in detail the processing operations in the backup management system 100.

[0058] <Backup Placement Calculation Program> The backup placement calculation program 140 is a process performed by the processor 161 of the management computer 160, and it constrains the repository servers 202 that can store the backup target data specified by the system administrator, and calculates based on priority.

[0059] Figure 7 is a flowchart of the backup placement calculation process according to the first embodiment. The backup placement calculation program 140 starts processing, for example, when it detects that a new backup job setting has been registered via the backup setting input screen 11000.

[0060] In step S701, the backup placement calculation program 140 (more precisely, the processor 161 that executes the backup placement calculation program 140) receives backup configuration information. For example, the backup configuration information may be the values ​​entered on the backup information input screen 11000.

[0061] In step S702, the backup placement calculation program 140 calculates combinations of backup data placements based on placement constraint rules 113 from the received backup purpose 703 and backup number 604 values. For example, as shown in Figure 6, if the backup purpose is "logical failure" and "zone failure" and the number of backups is "2", then placement rules 113 determine that the placements that satisfy both "logical failure" and "zone failure" are other zones and other regions. Three combinations are derived as placements that satisfy these conditions for the two backup data: one where the backup data is stored in the two repository servers 202 in zone 207ab, one where the backup data is stored in the two repository servers 202 in zone 207bc, and one where the backup data is stored in the respective repository servers 202 in zones 207ab and 207bc. Alternatively, although the availability of backup data will decrease, the following configurations may be derived as combinations that satisfy the placement constraint rule 113, such as the configuration in which each backup data is stored in the respective repository server 202 of zone 207aa and zone 207ab, and the configuration in which each backup data is stored in the respective repository server 202 of zone 207aa and zone 207bc.

[0062] In step S703, the backup placement calculation program 140 stores the list of placement combinations derived in step S703. For example, the list of placement combinations may be stored in the main memory 162.

[0063] In step S704, the backup placement calculation program 140 retrieves entries from the business system configuration information 111 based on the server ID and data ID specified on the backup target server 601.

[0064] In step S705, the backup placement calculation program 140 processes the combination of placements from step S703 and repeats the processing of loop 1 (steps S707 to S708).

[0065] In step S706, the backup placement calculation program 140 processes the backup repository 205 included in the given placement combination and repeats the processing of loop 2 (steps S707 to S708).

[0066] In step S707, the backup placement calculation program 140 calls the backup processing performance calculation program 141 and uses the configuration information of the data to be backed up to predict the backup completion time for the data to be backed up to the backup repository 205. The backup processing performance calculation program 141 learns correlations such as those shown in graphs 901, 902, and 903 in Figures 9A, 9B, and 9C, and performs a process to predict the backup completion time for each placement from the disk transfer bandwidth 305 of the business system server 201, the maximum disk IOPS, and the data capacity 303 of the data 203. Graph 901 in Figure 9A shows the correlation when the business system server 201 and the repository server 202 are in the same zone, graph 902 in Figure 9B shows the correlation when the business system server 201 and the repository server 202 are in the same region but in different zones, and graph 903 in Figure 9C shows the correlation when the business system server 201 and the repository server 202 are in region A and region B, respectively. If the network's bandwidth and characteristics differ from zone to zone, the correlation can be learned for each combination of zones.

[0067] The backup completion time prediction in this embodiment is based on the assumption that the disk IOPS, disk transfer bandwidth, or inter-region network transfer bandwidth of the business system server 201 will be bottlenecks, and these will vary depending on the characteristics of the backup program 204 and the IT infrastructure that constitutes the managed system 200. For example, the maximum network bandwidth 304 of the business system server 201, processor performance, and the number of processors may be used to learn the correlation including parameters.

[0068] Furthermore, in this embodiment, the prediction calculation is performed assuming that the business system server 201 is not under any load other than backup processing. However, it is also possible to predict the maximum disk transfer bandwidth and maximum disk IOPS by considering the load on the business system server 201 due to the business system program 221 and reducing them by a certain amount.

[0069] In this embodiment, the backup completion time is predicted on the assumption that the performance of the repository server 202 is always higher than that of the business system server 201. However, to account for cases where the performance of the repository server 202 becomes a bottleneck, the performance of the repository server 202's disk and network interface may be included as parameters to learn the correlation.

[0070] Furthermore, while this embodiment assumes a full backup that backs up all of the data 203, the processing time for differential backups or incremental backups may also be taken into consideration during the prediction.

[0071] Furthermore, in this embodiment, it is assumed that data is always transferred from the business system server 201 when storing two or more backup data sets. However, there are also backup programs 204 that store the first backup data in the repository server 202, and then copy the backup data stored in the repository server 202 to another repository server 202. In this case, a process for predicting the backup completion time, taking into account the copying between repository servers 202, may be performed.

[0072] In step S708, the backup placement calculation program 140 calls the restore processing performance calculation program 142 and uses the configuration information of the data to be backed up to predict the restore processing time for each combination of the backup repository 205 and the purpose of the restore (the purpose of the backup). The restore processing performance calculation program 142 learns correlations such as those shown in graphs 1001, 1002, and 1003 in Figures 10A, 10B, and 10C, and uses the disk transfer bandwidth 305 of the business system server 201, the maximum disk IOPS, and the data capacity 303 of the data 203 to predict the restore processing time for each combination of the placement of the backup repository 205 and the purpose of the restore (the purpose of the backup). Graph 1001 in Figure 10A shows the correlation when the business system server 201 and repository server 202, which are the restore destinations, are in the same zone; Graph 1002 in Figure 10B shows the correlation when the business system server 201 and repository server 202, which are the restore destinations, are in the same region but in different zones; and Graph 1003 in Figure 10C shows the correlation when the business system server 201 and repository server 202, which are the restore destinations, are in region A and region B, respectively. The method for learning these correlations differs depending on the characteristics of the backup program 204 and the IT infrastructure that constitutes the managed system 200, similar to the backup processing performance calculation program 141. For example, the correlation may be learned by including parameters such as the maximum network bandwidth 304 of the business system server 201, processor performance, and the number of processors. Assuming that the performance of the repository server 202 becomes a bottleneck, the correlation may be learned by including the performance of the repository server 202's disk and network interface as parameters. Furthermore, given that frequent differential / incremental backups during restoration consume a significant amount of processor resources, it may be beneficial to include the frequency of full backups and differential / incremental backups as parameters to learn their correlation.

[0073] Furthermore, in this embodiment, for example, when a new business system server 201 is constructed as the destination for restoration in the case of a zone failure, it is assumed that its performance is equivalent to that of the original business system server 201, but this is not limited to this. Also, some backup programs can perform backups on a volume basis and restores on a file basis. In this case, the capacity of the data to be restored may be smaller than the backup data, but in this embodiment, when predicting the restore processing time, it is acceptable to assume that the capacity of the data to be restored is equal to the capacity of the backup data in order to predict the longest possible time.

[0074] In step S709, the backup placement calculation program 140 extracts and stores from the combinations stored in step S703 the combinations for which the predicted backup completion time and predicted restore processing time of each placement combination derived in steps S707 and S708 satisfy the target backup completion time 605 and the target restore time 607.

[0075] In step S710, the backup placement calculation program 140 calls the additional resource calculation process to determine whether additional resources from the repository server 202 are necessary for each combination of backup data placement in step S709, and calculates the amount of resources and costs if necessary. The additional resource calculation process will be described in detail later.

[0076] In step S711, the backup placement calculation program 140 outputs a placement plan that includes combinations of backup data placements and information on additional resources. The displayed backup data placement combinations may be sorted in ascending order of additional cost. Alternatively, they may be sorted in order of availability. Order of availability may be, for example, in descending order of the number of backup repositories used. Order of availability may be in descending order of the number of zones in which the backup data is stored by the backup job. Order of availability may be in descending order of the number of regions in which the backup data is stored by the backup job. Alternatively, points may be assigned to the number of backup repositories, zones, and regions, and the combinations may be sorted in descending order of the highest score. The combinations may be sorted in descending order of the difference between the predicted backup completion time and the target backup completion time value 605. Alternatively, they may be sorted in descending order of the difference between the predicted restore time and the target restore time value 607. The system administrator may select the criteria for sorting the displayed backup data placement combinations. Alternatively, they may be sorted in evaluation order by combining evaluations of additional cost, availability, predicted backup completion time, and predicted restore time.

[0077] <Additional resource calculation process 800> The additional resource calculation process calculates the amount of additional resources and their costs required to implement each combination of backup data placements.

[0078] Figure 8 is a flowchart of the additional resource calculation process 800 according to the first embodiment. The additional resource calculation process 800 is called by the backup placement calculation program 140 in step S710, and the process begins.

[0079] In step S801, the backup placement calculation program 140 processes the combinations of placements extracted in step S707 and repeats the processing of loop 1 (steps S802 to S808).

[0080] In step S802, the backup placement calculation program 140 processes the backup repository 205 for the given placement combination and repeats the processing of loop 2 (steps S803 to S806).

[0081] In step S803, the backup placement calculation program 140 calls the backup processing performance calculation program 141 and the restore processing performance calculation program 142 to predict the load on the components that make up the data transfer path when backing up and restoring the backup target data 203 of the backup target server 201, and calculates this load as the "required amount of resources".

[0082] The load on the components that make up the data transfer path refers to, for example, the load (IOPS and transfer bandwidth) of the disks that make up the backup repository 205 when storing backup data. The load during restore execution can be calculated for each purpose (backup purpose) because the data transfer path differs for each purpose.

[0083] The backup processing performance calculation program 141 learns correlations such as those shown in graphs 1101 to 1103 and 1111 to 1113 in Figures 11A to 11F, and performs a process to predict the disk IOPS and transfer bandwidth load of the repository server 202 in each configuration, based on the disk transfer bandwidth 305, maximum disk IOPS 306, and data capacity 303 of the business system server 201. Graphs 1101 in Figure 11A and 1111 in Figure 11D show the correlation when the business system server 201 and the repository server 202 are in the same zone, graphs 1102 in Figure 11B and 1112 in Figure 11E show the correlation when the business system server 201 and the repository server 202 are in the same region but in different zones, and graphs 1103 in Figure 11C and 1113 in Figure 11F show the correlation when the business system server 201 and the repository server 202 are in region A and region B, respectively.

[0084] In this embodiment, only the disk of the repository server 202 is listed as the data transfer path, but the load of other components such as the processor of the repository server and the network bandwidth of the backup target server may also be included in the calculation.

[0085] Note that graphs 1101-1103 and 1111-1113 in Figures 11A-11F represent the load when the backup time is as fast as possible. Therefore, for example, if the fastest backup time is less than the target backup completion time of 605 entered in Figure 6 for a given backup data capacity, the minimum load required to achieve the target backup completion time may be considered the "required resource amount". For example, if the backup time for a backup data capacity of 100GB is 30 minutes in the graph in Figure 9A, the load on the repository server for a backup data capacity of 100GB is 1000 IOPS / second in the graph in Figure 11A, and the entered target backup completion time of 605 is 60 minutes, then since the fastest backup time is half of the target backup time, the required IOPS for the repository server may also be calculated as half, or 500 / second. The relationship between the fastest backup time, the target backup completion time, and the "required resource amount" may be calculated using the simple calculation described above, or it may be calculated using another formula that expresses their correlation.

[0086] In addition to data transfer performance, the disk capacity required to store backup data may also be calculated as a load. The required disk capacity may be calculated, for example, from the backup frequency specified in backup schedule 606 and the backup retention period 608. Alternatively, the required disk capacity may be calculated considering the frequency of full backups and incremental / differential backups, as well as the data compression ratio.

[0087] Furthermore, similar to the correlations in Figures 9A, 9B, and 9C, the correlations learned by the backup processing performance calculation program 141 may be learned for each combination of zones, and the correlation parameters may include other parameters.

[0088] The restore processing performance calculation program 142 learns correlations such as those shown in graphs 1201-1203 and 1211-1213 in Figures 12A-12F, and uses the disk transfer bandwidth 305, maximum disk IOPS, and data capacity 303 of the data 203 of the restore destination business system server 201 to predict the disk IOPS and transfer bandwidth load of the repository server 202 for each combination of backup data placement and restore purpose (backup purpose). Graphs 1201 in Figure 12A and 1211 in Figure 12D show the correlation when the restore destination business system server 201 and repository server 202 are in the same zone. Graphs 1202 in Figure 12B and 1212 in Figure 12E show the correlation when the restore destination business system server 201 and repository server 202 are in the same region but in different zones. Graphs 1203 in Figure 12C and 1213 in Figure 12F show the correlation when the restore destination business system server 201 and repository server 202 are in region A and region B, respectively.

[0089] In this embodiment, only the disk of the repository server 202 is listed as the data transfer path, but the load of other components such as the processor of the repository server and the network bandwidth of the backup target server may also be included in the calculation.

[0090] Furthermore, similar to the correlations in Figures 10A, 10B, and 10C, the correlations learned by the backup processing performance calculation program 141 may be learned for each combination of zones, and the correlation parameters may include other parameters.

[0091] In step S804, the backup placement calculation program 140 searches for backup repository configuration information 112 and determines whether a repository server 202 has already been established for the location of the backup repository 205. If the result of this determination is true (S804:YES), the backup placement calculation program 140 proceeds to step S805; if the result of this determination is false (S804:NO), the process proceeds to step S806.

[0092] In step S805, the backup placement calculation program 140 determines whether the maximum performance of each component of the data transfer path of the backup target server 601 (in this embodiment, the maximum disk transfer bandwidth 407 and the maximum disk IOPS 408) for the backup repository 205 identified in the search in step S804 satisfies the "required resource amount" calculated in step S803. If the result of this determination is true (S805:YES), the backup placement calculation program 140 proceeds to step S806; if the result of this determination is false (S805:NO), the process proceeds to step S803.

[0093] In step S806, the backup placement calculation program 140 calculates the additional resource amount as the difference between the "required resource amount" calculated in step S803 and the maximum performance of the already constructed backup repository 205. If the result of the judgment in step S804 is false, the repository server 202, which has the "required resource amount," becomes the additional resource amount.

[0094] In this embodiment, the calculation of "additional resources" is based on the disk IOPS, disk transfer bandwidth, and disk capacity of the repository server 202, but it may also include the number of processors, main memory capacity, network interface bandwidth, etc. Furthermore, if a proxy server or the like is provided for managing the backup process and serves as the transfer path for backup data, the proxy server and its resources may also be included in the calculation of "required resources." The scope of the additional resources calculation will vary depending on the characteristics and configuration of the backup program 204, and, if the managed system 200 is a public cloud, on the resources that can be added in the public cloud.

[0095] In step S807, the backup placement calculation program 140 stores all the placement combinations and the additional resources calculated in step S806. If step S806 is never executed, it stores the result as "No additional resources".

[0096] In step S808, the backup placement calculation program 140 stores the additional cost for the additional resources calculated in step 806, along with the combination of placements stored in step S807. For example, if the additional resource is a disk with a transfer bandwidth of 100 MB / s, and the monthly cost for a transfer bandwidth of 100 MB / s is 2000 yen, then the additional cost will be 2000 yen. In other words, the backup placement calculation program 140 calculates the additional cost for resources that need to be added in the above combination of placements stored in step S807, calculated using the business system configuration information 111 and the backup repository configuration information 112, based on the correlation of costs for those resources, that is, the relationship determined according to those resources.

[0097] <Layout Selection Screen 12000> Figure 13 shows an example of a layout selection screen according to the first embodiment. The layout selection screen 12000 is output in step S711 by the backup layout calculation program 140. The output screen shown in Figure 13 is an example of a GUI implementation.

[0098] The deployment plan selection screen 12000 has a deployment plan 1300 that displays combinations of deployments for backup data. The deployment plan 1300 may display one or more of the deployment combinations stored in step S808. The deployment plan display area 1300 also has a backup destination 1301, additional costs 1302, additional resources 1303, predicted backup completion time 1304, predicted restore time 1305, backup frequency 1306, and backup data deployment 1307. The backup destination 1301 displays the combination of backup data deployments stored in step S808. The additional costs 1302 displays the additional costs stored in step S808. The additional resources 1303 displays the additional resources stored in step S807. The predicted backup completion time 1304 displays the predicted backup processing time calculated in step S707. If there are multiple repository servers, the maximum predicted backup completion time for each repository server 202 may be displayed. The predicted restore time 1305 displays the predicted restore processing time for each restore purpose calculated in step S708. If there are multiple repository servers, the maximum or minimum predicted restore time for each repository server 202 may be displayed. The backup frequency 1306 may display a value calculated based on the backup frequency entered in backup schedule 606, for example. The backup data placement 1307 displays the backup data placement (zone, region, repository server) in the combination of backup data placements stored in step S808, and the number of backup data in each placement (the number written in the circle in backup data placement 1307).

[0099] One of the 1300 deployment options will be selected by the system administrator.

[0100] The deployment option selection screen 12000 has a job registration button 1311. When the system administrator selects one of the deployment options 1300 and presses the job registration button 1311, the backup configuration change program 143 and the backup job registration program 144 are called.

[0101] Based on the selected layout plan 1300 and the input values ​​on the backup settings input screen 11000, the backup job information is registered in the backup job information 121.

[0102] <Backup Job Information> Figure 14 is a diagram showing the configuration of the backup job information table 121 according to the first embodiment. Backup rejob information 121 stores information about backup jobs registered by the backup job registration program 141. Backup job information 121 includes fields for job ID 1401, source server ID 1402, source data ID 1403, backup repository 1404, schedule 1405, predicted backup completion time 1406, backup purpose 1407, and predicted restore time 1408. There is one entry for each backup job. Note that the fields included in an entry are not limited to those described above. It may not include any of the fields described above, or it may include other fields.

[0103] Job ID 1401 stores a value that uniquely identifies the backup job. Source 1402 stores a value that uniquely identifies the business system server 201 based on the value entered in the backup target server 601 on the backup settings input screen 11000. Source data ID 1403 stores a value that uniquely identifies the data 203 of the business system server 201 based on the value entered in the backup target data 602 on the backup settings input screen 11000. Backup repository 1404 stores a value that uniquely identifies the backup repository 205 indicated by the backup destination 1301 of the deployment plan 1300 selected on the deployment plan selection screen 12000. Schedule 1405 stores a value representing the start timing of the backup job execution based on the value entered in the backup schedule 606 on the backup settings input screen 11000. Predicted backup completion time 1406 stores the predicted backup processing time for each backup data deployment calculated in step S707. Backup purpose 1407 stores a value that identifies the purpose of the backup data stored in the repository server indicated by the backup repository 1404, based on the value entered in backup purpose 603 on the backup setting input screen 11000 and the entries of the placement constraint rule 113 obtained when deriving the placement plan. Predicted restore time 1408 stores the predicted restore processing time for each backup data placement and backup purpose (restore purpose) calculated in step S708.

[0104] Figures 15A to 15C are flowcharts of the backup configuration change program 143, backup job registration program 144, and backup job execution program 145, which represent a series of processes from the system administrator selecting the deployment plan 1300 on the deployment plan selection screen 12000, pressing the job registration button 1311, to registering and executing the backup job.

[0105] In Figure 15A, the backup configuration change program 143 starts processing when the job registration button 1311 is pressed on the layout selection screen 12000.

[0106] In step S1501, the backup configuration change program 143 receives information about the deployment plan 1300 selected by the system administrator.

[0107] In step S1502, the backup configuration change program 143 determines whether the received deployment proposal 1300 requires a configuration change or addition of a repository server 202. If the result of this determination is true (S1502: YES), the backup configuration change program 143 proceeds to step S1503; if the result of this determination is false (S1502: NO), the process proceeds to step S1504.

[0108] In step S1503, the backup configuration change program 143 performs a configuration change or adds a repository server 202 based on the information in the deployment plan 1300.

[0109] In step S1504, the backup configuration change program 143 calls the backup job registration program 144.

[0110] In Figure 15B, the backup job registration program 144 is called by the backup configuration change program 143, and processing begins. Alternatively, processing may also begin when the job registration button 1311 is pressed on the layout selection screen 12000.

[0111] In step S1511, the backup job registration program 144 receives information on the deployment plan 1300 selected by the system administrator and information entered on the backup settings screen 11000 by the system administrator.

[0112] In step S1512, the backup job registration program 144 adds some or all of the information from the received deployment plan 1300 and the input information from the backup settings screen 11000 as entries in the backup job information 121.

[0113] In Figure 15C, the backup job execution program 145 periodically checks the backup job information 121, and when the time corresponding to the schedule 1405 arrives, processing begins.

[0114] In step S1521, the backup job execution program 145 receives an entry for backup job information.

[0115] In step S1522, the backup job execution program 145 starts the backup program 204 using the backup job information entry as a setting value and executes the backup process.

[0116] In step S1523, the backup job execution program 145 stores information about the backup data created by the executed backup job as an entry in the backup data information 122.

[0117] <Backup data information> Figure 16 is a diagram showing the configuration of the backup data information table 122 according to the first embodiment. Backup data information 122 stores information about the backup data registered in step S1523 by the backup job execution program 145. Backup data information 122 includes fields for backup data ID 1601, source server ID 1602, source data ID 1603, backup repository 1604, backup purpose 1605, predicted restore time 1606, and backup time 1607. There is one entry for the backup data created by the execution of the backup job. Note that the fields included in the entry are not limited to those described above. It may not include any of the fields described above, or it may include other fields.

[0118] Backup data ID 1601 stores a value that uniquely identifies the backup data. Source server ID 1602 stores the value of source server ID 1402 of the backup job executed by backup job execution program 145. Source data ID 1603 stores the value of source data ID 1403 of the backup job executed by backup job execution program 145. Backup repository 1604 stores the value of backup repository 1404 of the backup job executed by backup job execution program 145. Backup purpose 1605 stores the value of backup purpose 1407 of the backup job executed by backup job execution program 145. Predicted restore time 1606 stores the value of predicted restore time 1408 of the backup job executed by backup job execution program 145. Backup time 1607 stores the time when the backup job executed by backup job execution program 145 was completed.

[0119] According to the first embodiment, the backup management system 100 can construct and configure a repository server configuration and backup jobs that are cost-effective for backups and that meet backup requirements specified by the system administrator (such as the purpose of backup, target backup completion time, target restore processing time, and backup data availability).

[0120] Thus, in the first embodiment, as explained using S701 to S709 in Figure 7, etc., in a backup management system 100 that manages backups and restores of managed items by a management computer 160, which is a computer having a processor and memory, the processor has business system configuration information 111, which is information about the configuration of the business system server 201 included in the managed items, backup repository configuration information 112, which is information about the configuration of the repository server that stores the backup data, input backup setting information (for example, input information on the backup setting input screen shown in Figure 6), and backups according to the purpose of the backup. Based on the placement constraint rule 113 for determining the placement of the updater, combinations of backup repository placements that satisfy the placement constraint rule are calculated, a predetermined backup processing time (e.g., processing time based on the training data shown in Figure 9) is predicted for the backup repository placement, a predetermined restore processing time (e.g., processing time based on the training data shown in Figure 10) is predicted for the backup repository placement and the purpose of restore, and among the above combinations of backup repository placements, the combination in which the backup processing time and the restore processing time satisfy the target backup completion time and target restore processing time included in the input backup configuration information is derived. This makes it possible to achieve a cost-effective data protection configuration and settings in the data backup system.

[0121] In other words, when managing a backup system comprising a server to be managed, a backup program that manages and executes backup and restore processes for that server, and a repository server that stores backup data, it becomes possible to search for a backup data storage location that satisfies backup requirements (e.g., backup purpose, backup job execution time, restore processing time, and backup data availability) for the IT system to be backed up. Furthermore, it becomes possible to search for a backup data storage location that satisfies the requirements and is cost-effective, and if no backup data storage location that satisfies the requirements is found, the configuration of the backup system can be changed.

[0122] Furthermore, as explained using S711 in Figure 7 and Figure 13, the processor displays a list of possible backup repository placements (for example, the placement selection screen 12000). The processor also sorts and displays the backup repository placements in ascending order of the additional costs required, in descending order of availability, or in order of evaluation of the combination thereof. Therefore, users of this system can easily confirm and select a backup data storage location that meets their requirements and is cost-effective.

[0123] Furthermore, as explained using Figure 8, the processor calculates and displays the resources that need to be added from the combinations of backup repository placements, based on the business system configuration information 111 and the backup repository configuration information 112. This allows users of the system to quickly identify the resources that need to be added.

[0124] Furthermore, as explained in Figure 8, S808, etc., the processor calculates and displays the additional costs required based on the correlation of costs for additional resources among the combinations of the business system configuration information 111, the backup repository configuration information 112, and the placement of each backup repository. This allows users of the system to quickly grasp the costs for additional resources that satisfy the correlation.

[0125] Furthermore, as explained in Figures 15B, 15C, etc., the processor creates backup job information 121, which is the configuration information for the backup job, based on the selected combination of backup repository placements, and executes the backup job. This enables the data to be automatically backed up to the backup destination configured from the selected combination of placements.

[0126] Furthermore, as explained in Figure 15A, etc., the processor modifies the managed configuration based on the selected combination of backup repository placements and the additional resources required. This allows for the modification of the protection configuration and settings to a cost-effective backup destination, thereby reducing the cost burden on users of this system.

[0127] ≪Second Embodiment≫ Next, a backup management system according to the second embodiment will be described. In the following description, the differences from the first embodiment will be the main focus, and the same reference numerals will be used for equivalent components, programs with equivalent functions, and tables with equivalent items, and their descriptions will be omitted or simplified.

[0128] In the second embodiment, the difference from the first embodiment is that other backup jobs are already registered before the system administrator configures the backup job on the backup settings screen 11000. If other backup jobs are executed at the same time as the newly configured backup job, and some or all of the data transfer paths overlap, the backup processing performance will decrease because the resources of the components of the data transfer paths will be consumed by each other. Therefore, it is necessary to design the backup repository configuration taking into account the resources consumed by other backup jobs.

[0129] In the second embodiment, the backup placement calculation program 140 calculates additional resources to be added to the candidate backup data placements derived by other backup jobs, including resource consumption of components of the data transfer path. The management computer 160 according to the second embodiment stores a program that executes an additional resource calculation process 1700 instead of the additional resource calculation process 800 in Figure 8.

[0130] <Additional resource calculation process> Figure 17 is a flowchart of the additional resource calculation process according to the second embodiment. The additional resource calculation process according to the second embodiment is called by the backup placement calculation program 140 and starts processing, similar to the first embodiment.

[0131] Steps S801 to S803 in Figure 17 execute the same processes as steps S801 to S803 shown in Figure 8.

[0132] In step S1701, the backup placement calculation program 140 searches for backup repository configuration information 112 and determines whether a repository server 202 has been established at the location of the backup repository 205. If the result of this determination is true (S1701:YES), the backup placement calculation program 140 proceeds to step S1702; if the result of this determination is false (S1701:NO), the process proceeds to step S1708.

[0133] In step S1702, the backup placement calculation program 140 calculates the time period during which backup processing will be performed based on the backup schedule 606 of the new backup job on the backup setting input screen 600 and the predicted backup processing time calculated in step S707. Based on the schedule 1405 and predicted backup completion time of the backup job information 121, it retrieves all entries in the backup job information 121 whose backup processing execution time overlaps with that of the new backup job. Furthermore, it extracts backup jobs whose backup data transfer paths overlap (in this embodiment, when the repository server 202 that stores the backup data is the same). In this embodiment, the example given is a configuration in which the repository server 202 has one network interface or backup repository, but if there are multiple, they may be processed as different transfer paths.

[0134] In step S1703, the backup placement calculation program 140 obtains the maximum performance of the components of the backup data transfer path between the backup target server 601 and the backup repository from the backup repository configuration information 112 in Figure 4. In this embodiment, the resources that may become bottlenecks in the data transfer path are the disk IOPS and disk transfer bandwidth of the backup repository 205. Therefore, in this embodiment, in step S1703, the backup repository configuration information 112 is searched for the backup repository and the values ​​of maximum disk transfer bandwidth 407 and maximum disk IOPS 408 are obtained. In this embodiment, only the disk of the repository server 202 is listed as the data transfer path, but the maximum performance of other components such as the processor of the repository server and the network bandwidth of the backup target server may be included. In addition to data transfer performance, the free space 404 of the repository may be included in order to calculate the additional disk space required to store the backup data.

[0135] In step S1704, the backup placement calculation program 140 calculates the load on the components of the backup data transfer path between the backup target server 601 and the backup repository for that placement. The load on the components is calculated from the load on the backup jobs extracted in step S1702. The load on the backup jobs may be calculated from the values ​​of the business system load information 131 and the backup repository load information 132 based on the load of backup jobs executed in the past, or the backup processing performance calculation program 141 may calculate it in the same way as in step S803 using the correlation shown in Figures 11A to 11F.

[0136] In step S1705, the backup placement calculation program 140 determines whether the maximum performance of each component of the data transfer path identified in the search in step S1703 (in this embodiment, the maximum disk transfer bandwidth 407 and the maximum disk IOPS 408) satisfies the "required resource amount" calculated in step S803 and the load by each backup job calculated in step S1704. If the result of this determination is true (S1705: YES), the backup placement calculation program 140 proceeds to step S1706; if the result of this determination is false (S1705: NO), the process proceeds to step S803.

[0137] In step S1706, the backup placement calculation program 140 calculates the additional resource amount based on the maximum performance of each component of the data transfer path identified in the search in step S1703, the "required resource amount" calculated in step S803, and the load of each backup job calculated in step S1704. If the result of the determination in step S1701 is false, the repository server 202, which has the "required resource amount," becomes the additional resource amount.

[0138] Steps S801 to S803 in Figure 17 perform the same processing as steps S807 to S808 shown in Figure 8.

[0139] As described above, according to the second embodiment, as explained in Figure 17, for example, the processor of the management computer 160, which is a computer having a processor and memory, calculates the load on the data transfer path in backup and restore in the combination of backup repository placements from the business system configuration information 111, the backup repository configuration information 112, the combination of backup repository placements, and the backup job information 121, which is the setting information of previously registered backup jobs, and calculates and displays the additional resources that need to be added. This makes it possible to calculate the amount of additional resources considering the resources consumed by other backup jobs when other backup jobs are executed at the same time as a newly set backup job and some or all of the data transfer paths overlap.

[0140] ≪Third Embodiment≫ Next, the backup management system 100 according to the third embodiment will be described. In the following description, the differences from the first and second embodiments will be the main focus, and the same reference numerals will be used for equivalent components, programs with equivalent functions, and tables with equivalent items, and their descriptions will be omitted or simplified.

[0141] The first and second embodiments described methods for setting up backup jobs when a business system server has already been established. However, when building an IT system, the backup system may be designed before the business system server is actually built. Therefore, it is necessary to determine the configuration of the backup system from the configuration information of the expected business system server, even when the business system server does not actually exist.

[0142] Therefore, in the backup management system 100 according to the third embodiment, an example will be described in which the configuration of the backup system is determined based on information of a business system server that does not yet exist, provided by the system administrator.

[0143] In the third embodiment, the management computer 160 displays the backup setting input screen 11001 instead of the backup setting input screen 11000.

[0144] <Backup settings input screen> Figure 18 shows an example of the backup settings input screen 11001 according to the third embodiment. The input screen shown in Figure 18 is an example of a GUI implementation. Parts similar to those in the backup settings input screen 11000 according to the first embodiment are denoted by the same reference numerals.

[0145] The backup settings input screen 11001 in the third embodiment is an input screen for the system administrator to input the information necessary to build a backup system for the business system server to be constructed. In particular, the main purpose of this embodiment is the design and construction of the repository server 202.

[0146] The backup setting input screen 11001 of the third embodiment has a total data capacity 1801, a number of servers to be backed up 1802, assumed business system disk IOPS 1803, and assumed business system disk transfer bandwidth 1804. It also has a backup purpose 603, a number of backups 604, a target backup completion time 605, a backup schedule 606, a target restore time 607, and a backup retention period 608, which are the same as those of the backup setting input screen 11000 in Figure 6.

[0147] The total data capacity 1801 is the area that defines the estimated total value of data to be backed up across the entire newly constructed managed system 200. The number of servers to be backed up 1802 is the area that defines the number of business system servers to be backed up. The assumed business system disk IOPS 1803 is the area that defines the disk IOPS of the business system servers to be built in the newly constructed managed system 200. The assumed business system disk transfer bandwidth 1804 is the area that defines the disk transfer bandwidth of the business system servers to be built in the newly constructed managed system 200. In this embodiment, even if there are multiple business system servers, the total data capacity 1801, assumed business system disk IOPS 1803, and assumed business system disk transfer bandwidth 1804 are all considered to be the same and only one value is defined for each, but they may be set for each business system server. The values ​​to be defined may be entered by the system administrator, or values ​​automatically calculated from the performance of other systems in the past may be entered. In this embodiment, only disk IOPS and disk transfer bandwidth are targeted for input, but resources that may become bottlenecks may also be targeted. For example, the transfer bandwidth or the number of processors of the network interface could be the target.

[0148] In the third embodiment, the backup placement calculation program 140 calculates the data backup target server and data configuration information from the information defined on the backup setting input screen 11001, rather than obtaining the data backup target server and data configuration information from the business system configuration information 111 in step S704. For example, instead of the data capacity 303 in the business system configuration information 111, the value obtained by dividing the total data capacity 1801 by the number of backup target servers 1802 is used. Instead of the value of maximum disk transfer bandwidth 305, the value of assumed business system IOPS 1804 is used. Instead of maximum disk IOPS 306, the value of assumed business system server IOPS 1803 is used. The placement 307 uses random or fixed values.

[0149] In the additional resource calculation process in the third embodiment, the determination in step S804 is always false (S804:NO), and in step S806, the amount of additional resources is not stored and output as the amount of resources required during the initial system construction.

[0150] As described above, according to the third embodiment, as explained in Figure 18, etc., the processor of the management computer 160, which is a computer having a processor and memory, generates the business system configuration information based on the input backup configuration information, which includes the configuration information before the construction of the business system server (for example, total data capacity 1801, number of servers to be backed up 1802, assumed business system disk IOPS 1803, assumed business system disk transfer bandwidth 1804), and derives the combination of backup repository placements in which the backup processing time and the restore processing time satisfy the target backup completion time and target restore processing time included in the input backup configuration information. This makes it possible to design and estimate the backup system before the construction of the managed system 200.

[0151] ≪Fourth Embodiment≫ Next, the backup management system 100 according to the fourth embodiment will be described. In the following description, the differences from the first, second, and third embodiments will be the main focus, and the same reference numerals will be used for equivalent components, programs with equivalent functions, and tables with equivalent items, and their descriptions will be omitted or simplified.

[0152] In the fourth embodiment, an example is described in which a restore process is performed after designing the backup system and configuring backup jobs in the first, second, and third embodiments.

[0153] <Restore execution screen 13000a> Figure 19 shows an example of the restore execution screen 13000a according to the fourth embodiment. The input screen shown in Figure 19 is an example of a GUI implementation.

[0154] The restore execution screen 13000a in the fourth embodiment is an input screen for the system administrator to input the information necessary to perform a restore process using backup data stored in the repository server 202. The system administrator may perform a restore process of backup data related to the data 203 of the business system server 201 in order to start a replacement business system server 201 in the event of a failure in the business system server 201 or related IT infrastructure and software. Alternatively, the system administrator may perform a restore process of backup data related to the data 203 in order to restore the data 203 of the business system server 201 to a certain point in time if an abnormality occurs in the data 203 of the business system server 201.

[0155] The restore execution screen 13000a includes the server to be restored 1901, the data to be restored 1902, the purpose of the restore 1903, and a button 1904.

[0156] The area 1901 defines the server to be restored, which is the business system server 201 to be restored. The area 1902 defines the data 203 of the business system server 201 to be restored. In this embodiment, the units of backup data and restore data are unified to volume units obtained by logically dividing the secondary storage device 213. However, depending on the function of the backup program 204, it may be possible to back up in volume units and restore in file units contained in the volume. In this case, a value to identify the file may be defined in the data to be restored 1902. In this case, the backup management system 100 is assumed to remember which volume the file is stored in. The restore purpose 1903 defines the purpose of the restore process to be executed. The value defined in the restore purpose 1903 is selected to be equivalent to the value defined in the backup purpose 603 set in the backup setting screen 11000 of the first embodiment. Button 1904 is an interface that indicates that input on the restore execution screen 13000a has been completed and sends the input value to the restore execution program 150.

[0157] <Restore execution program> The restore execution program 150 is a process performed by the processor 161 of the management computer 160. It searches for available backup data according to the purpose of the restore specified by the system administrator and executes the restore process according to the system administrator's input.

[0158] Figure 20 is a flowchart of the restore process according to the fourth embodiment. The restore process execution program 150 starts processing when, for example, it detects that configuration information for restore execution has been entered via the restore execution screen 13000a and that button 1904 has been pressed.

[0159] In step S2001, the restore execution program 150 receives the values ​​of the restore target server 1901 and the restore objective 1902 entered on the restore execution screen 13000a.

[0160] In step S2002, the restore execution program 150 searches the backup data information 122 for entries where the received server to be restored 1901 and source server ID 1602 are the same, the data to be restored 1902 and source data ID 1603 are the same, and the purpose of the restore 1903 is included in the backup purpose 1605.

[0161] In step S2003, the restore execution program 150 obtains the predicted restore time for all the backup data acquired in step S2002. The predicted restore time is stored in the predicted restore time 1408 of the backup data information 122, and the program may obtain the predicted restore time corresponding to the received restore objective 1903. The restore processing time will vary depending on the extent to which the backup data includes full backup data and incremental / differential backup data, and whether the performance of the server to which the data is restored changes. Therefore, in step S2003, the program may call the restore processing performance calculation program 142 to calculate the predicted restore time.

[0162] In step S2004, the restore execution program 150 outputs the backup data information 121 obtained in step S2003 as a restore point list to the restore execution screen 13000b. The restore execution screen 13000b will be described later.

[0163] In step S2005, the restore execution program 150 receives the restore point selected by the system administrator on the restore execution screen 13000b.

[0164] In step S2006, the restore execution program 150 obtains backup job information from the backup job information 121 where the data transfer path from the backup repository 205 to the restore destination business system server 202 overlaps with the received restore point and the restore objective 1903. In this embodiment, the location of the repository destination business system server 202 is determined by the restore objective. For example, in the case of logical failure, it is the same server as the server to be restored (i.e., the backup target server). In the case of storage failure, it is the same zone as the server to be restored (the backup target server). In the case of zone failure, it is a different zone in the same region as the server to be restored (the backup target server). In the case of region failure, it is a different region from the server to be restored (the backup target server). In this embodiment, only disks and network interfaces are targeted as information on the components that form the data transfer path, but processors of the business system server 201 and the repository server 202 may also be targeted.

[0165] In step S2007, the restore execution program 150 searches the backup job information 121 for backup jobs to be executed during the restore execution time period, from the backup job information obtained in step S2006. If no specific restore execution time is specified in the input, the restore execution time period will be, for example, the time period of the predicted restore time starting from the current time. The execution time period for backup jobs will be the time period of the value stored in the predicted backup completion time 1406, starting from the time of schedule 1405.

[0166] In step S2008, the restore execution program 150 determines whether the search results from step S2007 are one or more. If the result of this determination is true (S2009: YES), the restore execution program 150 proceeds to step S2009; if the result of this determination is false (S2008: NO), the process proceeds to step S2010.

[0167] In step S2009, the restore execution program 150 outputs a warning to the restore execution screen 13000b indicating that the performance of the restore process may be degraded because backup jobs are executed during the restore execution time.

[0168] In step S2010, when the system administrator sends a restore command on the restore execution screen 13000b, the restore execution program 150 executes the restore process on the management system target 200 based on the input information received on the restore execution screen 13000a and the input information on the restore execution screen 13000b.

[0169] <Restore execution screen 13000b> Figure 21 shows an example of the restore execution screen 13000b according to the fourth embodiment. The input screen shown in Figure 21 is an example of a GUI implementation.

[0170] In the fourth embodiment, the restore execution screen 13000b is a screen on which the restore execution program 150 outputs a list of restore points in step S2004. It is also an input screen for the system administrator to select and input which restore point to use to perform the restore process.

[0171] The restore execution screen 13000b includes a restore point list display area 2100 that displays the backup data information acquired in step S2002 as a list of restore points, and a restore execution button 2121. The restore point list display area 2100 also includes the backup time 2101, the repository 2102, and the predicted restore time 2103.

[0172] Backup time 2101 displays the time when the backup job completed the backup process, i.e., the time when the data became recoverable. Repository 2102 displays the repository where the backup data is stored. Predicted restore time 2103 displays the predicted restore time when the restore execution program 150 restores the backup data acquired in step S2003.

[0173] The restore points displayed in Restore Point 2100 may be sorted and displayed in order of backup time value. Alternatively, the restore points displayed in Restore Point 2100 may be sorted and displayed in order of predicted restore time value. This makes it easier for system administrators to find the restore point closest to the desired restoration time, or a restore point with an earlier restore time.

[0174] Each of the restore points displayed in the restore point list display area 2100 can be selected, and the restore execution program 150 receives the selected result in step S2005.

[0175] When the system administrator presses the restore execution button 2121, the restore execution program 150 receives the restore execution instruction and executes the restore process.

[0176] As described above, according to the fourth embodiment, the restore process can be performed according to the purpose of the restore.

[0177] For example, as explained in Figures 20 and 21, the processor of the management computer 160, which is a computer having a processor and memory, displays the restore point based on the backup data information 122, which is information about the backup data stored in the backup repository by the backup job executed above, the identification information of the data to be restored (for example, the server to be restored 1901, the data to be restored 1902), and the purpose of the restore (for example, the purpose of the restore 1903). This allows users of this system to select the data to be restored according to the purpose of the restore.

[0178] Furthermore, as explained in Figure 20, S2010, etc., the processor performs the restore based on the selected restore point from among the restore points, the identification information of the data to be restored, and the input purpose of the restore. This allows the user of this system to perform the restore process for the selected desired data.

[0179] Furthermore, as explained in Figure 20, S2010, etc., the processor acquires and displays the predicted predetermined restore processing time (for example, the processing time based on the training data shown in Figure 10) based on the backup data information 122, the identification information of the data to be restored, and the purpose of the restore that has been input. This allows users of the system to easily select a restore process that corresponds to the predicted restore time.

[0180] Furthermore, as explained in Figure 20, S2006-S2009, the processor searches for backup jobs whose transfer paths overlap with the data to be restored, based on the selected restore point, the identification information of the data to be restored, the input purpose of the restore, and the backup job information 121, which is the configuration information of a previously registered backup job. The processor then displays whether such backup jobs exist. This makes it possible to know in advance whether there are backup jobs with the same transfer path and whether such backup jobs may degrade the performance of the restore process.

[0181] It should be noted that the present invention is not limited to the embodiments described above, and can be implemented with appropriate modifications without departing from the spirit of the invention.

[0182] For example, in the above embodiment, some or all of the processing performed by the processor may be performed by a dedicated hardware circuit. Also, the program in the above embodiment may be installed from a program source. The program source may be a program distribution server or a storage medium (e.g., a portable storage medium). [Explanation of symbols]

[0183] 100 Backup Management Systems 111 Business System Configuration Information 112 Backup Repository 113 Placement Constraint Rules 121 Backup Job Information 122 Backup data information 131 Business System Load Information 132 Backup Repository Load Information 140 Backup Placement Calculation Program 141 Backup Processing Performance Calculation Program 142 Restore Processing Performance Calculation Program 143 Backup configuration change program, 144 Backup Job Registration Program 145 Backup execution program 146 Managed Information Collection Program 150 Restore Execution Program 170 Networks 200 managed systems 201 Business System Server 202 Repository Server 203 Data 204 Backup Program 205 Backup Repository 206 Regions 207 Zones

Claims

1. A backup management system that uses a computer having a processor and memory to perform backup and restore operations on managed data and manage backup data, The aforementioned processor, Based on the business system configuration information, which is information regarding the configuration of the business system servers included in the managed object, the backup repository configuration information, which is information regarding the configuration of the repository server that stores the backup data, the input backup setting information, and the placement constraint rules for determining the placement of backup data according to the purpose of the backup, the system calculates combinations of backup repository placements that satisfy the placement constraint rules. Predict the processing time for a given backup based on the placement of the backup repository. Based on the placement of the backup repository and the purpose of the restore, predict the processing time for a predetermined restore. Among the combinations of backup repository placements, derive the combination in which the backup processing time and the restore processing time satisfy the target backup completion time and target restore processing time included in the input backup configuration information. Based on the aforementioned business system configuration information and the aforementioned backup repository configuration information, the system calculates and displays the resources that need to be added among the combinations of backup repository placements. A backup management system characterized by the following features.

2. The aforementioned processor, Display a list of combinations of backup repository placements. The backup management system according to feature 1.

3. The aforementioned processor, The system calculates and displays the additional costs required based on the correlation of costs for additional resources among the combinations of the aforementioned business system configuration information, the aforementioned backup repository configuration information, and the placement of each of the aforementioned backup repositories. The backup management system according to feature 1.

4. The aforementioned processor, The combinations of backup repository locations are sorted and displayed in ascending order of the additional costs required, or in order of highest availability, or in order of evaluation of a combination thereof. The backup management system according to feature 1.

5. The aforementioned processor, Based on the selected combination of backup repository placements, backup job information, which is the configuration information for the backup job, is created, and the backup job is executed. The backup management system according to feature 1.

6. The aforementioned processor, Based on the selected combination of backup repository placements and the additional resources required, the configuration to be managed is modified. The backup management system according to feature 1.

7. The aforementioned processor, Based on the aforementioned business system configuration information, the backup repository configuration information, the combination of backup repository placements, and backup job information which is the configuration information for previously registered backup jobs, the load on the data transfer path during backup and restore in the combination of backup repository placements is calculated, and the additional resources required are calculated and displayed. The backup management system according to feature 1.

8. The aforementioned processor, Based on the input backup configuration information, including the configuration information of the business system server before its construction, the business system configuration information is generated. Among the combinations of backup repository placements, derive the combination in which the backup processing time and the restore processing time satisfy the target backup completion time and target restore processing time included in the input backup configuration information. The backup management system according to feature 1.

9. The aforementioned processor, Based on the backup data information, which is information about the backup data stored in the backup repository by the executed backup job, the identification information of the data to be restored, and the purpose of the restore, the restore point is displayed. The backup management system according to claim 5.

10. The aforementioned processor, Based on the selected restore point from the aforementioned restore points, the identification information of the data to be restored, and the entered purpose of the restore, the restore is performed. The backup management system according to feature 9.

11. The aforementioned processor, Based on the backup data information, the identification information of the data to be restored, and the purpose of the restore, the predicted predetermined restore processing time is obtained. Display The backup management system according to feature 9.

12. The aforementioned processor, From the aforementioned restore points, the system searches for backup jobs whose transfer paths overlap with the data to be restored, based on the selected restore point, the identification information of the data to be restored, the entered purpose of the restore, and the backup job information, which is the configuration information of a previously registered backup job. The system then displays whether any matching backup jobs exist. The backup management system according to feature 9.

13. A management computer having a processor and memory, which performs managed backup and restore operations and manages backup data, The aforementioned processor, Based on the business system configuration information, which is information regarding the configuration of the business system servers included in the managed object, the backup repository configuration information, which is information regarding the configuration of the repository server that stores the backup data, the input backup setting information, and the placement constraint rules for determining the placement of backup data according to the purpose of the backup, the system calculates combinations of backup repository placements that satisfy the placement constraint rules. Predict the processing time for a given backup based on the placement of the backup repository. Based on the placement of the backup repository and the purpose of the restore, predict the processing time for a predetermined restore. Among the combinations of backup repository placements, derive the combination in which the backup processing time and the restore processing time satisfy the target backup completion time and target restore processing time included in the input backup configuration information. Based on the aforementioned business system configuration information and the aforementioned backup repository configuration information, the system calculates and displays the resources that need to be added among the combinations of backup repository placements. A management computer characterized by the following features.

14. On the computer, A process for calculating combinations of backup repository placements that satisfy the placement constraint rules, based on business system configuration information, which is information about the configuration of business system servers included in the management; backup repository configuration information, which is information about the configuration of repository servers that store backup data; input backup setting information; and placement constraint rules for determining the placement of backup data according to the purpose of the backup. A process to predict the processing time for a given backup based on the location of the backup repository, The backup repository's location and the purpose of the restore determine the predetermined restore processing time. Prediction process, A process to derive from among the combinations of backup repository placements a combination in which the backup processing time and the restore processing time satisfy the target backup completion time and target restore processing time included in the input backup configuration information, Based on the aforementioned business system configuration information and the aforementioned backup repository configuration information, the process calculates and displays the resources that need to be added from the combination of backup repository placements. A backup management program characterized by its ability to execute certain actions.

Images