Disaster recovery method, device and system

Abstract

The embodiment of the present application discloses a disaster recovery method, device and system for realizing a data backup mode under multiple data centers in a virtualized cloud platform, thereby improving the security and reliability of cloud platform data. The method comprises: when the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site; when an operating failure of the production data center is detected, switching the first production business of the production site to the disaster recovery site. During the disaster recovery process, this technical solution adopts a data synchronization solution under multiple data centers, that is, synchronizing the production data center to the disaster recovery data center, thereby improving the security and reliability of the data and meeting the security and reliability requirements of the cloud platform data.

Description

Technical Field

[0001] The present invention relates to the field of computer disaster recovery, and in particular to a disaster recovery method, device and system. Background Art

[0002] The traditional virtual machine backup method used by virtualized cloud platforms is to perform full and incremental backups of virtual machines in one data center. Obviously, this backup mode is less secure because it is performed in one data center and can no longer meet the security and reliability requirements of cloud platform data. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a disaster recovery method, device and system for realizing a data backup mode under multiple data centers in a virtualized cloud platform, thereby improving the security and reliability of cloud platform data.

[0004] To solve the above technical problems, the embodiments of the present application are implemented as follows:

[0005] On the one hand, an embodiment of the present application provides a disaster recovery method, which is applied to a disaster recovery system, wherein the disaster recovery system includes a production data center and a disaster recovery data center, wherein the production data center has a production site, and the disaster recovery data center has a disaster recovery site; the method includes:

[0006] When the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site;

[0007] When an operation failure of the production data center is detected, the first production business of the production site is switched to the disaster recovery site.

[0008] On the other hand, an embodiment of the present application provides a disaster recovery device, which is applied to a disaster recovery system, wherein the disaster recovery system includes a production data center and a disaster recovery data center, wherein the production data center has a production site, and the disaster recovery data center has a disaster recovery site; the device includes:

[0009] A first synchronization module, configured to synchronize first configuration information of a first virtual machine on the production site to a virtual machine to be synchronized on the disaster recovery site when the production data center is operating normally;

[0010] The first switching module is used to switch the first production business of the production site to the disaster recovery site when a failure in the production data center is detected.

[0011] On the other hand, an embodiment of the present application provides a disaster recovery system, including a production data center and a disaster recovery data center; the production data center has a production site, and the disaster recovery data center has a disaster recovery site; the production data center and the disaster recovery data center each include:

[0012] A disaster recovery module DRM, configured to synchronize the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site when the production data center is operating normally;

[0013] A resource operation system iROS, configured to switch the first production business of the production site to the disaster recovery site when a failure in the production data center is detected;

[0014] A storage device is used to store first configuration information of the first virtual machine.

[0015] On the other hand, an embodiment of the present application provides a disaster recovery device, which is applied to a disaster recovery system, wherein the disaster recovery system includes a production data center and a disaster recovery data center, wherein the production data center has a production site, and the disaster recovery data center has a disaster recovery site; the device includes:

[0016] Processor; and

[0017] a memory arranged to store computer executable instructions which, when executed, cause the processor to:

[0018] When the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site;

[0019] When an operation failure of the production data center is detected, the first production business of the production site is switched to the disaster recovery site.

[0020] In another aspect, an embodiment of the present application provides a storage medium for storing computer executable instructions, wherein the executable instructions implement the following process when executed:

[0021] When the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site;

[0022] When an operation failure of the production data center is detected, the first production business of the production site is switched to the disaster recovery site.

[0023] By adopting the technical solution of the embodiment of the present invention, the first configuration information of the first virtual machine on the production site can be synchronized to the virtual machine to be synchronized on the disaster recovery site when the production data center is running normally, and then when a production data center operation failure is detected, the first production business on the production site is switched to the disaster recovery site. It can be seen that in the disaster recovery process, the technical solution adopts a data synchronization solution under multiple data centers, that is, synchronizing the production data center to the disaster recovery data center, thereby improving the security and reliability of the data and meeting the security and reliability requirements of the cloud platform data. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0025] Figure 1 is a schematic flow chart of a disaster recovery method according to an embodiment of the present invention;

[0026] Figure 2 is a schematic block diagram of a disaster recovery device according to an embodiment of the present invention;

[0027] Figure 3 is a schematic block diagram of a disaster recovery system according to an embodiment of the present invention;

[0028] Figure 4 is a schematic block diagram of a disaster recovery device according to an embodiment of the present invention;

[0029] Figure 5 The figure is a schematic structural diagram of a disaster recovery system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0030] The embodiments of the present application provide a disaster recovery method, device and system for realizing a data backup mode under multiple data centers in a virtualized cloud platform, thereby improving the security and reliability of cloud platform data.

[0031] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0032] Figure 1 The present invention is a schematic flow chart of a disaster recovery method according to an embodiment of the present invention. The method is applied to a disaster recovery system. The disaster recovery system includes a production data center and a disaster recovery data center. The production data center has a production site, and the disaster recovery data center has a disaster recovery site. Figure 1 As shown in the figure, the disaster recovery methods include:

[0033] S102: When the production data center is operating normally, synchronize first configuration information of a first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site.

[0034] S104, when a production data center operation failure is detected, the first production service of the production site is switched to the disaster recovery site.

[0035] Figure 2 The disaster recovery system to which the disaster recovery method is applicable is shown, such as Figure 2 As shown in Figure 1, the disaster recovery system includes

[0036] By adopting the technical solution of the embodiment of the present invention, it is possible to synchronize the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site when the production data center is operating normally, and then switch the first production business on the production site to the disaster recovery site when an operating failure of the production data center is detected. It can be seen that during the disaster recovery process, this technical solution adopts a data synchronization solution under multiple data centers, that is, synchronizes the production data center to the disaster recovery data center, thereby improving the security and reliability of the data and meeting the security and reliability requirements of the cloud platform data. In particular, for certain industries such as banks, insurance and other related financial industries that have high requirements for data security and reliability, this technical solution can largely meet the requirements of these industries for data security and reliability because it improves the security and reliability of cloud platform data.

