WO2018058942A1

WO2018058942A1 - Data processing method and backup server

Info

Publication number: WO2018058942A1
Application number: PCT/CN2017/081070
Authority: WO
Inventors: 黄恒
Original assignee: 华为技术有限公司
Priority date: 2016-09-30
Filing date: 2017-04-19
Publication date: 2018-04-05
Also published as: CN106528327B; CN106528327A

Abstract

Disclosed in the embodiments of the present application are a data processing method and a backup server, for being able to ensure data transmission resuming from a breakpoint after an instant recovery task has a failover. The method of the embodiments of the present application comprises: a first backup node virtualizing backup data in the form of a block storage device, and establishing a target virtual machine according to the specification of a virtual machine carried by the backup data; the first backup node identifying a block storage device with a world wide name (WWN); a management node acquiring and storing the identifier of the target virtual machine and the WWN; when the management node determines that an instant recovery task failed, the management node sending to a second backup node an execution instruction to execute the instant recovery task; the second backup node acquiring the identifier of a temporary data storer, the WWN and the identifier of the target virtual machine; the second backup node virtualizing the backup data in the form of the block storage device, and identifying the block storage device along with the WWN; and the second backup node executing the instant recovery task according to the block storage device, the identifier of the temporary data storer and the identifier of the target virtual machine.

Description

Data processing method and backup server

Technical field

The present application relates to the field of computers, and in particular, to a data processing method and a backup server.

Background technique

With the continuous development of information technology (information technology, IT for short), more and more enterprises are transforming their IT infrastructure into virtualized and cloudized environments to provide computing resources using virtualization technology. The use efficiency to achieve an elastic computing system architecture. In the cloud computing/virtualization environment, in order to avoid the loss of virtual machine data caused by human error or system failure, the backup system is generally used to perform data backup on the virtual machine and back up the virtual machine data to the third-party backup storage device. . When the virtual machine data is restored, the previously backed up data needs to be restored from the backup storage to the production environment.

In recent years, a virtual machine instant recovery technology has emerged. The implementation process is to simulate backup data as a network file system (English name: Network File System, NFS for short), and mount the NFS share to the production environment host and create it as NFS. Data storage (English name: Data Store), then register the virtual machine in the NFS Data Store on the production environment, and finally run the virtual machine in the NFS DataStore directly. After the NFS DataStore mount and create and the virtual machine registration action is completed, , you can directly start the virtual machine to be restored. Since the NFS Data Store is set to non-persistent storage, the data written by the instant recovery virtual machine during the read and write operations is stored in the temporary storage space of the NFS DataStore. The industry backup server generally adopts a multi-node distributed architecture, and has a failover mechanism Failover for reliability. After the task fails, it will automatically switch to another backup node for re-execution.

The prior art solution is an NFS share that is simulated on the backup node, that is, an address of the Internet protocol (English name: Internet Protocol, IP address) of the backup node that provides the NFS shared service address. In the event of a failover of a backup task, that is, a failure of the backup task itself, the previous NFS share service is interrupted. This will result in the recovery of the instant recovery task, after switching to another backup node to re-execute, the recovery data that has been transmitted by the previous instant recovery task does not support the resume of the breakpoint, and only all of them can be resumed.

Summary of the invention

The embodiment of the present application provides a data processing method and a backup server, which can be used to ensure data breakpoint retransmission after the instant recovery task is switched.

In a first aspect, an embodiment of the present application provides a data processing method, including:

The data processing method is used for a backup server, where the backup server includes a management node, a first backup node, and a second backup node; wherein the first backup node is an execution node that is performing an immediate recovery task, and the second backup node is in the After the instant recovery task fails, the execution node of the instant recovery task is continued. The data processing method specifically includes the following steps: the first backup node virtualizes the backup data into a block storage device, and creates a target virtual machine according to the specification of the virtual machine carried in the backup data; the first backup node is the backup data virtual The generated block storage device identifier is a full identification name (English name: World Wide Name, WWN for short); the management node acquires and saves the identifier of the target virtual machine and the WWN; and when the backup server is running, the management node When it is determined that the instant recovery task fails, the management node sends an execution instruction for executing the instant recovery task to the second backup node; after receiving the execution instruction, the second backup node acquires temporary data storage. The identity of the Data Storer, the WWN, and the identity of the target virtual machine, the temporary Data Storer is pre- Setting the virtual data to the block storage device and identifying the WWN for the block storage device; the second backup node is based on the block storage device, the identifier of the temporary Data Storer, and the target virtual The identity of the machine performs this instant recovery task.

