Data disaster recovery method and computing device

Abstract

The embodiment of the invention provides a data disaster recovery method and computing equipment, relates to the field of computers, and can improve the data read-write capability of the disaster recovery equipment. The method comprises the steps that under the condition that production equipment breaks down, services on the production equipment are migrated to disaster recovery equipment, a service data volume is generated based on a snapshot data volume of the production equipment, and the snapshot data volume comprises snapshots of backup data of service data used by the production equipment; the service data volume comprises service data in the snapshot; and setting the service data volume as a data source of disaster recovery equipment, so that the disaster recovery equipment bears the service before the production equipment fails based on the service data volume.

Description

Technical Field

[0001] The embodiments of the present application relate to the computer field, and in particular to a data disaster recovery method and a computing device. Background Art

[0002] With the continuous development of computer technology, disaster recovery technology has become a focus of major manufacturers in order to avoid long-term business interruption caused by natural disasters or other factors in software systems.

[0003] A common disaster recovery method is that when a computing device in a production system (i.e., the production end) fails, the disaster recovery device (e.g., a disaster recovery virtual machine) in the disaster recovery system (i.e., the disaster recovery end) uses the data in the snapshot of the backup data as the data source to take over the equipment processing business in the production system; thereby avoiding the problem of long-term business interruption; wherein the backup data is a backup of the business data stored in the above-mentioned production system.

[0004] However, since snapshots have performance limitations on reading and writing data, the disaster recovery system has low efficiency in processing services when the service load is large. Therefore, how to improve the data reading and writing capabilities of the disaster recovery system has become an urgent problem to be solved in this field. Summary of the invention

[0005] The embodiments of the present application provide a data disaster recovery method and a computing device for improving the data reading and writing capabilities of a disaster recovery system.

[0006] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, an embodiment of the present application provides a data disaster recovery method, the method comprising: in the event of a production equipment failure, migrating the business on the production equipment to the disaster recovery equipment, and generating a business data volume based on the snapshot data volume of the production equipment, the snapshot data volume including a snapshot of backup data of the business data used by the business on the above-mentioned production equipment, the business data volume including the business data corresponding to the above-mentioned snapshot; setting the above-mentioned business data volume as the data source of the disaster recovery equipment, so that the disaster recovery equipment carries the business before the failure of the above-mentioned production equipment based on the business data volume.

[0008] An embodiment of the present application provides a data disaster recovery method. In the event of a production device failure, the method migrates the business on the production device to the disaster recovery device, and generates a business data volume based on the snapshot data volume of the production device, wherein the snapshot data volume includes a snapshot of backup data of the business data used by the production device, and the business data volume is set as the data source of the disaster recovery device, so that the disaster recovery device carries the business before the production device failure based on the business data volume; since the business data volume includes the business data corresponding to the snapshot in the snapshot data volume, rather than the snapshot in the snapshot data volume, there is no restriction on data reading and writing for the business data volume, and since the above-mentioned disaster recovery device carries the business on the production device based on the business data volume, the data reading and writing capability of the disaster recovery device is improved.

[0009] In a possible implementation, before generating the service data volume based on the snapshot data volume of the production device, the method further includes: setting the snapshot data volume as a data source of the disaster recovery device.

[0010] An embodiment of the present application provides a data disaster recovery method, which, in the event of a production device failure, migrates the business on the production device to the disaster recovery device, and sets the snapshot data volume as the data source of the disaster recovery device, so as to achieve rapid takeover of the production device; wherein the snapshot data volume includes a snapshot of the backup data, and the backup data is a backup of the business data on the above-mentioned production device. In the process of the disaster recovery device carrying the above-mentioned business based on the snapshot data volume, a business data volume is generated based on the snapshot data volume, and the business data volume is set as the data source of the disaster recovery device; the business data volume includes the business data in the snapshot in the snapshot data volume. Since the data in the business data volume is business data, not a snapshot of business data, there is no restriction on data reading and writing, thereby improving the efficiency of the disaster recovery device in processing business; therefore, the above method not only realizes the rapid takeover of the production system by the disaster recovery system, but also ensures the data reading and writing capabilities of the disaster recovery system.

[0011] In a possible implementation, generating a business data volume based on a snapshot data volume of a production device includes: obtaining full business data in a current snapshot data volume; and synchronizing the full business data to the business data volume.

[0012] A possible implementation method also includes: obtaining the first incremental data in the above-mentioned snapshot data volume; the first incremental data is the business data corresponding to the differential snapshot data that has changed in the snapshot included in the snapshot data volume during the last synchronization to the business data volume; and synchronizing the first incremental data to the business data volume.

[0013] In the above-mentioned embodiment, in the process of the disaster recovery device carrying the above-mentioned business based on the snapshot data volume, not only the full business data in the snapshot data volume is synchronized to the business data volume; the first incremental data in the snapshot data volume is also synchronized to the business data volume; because the first incremental data is the business data corresponding to the differential snapshot data that has changed in the snapshot included in the snapshot data volume during the last synchronization to the business data volume; thereby, the inconsistency between the data in the snapshot data volume and the data in the above-mentioned business data volume is avoided to a certain extent, and then, the problem of business data loss is solved to a certain extent.

[0014] In a possible implementation, the business data volume is set as the data source of the disaster recovery device, and the method further includes: when the data volume of the first incremental data is less than or equal to the preset data volume, setting the business data volume as the data source of the disaster recovery device.

[0015] In one possible implementation, the above-mentioned setting of the business data volume as the data source of the disaster recovery device includes: performing a shutdown operation on the disaster recovery device; when the disaster recovery device is in a shutdown state, synchronizing the first incremental data to the above-mentioned business data volume; switching the data source of the business of the above-mentioned disaster recovery device from the snapshot data volume to the business data volume; and starting the disaster recovery device.

[0016] In the above embodiment, when the data amount of the first incremental data is less than or equal to the preset data amount, the disaster recovery device is shut down so that the data in the snapshot data volume serving as the data source of the disaster recovery device will no longer change; and when the disaster recovery device is in a shutdown state, the first incremental data is synchronized to the business data volume so that the business data in the business data volume is the same as the business data in the snapshot data volume, thereby avoiding the problem of inconsistency between the data in the snapshot data volume and the data in the above business data volume, and therefore solving the problem of business data loss.

[0017] In a possible implementation, before setting the business data volume as the data source of the disaster recovery device, the method also includes: monitoring whether the snapshot data volume generates second incremental data within a preset time period; setting the business data volume as the data source of the disaster recovery device includes: setting the business data volume as the data source of the disaster recovery device when no second incremental data is generated within the preset time period.

[0018] After synchronizing the full amount of business data in the snapshot data volume to the business data volume, the above embodiment obtains the business data (i.e., the first incremental data) corresponding to the differential snapshot data that has changed in the snapshot data volume during the synchronization of the full amount of business data; and when the first incremental data is less than or equal to the preset data volume, and the snapshot data volume does not have the second incremental data within the preset time period, the disaster recovery device is shut down, the first incremental data is synchronized to the business data volume, and the data source of the business of the disaster recovery device is switched from the snapshot data volume to the business data volume; then, the disaster recovery device is started so that the disaster recovery device processes the business based on the business data in the business data volume. Since the data in the above business data volume is business data, not a snapshot of business data, there is no restriction on data reading and writing, thereby improving the efficiency of the disaster recovery device in processing business; therefore, the above method not only realizes the rapid takeover of the production system by the disaster recovery system, but also ensures the data reading and writing capability of the disaster recovery system.