[0037] In one embodiment, after the production business of the production site is switched to the disaster recovery site, when it is monitored that the production data center has resumed operation, the second configuration information of the disaster recovery virtual machine on the disaster recovery site is reversely synchronized to the virtual machine to be reversely synchronized on the production site, and then the second production business of the disaster recovery site is switched to the production site.

[0038] In the above embodiment, before executing S102, it is necessary to first perform disaster recovery configuration in the disaster recovery system, and the specific configuration content includes:

[0039] (1) First, deploy a set of iROS (Resource Operating System) at the production site and the disaster recovery site respectively. The two sets of iROS are in a primary and disaster recovery relationship. The iROS at the production site is the primary one, and the iROS at the disaster recovery site is the disaster recovery one. Secondly, configure the databases of the production iROS (i.e. the iROS at the production site) and the disaster recovery iROS (i.e. the iROS at the disaster recovery site) to achieve real-time replication of the data in the production iROS database to the disaster recovery IROS database.

[0040] (2) A LUN (Logical Unit Number) device of the same size is allocated on the storage devices of the production site and the disaster recovery site, and a synchronous or asynchronous replication relationship is configured between the two LUN devices.

[0041] (3) On the iROS operation management portal, use the above LUN devices to create a production storage repository and a disaster recovery storage repository for the production site and the disaster recovery site respectively, and add the created production storage repository to the resource pool of the production site, and add the created disaster recovery storage repository to the resource pool of the disaster recovery site.

[0042] (4) The tenant has configured a VLAN (Virtual Local Area Network) type port group network on the associated production and disaster recovery sites.

[0043] (5) iROS disaster recovery management.

[0044] In iROS disaster recovery management, you can configure site management, site pair management, and protection group management separately. Specifically, it may include the following:

[0045] a. Create production sites and disaster recovery sites in site management, and the production iROS and disaster recovery iROS send the newly added site information to the corresponding DRM (Disaster Recovery Management).

[0046] For example, when creating sites such as "126-DataCenter-Dual Active", "102-DataCenter-Remote Disaster Recovery", and "103-DataCenter-Same-City Disaster Recovery", the authentication URL, authentication user name, and online status of each site created can be displayed on the site creation interface.

[0047] b. Create site pairs for the production site and the disaster recovery site in site pair management, and configure the network mapping relationship between tenants on the production site and the disaster recovery site.

[0048] For example, create site pairs "126-DataCenter-Dual Active" and "102-DataCenter-Remote Disaster Recovery", and configure the network mapping relationship of tenants on site pairs "126-DataCenter-Dual Active" and "102-DataCenter-Remote Disaster Recovery"; for another example, create site pairs "126-DataCenter-Dual Active" and "103-DataCenter-Same City Disaster Recovery", and configure the network mapping relationship of tenants on site pairs "126-DataCenter-Dual Active" and "103-DataCenter-Same City Disaster Recovery". On the site pair creation interface, the created site pair and network mapping relationship and other information can be displayed.

[0049] c. Protection group management. A protection group is the smallest operation unit for switching between production sites and disaster recovery sites in disaster recovery management. A group of virtual machines in a protection group are switched or cut back at the same time when the site switches. When creating a protection group, you need to select a site pair, resource pools for the production site and disaster recovery site, and a storage repository for disaster recovery. You also need to add virtual machines that require disaster recovery from non-disaster recovery virtual machines to the disaster recovery virtual machine list.

[0050] In addition, after the protection group is successfully created, the production iROS and the disaster recovery iROS respectively send the creation information of the protection group to the corresponding DRM.

[0051] For example, on the protection group management interface, the name of the protection group created is "g2-126-103", and the site pair selected is: "126-DataCenter-Dual Active" and "103-DataCenter-Local Disaster Recovery". Among them, the resource pool of the production site "126-DataCenter-Dual Active" is "pool2-Huaxiang Computer Room", and the storage library is "FC-MASTER1"; the resource pool of the disaster recovery site "103-DataCenter-Local Disaster Recovery" is "pool2-Local Disaster Recovery", and the storage library is "ibm-fc-s1".

[0052] d. Enable the protection group in the protection group management. After the disaster recovery function is enabled for the virtual machine at the production site, the system automatically creates a corresponding disaster recovery virtual machine at the disaster recovery site.

[0053] The above details the disaster recovery configuration content of the disaster recovery system. After the disaster recovery configuration is completed, the first configuration information of the first virtual machine on the production site is synchronized to the virtual machine to be synchronized on the disaster recovery site. The first configuration information includes resource configuration information and disk configuration information of the first virtual machine. The resource configuration information includes site information, site pair information, protection group information, virtual machine information in the protection group, CPU information, memory information, network card information, etc. The disk configuration information includes disk operation information, disk snapshot information, disk snapshot recovery information, virtual machine clone information, virtual machine backup information, virtual machine backup recovery information, etc.

[0054] In one embodiment, the DRM periodically compares the virtual machine configuration information of the production site and the disaster recovery site (e.g., at a preset frequency), and when it is found that the virtual machine configuration information on the disaster recovery site is inconsistent with the virtual machine configuration information on the production site, the disaster recovery site is triggered to adjust the resources of the virtual machine to be synchronized according to the resource configuration information of the first virtual machine at the production site. Then, it is monitored whether the resource adjustment of the resource configuration information by the disaster recovery site is successful; if it is unsuccessful, the disaster recovery site is triggered again to adjust the resources of the virtual machine to be synchronized according to the resource configuration information of the first virtual machine.

[0055] In one embodiment, the DRM triggers the disaster recovery site in real time to adjust resources of the virtual machine to be synchronized according to the disk configuration information of the first virtual machine at the production site.

[0056] In this embodiment, by periodically comparing the virtual machine configuration information on the production site and the disaster recovery site, and timely making corresponding resource adjustments to the virtual machine configuration information on the disaster recovery site that is inconsistent with the production site, the virtual machine configuration information on the disaster recovery site and the production site can be kept consistent, ensuring data consistency during site switching.

