JP2020135049A - Data migration management device, data migration management program and data migration management method - Google Patents

Abstract

To promptly perform data migration.SOLUTION: A data migration management device comprises: a specification unit for, when an instruction of causing first data stored in a first device to migrate to a second device is accepted, referring to information indicating a third device in which second data identical to the first data is stored, so as to specify the third device in which the second data identical to the first data to be a migration object is stored; and a determination unit for determining which one of the first data and the second data is to migrate to the second device on the basis of a line speed between the first device and the second device and a line speed between the second device and the specified third device.SELECTED DRAWING: Figure 7

Description

The present invention relates to a data migration management device, a data migration management program, and a data migration management method.

Continuous Integration / Continuous Delivery (CI / CD) is performed to automatically test programs used for virtual machines in cloud services in response to changes in the program in order to respond quickly to changes in the market. ing. As a result, in addition to operating system (OS) updates and security patch application, frequent program updates by CI / CD occur. Therefore, the number of program backups is also increasing.

As a related technology, a technology has been proposed in which a difference file is generated according to the modification contents of the file to be backed up, and a group of files to which the difference file is applied to a plurality of files is transmitted to the backup destination device. (See, for example, Patent Document 1).

In addition, as a related technology, there is a technology for generating deployment information including information necessary for deploying a VM image based on common configuration information including software modules common to each virtual machine and physical server configuration information. It has been proposed (see, for example, Patent Document 2).

Japanese Unexamined Patent Publication No. 2018-25849 Japanese Unexamined Patent Publication No. 2016-9341

When a failure occurs in the server in the operation site used for the cloud service, the server in the disaster countermeasure site is used as an alternative server. When the server program in the operation site is updated, the backup target data (migration target data) is sent to the disaster countermeasure site. However, if the distance between the operation site and the disaster countermeasure site is long, it takes time to transmit the data to be migrated.

As one aspect, the present invention aims to facilitate data migration.

In one aspect, when the data migration management device receives an instruction to transfer the first data stored in the first device to the second device, the data migration management device stores the same second data as the first data. With reference to the information indicating, the specific unit that identifies the third device that stores the same second data as the first data to be migrated, the line speed between the first device and the second device, and A decision to determine whether to transfer the first data or the second data to the second device based on the line speed between the second device and the identified third device. It has a part.

According to one aspect, data migration can be done quickly.

It is a figure which shows an example of the whole structure of the system of 1st Embodiment. It is a figure which shows the 1st example of the backup method. It is a figure which shows the 2nd example of the backup method. This is an example showing an outline of the backup method in the first embodiment. It is a figure which shows an example of the functional structure of an operation server. It is a figure which shows an example of the functional structure of the 1st management server. It is a figure which shows an example of the functional structure of the 2nd management server. It is a figure which shows an example of a package management information. It is a figure which shows an example of the transferred package list. It is a figure which shows an example of the repository management information. It is a figure which shows an example of the line speed between an operation site and a disaster countermeasure site. It is a flowchart which shows an example of the process of the 1st management server in 1st Embodiment. It is a flowchart which shows the detail of the package transfer processing of the 1st management server in 1st Embodiment. It is a flowchart which shows an example of the process of the 2nd management server in 1st Embodiment. It is a figure which shows an example of the hardware configuration of the 2nd management server. It is a figure which shows an example of the whole structure of the system of 2nd Embodiment. It is a figure which shows the 3rd example of a backup method. It is a figure which shows the 4th example of a backup method. This is an example showing an outline of the backup method in the second embodiment. It is a figure which shows an example of the functional structure of the 3rd management server. It is a figure which shows an example of the functional structure of the 4th management server. It is a figure which shows an example of the transfer waiting package list. It is a figure which shows an example of a package acquisition list. It is a flowchart which shows an example of the process of the 3rd management server in 2nd Embodiment. It is a flowchart which shows the detail of the package transfer processing of the 3rd management server in 2nd Embodiment. It is a flowchart which shows an example of the processing of the 4th management server in 2nd Embodiment.

Hereinafter, the first embodiment will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the overall configuration of the system of the first embodiment. The system of the first embodiment includes an operation site 10, a disaster countermeasure site 20, a data server 5, and a repository server 6. The operation site 10 can communicate with the data server 5 and the disaster countermeasure site 20 via a Wide Area Network (WAN) or a dedicated line. The disaster countermeasure site 20 can communicate with the data server 5, the repository server 6, and the operation site 10 via a WAN or a dedicated line.

The operation site 10 includes an operation server 1 used for a cloud service and a first management server 2 that manages the operation server 1. The operation server 1 is equipped with, for example, a virtual machine (VM) used by a plurality of users. The first management server 2 can communicate with the operation server 1 via a network such as a local area network (LAN). The operation site 10 may include a plurality of operation servers 1. The operation server 1 is an example of the first device. The first management server 2 is, for example, a cloud controller.

The disaster countermeasure site 20 includes a backup server 3 and a second management server 4 having the same configuration as the operation site 10. The second management server 4 can communicate with the backup server 3 via a network such as a LAN. The backup server 3 is used in place of the operation server 1, for example, when a failure occurs in the operation server 1. The second management server 4 is an example of a computer and a data migration management device. The backup server 3 is an example of the second device.

The data server 5 stores user-specific data among the data possessed by the operation server 1 as backup data.

The repository server 6 stores the same data as the data possessed by the operation server 1. The repository server 6 stores, for example, data commonly used by a plurality of VMs as backup data. The data stored in the repository server 6 is, for example, a package containing various data such as a program applied to the VM. The repository server 6 is an example of the third device.

The process related to the data backup of the operation server 1 will be described below, but the data backup is an example of data migration. For example, the same process can be applied when moving the VM or the like of the operation server 1 to another site.