[0019] In a possible implementation, before the business data volume is generated based on the snapshot data volume of the production device, the method includes: in the system where the disaster recovery device is located, creating a business data volume that has the same attributes and quantity as the production volume of the production device for storing business data, and does not contain data, wherein the business data volume includes a first business data volume and a second business data volume; the above-mentioned generation of the business data volume based on the snapshot data volume includes: synchronizing the business data in the first snapshot included in the first snapshot data volume to the first business data volume; wherein the snapshot data volume includes: the first snapshot data volume and the second snapshot data volume; the first snapshot is a snapshot of the backup data of the production volume with the same attributes as the above-mentioned first business data volume; synchronizing the business data in the second snapshot included in the above-mentioned second snapshot data volume to the second business data volume; wherein the second snapshot is a snapshot of the backup data of the production volume with the same attributes as the second business data volume.

[0020] In the above embodiment, in the system where the disaster recovery device is located, after creating a business data volume (including: a first business data volume and a second business data volume) with the same attributes and quantity as the production volume used by the production device to store business data, the business data in the first snapshot included in the first snapshot data volume is synchronized to the first business data volume, and the business data in the second snapshot included in the second snapshot data volume is synchronized to the second business data volume; since the first snapshot is a snapshot of the backup data of the production volume with the same attributes as the above-mentioned first business data volume, and the second snapshot is a snapshot of the backup data of the production volume with the same attributes as the above-mentioned second business data volume; it can be seen that the above is to store the business data in the snapshot data volume in a distributed storage manner, which improves the reading and writing efficiency of the data in the business data volume compared to the method of centrally storing all data in all snapshot data volumes in one business data volume.

[0021] In a possible implementation, the generating of the business data volume based on the snapshot data volume of the production device includes: obtaining a disaster recovery state, the disaster recovery state including: an on state or a off state. When the disaster recovery state is on, generating the business data volume based on the snapshot data volume.

[0022] In the above embodiment, the method controls the disaster recovery device to use the snapshot in the snapshot data volume as the data source and take over the business on the production device in the case of a production device failure; at the same time, when the disaster recovery state is turned on, a business data volume is generated based on the snapshot data volume, and the business data volume is set as the data source of the business on the disaster recovery device. Since the above method generates the business data volume when the disaster recovery state is turned on, and controls the disaster recovery device to carry the business based on the data in the business data volume; it can be seen that by setting the above disaster recovery state, the disaster recovery device can control whether to execute the above action of generating the above business data volume, thereby improving the flexibility of the above data disaster recovery method.

[0023] In the second aspect, an embodiment of the present application provides a data disaster recovery device, which includes: a setting module and a generation module; the setting module is used to migrate the business on the production device to the disaster recovery device in the event of a production equipment failure, and the generation module is used to generate a business data volume based on the snapshot data volume of the production device, the snapshot data volume includes a snapshot of backup data of the business data used by the business on the production device, and the business data volume includes the business data corresponding to the snapshot; the setting module is used to set the business data volume as the data source of the disaster recovery device, so that the disaster recovery device carries the business before the production equipment failure based on the business data volume.

[0024] In a possible implementation, the setting module is used to set the snapshot data volume as the data source of the disaster recovery device.

[0025] In a possible implementation, the data disaster recovery device also includes a transceiver module and a synchronization module; the transceiver module is used to obtain the full amount of business data in the current snapshot data volume; the synchronization module is used to synchronize the full amount of business data to the business data volume.

[0026] In one possible implementation, the transceiver module is used to obtain the first incremental data in the snapshot data volume; the first incremental data is the business data corresponding to the differential snapshot data that has changed in the snapshot included in the snapshot data volume during the last synchronization to the business data volume; the synchronization module is used to synchronize the first incremental data to the business data volume.

[0027] In a possible implementation, the setting module is used to set the business data volume as the data source of the disaster recovery device when the data volume of the first incremental data is less than or equal to the preset data volume.

[0028] In one possible implementation, the setting module is used to perform a shutdown operation on the disaster recovery device; the synchronization module is used to synchronize the first incremental data to the business data volume when the disaster recovery device is in a shutdown state; the setting module is used to switch the data source of the business of the disaster recovery device from the snapshot data volume to the business data volume; the setting module is also used to start the disaster recovery device.

[0029] In one possible implementation, the transceiver module is used to monitor whether the snapshot data volume generates second incremental data within a preset time period; the setting module is used to set the business data volume as the data source of the disaster recovery device if the second incremental data is not generated within the preset time period.

[0030] In one possible implementation, a setting module is used to create a business data volume in a system where a disaster recovery device is located, which has the same properties and quantity as a production volume used by a production device to store business data, and does not contain data, wherein the business data volume includes a first business data volume and a second business data volume; a synchronization module is used to synchronize the business data in a first snapshot included in a first snapshot data volume to the first business data volume; wherein the snapshot data volume includes: a first snapshot data volume and a second snapshot data volume; the first snapshot is a snapshot of the backup data of the production volume with the same properties as the first business data volume; the synchronization module is used to synchronize the business data in a second snapshot included in the second snapshot data volume to the second business data volume; wherein the second snapshot is a snapshot of the backup data of the production volume with the same properties as the second business data volume.

[0031] In a possible implementation, the transceiver module is used to obtain the disaster recovery state, which includes: an on state or a off state. The generation module is used to generate a business data volume based on the snapshot data volume when the disaster recovery state is on.

[0032] In a third aspect, an embodiment of the present application provides a computing device, which includes a memory and a processor, wherein the memory is coupled to the processor; the memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the processor, the method of the first aspect and its possible implementation methods are implemented.

[0033] In a fourth aspect, a computer-readable storage medium is provided, which stores computer instructions. When the computer instructions in the computer-readable storage medium are executed by a computing device, the computing device performs the functions of the apparatus of the first aspect and its possible implementation methods.

[0034] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computing device, enables the computing device to execute the functions of the apparatus of the above-mentioned first aspect and possible implementations thereof.

[0035] It should be understood that the beneficial effects achieved by the technical solutions of the second to fifth aspects of the embodiments of the present application and the corresponding possible implementation methods can be referred to the technical effects of the first aspect and its corresponding possible implementation methods mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 A management system provided in this application embodiment Figure 1 ;

[0037] Figure 2 A management system provided in this application embodiment Figure 2 ;

[0038] Figure 3 A management system provided in this application embodiment Figure 3 ;

[0039] Figure 4 A schematic diagram of the hardware structure of a computing device provided in an embodiment of the present application;

[0040] Figure 5 A data disaster recovery method process diagram provided in the embodiment of the present application Figure 1 ;

[0041] Figure 6 A data disaster recovery method process diagram provided in the embodiment of the present application Figure 2 ;

[0042] Figure 7 A data disaster recovery method process diagram provided in the embodiment of the present application Figure 3 ;

[0043] Figure 8 A data disaster recovery method process diagram provided in the embodiment of the present application Figure 4 ;

[0044] Fig. 9 A data disaster recovery method process diagram provided in the embodiment of the present application Figure 5 ;

[0045] Fig.10 A data disaster recovery method process diagram provided in the embodiment of the present application Figure 6 ;

[0046] Fig.11 A data disaster recovery method process diagram provided in the embodiment of the present application Figure 7 ;

[0047] Fig.12 A data disaster recovery method process diagram provided in the embodiment of the present application Figure 8 ;

