Backup schedule creation device and backup schedule creation method

Abstract

To propose an appropriate backup schedule in a system in which it is difficult to predict the change in volume of backup data.SOLUTION: A backup schedule management apparatus 2 includes: a backup prediction time calculation unit 231 which calculates a backup prediction time in each of combinations of data transfer servers 13 and backup target servers 12, on the basis of temporary backup throughput and the volume of backup data used in the backup target servers 12; and a schedule preparation unit 232 which sequentially allocates backup processes of the backup target servers 12 to the data transfer servers 13, based on information on the backup prediction time and information on network usage, to prepare a backup schedule based on a result of the allocation.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a backup schedule creation device and a backup schedule creation method.

Background Art

[0002] In recent years, in systems having data that needs to be backed up, those equipped with data transfer servers have been increasing. A data transfer server is a server that transfers backup target data (hereinafter also referred to as "backup data") to a backup storage. Even when there are multiple machines to be backed up in the system, by arranging a plurality of data transfer servers in the system, backup processing can be executed in parallel. In such a system, it is required to complete all backup processing within a limited backup allowable time (hereinafter also referred to as "backup window").

[0003] For example, the backup management program described in Patent Document 1 acquires, from each data transfer device, the first data amount transmitted to the backup storage and the second data amount not transmitted to the backup storage by the deduplication function among the data previously assigned to each data transfer device. Further, the backup management program calculates the previous transmission data amount transmitted to the backup storage by a plurality of data transfer devices based on the acquired first data amount. Further, the backup management program calculates the next transmission data amount to be transmitted to the backup storage based on the acquired first data amount, the second data amount, and the size of the backup target data. Furthermore, the backup management program increases or decreases the number of a plurality of data transfer devices based on the result of comparing the calculated previous transmission data amount and the next transmission data amount. According to the technique described in Patent Document 1, the resources used for backup can be controlled so that the backup is completed within the assumed time.

