[go: up one dir, main page]

CN112241341A - A method, device and system for remote disaster recovery - Google Patents

A method, device and system for remote disaster recovery Download PDF

Info

Publication number
CN112241341A
CN112241341A CN201910638566.XA CN201910638566A CN112241341A CN 112241341 A CN112241341 A CN 112241341A CN 201910638566 A CN201910638566 A CN 201910638566A CN 112241341 A CN112241341 A CN 112241341A
Authority
CN
China
Prior art keywords
virtual machine
site
backup
protection group
request
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
CN201910638566.XA
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201910638566.XA priority Critical patent/CN112241341A/en
Priority to PCT/CN2020/102072 priority patent/WO2021008550A1/en
Publication of CN112241341A publication Critical patent/CN112241341A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16Error detection or correction of the data by redundancy in hardware
    • G06F11/20Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023Failover techniques
    • G06F11/2033Failover techniques switching over of hardware resources
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; 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
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16Error detection or correction of the data by redundancy in hardware
    • G06F11/20Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; 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

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Hardware Redundancy (AREA)

Abstract

The embodiment of the invention discloses a method, a device and a system for remote disaster recovery, wherein the method comprises the following steps: the main site regularly checks whether a pre-established protection group exists; when a pre-created protection group exists, sending an inquiry request to a standby site according to a preset main-standby site relation, wherein the inquiry request is used for determining whether a backup virtual machine of a virtual machine needing to be protected in the protection group exists in the standby site; when the backup virtual machine of the virtual machine needing to be protected does not exist in the standby site, sending a request for creating the backup virtual machine to the standby site, so that the standby site can create the backup virtual machine which is the same as the virtual machine needing to be protected and has the same configuration as the virtual machine needing to be protected according to the request for creating the backup virtual machine. The method can ensure that the virtual machines in the main and standby sites are consistent, so that a user can quickly switch to the standby site to use the virtual machines normally when the main site cannot be used normally.

Description