[0057] In one embodiment, when synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site, the virtual machine to be synchronized needs to be determined first, and then the first configuration information is synchronized to the determined virtual machine to be synchronized.

[0058] Among them, the steps for determining the virtual machines to be synchronized are as follows: first, obtain a preset virtual machine list of the disaster recovery system, and obtain a synchronized virtual machine list corresponding to the first virtual machine; second, update the synchronized virtual machine list according to the preset virtual machine list; third, add the virtual machines in the synchronized virtual machine list to the list of virtual machines to be synchronized to obtain the virtual machines to be synchronized.

[0059] Next, based on the disaster recovery configuration content of the disaster recovery system in the above embodiment, how to obtain the virtual machine to be synchronized is described in detail.

[0060] First, the protection group list of the disaster recovery system is searched, and it is determined whether the protection group list is empty. Since the protection group list of the disaster recovery system has been configured in the above embodiment, the protection group list found here is not empty. If the protection group list is not empty, the list of virtual machines to be synchronized is initialized.

[0061] Then, the protection group is traversed to determine whether the status of the production site is "under protection" (i.e., whether the protection group is enabled). If the status of the production site is "under protection", it is further determined whether the status of the disaster recovery site is "under protection". If the status of the disaster recovery site is also "under protection", the virtual machine list of the protection group (i.e., the preset virtual machine list) is obtained, and the synchronized virtual machine list corresponding to the first virtual machine of the production site is obtained, and then the synchronized virtual machine list is updated according to the virtual machine list of the protection group, and the records in the synchronized virtual machine list are added to the list of virtual machines to be synchronized.

[0062] Specifically, when updating the synchronized virtual machine list according to the virtual machine list of the protection group, the following three methods may be included: 1. For virtual machines that exist in the virtual machine list of the protection group (i.e., the preset virtual machine list) but do not exist in the synchronized virtual machine list, add them to the synchronized virtual machine list; 2. For virtual machines that do not exist in the virtual machine list of the protection group but exist in the synchronized virtual machine list, delete them from the synchronized virtual machine list; 3. For virtual machines that exist in the virtual machine list of the protection group and also exist in the synchronized virtual machine list, do not perform any operation.

[0063] The update process of the synchronized virtual machine list determines the current synchronization status. For example, if a virtual machine is added to the synchronized virtual machine list, the current synchronization status is "Newly added"; if a virtual machine is deleted from the synchronized virtual machine list, the current synchronization status is "To be deleted" or "Deleting"; if the update operation is completed, the current synchronization status is "Last task successful"; and so on.

[0064] After the virtual machine to be synchronized is determined, the first configuration information of the first virtual machine on the production site is synchronized to the determined virtual machine to be synchronized. The following describes in detail how to synchronize the first configuration information of the first virtual machine on the production site to the determined virtual machine to be synchronized.

[0065] First, traverse the list of virtual machines to be synchronized.

[0066] During the traversal process, if the current synchronization state is "newly added", the VMC (Virtual Management Center) interface of the current site is called to query the detailed information of the virtual machine to be added, and then the interface of the destination site is called again to create the virtual machine, and the current synchronization state is updated to "creating", and then the list of virtual machines to be synchronized is continued to be traversed. If the current synchronization state is not "newly added", it is further determined whether the current synchronization state is "to be deleted".

[0067] During the traversal process, if the current synchronization state is "to be deleted", the interface of the destination site is called to delete the virtual machine to be deleted. If the interface returns successfully, the virtual machine is removed from the cache, and the current synchronization state is changed to "deleting", and then the list of virtual machines to be synchronized is traversed. If the current synchronization state is not "to be deleted", it is further determined whether the current synchronization state is "deleting".

[0068] During the traversal process, if the current synchronization status is "deleting", the interface of the destination site is called to query the deleted virtual machine information. If the query finds that the virtual machine still exists, the current synchronization status is changed to "to be deleted" and the interface of the destination site is called to delete the virtual machine to be deleted. If the query result shows that the virtual machine does not exist, it means that the virtual machine has been successfully deleted. At this time, the current synchronization status is changed to "deleted", and then the list of virtual machines to be synchronized is continued. If the current synchronization status is not "deleting", it is further determined whether the current synchronization status is "last task successful" or "no change".

[0069] During the traversal process, if the current synchronization status is "Last task successful" or "No change", the VMC interface of the current site is called to query the detailed information of the virtual machine, and determine whether the queried virtual machine information is the same as the virtual machine information in the current site cache; if different, the interface of the destination site is called to adjust the virtual machine resources, and when the interface returns success, the current synchronization status is changed to "Resource adjustment", and then the list of virtual machines to be synchronized is continued to be traversed; if the interface returns unsuccessful, the list of virtual machines to be synchronized is continued to be traversed; if the queried virtual machine information is the same as the virtual machine information in the current site cache, the current synchronization status is changed to "No change", and then the list of virtual machines to be synchronized is continued to be traversed.

[0070] During the traversal process, if the current synchronization status does not belong to "newly added", "to be deleted", "deleting", "last task successful" and "no change", the interface of the destination site is called to query the virtual machine details, and determine whether the queried virtual machine information is the same as the virtual machine information in the current site cache. When the queried virtual machine information is different from the virtual machine information in the current site cache, further determine whether the current synchronization status is "creating". If the current synchronization status is not "creating", further determine whether the current synchronization status is "resources are being adjusted". If the current synchronization status is "resources are being adjusted", call the VMC interface of the current site to query the virtual machine details, and compare the virtual machine information of the destination site with the virtual machine information of the current site to determine whether they are consistent; if they are consistent, change the current synchronization status to "no change". If they are inconsistent, call the destination site interface to adjust resources, and change the current synchronization status to "resources are being adjusted", and then continue to traverse the list of virtual machines to be synchronized. If the current synchronization status is not "resources are being adjusted", continue to traverse the list of virtual machines to be synchronized. If the current synchronization status is "Creating", call the VMC interface of the current site to query the virtual machine details, and call the interface of the destination site again to create the virtual machine. When the interface returns success, change the current synchronization status to "Creating", and then continue to traverse the list of virtual machines to be synchronized.

