Disaster recovery and recovery method, device, equipment and storage medium

Abstract

The present invention discloses a disaster recovery backup and disaster recovery method, device, equipment and storage medium. The method comprises: reading configuration information contained in a configuration file; creating a snapshot corresponding to the business data of the data source based on the configuration information, the data source having a snapshot function; sending the snapshot to a target virtual machine of a cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine, the target virtual machine being a virtual machine that ultimately stores the business data of the data source. Through the technical solution of the present invention, disaster recovery backup of business data based on a cloud platform can be performed according to user needs, and disaster recovery management of heterogeneous clouds can be realized without establishing an environment with the same topology structure on the cloud platform.

Description

Technical Field

[0001] The embodiments of the present invention relate to the technical field of data storage, and in particular to a disaster recovery backup and recovery method, device, equipment and storage medium. Background Art

[0002] Modern information technology has developed rapidly and its business has become extensive. The accompanying information security issues have also posed a serious threat to normal business and data security. When force majeure causes the system to fail, in order to ensure that the business system can continue to provide services stably, reliable host-based disaster recovery services are required. The cloud platform has features such as elastic and agile scheduling systems, professional infrastructure maintenance, and on-demand billing. Therefore, host disaster recovery based on the cloud platform has become an inevitable trend.

[0003] There are three main cloud-based disaster recovery methods: The first is to copy the image file of business data to the cloud platform, which requires the cloud platform to support the data format of business data, which is complex to implement, difficult to operate and maintain, and has great limitations. The second is that users build an environment with the same topology on the cloud platform to synchronize business data. The disadvantage is that the cloud platform needs to establish the same topology, which consumes a lot of resources, is costly, and has certain limitations. The third is to use the storage cluster to synchronize data. This method requires the deployment of the corresponding storage cluster in the backup area, which is not suitable for heterogeneous multi-cloud scenarios. Summary of the invention

[0004] The embodiments of the present invention provide a disaster recovery backup and recovery method, apparatus, device and storage medium to realize disaster recovery backup of business data based on a cloud platform according to user needs, and disaster recovery management of heterogeneous clouds can be realized without establishing an environment with the same topology structure on the cloud platform.

[0005] In a first aspect, an embodiment of the present invention provides a disaster recovery backup method, the method comprising:

[0006] Read the configuration information contained in the configuration file;

[0007] Creating a snapshot corresponding to the business data of the data source based on the configuration information; the data source has a snapshot function;

[0008] The snapshot is sent to a target virtual machine of a cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine. The target virtual machine is the virtual machine that ultimately receives the business data of the data source.

[0009] In a second aspect, an embodiment of the present invention further provides a disaster recovery method, the method comprising:

[0010] When a disaster occurs on the source host, the configuration information stored in the metadata management module is read;

[0011] A virtual host having the same resource configuration and network topology as the source host is created based on the configuration information, and the virtual host is connected to the virtual hard disk so that the virtual hard disk provides service data to the virtual host.

[0012] In a third aspect, an embodiment of the present invention further provides a disaster recovery backup device, the device comprising:

[0013] A reading module is used to read the configuration information contained in the configuration file;

[0014] A creation module, used to create a snapshot corresponding to the business data of the data source based on the configuration information; the data source has a snapshot function;

[0015] A sending module is used to send the snapshot to a target virtual machine of a cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine. The target virtual machine is the virtual machine that ultimately receives the business data of the data source.

[0016] In a fourth aspect, an embodiment of the present invention further provides a disaster recovery device, the device comprising:

[0017] A reading module is used to read the configuration information stored in the metadata management module when a disaster occurs on the source host;

[0018] A creation module is used to create a virtual host with the same resource configuration and network topology as the source host based on the configuration information, and the virtual host is connected to the virtual hard disk so that the virtual hard disk provides business data to the virtual host.

[0019] In the fifth aspect, an embodiment of the present invention further provides a computer device, which is a source host or a target virtual machine. The computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements a disaster recovery backup method or a disaster recovery method as described in any one of the embodiments of the present invention.

[0020] In a sixth aspect, an embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the disaster recovery backup method or disaster recovery method as described in any one of the embodiments of the present invention is implemented.