FIG. 2 is a diagram showing a first example of a backup method. In the first example, the first management server 2 acquires backup data for all the data related to the VM to be backed up by the operation server 1 (1-1). The backup method of the operation server 1 may be either a full backup or a differential backup. The backup data includes program and user-specific data (eg, customer data) and the like. The first management server 2 transmits the acquired backup data to the data server 5 (1-2). The second management server 4 of the disaster countermeasure site 20 acquires the backup data stored in the data server 5 (1-3), and builds a VM on the backup server 3 based on the acquired backup data (1-4). ).

By the above processing, the second management server 4 can build a VM similar to the VM in the operation server 1 on the backup server 3. However, in the example shown in FIG. 2, even if there is a program common to a plurality of VMs, since all the programs are backed up for each VM, the amount of backup data is large and the processing takes time.

FIG. 3 is a diagram showing a second example of the backup method. In the first example, the first management server 2 distinguishes between a package containing data (programs and the like) commonly used by a plurality of VMs and user-specific data, and acquires the data as backup data (2-1). When there is a package commonly used by a plurality of VMs, the first management server 2 acquires the packages so as not to be duplicated. The first management server 2 updates the template including the VM package configuration, OS settings, and the like.

Then, the first management server 2 transmits the acquired package and the template to the second management server 4 (2-2). In addition, the first management server 2 transmits the user's unique data to the data server 5 (2-3). The second management server 4 builds a VM on the backup server 3 based on the received package and template (2-4). The second management server 4 may receive the user's unique data from the data server 5 and build a VM including the user's unique data on the backup server 3.

By the above processing, the second management server 4 can construct a VM having the same package configuration as the VM in the operation server 1 on the backup server 3. Further, when a package shared by a plurality of VMs exists, the first management server 2 acquires the packages so as not to be duplicated and transmits the packages to the second management server 4, so that the backup efficiency can be improved. However, if the line speed is slow due to a long distance between the operation site 10 and the disaster countermeasure site 20, it takes time to transfer the package.

FIG. 4 is an example showing an outline of the backup method according to the first embodiment. The example shown in FIG. 4 differs from the example shown in FIG. 3 in that the second management server 4 acquires the package from the repository server 6. The first management server 2 distinguishes between a package containing data (programs and the like) commonly used by a plurality of VMs and user-specific data, and acquires the data as backup data (3-1). When there is a package commonly used by a plurality of VMs, the first management server 2 acquires the packages so that they do not overlap. The first management server 2 updates the template including the VM package configuration, OS settings, and the like.

The first management server 2 transmits the template to the second management server 4 (3-2). The second management server 4 receives the package described in the template from the repository server 6 or the operation site 10 whichever has the faster line speed (3-3).

The first management server 2 transmits the user's unique data to the data server 5 (3-4). The second management server 4 builds a VM on the backup server 3 using the received package (3-5). The second management server 4 may receive the user's unique data from the data server 5 and build a VM including the user's unique data on the backup server 3.

As described above, the second management server 4 in the first embodiment quickly acquires the package by receiving the package from the repository server 6 or the operation site 10 which has the faster line speed, and obtains the VM. Can be built.

FIG. 5 is a diagram showing an example of the functional configuration of the operation server 1. The operation server 1 includes a host OS 11, a management agent 12, and a plurality of VMs 13.

The host OS 11 is the OS of the operation server 1. The management agent is software that manages the VM13. The VM 13 is a virtual machine that operates on the host OS 11, and is used as, for example, a user's business server. The functional configuration of the backup server 3 is the same as the functional configuration of the operation server 1.

FIG. 6 is a diagram showing an example of the functional configuration of the first management server 2. The first management server 2 includes a control unit 21, a transmission unit 22, a reception unit 23, a transfer unit 24, and a storage unit 25.

The control unit 21 performs various control processes related to the transfer of packages of the operation server 1. The control unit 21 generates, for example, a template of the VM13 to be backed up and package management information regarding the package to be backed up.

The transmission unit 22 transmits the template of the VM13 to be backed up, the package management information about the package to be backed up, and the instruction to migrate the package to the backup server 3 to the second management server 4. The template includes the identification information of the package included in the VM13, the OS setting of the VM13, and the like. The package management information includes identification information of available repositories for each package. The usable repository is the repository server 6 that stores the same package as the package used for the operation server 1 among the repository servers 6.

The receiving unit 23 receives the package to be backed up and the user's unique data from the operation server 1. When the transfer unit 24 does not receive the notification indicating the success of package acquisition from the repository server 6 from the second management server 4, the transfer unit 24 transfers the backup target package received from the operation server 1 to the second management server 4. In addition, the transfer unit 24 transfers the user's unique data to the data server 5.

The storage unit 25 stores the template of the VM13 to be backed up, the package management information, the transferred package list for recording the transferred packages, and the like. Details of the package management information and the transferred package list will be described later.

FIG. 7 is a diagram showing an example of the functional configuration of the second management server 4. The second management server 4 includes a receiving unit 41, a specific unit 42, a determination unit 43, a notification unit 44, a construction unit 45, a storage unit 46, and a control unit 47.

The receiving unit 41 includes the identification information of the package to be migrated (backup) stored in the operation server 1, the identification information of the repository server 6 storing the same package as the package, and an instruction to migrate the package to the backup server 3. To receive. The package is an example of the first data and the second data. The first data and the second data are not limited to the package, and may be user-specific data or the like. The identification information of the package to be backed up is recorded in the template of VM13, for example. The identification information of the repository server 6 that stores the package is, for example, the identification information recorded as a usable repository in the package management information.