[0071] In the above resource synchronization process, the current site is the production site, and the destination site is the disaster recovery site.

[0072] During synchronization of the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site, the operation status of the production data center is monitored. If the production data center fails, the first production business of the production site is switched to the disaster recovery site.

[0073] When performing a site switch, first make sure that all the protection virtual machines at the production site have been shut down, then stop the data replication relationship between the LUN devices at the production site and the disaster recovery site, that is, stop the process of synchronizing the first configuration information on the production site to the disaster recovery site. At this time, the disaster recovery site is allowed to read and write to the auxiliary volumes in the data replication relationship of the LUN device. Then, open the disaster recovery management through the iROS operation management portal, first deactivate the protection group in the protection group management, and then switch the production site and the disaster recovery site. During the site switching process, iROS sends a message to the DRM of the disaster recovery site, and notifies the DRM to perform the disaster recovery switch in the interface with the DRM. The DRM then starts the disaster recovery virtual machine to complete the site switch.

[0074] In one embodiment, when reversely synchronizing the second configuration information of the disaster recovery virtual machine on the disaster recovery site to the virtual machine to be reversely synchronized on the production site, the virtual machine to be reversely synchronized needs to be determined first, and then the second configuration information is synchronized to the determined virtual machine to be reversely synchronized.

[0075] Among them, the steps of determining the virtual machines to be reverse synchronized are as follows: first, obtain a preset virtual machine list of the disaster recovery system, and obtain a reverse synchronization virtual machine list corresponding to the disaster recovery virtual machine; second, update the reverse synchronization virtual machine list according to the preset virtual machine list; third, add the virtual machines in the reverse synchronization virtual machine list to the virtual machine list to be reverse synchronized, and obtain the virtual machines to be reverse synchronized.

[0076] Next, based on the disaster recovery configuration content of the disaster recovery system in the above embodiment, how to obtain the virtual machine to be reversely synchronized is described in detail.

[0077] First, the protection group list of the disaster recovery system is searched, and it is determined whether the protection group list is empty. Since the protection group list of the disaster recovery system has been configured in the above embodiment, the protection group list found here is not empty. If the protection group list is not empty, the list of virtual machines to be reversely synchronized is initialized.

[0078] Then, the protection group is traversed to determine whether the status of the disaster recovery site is "under protection" (i.e., whether the protection group is enabled). If the status of the disaster recovery site is "under protection", it is further determined whether the status of the production site is "under protection". If the status of the production site is also "under protection", the virtual machine list of the protection group (i.e., the preset virtual machine list) is obtained, and the reverse synchronization virtual machine list corresponding to the disaster recovery virtual machine is obtained, and then the reverse synchronization virtual machine list is updated according to the virtual machine list of the protection group, and the records in the reverse synchronization virtual machine list are added to the list of virtual machines to be reversely synchronized.

[0079] Specifically, when updating the reverse synchronization virtual machine list according to the virtual machine list of the protection group, the following three methods may be included: 1. For virtual machines that exist in the virtual machine list of the protection group (i.e., the preset virtual machine list) but do not exist in the reverse synchronization virtual machine list, add them to the reverse synchronization virtual machine list; 2. For virtual machines that do not exist in the virtual machine list of the protection group but exist in the synchronization virtual machine list, delete them from the reverse synchronization virtual machine list; 3. For virtual machines that exist in the virtual machine list of the protection group and also in the reverse synchronization virtual machine list, no operation is performed.

[0080] The update process of the reverse synchronization virtual machine list determines the current reverse synchronization state. For example, if a virtual machine is added to the reverse synchronization virtual machine list, the current reverse synchronization state is "Newly added"; if a virtual machine is deleted from the reverse synchronization virtual machine list, the current reverse synchronization state is "To be deleted" or "Deleting"; if the update operation is completed, the current reverse synchronization state is "Last task successful"; and so on.

[0081] After determining the virtual machine to be reversely synchronized, the second configuration information of the disaster recovery virtual machine is reversely synchronized to the determined virtual machine to be reversely synchronized. The following describes in detail how to reversely synchronize the second configuration information of the disaster recovery virtual machine to the determined virtual machine to be reversely synchronized.

[0082] First, traverse the list of virtual machines to be reversely synchronized.

[0083] During the traversal process, if the current reverse synchronization state is "newly added" or "to be deleted", the list of virtual machines to be reverse synchronized is continued to be traversed. If the current reverse synchronization state is not "newly added" or "to be deleted", it is further determined whether the current reverse synchronization state is "deleting".

[0084] During the traversal process, if the current reverse synchronization state is "deleting", the interface of the destination site is called to query the deleted virtual machine information. If the query finds that the virtual machine still exists, the current synchronization state is changed to "to be deleted", and then the list of virtual machines to be reverse synchronized is continued to be traversed. If the query result shows that the virtual machine does not exist, it means that the virtual machine has been successfully deleted. At this time, the current reverse synchronization state is changed to "deleted", and then the list of virtual machines to be reverse synchronized is continued to be traversed. If the current reverse synchronization state is not "deleting", it is further determined whether the current reverse synchronization state is "creating".

[0085] During the traversal process, if the current reverse synchronization status is "Creating", the interface of the destination site is called to query the detailed information of the virtual machine, and determine whether the virtual machine has been created in the destination site. If it has been created, the VMC interface of the current site is called to query the detailed information of the virtual machine, and determine whether the queried virtual machine information is consistent with the virtual machine information in the current site cache. If they are consistent, the current reverse synchronization status is changed to "Last task successful", and then the list of virtual machines to be reverse synchronized is continued to be traversed; if they are inconsistent, the local site interface is called to adjust the virtual machine resources, and the current reverse synchronization status is changed to "Resources are being adjusted", and then the list of virtual machines to be reverse synchronized is continued to be traversed. If the virtual machine has not been created in the destination site, the current reverse synchronization status is changed to "Newly added", and then the list of virtual machines to be reverse synchronized is continued to be traversed. If the current reverse synchronization status is not "Creating", it is further determined whether the current reverse synchronization status is "Resources are being adjusted".