[0048] Fig.13 A schematic diagram of the structure of a data disaster recovery device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0050] The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects rather than to describe a specific order of objects. For example, the first incremental data and the second incremental data are used to distinguish different incremental data rather than to describe a specific order of incremental data.

[0051] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0052] In the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" refers to two or more than two. For example, multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.

[0053] First, some concepts involved in a data disaster recovery method and a computing device provided in an embodiment of the present application are explained as follows:

[0054] Snapshot data: usually refers to the image of a specified data set at a certain point in time (the point in time when the copy starts). Snapshot data is not a copy of the data, but records the metadata of the data.

[0055] Full data: refers to all data in the data warehouse.

[0056] When a production device fails, a snapshot volume of backup data of the business data on the production device is usually mounted under the system file of the disaster recovery device; then, the business on the production device is migrated to the disaster recovery device, so that the disaster recovery device uses the snapshot (i.e., snapshot data) in the mounted snapshot volume as a data source to carry the business originally belonging to the production device.

[0057] It can be seen that the data source used by the above-mentioned disaster recovery equipment to process business is the snapshot data in the snapshot volume; however, since the snapshot has performance limitations on reading and writing data, when the business load is large, the efficiency of the disaster recovery system in processing business is low. Therefore, how to improve the data reading and writing capabilities of the disaster recovery system has become a problem that needs to be urgently solved in this field.

[0058] In view of this, an embodiment of the present application provides a data disaster recovery method. In the event of a failure in a production device, the disaster recovery device uses a snapshot volume as a data source to quickly take over the business on the production device. At the same time, the business data in the snapshot included in the snapshot volume is synchronized to the business data volume. After the data synchronization is completed, the data source of the disaster recovery device is switched from the above-mentioned snapshot volume to the above-mentioned business data volume. Since the data in the business data volume is business data, not a snapshot (i.e., snapshot data), there is no restriction on data reading and writing for the business data volume, thereby improving the data reading and writing capabilities of the disaster recovery device.

[0059] In some embodiments, an embodiment of the present application provides a data disaster recovery method, which, in the event of a production equipment failure, migrates the business on the production equipment to the disaster recovery equipment, and generates a business data volume based on the snapshot data volume of the production equipment, wherein the snapshot data volume includes a snapshot of backup data of the business data used by the production equipment, and the business data volume is set as the data source of the disaster recovery equipment, so that the disaster recovery equipment carries the business before the failure of the production equipment based on the business data volume; since the business data volume includes the business data corresponding to the snapshot in the snapshot data volume, there is no restriction on data reading and writing for the business data volume, and since the above-mentioned disaster recovery equipment carries the business on the production equipment based on the business data volume, the data reading and writing capability of the disaster recovery equipment is improved.

[0060] The data disaster recovery method provided in the embodiment of the present application can be applied in the following aspects: Figure 1 In the management system shown, the management system includes: a production end, a management device and a disaster recovery end; wherein the production end includes: production equipment and production volumes, and the disaster recovery end includes: disaster recovery equipment.

[0061] It should be noted that the specific types of the above-mentioned production equipment, management equipment and disaster recovery equipment can be virtual machines or physical machines, and the embodiments of the present application do not specifically limit them.

[0062] The above-mentioned production volume is used to store the business data of the production equipment. When there is no failure on the production side, the production volume is the data source of the production equipment; that is, when there is no failure on the production side, the production equipment processes the business input into the production equipment based on the business data in the production volume.

[0063] It should be noted that the above-mentioned production-end failure may be a failure of the production equipment in the above-mentioned production end, or a failure of the production volume in the production end, or a failure of both the production equipment and the production volume at the same time, which is not specifically limited in the embodiments of the present application.

[0064] The production device is also used to back up the business data in the production volume to the mirror volume in the management device; the specific implementation method may be to mount the mirror volume in the management device in the system file of the production device; then, the production device backs up the business data in the production volume to the mirror volume. Alternatively, a data transmission link is established between the production device and the management device, and then, the production device backs up the business data in the production volume to the mirror volume through the data transmission link.

[0065] Optionally, the execution subject of backing up the business data in the production volume to the mirror volume in the management device may also be the management device, which is not specifically limited in the embodiments of the present application.

[0066] In one implementation, the production volume is located in other devices in the production end. The production volume is mounted in the system file of the production device, or the production device accesses the production volume through a remote link, so that the production device can add, delete, modify and query the business data in the production volume.

[0067] Disaster recovery equipment is used to take over the business on the production equipment when a failure occurs on the production side.

[0068] The above-mentioned management device includes a management module, which is used to generate a snapshot data volume based on the above-mentioned mirror volume in the event of a production end failure. The snapshot data volume includes a snapshot of the backup data in the mirror volume (i.e., snapshot data of the backup data); then, the management module mounts the snapshot data volume under the system file of the disaster recovery device, and sets the data source used by the disaster recovery device to process the business (i.e., business request) to the snapshot data volume; so that the disaster recovery device processes the business using the snapshot data volume as the data source.

[0069] It should be noted that a snapshot is a way to back up or store data. When writing business data to a snapshot, the snapshot data (i.e., metadata) corresponding to the business data is written into the snapshot. When reading data from a snapshot, the business data corresponding to the snapshot data in the snapshot is read. In other words, the data read is not the snapshot data in the snapshot, but the normal data (i.e., business data) corresponding to the snapshot data. Based on this, although the snapshot data volume stores a snapshot of the backup data, the data read from the snapshot data volume is the business data corresponding to the snapshot data in the snapshot data volume.

[0070] The above-mentioned management module is also used to synchronize the business data in the snapshot data volume to the disaster recovery end to obtain the business data volume when the disaster recovery device processes the business using the snapshot data volume as the data source, and set the business data volume as the data source of the disaster recovery device, so that the disaster recovery device carries the business before the failure of the production equipment based on the business data volume. Since the business data volume and the disaster recovery device are located at the same end (i.e., the disaster recovery end), the processing efficiency of the disaster recovery device on the data in the business data volume is improved.

[0071] The data disaster recovery method provided in the embodiment of the present application can also be applied to Figure 2 In the management system shown, the management system includes: a production end (ie, a production environment or a production system) and a disaster recovery end (ie, a disaster recovery environment or a disaster recovery system).

[0072] The above-mentioned production end includes: production virtual machine (virtual manufacturing, VM) 1, production VM2 and production volume; wherein, production VM1 and production VM2 are production equipment for processing business; when there is no failure in the production end, the production VM1 and production VM2 use the production volume storing business data as the data source to process business.

[0073] It should be noted that the above-mentioned production end may include one production VM or multiple production VMs. Specifically, the embodiment of the present application does not limit the number of production VMs in the production end.

[0074] The above-mentioned disaster recovery end includes a management device; the management device includes: management VM5 (i.e., management device) and disaster recovery VM; wherein, when no failure occurs on the production end, the management VM5 synchronizes the business data in the production volume included in the production end to the mirror volume in the above-mentioned management VM5, so that the mirror volume includes backup data of the business data in the production volume.

[0075] The management VM5 is also used to generate a snapshot data volume based on the mirror volume in the above management device when a failure occurs on the production end, the snapshot data volume includes a snapshot of the backup data in the mirror volume; and mount the snapshot data volume to the disaster recovery VM.

[0076] The above-mentioned disaster recovery VMs include disaster recovery VM3 and disaster recovery VM4; wherein, disaster recovery VM3 and disaster recovery VM4 are used to take over the business originally belonging to production VM1 and production VM2 in the production end in the event of a failure in the production end; that is, the above-mentioned disaster recovery VM3 and disaster recovery VM4 are disaster recovery devices in the disaster recovery end.