The specifying unit 42 refers to the package management information and identifies the repository server 6 that stores the same package as the backup target package stored in the operation server 1 from the plurality of repository servers 6. For example, when there are a plurality of repository servers 6 for storing packages to be backed up, the specific unit 42 selects the repository server 6 having the fastest line speed with the backup server 3 among the plurality of repository servers 6. Identify. The line speed between the repository server 6 and the backup server 3 is measured in advance and stored in the storage unit 46.

In the determination unit 43, the package stored in the operation server 1 and the repository server 6 are stored based on the line speed between the operation server 1 and the backup server 3 and the line speed between the backup server 3 and the repository server 6. Decide which of the stored packages to migrate to the backup server 3. For example, the determination unit 43 compares the line speed between the operation server 1 and the backup server 3 and the line speed between the backup server 3 and the repository server 6, and sets the package to be backed up as the operation server 1 and the repository server 6. Decide which one to get from.

When the package acquisition from the repository server 6 is successful, the notification unit 44 transmits a notification indicating the success of the package acquisition to the first management server 2.

The construction unit 45 constructs a virtual machine (VM13) on the backup server 3 by using the package received from the first management server 2 or the package received from the repository server 6.

The storage unit 46 stores the repository management information including the line speed between the backup server 3 and the repository server 6, the line speed between the operation site 10 and the disaster countermeasure site 20, and the like. Further, the storage unit 46 temporarily stores the package received from the first management server 2 or the repository server 6.

The control unit 47 performs various control processes related to the acquisition of packages in the backup server 3. The control unit 47 determines, for example, whether or not the processing of all the packages recorded in the template received from the first management server 2 has been completed. Further, when each package is acquired, the acquisition status of the package is determined, and the transmission operation of the notification unit 44 is controlled according to the result.

The second management server 4 may perform the processing of the determination unit 43 and transmit the determination result to another device different from the second management server 4. Then, another device may receive the package from the operation server 1 or the repository server 6 according to the result of the determination unit 43, and construct the virtual machine of the backup server 3.

FIG. 8 is a diagram showing an example of package management information. The package management information is stored in the storage unit 25 of the first management server 2. As shown in FIG. 8, as package management information, package identification information, package hash value, package size, and available repository identification information are stored in association with each other. The usable repository is the repository server 6 that stores the same package as the package stored in the operation server 1.

FIG. 9 is a diagram showing an example of a transferred package list. The transferred package list is stored in the storage unit 25 of the first management server 2. Among the packages included in the package management information shown in FIG. 8, the transferred package list stores the identification information of the package transferred to the second management server 4 and the hash value of the package in association with each other. Further, in the transferred package list, when a package acquisition success notification is received from the second management server 4, the identification information of the package and the hash value of the package are stored in association with each other.

FIG. 10 is a diagram showing an example of repository management information. The repository management information is stored in the storage unit 46 of the second management server 4. As shown in FIG. 10, as the repository management information of the disaster countermeasure site 20, the repository name which is the name of the repository server 6, the IP address of the repository server 6, and the line speed between the disaster countermeasure site 20 and the repository server 6 Are associated and stored. In this embodiment, the communication delay in the disaster countermeasure site 20 is ignored. Therefore, it is assumed that the line speed shown in FIG. 10 is the same as the line speed between the backup server 3 and the repository server 6 and the line speed between the second management server 4 and the repository server 6.

The second management server 4 measures, for example, the line speed between the backup server 3 and the repository server 6 in the disaster countermeasure site 20 and stores it as the repository management information shown in FIG. The second management server 4 stores "0MB / S" as the line speed when communication is not possible due to, for example, a communication failure.

FIG. 11 is a diagram showing an example of the line speed between the operation site 10 and the disaster countermeasure site 20. The information shown in FIG. 11 is stored in the storage unit 46 of the second management server 4. As shown in FIG. 11, the name of the operation site 10 and the line speed between the operation site 10 and the disaster countermeasure site 20 are stored in association with each other. The second management server 4, for example, measures the line speed between the operation server 1 and the backup server 3 in advance, and stores the line speed in association with the name of the operation site.

FIG. 12 is a flowchart showing an example of the processing of the first management server 2 in the first embodiment. The first management server 2 starts the process shown in FIG. 12, for example, in response to a user's instruction. Further, the first management server 2 may automatically execute the process shown in FIG. 12 before and after the program update of the operation server 1 is performed.

The control unit 21 determines whether the processes of steps S102 to S105 described later have been completed for all the VM13s to be backed up among the VM13s in the operation server 1 (step S101). If NO in step S101, the control unit 21 selects one of the VM13s to be backed up (step S102). The transmission unit 22 transmits the template of the VM13 to be backed up and the instruction to migrate the package to the backup server 3 to the second management server 4 (step S103). The control unit 21 updates the template to the latest state before transmitting the template.

The control unit 21 determines whether the transfer process of all the packages in the VM13 to be backed up is completed (step S104). If NO in step S104, the first management server 2 executes the package transfer process (step S105). The process of step S105 is executed for each package in the VM13 to be backed up. Details of step S105 will be described later.

If YES in step S104, the process proceeds to step S101. If YES in step S101, the process of the first management server 2 ends.

FIG. 13 is a flowchart showing details of the package transfer process of the first management server 2 in the first embodiment. The process shown in FIG. 13 is a detail of the process in step S105 of FIG. The control unit 21 determines whether the package to be processed has been transferred (step S201). The package to be processed is the package included in the template and the package to be backed up. The control unit 21 determines, for example, whether the package to be processed exists in the transferred package list (for example, FIG. 9).