[0086] During the traversal process, if the current reverse synchronization status is "resources are being adjusted", the interface of the destination site and the VMC interface of the current site are called to query the detailed information of the virtual machine, and determine whether the virtual machine information of the destination site is consistent with the virtual machine information of the current site. If they are consistent, the current reverse synchronization status is changed to "last task successful", and then the list of virtual machines to be reverse synchronized is continued to be traversed; if they are inconsistent, the local site interface is called to adjust the virtual machine resources, and the current reverse synchronization status is changed to "resources are being adjusted", and then the list of virtual machines to be reverse synchronized is continued to be traversed.

[0087] If the current reverse synchronization status is not "resources are being adjusted", the interface of the destination site and the VMC interface of the current site are called to query the detailed information of the virtual machine, and determine whether the virtual machine information of the destination site is consistent with the virtual machine information of the current site. If they are consistent, continue to traverse the list of virtual machines to be reversely synchronized; if they are inconsistent, call the local site interface to adjust the virtual machine resources, and change the current reverse synchronization status to "resources are being adjusted", and then continue to traverse the list of virtual machines to be reversely synchronized.

[0088] During the above resource synchronization process, the current site is the disaster recovery site, and the destination site is the production site.

[0089] In one embodiment, the second configuration information includes differential resource information between the disaster recovery virtual machine and the virtual machine to be reversely synchronized. Therefore, when the second configuration information of the disaster recovery virtual machine on the disaster recovery site is reversely synchronized to the virtual machine to be reversely synchronized on the production site, the resource information of the disaster recovery virtual machine and the virtual machine to be reversely synchronized can be compared, and based on the comparison result of the resource information comparison, the differential resource information between the disaster recovery virtual machine and the virtual machine to be reversely synchronized can be determined, and then the resources of the virtual machine to be reversely synchronized can be adjusted based on the differential resource information.

[0090] After the second configuration information of the disaster recovery virtual machine on the disaster recovery site is reversely synchronized to the virtual machine to be reversely synchronized on the production site, the second production service of the disaster recovery site is switched to the production site.

[0091] When switching back the disaster recovery site to the production site, you need to open the disaster recovery management through the iROS operation management portal and switch back the protection group in the protection group management. When the switchback starts, the status of the protection group is displayed as "Switching back". When the resource synchronization is completed, the status of the protection group changes to "Switched back". At this time, the protection group is re-enabled.

[0092] In summary, specific embodiments of the present subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recorded in the claims can be performed in a different order and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing can be advantageous.

[0093] The above is a disaster recovery method provided in an embodiment of the present application. Based on the same idea, an embodiment of the present application also provides a disaster recovery device.

[0094] Figure 2 The present invention is a schematic block diagram of a disaster recovery device according to an embodiment of the present invention. The device is applied to a disaster recovery system. The disaster recovery system includes a production data center and a disaster recovery data center. The production data center has a production site, and the disaster recovery data center has a disaster recovery site. Figure 2 As shown, the disaster recovery device 200 includes:

[0095] The first synchronization module 210 is used to synchronize the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site when the production data center is operating normally.

[0096] The first switching module 220 is used to switch the first production business of the production site to the disaster recovery site when a production data center operation failure is detected.

[0097] In one embodiment, the apparatus 200 further includes:

[0098] The second synchronization module is used to reversely synchronize the second configuration information of the disaster recovery virtual machine on the disaster recovery site to the virtual machine to be reversely synchronized on the production site after the production business of the production site is switched to the disaster recovery site and when it is monitored that the production data center has resumed operation;

[0099] The second switching module is used to switch the second production business of the disaster recovery site to the production site.

[0100] In one embodiment, the first synchronization module 210 includes:

[0101] A first determining unit, configured to determine a virtual machine to be synchronized;

[0102] A first synchronization unit, configured to synchronize the first configuration information to the determined virtual machine to be synchronized;

[0103] Wherein, the first determining unit is used for:

[0104] Obtain a preset virtual machine list of the disaster recovery system; and, obtain a synchronized virtual machine list corresponding to the first virtual machine;

[0105] Update the synchronized virtual machine list according to the preset virtual machine list;

[0106] The virtual machines in the synchronization virtual machine list are added to the list of virtual machines to be synchronized, thereby obtaining the virtual machines to be synchronized.

[0107] In one embodiment, the first determining unit is further configured to:

[0108] Add virtual machines that exist in the preset virtual machine list and do not exist in the synchronized virtual machine list to the synchronized virtual machine list;

[0109] The virtual machines that do not exist in the preset virtual machine list but exist in the synchronized virtual machine list are deleted from the synchronized virtual machine list.

[0110] In one embodiment, the second synchronization module includes:

[0111] A second determining unit, configured to determine a virtual machine to be reversely synchronized;

[0112] A second synchronization unit, configured to synchronize the second configuration information to the determined virtual machine to be reversely synchronized;

[0113] Wherein, the second determining unit is used for:

[0114] Obtain a preset virtual machine list of the disaster recovery system; and, obtain a reverse synchronization virtual machine list corresponding to the disaster recovery virtual machine;

[0115] Update the reverse synchronization virtual machine list according to the preset virtual machine list;

[0116] The virtual machines in the reverse synchronization virtual machine list are added to the list of virtual machines to be reversely synchronized, so as to obtain the virtual machines to be reversely synchronized.

[0117] In one embodiment, the first configuration information includes resource configuration information of the first virtual machine; the resource configuration information includes at least one of site information, site pair information, protection group information, virtual machine information in the protection group, CPU information, memory information, and network card information;

[0118] The first synchronization module 210 includes:

[0119] A first triggering unit is used to trigger the disaster recovery site to adjust the resources of the virtual machine to be synchronized according to the resource configuration information of the first virtual machine at a first preset frequency;