Remote disaster recovery method, device and system
Technical Field
The embodiment of the invention relates to but is not limited to a virtualization platform disaster recovery technology, and more particularly relates to a method, a device and a system for remote disaster recovery.
Background
The remote disaster recovery refers to that servers with similar functions are deployed in two places far away from each other, and the active and standby sites can provide the same service function. Once major accidents such as earthquake, flood, fire and the like occur in the area of the main site or power failure and the like occur, the main site cannot normally provide services for the business, and the standby site can be quickly started in a different place and provides the same services as the main site, so that the continuous service capability can be provided.
In the existing disaster recovery scheme of the virtualization platform, the backup site only plays a role of data backup, and cannot be quickly switched to the backup site for normal virtual machine use when the main site fails.
Disclosure of Invention
In view of this, an embodiment of the present invention provides a method for remote disaster recovery, including:
the main site regularly checks whether a pre-established protection group exists;
when a pre-created protection group exists, sending an inquiry request to a standby site according to a preset main-standby site relation, wherein the inquiry request is used for determining whether a backup virtual machine of a virtual machine needing to be protected in the protection group exists in the standby site;
when the backup virtual machine of the virtual machine needing to be protected does not exist in the standby site, sending a request for creating the backup virtual machine to the standby site, so that the standby site can create the backup virtual machine which is the same as the virtual machine needing to be protected and has the same configuration as the virtual machine needing to be protected according to the request for creating the backup virtual machine;
and the request for creating the backup virtual machine carries the name and the configuration information of the virtual machine to be protected.
The embodiment of the invention also provides a device for remote disaster recovery, which is applied to the main site and comprises the following components:
the system comprises a determining unit, a backup unit and a judging unit, wherein the determining unit is used for sending a query request to a backup site according to a preset main-backup site relation, and the query request is used for determining whether a backup virtual machine of a virtual machine needing to be protected in a pre-established protection group exists in the backup site;
a sending unit, configured to send a request for creating a backup virtual machine to the backup site when there is no backup virtual machine of the virtual machine to be protected in the backup site, so that the backup site creates a backup virtual machine that is the same name as the virtual machine to be protected and configured according to the request for creating the backup virtual machine;
and the request for creating the backup virtual machine carries the name and the configuration information of the virtual machine to be protected.
The embodiment of the invention also provides a remote disaster recovery system, which comprises: a primary site and a backup site; the primary site comprises a first disaster recovery management DRM unit, and the backup site comprises a second disaster recovery management DRM unit;
the first disaster recovery management DRM unit is used for regularly checking whether a pre-established protection group exists; when a pre-created protection group exists, sending an inquiry request to a standby site according to a preset main-standby site relation, wherein the inquiry request is used for determining whether a backup virtual machine of a virtual machine needing to be protected in the protection group exists in the standby site; when the backup virtual machine of the virtual machine needing to be protected does not exist in the backup site, sending a request for creating the backup virtual machine to the backup site;
the second disaster recovery management DRM unit is used for creating a backup virtual machine which is configured in the same name as the virtual machine to be protected according to the request for creating the backup virtual machine;
and the request for creating the backup virtual machine carries the name and the configuration information of the virtual machine to be protected.
The embodiment of the invention also provides a remote disaster recovery system, which comprises:
a plurality of sites;
a first site in the multiple sites is used for adding basic information of a second site and setting a primary-standby site relationship between the first site and the second site; creating a protection group and adding a virtual machine to be protected in the protection group;
the second site is used for increasing the basic information of a third site and setting the relationship between the second site and the main site and the standby site of the third site; creating a protection group and adding a virtual machine to be protected in the protection group;
and repeating the steps until the plurality of stations are mutually main and standby.
The embodiment of the invention also provides a remote disaster recovery device, which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein when the computer program is executed by the processor, the remote disaster recovery device realizes the remote disaster recovery method.
The technical scheme provided by the embodiment of the invention can ensure that the virtual machines in the main and standby sites are consistent, so that a user can quickly switch to the standby site to use the virtual machines normally when the main site cannot be used normally.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.
Fig. 1 is a schematic flow chart of a remote disaster recovery method according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a remote disaster recovery method according to another embodiment of the present invention;
fig. 3 is a schematic flow chart of a remote disaster recovery method according to another embodiment of the present invention;
fig. 4 is a schematic structural diagram of a remote disaster recovery system according to an embodiment of the present invention;
fig. 5 is a schematic flow chart of a remote disaster recovery method according to another embodiment of the present invention;
fig. 6 is a schematic structural diagram of a remote disaster recovery system according to an embodiment of the present invention;
fig. 7 is a schematic flow chart of a remote disaster recovery method according to another embodiment of the present invention;
fig. 8 is a schematic flow chart of a remote disaster recovery apparatus according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a remote disaster recovery system according to another embodiment of the present invention;
fig. 10 is a schematic structural diagram of a remote disaster recovery system according to another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
The steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.
Fig. 1 is a schematic flow chart of a remote disaster recovery method according to an embodiment of the present invention. As shown in fig. 1, the method includes:
step 101, a master site regularly checks whether a pre-established protection group exists;
step 102, when a pre-created protection group exists, sending an inquiry request to a standby site according to a preset relationship between the standby site and the standby site, wherein the inquiry request is used for determining whether a backup virtual machine of a virtual machine needing to be protected in the protection group exists in the standby site;
103, when the backup virtual machine of the virtual machine to be protected does not exist in the backup site, sending a request for creating the backup virtual machine to the backup site, so that the backup site creates a backup virtual machine which is the same name as the virtual machine to be protected and configured according to the request for creating the backup virtual machine;
and the request for creating the backup virtual machine carries the name and the configuration information of the virtual machine to be protected.
Before the primary site checks whether a pre-created protection group exists, the method further comprises the following steps:
the primary site adds basic information of a standby site and sets a primary-standby site relation between the primary site and the standby site;
creating a protection group and adding a virtual machine to be protected in the protection group;
wherein the basic information includes: IP address, authentication URL, authentication user name and authentication password.
Wherein, the method also comprises:
when the backup virtual machine of the virtual machine needing to be protected exists in the backup site, inquiring whether the configuration information of the virtual machine in the protection group is consistent with the configuration information of the backup virtual machine in the backup site;
when the configuration is inconsistent with the configuration change request, sending a configuration change request to the standby site so that the configuration of the backup virtual machine set by the standby site according to the configuration change request is consistent with the configuration of the virtual machines in the protection group;
and the configuration change request carries the virtual machine configuration information in the protected group.
Wherein, when there is a pre-created protection group, the method further comprises:
inquiring whether the virtual machine information in the protection group is consistent with the backup virtual machine information in the backup site;
when the virtual machines in the protection group are inconsistent and the virtual machines in the protection group are deleted, sending a synchronization request to the standby site so that the standby site deletes the backup virtual machine corresponding to the deleted virtual machine according to the synchronization request;
and the synchronization request carries the deleted virtual machine information.
Wherein, when there is a pre-created protection group, the method further comprises:
inquiring whether the virtual machines in the protection group are consistent with the backup virtual machine in the backup site;
when the virtual machines are inconsistent and newly added into the protection group, sending a synchronization request to the standby site so that the standby site can create backup virtual machines with the same name and configuration corresponding to the newly added virtual machines according to the synchronization request;
and the synchronization request carries the name and the configuration information of the newly added virtual machine.
Fig. 2 is a schematic flow chart of a remote disaster recovery method according to another embodiment of the present invention. As shown in fig. 2, the method includes:
step 201, a primary site adds basic information of a standby site and sets a relationship between the primary site and the standby site;
the basic information of the standby site includes an IP Address (Internet Protocol Address), an authentication URL (Uniform Resource Locator), an authentication user name, and an authentication password of the standby site. Through which the DRM of the backup site can be accessed through the primary site.
202, creating a protection group in a master site, and adding virtual machine information needing to be protected in the protection group;
the protection group may be a table stored in the storage of the primary site, and the table records information of the virtual machine that needs protection, i.e., needs disaster recovery from a different location, such as an ID of the virtual machine.
Specifically, the virtual machine may be created first and then added to the protected group.
Step 203, the master site checks whether a pre-established protection group exists at regular time;
when there is a pre-created protected group, step 204 is performed, and when there is no protected group, the flow ends.
Step 204, the primary site sends a query request to the backup site, and determines whether a backup virtual machine of the virtual machines needing to be protected in the protection group exists in the backup site;
the query request may carry information such as names of virtual machines to be protected in the protection group, and the backup site searches whether a backup virtual machine corresponding to the information exists locally after receiving the query request, and when the backup virtual machine exists, it indicates that the backup virtual machine exists in the backup site, and when the backup virtual machine does not exist, it indicates that the backup virtual machine does not exist in the backup site. And the standby site returns a response message of the query request to the main site according to the searching condition, wherein the response message carries the information of the backup virtual machine.
When there is no backup virtual machine, step 205 is executed, and when there is a backup virtual machine, step 207 is executed:
step 205, the primary site sends a request for creating a backup virtual machine to the backup site;
step 206, the backup site creates a backup virtual machine which is configured with the same name as the virtual machine to be protected according to the request for creating the backup virtual machine;
and the request for creating the backup virtual machine carries the name and the configuration information of the virtual machine to be protected.
Step 207, the primary site queries whether the configuration information of the virtual machines in the protected group is consistent with the configuration information of the backup virtual machines in the backup site;
specifically, the primary site may send a configuration information query request to the backup site, where the configuration information query request may carry configuration information of a virtual machine to be protected in the protection group, and the backup site determines whether the configuration information of the virtual machine in the protection group is consistent with the configuration information of the backup virtual machine in the backup site after receiving the configuration information query request. And the standby site returns a response message of the configuration information inquiry request to the main site, wherein the response message carries information of whether the configuration information inquiry request is consistent or not.
When not consistent, step 208 is executed, and when consistent, the flow ends.
Step 208, sending a configuration change request to the standby station;
and the configuration change request carries the virtual machine configuration information in the protected group.
Step 209, the backup site sets the configuration of the backup virtual machine to be consistent with the configuration of the virtual machines in the protected group according to the configuration change request.
Specifically, the backup site may call an interface device backup site virtual machine of the virtualization management platform to achieve the purpose of synchronizing with the primary site virtual machine configuration.
In the technical scheme provided by the embodiment, a master site creates and manages a master site and a slave site, sets a master-slave relationship of the master site and the slave site, and creates a relationship between a protection group and a protected virtual machine; the backup site is responsible for monitoring messages such as query requests, backup virtual machine creating requests and configuration change requests sent by the main site, creating backup virtual machines on the backup site and synchronizing configuration information of the virtual machines. Therefore, when the primary site cannot be used normally, a user can quickly switch to the standby site to use the virtual machine normally, and data and configuration in the standby site virtualization platform are ensured to be consistent with those of the primary site.
Fig. 3 is a schematic flow chart of a remote disaster recovery method according to another embodiment of the present invention. As shown in fig. 3, the method includes:
step 301, the primary site checks whether a pre-established protection group exists at regular time;
before that, the primary site may add the basic information of the standby site and set the relationship between the primary and standby sites; and creating a protection group, and adding virtual machine information needing protection in the protection group.
When there is a pre-created protected group, step 302 is performed, and when there is no protected group, the flow ends.
Step 302, inquiring whether the virtual machine information in the protection group is consistent with the backup virtual machine information in the backup site;
the virtual machine information refers to virtual machine identification information, and is used for identifying whether the virtual machines in the protection group are consistent with the backup virtual machine. For example, a virtual machine in the primary site's protected group is deleted, or a new virtual machine is added to the protected group
When the virtual machines in the protection group are inconsistent and deleted, step 303 is executed, when the virtual machines in the protection group are inconsistent and newly added, step 305 is executed, and when the virtual machines in the protection group are consistent, the flow is ended.
Step 303, sending a first synchronization request to the standby station;
and the first synchronization request carries the name and the configuration information of the deleted virtual machine.
Step 304, the backup site deletes the backup virtual machine corresponding to the deleted virtual machine according to the first synchronization request;
specifically, after receiving the first synchronization request, the standby site may call a standby site virtualization platform interface to delete the information of the standby site virtual machine.
Step 305, sending a second synchronization request to the standby station;
and the second synchronization request carries the name and the configuration information of the newly added virtual machine.
Step 306, the backup site creates a backup virtual machine with the same name and configuration corresponding to the newly added virtual machine according to the second synchronization request.
Fig. 4 is a schematic structural diagram of a remote disaster recovery system according to an embodiment of the present invention, and as shown in fig. 4, the system includes:
a primary site and a backup site; the primary site comprises a first disaster recovery management DRM unit, and the backup site comprises a second disaster recovery management DRM unit;
the first disaster recovery management DRM unit is used for regularly checking whether a pre-established protection group exists; when a pre-created protection group exists, sending an inquiry request to a standby site according to a preset main-standby site relation, wherein the inquiry request is used for determining whether a backup virtual machine of a virtual machine needing to be protected in the protection group exists in the standby site; when the backup virtual machine of the virtual machine needing to be protected does not exist in the backup site, sending a request for creating the backup virtual machine to the backup site;
and the second disaster recovery management DRM unit is used for creating a backup virtual machine which is configured in the same name as the virtual machine to be protected according to the request for creating the backup virtual machine.
And the request for creating the backup virtual machine carries the name and the configuration information of the virtual machine to be protected.
The first DRM unit is further configured to add basic information of a backup site, and set a relationship between the primary site and the backup site; creating a protection group and adding a virtual machine needing protection in the protection group.
Wherein the basic information includes: IP address, authentication URL, authentication user name and authentication password.
The first DRM unit is further configured to, when a backup virtual machine of the virtual machine to be protected exists in the backup site, query whether configuration information of the virtual machine in the protection group is consistent with configuration information of the backup virtual machine in the backup site;
when the configuration information is inconsistent with the configuration information, sending a configuration change request to the standby site;
the second disaster recovery management DRM unit is further configured to set that the configuration of the backup virtual machine is consistent with the configuration of the virtual machines in the protection group according to the configuration change request;
wherein the configuration change request carries virtual machine configuration information in the protected group
The first disaster recovery management DRM unit is further configured to, when a pre-created protection group exists, query whether virtual machine information in the protection group is consistent with backup virtual machine information in the backup site;
when the virtual machines in the protection group are inconsistent and deleted, sending a synchronization request to the standby site;
the second disaster recovery management DRM unit is further configured to delete the backup virtual machine corresponding to the deleted virtual machine according to the synchronization request;
and the synchronization request carries the deleted virtual machine information.
The first disaster recovery management DRM unit is further configured to, when a pre-created protection group exists, query whether a virtual machine in the protection group is consistent with a backup virtual machine in the backup site;
when the virtual machines are inconsistent and newly added in the protection group, sending a synchronization request to the standby site;
the second disaster recovery management DRM unit is further configured to create a backup virtual machine corresponding to the newly added virtual machine and having the same name and configuration according to the synchronization request;
and the synchronization request carries the name and the configuration information of the newly added virtual machine.
Fig. 5 is a schematic flow chart of a remote disaster recovery method according to another embodiment of the present invention.
The present embodiment is applied to the system shown in fig. 6. As shown in fig. 6, site A, B backs up each other with site a as the primary site and site B as the backup site. The site a is provided with DRM (DRM Recovery management), and the site B is also provided with DRM. The site a also includes a virtualization platform for managing the virtual machines 1, 2, and 3. The site B also includes a virtualization platform for managing virtual machines 1x, 2x, and 3x, where the virtual machines 1x, 2x, and 3x are backup virtual machines of the virtual machines 1, 2, and 3, respectively. Site A, B also includes a storage unit. In addition, the site A, B also deploys a set of OpenStack for resource management.
As shown in fig. 5, the method includes:
step 501, adding basic information of a site B in a site A, and setting a main-standby relationship between the site A and the site B;
the site B information includes an IP Address (Internet Protocol Address) of the site B, an authentication URL (Uniform Resource Locator), an authentication user name and an authentication password, and the information can access the DRM of the site B through the site a.
The storage unit may store the basic information of the station B.
Step 502, adding a protection group in a site A, and adding a virtual machine to be protected;
in this embodiment, virtual machines 1, 2, and 3 are added to a protected group. And only part of the virtual machines in the site A can be added to the protected group according to factors such as importance and the like, and backup is not set for the virtual machines added to the protected group.
The protection group, the virtual machine configuration information, the virtual machine information, and the like in the site a may be stored in the storage unit.
Step 503, the DRM of site a checks if there is a pre-created protection group at regular time;
when there is a pre-created protected group, step 504 is performed, and when not, the flow ends.
Step 504, the DRM of site a sends a query request to the DRM module of site B to determine whether a backup virtual machine exists in site B;
the query request may be an HTTP message, and the site B returns an HTTP response after querying the local area, and carries a message indicating whether the backup virtual machine exists.
When not present, executing step 505, and when present, executing step 507:
step 505, the DRM of site a sends a request to create a backup virtual machine to the DRM module of site B;
wherein the create backup virtual machine request may be an HTTP message.
And the request for creating the backup virtual machine carries the name and the configuration information of the virtual machine to be protected.
Step 506, the DRM of the site B calls an Open Stack interface to create a virtual machine according to the request for creating the backup virtual machine;
specifically, the DRM module of site B invokes an Open Stack interface to create a backup virtual machine configured identically to the virtual machine that needs to be protected in the protection group. For example, in this embodiment, corresponding backup virtual machines 1x, 2x, and 3x are created for virtual machines 1, 2, and 3 in the protection group.
The virtual machine configuration information, the virtual machine information, and the like in the site B may be stored in the storage unit.
Step 507, the DRM of site a queries whether the configuration information of the virtual machines in the protected group is consistent with the configuration information of the backup virtual machine in the backup site;
for example, the configuration information of virtual machine 1 may be modified in site a, where the configuration information of virtual machine 1 in site a is inconsistent with the configuration information of backup virtual machine 1 x.
Specifically, the DRM of the site a sends a configuration information query request to the DRM of the site B, where the configuration information query request may carry configuration information of virtual machines to be protected in the protection group, for example, configuration information of virtual machines 1, 2, and 3, and after receiving the configuration information query request, the DRM of the site B determines whether the configuration information of the virtual machines in the protection group is consistent with the configuration information of the backup virtual machine in the backup site. The DRM of the site B returns a response message of the configuration information inquiry request to the DRM of the site A, and the response message carries information of whether the configuration information inquiry request is consistent or not. For example, it may be queried whether the configuration information of the virtual machines 1x, 2x, and 3x in the storage unit is consistent with the configuration information of the virtual machines 1, 2, and 3, respectively.
If not, step 508 is executed, and if yes, the flow ends.
Step 508, the DRM of site a sends a configuration change request to the DRM of site B;
the configuration change request may carry virtual machine configuration information that needs to be changed, for example, modified configuration information of the virtual machine 1.
In step 509, the DRM of site B invokes the OpenStack interface of site B to modify the configuration information of the virtual machine, and the configuration information of the virtual machine in site a is kept consistent.
For example, in this embodiment, the site B modifies the configuration information of the virtual machine 1x to be consistent with the configuration information of the virtual machine 1.
Fig. 7 is a flowchart illustrating a method for disaster recovery in different areas according to another embodiment of the present invention.
The present embodiment is equally applicable to the system shown in fig. 6.
As shown in fig. 7, the method includes:
step 701, the DRM of the primary site a checks regularly whether a pre-created protection group exists;
before that, the primary site a may add the basic information of the secondary site B, and set the relationship between the primary and secondary sites; creating a protection group, and adding virtual machine information needing protection in the protection group, such as the names, identifications and other information of the virtual machines 1, 2 and 3.
When there is a pre-created protected group, step 702 is performed, and when not, the flow ends.
Step 702, inquiring whether the virtual machine information in the protection group is consistent with the backup virtual machine information in the site B;
the virtual machine information refers to virtual machine identification information, and is used for identifying whether the virtual machines in the protection group are consistent with the backup virtual machine. For example, virtual machine 1 in the primary site A protected group is deleted, or a new virtual machine 4 is added to the protected group.
And when the virtual machines in the protection group are inconsistent and the virtual machines in the protection group are deleted, executing step 703, when the virtual machines in the protection group are inconsistent and the virtual machines in the protection group are newly added, executing step 705, and when the virtual machines in the protection group are consistent, ending the flow.
Step 703, sending a first synchronization request to the DRM of site B;
and the first synchronization request carries the name and the configuration information of the deleted virtual machine. For example, the name and configuration information of the virtual machine 1 are carried, and the first synchronization request is used to request to delete the backup virtual machine 1x corresponding to the virtual machine 1.
Step 704, the DRM of site B deletes the backup virtual machine corresponding to the deleted virtual machine according to the first synchronization request;
specifically, after receiving the synchronization request, the DRM of the site B may call a standby site virtualization platform interface to delete the backup virtual machine information. Such as deleting backup virtual machine 1 x.
Step 705, sending a second synchronization request to the DRM of site B;
and the second synchronization request carries the name and the configuration information of the newly added virtual machine. For example, the name and configuration information of the virtual machine 4 are carried, and the second synchronization request is used to request to create a backup virtual machine 4x corresponding to the virtual machine 4.
Step 706, the DRM of site B creates a backup virtual machine with the same name and configuration corresponding to the newly added virtual machine according to the second synchronization request.
Specifically, after receiving the synchronization request, the DRM of the site B may invoke an OpenStack interface to create a virtual machine. Such as creating backup virtual machine 4 x.
Fig. 8 is a schematic flow chart of a remote disaster recovery apparatus according to an embodiment of the present invention. The apparatus is applied to a master site, and as shown in fig. 8, the apparatus includes:
the system comprises a determining unit, a backup unit and a judging unit, wherein the determining unit is used for sending a query request to a backup site according to a preset main-backup site relation, and the query request is used for determining whether a backup virtual machine of a virtual machine needing to be protected in a pre-established protection group exists in the backup site;
a sending unit, configured to send a request for creating a backup virtual machine to the backup site when there is no backup virtual machine of the virtual machine to be protected in the backup site, so that the backup site creates a backup virtual machine that is the same name as the virtual machine to be protected and configured according to the request for creating the backup virtual machine;
and the request for creating the backup virtual machine carries the name and the configuration information of the virtual machine to be protected.
Wherein, the device still includes:
a setting unit for checking whether there is a pre-created protection group before the master site periodically,
adding basic information of a standby site, and setting a relationship between the main site and the standby site of the standby site;
creating a protection group and adding a virtual machine to be protected in the protection group;
wherein the basic information includes: IP address, authentication URL, authentication user name and authentication password.
Wherein, the device still includes: the query unit is configured to query whether configuration information of the virtual machines in the protection group is consistent with configuration information of the backup virtual machines in the backup site when the backup virtual machines of the virtual machines to be protected are present in the backup site;
when the configuration is inconsistent with the configuration change request, sending a configuration change request to the standby site so that the configuration of the backup virtual machine set by the standby site according to the configuration change request is consistent with the configuration of the virtual machines in the protection group;
and the configuration change request carries the virtual machine configuration information in the protected group.
Wherein, the device still includes: the query unit is used for querying whether the virtual machine information in the protection group is consistent with the backup virtual machine information in the backup site or not when the pre-established protection group exists;
when the virtual machines in the protection group are inconsistent and the virtual machines in the protection group are deleted, sending a synchronization request to the standby site so that the standby site deletes the backup virtual machine corresponding to the deleted virtual machine according to the synchronization request;
and the synchronization request carries the deleted virtual machine information.
Wherein, the device still includes: the query unit is used for querying whether the virtual machines in the protection group are consistent with the backup virtual machines in the backup site or not when the pre-established protection group exists;
when the virtual machines are inconsistent and newly added into the protection group, sending a synchronization request to the standby site so that the standby site can create backup virtual machines with the same name and configuration corresponding to the newly added virtual machines according to the synchronization request;
and the synchronization request carries the name and the configuration information of the newly added virtual machine.
Fig. 9 is a schematic structural diagram of a remote disaster recovery system according to another embodiment of the present invention, as shown in fig. 9, the system includes:
n sites; n is a natural number of 3 or more.
A first site in the multiple sites is used for adding basic information of a second site and setting a primary-standby site relationship between the first site and the second site; creating a protection group and adding a virtual machine to be protected in the protection group;
the second site is used for increasing the basic information of a third site and setting the relationship between the second site and the main site and the standby site of the third site; creating a protection group and adding a virtual machine to be protected in the protection group;
and so on until the n sites are mutually active and standby.
Fig. 10 is a schematic structural diagram of a remote disaster recovery system according to another embodiment of the present invention, as shown in fig. 10, the system includes:
site a, site B, and site C.
And adding basic information of a site B in the site A, and setting the main-standby relationship between the site A and the site B. And adding a protection group in the site A, wherein the site corresponding relation in the protection group is the site A and the site B, and adding the virtual machine to be protected in the site A into the protection group. And a backup virtual machine of the virtual machine needing to be protected in the site A protection group is created in the site B, and the consistency of the virtual machine and the configuration information thereof is kept.
And adding the basic information of the site C in the site B, and setting the main-standby relationship between the site B and the site C. And adding a protection group in the site B, wherein the site corresponding relation in the protection group is the site B and the site C, and adding the virtual machine to be protected in the site B into the protection group. And a backup virtual machine of the virtual machine needing to be protected in the site B protection group is created in the site C, and the consistency of the virtual machine and the configuration information thereof is kept.
And adding the basic information of the site A in the site C, and setting the main-standby relationship between the site C and the site A. And adding a protection group in the site C, wherein the site corresponding relation in the protection group is the site C and the site A, and adding the virtual machine to be protected in the site C into the protection group. And a backup virtual machine of the virtual machine to be protected in the site C protection group is created in the site A, and the consistency of the virtual machine and the configuration information thereof is kept.
According to the technical scheme provided by the embodiment of the invention, a plurality of sites are mutually backed up, and when one site cannot be normally used, a user can quickly switch to another site to normally use the virtual machine.
The embodiment of the present invention further provides a remote disaster recovery device, which includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the method for implementing any one of the above remote disaster recovery methods is implemented.
The embodiment of the invention also provides a computer-readable storage medium, wherein an information processing program is stored on the computer-readable storage medium, and when the information processing program is executed by a processor, the steps of any one of the above-mentioned remote disaster recovery methods are realized.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.