[0021] The embodiment of the present invention reads the configuration information contained in the configuration file; creates a snapshot corresponding to the business data of the data source based on the configuration information, and the data source has a snapshot function; sends the snapshot to the target virtual machine of the cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine. The target virtual machine is a virtual machine that ultimately stores the business data of the data source. The business data can be backed up based on the cloud platform for disaster recovery according to user needs, and disaster recovery management of heterogeneous clouds can be achieved without establishing an environment with the same topology structure on the cloud platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0023] Figure 1 This is a flow chart of a disaster recovery backup method in Embodiment 1 of the present invention;

[0024] Figure 2A is a schematic diagram of a direct connection mode between a source host and a target virtual machine;

[0025] Figure 2B It is a schematic diagram of a transit proxy mode between a source host and a target virtual machine;

[0026] Figure 2C It is a schematic diagram of another transit proxy mode between the source host and the target virtual machine;

[0027] Figure 2D It is a schematic diagram of another transit proxy mode between the source host and the target virtual machine;

[0028] Figure 2E It is a schematic diagram of another transit proxy mode between the source host and the target virtual machine;

[0029] Figure 3 is a flow chart of a disaster recovery method in Embodiment 3 of the present invention;

[0030] Figure 4 It is a structural schematic diagram of a disaster recovery backup device in Embodiment 4 of the present invention;

[0031] Figure 5 It is a structural schematic diagram of a disaster recovery device in Embodiment 4 of the present invention;

[0032] Figure 6It is a structural diagram of a computer device in Embodiment 6 of the present invention. DETAILED DESCRIPTION

[0033] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0034] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0035] Embodiment 1

[0036] Figure 1 A flowchart of a disaster recovery backup method provided in the first embodiment of the present invention. This embodiment is applicable to the case of backing up business data to a cloud platform. The method can be executed by a disaster recovery backup device in the embodiment of the present invention, and the device can be implemented in software and / or hardware. The disaster recovery backup device is integrated in the source host, and the source host is the host that generates the data source. The host refers to a computer that is connected to the network and can run independently; in the embodiment of the present invention, the data source refers to a file system for storing business data.

[0037] like Figure 1 As shown, the method specifically comprises the following steps:

[0038] S110, reading configuration information contained in the configuration file.

[0039] Among them, the configuration file can be written by the user himself to set the source configuration items, target configuration items, network topology, cloud platform interface protocol, resource configuration and other information corresponding to the data source based on the user's business needs. The source configuration item is used to configure the acquisition path of the data source, and the target configuration item is used to configure the virtual machine that stores the backup data of the data source.

[0040] The configuration information may include: data source name or data source directory path, virtual machine name, network topology between multiple hosts, cloud platform interface protocol or mapping relationship between nodes and other information that needs to be configured by the user.

[0041] Specifically, the host obtains the configuration file through the input device, and uses a parsing tool to read and parse the configuration information in the configuration file.

[0042] S120, creating a snapshot corresponding to the business data of the data source based on the configuration information; the data source has a snapshot function.

[0043] The data source refers to a file system used to store business data. In the embodiment of the present invention, the data source has a snapshot function. The snapshot is a fast reading technology for memory based on hardware programming technology. The file systems with the snapshot function are basically some special systems or file systems implemented for a specific function. The number of data sources can be one or more.

[0044] Specifically, the configuration information is checked and the data source is determined, and a snapshot function of the data source is used to create a snapshot corresponding to the business data contained in the data source based on the snapshot technology. Any existing technology can be used to create a snapshot corresponding to the business data contained in the data source, and the embodiment of the present invention does not limit this.

[0045] When performing disaster recovery backup of a data source to the cloud platform for the first time, you need to first create a file system in the cloud platform that is the same as the data source before you can create a snapshot; when performing disaster recovery backup of the data source in the future, if you verify that the same file system as the data source is established in the cloud platform, you can create a snapshot. If there are multiple data sources, you can create snapshots corresponding to the business data of the data source in parallel.

[0046] Optionally, the data source includes: a logical volume lvm for storing business data or a dynamic file system zfs for storing business data.

[0047] S130, sending the snapshot to a target virtual machine of the cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine, the target virtual machine being the virtual machine that ultimately stores the business data of the data source.

[0048] Wherein, a target virtual machine is created in the platform, and at least one virtual hard disk is mounted on the target virtual machine to store the business data of the data source.