If NO in step S201, the transmission unit 22 transmits the package management information regarding the package to be processed to the second management server 4 (step S202). For example, among the information shown in FIG. 8, the transmission unit 22 transmits the information indicating the usable repository associated with the package to be processed to the second management server 4. That is, the transmission unit 22 transmits the identification information of the repository server 6 that stores the same package as the package to be processed.

The control unit 21 determines whether or not the notification indicating the success of package acquisition from the repository server 6 has been received from the second management server 4 (step S203). For example, the control unit 21 waits for a predetermined time after the process of step S202, and determines whether or not the notification indicating the success of package acquisition has been received from the second management server 4 within the predetermined time. If NO in step S203, the transfer unit 24 transfers the package to be processed to the second management server 4 (step S204).

If YES in step S203, or after the processing in step S204, the control unit 21 adds the identification information of the package to be processed to the transferred package list (step S205). After the process of step S205, or if YES in step S201, the first management server 2 ends the package transfer process.

FIG. 14 is a flowchart showing an example of the processing of the second management server 4 in the first embodiment. The receiving unit 41 receives the template of the VM to be processed and the instruction to migrate the package to the backup server 3 from the first management server 2 (step S301). The template of the VM to be processed received in step S301 is the template transmitted by the first management server 2 in step S103 of FIG.

The control unit 47 determines whether or not the processing of all the packages recorded in the received template has been completed (step S302). If NO in step S302, the receiving unit 41 receives the package management information regarding the package to be processed (step S303). The package management information received by the receiving unit 41 is the information transmitted by the first management server 2 in step S202 of FIG.

The specific unit 42 refers to the package management information and determines whether or not there is a usable repository associated with the package to be processed (step S304). If YES in step S304, the specific unit 42 refers to the repository management information (for example, FIG. 10), and among the repository servers 6 recorded as usable repositories in the package management information, between the repository server 6 and the disaster countermeasure site 20. The repository server 6 having the fastest line speed is specified (step S305). When there is only one available repository associated with the package to be processed, which is included in the package management information, the specific unit 42 does not refer to the repository management information and acquires the available repository (repository server 6) of the package. It may be specified as a destination.

The determination unit 43 determines whether the line speed between the backup server 3 and the specified repository server 6 is faster than the line speed between the operation server 1 and the backup server 3 (for example, FIG. 11) (step S306). If YES in step S306, the determination unit 43 determines to acquire the package to be processed from the repository server 6 (step S307). Then, the receiving unit 41 receives the package to be processed from the specified repository server 6 (step S308).

The control unit 47 determines whether the acquisition of the package is successful (step S309). If YES in step S309, the notification unit 44 transmits a notification indicating successful package acquisition to the first management server 2 (step S310). For example, if the acquisition of the package fails due to a communication failure or the like, the result is NO in step S309. If NO in step S304, NO in step S306, or NO in step S309, the determination unit 43 determines to acquire the package from the operation server 1 (step S311).

After the processing of steps S310 and S311, the processing returns to step S302. If YES in step S302, the construction unit 45 builds a virtual machine (VM13) on the backup server 3 using the received package (step S312). The second management server 4 may receive the user's unique data from the data server 5 and build the virtual machine including the user's unique data before constructing the virtual machine.

As described above, the second management server 4 of the first embodiment quickly migrates to the package by deciding whether to acquire the package from the operation site 10 or the repository server 6 based on the line speed. be able to. As a result, the second management server 4 can quickly back up the data.

Further, since the second management server 4 acquires the package from the repository server 6 having the fastest line speed with the second management server 4 among the plurality of repository servers 6, backup can be performed quickly. ..

Next, an example of the hardware configuration of the second management server 4 will be described. FIG. 15 is a diagram showing an example of the hardware configuration of the second management server 4. As shown in the example of FIG. 15, in the second management server 4, the processor 111, the memory 112, the auxiliary storage device 113, the communication interface 114, the medium connection unit 115, the input device 116, and the output device 117 are connected to the bus 100. Will be done.

The processor 111 executes the program expanded in the memory 112. A data migration management program that performs processing according to the embodiment may be applied to the program to be executed.

The memory 112 is, for example, a Random Access Memory (RAM). The auxiliary storage device 113 is a storage device that stores various types of information, and for example, a hard disk drive, a semiconductor memory, or the like may be applied. The data migration management program that performs the processing of the embodiment may be stored in the auxiliary storage device 113.

The communication interface 114 is connected to a communication network such as a LAN or WAN, and performs data conversion or the like associated with the communication.

The medium connection unit 115 is an interface to which the portable recording medium 118 can be connected. An optical disc (for example, Compact Disc (CD) or Digital Versatile Disc (DVD), etc.), a semiconductor memory, or the like may be applied to the portable recording medium 118. A data migration management program that performs the processing of the embodiment may be recorded on the portable recording medium 118.

The input device 116 is, for example, a keyboard, a pointing device, or the like, and receives instructions and information input from the user.

The output device 117 is, for example, a display device, a printer, a speaker, or the like, and outputs an inquiry or instruction to a user, a processing result, or the like.

The storage unit 46 shown in FIG. 7 may be realized by a memory 112, an auxiliary storage device 113, a portable recording medium 118, or the like. Even if the receiving unit 41, the specifying unit 42, the determining unit 43, the notification unit 44, the construction unit 45, and the control unit 47 in FIG. 7 are realized by the processor 111 executing the data migration program expanded in the memory 112. Good.

The memory 112, the auxiliary storage 113, and the portable recording medium 118 are computer-readable and non-temporary tangible storage media, not temporary media such as signal carriers.

The second management server 4 may not include all the components shown in FIG. 15, and some components may be omitted. Further, some components may exist in the external device of the second management server 4, and the second management server 4 may connect to the external device to use the components in the external device. Further, it is assumed that the hardware configuration of the first management server 2 is the same as the hardware configuration shown in FIG.

