CN112000437A - Disaster recovery method and device, electronic equipment and storage medium - Google Patents

Disaster recovery method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN112000437A
CN112000437A CN202010851571.1A CN202010851571A CN112000437A CN 112000437 A CN112000437 A CN 112000437A CN 202010851571 A CN202010851571 A CN 202010851571A CN 112000437 A CN112000437 A CN 112000437A
Authority
CN
China
Prior art keywords
virtual machine
standby
creating
instruction
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010851571.1A
Other languages
Chinese (zh)
Inventor
李东岳
郭涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jinan Inspur Data Technology Co Ltd
Original Assignee
Jinan Inspur Data Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jinan Inspur Data Technology Co Ltd filed Critical Jinan Inspur Data Technology Co Ltd
Priority to CN202010851571.1A priority Critical patent/CN112000437A/en
Publication of CN112000437A publication Critical patent/CN112000437A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1479Generic software techniques for error detection or fault masking
    • G06F11/1482Generic software techniques for error detection or fault masking by means of middleware or OS functionality
    • G06F11/1484Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45562Creating, deleting, cloning virtual machine instances

Abstract

The application discloses a disaster recovery method, a disaster recovery device, electronic equipment and a storage medium, wherein the method comprises the following steps: the method comprises the steps that when a main virtual machine is established, an establishing instruction of a standby virtual machine is obtained, wherein the establishing instruction comprises a delay establishing instruction and an immediate establishing instruction; executing the relevant operation of the standby virtual machine according to the creating instruction; when the disaster occurs to the main virtual machine, judging whether a standby virtual machine exists in the standby data center; if the standby virtual machine does not exist, establishing an operating environment on the standby data center according to the operating environment data stored in the standby data center; the operating environment data corresponds to the primary virtual machine; creating a standby virtual machine according to the running environment; mounting a standby cloud hard disk on a standby virtual machine, and switching the standby virtual machine into a main virtual machine; and the data in the standby cloud hard disk is consistent with the data in the main cloud hard disk corresponding to the main virtual machine. The method and the device support the separation of data backup and virtual machine backup, and a standby virtual machine cannot be created when no disaster occurs, so that a large amount of physical resources are saved.

Description