In the embodiment of the present application, before the first backup node obtains the backup data, the backup server determines backup data from the backup storage space, and selects a temporary Data Storer for storing temporary data and a target data for restoring the virtual machine. Storer. The identifier of the temporary Data Storer and the identifier of the target Data Storer are pre-stored in the management node of the backup server. The management node of the backup server determines, by the load balancing mechanism, the first backup node that first performs an immediate recovery task, and sends an instruction to the first backup node to perform an immediate recovery task. The first backup node obtains the metadata of the backup data determined by the backup server for verification, and the first backup node can obtain the backup data after the verification is passed.

In the technical solution provided by the embodiment of the present application, the second backup node and the first backup node are the same WWN as the block storage device identifier, that is, the second backup node is the same as the block storage device used by the first backup node, and The second backup node uses the same temporary data storer and the target virtual machine as the first backup node, so the second backup node can ensure that the instant execution is performed on the basis of the first backup node when performing the instant recovery task. To resume the task, that is, to ensure that the resume can be resumed.

Optionally, the data processing method further includes: the first backup node mounts the block storage device to the target virtual machine by using a raw device mapping (Raw Device Mapping, RDM for short) A virtual machine VM disk file is generated at the temporary Data Storer; the first backup node migrates the VM disk file from the temporary Data Storer to a pre-set target data store Data Storer.

In the technical solution provided by the embodiment of the present application, the first backup node uses the data migration capability of the production environment virtualization platform to migrate the backup data to the target Data Storer for instant recovery.

Optionally, the data processing method further includes: the first backup node generates a snapshot file for the target virtual machine by using a snapshot technology, and generates a change virtual machine Delta VM disk file in the temporary data storer; the first backup node The Delta VM disk file is migrated from the temporary Data Storer to the target Data Storer.

In the technical solution provided by the embodiment of the present application, the first backup node uses the data migration capability of the production environment virtualization platform and the snapshot technology to migrate the read and write data generated in the instant recovery task to the target Data Storer, thereby preventing the read and write. data lost.

Optionally, the data processing method further includes: the first backup node mounts the block storage device to the target virtual machine in a manner of original device mapping RDM, and generates a virtual machine VM disk file in the temporary data storer. The first backup node generates a snapshot file for the target virtual machine by using a snapshot technology, and generates a change virtual machine Delta VM disk file in the temporary data storer; the first backup node selects the VM disk file and the Delta VM disk file by the first backup node The temporary Data Storer is migrated to the target Data Storer.

In the technical solution provided by the embodiment of the present application, the first backup node uses the data migration capability of the production environment virtualization platform to migrate the backup data to the target Data Storer for instant recovery. At the same time, the first backup node utilizes the data migration capability of the production environment virtualization platform and the snapshot technology to migrate the read and write data generated in the instant recovery task to the target Data Storer, thereby preventing the read and write data from being lost.

Optionally, after the first backup node migrates the VM disk file and the Delta VM disk file from the temporary Data Storer to the target Data Storer, the first backup node deletes the snapshot file, and the target Data Storer The VM disk file is merged with the Delta VM disk file.

In the technical solution provided by the embodiment of the present application, the storage space can be effectively saved.

In a second aspect, the embodiment of the present application provides a backup server, which has the function of implementing the backup server in the foregoing method. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. The backup server includes:

The first backup node is configured to virtualize the backup data as a block storage device, and create a target virtual machine according to the specification of the virtual machine carried in the backup data; and identify the global identifier name WWN for the block storage device;

The management node is configured to acquire and save the identifier of the target virtual machine and the WWN; when it is determined that the instant recovery task fails, send an execution instruction for executing the instant recovery task to the second backup node;

The second backup node is configured to obtain an identifier of the temporary data storage Data Storer, the WWN and an identifier of the target virtual machine, where the temporary Data Storer is preset; the backup data is virtualized as the block storage device, and is the block The storage device identifies the WWN; and according to the block storage device, the identifier of the temporary Data Storer and the identifier of the target virtual machine perform the instant recovery task.