<Example>
Next, processing for each of packages 1 to 3 will be described with reference to the information of FIGS. 8 to 11. First, the case where the processing target package is package 1 will be described. As shown in FIG. 8, the usable repositories of the package 1 are the repository 1 and the repository 3. The identification unit 42 identifies the repository 1 having a high line speed with the backup server 3 among the repository 1 and the repository 3 with reference to the repository management information shown in FIG. The determination unit 43 compares the line speed between the backup server 3 and the repository 1 (5 MB / S) with the line speed between the backup server 3 and the operation server 1 (1 MB / S) (FIG. 11). .. Since the line speed (5MB / S) between the backup server 3 and the repository 1 is high, the determination unit 43 decides to acquire the package from the repository 1.

A case where the processing target package is package 2 will be described. As shown in FIG. 8, the usable repositories of the package 2 are the repository 2 and the repository 3. The identification unit 42 identifies the repository 2 having a high line speed with the backup server 3 among the repository 2 and the repository 3 with reference to the repository management information shown in FIG. The determination unit 43 determines the line speed between the backup server 3 and the repository 2 (0.2 MB / S) and the line speed between the backup server 3 and the operation server A (1 MB / S) (FIG. 11). Compare. The operation server A is an example of the operation server 1. Since the line speed (1MB / S) between the backup server 3 and the operation server 1 is high, the determination unit 43 decides to acquire the package from the operation server 1.

A case where the processing target package is package 3 will be described. As shown in FIG. 8, the usable repository of the package 3 is the repository 3. The determination unit 43 compares the line speed between the backup server 3 and the repository 3 (0 MB / S) with the line speed between the backup server 3 and the operation server 1 (1 MB / S) (FIG. 11). .. Since the line speed (1MB / S) between the backup server 3 and the operation server 1 is high, the determination unit 43 decides to acquire the package from the operation server 1.

<Second embodiment>
Hereinafter, the second embodiment will be described with reference to the drawings. FIG. 16 is a diagram showing an example of the overall configuration of the system of the second embodiment. The system of the second embodiment includes an operation site 10, a disaster countermeasure site 20, and a repository server 6. The operation site 10 can communicate with the disaster countermeasure site 20 via a WAN or a dedicated line. The disaster countermeasure site 20 can communicate with the operation site 10 and the repository server 6 via a WAN or a dedicated line.

The operation site 10 includes an operation server 1 used for a cloud service and a third management server 7 that manages the operation server 1. The operation server 1 is equipped with, for example, a VM used by a plurality of users. The operation site 10 may include a plurality of operation servers 1. The third management server 7 can communicate with the operation server 1 via a network such as a local area network (LAN). The operation server 1 is an example of the first device. The third management server 7 is, for example, a cloud controller. It is assumed that the functional configuration of the operation server 1 is the same as the functional configuration of the first embodiment shown in FIG.

The disaster countermeasure site 20 includes a backup server 3 and a fourth management server 8 having the same configuration as the operation site 10. The backup server 3 is used in place of the operation server 1, for example, when a failure occurs in the operation server 1. The fourth management server 8 is an example of a computer and a data migration management device. The backup server 3 is an example of the second device.

The repository server 6 stores the same data as the data possessed by the operation server 1 as backup data. The repository server 6 stores, for example, a package containing various data such as a program applied to a virtual machine. The repository server 6 is an example of the third device.

FIG. 17 is a diagram showing a third example of the backup method. In the third example, the third management server 7 acquires backup data for all the data related to the VM to be backed up by the operation server 1 (4-1). The backup method of the operation server 1 may be either a full backup or a differential backup. The backup data includes program and user-specific data (eg, customer data) and the like. The first management server 2 transmits the acquired backup data to the fourth management server 8 of the disaster countermeasure site 20 (4-2). The fourth management server 8 builds a VM on the backup server 3 based on the received data (4-3).

By the above processing, the fourth management server 8 can construct a VM similar to the VM in the operation server 1 on the backup server 3. However, in the example shown in FIG. 17, as in the example shown in FIG. 2, even if there is a program common to a plurality of VMs, all the programs are backed up for each VM, so that the amount of backup data is large and processing is performed. It takes time.

FIG. 18 is a diagram showing a fourth example of the backup method. In the fourth example, the third management server 7 distinguishes between a package containing data (programs and the like) commonly used by a plurality of VMs and user-specific data, and acquires the data as backup data (5-1). When there is a package commonly used by a plurality of VMs, the third management server 7 acquires the packages so as not to be duplicated. The third management server 7 updates the template including the VM package configuration, OS settings, and the like.

Then, the third management server 7 transmits the acquired package and the template to the second management server 4 (5-2). Further, the third management server 7 transmits the user's unique data to the second management server 4 (5-3). The fourth management server 8 builds a VM on the backup server 3 based on the received package, template, and user-specific data (5-4).

By the above processing, the fourth management server 8 can construct a VM having the same package configuration as the VM in the operation server 1 on the backup server 3. Further, when there is a package commonly used by a plurality of VMs, the third management server 7 acquires the packages so as not to be duplicated and transmits the packages to the fourth management server 8, so that the backup can be made more efficient. However, if the distance between the operation site 10 and the disaster countermeasure site 20 is long, it takes time to transfer the package, and the risk of transfer failure due to a communication failure during transfer increases. Then, for example, if a communication failure occurs between the processes of 5-2 and 5-3, the backup server 3 of the disaster countermeasure site 20 may not be updated.