[0049] Specifically, the source host where the data source is located sends the business data of the data source to the target virtual machine of the cloud platform in the form of a snapshot. The target virtual machine will receive the business data and store it in the virtual hard disk. Since the target virtual machine has multiple virtual machine hard disks mounted, it is not necessary to establish an environment with the same topology on the cloud platform during the synchronization phase of the snapshot data. For example, the source host includes: source host 1 and source host 2, the target virtual machine is virtual machine 1, and two hard disks are mounted on virtual machine 1. The business data of the data source corresponding to host 1 is stored in the corresponding hard disk 1, and the business data of the data source corresponding to host 2 is stored in the hard disk 2. However, the virtual machines in the cloud platform do not need to establish an environment with the same topology as the hosts, which can save computing resources, memory and costs.

[0050] The technical solution of this embodiment reads the configuration information contained in the configuration file; creates a snapshot corresponding to the business data of the data source based on the configuration information, and the data source has a snapshot function; sends the snapshot to the target virtual machine of the cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine. The target virtual machine is finally a virtual machine that stores the business data of the data source. It can perform disaster recovery backup of the business data based on the cloud platform according to user needs, and does not need to establish an environment with the same topology structure on the cloud platform, so as to realize disaster recovery management of heterogeneous clouds.

[0051] Embodiment 2

[0052] This embodiment is optimized based on the above embodiment. Optionally, at least one virtual machine is pre-created in the cloud platform, and the virtual machines include a target virtual machine; the metadata management module of each virtual machine stores a configuration file and a deployment mode between the source host and the target virtual machine.

[0053] Specifically, in the cloud platform, according to user needs, only one or more target virtual machines can be created to receive the business data of the source data sent by the source host, or multiple virtual machines can be created, among which one or some of the target virtual machines are designated to ultimately receive the business data of the data source, and other virtual machines are used to transfer the business data of the data source. Each virtual machine is provided with a metadata management module for storing the written configuration files.

[0054] Since the metadata management module records all source data information, the cloud platform can start only one or more virtual machines to receive the business data of the source data. Each virtual machine mounts multiple hard disks to save business data, which greatly reduces the consumption of computing resources and effectively reduces the cost of disaster recovery services.

[0055] Based on the above embodiments, the deployment mode between the source host and the target virtual machine can be set by the user.

[0056] Optionally, deployment modes include: direct connection mode and transit agent mode; in direct connection mode, the source host is connected to at least one target virtual machine respectively; in transit agent mode, the source host is connected to at least one transit agent node respectively, and each transit agent node is connected to at least one target virtual machine respectively; the transit agent node is a host other than the source host, or a virtual machine other than the target virtual machine in the cloud platform.

[0057] Specifically, in the direct connection mode, the source host corresponding to the data source is directly connected to at least one target virtual machine, and the source host can send business data corresponding to the data source to one or more target virtual machines to achieve one or more backups.

[0058] If the source host and the target virtual machine cannot be directly connected to the network, a transit proxy node is required to send the service data corresponding to the data source of the source host to the target virtual machine. In the transit proxy mode, the transit proxy node is at least one host other than the source host, and can also be at least one virtual machine other than the target virtual machine in the cloud platform. The source host is connected to the transit proxy node respectively, and the transit proxy node is connected to at least one target virtual machine respectively.

[0059] In a specific example, Figure 2A As shown, the target virtual machines include: a first target virtual machine and a second target virtual machine. In the direct connection mode, the source host corresponding to the data source is connected to the first target virtual machine and the second target virtual machine respectively, so as to realize double backup of the data source.

[0060] In another specific example, in the transit agent mode, such as Figure 2B As shown, the transit agent node is the first host. The source host corresponding to the data source is connected to the first host, and the first host is connected to the first target virtual machine. Figure 2C and Figure 2D In the example, the transit agent nodes are the first virtual machine and the second virtual machine in the cloud platform. Figure 2C As shown, the source host corresponding to the data source is connected to the first virtual machine and the second virtual machine respectively, the first virtual machine is connected to the first target virtual machine, and the second virtual machine is connected to the second target virtual machine. Figure 2D As shown, the source host corresponding to the data source is connected to the first virtual machine, the first virtual machine is connected to the second virtual machine, the first virtual machine is connected to the first target virtual machine, and the second virtual machine is connected to the second target virtual machine. That is, the source host is connected to the first target virtual machine through the first virtual machine, and the source host is connected to the second target virtual machine through the first virtual machine and the second virtual machine.

[0061] It should be noted that the above-mentioned deployment modes are relatively common scenarios, and the optimal mode should be selected based on factors such as network conditions and operational complexity. In reality, there may be more complex network structures, and the deployment mode can be flexibly adjusted as needed.