Claims (10)

1.一种异地容灾的方法,包括:1. A method for remote disaster recovery, comprising: 主站点定时检查是否存在预先创建的保护组;The main site regularly checks whether there is a pre-created protection group; 当存在预先创建的保护组时,根据预先设置的主备站点关系向备站点发送查询请求,所述查询请求用于确定备站点中是否有所述保护组中需要保护的虚拟机的备份虚拟机;When there is a pre-created protection group, send a query request to the standby site according to the preset relationship between the primary and secondary sites, where the query request is used to determine whether there is a backup virtual machine of the virtual machine in the protection group that needs to be protected in the standby site ; 当所述备站点中没有所述需要保护的虚拟机的备份虚拟机时,向所述备站点发送创建备份虚拟机请求,以便所述备站点根据所述创建备份虚拟机请求创建与所述需要保护的虚拟机同名同配置的备份虚拟机;When there is no backup virtual machine of the virtual machine that needs to be protected in the standby site, send a request for creating a backup virtual machine to the standby site, so that the standby site can create a backup virtual machine according to the request for creating a backup virtual machine that matches the needs The protected virtual machine has the same name and the same configuration as the backup virtual machine; 其中,所述创建备份虚拟机请求携带所述需要保护的虚拟机的名称和配置信息。The request for creating a backup virtual machine carries the name and configuration information of the virtual machine to be protected. 2.根据权利要求1所述的方法,其特征在于,在主站点定时检查是否存在预先创建的保护组之前,该方法还包括:2. The method according to claim 1, characterized in that, before the primary site regularly checks whether there is a pre-created protection group, the method further comprises: 所述主站点增加备站点的基本信息,并设置所述主站点和所述备站点的主备站点关系;The primary site adds the basic information of the secondary site, and sets the primary and secondary site relationship between the primary site and the secondary site; 创建保护组并在所述保护组中添加需要保护的虚拟机;Create a protection group and add virtual machines to be protected in the protection group; 其中,所述基本信息包括:IP地址,鉴权URL,鉴权用户名和鉴权密码。Wherein, the basic information includes: IP address, authentication URL, authentication user name and authentication password. 3.根据权利要求1所述的方法,其特征在于,该方法还包括:3. The method according to claim 1, wherein the method further comprises: 当所述备站点中有所述需要保护的虚拟机的备份虚拟机时,查询所述保护组中的虚拟机的配置信息和所述备站点中的备份虚拟机的配置信息是否一致;When there is a backup virtual machine of the virtual machine to be protected in the standby site, query whether the configuration information of the virtual machine in the protection group is consistent with the configuration information of the backup virtual machine in the standby site; 当不一致时,向所述备站点发送配置变更请求,以便所述备站点根据所述配置变更请求设置备份虚拟机的配置与所述保护组中的虚拟机配置保持一致;When inconsistent, sending a configuration change request to the standby site, so that the standby site sets the configuration of the backup virtual machine according to the configuration change request to be consistent with the virtual machine configuration in the protection group; 其中,所述配置变更请求携带所述保护组中的虚拟机配置信息。The configuration change request carries the virtual machine configuration information in the protection group. 4.根据权利要求1所述的方法,其特征在于,当存在预先创建的保护组时,该方法还包括:4. The method according to claim 1, wherein when there is a pre-created protection group, the method further comprises: 查询所述保护组中的虚拟机信息和所述备站点中的备份虚拟机信息是否一致;query whether the virtual machine information in the protection group is consistent with the backup virtual machine information in the standby site; 当不一致且所述保护组中的虚拟机被删除时,向所述备站点发送同步请求,以便所述备站点根据所述同步请求删除所述被删除的虚拟机对应的备份虚拟机;When inconsistent and the virtual machine in the protection group is deleted, send a synchronization request to the standby site, so that the standby site deletes the backup virtual machine corresponding to the deleted virtual machine according to the synchronization request; 其中,所述同步请求携带所述被删除的虚拟机信息。Wherein, the synchronization request carries the deleted virtual machine information. 5.根据权利要求1所述的方法,其特征在于,当存在预先创建的保护组时,该方法还包括:5. The method according to claim 1, wherein when there is a pre-created protection group, the method further comprises: 查询所述保护组中的虚拟机和所述备站点中的备份虚拟机是否一致;query whether the virtual machine in the protection group is consistent with the backup virtual machine in the standby site; 当不一致且所述保护组中有新添加的虚拟机时,向所述备站点发送同步请求,以便所述备站点根据所述同步请求创建所述新添加的虚拟机对应的同名同配置的备份虚拟机;When it is inconsistent and there is a newly added virtual machine in the protection group, a synchronization request is sent to the standby site, so that the standby site creates a backup with the same name and the same configuration corresponding to the newly added virtual machine according to the synchronization request virtual machine; 其中,所述同步请求携带所述新添加的虚拟机的名称和配置信息。The synchronization request carries the name and configuration information of the newly added virtual machine. 6.一种异地容灾的装置,其特征在于,应用于主站点,包括:6. A device for remote disaster recovery, characterized in that, applied to the main site, comprising: 确定单元,用于根据预先设置的主备站点关系向备站点发送查询请求,所述查询请求用于确定备站点中是否有预先创建的保护组中需要保护的虚拟机的备份虚拟机;a determining unit, configured to send a query request to the standby site according to the preset relationship between the primary and secondary sites, where the query request is used to determine whether there is a backup virtual machine of the virtual machine that needs to be protected in the pre-created protection group in the standby site; 发送单元,用于当所述备站点中没有所述需要保护的虚拟机的备份虚拟机时,向所述备站点发送创建备份虚拟机请求,以便所述备站点根据所述创建备份虚拟机请求创建与所述需要保护的虚拟机同名同配置的备份虚拟机;a sending unit, configured to send a request for creating a backup virtual machine to the backup site when there is no backup virtual machine of the virtual machine to be protected in the backup site, so that the backup site can create a backup virtual machine according to the request for creating a backup virtual machine Create a backup virtual machine with the same name and configuration as the virtual machine to be protected; 其中,所述创建备份虚拟机请求携带所述需要保护的虚拟机的名称和配置信息。The request for creating a backup virtual machine carries the name and configuration information of the virtual machine to be protected. 7.一种异地容灾的系统,其特征在于,包括:主站点和备站点;所述主站点包括第一容灾管理DRM单元,所述备站点包括第二容灾管理DRM单元;7. A remote disaster recovery system, comprising: a primary site and a backup site; the primary site includes a first disaster recovery management DRM unit, and the backup site includes a second disaster recovery management DRM unit; 所述第一容灾管理DRM单元,用于定时检查是否存在预先创建的保护组;当存在预先创建的保护组时,根据预先设置的主备站点关系向备站点发送查询请求,所述查询请求用于确定备站点中是否有所述保护组中需要保护的虚拟机的备份虚拟机;当所述备站点中没有所述需要保护的虚拟机的备份虚拟机时,向所述备站点发送创建备份虚拟机请求;The first disaster recovery management DRM unit is used to regularly check whether there is a pre-created protection group; when there is a pre-created protection group, send a query request to the standby site according to the preset relationship between the primary and secondary sites, and the query request It is used to determine whether there is a backup virtual machine of the virtual machine that needs to be protected in the protection group in the standby site; when there is no backup virtual machine of the virtual machine that needs to be protected in the standby site, send the backup virtual machine to the standby site. Backup virtual machine request; 所述第二容灾管理DRM单元,用于根据所述创建备份虚拟机请求创建与所述需要保护的虚拟机同名同配置的备份虚拟机;The second disaster tolerance management DRM unit is configured to create, according to the request for creating a backup virtual machine, a backup virtual machine with the same name and configuration as the virtual machine to be protected; 其中,所述创建备份虚拟机请求携带所述需要保护的虚拟机的名称和配置信息。The request for creating a backup virtual machine carries the name and configuration information of the virtual machine to be protected. 8.根据权利要求7所述的系统,其特征在于,8. The system of claim 7, wherein: 所述第一容灾管理DRM单元,还用于增加备站点的基本信息,并设置所述主站点和所述备站点的主备站点关系;创建保护组并在所述保护组中添加需要保护的虚拟机。The first disaster recovery management DRM unit is also used to increase the basic information of the standby site, and set the relationship between the primary site and the standby site; create a protection group and add the protection group to the protection group virtual machine. 9.一种异地容灾的系统,其特征在于,包括:9. A remote disaster recovery system, comprising: 多个站点;multiple sites; 其中,所述多个站点中的第一站点,用于增加第二站点的基本信息,并设置所述第一站点和所述第二站点的主备站点关系;创建保护组并在所述保护组中添加需要保护的虚拟机;Wherein, the first site among the multiple sites is used to add basic information of the second site, and set the relationship between the primary and secondary sites of the first site and the second site; Add virtual machines to be protected to the group; 第二站点,用于增加第三站点的基本信息,并设置所述第二站点和所述第三站点的主备站点关系;创建保护组并在所述保护组中添加需要保护的虚拟机;The second site is used to add basic information of the third site, and set the relationship between the primary and secondary sites of the second site and the third site; create a protection group and add virtual machines to be protected in the protection group; 以此类推,直至所述多个站点互为主备。And so on, until the multiple sites are the master and backup of each other. 10.一种异地容灾的装置,其特征在于,包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序,所述计算机程序被所述处理器执行时实现权利要求1至5任一项所述异地容灾的方法。10. A device for remote disaster recovery, characterized in that it comprises a memory, a processor and a computer program stored on the memory and running on the processor, when the computer program is executed by the processor A method for realizing the remote disaster recovery described in any one of claims 1 to 5.
CN201910638566.XA 2019-07-16 2019-07-16 A method, device and system for remote disaster recovery Pending CN112241341A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910638566.XA CN112241341A (en) 2019-07-16 2019-07-16 A method, device and system for remote disaster recovery
PCT/CN2020/102072 WO2021008550A1 (en) 2019-07-16 2020-07-15 Method, device, and system for remote disaster tolerance

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910638566.XA CN112241341A (en) 2019-07-16 2019-07-16 A method, device and system for remote disaster recovery