FIG. 19 is an example showing an outline of the backup method in the second embodiment. In the second embodiment, the third management server 7 distinguishes between a package containing data (programs and the like) commonly used by a plurality of VMs and user-specific data, and acquires the data as backup data (6-1). .. When there is a package commonly used by a plurality of VMs, the third management server 7 acquires the packages so as not to be duplicated. The third management server 7 updates the template including the VM package configuration, OS settings, and the like.

Then, the third management server 7 transmits the package management information regarding the acquired package and the template to the second management server 4 (6-2). The fourth management server 8 refers to the template and the package management information, and determines whether the package to be backed up can be acquired from the repository server 6. The fourth management server 8 notifies the third management server 7 of information indicating a package that cannot be acquired from the repository server 6 (6-3). The third management server 7 transmits a package that the fourth management server 8 cannot obtain from the repository server 6 to the fourth management server 8 (6-4).

The fourth management server 8 acquires the packages that can be acquired from the repository server 6 after acquiring the packages from the third management server 7 (6-5). Further, the third management server 7 transmits the user's unique data to the second management server 4 (6-5). The fourth management server 8 builds a VM on the backup server 3 based on the received package, template, and user-specific data (6-7).

By the above processing, the fourth management server 8 can construct a VM having the same package configuration as the VM in the operation server 1 on the backup server 3. When a communication failure or the like occurs with the repository server 6, the fourth management server 8 acquires data to be backed up that cannot be acquired from the repository server 6 from the operation server 1 via the third management server 7. Further, the fourth management server 8 acquires the package that can be acquired from the repository server 6 after acquiring the package from the third management server 7. That is, since the package is preferentially acquired from the third management server 7, the risk of backup failure can be reduced even if the operation site 10 and the disaster countermeasure site are far apart and a line failure or the like occurs.

FIG. 20 is a diagram showing an example of the functional configuration of the third management server 7. The third management server 7 includes a control unit 71, a transmission unit 72, a reception unit 73, a transfer unit 74, and a storage unit 75.

The control unit 71 performs various control processes related to the transfer of packages of the operation server 1. The control unit 71 generates, for example, a template of the VM13 to be backed up and package management information regarding the package to be backed up.

The transmission unit 72 transmits the template of the VM13 to be backed up, the package management information regarding the package to be processed, and the backup instruction of the package to the fourth management server 8. The template includes the identification information of the package included in the VM, the OS setting of the VM13, and the like. The package management information is the same as the package management information (for example, FIG. 8) in the first embodiment.

The receiving unit 73 receives the package to be backed up and the user's unique data from the operation server 1. When the transfer unit 74 receives information from the fourth management server 8 indicating that the package to be processed has not been acquired from the repository server 6, the transfer unit 74 receives the backup target package received from the operation server 1 from the fourth management server 8. Transfer to. Further, the transfer unit 74 transfers the user's unique data received from the operation server 1 to the fourth management server 8.

The storage unit 75 stores the package management information which is information about the package, the transfer waiting package list for recording the transfer waiting package, and the transferred package list for recording the transferred package. The transferred package list is the same as the transferred package list in the first embodiment (for example, FIG. 9).

FIG. 21 is a diagram showing an example of the functional configuration of the fourth management server 8. The fourth management server 8 includes a receiving unit 81, a determination unit 82, a notification unit 83, a construction unit 84, a storage unit 85, and a control unit 86.

The receiving unit 81 receives the identification information of the package to be backed up stored in the operation server 1, the identification information of the repository server 6 storing the same package as the package, and the backup instruction of the package. The package is, for example, a package of a program applied to VM13, and is an example of first data and second data. The first data and the second data are not limited to the package, and may be user-specific data or the like. The identification information of the package to be backed up is recorded in the template of VM13, for example. The identification information of the repository server 6 that stores the package is, for example, the identification information recorded as a usable repository in the package management information. The receiving unit 81 further receives the user's unique data from the third management server 7.

The determination unit 82 determines that the receivable package is received from the repository server 6 among the plurality of packages to be backed up, and the same package as the package that cannot be received from the repository server 6 is received from the operation server 1. For example, when communication with the repository server 6 for storing the package is difficult due to a communication failure or the like, the determination unit 82 determines to receive the package from the operation server 1. In the second embodiment, it is assumed that the distance between the repository server and the backup server 3 is closer than the distance between the operation server 1 and the backup server 3.

When the determination unit 83 determines that the package to be processed cannot be acquired from the repository server 6, the notification unit 83 informs the third management server 7 that the package cannot be acquired from the repository server 6 together with the identification information of the package. Notice.

The construction unit 84 constructs a virtual machine (VM13) on the backup server 3 using the package received from the operation server 1 via the third management server 7, the package received from the repository server 6, and the user's unique data. ..

Similar to the storage unit 46 of the first embodiment, the storage unit 85 includes repository management information including the line speed between the repository server 6 (for example, FIG. 10), and between the operation site 10 and the disaster countermeasure site 20. (For example, FIG. 11) is stored. The storage unit 85 further stores a package acquisition list indicating the packages to be acquired. In addition, the storage unit 46 temporarily stores the package received from the first management server 2 or the repository server 6 and the user's unique data.

The control unit 86 controls the transfer order of the packages to be transferred based on the template received from the third management server. Also, the information in the package acquisition list is edited according to the transfer status of the package.

FIG. 22 is a diagram showing an example of a transfer waiting package list. The transfer waiting package list is stored in the storage unit 75 of the third management server 7. When the control unit 71 receives a notification from the fourth management server 8 indicating that the package to be processed cannot be acquired from the repository server 6, the control unit 71 adds the identification information of the package to the transfer waiting package list. When the control unit 71 transfers the package in the transfer waiting package list to the fourth management server 8, the control unit 71 deletes the identification information of the transferred package from the transfer waiting package list.

