Backup schedule preparation apparatus and backup schedule preparation 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 technology]

[0002] In recent years, an increasing number of systems that have data that needs to be backed up are equipped with data transfer servers. A data transfer server is a server that transfers data to be backed up (hereinafter also referred to as "backup data") to backup storage. Even if a system contains multiple machines that are the target of backup processing, by placing multiple data transfer servers in the system, it becomes possible to execute backup processing in parallel. In such systems, it is required that all backup processing be completed within a limited backup allowable time (hereinafter also referred to as "backup window").

[0003] For example, a backup management program described in Patent Document 1 acquires from each data transfer device a first data amount sent to the backup storage and a second data amount not sent to the backup storage due to the deduplication function, among the data previously allocated to each data transfer device. The backup management program also calculates the amount of data previously sent from the multiple data transfer devices to the backup storage based on the acquired first data amount. The backup management program also calculates the next amount of data to be sent to the backup storage based on the acquired first and second data amounts and the size of the data to be backed up. The backup management program also increases or decreases the number of multiple data transfer devices based on the result of comparing the calculated amount of data previously sent with the calculated amount of data to be sent next. The technology described in Patent Document 1 makes it possible to control resources used for backup so that backup is completed within an expected time.

[0004] For example, a job scheduler described in Patent Document 2 receives inputs from an archive management system, including task information, replica placement data, infrastructure topology data, and resource performance data. The job scheduler then models a flow network representing the archive management system's data content, software programs, physical devices, and communication capacity 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 generates 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 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 Summary of the Invention [Problem to be solved by the invention]

[0006] In recent years, backup data can increase rapidly due to factors such as the ease of scaling environments and the rapid growth of data. When backup data increases rapidly, it is possible that the backup process will not be completed within the backup window for the combination of a pre-configured data transfer server and a machine to be backed up. If the backup process is not completed within the backup window, the RPO (Recovery Point Objective) will not be met.

[0007] The present invention has been made in consideration of the above circumstances, and an object of the present invention is to make it possible to create an appropriate backup schedule even in a system in which changes in the volume of backup data are difficult to predict. [Means for solving the problem]

[0008] A backup schedule creation device according to one aspect of the present invention creates a backup schedule for backup processing in a backup schedule management system in which multiple backup target servers, each having backup data to be backed up to a data storage server, and multiple data transfer servers, which acquire the backup data from the backup target servers and transfer it to the data storage servers, are connected to one another via a network. The backup schedule creation device according to one aspect of the present invention includes: a predicted backup time calculation unit that calculates a predicted backup time for each combination of the data transfer server and the backup target server based on an estimated backup throughput during backup data transmission and the amount of backup data used in the backup target servers; and a schedule creation unit that assigns backup processing of the backup data of the backup target servers to the data transfer servers in order based on information about the predicted backup time and information about the network usage when the backup processing is performed, 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 a system in which changes in the volume of backup data are difficult to predict. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram illustrating a schematic configuration example of a backup schedule management system according to an embodiment of the present invention. [Figure 2] 1 is a block diagram showing an example of the hardware configuration of a server and a backup schedule management device that constitute a backup schedule management system according to an embodiment of the present invention; [Figure 3] FIG. 10 is a diagram illustrating an example of the configuration of a backup job table according to an embodiment of the present invention. [Figure 4] FIG. 4 is a diagram illustrating an example of a configuration of a VM configuration information table according to an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram illustrating an example of the configuration of a backup data path table according to an embodiment of the present invention. [Figure 6] FIG. 10 is a diagram showing an example of the configuration of a backup predicted time table according to an embodiment of the present invention. [Figure 7] 10 is a graph showing the length of the estimated provisional backup time for each combination of the backup target server and data transfer server shown in the estimated backup time table according to one embodiment of the present invention. [Figure 8] FIG. 10 is a diagram showing an example of the configuration of a provisional backup schedule table according to an embodiment of the present invention. [Figure 9] FIG. 10 is a diagram showing an example of correspondence between backup target servers and data transfer servers after allocation processing is performed by a schedule creation unit according to an embodiment of the present invention. [Figure 10]FIG. 10 is a diagram showing an example of the configuration of a candidate backup schedule table, which is a modified interim backup schedule table according to an embodiment of the present invention. [Figure 11] FIG. 10 is a diagram showing an overview of a process for modifying a provisional backup schedule table by a schedule creation unit according to an embodiment of the present invention. [Figure 12] FIG. 10 is a diagram showing an overview of a process for modifying a provisional backup schedule table by a schedule creation unit according to an embodiment of the present invention. [Figure 13] FIG. 10 is a diagram showing an overview of a process for modifying a provisional backup schedule table by a schedule creation unit according to an embodiment of the present invention. [Figure 14] 10 is a flowchart illustrating an example of a procedure for a backup schedule management process performed by a backup schedule management system according to an embodiment of the present invention. [Figure 15] 10 is a flowchart illustrating an example of a procedure for a predicted backup time table creation process performed by a predicted backup time calculation unit according to an embodiment of the present invention. [Figure 16] 10 is a flowchart illustrating an example of a procedure for creating a provisional backup schedule table by a schedule creation unit according to an embodiment of the present invention. [Figure 17] 10 is a flowchart illustrating an example of a procedure for creating a provisional backup schedule table by a schedule creation unit according to an embodiment of the present invention. [Figure 18] 10 is a flowchart illustrating an example of a procedure for creating a candidate backup schedule table by a schedule creating unit according to an embodiment of the present invention. [Figure 19] 10 is a flowchart illustrating an example of a procedure for creating a candidate backup schedule table by a schedule creating unit according to an embodiment of the present invention. [Figure 20] 10 is a flowchart illustrating an example of a procedure for a backup schedule determination process performed by a schedule creation unit according to an embodiment of the present invention. [Figure 21]FIG. 10 is a diagram showing an example of the configuration of a candidate backup schedule selection screen according to an embodiment of the present invention. [Figure 22] 10 is a flowchart illustrating an example of a procedure for updating a predicted backup time table by a schedule creation unit according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In each drawing, the same components are designated by the same reference numerals. The following description and drawings are examples for explaining the present invention, and for clarity of explanation, appropriate omissions and simplifications have been made. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0012] <Configuration of the backup schedule management system> First, the configuration of a backup schedule management system 100 according to an embodiment of the present invention will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the schematic configuration of the backup schedule management system 100.

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