[0077] It should be noted that the above-mentioned disaster recovery VM3 and disaster recovery VM4 can be pre-created, or they can be generated by triggering the above-mentioned management VM5 when a failure occurs on the production side. The specific embodiments of the present application do not specifically limit them.

[0078] The management VM5 is used to set the data source of the disaster recovery VM3 and the disaster recovery VM4 to the snapshot data volume, so that the disaster recovery VM3 and the disaster recovery VM4 perform business processing based on the data in the snapshot data volume.

[0079] Management VM5 is also used to generate a business data volume based on the snapshot data volume when disaster recovery VM3 and disaster recovery VM4 use the snapshot data volume as the data source to process business; the business data volume includes the business data in the snapshot included in the snapshot data volume (that is, the business data volume includes the business data corresponding to the snapshot data in the snapshot data volume); and set the business data volume as the data source of the above-mentioned disaster recovery VM3 and disaster recovery VM4, so that disaster recovery VM3 and disaster recovery VM4 perform business processing based on the business data in the business data volume.

[0080] The data disaster recovery method provided in the embodiment of the present application can also be applied to Figure 3 In the management system shown, the management system includes: a production end and a disaster recovery end.

[0081] The above-mentioned production end includes production VM6 and production volumes. When there is no failure in the production end, production VM6 uses the production volume storing business data as the data source to process business; that is, production VM6 is a production device that processes business based on the production volume.

[0082] The above-mentioned disaster recovery end includes multiple disaster recovery integrated machines, the processing resources of the multiple disaster recovery integrated machines are virtualized into a virtualization layer, and the storage resources of the multiple disaster recovery integrated machines are virtualized into a storage layer.

[0083] It should be noted that the above-mentioned disaster recovery machine can be Figure 1 The management device in Figure 1 The disaster recovery device in the present application is not specifically limited in the embodiments.

[0084] The above-mentioned virtualization layer includes management VM7 (i.e., management device) and disaster recovery VM8, wherein the disaster recovery VM8 can be a VM created in advance in the virtualization layer, or it can be a VM created in the virtualization layer by the above-mentioned management VM7 when a failure occurs on the production end. The specific embodiments of the present application do not specifically limit it.

[0085] In the case that no failure occurs on the production side, the management VM7 is used to synchronize the service data in the production volume to the mirror volume in the storage layer, so that the mirror volume includes the backup data of the service data in the production volume.

[0086] In the event of a failure on the production side, management VM7 is used to generate a snapshot data volume based on the mirror volume thereon, and the snapshot data volume includes a snapshot of the backup data in the mirror volume; then, the snapshot data volume is determined as the data source of the above-mentioned disaster recovery VM8, so that the disaster recovery VM8 performs business processing based on the data in the snapshot data volume.

[0087] The management VM7 is also used to generate a business data volume based on the snapshot data volume when the disaster recovery VM8 uses the snapshot data volume as a data source to process the business, and set the business data volume as the data source of the disaster recovery VM8, so that the disaster recovery device carries the business before the production device fails based on the business data volume; the business data volume includes the business data in the snapshot included in the snapshot data volume; that is, the disaster recovery VM8 is a disaster recovery device that takes over the business on the production VM6 in the event of a production VM6 failure. .

[0088] For example, Figure 4 is the above Figure 1 or Figure 2 A schematic diagram of the hardware structure of a computing device of a management device in the embodiment of the present invention. Taking the computing device as a server as an example, the server can be a high-density server, a rack server or a whole cabinet server in terms of form; and can be a general-purpose server, a GPU (graphics processing unit) server, etc. or an artificial intelligence (AI) server in terms of performance.

[0089] The hardware part of the computing device includes a processor, an out-of-band controller and a memory, and the software part includes an out-of-band management module, processor firmware and an operating system (OS) management unit.

[0090] The out-of-band management module runs in the out-of-band controller, and the OS management unit runs on the processor (such as Figure 4 ), the processor firmware may be located within the processor (as shown in Figure 4 As shown). The out-of-band management module may be a management unit of a non-business module. For example, the out-of-band management module may remotely maintain and manage the computing device through a dedicated data channel. The out-of-band management module is completely independent of the operating system of the computing device and may communicate with the OS through the out-of-band management interface of the computing device.

[0091] Exemplarily, the out-of-band management module may include a management unit for the computing device operation mode, a management system in a management chip outside the processor, a computing device motherboard management unit (baseboard management controller, BMC), a system management module (system management mode, SMM), etc. It should be noted that the embodiments of the present application do not limit the specific form of the out-of-band management module, and the above is only an exemplary description. In the following embodiments, only the out-of-band management module is taken as an example for description.

[0092] Among them, the memory, also called internal memory or main memory, is installed in the memory slot on the motherboard of the computing device, and the memory communicates with the memory controller through a memory channel.

[0093] Optionally, the computing device further includes a hard disk ( Figure 4 Not shown), the hard disk is used to store the business data of the above-mentioned computing device, that is, the hard disk includes a data volume (such as a production volume or a mirror volume).

[0094] It should be noted that the system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0095] The present invention provides a data disaster recovery method for Figure 1 The management device shown, Figure 2 Management VM5 and Figure 3 The virtual management VM7 of the disaster recovery machine in the embodiment of the present application is used as an example for ease of description. Figure 1 The management device shown is used as an example for explanation and will not be further explained later.

[0096] The present application embodiment provides a data disaster recovery method, such as Figure 5 As shown, the method includes: S110-S130.

[0097] S110. In case of a production equipment failure, migrate the business on the production equipment to the disaster recovery equipment.

[0098] It should be noted that migrating the business on the production device to the disaster recovery device means switching the tasks originally performed by the production device to be performed by the disaster recovery device; that is, the disaster recovery device processes the business requests originally processed by the production device application.

[0099] The implementation method of migrating the business on the production device to the disaster recovery device in the above S110 may be to set the Internet Protocol (IP) address of the disaster recovery device to the same address as the IP address of the production device; then, start the disaster recovery device and shut down the production device, so that the business request sent by the business end to the IP address of the production device is successfully obtained by the disaster recovery device. It can also be to add a node corresponding to the disaster recovery device in the load balancing module and delete the node corresponding to the production device, so that the load balancing module will divert the business request to the disaster recovery device after receiving the business, which is not specifically limited in the embodiments of the present application.

[0100] S120 . Generate a business data volume based on the snapshot data volume of the production device.

[0101] It should be noted that, when there is no failure in the production equipment, the management equipment or the production equipment will back up the business data in the production equipment to obtain backup data; for example, the business data in the production volume on the production equipment is synchronized to the mirror volume in the management equipment; at this time, the mirror volume includes the backup data of the above business data; wherein, the production volume is the data source used by the production equipment to process business.

[0102] It should be understood that a service on a device is a task that the device needs to perform, such as a service may specifically be a service request; and service data is data required in the process of processing a service (eg, a service request).

[0103] The snapshot data volume is a snapshot volume generated when a production device fails and is used to store a snapshot of the backup data in the mirror volume; that is, the snapshot data volume includes a snapshot of the backup data of the business data used by the business on the production device.

[0104] The above-mentioned business data volume includes the business data in the snapshot in the above-mentioned snapshot data volume, that is, the business data volume includes the business data corresponding to the snapshot data in the above-mentioned snapshot data volume; that is, the business data volume stores the business data in the snapshot included in the above-mentioned snapshot data volume, not the snapshot in the snapshot data volume.