FIG. 23 is a diagram showing an example of a package acquisition list. The control unit 86 records the identification information and the hash value of the package to be acquired, for example, based on the template received from the third management server. Further, when the determination unit 82 determines whether to acquire the package to be processed from the repository server 6 or the operation server 1, the determination unit 82 records the acquisition destination according to the decision. Further, the initial setting of the acquisition status is "not yet", and when the control unit 86 acquires the package, the control unit 86 changes the package acquisition status to "completed".

FIG. 24 is a flowchart showing an example of the processing of the third management server 7 in the second embodiment. The third management server 7 executes the process shown in FIG. 24, for example, in response to a user's instruction. Further, the third management server 7 may automatically execute the process shown in FIG. 24 before and after the program update of the operation server 1 is performed.

The control unit 71 determines whether or not the processes of steps S402 to S405 described later have been completed for the VM13 to be backed up among the VM13s in the operation server 1 (step S401). If NO in step S401, the control unit 71 selects one of the VM13s to be backed up (step S402). The transmission unit 72 transmits a package backup instruction to the fourth management server 8 together with the template of the VM13 to be backed up (step S403). The control unit 71 updates the template to the latest state before transmitting the template.

The control unit 71 determines whether the transfer process of all the packages in the VM13 to be backed up is completed (step S404). If NO in step S404, the third management server 7 executes the package transfer process (step S405). The process of step S405 is executed for each package in the VM13 to be backed up. Details of step S405 will be described later.

If YES in step S404, the process proceeds to step S401. If YES in step S401, the process of the third management server 7 ends.

FIG. 25 is a flowchart showing details of the package transfer process of the third management server 7 in the second embodiment. The process shown in FIG. 25 is a detail of the process in step S405 of FIG. The control unit 71 determines whether the package to be processed has been transferred (step S501). The package to be processed is the package included in the template and the package to be backed up. The control unit 71 determines, for example, whether the package to be processed exists in the transferred package list (for example, FIG. 9).

If NO in step S501, the transmission unit 72 transmits the package management information regarding the package to be processed to the fourth management server 8 (step S502). For example, among the information shown in FIG. 8, the transmission unit 72 transmits the information indicating the usable repository associated with the package to be processed to the second management server 4. That is, the transmission unit 72 transmits the identification information of the repository server 6 that stores the same package as the package to be processed.

When the control unit 71 receives a notification from the fourth management server 8 (YES in step S503) indicating that the package to be processed cannot be acquired from the repository server 6, the control unit 71 transfers the identification information of the package. Add to the waiting package list (step S504). The transfer unit 74 transfers the package to be processed to the fourth management server 8 (step S505). The control unit 71 deletes the identification information of the transferred package from the transfer waiting package list (step S506). After the processing of step S506, or when NO in step S503, the control unit 71 adds the identification information of the transferred package to the transferred package list (step S507). After the process of step S507, or if YES in step S501, the third management server 7 ends the package transfer process.

FIG. 26 is a flowchart showing an example of the processing of the fourth management server 8 in the second embodiment. The receiving unit 81 receives the backup instruction of the VM template and the package to be processed from the third management server 7 (step S601). The template of the VM to be processed received in step S601 is the template transmitted by the third management server 7 in step S403 of FIG. 24.

The control unit 86 determines whether the processing of all the packages recorded in the received template is completed (step S602). If NO in step S602, the receiving unit 81 receives the package management information regarding the package to be processed (step S603). The package management information received by the receiving unit 81 is the information transmitted by the third management server 7 in step S502 of FIG.

The control unit 86 refers to the package management information and determines whether or not there is a usable repository associated with the package to be processed (step S604). If YES in step S604, the determination unit 82 determines whether the package to be processed can be acquired from the repository server 6 (step S605). For example, in the repository management information (for example, FIG. 10), the determination unit 82 determines that if the line speed of the repository server 6 is not 0 MB / S, it can be acquired from the repository server 6.

If YES in step S605, the determination unit 82 determines to acquire the package to be processed from the repository server 6 (step S606). In this case, the determination unit 43 records "repository server" as the acquisition destination of the package to be processed in the package acquisition list (FIG. 23). If NO in step S604 or NO in step S605, the determination unit 82 determines to acquire the package to be processed from the operation server 1 (step S607). In this case, the determination unit 82 records “operation server” as the acquisition destination of the package to be processed in the package acquisition list (FIG. 23). Then, the notification unit 83 notifies the third management server 7 that the package is not acquired from the repository server 6 together with the identification information of the package to be processed (step S608). When step S608 is executed, the package is transferred from the third management server 7 by the process of step S505 of FIG.

After the processing of step S606 or S608, the processing returns to step S602. If YES in step S602, the control unit 86 determines whether all the packages determined to be acquired from the operation server 1 have been acquired from the operation server 1 via the third management server 7 (step S609). For example, the control unit 86 determines whether or not all the packages recorded as "operation server" in the package acquisition list (FIG. 23) have been acquired. The fourth management server 8 may omit the process of step S609 when the package recorded as "operation server" in the package acquisition list does not exist. The control unit 86 waits until all the packages determined to be acquired from the operation server are acquired.

If YES in step S609, the receiving unit 81 receives the package determined to be acquired from the repository server 6 from the repository server 6 (step S610). The receiving unit 81 refers to, for example, the package acquisition list and receives the package recorded as “repository server”. Further, the receiving unit 81 receives the user's unique data from the third management server 7 (step S611). The construction unit 84 constructs a virtual machine (VM13) on the backup server 3 using the received package and the user's unique data (step S612).