[0004] Furthermore, for example, the job scheduler described in Patent Document 2 receives task information, replica placement data, infrastructure topology data, and resource performance data as inputs from the archive management system. The job scheduler also models a flow network representing the data content, software programs, physical devices, and communication capacity of the archive management system at various levels of vertices, according to the received inputs. The optimal path within the modeled flow network is calculated as an initial schedule, and the archive management system executes tasks according to the initial schedule. The operation of the scheduled tasks is monitored, and the job scheduler creates a new schedule based on feedback from the monitored operation and predetermined heuristics. According to the technology described in Patent Document 2, the optimal (fastest) network path can be derived as a schedule from the communication capacity and network topology information and applied to the management system. [Prior art documents] [Patent Documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2023-009583 [Patent Document 2] Special Publication No. 2013-513150 [Overview of the project] [Problems that the invention aims to solve]

[0006] Incidentally, in recent years, due to factors such as the ease of scaling environments and the rapid growth of data, backup data can increase rapidly. When backup data increases rapidly, a situation may arise where the backup process cannot be completed within the backup window, depending on the pre-configured data transfer server and the machines being backed up. If the entire backup process is not completed within the backup window, the Recovery Point Objective (RPO) cannot be met.

[0007] This invention was made in consideration of the above circumstances, and its objective is to enable the creation of an appropriate backup schedule even in systems where it is difficult to predict changes in the volume of backup data. [Means for solving the problem]

[0008] A backup schedule creation device according to one aspect of the present invention is a backup schedule creation device that creates a backup schedule for backup processing in a backup schedule management system in which a plurality of backup target servers having backup data to be backed up to a data storage server and a plurality of data transfer servers that acquire backup data from the backup target servers and transfer it to the data storage server are connected to each other by a network. The backup schedule creation device according to one aspect of the present invention comprises a backup prediction time calculation unit that calculates the predicted backup time for each combination of data transfer servers and backup target servers based on the estimated backup throughput during backup data transmission and the backup data usage capacity of the backup target servers, and a schedule creation unit that sequentially assigns backup processing of backup data of backup target servers to data transfer servers based on backup prediction time information and information on the degree of network usage when performing backup processing, and creates a backup schedule based on the assignment results. [Effects of the Invention]

[0009] According to at least one aspect of the present invention, it becomes possible to create an appropriate backup schedule even in systems where it is difficult to predict changes in the volume of backup data. Other issues, configurations, and effects not mentioned above will be clarified by the following description of the embodiments. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing an example of the schematic configuration of a backup schedule management system according to one embodiment of the present invention. [Figure 2] This is a block diagram showing examples of the hardware configurations of a server and a backup schedule management device that constitute a backup schedule management system according to one embodiment of the present invention. [Figure 3] This figure shows an example configuration of a backup job table according to one embodiment of the present invention. [Figure 4] This figure shows an example of the configuration of a VM configuration information table according to one embodiment of the present invention. [Figure 5] This figure shows an example configuration of a backup data path table according to one embodiment of the present invention. [Figure 6] This figure shows an example configuration of a backup prediction time table related to one embodiment of the present invention. [Figure 7] This graph shows the length of the provisional backup prediction time for each combination of the backup target server and the data transfer server, as shown in the backup prediction time table for one embodiment of the present invention. [Figure 8] This figure shows an example configuration of a provisional backup schedule table according to one embodiment of the present invention. [Figure 9] This figure shows an example of the correspondence between the backup target server and the data transfer server after the allocation process has been performed by the scheduling unit according to one embodiment of the present invention. [Figure 10]It is a diagram showing a configuration example of a candidate backup schedule table which is a revised provisional backup schedule table according to an embodiment of the present invention. [Figure 11] It is a diagram showing an outline of the correction process of the provisional backup schedule table by the schedule creation unit according to an embodiment of the present invention. [Figure 12] It is a diagram showing an outline of the correction process of the provisional backup schedule table by the schedule creation unit according to an embodiment of the present invention. [Figure 13] It is a diagram showing an outline of the correction process of the provisional backup schedule table by the schedule creation unit according to an embodiment of the present invention. [Figure 14] It is a flowchart showing an example of the procedure of the backup schedule management process by the backup schedule management system according to an embodiment of the present invention. [Figure 15] It is a flowchart showing an example of the procedure of the backup prediction time table creation process by the backup prediction time calculation unit according to an embodiment of the present invention. [Figure 16] It is a flowchart showing an example of the procedure of the provisional backup schedule table creation process by the schedule creation unit according to an embodiment of the present invention. [Figure 17] It is a flowchart showing an example of the procedure of the provisional backup schedule table creation process by the schedule creation unit according to an embodiment of the present invention. [Figure 18] It is a flowchart showing an example of the procedure of the candidate backup schedule table creation process by the schedule creation unit according to an embodiment of the present invention. [Figure 19] It is a flowchart showing an example of the procedure of the candidate backup schedule table creation process by the schedule creation unit according to an embodiment of the present invention. [Figure 20] It is a flowchart showing an example of the procedure of the backup schedule determination process by the schedule creation unit according to an embodiment of the present invention. [Figure 21]It is a diagram showing a configuration example of a candidate backup schedule selection screen according to an embodiment of the present invention. [Figure 22] It is a flowchart showing an example of the procedure of backup prediction time table update processing by a schedule creation unit according to an embodiment of the present invention.

Mode for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each figure, the same components are denoted by the same reference numerals. The following description and drawings are examples for explaining the present invention, and for the sake of clarity of explanation, omissions and simplifications are made as appropriate. The present invention can be implemented in various other forms. Unless otherwise limited, each component may be singular or plural.

[0012] <Configuration of Backup Schedule Management System> First, referring to FIG. 1, the configuration of a backup schedule management system 100 according to an embodiment of the present invention will be described. FIG. 1 is a block diagram showing a schematic configuration example of the backup schedule management system 100.

[0013] As shown in FIG. 1, the backup schedule management system 100 includes a server (host) 1 and a backup schedule management device 2. The server 1 is composed of servers 1a to 1d. Hypervisors 11a to 11d for creating and executing VMs (Virtual Machines) on the servers are installed on the servers 1a to 1d, respectively.

[0014] VMA12a and VMJ13j are configured on server 1a, and VMK12k and VMB12b are configured on server 1b. VMC12c to VME12e are configured on server 1c, and VML13l, VMN13n, and VMN14n are configured on server 1d.

[0015] VMA12a to VME12e are backup target servers 12 that have backup data. VMJ13j to VMM13m, enclosed in a dashed-dot frame in the diagram, are data transfer servers 13 that collect backup data from backup target servers 12 and store it in data storage server 14. VMN14n, enclosed in a double-dot frame in the diagram, is data storage server 14 where the backup data of VMA12a to VME12e collected based on the backup process by data transfer server 13 is stored.

[0016] The backup schedule management device 2 (an example of a backup schedule creation device) creates a backup processing schedule. The backup schedule management device 2 then notifies the VMJ13j to VMM13m of the data transfer server 13 of the created backup schedule and the result of the determination of whether or not the backup processing based on the backup schedule is possible.

[0017] Note that the number of servers 1 in the backup schedule management system 100, the number of VMs deployed on server 1, and the ratio of backup target servers 12, data transfer servers 13, and data storage servers 14 are not limited to the example shown in Figure 1. Also, backup target servers 12, data transfer servers 13, and data storage servers 14 may be located in a cloud environment or the like.

[0018] The backup schedule management device 2 comprises a backup configuration information acquisition unit 21, a VM configuration information acquisition unit 22, a schedule management unit 23, a result output unit 24, and a database Db.

[0019] The backup configuration information acquisition unit 21 acquires backup configuration information from the data storage server 14 and creates a backup job table T1 (see Figure 3). The backup configuration information is information about each element that constitutes a backup job, which is a job for backup processing. An example of the configuration of the backup job table T1 will be described in detail later with reference to Figure 3.

[0020] The VM configuration information acquisition unit 22 acquires the configuration information of each server 1 that constitutes the backup schedule management system 100, and also acquires the configuration information of each VM from the hypervisor 11 of each server 1. Then, the VM configuration information acquisition unit 22 creates a VM configuration information table T2 (see Figure 4) based on the acquired configuration information. The VM configuration information acquisition unit 22 also creates a backup data path table T3 (see Figure 5) based on the acquired configuration information. An example of the configuration of the VM configuration information table T2 will be described in detail with reference to Figure 4 below, and an example of the configuration of the backup data path table T3 will be described in detail with reference to Figure 5 below.

[0021] The schedule management unit 23 includes a backup prediction time calculation unit 231 and a schedule creation unit 232. The backup prediction time calculation unit 231 creates a backup prediction time table T11 (see Figure 6) based on the backup job table T1, the VM configuration information table T2, and the backup data path table T3. The backup prediction time table T11 is a table that stores the provisional backup throughput and the backup prediction time required for the backup process for each combination of the backup target server 12 and the data transfer server 13. The backup prediction time table T11 will be described in detail below with reference to Figure 6.

[0022] The schedule creation unit 232 creates a provisional backup schedule table T12 (see Figure 7) based on the information in the backup prediction time table T11. The provisional backup schedule table T12 is a table that shows the result of assigning compatible data transfer servers in order from the backup target servers with the longest backup prediction times. The provisional backup schedule table T12 will be described in detail below with reference to Figure 7.

[0023] Furthermore, the schedule creation unit 232 modifies the provisional backup schedule table T12 based on information such as the degree of distribution of data path usage during backup processing and the relationship between backup throughput and network bandwidth in each data path. The schedule creation unit 232 then uses the modified provisional backup schedule table T12 as the candidate backup schedule table T13. In this embodiment, the schedule creation unit 232 generates multiple candidate backup schedule tables T13 with different effects. For example, the schedule creation unit 232 can create candidate backup schedule tables T13 corresponding to the backup schedule that achieves the fastest backup completion time and the backup schedule that maximizes the degree of network distribution during backup processing.

[0024] Furthermore, the schedule creation unit 232 creates a backup schedule using the candidate backup schedule table T13, which has been selected based on predetermined criteria or selected by the user. After the actual backup process based on the created backup schedule is completed, the schedule creation unit 232 updates the backup prediction time table T11 (see Figure 6) using the processing results.

[0025] The result output unit 24 presents the candidate backup schedule table T13, the final determined backup schedule, etc., to the user via the display unit 230 (see Figure 2) screen, etc.

[0026] The database Db stores backup job table T1, VM configuration information table T2, backup data path table T3, backup prediction time table T11, provisional backup schedule table T12, candidate backup schedule table T13, etc.

[0027] <Example of computer hardware configuration> Next, the hardware configuration of the device for realizing the functions of the backup schedule management system 100 according to this embodiment will be described with reference to Figure 2. Figure 2 is a block diagram showing examples of the hardware configurations of the server 1 and backup schedule management device 2 that constitute the backup schedule management system 100. The computer 200 shown in Figure 2 is hardware used as a so-called computer.

[0028] The computer 200 comprises a control unit 210 connected to bus B, a non-volatile storage 220, a display unit 230, an operation input unit 240, and a communication interface 250.

[0029] The control unit 210 includes a CPU (Central Processing Unit) 211, a ROM (Read Only Memory) 212, and a RAM (Random Access Memory) 213.

[0030] The CPU 211 reads the program code of the software that implements each function according to this embodiment from the ROM 212, loads it into the RAM 213, and executes it. Variables, parameters, etc. that occur during the calculation process are temporarily written to the RAM 213.

[0031] The control unit 210 may be equipped with a processing unit such as an MPU (Micro-Processing Unit) instead of a CPU 211. Alternatively, the control unit 210 may use both a CPU and an MPU.

[0032] Non-volatile storage 220 can include, for example, an HDD (Hard Disk Drive), SSD (Solid State Drive), flexible disk, optical disk, magneto-optical disk, CD-ROM, CD-R, or non-volatile memory card. This non-volatile storage 220 stores the OS, various parameters, and programs necessary for the computer 200 to function. The programs may also be stored in ROM 212.

[0033] The display unit 230 is a monitor, for example, an LCD (Liquid Crystal Display), which displays the results of processing performed by the computer 200. The operation input unit 240 is composed of, for example, a keyboard, mouse, touch sensor, etc., and generates operation signals in response to user operations and supplies them to the CPU 211. The display unit 230 and the operation input unit 240 may be integrated as a single touch panel.

[0034] The program is stored in the form of computer-readable program code, and the CPU 211 sequentially executes operations according to that program code. In other words, the ROM 212 or non-volatile storage 220 is used as an example of a computer-readable, non-transient recording medium that stores a program executed by the computer.

[0035] The communication I / F250 uses, for example, a NIC (Network Interface Card), which enables the transmission and reception of various types of data with external devices via a network or communication line.

[0036] <Configuration of backup job table T1> Next, we will explain the configuration of the backup job table T1 with reference to Figure 3. Figure 3 shows an example of the configuration of the backup job table T1.

[0037] As shown in Figure 3, the backup job table T1 contains the following items: "Job Name", "VM Name", "VM Role", "Platform", "Backup Job Start Time", "Backup Window", "Next Backup Format", and "Standard Backup Throughput Value (MB / s)".

[0038] The "Job Name" field stores the job name of the backup job. The "VM Name" field stores the name assigned to the VM (VM name). The "VM Role" field stores the role assigned to the VM (VM role). The VM role may contain one of the following, for example, as shown in the diagram: "Backup Target," "Data Transfer," or "Data Storage."

[0039] The "Platform" field stores information about the name of the platform that enables virtualization. The "Backup Job Start Time" field stores information about the start time of the backup job. The "Backup Window" field stores information about the start and end times of the backup window.

[0040] The "Next Backup Format" field stores information about the backup format for the next backup process performed on the backup target server 12. In the example shown in Figure 3, the "Next Backup Format" field may contain "Incremental," "Full," or "null." "Incremental" indicates an incremental backup, which backs up data that has been added since the last backup process was executed. "Full" indicates a full backup, which backs up all data. "null" indicates that no backup will be performed.

[0041] The "Standard Backup Throughput Value (MB / s)" field stores information about the standard backup throughput value determined by the backup format stored in "Next Backup Format". This "Standard Backup Throughput Value (MB / s)" is stored as a provisional value in the "Provisional Backup Throughput (MB / s)" field in the backup prediction time table T11 shown in Figure 6 below.

[0042] For example, in the top record of the backup job table T1 shown in FIG. 3, it is shown that the backup job with the job name "Job A" is a job performed on the backup target server 12, which is VMA12a. Also, in the top record, it is shown that the virtualization platform of the VM is "Virtualization Infrastructure A", the start time of the backup job is "21:00", and the backup window is "21:00~7:00". Furthermore, in the top record, it is shown that the next backup format is "incremental" and the standard backup throughput value is "25 (MB / s)".

[0043] <Configuration of the VM Configuration Information Table> Next, referring to FIG. 4, the VM configuration information table T2 will be described. FIG. 4 is a diagram showing a configuration example of the VM configuration information table T2. As shown in FIG. 4, the VM configuration information table T2 has columns for "VM Name", "VM Role", "VM Deployment Host", and "VM Used Capacity (GB)".

[0044] In the "VM Name" column, the name of the VM is stored. In the "VM Role" column, information about the role assigned to the VM is stored. In the "VM Deployment Host" column, information about the host (server) on which the VM is deployed is stored. In the "VM Used Capacity" column, information about the used capacity (GB) of the VM's data is stored.

[0045] For example, in the top record of the VM configuration information table T2 shown in FIG. 4, it is shown that for VMA12a with the VM name "VMA", the VM role is "Backup Target (Server)", the host on which VMA12a is deployed is "Server 1a", and the used capacity of the VM is "40 (GB)".

[0046] <Configuration of the Backup Data Path Table> Next, referring to FIG. 5, the configuration of the backup data path table T3 will be described. FIG. 5 is a diagram showing a configuration example of the backup data path table T3. As shown in Figure 5, the backup data routing table T3 has the following items: "Data routing number", "Source host", "Destination host", and "Inter-host network bandwidth (Mb / s)".

[0047] The "Data Route Number" field stores information about the data route number, which is a number that identifies the route of the backup data. The "Source Host" field stores information about the name of Server 1 where the backup target server 12, which is the source of the backup data, is located. The "Destination Host" field stores information about the name of Server 1 where the data transfer server 13, which is the destination of the backup data, is located. The "Inter-Host Network Bandwidth (Mb / s)" field stores information about the network bandwidth occupied by the transmission path of the backup data when the backup data is transmitted from the source host to the destination host.

[0048] For example, the top record in the backup data path table T3 shown in Figure 5 indicates that for data path number "1", both the source host and destination host are "Server 1a", and the inter-host network bandwidth is "null". The second record from the top indicates that for data path number "2", the source host is "Server 1a" and the destination host is "Server 1b", and the inter-host network bandwidth is "1000 (Mb / s)".

[0049] <Backup Estimated Time Table> Next, the configuration of the backup prediction time table T11 will be described with reference to Figure 6. Figure 6 shows an example of the configuration of the backup prediction time table T11. The backup prediction time table T11 is a table created by the backup prediction time calculation unit 231 of the schedule management unit 23 based on the information described in the backup job table T1, the VM configuration information table T2, and the backup data path table T3.

[0050] As shown in Figure 6, the backup prediction time table T11 includes the following items: "Combination number", "Server to be backed up", "VM usage capacity (GB)", "Data transfer server", "Data path number", "Temporary backup throughput (Mb / s)", and "Temporary backup prediction time (minutes)".

[0051] The "Combination Number" field stores information about the combination number, which is a number that identifies the combination of the backup target server 12, which is the source of the backup data, and the data transfer server 13, which is the destination.

[0052] The "Backup Target Server" field stores information about the name of the backup target server 12. The "VM Usage Capacity (GB)" field stores information about the data usage capacity on the backup target server 12. The "Data Transfer Server" field stores information about the name of the data transfer server 13. The "Data Route Number" field stores information about the data route number of the data route used in the combination of the backup target server 12 and the data transfer server 13.

[0053] The "Temporary Backup Throughput (Mb / s)" field stores an estimated backup throughput value derived from information about the data path and the network bandwidth occupied when that data path is in use.

[0054] The "Predicted Pre-Backup Time (minutes)" field stores the estimated backup time calculated from the VM's backup capacity and pre-backup throughput.

[0055] For example, the top record in the backup prediction time table T11 shown in Figure 6 indicates that the data usage capacity of VMA12a on backup target server 12 for combination number "1" is "40 (GB)". The top record also indicates that the data transfer server is "VMJ13j", the data path number is "1", the provisional backup throughput is "100 (Mb / s)", and the provisional backup prediction time is "20 (minutes)".

[0056] Figure 7 is a graph showing the length of the provisional backup prediction time for each combination of the backup target server 12 and the data transfer server 13 as shown in the backup prediction time table T11. In the graph shown in Figure 7, the data transfer server 13 is placed on the vertical axis and the backup target server 12 is placed on the horizontal axis. Based on the information on the length of the provisional backup prediction time for each combination of the backup target server 12 and the data transfer server 13 shown in Figure 7, the backup prediction time calculation unit 231 of the schedule management unit 23 (see Figure 1) creates the provisional backup schedule table T12.

[0057] <Configuration of the provisional backup schedule table> Next, we will describe the configuration of the provisional backup schedule table T12 with reference to Figure 8. Figure 8 shows an example of the configuration of the provisional backup schedule table T12. As shown in Figure 8, the provisional backup schedule table T12 has the following items: "Job name", "Server to be backed up", "Data transfer server", "Backup capacity (GB)", "Temporary backup throughput (Mb / s)", "Temporary backup estimated time (minutes)", "Data path number", "Backup start time", and "Backup end time".

[0058] The "Job Name" field stores the job name information of the backup job. The "Backup Target Server" field stores the name information of backup target server 12. The "Data Transfer Server" field stores the name information of data transfer server 13. The "Backup Capacity (GB)" field stores the capacity information of the backup data for backup target server 12.

[0059] The "Temporary Backup Throughput (Mb / s)" field stores the temporary backup throughput value from the backup prediction time table T11 (see Figure 6). The "Temporary Backup Prediction Time (minutes)" field stores the temporary backup prediction time information from the backup prediction time table T11. The "Data Path Number" field stores the data path number information determined by the combination of the backup target server 12 and the data transfer server 13. The "Backup Start Time" field stores the start time information of the backup process. The "Backup End Time" field stores the end time information of the backup process.

[0060] For example, the top record in the provisional backup schedule table T12 shown in Figure 8 contains information about the backup process for backup data from VMA12a on the backup target server 12 to VMJ13j, which is the data transfer server 13, for a job named Job A. The top record also indicates that the backup capacity of VMA12a is "40 (GB)", the provisional backup throughput is "100 (Mb / s)", and the estimated backup time is "120 (minutes)". Furthermore, the top record indicates that the data path number of the network used by the VMA12a and VMJ13j combination is "1", the backup start time is "3:00", and the backup end time is "5:00".

[0061] The schedule creation unit 232 (see Figure 1) of the schedule management unit 23 assigns the backup target servers 12 to the data transfer server 13 based on the contents of the provisional backup schedule table T12. At this time, the schedule creation unit 232 assigns the backup target servers 12 to the data transfer server 13 in order from the backup target server 12 with the largest minimum backup prediction time.

[0062] For example, in the example shown in Figure 7, the backup target server 12, VMA12a, has the minimum predicted backup time when paired with the data transfer server 13, VML13l. Similarly, VMB12b has the minimum predicted backup time when paired with VMK13k, and VMC12c has the minimum predicted backup time when paired with VML13l. Also, VMD12d has the minimum predicted backup time when paired with VMJ13j. Among these minimum predicted backup times, the data transfer server 13 is allocated in order from the one with the longest predicted backup time.

[0063] Figure 9 shows an example of the correspondence between the backup target server 12 and the data transfer server 13 after the assignment process by the schedule creation unit 232. In Figure 9, the data transfer server 13 is located on the vertical axis, and the horizontal axis shows the time axis from the backup start time to the backup end time. In Figure 9, in order to make the explanation of the assignment process of the backup target server 12 to the data transfer server 13 easier to understand, an example is given in which there are more backup target servers 12 than shown in Figure 1 (there are VMs after VMF).

[0064] In the example shown in Figure 9, for the data transfer server 13, VMJ13j, the backup target servers 12, VMF (which has the longest predicted backup time) and VMD12d (which has the next longest), are assigned in order from the earliest backup start time. Similarly, for VMK13k, VMB12b (which has the longest predicted backup time), VMC12c (which has the next longest), and VMH (which has the next longest), are assigned in order from the earliest backup start time.

[0065] It should be noted that the scheduling unit 232 assigning backup target servers 12 with longer backup prediction times to earlier time slots in the backup processing time by the data transfer server 13 is just one example, and the present invention is not limited to this. The scheduling unit 232 may also assign schedules to the data transfer server 13 in order from backup target servers 12 with shorter backup prediction times to earlier time slots.

[0066] After the backup target server 12 has been assigned to the data transfer server 13, the schedule creation unit 232 modifies the provisional backup schedule table T12 based on the backup window information and the degree of distribution of network routes used during the backup process. The schedule creation unit 232 then sets the modified provisional backup schedule table T12 as the candidate backup schedule table T13.

[0067] Figure 10 shows an example configuration of the candidate backup schedule table T13, which is the corrected provisional backup schedule table T12. Figure 11 shows an overview of the correction process of the provisional backup schedule table T12 by the schedule creation unit 232. In Figure 11, the data transfer server 13 is located on the vertical axis, and the horizontal axis shows the time axis from the backup start time to the backup end time.

[0068] The difference between the candidate backup schedule table T13 shown in Figure 10 and the provisional backup schedule table T12 before modification is that it includes a "path concurrency counter" item. Since the other items are the same as those in the provisional backup schedule table T12 shown in Figure 8, explanations of the duplicate items are omitted.

[0069] The "Route Concurrency Counter" field stores a value for a counter that indicates the concurrency of network routes. Network route concurrency indicates the degree of network usage during backup data transmission. If routes used in the same time period in the backup schedule overlap with routes for other backup data, the value of the route concurrency counter is incremented. The schedule creation unit 232 modifies the provisional backup throughput value in the provisional backup schedule table T12 based on the count value stored in the "Route Concurrency Counter" field.

[0070] In the example shown in Figure 10, the temporary backup throughput value for backup data transmission from VMA12a to VMJ13j for a backup job named "job A" has been changed from "100 (minutes)" to "150 (minutes)". This change was made by the schedule creation unit 232 because other backup data transmissions were also taking place at the same time on the data path number "1".

[0071] Figure 11 shows an example where the backup prediction times for VMF, VMC12c, and VMA12a of the backup target server 12, which are assigned to VMJ13j of the data transfer server 13, have all been revised to be longer. This revision was made by the schedule creation unit 232 because the backup data for VMF, VMC12c, and VMA12a of the backup target server 12 are transmitted at the same time using the same data path.

[0072] Furthermore, if the backup data transmission paths overlap during the same time period in which backup processing is performed, the schedule creation unit 232 adjusts the provisional backup throughput so that the network throughput along the paths remains within the bandwidth. Then, the schedule creation unit 232 recalculates the provisional backup prediction time based on the adjusted provisional backup throughput. The schedule creation unit 232 also recalculates the backup start and end times based on the recalculated provisional backup throughput and provisional backup prediction time.

[0073] If there are combinations in the candidate backup schedule table T13 where the backup completion time does not fall within the backup window time, the schedule creation unit 232 readjusts the values ​​in the candidate backup schedule table T13. Specifically, the schedule creation unit 232 changes the combination of the backup target server 12 and the data transfer server 13, changes the order in which backup data is sent, etc.

[0074] Figures 12 and 13 show an overview of the modification process of the provisional backup schedule table T12 by the schedule creation unit 232. In Figures 12 and 13, the data transfer server 13 is located on the vertical axis, and the horizontal axis shows the time axis from the backup start time to the backup end time.

[0075] In the example shown in the upper part of Figure 12, the time when backup data for VMB12b is transmitted from the data transfer server 13 assigned to VMJ13j of the data transfer server 13 falls outside the backup window indicated by the solid rectangular frame in the figure. Therefore, the schedule creation unit 232 changes the data transfer server 13 that transfers the backup data for VMB12b to VMK13k, which has the earliest backup completion time.

[0076] The middle section of Figure 12 shows the state where the data transfer server 13, which transfers backup data for VMB12b, has been changed from VMJ13j to VMK13k.

[0077] If there are time periods in the revised schedule of the data transfer server 13 where the networks used overlap, the schedule creation unit 232 corrects the predicted backup time for the backup data during those time periods.

[0078] In the lower part of Figure 12, the estimated backup time for the backup data of VMD12d assigned to VMK13k, which is the data transfer server 13, and the estimated backup time for the backup data of VMG assigned to VML13l have both been corrected to larger (longer) times.

[0079] Furthermore, if the schedule creation unit 232 determines that the network redundancy can be reduced by changing the transfer order of backup data in the data transfer server 13, it modifies the transfer order of the backup data.

[0080] The upper part of Figure 13 shows the same schedule as the lower part of Figure 12. The middle part of Figure 13 shows the state in which the time for transferring backup data of VMB12b, which is assigned to the data transfer server 13, VMK13k, has been changed to the earliest time slot. This adjustment by the schedule creation unit 232 reduces the network concurrency in the latter half (later time) of the backup schedule. As a result of the reduced network concurrency, the time required to transfer backup data is shortened, and the estimated backup time is also shortened.

[0081] The lower part of Figure 13 shows that the estimated backup time for the backup data of VMD12d assigned to the data transfer server 13, VMK13k, and the estimated backup time for the backup data of VMH assigned to VML13l have both been reduced.

[0082] The result output unit 24 presents the adjusted provisional backup schedule table T12' as a candidate backup schedule table T13 to the user via the display unit 230 (see Figure 2). Then, the schedule management unit 23 creates the final backup schedule based on the user's instructions after they have reviewed the candidate backup schedule table T13.

[0083] <Backup Schedule Management Process> Next, a backup schedule management method using the backup schedule management system 100 according to this embodiment will be described. Figure 14 is a flowchart showing an example of the procedure for backup schedule management processing using the backup schedule management system 100.

[0084] First, the backup configuration information acquisition unit 21 of the backup schedule management device 2 acquires backup configuration information from the data storage server 14, and the VM configuration information acquisition unit 22 acquires configuration information for server 1 and VM. Then, the backup configuration information acquisition unit 21 creates the backup job table T1, and the VM configuration information acquisition unit 22 creates the VM configuration information table T2 and the backup data path table T3 (step S1).

[0085] Next, the backup prediction time calculation unit 231 of the schedule management unit 23 performs backup prediction time table creation processing (step S2). The backup prediction time table creation processing in step S2 will be described in detail with reference to Figure 15 below.

[0086] Next, the schedule creation unit 232 of the schedule management unit 23 performs the provisional backup schedule table creation process (step S3). The provisional backup schedule table creation process in step S3 will be described in detail with reference to Figures 16 and 17 below.

[0087] Next, the schedule creation unit 232 performs the candidate backup schedule table creation process (step S4). The candidate backup schedule table creation process in step S4 will be described in detail with reference to Figures 18 and 19 below.

[0088] Next, the schedule creation unit 232 performs backup schedule determination processing (step S5). The backup schedule determination processing in step S5 will be described in detail later with reference to Figure 20.

[0089] [Backup prediction time table creation process] Next, with reference to Figure 15, the backup prediction time table creation process by the backup prediction time calculation unit 231 will be described. Figure 15 is a flowchart showing an example of the procedure for creating a backup prediction time table by the backup prediction time calculation unit 231. First, the backup prediction time calculation unit 231 adds the combination of the backup target server 12 and the data transfer server 13 as components to the backup prediction time table T11 (step S11).

[0090] Next, the backup prediction time calculation unit 231 identifies the data paths for each combination of the backup target server 12 and the data transfer server 13, and adds the identified data paths as components to the backup prediction time table T11 (step S12).

[0091] Next, the backup prediction time calculation unit 231 performs a provisional backup throughput calculation process. The provisional backup throughput calculation process is performed for all combinations (and corresponding records) of the backup target server 12 and the data transfer server 13.

[0092] In the provisional backup throughput calculation process, the backup prediction time calculation unit 231 first determines whether the host (server) of the backup target server 12 and the host of the data transfer server 13 are the same (step S13). In other words, the backup prediction time calculation unit 231 determines whether the transmission of backup data between the backup target server 12 and the data transfer server 13 takes place within the same server 1.

[0093] If, in step S13, it is determined that the hosts match (step S13 is YES), the backup prediction time calculation unit 231 sets the standard backup throughput value as the temporary backup throughput for that combination (step S14). On the other hand, if, in step S13, it is determined that the hosts are different (step S13 is NO), the backup prediction time calculation unit 231 sets the smaller of the network bandwidth of the data path used by the combination of the backup target server 12 and the data transfer server 13 and the standard backup throughput value as the temporary backup throughput for that combination (step S15).

[0094] After processing in step S14 or step S15, the backup prediction time calculation unit 231 performs backup prediction time calculation processing. The backup prediction time calculation processing is performed on all records corresponding to all combinations of the backup target server 12 and the data transfer server 13. In the backup prediction time calculation processing, the backup prediction time calculation unit 231 calculates the backup prediction time by dividing the backup capacity by the provisional backup throughput (step S16). After processing in step S16, the backup prediction time table creation processing by the backup prediction time calculation unit 231 is completed.

[0095] [Provisional backup schedule table creation process] Next, with reference to Figures 16 and 17, the process of creating a provisional backup schedule table by the schedule creation unit 232 of the schedule management unit 23 will be described. Figures 16 and 17 are flowcharts showing examples of the procedure for creating a provisional backup schedule table by the schedule creation unit 232.

[0096] In the process of creating a provisional backup schedule table, the schedule creation unit 232 first performs the process of assigning backup target servers 12 to the data transfer server 13. The process of assigning backup target servers 12 to the data transfer server 13 is performed for each backup target server 12. In the process of assigning backup target servers 12, the schedule creation unit 232 assigns them in order from the backup target server 12 with the largest minimum backup prediction time to the data transfer server 13 with the smallest backup prediction time (step S21). After the process in step S21, the schedule creation unit 232 performs a processing to correct the throughput and backup prediction time considering the network concurrency (Figure 17).

[0097] The processing to correct throughput and backup prediction time considering network redundancy is performed for all combinations of backup target servers 12 and data transfer servers 13 for each backup job. In the processing to correct throughput and backup prediction time considering network redundancy, the schedule creation unit 232 first determines whether the same data path is being used during the same backup time (step S31).

[0098] If, in step S31, it is determined that the same data path is being used during the same backup time (step S31 is YES), the schedule creation unit 232 determines whether the total backup throughput of backup data transmitted using the same data path exceeds the network bandwidth of that data path (step S32). If, in step S32, it is determined that the network bandwidth is exceeded (step S32 is YES), the schedule creation unit 232 recalculates the backup throughput so that the throughput during the backup time fits within the network bandwidth (step S33).

[0099] If step S31 is determined to be NO, or if step S32 is determined to be NO, the schedule creation unit 232 sets the smaller of the network bandwidth of the data path used by the combination of the backup target server 12 and the data transfer server 13 and the standard backup throughput value as the backup throughput for that combination (step S34). After processing in step S33 or step S34, the schedule creation unit 232 corrects the backup prediction time using the calculated backup throughput (step S35). After processing in step S35, the provisional backup schedule table creation process by the schedule creation unit 232 is completed.

[0100] [Candidate backup schedule table creation process] Next, the process of creating a candidate backup schedule table by the schedule creation unit 232 will be described with reference to Figures 18 and 19. Figures 18 and 19 are flowcharts illustrating an example of the procedure for creating a candidate backup schedule table by the schedule creation unit 232. The candidate backup schedule table T13 is a table generated by the schedule creation unit 232 modifying the provisional backup schedule table T12, as described above.

[0101] First, the schedule creation unit 232 determines whether the total backup completion times in the provisional backup schedule table T12 fall within the backup window time (step S41). If it is determined in step S41 that the times fall within the backup window time (step S41 is YES), the schedule creation unit 232 calculates the path concurrency of the data path through which the backup data is transmitted and stores the calculated result in the candidate backup schedule table T13 (step S42).

[0102] If step S41 is determined to be NO, or after processing in step S42, the schedule creation unit 232 performs a correction process for assigning backup target servers to the data transfer server. In the correction process for assigning backup target servers to the data transfer server, the schedule creation unit 232 assigns the backup target server 12 with the latest backup completion time to the data transfer server 13 with the earliest backup completion time (step S43). The process in step S43 is the process described with reference to Figure 12.

[0103] Next, the schedule creation unit 232 corrects the throughput and backup prediction time, taking into account the network concurrency (step S44). The process in step S44 is the process described with reference to Figure 13.

[0104] After processing in step S44, the schedule creation unit 232 again determines whether the completion times of all backups in the provisional backup schedule table T12 fall within the backup window time (step S45). If it is determined in step S45 that all backups fall within the backup window time (step S45 is YES), the schedule creation unit 232 calculates the path concurrency of the data path through which the backup data is transmitted and stores the calculated result in the candidate backup schedule table T13 (step S46).

[0105] On the other hand, if step S45 determines that there is a backup completion time that does not fall within the backup window time (step S45 is NO), or after processing in step S46, the schedule creation unit 232 performs a process to rearrange the processing order of backup target servers assigned to the data transfer server (Figure 19).

[0106] In the process of reordering backup processing servers assigned to the data transfer server, the schedule creation unit 232 first changes the backup start time of the backup target server with the latest backup completion time to the earliest time in the backup process (step S51). Next, the schedule creation unit 232 corrects the throughput and backup prediction time taking into account the network concurrency (step S52).

[0107] After processing in step S52, the schedule creation unit 232 again determines whether the total backup completion time in the provisional backup schedule table T12 falls within the backup window time (step S53). If it is determined in step S53 that it falls within the backup window time (step S53 is YES), the schedule creation unit 232 calculates the path concurrency of the data path through which the backup data is transmitted and stores the calculated result in the candidate backup schedule table T13 (step S54).

[0108] After the processing in step S54, or if it is determined in step S53 that there is a backup completion time that does not fall within the backup window time (step S53 is NO), the schedule creation unit 232 performs the determination in step S55. In step S55, the schedule creation unit 232 determines whether the count value j, which indicates the number of backup processes (number of backup target servers 12) in the data transfer server 13 targeted in the processing so far, exceeds the number of data transfer servers 13. If it is determined in step S55 that "count value j ≤ number of backup processes in data transfer server 13" (step S55 is NO), the schedule creation unit 232 performs the reordering process of backup processing servers assigned to the data transfer server (steps S51 and S52).

[0109] On the other hand, if it is determined in step S55 that "count value j > number of backup processes in data transfer server 13" (step S55 is YES), the schedule creation unit 232 determines whether the count value i, which indicates the number of data transfer servers targeted in the processing so far, exceeds the actual number of data transfer servers 13 (step S56). If it is determined in step S56 that "count value i ≤ number of data transfer servers 13" (step S56 is NO), the schedule creation unit 232 performs the modification process for assigning backup target servers to the data transfer servers shown in Figure 18 (steps S43 and S44 in Figure 18).

[0110] On the other hand, if it is determined in step S56 that "count value i > number of data transfer servers 13" (step S56 is YES), the schedule creation unit 232 determines whether the number of candidate backup schedule tables T13 created in the processes so far is greater than 0 (step S57). If it is determined in step S57 that the number of created candidate backup schedule tables T13 is 1 or more (step S57 is YES), the candidate backup schedule table creation process by the schedule creation unit 232 is terminated.

[0111] On the other hand, if it is determined that the number of created candidate backup schedule tables T13 is 0 (step S57 is NO), the result output unit 24 notifies the administrator that there are no candidate backup schedules (step S58). For example, if the backup data volume increases rapidly more than expected, it may be possible to create only schedules in which the completion time of the backup process does not fit within the backup window, that is, it may not be possible to create candidate backup schedules. Even in such cases, according to this embodiment, the administrator is notified of this fact, so the administrator can take countermeasures before executing the backup process. After the processing in step S58, the candidate backup schedule table creation process by the schedule creation unit 232 is completed.

[0112] [Backup schedule determination process] Next, with reference to Figure 20, the backup schedule determination process by the schedule creation unit 232 will be described. Figure 20 is a flowchart showing an example of the procedure for the backup schedule determination process by the schedule creation unit 232. The process shown in Figure 20 is based on the premise that the schedule creation unit 232 creates multiple types of candidate backup schedule tables T13 depending on the desired effect. These multiple types of candidate backup schedule tables T13 include, for example, a candidate backup schedule table T13 that can shorten the backup completion time, and a candidate backup schedule table T13 that can increase the degree of data path distribution.

[0113] First, the schedule creation unit 232 determines whether the number of existing candidate backup schedule tables T13 is greater than "1" (step S61). If it is determined in step S61 that the number of candidate backup schedule tables T13 is greater than "1" (step S61 is YES), the schedule creation unit 232 performs the candidate backup schedule table selection process.

[0114] In the process of selecting a candidate backup schedule table, the schedule creation unit 232 determines whether the priority for schedule selection is the backup completion time or the degree of data path distribution (step S62). The schedule creation unit 232 can determine the priority for schedule selection based, for example, on user instructions on the candidate backup schedule selection screen Sc shown in Figure 21. The configuration of the candidate backup schedule selection screen Sc will be described later with reference to Figure 21.

[0115] If the priority for schedule selection is the backup completion time, the schedule creation unit 232 selects the candidate backup schedule table T13 with the earliest backup completion time (step S63). On the other hand, if the priority for schedule selection is the degree of data path dispersion, the schedule creation unit 232 selects the candidate backup schedule table T13 with the greatest degree of data path dispersion (step S64).

[0116] If step S61 is determined to be NO, or after processing in step S63 or step S64, the schedule creation unit 232 determines a backup schedule based on the selected candidate backup schedule table T13 (step S65). If step S61 is determined to be NO, that is, if the number of candidates in the candidate backup schedule table T13 is 1 or less, the schedule creation unit 232 determines a backup schedule based on that candidate backup schedule table T13. After processing in step S65, the backup schedule determination process by the schedule creation unit 232 is completed.

[0117] Figure 21 shows an example of the configuration of the candidate backup schedule selection screen Sc. As shown in Figure 21, the upper left of the candidate backup schedule selection screen Sc displays the options "fastest backup completion time" and "most distributed backup data paths used". In the example shown in Figure 21, the second option, "most distributed backup data paths used," is selected.

[0118] Below this option, a table titled "20yy / mm / dd Backup Schedule" is displayed. This table is the same as the graph shown in the lower part of Figure 13. In other words, it is a table in which the backup target servers 12 corresponding to each backup process in the data transfer server 13 are assigned in chronological order of the backup schedule. By selecting one of the options at the top of the table, the user can display schedules corresponding to the schedule selection priorities indicated in the option on the candidate backup schedule selection screen Scr.

[0119] Below the table are the OK button B1 and the Cancel button B2. When the user presses the OK button B1, the backup schedule displayed on the candidate backup schedule selection screen Scr is applied to each data transfer server 13.

[0120] <Updating the backup prediction time table> Next, with reference to Figure 22, the backup prediction time table update process by the schedule creation unit 232 will be described. Figure 22 is a flowchart showing an example of the procedure for updating the backup prediction time table by the schedule creation unit 232.

[0121] First, the schedule creation unit 232 obtains the configuration information of the backup target servers after the backup process (step S71). Next, based on the obtained configuration information, the schedule creation unit 232 updates the backup capacity and backup throughput values ​​for each backup target server 12 in the backup prediction time table T11 (step S72).

[0122] Next, the schedule creation unit 232 calculates the backup prediction time using the updated backup capacity and backup throughput values ​​(step S73). Then, the schedule creation unit 232 updates the provisional backup prediction time in the backup prediction time table T11 with the calculated backup prediction time (step S74). After the processing in step S74, the backup prediction time table update process by the schedule creation unit 232 is completed.

[0123] [Various effects] In the embodiment described above, the backup prediction time calculation unit 231 calculates the predicted backup time for each combination of the data transfer server 13 and the backup target server 12 based on the provisional backup throughput and the backup data usage capacity of the backup target server 12. The schedule creation unit 232 then sequentially assigns the backup processing of the backup target server 12 to the data transfer server 13 based on the backup prediction time information and the network usage information when performing backup processing, and creates a backup schedule based on the assignment results.

[0124] The time required for backup processing varies depending on the combination of the data transfer server 13 and the backup target server 12, the data capacity of the backup target server 12, the degree of network usage, etc. In this embodiment, a backup schedule is created taking these factors into consideration, so according to this embodiment, an appropriate backup schedule can be created even in systems where it is difficult to predict changes in the volume of backup data. Furthermore, according to this embodiment, since the backup schedule management device 2 automatically creates the backup schedule, the effort required for administrators to create or adjust the backup schedule can be eliminated.

[0125] Furthermore, in the embodiment described above, the schedule creation unit 232 assigns the backup process of the backup target server 12 to the data transfer server 13 that can minimize the predicted backup time. Therefore, according to this embodiment, a backup schedule is created that can further shorten the backup completion time.

[0126] Furthermore, in the embodiment described above, the schedule creation unit 232 adjusts the predicted backup time for each combination of data transfer server 13 and backup target server 12 to a longer time during periods when network usage is expected to increase due to the execution of backup processing. Therefore, according to this embodiment, a backup schedule can be created that is tailored to network usage.

[0127] Furthermore, in the embodiment described above, if there is a data transfer server 13 whose backup processing completion time does not fall within the backup window, the schedule creation unit 232 transfers the backup processing performed outside the backup window to the data transfer server 13 with the earliest backup processing completion time. Therefore, according to this embodiment, a backup schedule that takes the backup window into consideration can be created.

[0128] Furthermore, in the embodiment described above, the schedule creation unit 232 changes the order of backup processing for the backup target servers 12 assigned to the data transfer server 13 to an order that reduces network usage. Therefore, according to this embodiment, a backup schedule is created that can shorten the backup completion time.

[0129] Furthermore, in the embodiment described above, the result output unit 24 presents the user with both a candidate backup schedule prioritizing backup completion time and a candidate backup schedule prioritizing the degree of data path distribution. The schedule creation unit 232 then creates a backup schedule based on the candidate backup schedule selected by the user. Therefore, according to this embodiment, a backup schedule is created based on the user's priorities.

[0130] Furthermore, in the embodiment described above, the schedule creation unit 232 acquires information on the amount of backup data used by each of the multiple backup target servers 12 after the backup process based on the created backup schedule has been completed. The schedule creation unit 232 then calculates the backup prediction time based on the acquired information on the amount of backup data used, and updates the backup prediction time before the execution of the backup process with the calculated backup prediction time. Therefore, according to this embodiment, information on the actual values ​​of the backup process is fed back into the creation of the next backup schedule, making it possible to constantly improve the accuracy of backup schedule creation by the schedule creation unit 232.

[0131] In the embodiments described above, an example was given in which the backup schedule management system according to the present invention is applied to a virtualization system implemented using hypervisor technology, but the present invention is not limited thereto. The backup schedule management system according to the present invention may also be applied to a virtualization system implemented using other virtualization technologies such as containers. Furthermore, it may be applied to a system implemented without virtualization technology, as long as the combination of the backup target server 12 and the data transfer server 13 can be flexibly changed.

[0132] Furthermore, in the embodiments described above, the backup prediction time calculation unit 231 and the schedule creation unit 232 calculate the backup prediction time and create a backup schedule using values ​​stored in various tables, but the present invention is not limited to this. For example, in the backup schedule management system according to the present invention, the functions of the backup prediction time calculation unit 231 and the schedule creation unit 232 may be configured as a machine learning model, and the backup schedule may be output as an inference result from the machine learning model.

[0133] Furthermore, the embodiments described above are detailed and specific explanations of the system configuration in order to clearly illustrate the present invention, and are not necessarily limited to systems that have all the configurations described. In Figures 1 and 2, the control lines or information lines shown with solid lines or arrows are those considered necessary for explanation, and do not necessarily represent all control lines or information lines in the actual product. In practice, it can be assumed that almost all components are interconnected.

[0134] Furthermore, in this specification, processing steps describing chronological processing include not only processing performed chronologically in the order described, but also processing that is not necessarily performed chronologically but is performed in parallel or individually (for example, parallel processing or processing by objects). [Explanation of symbols]

[0135] 1...Server, 2...Backup Schedule Management Device, 11...Hypervisor, 12...Server to be Backed Up, 12a...VMA, 12b...VMB, 12c...VMC, 12d...VMD, 12e...VME, 12k...VMK, 13...Data Transfer Server, 13j...VMJ, 13k...VMK, 13l...VML, 13m...VMM, 13n...VMN, 14...Data Storage Server, 14n...VMN, 21...Backup Configuration Information Acquisition Unit, 22...VM Configuration Information Acquisition Unit, 23...Schedule Management Unit, 24...Result Output Unit, 100...Backup Schedule Management System, 231...Backup Prediction Time Calculation Unit, 232...Schedule Creation Unit, T1...Backup Job Table, T11...Backup Prediction Time Table, T12...Provisional Backup Schedule Table, T13...Candidate Backup Schedule Table, T2...VM Configuration Information Table, T3...Backup Data Path Table

Claims

1. A backup schedule creation device for creating a backup schedule for backup processing in a backup schedule management system in which a plurality of backup target servers having backup data to be backed up to a data storage server, and a plurality of data transfer servers that acquire the backup data from the backup target servers and transfer it to the data storage server are connected to each other via a network, A backup prediction time calculation unit calculates the estimated backup time for each combination of the data transfer server and the backup target server based on the estimated backup throughput during the transmission of the backup data and the capacity used by the backup target server for the backup data. The system includes a scheduling unit that, based on the backup prediction time information and the network usage information when performing the backup process, sequentially assigns the backup process of the backup data of the backup target server to the data transfer server, and creates the backup schedule based on the assignment results. Backup schedule creation device.

2. The scheduling unit assigns the backup process of the backup target server to the data transfer server that can minimize the predicted backup time. The backup schedule creation device according to claim 1.

3. The backup prediction time calculation unit calculates the backup time based on network bandwidth information in the network path connecting the data transfer server and the backup target server. The estimated backup throughput is calculated as described above. The backup schedule creation device according to claim 2.

4. The scheduling unit adjusts the predicted backup time for each combination of data transfer servers and backup target servers to a longer time during periods when it is expected that the network usage will be high due to the execution of the backup process in multiple combinations of data transfer servers and backup target servers. The backup schedule creation device according to claim 3.

5. If there is a data transfer server whose backup process completion time does not fall within the backup window, the scheduling unit will transfer the backup process performed outside the backup window to the data transfer server whose backup process completion time is earliest. The backup schedule creation device according to claim 4.

6. The schedule creation unit changes the order of backup processing for the backup target servers assigned to the data transfer server to an order that reduces the usage of the network. The backup schedule creation device according to claim 5.

7. When the schedule creation unit determines that there is a time period in the backup schedule in which network usage can be reduced, it changes the order of backup processing of the backup target servers assigned to the data transfer server to an order that reduces network usage during the time period in which network usage can be reduced. The backup schedule creation device according to claim 5.

8. The schedule creation unit creates backup schedule candidates that shorten the completion time of the backup process and backup schedule candidates that reduce the degree of network usage. Based on pre-set priorities or instructions entered via the operation input unit, it selects one of the candidates and creates the backup schedule based on the selected candidate. The backup schedule creation device according to claim 6.

9. The schedule creation unit, after the completion of the backup process based on the created backup schedule, obtains information on the backup data usage capacity of each of the multiple backup target servers, calculates the backup prediction time based on the obtained backup data usage capacity information, and updates the backup prediction time before the execution of the backup process with the calculated backup prediction time. The backup schedule creation device according to claim 8.

10. A backup creation method using a backup schedule creation device that creates a backup schedule for backup processing in a backup schedule management system in which multiple backup target servers having backup data to be backed up to a data storage server, and multiple data transfer servers that acquire the backup data from the backup target servers and transfer it to the data storage server are connected to each other via a network, A backup prediction time calculation unit calculates the backup prediction time for each combination of the data transfer server and the backup target server based on the estimated backup throughput during the transmission of the backup data and the capacity used for the backup data on the backup target server. The procedure includes: a schedule creation unit sequentially assigning backup processing of the backup data of the backup target server to the data transfer server based on the backup prediction time information and the network usage information when performing the backup processing, and creating the backup schedule based on the assignment results. How to create a backup schedule.

Images