[0062] Optionally, the files used to store business data in the transit agent node include: a logical volume lvm, a dynamic file system zfs, or a folder.

[0063] like Figure 2E As shown, the method of this embodiment specifically includes the following steps:

[0064] S210, reading configuration information contained in the configuration file.

[0065] Optionally, the configuration information contained in the configuration file includes at least one of the following:

[0066] Source configuration items corresponding to the data source, target configuration items corresponding to the data source, network topology, resource configuration, resource mapping table and cloud platform interface protocol;

[0067] Among them, the source configuration items include: data source name or data source directory path, the target configuration items include: virtual machine name, network topology is used to represent the topological relationship between multiple hosts, resource configuration is used to represent the configuration information of the sending node and the receiving node; the resource mapping table is used to represent the mapping relationship between the sending node and the receiving node; the cloud platform interface protocol includes protocol, address, port and authentication access key.

[0068] Among them, in the direct connection mode, the source host acts as a sending node and the target virtual machine acts as a receiving node; in the transit agent mode, when the source host transmits business data to the transit agent node, the source host acts as a sending node and the transit agent node acts as a receiving node; when the transit agent node transmits business data to the target virtual machine, the transit agent node acts as a sending node and the target virtual machine acts as a receiving node.

[0069] S220, creating a snapshot corresponding to the business data of the data source based on the configuration information; the data source has a snapshot function.

[0070] S230, based on the deployment mode, sends a synchronization request message to the target virtual machine, and when the target virtual machine responds to the synchronization request message, sends a snapshot to the target virtual machine, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine; wherein, if the snapshot is the first snapshot, the target virtual machine receives the full business data in the snapshot; if the snapshot is not the first snapshot, the target virtual machine receives the differential business data in the snapshot.

[0071] Specifically, if the deployment mode is direct connection mode, the source host and the target virtual machine can be directly connected, and the source host directly sends synchronization request information and snapshots to the target virtual machine; if the deployment mode is transit agent mode, the source host and the target virtual machine need to be connected through a transit agent node, and the source host can send synchronization request information and snapshots to the target virtual machine through the transit agent node, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine.

[0072] If the snapshot is the first snapshot, the target virtual machine receives the full amount of business data in the snapshot; if the snapshot is not the first snapshot, the target virtual machine receives the differential business data in the snapshot. The advantage of this is that after storing as much business data as possible in the virtual hard disk, if the difference in incremental data is within the allowable range, the business is closed and the remaining incremental data is synchronized. This not only reduces business downtime, but also facilitates business migration.

[0073] The technical solution of this embodiment is to read the configuration information contained in the configuration file; create a snapshot corresponding to the business data of the data source based on the configuration information, and the data source has a snapshot function; send the snapshot to the target virtual machine of the cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine. The target virtual machine is the virtual machine that finally stores the business data of the data source, and can perform disaster recovery backup of the business data based on the cloud platform according to user needs. There is no need to establish the same topology structure environment on the cloud platform, and disaster recovery management of heterogeneous clouds can be realized.

[0074] Optionally, if the deployment mode is a direct connection mode, directly sending a synchronization request message to the target virtual machine, and when the target virtual machine responds to the synchronization request message, directly sending the snapshot to the target virtual machine;

[0075] If the deployment mode is the transit proxy mode, a synchronization request message is sent to the target virtual machine through the transit proxy node, and when the target virtual machine responds to the synchronization request message, the snapshot is sent to the target virtual machine through the transit proxy node.

[0076] For example, in the transit agent mode, Figure 2B As shown, if the transit agent node is the first host, the source host sends a synchronization request message to the first host, and when the first host responds to the synchronization request message, the source host sends the snapshot to the first host; the first host sends a synchronization request message to the target virtual machine, and when the target virtual machine responds to the synchronization request message, the first host sends the snapshot to the target virtual machine.

[0077] Embodiment 3

[0078] Figure 3 This is a flowchart of a disaster recovery method provided in the third embodiment of the present invention. This embodiment can be applied to the case where a data service is restored by creating a virtual host when a disaster occurs on the source host. The method can be executed by a disaster recovery device in the embodiment of the present invention. The device can be implemented in software and / or hardware. The disaster recovery device can be integrated into the target virtual machine. When a disaster occurs on the source host, the virtual host is used to replace the source host, obtain business data from the virtual hard disk, and restore data services.