[0014] The server 1a is configured with a VMA 12a and a VMJ 13j, the server 1b is configured with a VMK 12k and a VMB 12b, the server 1c is configured with a VMC 12c to a VME 12e, and the server 1d is configured with a VML 13l, a VMN 13n, and a VMN 14n.

[0015] VMA 12a to VME 12e are backup target servers 12 having backup data. VMJ 13j to VMM 13m enclosed in a dashed-dotted line frame in the figure are data transfer servers 13 that collect backup data from the backup target servers 12 and store it in the data storage server 14. VMN 14n enclosed in a dashed-dotted line frame in the figure is the data storage server 14 in which backup data of VMA 12a to VME 12e collected based on the backup processing by the data transfer server 13 is stored.

[0016] The backup schedule management device 2 (an example of a backup schedule creation device) creates a schedule for backup processing. The backup schedule management device 2 then notifies the VMJ 13j to VMM 13m of the data transfer server 13 of the created backup schedule and the result of a determination as to whether 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 placed on the servers 1, and the ratio of the backup target servers 12, the data transfer servers 13, and the data storage servers 14 are not limited to the example shown in Fig. 1. Furthermore, the backup target servers 12, the data transfer servers 13, and the data storage servers 14 may be provided in a cloud environment or the like.

[0018] The backup schedule management device 2 includes 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 FIG. 3). The backup configuration information is information about each element that makes up a backup job, which is a backup processing job. An example of the configuration of the backup job table T1 will be described in detail below with reference to FIG. 3.

[0020] The VM configuration information acquisition unit 22 acquires configuration information of each server 1 constituting the backup schedule management system 100, and acquires 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 FIG. 4) based on the acquired configuration information. The VM configuration information acquisition unit 22 also creates a backup data path table T3 (see FIG. 5) based on the acquired configuration information. A configuration example of the VM configuration information table T2 will be described in detail with reference to FIG. 4, which will be described later, and a configuration example of the backup data path table T3 will be described in detail with reference to FIG. 5, which will be described later.

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

[0022] The schedule creation unit 232 creates a tentative backup schedule table T12 (see FIG. 7) based on the information stored in the predicted backup time table T11. The tentative backup schedule table T12 is a table showing the results of assigning data transfer servers with good compatibility to backup target servers in descending order of the predicted backup time. The tentative backup schedule table T12 will be described in detail later with reference to FIG. 7.