[0120] A monitoring unit, used to monitor whether the resource adjustment of the resource configuration information by the disaster recovery site is successful;

[0121] The second triggering unit is configured to trigger the disaster recovery site again to adjust the resources of the to-be-synchronized virtual machine according to the resource configuration information of the first virtual machine if the disaster recovery site fails to adjust the resources of the resource configuration information.

[0122] In one embodiment, the first configuration information includes disk configuration information of the first virtual machine; the disk configuration information includes at least one of disk operation information, disk snapshot information, disk snapshot recovery information, virtual machine clone information, virtual machine backup information, and virtual machine backup recovery information;

[0123] The first synchronization module 210 includes:

[0124] The third triggering unit is used to trigger the disaster recovery site to adjust the resources of the virtual machine to be synchronized according to the disk configuration information of the first virtual machine.

[0125] In one embodiment, the second synchronization module is used to:

[0126] A comparison unit, used to compare resource information between the disaster recovery virtual machine and the virtual machine to be reversely synchronized;

[0127] A third determining unit is used to determine the difference resource information between the disaster recovery virtual machine and the virtual machine to be reversely synchronized according to the comparison result of the resource information comparison;

[0128] The adjustment unit is used to adjust the resources of the virtual machine to be reversely synchronized according to the difference resource information.

[0129] The device of the embodiment of the present invention can synchronize the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site when the production data center is operating normally, and then switch the first production service on the production site to the disaster recovery site when a production data center operation failure is detected. It can be seen that the technical solution adopts a data synchronization solution under multiple data centers during the disaster recovery process, that is, synchronizing the production data center to the disaster recovery data center, thereby improving the security and reliability of the data and meeting the security and reliability requirements of the cloud platform data.

[0130] Those skilled in the art should understand that the above-mentioned disaster recovery device can be used to implement the disaster recovery method described above, and the detailed description thereof should be similar to the description of the method part above, and will not be further described here to avoid redundancy.

[0131] Figure 3 is a schematic block diagram of a disaster recovery system according to an embodiment of the present invention. Figure 3 As shown, the disaster recovery system 300 includes a production data center 310 and a disaster recovery data center 320 .

[0132] The production data center 310 is provided with a production site, and the disaster recovery data center 320 is provided with a disaster recovery site; the production data center 310 and the disaster recovery data center 320 each include:

[0133] The disaster recovery module DRM is used to synchronize the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site when the production data center is operating normally.

[0134] The resource operation system iROS is used to switch the primary production business of the production site to the disaster recovery site when a production data center operation failure is detected.

[0135] The storage device is used to store first configuration information of the first virtual machine.

[0136] In one embodiment, the disaster recovery module DRM is further used to reversely synchronize the second configuration information of the disaster recovery virtual machine on the disaster recovery site to the virtual machine to be reversely synchronized on the production site when monitoring that the production data center is restored to operation.

[0137] The resource operation system iROS is also used to switch the secondary production business of the disaster recovery site to the production site.

[0138] The storage device is also used to store the second configuration information of the disaster recovery virtual machine.

[0139] The system using the embodiment of the present invention can synchronize the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site when the production data center is running normally, and then switch the first production business on the production site to the disaster recovery site when a production data center operation failure is detected. It can be seen that in the disaster recovery process, the technical solution adopts a data synchronization solution under multiple data centers, that is, synchronizing the production data center to the disaster recovery data center, thereby improving the security and reliability of the data and meeting the security and reliability requirements of the cloud platform data.

[0140] Based on the same idea, the embodiment of the present application also provides a disaster recovery device, such as Figure 4As shown. The disaster recovery device may have relatively large differences due to different configurations or performances, and may include one or more processors 401 and memory 402, and the memory 402 may store one or more storage applications or data. Among them, the memory 402 can be short-term storage or persistent storage. The application stored in the memory 402 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the disaster recovery device. Furthermore, the processor 401 can be configured to communicate with the memory 402 to execute a series of computer executable instructions in the memory 402 on the disaster recovery device. The disaster recovery device may also include one or more power supplies 403, one or more wired or wireless network interfaces 404, one or more input and output interfaces 405, and one or more keyboards 406.

[0141] Specifically in this embodiment, the disaster recovery device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the disaster recovery device, and the one or more programs are configured to be executed by one or more processors, including the following computer executable instructions:

[0142] When the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site;

[0143] When a production data center operation failure is detected, the primary production business of the production site is switched to the disaster recovery site.

[0144] Optionally, when the computer executable instructions are executed, the processor may also:

[0145] After the production business of the production site is switched to the disaster recovery site, when it is monitored that the production data center is restored to operation, the second configuration information of the disaster recovery virtual machine on the disaster recovery site is reversely synchronized to the virtual machine to be reversely synchronized on the production site;

[0146] Switch the second production service of the disaster recovery site to the production site.

[0147] Optionally, when the computer executable instructions are executed, the processor may also:

[0148] Determining the virtual machine to be synchronized;

[0149] The first configuration information is synchronized to the determined virtual machine to be synchronized.

[0150] Optionally, when the computer executable instructions are executed, the processor may also:

[0151] Obtaining a preset virtual machine list of the disaster recovery system; and, obtaining a synchronized virtual machine list corresponding to the first virtual machine;

[0152] Updating the synchronized virtual machine list according to the preset virtual machine list;

[0153] The virtual machines in the synchronized virtual machine list are added to the list of virtual machines to be synchronized, so as to obtain the virtual machines to be synchronized.

[0154] Optionally, when the computer executable instructions are executed, the processor may also:

[0155] Adding virtual machines that exist in the preset virtual machine list and do not exist in the synchronized virtual machine list to the synchronized virtual machine list;

[0156] Virtual machines that do not exist in the preset virtual machine list but exist in the synchronous virtual machine list are deleted from the synchronous virtual machine list.

[0157] Optionally, when the computer executable instructions are executed, the processor may also:

[0158] Determine the virtual machine to be reversely synchronized;

[0159] The second configuration information is synchronized to the determined virtual machine to be reversely synchronized.

[0160] Optionally, when the computer executable instructions are executed, the processor may also:

[0161] Obtaining a preset virtual machine list of the disaster recovery system; and, obtaining a reverse synchronization virtual machine list corresponding to the disaster recovery virtual machine;

[0162] Updating the reverse synchronization virtual machine list according to the preset virtual machine list;

[0163] The virtual machines in the reverse synchronization virtual machine list are added to the list of virtual machines to be reversely synchronized, so as to obtain the virtual machines to be reversely synchronized.

[0164] Optionally, the first configuration information includes resource configuration information of the first virtual machine; the resource configuration information includes at least one of site information, site pair information, protection group information, virtual machine information in the protection group, CPU information, memory information, and network card information;

[0165] The computer executable instructions, when executed, may also cause the processor to:

[0166] Triggering the disaster recovery site to adjust resources of the to-be-synchronized virtual machine according to the resource configuration information of the first virtual machine at a first preset frequency;

[0167] Monitoring whether the resource adjustment of the resource configuration information by the disaster recovery site is successful;

[0168] If not, the disaster recovery site is triggered again to adjust the resources of the virtual machine to be synchronized according to the resource configuration information of the first virtual machine.

[0169] Optionally, the first configuration information includes disk configuration information of the first virtual machine; the disk configuration information includes at least one of disk operation information, disk snapshot information, disk snapshot recovery information, virtual machine clone information, virtual machine backup information, and virtual machine backup recovery information;

[0170] The computer executable instructions, when executed, may also cause the processor to:

[0171] The disaster recovery site is triggered to adjust resources of the virtual machine to be synchronized according to the disk configuration information of the first virtual machine.

[0172] Optionally, when the computer executable instructions are executed, the processor may also:

[0173] Comparing resource information between the disaster recovery virtual machine and the virtual machine to be reversely synchronized;

[0174] Determining the difference resource information between the disaster recovery virtual machine and the virtual machine to be reversely synchronized according to the comparison result of the resource information comparison;

[0175] The resources of the virtual machine to be reversely synchronized are adjusted according to the difference resource information.

[0176] Figure 5 FIG. 2 shows a schematic structural diagram of a disaster recovery system according to an embodiment of the present invention. Figure 5 As shown in FIG. 1 , the disaster recovery system includes a production data center and a disaster recovery data center. The production data center and the disaster recovery data center are in a primary-backup relationship.

[0177] Among them, the production data center and disaster recovery data center each include a resource operation system iROS, a disaster recovery management DRM, a resource pool (including a general resource pool and a disaster recovery resource pool) and a storage library (including a general storage library and a disaster recovery storage library).

[0178] The resource operation system iROS implements disaster recovery management, that is, disaster recovery configuration, disaster recovery drills, and disaster recovery switching can be performed through the iROS operation management portal.

[0179] Disaster recovery management DRM includes TECS, unified elastic computing system iECS and virtualization management center VMC. Among them, TECS is a virtualization product based on the open source KVM (Keyboard Video Mouse) virtualization technology, which has been enhanced in terms of performance and real-time performance. It is used to provide virtualization management functions such as virtual machine life cycle management, cluster management, dynamic resource scheduling and dynamic energy consumption management. Unified elastic computing system iECS and virtualization management center VMC are used to achieve resource synchronization between production data centers and disaster recovery data centers. Disaster recovery management DRM is the data center DC (Data Center) of each site.

[0180] The storage library is used to store resource data of each data center, and relies on the data synchronization technology of the storage itself to realize the single data replication function from the LUN device of the production data center to the LUN device of the disaster recovery data center. Through the data replication function between the storage libraries, data synchronization between the production data center and the disaster recovery data center is realized.

[0181] The embodiment of the present application further proposes a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute the above-mentioned disaster recovery method, and are specifically used to execute:

[0182] When the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site;

[0183] When a production data center operation failure is detected, the primary production business of the production site is switched to the disaster recovery site.

[0184] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0185] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0186] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0187] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0188] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0189] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0190] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0191] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0192] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0193] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0194] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0195] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0196] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A disaster recovery method, characterized in that: Applied to a disaster recovery system, the disaster recovery system includes a production data center and a disaster recovery data center, the production data center has a production site, and the disaster recovery data center has a disaster recovery site; the method includes: When the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site; When a failure in the production data center is detected, the first production service of the production site is switched to the disaster recovery site; Synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site includes: Determining the virtual machine to be synchronized; Synchronizing the first configuration information to the determined virtual machine to be synchronized; Wherein, determining the virtual machine to be synchronized includes: Obtaining a preset virtual machine list of the disaster recovery system; and, obtaining a synchronized virtual machine list corresponding to the first virtual machine; Updating the synchronized virtual machine list according to the preset virtual machine list; The virtual machines in the synchronized virtual machine list are added to the list of virtual machines to be synchronized, so as to obtain the virtual machines to be synchronized.

2. The method according to claim 1, characterized in that: After switching the production service of the production site to the disaster recovery site, the method further includes: When it is monitored that the production data center is restored to operation, the second configuration information of the disaster recovery virtual machine on the disaster recovery site is reversely synchronized to the virtual machine to be reversely synchronized on the production site; Switch the second production service of the disaster recovery site to the production site.

3. The method according to claim 2, characterized in that Reversely synchronizing the second configuration information of the disaster recovery virtual machine on the disaster recovery site to the virtual machine to be reversely synchronized on the production site, including: Determine the virtual machine to be reversely synchronized; Synchronizing the second configuration information to the determined virtual machine to be reversely synchronized; Wherein, determining the virtual machine to be reversely synchronized includes: Obtaining a preset virtual machine list of the disaster recovery system; and, obtaining a reverse synchronization virtual machine list corresponding to the disaster recovery virtual machine; Updating the reverse synchronization virtual machine list according to the preset virtual machine list; The virtual machines in the reverse synchronization virtual machine list are added to the list of virtual machines to be reversely synchronized, so as to obtain the virtual machines to be reversely synchronized.