Publications (1)

Publication Number Publication Date
CN112241341A true CN112241341A (en) 2021-01-19

Family

ID=74166923

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910638566.XA Pending CN112241341A (en) 2019-07-16 2019-07-16 A method, device and system for remote disaster recovery

Country Status (2)

Country Link
CN (1) CN112241341A (en)
WO (1) WO2021008550A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113687982A (en) * 2021-08-20 2021-11-23 济南浪潮数据技术有限公司 Method and device for building remote disaster recovery cluster and related equipment
CN114706661A (en) * 2022-05-31 2022-07-05 武汉四通信息服务有限公司 Disaster recovery backup method and system for virtual machine, computer equipment and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080209142A1 (en) * 2007-02-23 2008-08-28 Obernuefemann Paul R Data Recovery Systems and Methods
CN104965771A (en) * 2015-07-29 2015-10-07 浪潮(北京)电子信息产业有限公司 Method and system for verifying remote disaster recovery data consistency
CN105068856A (en) * 2015-07-16 2015-11-18 武汉噢易云计算有限公司 Mirror image snapshooting based on virtual machine backup system and backup method
CN107566139A (en) * 2016-06-30 2018-01-09 中兴通讯股份有限公司 Virtual machine disaster recovery method, apparatus and system
CN108304281A (en) * 2018-02-28 2018-07-20 南京铱迅信息技术股份有限公司 A kind of method that virtual machine is backed up in realtime

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8423821B1 (en) * 2006-12-21 2013-04-16 Maxsp Corporation Virtual recovery server
US20100228819A1 (en) * 2009-03-05 2010-09-09 Yottaa Inc System and method for performance acceleration, data protection, disaster recovery and on-demand scaling of computer applications
CN105589735B (en) * 2015-12-16 2020-06-09 深信服科技股份有限公司 Remote disaster recovery method, device and system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080209142A1 (en) * 2007-02-23 2008-08-28 Obernuefemann Paul R Data Recovery Systems and Methods
CN105068856A (en) * 2015-07-16 2015-11-18 武汉噢易云计算有限公司 Mirror image snapshooting based on virtual machine backup system and backup method
CN104965771A (en) * 2015-07-29 2015-10-07 浪潮(北京)电子信息产业有限公司 Method and system for verifying remote disaster recovery data consistency
CN107566139A (en) * 2016-06-30 2018-01-09 中兴通讯股份有限公司 Virtual machine disaster recovery method, apparatus and system
CN108304281A (en) * 2018-02-28 2018-07-20 南京铱迅信息技术股份有限公司 A kind of method that virtual machine is backed up in realtime

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113687982A (en) * 2021-08-20 2021-11-23 济南浪潮数据技术有限公司 Method and device for building remote disaster recovery cluster and related equipment
CN113687982B (en) * 2021-08-20 2024-02-09 济南浪潮数据技术有限公司 Method and device for constructing off-site disaster recovery cluster and related equipment
CN114706661A (en) * 2022-05-31 2022-07-05 武汉四通信息服务有限公司 Disaster recovery backup method and system for virtual machine, computer equipment and storage medium