[0023] The schedule creation unit 232 also modifies the interim backup schedule table T12 based on information such as the degree of dispersion of data path usage during backup processing and the relationship between the backup throughput and the network bandwidth for each data path. The schedule creation unit 232 then sets the modified interim 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 that provide different effects. For example, the schedule creation unit 232 can create candidate backup schedule tables T13 that correspond to a backup schedule that achieves the shortest backup completion time and a backup schedule that achieves the greatest degree of network dispersion during backup processing.

[0024] Furthermore, the schedule creation unit 232 creates a backup schedule using a candidate backup schedule table T13 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 predicted backup time table T11 (see FIG. 6) using the processing results.

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

[0026] The database Db stores a backup job table T1, a VM configuration information table T2, a backup data path table T3, a predicted backup time table T11, a provisional backup schedule table T12, a candidate backup schedule table T13, and the like.

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

[0028] The computer 200 includes a control unit 210, a nonvolatile storage 220, a display unit 230, an operation input unit 240, and a communication I / F (Interface) 250, which are all connected to a bus B.

[0029] The control unit 210 includes a central processing unit (CPU) 211, a read only memory (ROM) 212, and a random access memory (RAM) 213.

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

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

[0032] The nonvolatile storage 220 may be, for example, a hard disk drive (HDD), a solid state drive (SSD), a flexible disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, or a nonvolatile memory card. In addition to the OS and various parameters, the nonvolatile storage 220 also stores programs for operating the computer 200. The programs may also be stored in the ROM 212.

[0033] The display unit 230 is, for example, a monitor configured with an LCD (Liquid Crystal Display) or the like, and displays the results of processing performed by the computer 200, etc. The operation input unit 240 is configured with, for example, a keyboard, a mouse, a touch sensor, etc., and generates an operation signal according to an operation by a user and supplies it to the CPU 211. The display unit 230 and the operation input unit 240 may be integrated into a touch panel.

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

[0035] The communication I / F 250 may be, for example, a network interface card (NIC), and may transmit and receive various data to and from external devices via a network or communication line.

[0036] <Configuration of backup job table T1> Next, the configuration of the backup job table T1 will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the configuration of the backup job table T1.

[0037] As shown in Figure 3, the backup job table T1 has 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 information about the job name of the backup job. The "VM Name" field stores information about the name given to the VM (VM name). The "VM Role" field stores information about the role assigned to the VM (VM role). For example, the VM role stores one of the following as shown in the figure: "Backup Target," "Data Transfer," or "Data Storage."

[0039] The "Platform" field stores information about the name of the platform that realizes 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" item stores information about the backup format of the next backup process to be performed on the backup target server 12. In the example shown in Fig. 3, the "next backup format" item stores "incremental," "full," "null," etc. "Incremental" indicates an incremental backup that backs up data that has increased since the previous backup process was performed, while "full" indicates a full backup that backs up all data. "null" indicates no backup.