4. The method according to claim 1, characterized in that The first configuration information includes resource configuration information of the first virtual machine; the resource configuration information includes at least one of site information, site pair information, protection group information, virtual machine information in the protection group, CPU information, memory information, and network card information; The step of synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site includes: Triggering the disaster recovery site to adjust resources of the to-be-synchronized virtual machine according to the resource configuration information of the first virtual machine at a first preset frequency; Monitoring whether the resource adjustment of the resource configuration information by the disaster recovery site is successful; If not, the disaster recovery site is triggered again to adjust the resources of the virtual machine to be synchronized according to the resource configuration information of the first virtual machine.

5. The method according to claim 1, characterized in that The first configuration information includes disk configuration information of the first virtual machine; the disk configuration information includes at least one of disk operation information, disk snapshot information, disk snapshot recovery information, virtual machine clone information, virtual machine backup information, and virtual machine backup recovery information; The step of synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site includes: The disaster recovery site is triggered to adjust resources of the virtual machine to be synchronized according to the disk configuration information of the first virtual machine.

6. The method according to claim 2, characterized in that The reverse synchronization of the second configuration information of the disaster recovery virtual machine on the disaster recovery site to the virtual machine to be reversely synchronized on the production site includes: Comparing resource information between the disaster recovery virtual machine and the virtual machine to be reversely synchronized; Determining the difference resource information between the disaster recovery virtual machine and the virtual machine to be reversely synchronized according to the comparison result of the resource information comparison; The resources of the virtual machine to be reversely synchronized are adjusted according to the difference resource information.

7. A disaster recovery device, characterized in that: Applied to a disaster recovery system, the disaster recovery system includes a production data center and a disaster recovery data center, the production data center has a production site, and the disaster recovery data center has a disaster recovery site; the device includes: A first synchronization module, configured to synchronize first configuration information of a first virtual machine on the production site to a virtual machine to be synchronized on the disaster recovery site when the production data center is operating normally; A first switching module is used to switch the first production business of the production site to the disaster recovery site when a failure in the production data center is detected; The first synchronization module comprises: A first determining unit, configured to determine a virtual machine to be synchronized; A first synchronization unit, configured to synchronize the first configuration information to the determined virtual machine to be synchronized; Wherein, the first determining unit is used for: Obtain a preset virtual machine list of the disaster recovery system; and, obtain a synchronized virtual machine list corresponding to the first virtual machine; Update the synchronized virtual machine list according to the preset virtual machine list; The virtual machines in the synchronization virtual machine list are added to the list of virtual machines to be synchronized, thereby obtaining the virtual machines to be synchronized.

8. The device according to claim 7, characterized in that The device also includes: A second synchronization module is used to reversely synchronize the second configuration information of the disaster recovery virtual machine on the disaster recovery site to the virtual machine to be reversely synchronized on the production site after the production business of the production site is switched to the disaster recovery site and when it is monitored that the production data center resumes operation; The second switching module is used to switch the second production service of the disaster recovery site to the production site.

9. A disaster recovery system, characterized in that: It includes a production data center and a disaster recovery data center; the production data center has a production site, and the disaster recovery data center has a disaster recovery site; the production data center and the disaster recovery data center each include: The disaster recovery module DRM is used to synchronize the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site when the production data center is operating normally; determine the virtual machine to be synchronized; synchronize the first configuration information to the determined virtual machine to be synchronized; obtain a preset virtual machine list of the disaster recovery system; and obtain a synchronized virtual machine list corresponding to the first virtual machine; update the synchronized virtual machine list according to the preset virtual machine list; add the virtual machines in the synchronized virtual machine list to the virtual machine list to obtain the virtual machine to be synchronized; A resource operation system iROS, configured to switch the first production business of the production site to the disaster recovery site when a failure in the production data center is detected; A storage device is used to store first configuration information of the first virtual machine.

10. The system according to claim 9, characterized in that The disaster recovery module DRM is further used to reversely synchronize the second configuration information of the disaster recovery virtual machine on the disaster recovery site to the virtual machine to be reversely synchronized on the production site when monitoring that the production data center has resumed operation; The resource operation system iROS is also used to switch the second production business of the disaster recovery site to the production site; The storage device is also used to store the second configuration information of the disaster recovery virtual machine.

11. A disaster recovery device, characterized in that: Applied to a disaster recovery system, the disaster recovery system includes a production data center and a disaster recovery data center, the production data center has a production site, and the disaster recovery data center has a disaster recovery site; the device includes: Processor; and a memory arranged to store computer executable instructions which, when executed, cause the processor to: When the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site; When a failure in the production data center is detected, the first production service of the production site is switched to the disaster recovery site; Determining the virtual machine to be synchronized; Synchronizing the first configuration information to the determined virtual machine to be synchronized; Obtaining a preset virtual machine list of the disaster recovery system; and, obtaining a synchronized virtual machine list corresponding to the first virtual machine; Updating the synchronized virtual machine list according to the preset virtual machine list; The virtual machines in the synchronized virtual machine list are added to the list of virtual machines to be synchronized, so as to obtain the virtual machines to be synchronized.

12. A storage medium for storing computer executable instructions, wherein the executable instructions implement the following process when executed: When the production data center is operating normally, synchronizing the first configuration information of the first virtual machine on the production site to the virtual machine to be synchronized on the disaster recovery site; When a failure in the production data center is detected, the first production service of the production site is switched to the disaster recovery site; Determining the virtual machine to be synchronized; Synchronizing the first configuration information to the determined virtual machine to be synchronized; Obtaining a preset virtual machine list of the disaster recovery system; and, obtaining a list of synchronized virtual machines corresponding to the first virtual machine; Updating the synchronized virtual machine list according to the preset virtual machine list; The virtual machines in the synchronized virtual machine list are added to the list of virtual machines to be synchronized, so as to obtain the virtual machines to be synchronized.

Images