Disaster recovery method and device, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of disaster recovery, and in particular, to a disaster recovery method, a disaster recovery device, an electronic device, and a storage medium.
Background
With the development of information technology, cloud computing has gradually become a development hotspot in the industry, and the cloud computing technology is also gradually applied to multiple fields of education, science, culture, public security, government, sanitation, high-performance computing, electronic commerce, internet of things and the like, and accordingly, the usage amount and the activity of cloud computing service platforms are increasing day by day. With the development of cloud computing, the cloud computing management platform system is gradually huge, and the cloud computing management platform has higher requirements on the speed and the cache of data query.
In the related art, a standby virtual machine corresponding to a virtual machine is created while the virtual machine is created, and then data synchronization is performed on a main virtual machine and the standby virtual machine, but the probability of occurrence of a disaster is low, and if the main virtual machine and the standby virtual machine are created at the same time, resource waste is caused.
Therefore, how to provide a solution to the above technical problem is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The application aims to provide a disaster recovery method, a disaster recovery device, an electronic device and a computer readable storage medium, which support the separation of data backup and virtual machine backup, and do not create a backup virtual machine when there is no disaster, thereby saving a large amount of physical resources. The specific scheme is as follows:
the application provides a disaster recovery method, which comprises the following steps:
the method comprises the steps that when a main virtual machine is established, an establishing instruction of a standby virtual machine is obtained, wherein the establishing instruction comprises a delay establishing instruction and an immediate establishing instruction;
executing the relevant operation of the standby virtual machine according to the creating instruction;
judging whether the standby virtual machine exists in a standby data center or not after the primary virtual machine has a disaster;
if the standby virtual machine does not exist, creating an operating environment on the standby data center according to the operating environment data stored in the standby data center; the operating environment data corresponds to the primary virtual machine;
creating the standby virtual machine according to the running environment;
mounting a standby cloud hard disk on the standby virtual machine, and switching the standby virtual machine into the main virtual machine; and the data in the standby cloud hard disk is consistent with the data in the main cloud hard disk corresponding to the main virtual machine.
Preferably, the executing the relevant operation of the standby virtual machine according to the creating instruction includes:
when the creation instruction is the delay creation instruction, storing the operating environment data of the primary virtual machine in the standby data center, and pairing and synchronizing the primary cloud hard disk of the primary data center and the standby cloud hard disk of the standby data center.
Preferably, the executing the relevant operation of the standby virtual machine according to the creating instruction includes:
when the creating instruction is the instant creating instruction, inquiring the operating environment data of the primary virtual machine, and creating the operating environment according to the operating environment data;
and creating the standby virtual machine according to the running environment so as to synchronize the main virtual machine and the standby virtual machine.
Preferably, before the obtaining of the creating instruction of the standby virtual machine, the method further includes:
determining a target protection group on a primary data center, the target protection group comprising a plurality of the primary virtual machines.
Preferably, the operating environment data includes: VDC, VPC, network, security group, host specification and the master cloud hard disk.
Preferably, the switching the standby virtual machine to the primary virtual machine includes:
and executing the production environment and the production flow on the virtual machine.
The application provides a disaster recovery device, includes:
the system comprises a primary virtual machine creating module, a standby virtual machine creating module and a standby virtual machine creating module, wherein the primary virtual machine creating module is used for creating a primary virtual machine and simultaneously acquiring a creating instruction of a standby virtual machine, and the creating instruction comprises a delay creating instruction and an immediate creating instruction;
the execution module is used for executing the relevant operation of the standby virtual machine according to the creation instruction;
the judging module is used for judging whether the standby virtual machine exists in the standby data center or not after the main virtual machine has a disaster;
the running environment creating module is used for creating a running environment on the standby data center according to the running environment data stored in the standby data center if the standby virtual machine does not exist; the operating environment data corresponds to the primary virtual machine;
the standby virtual machine creating module is used for creating the standby virtual machine according to the running environment;
the switching module is used for mounting a standby cloud hard disk on the standby virtual machine and switching the standby virtual machine into the main virtual machine; and the data in the standby cloud hard disk is consistent with the data in the main cloud hard disk corresponding to the main virtual machine.
Preferably, the execution module includes:
the storage unit is configured to store the operating environment data of the primary virtual machine in the standby data center and pair and synchronize the primary cloud hard disk of the primary data center and the standby cloud hard disk of the standby data center when the creation instruction is the delayed creation instruction.
The application provides an electronic device, including:
a memory for storing a computer program;
a processor for implementing the steps of the disaster recovery method as described above when executing the computer program.
The present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the disaster recovery method as described above.
The application provides a disaster recovery method, which comprises the following steps: the method comprises the steps that when a main virtual machine is established, an establishing instruction of a standby virtual machine is obtained, wherein the establishing instruction comprises a delay establishing instruction and an immediate establishing instruction; executing the relevant operation of the standby virtual machine according to the creating instruction; when the disaster occurs to the main virtual machine, judging whether a standby virtual machine exists in the standby data center; if the standby virtual machine does not exist, establishing an operating environment on the standby data center according to the operating environment data stored in the standby data center; the operating environment data corresponds to the primary virtual machine; creating a standby virtual machine according to the running environment; mounting a standby cloud hard disk on a standby virtual machine, and switching the standby virtual machine into a main virtual machine; and the data in the standby cloud hard disk is consistent with the data in the main cloud hard disk corresponding to the main virtual machine.
Therefore, after the operation environment is created according to the operation environment data, the standby virtual machine is created, and then the standby cloud hard disk is hung on the standby virtual machine, so that the quasi-standby switching is realized, the data backup and the virtual machine backup are separated, the standby virtual machine cannot be created when no disaster exists, and a large amount of physical resources are saved.
The application also provides a disaster recovery device, an electronic device and a computer readable storage medium, all having the above beneficial effects, which are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a disaster recovery method provided in an embodiment of the present application;
fig. 2 is a schematic structural diagram of an ICM nanotube backup data center according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of an operating environment created in a backup data center according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a disaster recovery device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the related art, a standby virtual machine corresponding to a virtual machine is created while the virtual machine is created, and then data synchronization is performed on a main virtual machine and the standby virtual machine, but the probability of occurrence of a disaster is low, and if the main virtual machine and the standby virtual machine are created at the same time, resource waste is caused. Based on the above technical problems, this embodiment provides a disaster recovery method, which supports separation of data backup and virtual machine backup, and does not create a backup virtual machine when there is no disaster, thereby saving a large amount of physical resources, specifically referring to fig. 1, where fig. 1 is a flowchart of a disaster recovery method provided in this embodiment of the present application, and specifically includes:
s101, while a main virtual machine is created, a creation instruction of a standby virtual machine is obtained;
the create instruction includes a delay create instruction and an immediate create instruction.
In this step, when the primary virtual machine is created, the user may select a creation instruction, and at this time, the cloud management platform receives a creation instruction about the standby virtual machine from the user, where the creation instruction includes, but is not limited to, a delayed creation instruction and an immediate creation instruction.
S102, executing relevant operations of the standby virtual machine according to the creation instruction;
in an implementation manner, the executing the relevant operation of the virtual machine according to the creating instruction comprises the following steps: when the creation instruction is a delay creation instruction, storing the operating environment data of the primary virtual machine in the standby data center, and pairing and synchronizing a primary cloud hard disk of the primary data center and a standby cloud hard disk of the standby data center;
when the creation instruction is a delayed creation instruction, storing running environment data, which is information required by the running environment of the primary virtual machine, in the standby data center, wherein the running environment data includes but is not limited to: VDC (virtual data center), VPC (virtual private cloud), network, security group, host specification and main cloud hard disk, wherein the VDC is used for binding resources (dividing CPU, memory, hard disk, network, subnet and the like) and limiting and isolating tenants; VPCs, wherein a user manages own network resources by using the VPCs, different VPCs are isolated from each other by the networks, and the VPCs comprise networks, routers, firewalls, load balancers and the like; the host specification is as follows: including information such as CPU, hard disk, memory, etc.
And then, a standby cloud hard disk is created for the standby data center, the standby cloud hard disk is paired with and synchronized with a main cloud hard disk of the main data center, data can be protected, data backup is realized, however, virtual machine backup is not realized at the moment, only when needed, an operating environment is created according to operating environment data, a standby virtual machine is created according to the operating environment, and the standby cloud hard disk is hung on the standby virtual machine, so that the main virtual machine and the standby virtual machine are synchronized.
In another implementation, the performing the relevant operation of the virtual machine according to the creating instruction includes: when the creating instruction is an instant creating instruction, inquiring the operating environment data of the main virtual machine, and creating an operating environment according to the operating environment data; and creating a standby virtual machine according to the running environment so as to synchronize the main virtual machine and the standby virtual machine.
When the creating instruction is an instant creating instruction, creating an operating environment according to the operating environment data; and creating a standby virtual machine according to the running environment so as to synchronize the main virtual machine and the standby virtual machine.
S103, judging whether a standby virtual machine exists in the standby data center or not after the main virtual machine has a disaster;
the disaster recovery system of the embodiment comprises: the system comprises a main data center, a standby data center and a cloud management platform. The cloud management platform is used for managing the main data center and the standby data center. The disaster recovery method provided in this embodiment is mainly applied to a cloud management platform, and this embodiment does not limit the cloud management platform, and may be an ICM (international cloud manager, cloud management platform) of a wave cloud management platform. The creation of the standby virtual machine in this embodiment includes two ways, one is to create the standby virtual machine immediately after the primary virtual machine is created, and the other is to create the standby virtual machine after the primary virtual machine is created and with a delay. The purpose of this step is to determine whether a standby virtual machine exists on the standby data center. It can be understood that, in this embodiment, the method is not limited to only when a disaster occurs in the primary virtual machine, but also when a user needs to establish a standby virtual machine at any time, which is not limited in this embodiment, as long as the purpose of this embodiment can be achieved.
And if the standby virtual machine exists, switching the standby virtual machine into the main virtual machine.
The method comprises the following steps that two conditions of a standby virtual machine exist, wherein the first condition is that the standby virtual machine is established when a main virtual machine is established; the other situation is that the creation of the standby virtual machine is delayed and is established before the disaster happens to the primary virtual machine, and the establishment process comprises the steps of obtaining a creation instruction of the standby virtual machine; when the creation instruction is a delay creation instruction, storing the operating environment data of the primary virtual machine in the standby data center, and pairing and synchronizing a primary cloud hard disk of the primary data center and a standby cloud hard disk of the standby data center; when the time is preset, creating an operating environment on the standby data center according to the operating environment data stored in the standby data center; the operating environment data corresponds to the primary virtual machine; creating a standby virtual machine according to the running environment; and mounting the standby cloud hard disk on the standby virtual machine to complete the creation of the standby virtual machine.
Therefore, in this embodiment, a user can select whether to immediately create the backup virtual machine of the disaster recovery, and if the backup virtual machine of the disaster recovery is created with a delay, the current running environment of the main virtual machine and the metadata thereof are saved.
Further, the cloud platform is complex in service, so that the maintenance is difficult, and the troubleshooting is difficult when a problem occurs. The invention provides and optimizes the function of the disaster recovery virtual machine, supports the backup of data only and supports the consistency protection of the data by taking a service as a unit, supports the separation of the data backup and the virtual machine backup when the virtual machine is backed up, and provides a selection for a user, thereby saving a large amount of physical resources. Before obtaining the creating instruction of the standby virtual machine, the method further comprises the following steps: a target protection group is determined on a primary data center, the target protection group including a plurality of primary virtual machines.
The method comprises the steps of determining a target protection group on a main data center, wherein the target protection group comprises a plurality of main virtual machines, then obtaining creating instructions of standby virtual machines of the main virtual machines, then creating an operating environment and corresponding standby virtual machines for each main virtual machine, mounting corresponding standby cloud hard disks, and carrying out consistency protection on data by taking a service as a unit.
S104, if the standby virtual machine does not exist, establishing an operating environment on the standby data center according to the operating environment data stored in the standby data center; the operating environment data corresponds to the primary virtual machine;
if the standby virtual machine does not exist, the standby virtual machine is not established, and at the moment, the running environment capable of running the standby virtual machine can be established according to the running environment data stored in the standby data center, wherein the running environment is consistent with the running environment of the main virtual machine.
S105, creating a standby virtual machine according to the running environment;
and after the operating environment is created, creating a standby virtual machine so that the standby virtual machine can operate in the operating environment.
S106, mounting the standby cloud hard disk on the standby virtual machine, and switching the standby virtual machine into a main virtual machine; and the data in the standby cloud hard disk is consistent with the data in the main cloud hard disk corresponding to the main virtual machine.
And mounting a standby cloud hard disk of the standby data center on the standby virtual machine to ensure the consistency of the main virtual machine and the standby virtual machine, switching the standby virtual machine into the main virtual machine, and continuously executing the read-write function.
Further, switching the standby virtual machine to the primary virtual machine includes: and executing the production environment and the production flow on the standby virtual machine.
In summary, it can be known that, in a related scheme, when a virtual machine is created, a primary and a secondary virtual machines are created at the same time, and then data synchronization is performed on the primary and the secondary virtual machines, but disaster recovery cannot be performed on the created virtual machine, however, in this embodiment, disaster recovery can still be performed on the created virtual machine, and a user can select whether to immediately create the virtual machine or delay creation of the virtual machine, and for delay creation of the virtual machine, only a backup cloud hard disk is created to protect data of the virtual machine, but a running environment on which the virtual machine depends and the secondary virtual machine may not be created first, and the virtual machine is created when disaster recovery is performed actually, so that resource usage is saved.
Based on the above technical solution, in the embodiment, delayed creation or immediate creation may be autonomously selected while creating the primary virtual machine, after a disaster occurs, if there is no standby virtual machine in the standby data center, that is, when delayed creation is selected, at this time, operating environment data corresponding to the primary virtual machine is stored in the standby data center, and data backup in the primary cloud hard disk corresponding to the primary virtual machine is in the standby cloud hard disk in the standby data center, so that, after an operating environment is created according to the operating environment data, the standby virtual machine is created, and then the standby cloud hard disk is hung on the standby virtual machine, thereby implementing quasi-master-slave switching, supporting separation of data backup and virtual machine backup, and not creating the standby virtual machine when there is no disaster, thereby saving a large amount of physical resources.
Based on the foregoing embodiment, this embodiment provides a specific disaster recovery method, which supports a cloud host disaster recovery method of CPU architectures such as x86, mips, arm64, and the like, and when backing up a virtual machine, supports separation of data backup and VM backup, and provides a selection for a user, where the method includes:
the ICM (cloud management platform) manages the active and standby data centers. Referring to fig. 2, fig. 2 is a schematic structural diagram of an ICM nanotube active/standby data center according to an embodiment of the present disclosure. The disaster recovery system comprises: the system comprises a main data center, a standby data center and a cloud management platform. The cloud management platform is used for managing the main data center and the standby data center.
Fig. 3 illustrates a disaster recovery process, where fig. 3 is a schematic diagram of an operating environment created in a backup data center according to an embodiment of the present disclosure. The specific implementation process is as follows:
(1) in the primary data center, a virtual machine to be disaster-tolerant is selected from the list of the existing virtual machines, and the selected virtual machine becomes the primary virtual machine (the scheme supports the disaster tolerance of the existing virtual machines, namely, a post-disaster tolerance mode, and the standby virtual machine does not need to be created when the virtual machine is created). The user can protect the virtual machines by taking a group of services as a unit, the virtual machines are put into a protection group, one group of services can have a plurality of virtual machines, the selected plurality of virtual machines are synchronized consistently, and the integrity of the services is ensured. Therefore, a client selects multiple virtual machines in a main data center, protection is carried out by taking a service group as a unit, and the user can select whether to immediately create the virtual machines in a standby data center;
(2) after the protection group is selected, a user is allowed to select whether to immediately create a standby virtual machine on the standby data center on the cloud management platform.
(3) And if the user selects the immediate creation instruction, inquiring the running environment data required by the running of the primary virtual machine, such as VDC, VPC, network, security group, host specification and cloud hard disk. The sizes of the standby cloud hard disk and the main cloud hard disk are kept consistent so that real-time backup of data can be achieved. A pure backup virtual machine is generally very limited because if a backup virtual machine is created on the backup in case of a disaster, but if a group of multiple virtual machines of a service cannot communicate with each other, only the virtual machine is created, and thus the use scenarios are limited. After the operating environment is established, a standby virtual machine is established from the standby data center, and then the standby virtual machine and the standby virtual machine are synchronized in real time. Therefore, if the user selects to create the virtual machine immediately, the network environment and the attributes of the virtual machine operated by the standby virtual machine are created immediately in the standby data center.
(4) If the user chooses to delay creation, only the information needed by the virtual machine runtime environment, such as VDCs, VPCs, networks, security groups, host specifications, and cloud drives, is saved on the backup data center. And then pairing and synchronizing the standby cloud hard disk created on the standby data center and the main cloud hard disk of the main data center, and protecting the data. The probability of disaster occurrence is relatively small, and when the disaster occurs, a standby virtual machine is created on the standby data center. Therefore, if the user selects to delay the creation of the virtual machine, the environment required by the running of the standby virtual machine, such as information of VPC, network, host specification and the like, is protected for use when the standby virtual machine is created when a subsequent disaster occurs. And then, a standby cloud hard disk is created, so that additional resources such as a CPU, a VPC, a memory, a network and a security group are not required to be occupied.
After a disaster occurs, if the standby virtual machine does not exist, the standby virtual machine is created, and then the main and standby switching is carried out, so that the production environment and the process are transferred to the standby virtual machine, and the service operation of the standby virtual machine is all normal.
Based on the technical scheme, the embodiment provides the post backup, and can backup the created virtual machine; the consistency protection of data can be provided for a group of multiple virtual machines by taking a service as a unit; when the virtual machine is backed up, the data backup and the virtual machine backup are separated, a selection is provided for a user, and the user can not create the backup virtual machine immediately, so that a large amount of physical resources are saved. The scheme not only supports the traditional X86 architecture, but also supports CPU architectures such as mips and arm 64.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a disaster recovery device according to an embodiment of the present application, where the disaster recovery device described below and the disaster recovery method described above are referred to in correspondence, and the disaster recovery device includes:
a primary virtual machine creating module 201, configured to obtain a creating instruction of a standby virtual machine while creating a primary virtual machine, where the creating instruction includes a delay creating instruction and an immediate creating instruction;
an execution module 202, configured to execute, according to the creation instruction, a relevant operation of the virtual machine;
the judging module 203 is configured to judge whether a standby virtual machine exists in the standby data center after a disaster occurs in the primary virtual machine;
the running environment creating module 204 is configured to create a running environment on the standby data center according to the running environment data stored in the standby data center if the standby virtual machine does not exist; the operating environment data corresponds to the primary virtual machine;
a standby virtual machine creating module 205, configured to create a standby virtual machine according to an operating environment;
the switching module 206 is configured to mount the standby cloud hard disk on the standby virtual machine, and switch the standby virtual machine to the primary virtual machine; and the data in the standby cloud hard disk is consistent with the data in the main cloud hard disk corresponding to the main virtual machine.
Preferably, the execution module 202 includes:
and the storage unit is used for storing the operating environment data of the primary virtual machine in the standby data center and pairing and synchronizing the primary cloud hard disk of the primary data center and the standby cloud hard disk of the standby data center when the creation instruction is a delayed creation instruction.
Preferably, the execution module 202 includes:
the query unit is used for querying the operating environment data of the main virtual machine when the creation instruction is an immediate creation instruction, and creating an operating environment according to the operating environment data;
and the creating unit is used for creating the standby virtual machine according to the running environment so as to synchronize the main virtual machine and the standby virtual machine.
Preferably, the method further comprises the following steps:
and the target protection group determining module is used for determining a target protection group on the main data center, and the target protection group comprises a plurality of main virtual machines.
Preferably, the operating environment data includes: VDC, VPC, network, security group, host specification, and master cloud disk.
Preferably, the switching module 206 includes:
and the execution unit is used for executing the production environment and the production flow on the standby virtual machine.
Since the embodiments of the apparatus portion and the method portion correspond to each other, please refer to the description of the embodiments of the method portion for the embodiments of the apparatus portion, which is not repeated here.
In the following, an electronic device provided in an embodiment of the present application is introduced, and the electronic device described below and the disaster recovery method described above may be referred to correspondingly.
The present embodiment provides an electronic device, including:
a memory for storing a computer program;
and the processor is used for realizing the steps of the disaster recovery method when executing the computer program.
Since the embodiment of the electronic device portion corresponds to the embodiment of the disaster recovery method portion, please refer to the description of the embodiment of the disaster recovery method portion for the embodiment of the electronic device portion, and details are not repeated here.
The following describes a computer-readable storage medium provided by embodiments of the present application, and the computer-readable storage medium described below and the method described above may be referred to correspondingly.
The present embodiment provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the disaster recovery method as described above.
Since the embodiment of the computer-readable storage medium portion and the embodiment of the method portion correspond to each other, please refer to the description of the embodiment of the method portion for the embodiment of the computer-readable storage medium portion, which is not repeated here.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The disaster recovery method, the disaster recovery device, the electronic device, and the computer-readable storage medium provided by the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.