[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 predicted backup time table T11 shown in Figure 6, which will be described later.

[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 VMA12a, which is the backup target server 12. 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 Placement Host", and "Used Capacity of VM (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 Placement Host" column, information about the host (server) on which the VM is placed is stored. In the "Used Capacity of VM" 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 the VM role of VMA12a with the VM name "VMA" is "Backup Target (Server)", the host on which VMA12a is placed is "Server la", 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 FIG. 5, the backup data path table T3 has the following items: "Data path number," "Source host," "Destination host," and "Network bandwidth between hosts (Mb / s)."

[0047] The "data path number" field stores information about the data path number, which is a number that identifies the path of the backup data. The "source host" field stores information about the name of the server 1 on which 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 the server 1 on which 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 that occupies 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 of the backup data path table T3 shown in Fig. 5 indicates that the data path with data path number "1" has both source host and destination host "Server 1a" and the inter-host network bandwidth is "null." The second record from the top indicates that the data path with data path number "2" has source host "Server 1a" and destination host "Server 1b," and the inter-host network bandwidth is "1000 (Mb / s)."

[0049] <Backup prediction time table> Next, the configuration of the predicted backup time table T11 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the configuration of the predicted backup time table T11. The predicted backup time table T11 is a table created by the predicted backup time calculation unit 231 of the schedule management unit 23 based on the information listed 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 predicted time table T11 has the following items: "Combination number," "Backup target server," "VM usage capacity (GB)," "Data transfer server," "Data path number," "Temporary backup throughput (Mb / s)," and "Temporary backup predicted time (minutes)."

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

[0052] The "Backup target server" field stores information on the name of the backup target server 12. The "VM usage capacity (GB)" field stores information on the data usage capacity of the backup target server 12. The "Data transfer server" field stores information on the name of the data transfer server 13. The "Data path number" field stores information on the data path number of the data path used in the combination of the backup target server 12 and the data transfer server 13.

[0053] The "provisional backup throughput (Mb / s)" field stores the estimated backup throughput value derived from information about the data path and the network bandwidth occupied when using that data path as the provisional backup throughput.

[0054] The "predicted tentative backup time (minutes)" field stores the estimated backup time calculated from the backup capacity of the VM and the provisional backup throughput as the provisional backup time.

[0055] 6 indicates that the data usage capacity of the VMA 12a of the 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 virtual backup throughput is "100 (Mb / s)," and the virtual backup predicted time is "20 (minutes)."

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

[0057] <Configuration of interim backup schedule table> Next, the configuration of the interim backup schedule table T12 will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of the configuration of the interim backup schedule table T12. As shown in Figure 8, the provisional backup schedule table T12 has the following items: "Job name," "Backup target server," "Data transfer server," "Backup capacity (GB)," "Provisional backup throughput (Mb / s)," "Provisional backup estimated time (minutes)," "Data path number," "Backup start time," and "Backup end time."

[0058] The "job name" field stores information about the job name of the backup job. The "backup target server" field stores information about the name of the backup target server 12. The "data transfer server" field stores information about the name of the data transfer server 13. The "backup capacity (GB)" field stores information about the capacity of the backup data of the backup target server 12.

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

[0060] 8, information is entered about the backup process of backup data from VMA 12a of the backup target server 12 to VMJ 13j of the data transfer server 13, for a job with the job name Job A. The top record also indicates that the backup capacity of VMA 12a is "40 (GB)", the provisional backup throughput is "100 (Mb / s)", and the predicted backup time is "120 (minutes)". The top record also indicates that the data path number of the network used by the combination of VMA 12a and VMJ 13j is "1", the backup start time is "3:00", and the backup end time is "5:00".

[0061] The schedule creation unit 232 (see FIG. 1) of the schedule management unit 23 performs a process of allocating the backup target servers 12 to the data transfer servers 13 based on the contents of the provisional backup schedule table T12. At this time, the schedule creation unit 232 allocates the backup target servers 12 to the data transfer servers 13 in order starting from the backup target server 12 with the longest minimum predicted backup time.

[0062] 7, for example, the predicted backup time for VMA 12a, which is the backup target server 12, is the shortest when paired with VML 13l, which is the data transfer server 13. Similarly, the predicted backup time for VMB 12b is the shortest when paired with VMK 13k, and the predicted backup time for VMC 12c is the shortest when paired with VML 13l. Furthermore, the predicted backup time for VMD 12d is the shortest when paired with VMJ 13j. Of these shortest predicted backup times, allocation to the data transfer servers 13 is performed in descending order of the predicted backup time.

[0063] 9 is a diagram showing an example of the correspondence between the backup target servers 12 and the data transfer servers 13 after the allocation process has been performed by the schedule creation unit 232. The vertical axis of Fig. 9 indicates the data transfer servers 13, and the horizontal axis indicates the time axis from the backup start time to the backup end time. In Fig. 9, in order to make it easier to understand the explanation of the allocation process of the backup target servers 12 to the data transfer servers 13, an example is given in which there are more backup target servers 12 than those shown in Fig. 1 (there are VMs after the VMF).

[0064] 9, VMF, which is the backup target server 12 with the longest predicted backup time, and VMD 12d, which is the next longest predicted backup time, are assigned to VMJ 13j, which is the data transfer server 13, in order of earliest backup start time. Also, VMB 12b, which is the longest predicted backup time, VMC 12c, which is the next longest predicted backup time, and VMH, which is the next longest predicted backup time, are assigned to VMK 13k, in order of earliest backup start time.

[0065] The process in which the schedule creation unit 232 assigns an earlier backup processing time to a backup target server 12 having a longer predicted backup time by the data transfer server 13 is an example, and the present invention is not limited to this. The schedule creation unit 232 may assign an earlier schedule time to the data transfer server 13 in order of the backup target server 12 having the shortest predicted backup time.

[0066] After completing the allocation of the backup target servers 12 to the data transfer servers 13, the schedule creation unit 232 modifies the interim backup schedule table T12 based on the backup window information and information on the degree of dispersion of the network routes used during backup processing. Then, the schedule creation unit 232 sets the modified interim backup schedule table T12 as the candidate backup schedule table T13.

[0067] Fig. 10 is a diagram showing an example of the configuration of a candidate backup schedule table T13, which is the modified interim backup schedule table T12. Fig. 11 is a diagram showing an overview of the modification process of the interim backup schedule table T12 by the schedule creation unit 232. The vertical axis of Fig. 11 shows the data transfer server 13, and the horizontal axis shows the time axis from the backup start time to the backup end time.

[0068] The candidate backup schedule table T13 shown in Fig. 10 differs from the pre-correction interim backup schedule table T12 in that it includes an item for "path multiplicity counter." The other items are the same as the items in the interim backup schedule table T12 shown in Fig. 8, so a description of the overlapping items will be omitted.

[0069] The "route multiplicity counter" field stores a counter value indicating the multiplicity of network routes. The multiplicity of network routes indicates the degree of network usage during backup data transmission. If a route used during the same time period in the backup schedule overlaps with a route for other backup data, the value of the route multiplicity counter is counted up. The schedule creation unit 232 modifies the value of the provisional backup throughput in the provisional backup schedule table T12 based on the count value stored in the "route multiplicity counter" field.

[0070] 10, the virtual backup throughput value for the backup job named job A when sending backup data from VMA 12a to VMJ 13j is corrected from "100 (minutes)" to "150 (minutes)." This correction was made by the schedule creation unit 232 because other backup data is also being transmitted during the same time period on the path with data path number "1."

[0071] 11 shows an example in which the predicted backup time of the VMF of the backup target server 12 assigned to VMJ 13j of the data transfer server 13, the predicted backup time of the VMC 12c assigned to VMK 13k, and the predicted backup time of the VMA 12a assigned to VML 13l are each corrected to a larger (longer) time. This correction was made by the schedule creation unit 232 because the backup data of the VMF, VMC 12c, and VMA 12a, which are the backup target servers 12, are transmitted using the same data path in the same time period.

[0072] Furthermore, if there are overlapping paths for transmitting backup data during the same time period when backup processing is performed, the schedule creation unit 232 modifies the provisional backup throughput so that the network throughput on the path falls within the bandwidth.The schedule creation unit 232 then recalculates the provisional backup predicted time based on the modified provisional backup throughput.The schedule creation unit 232 also recalculates the backup start and backup end times based on the recalculated provisional backup throughput and provisional predicted backup time values.

[0073] If there is a combination in the candidate backup schedule table T13 where the backup end 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 the backup data is sent, and so on.

[0074] 12 and 13 are diagrams showing an overview of the process of modifying the provisional backup schedule table T12 by the schedule creation unit 232. The vertical axis of Fig. 12 and Fig. 13 indicates the data transfer server 13, and the horizontal axis indicates the time axis from the backup start time to the backup end time.

[0075] 12, among the data transfer servers 13 assigned to VMJ 13j of the data transfer server 13, the time at which the backup data of VMB 12b is transmitted falls outside the backup window indicated by the solid rectangular frame in the drawing. Therefore, the schedule creation unit 232 changes the data transfer server 13 to which the backup data of VMB 12b is transferred to VMK 13k, which has the earliest backup end time.

[0076] The middle part of FIG. 12 shows a state in which the data transfer server 13 that transfers the backup data of VMB 12b has been changed from VMJ 13j to VMK 13k.

[0077] If there is a time period in which the networks used overlap in the changed schedule of the data transfer server 13, the schedule creation unit 232 modifies the predicted backup time of the backup data in that time period.

[0078] In the lower part of Figure 12, the predicted backup time of the backup data of VMD12d assigned to VMK13k, which is the data transfer server 13, and the predicted backup time of the backup data of VMG assigned to VML13l have each been revised to a larger (longer) time.

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

[0080] The top part of Fig. 13 shows the same schedule as the bottom part of Fig. 12. The middle part of Fig. 13 shows a state in which the time for transferring backup data of VMB12b assigned to VMK13k, which is the data transfer server 13, has been switched to the earliest time slot. This adjustment by the schedule creation unit 232 reduces the network multiplicity in the latter half (late time) of the backup schedule. Furthermore, the reduction in network multiplicity shortens the time required to transfer backup data, and the predicted backup time also shortens.

[0081] The lower part of Figure 13 shows how the predicted backup time of the backup data of VMD12d assigned to VMK13k, which is the data transfer server 13, and the predicted backup time of the backup data of VMH assigned to VML13l have each been shortened.

[0082] The result output unit 24 presents the adjusted tentative backup schedule table T12' as a candidate backup schedule table T13 to the user via the display unit 230 (see FIG. 2). Then, the schedule management unit 23 creates a final backup schedule based on instructions from the user who has checked the candidate backup schedule table T13.

[0083] <Backup schedule management process> Next, a description will be given of a backup schedule management method performed by the backup schedule management system 100 according to this embodiment.

[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 of the server 1 and the VMs. Then, the backup configuration information acquisition unit 21 creates a backup job table T1, and the VM configuration information acquisition unit 22 creates a VM configuration information table T2 and a backup data path table T3 (step S1).

[0085] Next, the predicted backup time calculation unit 231 of the schedule management unit 23 performs a process of creating a predicted backup time table (step S2). The process of creating a predicted backup time table in step S2 will be described in detail with reference to the following FIG.

[0086] Next, the schedule creation unit 232 of the schedule management unit 23 performs a process of creating a provisional backup schedule table (step S3). The process of creating a provisional backup schedule table in step S3 will be described in detail later with reference to FIGS.

[0087] Next, the schedule creation unit 232 performs candidate backup schedule table creation processing (step S4). The candidate backup schedule table creation processing in step S4 will be described in detail later with reference to FIGS.

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

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

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

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

[0092] In the virtual backup throughput calculation process, the predicted backup 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 predicted backup time calculation unit 231 determines whether the transmission of backup data between the backup target server 12 and the data transfer server 13 is performed within the same server 1.

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

[0094] After the processing of step S14 or step S15, the predicted backup time calculation unit 231 performs a process of calculating the predicted backup time. The calculation process of the predicted backup time is performed on all records corresponding to all combinations of the backup target server 12 and the data transfer server 13. In the calculation process of the predicted backup time, the predicted backup time calculation unit 231 calculates the predicted backup time by dividing the backup capacity by the virtual backup throughput (step S16). After the processing of step S16, the process of creating a predicted backup time table by the predicted backup time calculation unit 231 ends.

[0095] [Provisional backup schedule table creation process] 16 and 17, a description will be given of a process for creating a provisional backup schedule table by the schedule creation unit 232 of the schedule management unit 23. Figures 16 and 17 are flowcharts showing an example of the procedure for a process 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 a process of allocating the backup target servers 12 to the data transfer servers 13. The process of allocating the backup target servers 12 to the data transfer servers 13 is performed the same number of times as the number of the backup target servers 12. In the process of allocating the backup target servers 12, the schedule creation unit 232 allocates the backup target servers 12 to the data transfer servers 13 that have the shortest predicted backup times, starting with the backup target server 12 with the largest minimum predicted backup time (step S21). After the process of step S21, the schedule creation unit 232 performs a process of correcting the throughput and predicted backup time (FIG. 17) in consideration of the network multiplicity.

[0097] The process of correcting the throughput and the predicted backup time taking into account the network multiplicity is performed for all combinations of the backup target server 12 and the data transfer server 13 for each of all backup jobs. In the process of correcting the throughput and the predicted backup time taking into account the network multiplicity, the schedule creation unit 232 first determines whether the same data path is being used during the same backup time (step S31).

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

[0099] If step S31 is judged as NO, or if step S32 is judged as NO, the schedule creation unit 232 sets the smaller of the network bandwidth and standard backup throughput value of the data path used by the combination of the backup target server 12 and the data transfer server 13 as the backup throughput of that combination (step S34). After processing step S33 or step S34, the schedule creation unit 232 corrects the predicted backup time using the calculated backup throughput (step S35). After processing step S35, the process of creating a tentative backup schedule table by the schedule creation unit 232 ends.

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

[0101] First, the schedule creation unit 232 determines whether the end time of all backups in the provisional backup schedule table T12 falls within the backup window time (step S41). If it is determined in step S41 that it falls within the backup window time (YES in step S41), the schedule creation unit 232 calculates the path multiplicity 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 judged as NO, or after the processing of step S42, the schedule creation unit 232 performs processing to correct the allocation of backup target servers to data transfer servers. In the processing to correct the allocation of backup target servers to data transfer servers, the schedule creation unit 232 performs processing to assign the backup target server 12 with the latest backup end time to the data transfer server 13 with the earliest backup end time (step S43). The processing of step S43 is the processing described with reference to FIG. 12.

[0103] Next, the schedule creation unit 232 corrects the throughput and the predicted backup time in consideration of the network multiplicity (step S44). The process of step S44 is the process described with reference to FIG.

[0104] After processing step S44, the schedule creation unit 232 again determines whether the end times of all backups in the provisional backup schedule table T12 are within the backup window time (step S45). If it is determined in step S45 that all backups are within the backup window time (YES in step S45), the schedule creation unit 232 calculates the path multiplicity 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 it is determined in step S45 that there is a backup end time that does not fall within the backup window time (NO in step S45), or after the processing of step S46, the schedule creation unit 232 performs a process of rearranging the processing order of the backup target servers assigned to the data transfer server (FIG. 19).

[0106] In the process of rearranging the order of the 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 end time to the earliest time in the backup process (step S51). Next, the schedule creation unit 232 corrects the throughput and the predicted backup time taking into account the network multiplicity (step S52).

[0107] After processing step S52, the schedule creation unit 232 again determines whether the end time of all backups 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 (YES in step S53), the schedule creation unit 232 calculates the path multiplicity 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 process of step S54, or if it is determined in step S53 that there is a backup end time that does not fall within the backup window time (NO in step S53), the schedule creation unit 232 makes a determination in step S55. In step S55, the schedule creation unit 232 determines whether or not the count value j, which indicates the number of backup processes (the number of backup target servers 12) in the data transfer server 13 that has been the target of the processes up to this point, exceeds the number of data transfer servers 13. If it is determined in step S55 that "count value j≦number of backup processes in the data transfer server 13" (NO in step S55), the schedule creation unit 232 performs a process of rearranging the order of the backup processing servers assigned to the data transfer servers (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 the data transfer server 13" (YES in step S55), the schedule creation unit 232 determines whether or not the count value i, which indicates the number of data transfer servers targeted in the processing up to that point, 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" (NO in step S56), the schedule creation unit 232 performs processing to correct the allocation of backup target servers to data transfer servers in Fig. 18 (steps S43 and S44 in Fig. 18).

[0110] On the other hand, if it is determined in step S56 that "count value i>number of data transfer servers 13" holds (YES in step S56), the schedule creation unit 232 determines whether the number of candidate backup schedule tables T13 created in the processing up to this point is greater than 0 (step S57). If it is determined in step S57 that the number of candidate backup schedule tables T13 that have already been created is 1 or greater (YES in step S57), the candidate backup schedule table creation processing by the schedule creation unit 232 ends.

[0111] On the other hand, if it is determined that the number of created candidate backup schedule tables T13 is 0 (NO in step S57), 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 more rapidly than expected, it may be possible to create only a schedule that does not allow the backup process to finish within the backup window, i.e., no candidate backup schedule can be created. Even in such a case, according to this embodiment, the administrator is notified of this fact, allowing the administrator to take measures before executing the backup process. After processing in step S58, the candidate backup schedule table creation process by the schedule creation unit 232 ends.

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

[0113] First, the schedule creation unit 232 determines whether the number of created 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" (YES in step S61), the schedule creation unit 232 performs a candidate backup schedule table selection process.

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

[0115] If the priority in 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 in 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 the determination in step S61 is NO, or after the processing of 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 the determination in step S61 is NO, that is, if the number of candidate backup schedule tables T13 is one or less, the schedule creation unit 232 determines a backup schedule based on that candidate backup schedule table T13. After the processing of step S65, the backup schedule determination process by the schedule creation unit 232 ends.

[0117] Fig. 21 is a diagram showing an example of the configuration of the candidate backup schedule selection screen Sc. As shown in Fig. 21, the upper left corner of the candidate backup schedule selection screen Sc displays two options: "Fastest backup completion time" and "Most divergent backup data path used." The example shown in Fig. 21 shows that the second option, "Most divergent backup data path used," has been selected.

[0118] Below this option, a table titled "20yy / mm / dd Backup Schedule" is displayed. This table is the graph shown in the lower part of Figure 13. In other words, this 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 a schedule corresponding to the schedule selection priority shown in the option on the candidate backup schedule selection screen Sc.

[0119] Below the table, an enter button B1 and a cancel button B2 are arranged. When the enter button B1 is pressed by the user, the backup schedule displayed on the candidate backup schedule selection screen Sc is applied to each data transfer server 13.

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

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

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

[0123] [Various effects] In the above-described embodiment, the predicted backup 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 virtual backup throughput and the backup data usage capacity of the backup target server 12. Furthermore, the schedule creation unit 232 assigns backup processing of the backup target server 12 to the data transfer servers 13 in order based on information on the predicted backup time and information on the network usage level 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, and so on. In this embodiment, a backup schedule is created taking these factors into consideration, so that an appropriate backup schedule can be created even in a system where changes in the volume of backup data are difficult to predict. Furthermore, in this embodiment, the backup schedule management device 2 automatically creates a backup schedule, saving the administrator or the like the trouble of creating and adjusting the backup schedule.

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

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

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

[0128] Furthermore, in the above-described embodiment, 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 enables a reduction in the degree of network usage. Therefore, according to this embodiment, a backup schedule that enables a shorter backup completion time is created.

[0129] In the embodiment described above, the result output unit 24 presents the user with both a candidate backup schedule that prioritizes backup completion time and a candidate backup schedule that prioritizes 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 based on the user's priorities is created.

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

[0131] In the above-described embodiment, 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 to this. 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, the backup schedule management system according to the present invention may also be applied to a system implemented without using virtualization technology, as long as the system allows for dynamic changes to the combination of the backup target server 12 and the data transfer server 13.

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

[0133] Furthermore, the above-described embodiment has described the system configuration in detail and specifically to clearly explain the present invention, and is not necessarily limited to a system having all of the described configurations. The control lines or information lines indicated by solid lines or arrows in Figures 1 and 2 indicate those considered necessary for explanation, and do not necessarily indicate all of the control lines or information lines in the product. In reality, it can be considered that almost all of the configurations are interconnected.

[0134] Furthermore, in this specification, processing steps describing chronological processing include not only processing that is 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...backup target server, 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 predicted time calculation unit, 232...schedule creation unit, T1...backup job table, T11...backup predicted time table, T12...provisional backup schedule table, T13...candidate backup schedule table, T2...VM configuration information table, T3...backup data path table

Claims

1. 1. 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 in a data storage server and a plurality of data transfer servers that acquire the backup data from the backup target servers and transfer the backup data to the data storage servers are connected to each other via a network, a backup predicted time calculation unit that calculates a backup predicted time for each combination of the data transfer server and the backup target server based on an estimated backup throughput during transmission of the backup data and a usage capacity of the backup data in the backup target server; a schedule creation unit that assigns backup processing of the backup data of the backup target server to the data transfer servers in order based on information on the backup predicted time and information on the usage level of the network when the backup processing is performed, and creates the backup schedule based on the result of the assignment. Backup schedule creation device.

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

3. The backup predicted time calculation unit calculates the estimated backup throughput based on information about the network bandwidth of the network path connecting the data transfer server and the backup target server.

3. The backup schedule creation device according to claim 2.

4. The schedule creation unit modifies the predicted backup time for each combination of the data transfer server and the backup target server to a longer time during a time period when it is expected that the network will be used more frequently due to the execution of the backup process for a plurality of combinations of the data transfer server and the backup target server.

4. The backup schedule creation device according to claim 3.

5. When there is a data transfer server whose end time of the backup process does not fall within the backup window time, the schedule creation unit transfers the backup process to be performed outside the backup window time to the data transfer server whose end time of the backup process is the earliest.

5. The backup schedule creation device according to claim 4.

6. The schedule creation unit changes the order of backup processes of the backup target servers assigned to the data transfer server to an order that enables a reduction in the degree of use of the network.

6. The backup schedule creation device according to claim 5.

7. The schedule creation unit creates backup schedule candidates that can shorten the completion time of the backup process and backup schedule candidates that can further reduce the degree of network usage, selects one of the candidates based on a preset priority or an instruction input via an operation input unit, and creates the backup schedule based on the selected candidate.

7. The backup schedule creation device according to claim 6.

8. After the backup process based on the created backup schedule is completed, the schedule creation unit acquires information on the backup data usage capacity of each of the plurality of backup target servers, calculates the predicted backup time based on the acquired information on the backup data usage capacity, and updates the predicted backup time before the execution of the backup process with the calculated predicted backup time.

8. The backup schedule creation device according to claim 7.

9. 1. A backup creation method by 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 in a data storage server and a plurality of data transfer servers that acquire the backup data from the backup target servers and transfer the backup data to the data storage servers are connected to each other via a network, the method comprising: a step in which a backup predicted time calculation unit calculates a backup predicted time for each combination of the data transfer server and the backup target server based on an estimated backup throughput during transmission of the backup data and a usage capacity of the backup data in the backup target server; a schedule creation unit assigning backup processing of the backup data of the backup target server to the data transfer servers in order based on information on the predicted backup time and information on the degree of use of the network when the backup processing is performed, and creating the backup schedule based on the result of the assignment. How to create a backup schedule.

Images