[0079] like Figure 3 As shown, the method specifically comprises the following steps:

[0080] S310, when a disaster occurs on the source host, read the configuration information stored in the metadata management module.

[0081] Specifically, when a disaster occurs on the source host, the target virtual machine obtains configuration information from the metadata management module.

[0082] Among them, the source configuration items corresponding to the data source, the target configuration items corresponding to the data source, the network topology, the resource configuration, the resource mapping table and the cloud platform interface protocol;

[0083] Among them, the source configuration items include: data source name or data source directory path, the target configuration items include: virtual machine name, the network topology is used to represent the topological relationship between multiple hosts, the resource configuration is used to represent the configuration information of the sending node and the receiving node; the resource mapping table is used to represent the mapping relationship between the sending node and the receiving node.

[0084] Among them, in the direct connection mode, the source host acts as a sending node and the target virtual machine acts as a receiving node; in the transit agent mode, when the source host transmits business data to the transit agent node, the source host acts as a sending node and the transit agent node acts as a receiving node; when the transit agent node transmits business data to the target virtual machine, the transit agent node acts as a sending node and the target virtual machine acts as a receiving node.

[0085] S320: Create a virtual host with the same resource configuration and network topology as the source host based on the configuration information, and connect the virtual host to the virtual hard disk so that the virtual hard disk provides service data to the virtual host.

[0086] Specifically, based on the network topology and resource configuration of the source host in the configuration information, a virtual host with the same network topology and resource configuration as the source host is created in the cloud platform, and the virtual hard disk is unbound from the target virtual machine and connected to the virtual host so that the virtual host can obtain business data from the virtual hard disk.

[0087] Exemplarily, a resource orchestration task may be issued through the target virtual machine, and a cloud platform API interface may be called to create a virtual host having the same resource configuration and network topology as the source host.

[0088] The technical solution of this embodiment is to read the configuration information stored in the metadata management module when a disaster occurs in the source host; create a virtual host with the same resource configuration and network topology as the source host based on the configuration information, and connect the virtual host to the virtual hard disk so that the virtual hard disk provides business data to the virtual host. When a disaster occurs in the source host, the virtual host can obtain business data from the virtual hard disk, restore data and continue to provide services.

[0089] Embodiment 4

[0090] Figure 4 This is a schematic diagram of the structure of a disaster recovery backup device provided in Embodiment 4 of the present invention. This embodiment is applicable to the case where business data is backed up to a cloud platform. The device can be implemented in software and / or hardware. The device can be integrated in a source host that generates a data source, such as Figure 4 As shown, the disaster recovery backup device specifically includes: a reading module 410, a creating module 420 and a sending module 430.

[0091] Wherein, the reading module 410 is used to read the configuration information contained in the configuration file;

[0092] A creation module 420, configured to create a snapshot corresponding to the business data of the data source based on the configuration information; the data source has a snapshot function;

[0093] The sending module 430 is used to send the snapshot to the target virtual machine of the cloud platform so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine. The target virtual machine is the virtual machine that ultimately receives the business data of the data source.

[0094] Optionally, at least one virtual machine is pre-created in the cloud platform, and the virtual machines include a target virtual machine; the metadata management module of each of the virtual machines stores the configuration file and the deployment mode between the source host and the target virtual machine.

[0095] Optionally, the deployment modes include: a direct connection mode and a transit agent mode; the direct connection mode is that the source host is connected to at least one of the target virtual machines respectively; the transit agent mode is that the source host is connected to a transit agent node, and the transit agent node is connected to at least one target virtual machine; the transit agent node is at least one host other than the source host, or at least one virtual machine in the cloud platform other than the target virtual machine.

[0096] Optionally, the file used to store the business data in the transit agent node includes: a logical volume lvm, a dynamic file system zfs or a folder.

[0097] Optionally, the data source includes: a logical volume lvm for storing business data or a dynamic file system zfs for storing business data.

[0098] Optionally, the configuration information contained in the configuration file includes at least one of the following:

[0099] The source configuration items corresponding to the data source, the target configuration items corresponding to the data source, the network topology, the resource configuration, the resource mapping table and the cloud platform interface protocol;

[0100] The source configuration item includes: a data source name or a data source directory path; the target configuration item includes: a virtual machine name; the network topology is used to represent the topological relationship between the plurality of hosts; the resource configuration is used to represent the configuration information of the sending node and the receiving node; the resource mapping table is used to represent the mapping relationship between the sending node and the receiving node;