Claims (10)

1. A disaster recovery method is characterized by comprising the following steps:
the method comprises the steps that when a main virtual machine is established, an establishing instruction of a standby virtual machine is obtained, wherein the establishing instruction comprises a delay establishing instruction and an immediate establishing instruction;
executing the relevant operation of the standby virtual machine according to the creating instruction;
judging whether the standby virtual machine exists in a standby data center or not after the primary virtual machine has a disaster;
if the standby virtual machine does not exist, creating an operating environment on the standby data center according to the operating environment data stored in the standby data center; the operating environment data corresponds to the primary virtual machine;
creating the standby virtual machine according to the running environment;
mounting a standby cloud hard disk on the standby virtual machine, and switching the standby virtual machine into the main virtual machine; and the data in the standby cloud hard disk is consistent with the data in the main cloud hard disk corresponding to the main virtual machine.
2. The disaster recovery method of claim 1, wherein the performing the operations associated with the virtual machine according to the create instruction comprises:
when the creation instruction is the delay creation instruction, storing the operating environment data of the primary virtual machine in the standby data center, and pairing and synchronizing the primary cloud hard disk of the primary data center and the standby cloud hard disk of the standby data center.
3. The disaster recovery method of claim 2, wherein the performing the operations associated with the virtual machine according to the create instruction comprises:
when the creating instruction is the instant creating instruction, inquiring the operating environment data of the primary virtual machine, and creating the operating environment according to the operating environment data;
and creating the standby virtual machine according to the running environment so as to synchronize the main virtual machine and the standby virtual machine.
4. The disaster recovery method of claim 1, wherein before obtaining the creation instruction of the standby virtual machine, the method further comprises:
determining a target protection group on a primary data center, the target protection group comprising a plurality of the primary virtual machines.
5. Disaster recovery method according to claim 1, wherein said operational environment data comprises: VDC, VPC, network, security group, host specification and the master cloud hard disk.
6. The disaster recovery method according to any one of claims 1 to 5, wherein the switching the standby virtual machine to the primary virtual machine includes:
and executing the production environment and the production flow on the virtual machine.
7. A disaster recovery device, comprising:
the system comprises a primary virtual machine creating module, a standby virtual machine creating module and a standby virtual machine creating module, wherein the primary virtual machine creating module is used for creating a primary virtual machine and simultaneously acquiring a creating instruction of a standby virtual machine, and the creating instruction comprises a delay creating instruction and an immediate creating instruction;
the execution module is used for executing the relevant operation of the standby virtual machine according to the creation instruction;
the judging module is used for judging whether the standby virtual machine exists in the standby data center or not after the main virtual machine has a disaster;
the running environment creating module is used for creating a running environment on the standby data center according to the running environment data stored in the standby data center if the standby virtual machine does not exist; the operating environment data corresponds to the primary virtual machine;
the standby virtual machine creating module is used for creating the standby virtual machine according to the running environment;
the switching module is used for mounting a standby cloud hard disk on the standby virtual machine and switching the standby virtual machine into the main virtual machine; and the data in the standby cloud hard disk is consistent with the data in the main cloud hard disk corresponding to the main virtual machine.
8. The disaster recovery device of claim 7, wherein the execution module comprises:
the storage unit is configured to store the operating environment data of the primary virtual machine in the standby data center and pair and synchronize the primary cloud hard disk of the primary data center and the standby cloud hard disk of the standby data center when the creation instruction is the delayed creation instruction.
9. An electronic device, comprising:
a memory for storing a computer program;
processor for implementing the steps of the disaster recovery method according to any one of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the disaster recovery method according to any one of claims 1 to 6.
CN202010851571.1A 2020-08-21 2020-08-21 Disaster recovery method and device, electronic equipment and storage medium Pending CN112000437A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010851571.1A CN112000437A (en) 2020-08-21 2020-08-21 Disaster recovery method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010851571.1A CN112000437A (en) 2020-08-21 2020-08-21 Disaster recovery method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112000437A true CN112000437A (en) 2020-11-27