In a third aspect, an embodiment of the present application provides a computer storage medium, where the program storage code is stored in the computer storage medium, and the program code is used to indicate that the method of the first aspect or the second aspect is performed.

As can be seen from the foregoing technical solutions, the embodiment of the present application has the following advantages: the second backup node and the first backup node are the same WWN as the block storage device identifier, that is, the second backup node and the first backup node are used. The block storage device is the same, and the second backup node uses the same temporary Data Storer and the target virtual machine as the first backup node, so the second backup node can guarantee the first backup node when performing the instant recovery task. On the basis of this instant recovery task, that is, to ensure that the resume can be resumed.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the description of the embodiments will be briefly described below.

1 is a system framework diagram of a data processing method in an embodiment of the present application;

2 is a schematic diagram of an embodiment of a data processing method in an embodiment of the present application;

FIG. 3 is a schematic diagram of an embodiment of a backup server in an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described in the following with reference to the accompanying drawings.

The terms "first", "second", "third", "fourth", etc. (if present) in the specification and claims of the present application and the above figures are used to distinguish similar objects without having to use To describe a specific order or order. It is to be understood that the data so used may be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than what is illustrated or described herein. In addition, the terms "comprises" and "comprises" and "the" and "the" are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or device that comprises a series of steps or units is not necessarily limited to Those steps or units may include other steps or units not explicitly listed or inherent to such processes, methods, products or devices.

Please refer to the data processing system framework diagram shown in FIG. 1. The data processing system framework includes a backup server, a backup storage, a production environment, and a production storage. The backup server includes a management node, a first backup node, a second backup node, and a third backup node. It can be understood that the backup server can include multiple backup nodes, not just the three backup nodes drawn in the figure. Each backup node is a backup execution node in the data processing system, and provides a backup recovery task execution function. The management node provides backup management and system management of the data processing system. Can also be responsible for the scheduling of backup and recovery tasks in the data processing system, providing task scheduling load balancing and failover capabilities. The backup storage is responsible for storing backup data for virtual machines in the production environment. The production environment is responsible for carrying the user's production business, usually using a virtualized infrastructure, that is, including the host and multiple virtual machines on the host. The production store is responsible for storing production business data in the production environment.

Each backup node in the backup server adopts a multi-node distributed architecture, and has a reliability Failover mechanism. That is, after the task on the current backup node fails, the task is automatically switched to another backup node for re-execution. In the current virtual machine instant recovery technology, the NFS share simulated on the backup node, that is, the address of the external NFS sharing service is the Internet protocol (English full name: Internet Protocol, IP address) of the backup node. In the event of a failover of a backup task, that is, a failure of the backup task itself, the previous NFS share service is interrupted. This will result in the recovery of the instant recovery task, after switching to another backup node to re-execute, the recovery data that has been transmitted by the previous instant recovery task does not support the resume of the breakpoint, and only all of them can be resumed.

In order to solve this problem, the embodiment of the present application provides the following solution: the first backup node virtualizes the backup data into a block storage device, and creates a target virtual machine according to the specifications of the virtual machine carried in the backup data; the first backup a block storage device identifier WWN that is generated by the node for the backup data; the management node acquires and saves the identifier of the target virtual machine and the WWN; and when the backup node determines that the instant recovery task fails during the backup server operation, The management node sends an execution instruction for executing the instant recovery task to the second backup node; after receiving the execution instruction, the second backup node acquires the identifier of the temporary data storage Data Storer, the WWN, and the An identifier of the target virtual machine, the temporary Data Storer is set as a preview; the second backup node virtualizes the backup data as the block storage device, and identifies the WWN for the block storage device; the second backup node is according to the block storage device The identifier of the temporary Data Storer and the identifier of the target virtual machine perform the instant recovery .

For example, as shown in FIG. 2, an embodiment of a data processing method in the embodiment of the present application includes:

201. The first backup node virtualizes the backup data into a block storage device, and creates a target virtual machine according to the specifications of the virtual machine carried in the backup data.

The first backup node is used as an execution node of the current instant recovery task. After receiving the instruction to execute the virtual machine instant recovery task, the first backup node obtains backup data from the backup storage, and virtualizes the acquired backup data. A block storage device; in addition, the first backup node creates a new target virtual machine according to the specifications of the virtual machine carried in the backup data. The specifications of the virtual machine include the CPU model, the size of the memory, and the size of the hard disk. For example, the virtual machine carried in the backup data has a CPU of 2 cores, a memory of 3.5 gigabytes (English name: gigabyte, abbreviated as GB), and a hard disk of 500 GB, the target virtual node created by the first backup node. The specifications of the machine are 2 cores for the CPU, 3.5 GB for the memory, and 500 GB for the hard disk.