[0105] If there is a business data volume without data stored in the above-mentioned disaster recovery device, such as Figure 6 As shown, the implementation of the above S120 includes: S121-S122.

[0106] S121. Obtain the full amount of business data in the current snapshot data volume.

[0107] The full business data is all business data in the snapshot included in the snapshot data volume; that is, the full business data is business data corresponding to the full snapshot data in the snapshot data volume.

[0108] The implementation method of the above S121 includes: reading all business data in the snapshot included in the snapshot data volume, thereby obtaining the full amount of business data.

[0109] S122. Synchronize all business data to the business data volume.

[0110] The implementation method of the above S122 includes: writing the above full business data into the business data volume in the form of character stream or byte stream, so that the business data stored in the business data volume is the same as the full business data in the snapshot data volume.

[0111] In the case that there is no business data volume for storing data in the above-mentioned disaster recovery device, it is also necessary to create an empty (i.e., no data is stored) business data volume in the system where the disaster recovery device is located (i.e., the disaster recovery end) before the above-mentioned S120; wherein, the way of creating the business data volume can be to create a business data volume with the same properties and quantity as the production volume in the production device; or it can be to create a preset number and preset properties of business data volumes, which is not specifically limited in the specific embodiments of the present application.

[0112] It should be noted that the specific implementation of the above-mentioned creation of the business data volume having the same attributes and quantity as the production volume in the production device is referred to in the following S320, which will not be repeated here.

[0113] S130: Set the business data volume as the data source of the disaster recovery device, so that the disaster recovery device carries the business before the production device fails based on the business data volume.

[0114] The implementation method of setting the business data volume as the data source of the disaster recovery device in the above S130 can be to mount the business data volume to the system file of the disaster recovery device (such as: system file A), and configure the data source of the disaster recovery device as the business data volume in the system file A; or it can be to configure the data source address in the disaster recovery device as the absolute address of the above business data volume, so that the disaster recovery device can access the business data in the business data volume through the absolute address.

[0115] It should be understood that when the data source of the disaster recovery device is set to the above-mentioned business data volume, when the disaster recovery device receives a business, the disaster recovery device will process the business based on the business data in the business data volume; that is, the disaster recovery device carries the business before the production equipment fails based on the business data in the business data volume.

[0116] An embodiment of the present application provides a data disaster recovery method. In the event of a production device failure, the method migrates the business on the production device to the disaster recovery device, and generates a business data volume based on the snapshot data volume of the production device, wherein the snapshot data volume includes a snapshot of backup data of the business data used by the production device, and the business data volume is set as the data source of the disaster recovery device, so that the disaster recovery device carries the business before the production device failure based on the business data volume; since the business data volume includes the business data corresponding to the snapshot in the snapshot data volume, rather than the snapshot in the snapshot data volume, there is no restriction on data reading and writing for the business data volume, and since the above-mentioned disaster recovery device carries the business on the production device based on the business data volume, the data reading and writing capability of the disaster recovery device is improved.

[0117] based on Figure 5 or Figure 6 , the present application embodiment provides a specific implementation method, the method is as follows Figure 7 Shown include: S210-S240.

[0118] S210. In case of a production equipment failure, migrate the business on the production equipment to the disaster recovery equipment.

[0119] It should be noted that the implementation method of the above S210 is consistent with the implementation method of S110. For the specific description of S210, please refer to the above related description of S110, which will not be repeated here.

[0120] S220: Set the snapshot data volume as the data source of the disaster recovery device.

[0121] The implementation method of setting the snapshot data volume as the data source of the disaster recovery device in the above S220 can be to mount the snapshot data volume to the system file of the disaster recovery device (such as: system file A), and configure the data source of the disaster recovery device as the snapshot data volume in the system file A; or it can be to configure the data source address in the disaster recovery device as the absolute address of the above snapshot data volume, so that the disaster recovery device accesses the data in the snapshot data volume through the absolute address.

[0122] It should be understood that when the data source of the disaster recovery device is set to the above-mentioned snapshot data volume, when the disaster recovery device receives a service, the disaster recovery device will carry the service based on the snapshot data volume; that is, the disaster recovery device will process the service based on the data in the snapshot data volume.

[0123] S230. In the process of the disaster recovery device carrying the service based on the snapshot data volume, generate a service data volume based on the snapshot data volume.

[0124] It should be noted that the implementation method of the above S230 is similar to the implementation method of S120. For the specific description of S230, please refer to the above related description of S120, which will not be repeated here.

[0125] S240: Set the business data volume as the data source of the disaster recovery device.

[0126] The above-mentioned S240 can be implemented by unmounting the snapshot data volume in the system file (such as: system file A) mounted on the disaster recovery device, wherein the system file A is the data source for the disaster recovery device to process business; then, mounting the above-mentioned business data volume in the system file A; or updating the absolute address of the above-mentioned snapshot data volume configured by the data source of the disaster recovery device to the absolute address of the above-mentioned business data volume, so that the disaster recovery device can operate on the data in the business data volume by accessing the absolute address.

[0127] An embodiment of the present application provides a data disaster recovery method, which, in the event of a production device failure, migrates the business on the production device to the disaster recovery device, and sets the snapshot data volume as the data source of the disaster recovery device, so as to achieve rapid takeover of the production device; wherein the snapshot data volume includes a snapshot of the backup data, and the backup data is a backup of the business data on the above-mentioned production device. In the process of the disaster recovery device carrying the above-mentioned business based on the snapshot data volume, a business data volume is generated based on the snapshot data volume, and the business data volume is set as the data source of the disaster recovery device; the business data volume includes the business data in the snapshot in the snapshot data volume. Since the data in the business data volume is business data, not a snapshot of business data, there is no restriction on data reading and writing, thereby improving the efficiency of the disaster recovery device in processing business; therefore, the above method not only realizes the rapid takeover of the production system by the disaster recovery system, but also ensures the data reading and writing capabilities of the disaster recovery system.

[0128] It should be noted that after the above S220, since the disaster recovery device carries the business based on the snapshot data volume, the data in the snapshot data volume will change with the business, that is, the data in the snapshot data volume will generate incremental data as the business is processed. In the above S230 and S120, the full amount of business data in the current snapshot data volume is synchronized to the business data volume. However, in the process of synchronizing the above full amount of business data to the above business data volume, new incremental data may be generated in the snapshot data volume, so that after the above full amount of business data is synchronized, due to the generation of new incremental data in the snapshot data volume, the data in the snapshot data volume is inconsistent with the data in the above business data volume. Therefore, there is a problem of business data loss.

[0129] Based on this, combined Figure 5 , Figure 6 or Figure 7, the embodiment of the present application provides a specific implementation, such as Figure 8 As shown, the method includes: S310-S360.

[0130] S310: In the event of a production device failure, migrate the business on the production device to the disaster recovery device, and set the snapshot data volume as the data source of the disaster recovery device.

[0131] It should be noted that the above-mentioned implementation method of S310 is consistent with the above-mentioned implementation method of S210-S220. For the specific description of S310, please refer to the above-mentioned related description of S210-S220, which will not be repeated here.

[0132] S320. In the system where the disaster recovery device is located, create a business data volume that has the same properties and quantity as the production volume used by the production device to store business data and does not contain any data.

[0133] The above-mentioned properties of the production volume include: property information such as the size of the production volume and / or the identification (such as name) of the production volume.