Family

ID=73472350

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010851571.1A Pending CN112000437A (en) 2020-08-21 2020-08-21 Disaster recovery method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112000437A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114706661A (en) * 2022-05-31 2022-07-05 武汉四通信息服务有限公司 Disaster recovery backup method and system for virtual machine, computer equipment and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2006262046A1 (en) * 2005-06-24 2007-01-04 Catalogic Software, Inc. System and method for virtualizing backup images
CN105094897A (en) * 2015-07-02 2015-11-25 华为技术有限公司 Virtual machine starting method, cloud access equipment and cloud computing center
CN105242990A (en) * 2015-10-28 2016-01-13 浪潮(北京)电子信息产业有限公司 Cloud platform based data backup method and apparatus
US20160117231A1 (en) * 2014-10-23 2016-04-28 Unitrends, Inc. Complex Network Modeling For Disaster Recovery
CN109669812A (en) * 2018-11-27 2019-04-23 武汉烽火信息集成技术有限公司 Cloud data center disaster tolerance system and method based on data distribution backup
CN109828867A (en) * 2019-01-31 2019-05-31 郑州云海信息技术有限公司 A kind of cloud host disaster recovery method and system across data center
CN111143114A (en) * 2018-11-02 2020-05-12 深信服科技股份有限公司 Virtualization platform disaster tolerance method, system, server and storage medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2006262046A1 (en) * 2005-06-24 2007-01-04 Catalogic Software, Inc. System and method for virtualizing backup images
US20160117231A1 (en) * 2014-10-23 2016-04-28 Unitrends, Inc. Complex Network Modeling For Disaster Recovery
CN105094897A (en) * 2015-07-02 2015-11-25 华为技术有限公司 Virtual machine starting method, cloud access equipment and cloud computing center
CN105242990A (en) * 2015-10-28 2016-01-13 浪潮(北京)电子信息产业有限公司 Cloud platform based data backup method and apparatus
CN111143114A (en) * 2018-11-02 2020-05-12 深信服科技股份有限公司 Virtualization platform disaster tolerance method, system, server and storage medium
CN109669812A (en) * 2018-11-27 2019-04-23 武汉烽火信息集成技术有限公司 Cloud data center disaster tolerance system and method based on data distribution backup
CN109828867A (en) * 2019-01-31 2019-05-31 郑州云海信息技术有限公司 A kind of cloud host disaster recovery method and system across data center

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
杨皓森等: "面向OpenStack/Ceph的虚拟机备份系统研究", 《计算机系统应用》 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114706661A (en) * 2022-05-31 2022-07-05 武汉四通信息服务有限公司 Disaster recovery backup method and system for virtual machine, computer equipment and storage medium