In an actual application, the first backup node may virtualize the backup data as a block storage device based on the open source software tgt, lio or scst, and the specific manner is not limited herein.

It can be understood that, in the embodiment of the present application, before the first backup node acquires the backup data, the backup server determines backup data from the backup storage, and selects a temporary data storage Data Storer for storing temporary data and is used for Restore the target Data Storer of the virtual machine. The identifier of the temporary Data Storer and the identifier of the target Data Storer are pre-stored in the management node of the backup server. The management node of the backup server determines, by the load balancing mechanism, the first backup node that first performs an immediate recovery task, and sends an instruction to the first backup node to perform an immediate recovery task. The first backup node obtains the metadata of the backup data determined by the backup server for verification, and the first backup node can obtain the backup data after the verification is passed. For example, there is a backup in the backup storage. The data A, the backup data B, and the backup data C. The specifications of the virtual machine carried in the backup data A are default specifications; the backup server has a first backup node, a second backup node, and a third backup node. If the backup server needs to perform an instant recovery task, and the backup server determines the backup data A as the backup data of the instant recovery, the address of the temporary Data Storer and the address of the target Data Storer are determined in the production storage space. After the management node determines that the first backup node is the execution node that performs the instant recovery task, the first backup node acquires the address of the temporary Data Storer and the address of the target Data Storer; the first backup node also acquires The metadata of the backup data A is checked for integrity. If the first backup node determines that the backup data A is complete, the first backup node acquires the backup data A. The first backup node creates a target virtual machine in the production environment according to the specification of the virtual machine (that is, the default specification) carried in the backup data A, and the specification of the target virtual machine is a default specification. The first backup node virtualizes the backup data A as the block storage device A.

202. The first backup node is the block storage device identifier WWN.

After the first backup node virtualizes the backup data as the block storage device, the WWN is marked for the block storage device.

In the embodiment of the present application, the first backup node labels the block storage device A with a WWN.

203. The first backup node sends the identifier of the WWN and the target virtual machine to the management node.

The first backup node sends the WWN of the block storage device and the identifier of the target virtual machine created by the first backup node to the management node.

In the embodiment of the present application, the first backup node sends the WWN of the block storage device A and the identifier of the target virtual machine to the management node.

In the actual normal instant recovery task, after the first backup node creates the target virtual machine, the first backup node can mount the block storage device on the target virtual machine in a raw device mapping manner. Performing an instant recovery task of the virtual machine, and the first backup node generates temporary virtual data to generate a virtual machine disk file and stores the virtual machine disk file in the temporary data storer; then the first backup node uses the virtual machine disk The files are migrated to the target Data Storer for storage, completing the instant recovery task. Optionally, the first backup node may further generate the snapshot file by using the snapshot technology in the data of the target virtual machine, and store the data according to the identifier of the temporary data storer, generate the virtual machine disk file, and then virtualize the change. The machine disk files are migrated to the target destination Data Storer for storage. Optionally, the first backup node may also delete the generated snapshot file after the migration is completed. In the actual application, the snapshot file may or may not be deleted.

204. The management node saves the identifier of the WWN and the target virtual machine.

After receiving the identifier of the WWN and the target virtual machine, the management node saves the WWN and the identifier of the target virtual machine.

205. When the management node determines that the instant recovery task fails, the management node sends an instruction to perform the immediate recovery task to the second backup node.

The management node periodically monitors the progress and real-time status of the instant recovery task during actual operation. If the management node detects that the real-time status of the instant recovery task indicates that the instant recovery task is faulty (for example, the first backup node is down) If the power, the restart, or the like fails to access the backup storage, fails to read data from the production environment, and the like, the management node determines, by the load balancing mechanism, the second backup node as an execution node that performs the instant recovery task, and sends the second backup to the second backup. The node sends an instruction to perform the instant recovery task.

206. The management node sends the WWN and the identifier of the target virtual machine to the second backup node, and temporarily The identity of the Data Storer.

After the management node determines that the second backup node is the execution node of the instant recovery task, the management node sends the identifier of the WWN and the temporary Data Storer to the second backup node.