[0134] The implementation method of the above S320 includes: obtaining the number of production volumes on the production equipment and the attributes of each production volume; then, based on the attributes and number of the above production volumes, creating data volumes with the same number and attributes as the above business data volumes in the system where the disaster recovery equipment is located (ie: the disaster recovery end).

[0135] For example, assume that the production volumes on the production device include: a first production volume and a second production volume, wherein the first production volume is named "Data Volume A" and has a size of 500G; the second production volume is named "Data Volume B" and has a size of 800G; then, based on the number of production volumes and the attributes of each production volume, a first business data volume and a second business data volume are created in the system where the disaster recovery device is located, wherein the first business data volume is named "Data Volume A" and has a size of 500G; the second business data volume is named "Data Volume B" and has a size of 800G.

[0136] S330: Synchronize the full amount of business data in the snapshot data volume to the business data volume.

[0137] It should be noted that the number of the above-mentioned snapshot data volumes is the same as the number of production volumes on the production equipment, and each production volume corresponds to a snapshot data volume; wherein, the data in the snapshot data volume A corresponding to the production volume A is a snapshot of the backup data of the production volume A; that is, the business data in the production volume A and the business data in the snapshot in the snapshot data volume A corresponding to it (in short: the business data in the snapshot data volume A) are the same.

[0138] Based on this, in the case where the snapshot data volume includes the first snapshot data volume and the second snapshot data volume, the implementation method of S330 includes: S330A-S330B.

[0139] S330A: Synchronize the business data in the first snapshot included in the first snapshot data volume to the first business data volume.

[0140] The above-mentioned first snapshot is a snapshot of the backup data of the production volume with the same attributes as the above-mentioned first business data volume; that is, the above-mentioned first snapshot data volume includes a snapshot of the backup data of the production volume (such as: the first production volume) with the same attributes as the first business data volume; wherein, the above-mentioned first business data volume is a business data volume generated based on the attributes of the above-mentioned first production volume.

[0141] Based on this, the implementation method of the above S330A is to synchronize the business data in the first snapshot data volume (i.e., the business data in the above first snapshot) to the business data volume with the same attributes as the first production volume corresponding to the first snapshot data volume; wherein, the synchronization method of the business data refers to the above S121-S122 and will not be repeated here.

[0142] Exemplarily, based on the example in S320 above, assuming that the production volume corresponding to the first snapshot data volume is the first production volume above, that is, the data in the first snapshot data volume is a snapshot of the backup data of the first production volume above; then, S330A above is to synchronize the business data in the snapshot in the first snapshot data volume to the first business data volume named "Data Volume A" and with a size of 500G.

[0143] S330B: Synchronize the business data in the second snapshot included in the second snapshot data volume to the second business data volume.

[0144] The second snapshot is a snapshot of the backup data of the production volume having the same attributes as the second business data volume;

[0145] It should be noted that the implementation method of the above S330B is similar to the implementation method of the above S330A. For the specific description of S330B, please refer to the above related description of S330A, which will not be repeated here.

[0146] In the above embodiment, in the system where the disaster recovery device is located, after creating a business data volume (including: a first business data volume and a second business data volume) with the same attributes and quantity as the production volume used by the production device to store business data, the business data in the first snapshot included in the first snapshot data volume is synchronized to the first business data volume, and the business data in the second snapshot included in the second snapshot data volume is synchronized to the second business data volume; since the first snapshot is a snapshot of the backup data of the production volume with the same attributes as the above-mentioned first business data volume, and the second snapshot is a snapshot of the backup data of the production volume with the same attributes as the above-mentioned second business data volume; it can be seen that the above is to store the business data in the snapshot data volume in a distributed storage manner, which improves the reading and writing efficiency of the data in the business data volume compared to the method of centrally storing all data in all snapshot data volumes in one business data volume.

[0147] S340: Obtain the first incremental data in the snapshot data volume.

[0148] The first incremental data is the business data corresponding to the differential snapshot data that changed in the snapshot included in the snapshot data volume during the last synchronization to the business data volume. That is to say, the first incremental data is the business data corresponding to the differential snapshot data that changed in the snapshot included in the snapshot data volume during the last synchronization of the data in the snapshot data volume (such as: full business data) to the business data volume (such as: executing the above S330).

[0149] The above-mentioned S340 can be implemented by determining the business data that differs between the snapshot data volume and the business data volume as the first incremental data, and reading the first incremental data from the snapshot data volume; or by determining the difference data between the data in the current snapshot data volume and the data in the snapshot data volume when the data in the snapshot data volume was last synchronized as the first incremental data, and reading the first incremental data from the current snapshot data volume.

[0150] Exemplarily, assuming that the snapshot data volume includes data A and data B, and during the process of synchronizing data A and data B in the snapshot data volume to the business data volume, data C is newly added to the snapshot data volume. Then, the first incremental data is data C at this time.

[0151] S350: Synchronize the first incremental data to the business data volume.

[0152] It should be noted that the implementation method of the above S350 is similar to the implementation method of the above S122. For the specific description of S350, please refer to the above related description of S122, which will not be repeated here.

[0153] It should be understood that, when the snapshot data volume includes a first snapshot data volume and a second snapshot data volume, the implementation method of the above S350 is to synchronize the first incremental data in the first snapshot data volume to the first business data volume; and synchronize the first incremental data in the second snapshot data volume to the second business data volume.

[0154] S360. Set the business data volume as the data source of the disaster recovery device.

[0155] It should be noted that the implementation method of the above S360 is similar to the implementation method of the above S240. For the specific description of S360, please refer to the above related description of S240, which will not be repeated here.

[0156] The embodiment of the present application provides a data disaster recovery method, which, in the event of a production device failure, migrates the business on the production device to the disaster recovery device, and sets the snapshot data volume as the data source of the disaster recovery device, so as to realize the rapid takeover of the production device by the disaster recovery device; wherein the snapshot data volume includes a snapshot of the backup data, and the backup data is a backup of the business data on the production device. In the process of the disaster recovery device carrying the above-mentioned business based on the snapshot data volume, the full business data and the first incremental data in the snapshot data volume are synchronized to the business data volume, and the business data volume is set as the data source of the disaster recovery device. Since the data in the business data volume is business data, not a snapshot of business data, there is no restriction on data reading and writing, thereby improving the efficiency of the disaster recovery device in processing business; therefore, the above method not only realizes the rapid takeover of the production system by the disaster recovery system, but also ensures the data reading and writing capability of the disaster recovery system.

[0157] In addition, in the above-mentioned embodiment, during the process of the disaster recovery device carrying the above-mentioned business based on the snapshot data volume, not only the full business data in the snapshot data volume is synchronized to the business data volume; the first incremental data in the snapshot data volume is also synchronized to the business data volume; because the first incremental data is the business data corresponding to the differential snapshot data that has changed in the snapshot included in the snapshot data volume during the last synchronization to the business data volume; thereby, the inconsistency between the data in the snapshot data volume and the data in the above-mentioned business data volume is avoided to a certain extent, and then, the problem of business data loss is solved to a certain extent.

[0158] based on Figure 8 The data disaster recovery method shown in the embodiment of the present application provides another implementation method, which is a specific implementation of the above S350-S360, such as Fig. 9 Shown include: S410-S430.

[0159] S410: Determine whether the data volume of the first incremental data is greater than a preset data volume.

[0160] When the data volume of the first incremental data is greater than the preset data volume, the following S420 is executed.

[0161] When the data amount of the first incremental data is less than or equal to the preset data amount, the following S430 is executed.

[0162] S420. Synchronize the first incremental data to the business data volume.