As described above, when the fourth management server 8 of the second embodiment acquires the package from both the operation server 1 and the repository server 6, the package is acquired from the operation server 1 after acquiring the package from the repository server 6. get. As a result, the fourth management server 8 can reduce the risk that the package acquisition from the operation server 1 located at a distance farther than the repository server 6 fails due to a communication failure or the like, and the backup fails.

The hardware configurations of the third management server 7 and the fourth management server 8 are the same as those shown in FIG.

The present embodiment is not limited to the embodiments described above, and various changes, additions, and omissions can be applied without departing from the gist of the present embodiment.

The following additional notes will be further disclosed with respect to the above first embodiment and the second embodiment.
(Appendix 1)
When an instruction to transfer the first data stored in the first device to the second device is received, the information indicating the third device storing the same second data as the first data is referred to, and the transfer target. A specific unit that identifies a third device that stores the same second data as the first data of
The first data and the second data are based on the line speed between the first device and the second device and the line speed between the second device and the identified third device. A data migration management device including a determination unit for determining which of the two devices is to be transferred to the second device.
(Appendix 2)
In the specific unit, when a plurality of the third devices storing the second data exist, the third device has the fastest line speed with the second device among the plurality of third devices. The data migration management device according to Appendix 1, wherein the device is specified.
(Appendix 3)
The data migration management device according to Appendix 1 or 2, further comprising a construction unit for constructing a virtual machine in the second device using the first data or the second data.
(Appendix 4)
When an instruction to transfer the first data stored in the first device to the second device is received, the information indicating the third device storing the same second data as the first data is referred to, and the transfer target. A third device that stores the same second data as the first data of the above is specified.
The first data and the second data are based on the line speed between the first device and the second device and the line speed between the second device and the identified third device. A data migration management program for causing a computer to execute a process of deciding which of the two devices is to be migrated to the second device.
(Appendix 5)
The computer
When an instruction to transfer the first data stored in the first device to the second device is received, the information indicating the third device storing the same second data as the first data is referred to, and the transfer target. A third device that stores the same second data as the first data of the above is specified.
The first data and the second data are based on the line speed between the first device and the second device and the line speed between the second device and the identified third device. A data migration management method, characterized in that a process of determining which of the two is transferred to the second device is executed.
(Appendix 6)
When the distance between the third device and the second device, which stores the same second data as the first data, is shorter than the distance between the first device and the second device, which stores the first data, a plurality of cases. Of the second data, the receivable second data is received from the third device, and the same first data as the second data not received from the third device is received from the first device. The decision-making part that decides that,
A notification unit that notifies the first device of identification information indicating the second data that is not received from the third device, and
A data migration management device including a receiving unit that receives the second data from the third device after receiving the first data from the first device.
(Appendix 7)
When the distance between the third device and the second device, which stores the same second data as the first data, is shorter than the distance between the first device and the second device, which stores the first data, a plurality of cases. Of the second data, the receivable second data is received from the third device, and the same first data as the second data not received from the third device is received from the first device. Decided that
Notifying the first device of the identification information indicating the second data that is not received from the third device,
A data migration management program for causing a computer to execute a process of receiving the second data from the third device after receiving the first data from the first device.
(Appendix 8)
The computer
When the distance between the third device and the second device, which stores the same second data as the first data, is shorter than the distance between the first device and the second device, which stores the first data, a plurality of cases. Of the second data, the receivable second data is received from the third device, and the same first data as the second data not received from the third device is received from the first device. Decided that
Notifying the first device of the identification information indicating the second data that is not received from the third device,
A data migration management method, characterized in that, after receiving the first data from the first apparatus, a process of receiving the second data from the third apparatus is executed.

1 Operation server 2 1st management server 3 Backup server 4 2nd management server 5 Data server 6 Repository server 7 3rd management server 8 4th management server 10 Operation site 11 Host OS
12 Management Agent 13 VM
20 Disaster countermeasure site 21 Control unit 22 Transmission unit 23 Reception unit 24 Transfer unit 25 Storage unit 41 Reception unit 42 Specific unit 43 Decision unit 44 Notification unit 45 Construction unit 46 Storage unit 47 Control unit 100 Bus 111 Processor 112 Memory 113 Auxiliary storage device 114 Communication interface 115 Media connection 116 Input device 117 Output device 118 Portable recording medium

Claims (5)

When an instruction to transfer the first data stored in the first device to the second device is received, the information indicating the third device storing the same second data as the first data is referred to, and the transfer target. A specific unit that identifies a third device that stores the same second data as the first data of
The first data and the second data are based on the line speed between the first device and the second device and the line speed between the second device and the identified third device. A data migration management device including a determination unit for determining which of the two devices is to be transferred to the second device. When there are a plurality of the third devices storing the second data, the specific unit has the fastest line speed between the third device and the second device among the plurality of the third devices. The data migration management device according to claim 1, wherein the device is specified. The data migration management device according to claim 1 or 2, further comprising a construction unit for constructing a virtual machine in the second device using the first data or the second data. When an instruction to transfer the first data stored in the first device to the second device is received, the information indicating the third device storing the same second data as the first data is referred to, and the transfer target. A third device that stores the same second data as the first data of the above is specified.
The first data and the second data are based on the line speed between the first device and the second device and the line speed between the second device and the identified third device. A data migration management program for causing a computer to execute a process of deciding which of the two devices is to be migrated to the second device. The computer
When an instruction to transfer the first data stored in the first device to the second device is received, the information indicating the third device storing the same second data as the first data is referred to, and the transfer target. A third device that stores the same second data as the first data of the above is specified.
The first data and the second data are based on the line speed between the first device and the second device and the line speed between the second device and the identified third device. A data migration management method, characterized in that a process of determining which of the two is transferred to the second device is executed.

Images