[0101] Among them, in the direct connection mode, the source host acts as a sending node and the target virtual machine acts as a receiving node; in the transit agent mode, when the source host transmits business data to the transit agent node, the source host acts as a sending node and the transit agent node acts as a receiving node; when the transit agent node transmits business data to the target virtual machine, the transit agent node acts as a sending node and the target virtual machine acts as a receiving node.

[0102] Optionally, the sending module 430 is specifically configured to:

[0103] Based on the deployment mode, a synchronization request message is sent to the target virtual machine, and when the target virtual machine responds to the synchronization request message, the snapshot is sent to the target virtual machine; wherein, if the snapshot is the first snapshot, the target virtual machine receives the full business data in the snapshot; if the snapshot is not the first snapshot, the target virtual machine receives the differential business data in the snapshot.

[0104] Optionally, the sending module 430 includes:

[0105] A first sending unit, configured to directly send synchronization request information to the target virtual machine if the deployment mode is a direct connection mode, and directly send the snapshot to the target virtual machine when the target virtual machine responds to the synchronization request information;

[0106] The second sending unit is used to send synchronization request information to the target virtual machine through the transit agent node if the deployment mode is the transit agent mode, and send the snapshot to the target virtual machine through the transit agent node when the target virtual machine responds to the synchronization request information.

[0107] The above-mentioned product can execute the disaster recovery backup method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0108] Embodiment 5

[0109] Figure 5This is a schematic diagram of the structure of a disaster recovery device provided in Embodiment 5 of the present invention. This embodiment is applicable to the case where a data service is restored by creating a virtual host when a disaster occurs on the source host. The device can be implemented in software and / or hardware. The device can be integrated in the target virtual machine, such as Figure 5 As shown, the disaster recovery backup device specifically includes: a reading module 510 and a creating module 520.

[0110] The reading module 510 is used to read the configuration information stored in the metadata management module when a disaster occurs on the source host;

[0111] The creation module 520 is used to create a virtual host with the same resource configuration and network topology as the source host based on the configuration information, and the virtual host is connected to the virtual hard disk so that the virtual hard disk provides business data to the virtual host.

[0112] The above-mentioned product can execute the disaster recovery method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0113] Embodiment 6

[0114] Figure 6 A block diagram of a computer device provided in Embodiment 6 of the present invention, the computer device may be a source host or a target virtual machine, such as Figure 6 As shown, the computer device includes a processor 610, a memory 620, an input device 630, and an output device 640; the number of the processor 610 in the computer device can be one or more. Figure 6 A processor 610 is taken as an example; the processor 610, memory 620, input device 630 and output device 640 in the computer device can be connected via a bus or other means. Figure 6 The example of connecting through bus is taken in the following.

[0115] The memory 620, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as the program instructions / modules corresponding to the disaster recovery method in the embodiment of the present invention (for example, the reading module 410, the creation module 420 and the sending module 430 in the disaster recovery device), or the program instructions / modules corresponding to the disaster recovery method in the embodiment of the present invention (for example, the reading module 510 and the creation module 520 in the disaster recovery device). The processor 610 executes various functional applications and data processing of the computer device by running the software programs, instructions and modules stored in the memory 620, that is, realizes the above-mentioned disaster recovery method.

[0116] The memory 620 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created according to the use of the terminal, etc. In addition, the memory 620 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 620 may further include a memory remotely arranged relative to the processor 610, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0117] The input device 630 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the computer device. The output device 640 may include a display device such as a display screen.

[0118] Embodiment 7

[0119] Embodiment 7 of the present invention provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the disaster recovery backup method provided by all the embodiments of the present invention is implemented: reading configuration information contained in a configuration file; creating a snapshot corresponding to the business data of the data source based on the configuration information; the data source has a snapshot function; sending the snapshot to a target virtual machine of a cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine, and the target virtual machine is a virtual machine that finally receives the business data of the data source;

[0120] Or implement a disaster recovery method as provided in all the embodiments of the invention of this application: when a disaster occurs in a source host, read the configuration information stored in the metadata management module; based on the configuration information, create a virtual host with the same resource configuration and network topology as the source host, and connect the virtual host to the virtual hard disk so that the virtual hard disk provides business data to the virtual host.