[0163] The implementation method of the above S420 is similar to the implementation method of the above S350. For the specific description of S420, please refer to the above related description of S350, which will not be repeated here.

[0164] It should be noted that after the above S420, the above S340 is executed to obtain the incremental data generated in the snapshot data volume during the process of synchronizing the first incremental data to the business data volume, and this process is repeated until the amount of the incremental data is less than or equal to the preset data amount.

[0165] S430: Set the business data volume as the data source of the disaster recovery device.

[0166] The implementation of the above S430 is as follows Fig.10 As shown, including: S431-S434.

[0167] S431. Shut down the disaster recovery device.

[0168] The implementation of the above S431 includes: controlling the disaster recovery device to trigger a shutdown instruction so that the disaster recovery device executes a shutdown action. For its specific implementation, refer to the relevant technology and will not be repeated here.

[0169] S432: When the disaster recovery device is in a shutdown state, synchronize the first incremental data to the business data volume.

[0170] The implementation method of the above S432 includes: reading the above first incremental data from the snapshot data volume, and writing the first incremental data into the above business data volume.

[0171] S433: Switch the data source of the business of the disaster recovery device from the snapshot data volume to the business data volume.

[0172] The implementation method of the above S433 is consistent with the implementation method of the above S240. For the specific description of S433, please refer to the above related description of S240, which will not be repeated here.

[0173] S434. Start the disaster recovery device.

[0174] The implementation of S434 includes: controlling the disaster recovery device to trigger a startup instruction so that the disaster recovery device executes a startup action.

[0175] In the above embodiment, when the data amount of the first incremental data is less than or equal to the preset data amount, the disaster recovery device is shut down so that the data in the snapshot data volume serving as the data source of the disaster recovery device will no longer change; and when the disaster recovery device is in a shutdown state, the first incremental data is synchronized to the business data volume so that the business data in the business data volume is the same as the business data in the snapshot data volume, thereby avoiding the problem of inconsistency between the data in the snapshot data volume and the data in the above business data volume, and therefore solving the problem of business data loss.

[0176] In addition, when the data volume of the first incremental data is greater than the preset data volume, the first incremental data is synchronized to the business data volume, thereby avoiding the problem of taking too much time to synchronize the first incremental data when the disaster recovery device is in a shutdown state.

[0177] based on Fig. 9 , the present application embodiment provides another specific implementation of the above S350-S360, such as Fig.11 Shown include: S510-S550.

[0178] S510: Determine whether the data volume of the first incremental data is greater than a preset data volume.

[0179] When the data volume of the first incremental data is greater than the preset data volume, the following S520 is executed.

[0180] When the data amount of the first incremental data is less than or equal to the preset data amount, the following S530 is executed.

[0181] S520: Synchronize the first incremental data to the business data volume.

[0182] It should be noted that the implementation method of the above S520 is similar to the implementation method of the above S420. For the specific description of S520, please refer to the above related description of S420, which will not be repeated here.

[0183] S530: Monitor whether the snapshot data volume generates second incremental data within a preset time period.

[0184] The implementation method of the above S530 includes: periodically detecting whether the second incremental data is generated in the snapshot data volume within a preset time period.

[0185] It should be noted that the above method for determining whether to generate the second incremental data is similar to the implementation method of the above S340. For the specific description of the above method for determining whether to generate the second incremental data, please refer to the above description of S340, which will not be repeated here.

[0186] Exemplarily, assuming that the preset duration is 30 seconds, and assuming that each monitoring cycle is 10 seconds, the management device interrupts the current process, and during the interruption, monitors whether the snapshot data volume generates the second incremental data for three consecutive cycles.

[0187] When the snapshot data volume generates second incremental data within the preset time period, the following S540 is executed.

[0188] When the snapshot data volume does not generate the second incremental data within the preset time period, the following S550 is executed.

[0189] S540: Synchronize the first incremental data and the second incremental data to the business data volume.

[0190] The implementation method of the above S540 is similar to the implementation method of the above S350. For the specific description of S540, please refer to the above related description of S350, which will not be repeated here.

[0191] It should be noted that after the above S540, the above S340 is executed to obtain the incremental data generated in the snapshot data volume during the process of synchronizing the first incremental data and the second incremental data to the business data volume, and repeat this process until the above snapshot data volume does not generate the second incremental data within the preset time length.

[0192] S550: Set the business data volume as the data source of the disaster recovery device.

[0193] It should be noted that the implementation method of the above S550 is similar to the implementation method of the above S430. For the specific description of S550, please refer to the above related description of S430, which will not be repeated here.

[0194] After synchronizing the full amount of business data in the snapshot data volume to the business data volume, the above embodiment obtains the business data (i.e., the first incremental data) corresponding to the differential snapshot data that has changed in the snapshot data volume during the synchronization of the full amount of business data; and when the first incremental data is less than or equal to the preset data volume, and the snapshot data volume does not have the second incremental data within the preset time period, the disaster recovery device is shut down, the first incremental data is synchronized to the business data volume, and the data source of the business of the disaster recovery device is switched from the snapshot data volume to the business data volume; then, the disaster recovery device is started so that the disaster recovery device processes the business based on the business data in the business data volume. Since the data in the above business data volume is business data, not a snapshot of business data, there is no restriction on data reading and writing, thereby improving the efficiency of the disaster recovery device in processing business; therefore, the above method not only realizes the rapid takeover of the production system by the disaster recovery system, but also ensures the data reading and writing capability of the disaster recovery system.

[0195] based on Figure 7or Figure 8 The data disaster recovery method shown in the present application embodiment provides another implementation method, such as Fig.12 The method shown in the figure further includes: S610-S620 before S230 and after S220.

[0196] S610: Obtain disaster recovery status.

[0197] The above disaster recovery status includes an open state or a closed state.

[0198] It should be noted that the implementation method of the above S610 can be to obtain the disaster recovery status from a management device, or to obtain the disaster recovery status from a disaster recovery device, which is not specifically limited in the embodiments of the present application.

[0199] S620: Determine whether the disaster recovery state is enabled.

[0200] When the disaster recovery state is in the on state, the above S230 is executed.

[0201] When the disaster recovery state is closed, an end action is executed to end the current method flow.

[0202] In the above embodiment, the method controls the disaster recovery device to use the snapshot in the snapshot data volume as the data source and take over the business on the production device in the case of a production device failure; at the same time, when the disaster recovery state is turned on, a business data volume is generated based on the snapshot data volume, and the business data volume is set as the data source of the business on the disaster recovery device. Since the above method generates the business data volume when the disaster recovery state is turned on, and controls the disaster recovery device to carry the business based on the data in the business data volume; it can be seen that by setting the above disaster recovery state, the disaster recovery device can control whether to execute the above action of generating the above business data volume, thereby improving the flexibility of the above data disaster recovery method.

[0203] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. In order to realize the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0204] The embodiment of the present application can divide the functional modules of the data disaster recovery device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0205] In the case of dividing each functional module into corresponding functional modules, Fig.13 A possible structural diagram of the data disaster recovery device involved in the above embodiment is shown. Fig.13 As shown, the data disaster recovery device includes: a setting module 1301 and a generating module 1302.

[0206] The setting module 1301 is used to migrate the business on the production device to the disaster recovery device when the production device fails; for example, execute step S110 in the above method embodiment.

[0207] The generating module 1302 is used to generate a service data volume based on the snapshot data volume of the production device; for example, executing step S120 in the above method embodiment.