Similar Documents

Publication Publication Date Title
EP3819757A1 (en) Edge application management method and system
CN109831500B (en) Synchronization method for configuration file and Pod in Kubernetes cluster
CN109151045B (en) Distributed cloud system and monitoring method
US20200092222A1 (en) Automated migration of compute instances to isolated virtual networks
US11057471B2 (en) Edge application management method and system
US20130091376A1 (en) Self-repairing database system
KR20060051932A (en) Updating software while it is running
US10860375B1 (en) Singleton coordination in an actor-based system
CN107666493B (en) Database configuration method and equipment thereof
CN113032085A (en) Management method, device, server, management system and medium of cloud operating system
US20220206902A1 (en) Application template for application consistent backup and restore of database applications in kubernetes
CN105242990A (en) Cloud platform based data backup method and apparatus
CN111309443B (en) Virtualization method, device, equipment and storage medium of Internet of things equipment system
CN112328365A (en) Virtual machine migration method, device, equipment and storage medium
CN105183591A (en) High-availability cluster implementation method and system
CN111552540A (en) Resource synchronization method based on VMware cloud platform and super-fusion cloud platform
CN112000437A (en) Disaster recovery method and device, electronic equipment and storage medium
CN114201458B (en) Information updating method, micro-service system and computer readable storage medium
CN111008095A (en) State snapshot generation and recovery method facing edge cloud
US9348672B1 (en) Singleton coordination in an actor-based system
CN115174596A (en) Equipment remote copying method, device and medium
CN115599494A (en) Virtual machine migration method and device, upgrading method and server
US11290318B2 (en) Disaster recovery of cloud resources
US10613789B1 (en) Analytics engine using consistent replication on distributed sites
CN114385351A (en) Cloud management platform load balancing performance optimization method, device, equipment and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20201127