Also Published As

Publication number Publication date
WO2021008550A1 (en) 2021-01-21

Similar Documents

Publication Publication Date Title
CN107181686B (en) Routing table synchronization method, device and system
CN104636437B (en) A kind of processing method and processing device of event notification method, monitor
CN108667635B (en) Disaster recovery processing method, equipment and system
CN105208124A (en) Method and device for managing locks and method and device for determining lock management servers
CN108352995B (en) A kind of SMB service fault processing method and storage device
US8775859B2 (en) Method, apparatus and system for data disaster tolerance
KR20120072909A (en) Distribution storage system with content-based deduplication function and object distributive storing method thereof, and computer-readable recording medium
CN113986450B (en) Virtual machine backup method and device
CN110830283A (en) Fault detection method, device, equipment and system
CN105187517A (en) Metadata clustering method and metadata cluster
CN113038394B (en) Session binding relationship processing method, apparatus, electronic device and readable medium
CN111382132A (en) Medical image data cloud storage system
CN112241341A (en) A method, device and system for remote disaster recovery
CN112367182B (en) Configuration method and device of disaster recovery main and standby equipment
CN115248746A (en) Data backup method, system and related equipment
CN111708835B (en) Blockchain data storage method and device
CN116781713B (en) System for sharing and exchanging government affair data based on P2P and data acquisition method
WO2016000303A1 (en) Resource allocation method and system, and computer storage medium
CN113821333A (en) Android application migration method and device
CN103188632B (en) short message backup method and message backup server
CN114490633B (en) Method and device for dynamically accessing multi-type databases deployed across network areas
CN108881407A (en) A kind of information processing method and device
WO2019178839A1 (en) Method and device for creating consistency snapshot for distributed application and distributed system
WO2016078360A1 (en) Method and apparatus for optimizing reliability of user equipment tracing
CN114553704A (en) Method and system for supporting multiple devices to access server simultaneously to realize capacity expansion and contraction

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