[0121] Any combination of one or more computer-readable media can be used. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0122] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0123] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0124] Computer program code for performing the operation of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0125] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A disaster recovery backup method, characterized in that: Applied to a source host, the source host is a host that generates a data source, the method includes: Read the configuration information contained in the configuration file; the configuration information includes at least one of the following: a source configuration item corresponding to the data source, a target configuration item corresponding to the data source, a network topology, a resource configuration, a resource mapping table, and a cloud platform interface protocol; the source configuration item includes: a data source name or a data source directory path, the target configuration item includes: a virtual machine name, the network topology is used to represent the topological relationship between the multiple hosts, the resource configuration is used to represent the configuration information of the sending node and the receiving node; the resource mapping table is used to represent the mapping relationship between the sending node and the receiving node; Based on the configuration information, snapshots corresponding to the business data of the data source can be created in parallel; the data source has a snapshot function; the data source is one or more; The snapshot is sent to a target virtual machine of a cloud platform so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine, including: based on a deployment mode, a synchronization request message is sent to the target virtual machine, and when the target virtual machine responds to the synchronization request message, the snapshot is sent to the target virtual machine to implement one or more backups; wherein, if the snapshot is the first snapshot, the target virtual machine receives the full amount of business data in the snapshot; if the snapshot is not the first snapshot, the target virtual machine receives the differential amount of business data in the snapshot; the target virtual machine is the virtual machine that finally receives the business data of the data source; Among them, at least one virtual machine is pre-created in the cloud platform, and the virtual machine includes a target virtual machine; one or part of the target virtual machines can be designated for ultimately receiving business data of the data source; the metadata management module of each virtual machine stores the configuration file, and the deployment mode between the source host and the target virtual machine; the deployment mode includes: direct connection mode and transit agent mode; the direct connection mode is that the source host is connected to at least one of the target virtual machines respectively; the transit agent mode is that the source host is connected to a transit agent node, and the transit agent node is connected to at least one target virtual machine; the transit agent node is at least one host other than the source host, or at least one virtual machine other than the target virtual machine in the cloud platform.

2. The method according to claim 1, characterized in that The files used to store the business data in the transit agent node include: a logical volume lvm, a dynamic file system zfs or a folder.

3. The method according to claim 1, characterized in that: The data source includes: a logical volume lvm for storing business data or a dynamic file system zfs for storing business data.

4. The method according to claim 1, characterized in that: In direct connection mode, the source host acts as a sending node and the target virtual machine acts as a receiving node; in transit agent mode, when the source host transmits business data to the transit agent node, the source host acts as a sending node and the transit agent node acts as a receiving node; when the transit agent node transmits business data to the target virtual machine, the transit agent node acts as a sending node and the target virtual machine acts as a receiving node.

5. The method according to claim 1, characterized in that Sending synchronization request information to the target virtual machine based on the deployment mode, and sending the snapshot to the target virtual machine when the target virtual machine responds to the synchronization request information, including: If the deployment mode is a direct connection mode, directly sending a synchronization request message to the target virtual machine, and when the target virtual machine responds to the synchronization request message, directly sending the snapshot to the target virtual machine; If the deployment mode is the transit proxy mode, a synchronization request message is sent to the target virtual machine through the transit proxy node, and when the target virtual machine responds to the synchronization request message, the snapshot is sent to the target virtual machine through the transit proxy node.

6. A disaster recovery method, characterized in that: Applied to a target virtual machine, the method comprises: When a disaster occurs in the source host, the configuration information stored in the metadata management module is read; the configuration information includes at least one of the following: a source configuration item corresponding to the data source, a target configuration item corresponding to the data source, a network topology, a resource configuration, a resource mapping table, and a cloud platform interface protocol; the source configuration item includes: a data source name or a data source directory path, the target configuration item includes: a virtual machine name, the network topology is used to represent the topological relationship between the multiple hosts, the resource configuration is used to represent the configuration information of the sending node and the receiving node; the resource mapping table is used to represent the mapping relationship between the sending node and the receiving node; Creating a virtual host having the same resource configuration and network topology as the source host based on the configuration information, and connecting the virtual host to a virtual hard disk so that the virtual hard disk provides service data to the virtual host; Among them, at least one virtual machine is pre-created in the cloud platform, and the virtual machine includes a target virtual machine; one or part of the target virtual machines can be designated for ultimately receiving business data of the data source; the metadata management module of each virtual machine stores a configuration file, and a deployment mode between the source host and the target virtual machine; the deployment mode includes: a direct connection mode and a transit agent mode; the direct connection mode is that the source host is connected to at least one of the target virtual machines respectively; the transit agent mode is that the source host is connected to a transit agent node, and the transit agent node is connected to at least one target virtual machine; the transit agent node is at least one host other than the source host, or at least one virtual machine other than the target virtual machine in the cloud platform.