207. The second backup node virtualizes the backup data as the block storage device, and identifies the WWN for the block storage device.

The second backup node acquires the backup data after receiving the instruction sent by the management node to perform the instant recovery task, and then the second backup node virtualizes the backup data as the block storage device, and stores the device identifier for the block. The WWN.

In the embodiment of the present application, before acquiring the backup data, the management node sends the information of the backup data, the identifier of the target virtual machine, the identifier of the temporary Data Storer, and the identifier of the target Data Storer to the second backup node. The second backup node. The second backup node obtains the metadata of the backup data for verification, and the second backup node can obtain the backup data after the verification is passed. For example, after the management node determines the second backup node as the execution node that continues to execute the instant recovery task, the second backup node acquires the address of the temporary Data Storer and the address of the target Data Storer; the second backup node further Obtain the metadata of the backup data A and perform integrity check. If the second backup node determines that the backup data A is complete, the second backup node acquires the backup data A. The second backup node also needs to virtualize the backup data A as the block storage device A based on the open source software tgt, lio or scst.

208. The second backup node performs the instant recovery task by using the block storage device, the identifier of the temporary Data Storer, and the identifier of the target virtual machine.

After the second backup node acquires the block storage device, the second backup node performs the instant recovery task by using the identifier of the target virtual machine and the identifier of the temporary Data Storer.

In the embodiment of the present application, the second backup node stores temporary data in the temporary Data Storer, and the second backup node operates the target virtual machine as a virtual machine in a production environment. When the second backup node performs the instant recovery task normally, the steps performed are the same as those of the first backup node in performing the instant recovery task normally, and details are not described herein again.

In the embodiment of the present application, the second backup node and the first backup node are the same WWN as the block storage device identifier, that is, the second backup node is the same as the block storage device used by the first backup node, and the second backup is The node uses the same temporary data storer and the target virtual machine as the first backup node, so that the second backup node can perform the instant recovery task on the basis of the first backup node when performing the instant recovery task, that is, Guaranteed to resume the breakpoint.

The data processing method in the embodiment of the present application is described above. The backup server in the embodiment of the present application is described below.

Referring to FIG. 3, an embodiment of the backup server 300 in the embodiment of the present application includes: the first backup node 301, configured to virtualize backup data as a block storage device, and according to the virtual machine carried by the backup data. The specification creates a target virtual machine; identifies the global identifier name WWN for the block storage device;

The management node 302 is configured to acquire and save the identifier of the target virtual machine and the WWN; when it is determined that the instant recovery task fails, send an execution instruction for executing the instant recovery task to the second backup node;

The second backup node 303 is configured to obtain an identifier of the temporary data storage Data Storer, the WWN and an identifier of the target virtual machine, where the temporary Data Storer is preset; the backup data is virtualized as the block storage device, and The block storage device identifies the WWN; according to the block storage device, the identifier of the temporary Data Storer and the The identity of the target virtual machine performs the instant recovery task.

Optionally, the first backup node 301 is further configured to mount the block storage device to the target virtual machine in an original device mapping RDM manner, and generate a virtual machine VM disk file in the temporary data storer. Transferring the VM disk file from the temporary Data Storer to a target data store Data Storer, the target Data Storer being preset.

Optionally, the first backup node 301 is further configured to generate a snapshot file for the target virtual machine by using a snapshot technology, and generate a change virtual machine Delta VM disk file in the temporary Data Storer; and the Delta VM disk is The file is migrated by the temporary Data Storer to the target Data Storer.

Optionally, the first backup node 301 is further configured to mount the block storage device to the target virtual machine in an original device mapping RDM manner, and generate a virtual machine VM disk file in the temporary data storer. Generating a snapshot file for the target virtual machine by using a snapshot technology, and generating a change virtual machine Delta VM disk file in the temporary Data Storer; migrating the VM disk file and the Delta VM disk file from the temporary Data Storer Go to the target Data Storer.

Optionally, the first backup node is further configured to delete the snapshot file.

In the embodiment of the present application, the second backup node 303 and the first backup node 301 are the same WWN as the block storage device identifier, that is, the second backup node 303 is the same as the block storage device used by the first backup node 301. The second backup node 303 and the first backup node 301 use the same temporary data storer and the target virtual machine, so the second backup node 303 can ensure that the first backup node 301 is based on the first backup node 301. Continue to perform the instant recovery task, that is, to ensure that the resume can be resumed.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, and a read only memory (ROM, Read-Only Memory), random access memory (RAM), disk or optical disk, and other media that can store program code.