[0208] The setting module 1301 is used to set the business data volume as the data source of the disaster recovery device, so that the disaster recovery device carries the business before the production device fails based on the business data volume; for example, executing step S130 in the above method embodiment.

[0209] Optionally, the setting module 1301 is used to set the snapshot data volume as the data source of the disaster recovery device; for example, executing step S220 or S310 in the above method embodiment.

[0210] Optionally, the data disaster recovery device further includes: a transceiver module 1303 and a synchronization module 1304 .

[0211] The transceiver module 1303 is used to obtain the full amount of business data in the current snapshot data volume; for example, execute step S121 in the above method embodiment.

[0212] The synchronization module 1304 is used to synchronize the full amount of business data to the business data volume; for example, executing step S122 in the above method embodiment.

[0213] Optionally, the transceiver module 1303 is used to obtain the first incremental data in the snapshot data volume; for example, executing step S340 in the above method embodiment.

[0214] The synchronization module 1304 is used to synchronize the first incremental data to the business data volume; for example, executing step S350 in the above method embodiment.

[0215] Optionally, the setting module 1301 is used to set the business data volume as the data source of the disaster recovery device when the data volume of the first incremental data is less than or equal to the preset data volume; for example, execute step S430 in the above method embodiment.

[0216] Optionally, the setting module 1301 is used to perform a shutdown operation on the disaster recovery device; for example, execute step S431 in the above method embodiment.

[0217] The synchronization module 1304 is used to synchronize the first incremental data to the business data volume when the disaster recovery device is in a shutdown state; for example, executing step S432 in the above method embodiment.

[0218] The setting module 1301 is used to switch the data source of the service of the disaster recovery device from the snapshot data volume to the service data volume; for example, executing step S433 in the above method embodiment.

[0219] The setting module 1301 is used to start the disaster recovery device; for example, to execute step S434 in the above method embodiment.

[0220] Optionally, the transceiver module 1303 is used to monitor whether the snapshot data volume generates second incremental data within a preset time period; for example, executing step S530 in the above method embodiment.

[0221] The setting module 1301 is used to set the business data volume as the data source of the disaster recovery device when no second incremental data is generated within a preset time period; for example, executing step S550 in the above method embodiment.

[0222] Optionally, the setting module 1301 is used to create a business data volume that has the same properties and quantity as the production volume used by the production device to store business data and does not contain data in the system where the disaster recovery device is located; for example, execute step S320 in the above method embodiment.

[0223] The synchronization module 1304 is used to synchronize the business data in the first snapshot included in the first snapshot data volume to the first business data volume; for example, executing step S330A in the above method embodiment.

[0224] The synchronization module 1304 is used to synchronize the business data in the second snapshot included in the second snapshot data volume to the second business data volume; for example, executing step S330B in the above method embodiment.

[0225] Optionally, the transceiver module 1303 is used to obtain the disaster recovery status; for example, executing step S610 in the above method embodiment.

[0226] The generation module 1302 is used to generate a business data volume based on the snapshot data volume when the disaster recovery state is in the on state; for example, execute step S230 in the above method embodiment.

[0227] Each module of the above data disaster recovery device can also be used to execute other actions in the above method embodiment. All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0228] An embodiment of the present application also provides a computing device, including a memory and a processor, wherein the memory is coupled to the processor; the memory is used to store computer program code, and the computer program code includes computer instructions, which, when executed by the processor, implement any one of the methods executed by the above-mentioned management device.

[0229] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored. When the computer instructions are executed on a computing device, the computing device executes any one of the methods executed by the above-mentioned processor.

[0230] For the explanation of the relevant contents and description of the beneficial effects of any of the above-mentioned computer-readable storage media, reference may be made to the above-mentioned corresponding embodiments, which will not be repeated here.

[0231] An embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute any one of the methods executed by the processor described above.

[0232] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instruction is loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) mode or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a magnetic disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state drive (SSD)).

[0233] Through the description of the above implementation methods, technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0234] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

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

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

[0237] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art, or all or part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, disk or optical disk, and other media that can store program codes.

[0238] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A data disaster recovery method, characterized in that: The method comprises: In the event of a production device failure, the business on the production device is migrated to a disaster recovery device, and a business data volume is generated based on the snapshot data volume of the production device, wherein the snapshot data volume includes a snapshot of backup data of the business data used by the business on the production device, and the business data volume includes the business data corresponding to the snapshot; The business data volume is set as a data source of the disaster recovery device, so that the disaster recovery device carries the business before the production device fails based on the business data volume.

2. The method according to claim 1, characterized in that Before generating the service data volume based on the snapshot data volume of the production device, the method further includes: The snapshot data volume is set as the data source of the disaster recovery device.

3. The method according to claim 1 or 2, characterized in that: The generating of the service data volume based on the snapshot data volume of the production device includes: Obtaining the full amount of business data in the current snapshot data volume; Synchronize the full amount of business data to the business data volume.

4. The method according to claim 3, characterized in that Also includes: Acquire first incremental data in the snapshot data volume; The first incremental data is business data corresponding to differential snapshot data that has changed in the snapshot included in the snapshot data volume during the last synchronization to the business data volume; Synchronize the first incremental data to the business data volume.

5. The method according to claim 4, characterized in that The method further comprises: setting the business data volume as a data source of a disaster recovery device; When the data volume of the first incremental data is less than or equal to the preset data volume, the business data volume is set as the data source of the disaster recovery device.

6. The method according to claim 5, characterized in that The step of setting the business data volume as the data source of the disaster recovery device includes: Performing a shutdown operation on the disaster recovery device; When the disaster recovery device is in a shutdown state, synchronizing the first incremental data to the business data volume; Switching the data source of the service of the disaster recovery device from the snapshot data volume to the service data volume; Start the disaster recovery device.

7. The method according to claim 4, characterized in that Before setting the business data volume as the data source of the disaster recovery device, the method further includes: Monitoring whether the snapshot data volume generates second incremental data within a preset time period; The step of setting the business data volume as the data source of the disaster recovery device includes: When the second incremental data is not generated within the preset time period, the business data volume is set as the data source of the disaster recovery device.

8. The method according to any one of claims 1 to 7, characterized in that: Before generating a service data volume based on the snapshot data volume of the production device, the method includes: In the system where the disaster recovery device is located, creating a business data volume that has the same attributes and quantity as the production volume of the production device for storing business data and does not contain data, wherein the business data volume includes a first business data volume and a second business data volume; The generating of the service data volume based on the snapshot data volume includes: Synchronize the business data in the first snapshot included in the first snapshot data volume to the first business data volume; wherein the snapshot data volume includes: the first snapshot data volume and the second snapshot data volume; the first snapshot is a snapshot of the backup data of the production volume with the same attributes as the first business data volume; The business data in the second snapshot included in the second snapshot data volume is synchronized to the second business data volume; wherein the second snapshot is a snapshot of the backup data of the production volume having the same attributes as the second business data volume.

9. The method according to any one of claims 1 to 8, characterized in that: The generating of the business data volume based on the snapshot data volume of the production device comprises: Obtaining a disaster recovery state, wherein the disaster recovery state includes: an open state or a closed state; When the disaster recovery state is in an on state, the business data volume is generated based on the snapshot data volume.

10. A computing device, characterized in that It comprises a memory and a processor, the memory is coupled to the processor; the memory is used to store computer program code, the computer program code comprises computer instructions; when the computer instructions are executed by the processor, the processor executes the method as described in any one of claims 1 to 9.

Images