7. A disaster recovery backup device, characterized in that: Integrated in a source host, the source host is a host that generates a data source, and the device includes: A reading module, used to read the configuration information contained in the configuration file; the configuration information includes at least one of the following: a source configuration item corresponding to the data source, a target configuration item corresponding to the data source, a network topology, a resource configuration, a resource mapping table, and a cloud platform interface protocol; the source configuration item includes: a data source name or a data source directory path, the target configuration item includes: a virtual machine name, the network topology is used to represent the topological relationship between the plurality of hosts, the resource configuration is used to represent the configuration information of the sending node and the receiving node; the resource mapping table is used to represent the mapping relationship between the sending node and the receiving node; A creation module, configured to execute in parallel the creation of snapshots corresponding to the business data of the data source based on the configuration information; the data source has a snapshot function; the data source is one or more; A sending module, used for sending the snapshot to a target virtual machine of a cloud platform, so that the target virtual machine receives the business data in the snapshot and stores it in at least one virtual hard disk mounted by the target virtual machine, including: based on a deployment mode, sending a synchronization request message to the target virtual machine, and when the target virtual machine responds to the synchronization request message, sending the snapshot to the target virtual machine to implement one or more backups; wherein, if the snapshot is a first snapshot, the target virtual machine receives the full amount of business data in the snapshot; if the snapshot is not a first snapshot, the target virtual machine receives the differential amount of business data in the snapshot; the target virtual machine is the virtual machine that finally receives the business data of the data source; Among them, at least one virtual machine is pre-created in the cloud platform, and the virtual machine includes a target virtual machine; one or part of the target virtual machines can be designated for ultimately receiving business data of the data source; the metadata management module of each virtual machine stores the configuration file, and the deployment mode between the source host and the target virtual machine; the deployment mode includes: direct connection mode and transit agent mode; the direct connection mode is that the source host is connected to at least one of the target virtual machines respectively; the transit agent mode is that the source host is connected to a transit agent node, and the transit agent node is connected to at least one target virtual machine; the transit agent node is at least one host other than the source host, or at least one virtual machine other than the target virtual machine in the cloud platform.

8. A disaster recovery device, characterized in that: Integrated in a target virtual machine, the target virtual machine is a virtual machine that ultimately stores business data of a data source, the device comprising: A reading module is used to read the configuration information stored in the metadata management module when a disaster occurs in the source host; the configuration information includes at least one of the following: a source configuration item corresponding to the data source, a target configuration item corresponding to the data source, a network topology, a resource configuration, a resource mapping table, and a cloud platform interface protocol; the source configuration item includes: a data source name or a data source directory path, the target configuration item includes: a virtual machine name, the network topology is used to represent the topological relationship between the multiple hosts, the resource configuration is used to represent the configuration information of the sending node and the receiving node; the resource mapping table is used to represent the mapping relationship between the sending node and the receiving node; A creation module, used for creating a virtual host having the same resource configuration and network topology as the source host based on the configuration information, and the virtual host is connected to a virtual hard disk so that the virtual hard disk provides service data to the virtual host; Among them, at least one virtual machine is pre-created in the cloud platform, and the virtual machine includes a target virtual machine; one or part of the target virtual machines can be designated for ultimately receiving business data of the data source; the metadata management module of each virtual machine stores a configuration file, and a deployment mode between the source host and the target virtual machine; the deployment mode includes: a direct connection mode and a transit agent mode; the direct connection mode is that the source host is connected to at least one of the target virtual machines respectively; the transit agent mode is that the source host is connected to a transit agent node, and the transit agent node is connected to at least one target virtual machine; the transit agent node is at least one host other than the source host, or at least one virtual machine other than the target virtual machine in the cloud platform.

9. A computer device, the computer device being a source host or a target virtual machine, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor. If the computer device is a source host, the processor implements the disaster recovery method as described in any one of claims 1 to 5 when executing the program; if the computer device is a target virtual machine, the processor implements the disaster recovery method as described in claim 6 when executing the program.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the program is executed by a processor, the disaster recovery method as described in any one of claims 1 to 5 is implemented, or the disaster recovery method as described in claim 6 is implemented.

Images