The above embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents. The modifications and substitutions of the embodiments do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A data processing method, characterized in that it runs on a backup server, the backup server includes a management node, a first backup node, and a second backup node; the first backup node is an execution node that is performing an immediate recovery task, The second backup node is an execution node that continues to execute the instant recovery task after the instant recovery task fails. The method includes:

The first backup node virtualizes the backup data into a block storage device, and creates a target virtual machine according to the specifications of the virtual machine carried in the backup data;

The first backup node identifies the global identifier name WWN for the block storage device;

The management node acquires and saves an identifier of the target virtual machine and the WWN;

When the management node determines that the instant recovery task fails, the management node sends an execution instruction for executing the instant recovery task to the second backup node;

The second backup node acquires an identifier of the temporary data storage Data Storer, the WWN, and an identifier of the target virtual machine, where the temporary Data Storer is preset;

The second backup node virtualizes the backup data as the block storage device, and identifies the WWN for the block storage device;

The second backup node performs the instant recovery task according to the block storage device, the identifier of the temporary Data Storer, and the identifier of the target virtual machine.
The method of claim 1 further comprising:

The first backup node mounts the block storage device to the target virtual machine in an original device mapping RDM manner, and generates a virtual machine VM disk file in the temporary data storer;

The first backup node migrates the VM disk file from the temporary Data Storer to a target data store Data Storer, and the target Data Storer is preset.
The method of claim 1 further comprising:

The first backup node generates a snapshot file for the target virtual machine by using a snapshot technology, and generates a change virtual machine Delta VM disk file in the temporary data storer;

The first backup node migrates the Delta VM disk file from the temporary Data Storer to the target Data Storer.
The method of claim 1 further comprising:

The first backup node mounts the block storage device to the target virtual machine in an original device mapping RDM manner, and generates a virtual machine VM disk file in the temporary data storer;

The first backup node generates a snapshot file for the target virtual machine by using a snapshot technology, and generates a change virtual machine Delta VM disk file in the temporary data storer;

The first backup node migrates the VM disk file and the Delta VM disk file from the temporary Data Storer to the target Data Storer.
The method of claim 4, wherein the method further comprises:

The first backup node deletes the snapshot file.
A backup server, comprising: a first backup node, a second backup node, and a management node, where the backup server comprises:

The first backup node is configured to virtualize the backup data as a block storage device, and create a target virtual machine according to the specification of the virtual machine carried in the backup data; and identify the global identifier name WWN for the block storage device;

The management node is configured to acquire and save the identifier of the target virtual machine and the WWN; and when it is determined that the instant recovery task fails, send an execution instruction to execute the instant recovery task to the second backup node. ;

The second backup node is configured to acquire an identifier of the temporary data storage Data Storer, the identifier of the WWN and the target virtual machine, the temporary Data Storer is preset; and the backup data is virtualized as the block storage And identifying, by the block storage device, the WWN; performing, according to the block storage device, an identifier of the temporary Data Storer and an identifier of the target virtual machine.
A backup server according to claim 6 wherein:

The first backup node is further configured to mount the block storage device to the target virtual machine in an original device mapping RDM manner, and generate a virtual machine VM disk file in the temporary data storer; The disk file is migrated by the temporary Data Storer to the target data store Data Storer, and the target Data Storer is preset.
A backup server according to claim 6 wherein:

The first backup node is further configured to generate a snapshot file for the target virtual machine by using a snapshot technology, and generate a change virtual machine Delta VM disk file in the temporary Data Storer; and use the Delta VM disk file by the temporary The Data Storer migrates to the target Data Storer.
A backup server according to claim 6 wherein

The first backup node is further configured to mount the block storage device to the target virtual machine in an original device mapping RDM manner, and generate a virtual machine VM disk file in the temporary data storer; Generating, by the target virtual machine, a snapshot file, and generating a change virtual machine Delta VM disk file in the temporary data storer; migrating the VM disk file and the Delta VM disk file from the temporary Data Storer to the target data Storer.
A backup server according to claim 9, wherein

The first backup node is further configured to delete the snapshot file.