Data transmission methods, devices, electronic equipment and media

Abstract

This specification provides a data transmission method, apparatus, electronic device, and medium. The method includes: in memory mode, if the detected memory usage rate is greater than or equal to a first usage rate threshold, switching from memory mode to bitmap mode; in bitmap mode, generating a bitmap based on logical block address change information corresponding to the target data in response to a write request for target data; sending the bitmap to a disaster recovery system; receiving a difference data retrieval request from the disaster recovery system; and sending the target data corresponding to the difference data retrieval request to the disaster recovery system.

Description

Technical Field

[0001] This specification relates to the field of big data technology, and in particular to data transmission methods, devices, electronic equipment and media. Background Technology

[0002] As enterprises accelerate their digital transformation, business systems are increasingly demanding higher levels of data security and business continuity. Continuous Data Protection (CDP) is a storage technology that captures data changes in real time and enables recovery at any point in time. It eliminates the "backup window" limitation of traditional backups, providing a higher level of data security. Data generated by business systems can be synchronized to disaster recovery systems in real time through CDP technology to protect data security.

[0003] Therefore, how to synchronize data from the business system to the remote disaster recovery system has become an urgent problem to be solved. Summary of the Invention

[0004] To overcome the problems existing in related technologies, this specification provides data transmission methods, devices, electronic devices, and media.

[0005] According to a first aspect of the embodiments of this specification, a data transmission method is provided, the method comprising: in a memory mode, if a memory utilization rate is detected to be greater than or equal to a first utilization rate threshold, switching from memory mode to bitmap mode; in bitmap mode, generating a bitmap based on logical block address change information corresponding to the target data in response to a write request for target data; sending the bitmap to a disaster recovery system; receiving a difference data acquisition request sent by the disaster recovery system; and sending the target data corresponding to the difference data acquisition request to the disaster recovery system.

[0006] According to a second aspect of the embodiments of this specification, a data transmission method is provided, the method comprising: receiving a bitmap sent by a business system, the bitmap being used to indicate logical block address change information, the bitmap being sent by the business system when memory usage is greater than or equal to a usage threshold; sending a difference data acquisition request to the business system based on the logical block address change information; and receiving target data corresponding to the difference data acquisition request sent by the business system.

[0007] According to a third aspect of the embodiments of this specification, a data transmission apparatus is provided, comprising: a first switching module, configured to switch from memory mode to bitmap mode when the memory usage rate is detected to be greater than or equal to a first usage rate threshold while in memory mode; a bitmap generation module, configured to generate a bitmap based on logical block address change information corresponding to the target data in response to a write request for target data while in bitmap mode; a bitmap sending module, configured to send the bitmap to a disaster recovery system; an acquisition request receiving module, configured to receive a difference data acquisition request sent by the disaster recovery system; and a first data sending module, configured to send target data corresponding to the difference data acquisition request to the disaster recovery system.

[0008] According to a fourth aspect of the embodiments of this specification, a data transmission apparatus is provided, comprising: a bitmap receiving module, configured to receive a bitmap sent by a business system, the bitmap being used to indicate logical block address change information, the bitmap being sent by the business system when memory usage is greater than or equal to a usage threshold; an acquisition request sending module, configured to send a difference data acquisition request to the business system based on the logical block address change information; and a first data receiving module, configured to receive target data sent by the business system corresponding to the difference data acquisition request.

[0009] According to a fifth aspect of the embodiments of this specification, an electronic device is provided, comprising: processor; Memory used to store processor-executable instructions; The processor is configured to execute the data transmission method of the first aspect, the second aspect, or any corresponding embodiment thereof.

[0010] According to a sixth aspect of the embodiments of this specification, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, the computer instructions being configured to cause a computer to perform the data transmission method of the first aspect, the second aspect, or any corresponding embodiment thereof described above.

[0011] The technical solutions provided in the embodiments of this specification may include the following beneficial effects: In the embodiments described in this specification, when in bitmap mode, the business system can generate a bitmap based on the logical block address change information corresponding to the target data in response to a write request for the target data, and send it to the disaster recovery system. The disaster recovery system can then request the target data corresponding to the logical block address information from the business system based on the bitmap. This enables data synchronization between the business system and the disaster recovery system.

[0012] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this specification. Attached Figure Description

[0013] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this specification and, together with the description, serve to explain the principles of this specification.

[0014] Figure 1 This is a flowchart illustrating a data transmission method according to an exemplary embodiment of this specification.

[0015] Figure 2 This is a schematic diagram of a system architecture illustrated in this specification according to an exemplary embodiment.

[0016] Figure 3 This is a schematic diagram illustrating a biof SDK module according to another exemplary embodiment of this specification.

[0017] Figure 4 This is a hardware structure diagram of a computer device containing the data transmission device in an embodiment of this specification.

[0018] Figure 5 This is a block diagram illustrating a data transmission apparatus according to an exemplary embodiment of this specification.

[0019] Figure 6 This is a block diagram illustrating another data transmission apparatus according to an exemplary embodiment of this specification. Detailed Implementation

[0020] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.

[0021] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0022] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0023] The embodiments described in this specification will now be described in detail.

[0024] The data transmission method provided in the embodiments of this specification will be described in detail below. For example... Figure 1 As shown, Figure 1 This is a flowchart illustrating a data transmission method according to an exemplary embodiment of this specification. The data transmission method provided in the embodiments of this specification may include the following steps.

[0025] In step 110, if the business system detects that the memory usage rate is greater than or equal to the first usage rate threshold when it is in memory mode, it switches from memory mode to bitmap mode.

[0026] According to embodiments of this specification, the business system can be any system with data processing capabilities, such as data aggregation, cleaning, and analysis. For example, the business system can be a data analysis system, a risk control system, or a reporting system.

[0027] According to the embodiments in this specification, the business system can be connected to a corresponding disaster recovery system. The disaster recovery system is a critical infrastructure for ensuring data security and business continuity. It can be used to respond to emergencies such as natural disasters, hardware failures, and network attacks, ensuring rapid recovery of data and services after system interruption.

[0028] According to embodiments of this specification, the operating modes for a business system to transmit data to a disaster recovery system may include memory mode and bitmap mode. For a write request for target data, if in memory mode, the target data is copied to memory, and then the data in memory is sent to the disaster recovery system. If in bitmap mode, the bitmap corresponding to the target data is sent directly to the disaster recovery system.

[0029] According to the embodiments of this specification, the first usage rate threshold can be set according to actual needs, such as 90%.

[0030] In step 120, when the business system is in bitmap mode, it generates a bitmap based on the logical block address change information corresponding to the target data in response to the write request for the target data.

[0031] According to the embodiments of this specification, after the target data is written, the corresponding logical block address (LBA) change location can be recorded to obtain logical block address change information. A bitmap can be used to indicate this logical block address change information.

[0032] In step 130, the business system sends the bitmap to the disaster recovery system.

[0033] In step 140, after the disaster recovery system receives the bitmap sent by the business system, it sends a request to obtain the difference data to the business system based on the logical block address change information.

[0034] According to the embodiments of this specification, the disaster recovery system can obtain logical block address change information by parsing the bitmap.

[0035] According to embodiments of this specification, a difference data retrieval request can be used to request target data corresponding to logical block address change information. The disaster recovery system can send the corresponding difference data retrieval request immediately upon receiving the bitmap, or it can wait at any time before sending the request.

[0036] In step 150, after the business system receives the difference data acquisition request sent by the disaster recovery system, it sends the target data corresponding to the difference data acquisition request to the disaster recovery system.

[0037] According to the embodiments in this specification, the business system can obtain target data corresponding to the logical block address information based on the difference data acquisition request, and send it to the disaster recovery system. This enables data synchronization between the business system and the disaster recovery system.

[0038] According to the embodiments of this specification, after the disaster recovery system receives the target data corresponding to the difference data acquisition request sent by the business system, it can use the target data to perform disaster recovery operations such as data recovery.

[0039] According to the embodiments of this specification, generating a difference data acquisition request through a bitmap and acquiring the target data based on the difference data acquisition request can ensure data consistency between the disaster recovery system and the business system and avoid data loss.

[0040] Optionally, if the business system detects that the memory usage rate is less than the second usage rate threshold while it is in bitmap mode, it can switch from bitmap mode to memory mode.

[0041] According to the embodiments of this specification, the second usage rate threshold can be set according to actual needs, such as 30%.

[0042] Optionally, the business system can also send a notification to the disaster recovery system each time the mode switching conditions are met. For example, in memory mode, if the business system detects that the memory usage is greater than or equal to a first usage threshold, it can send a bitmap mode switching notification to the disaster recovery system to inform it that it has switched to bitmap mode. Upon receiving the bitmap mode switching notification, the disaster recovery system can determine that the business system is in bitmap mode. Once it determines that the business system is in bitmap mode, it receives the bitmap sent by the business system and, based on the logical block address change information represented by the bitmap, sends a difference data retrieval request to the business system.

[0043] If memory utilization falls below the second utilization threshold, a memory mode switch notification is sent to the disaster recovery system. Upon receiving the notification, the disaster recovery system determines that the business system has switched to memory mode. Once the business system is confirmed to be in bitmap mode, the system receives the data from the business system's memory.

[0044] According to the embodiments in this specification, the business system can proactively notify the disaster recovery system to switch its working mode, which can prevent data loss due to misjudgment by the disaster recovery system.

[0045] Optionally, the business system can notify the disaster recovery system of the working mode switch via event callbacks. Using event callbacks avoids polling and reduces CPU usage.

[0046] Optionally, after receiving the bitmap sent by the business system, the disaster recovery system can wait until it is idle to acquire the corresponding target data. For example, after receiving the bitmap from the business system, the disaster recovery system can monitor the computing resource utilization rate. If the computing resource utilization rate is less than a utilization rate threshold, it can send a request to the business system to acquire the difference data based on the logical block address change information. The utilization rate threshold can be set according to actual needs. Computing resource utilization rate may include, for example, CPU (Central Processing Unit) utilization rate, memory utilization rate, port utilization rate, etc.

[0047] Optionally, the business system can send target data and bitmaps to the disaster recovery system via an encrypted channel. The disaster recovery system can send a difference data retrieval request to the business system via the reverse channel of the encrypted channel. The encrypted channel may, for example, include an xnet (eXtensible Network Protocol) channel. The encrypted channel can support authentication and access control.

[0048] Optionally, the business system may include an I / O filter, and the disaster recovery system may include a biof (Block I / O Filter) SDK (Software Development Kit). Based on this, the filter module can intercept write requests and process the target data corresponding to the write requests according to different working modes. The biof SDK can act as middleware to uniformly manage the data interaction between the I / O filter and the disaster recovery system. The biof SDK may include a standardized set of interfaces that the disaster recovery system can call to receive I / O data. When the working mode of the business system switches, the interfaces provided by the biof SDK can be used to notify the disaster recovery system of the switched working mode through event callbacks. The I / O filter can, for example, be deployed in the I / O path of a virtualization platform. Virtualization platforms include, but are not limited to, QEMU.

[0049] According to the embodiments in this specification, by providing a standardized set of interfaces and shielding the differences in underlying implementations, different disaster recovery systems can use the same set of biof SDKs, thereby reducing integration costs.

[0050] The following combination Figure 2 The system architecture of the data transmission methods and apparatus applicable to the embodiments of this specification will be described. It should be noted that... Figure 2 The examples shown are merely examples of system architectures that can be applied to the embodiments of this specification, in order to help those skilled in the art understand the technical content of this specification, but do not mean that the embodiments of this specification cannot be used in other devices, systems, environments or scenarios.

[0051] Figure 2 This is a schematic diagram of a system architecture illustrated in this specification according to an exemplary embodiment.

[0052] like Figure 2 As shown, the system architecture may include, for example, business systems and disaster recovery systems.

[0053] According to embodiments of this specification, a business system may include a Guest (virtual machine) OS (operating system) and a Host (host machine) OS.

[0054] According to embodiments of this specification, the Guest OS may include a vDisk (virtual disk). A vDisk is a virtualization technology that centrally stores the operating system, applications, and user data on a server. Clients can load and run this virtual disk image over a network, enabling efficient and unified desktop management. The vDisk can communicate with the host machine through a Virtio queue. A Virtio queue is a data structure for communication between the virtual machine and the host machine, used to pass I / O requests and responses between them.

[0055] According to embodiments of this specification, the Host OS may include the following components: I / O Filter: This can be used to intercept all write requests from virtual machines, including but not limited to write requests to image files (such as qcow2). This module can be deployed in the I / O path of a virtualization platform (such as QEMU). IO Buffer: Can be used to cache raw I / O data in memory mode; Bitmap module: can be used to record LBA change positions in bitmap mode; xnet Client: Can be used to send data (data stream) to the xnet Server of the disaster recovery system through an encrypted channel. The data can be, for example, data in an IO Buffer or bitmap data. The encrypted channel can include, for example, an xnet channel. Cvd DS: Can be used to send commands to QEMU via Qmp Channel (QEMU Machine Protocol). Cvd DS also interacts with the Cvd SDK in the biof SDK via control messages to coordinate data consistency or operating modes.

[0056] According to embodiments of this specification, a disaster recovery system may include a biof SDK. The biof SDK can be encapsulated as a .so dynamic library, exposing a standardized API (Application Programming Interface). The disaster recovery system can use this standardized API to interface with the biof SDK dynamic library. For example, the biof SDK may include the libraries libbiof and libcvd. libbiof may contain an xnet server (for receiving data) and an SDK API (external interface). The SDK API coordinates internally within libbiof and processes the received data through Poll cb (polling callback). libcvd may contain a Cvd SDK for handling control commands.

[0057] According to the embodiments in this specification, the biof SDK is not only a data channel, but also a state awareness hub. It can proactively notify the disaster recovery system when the I / O Filter changes mode and provide a difference completion mechanism.

[0058] like Figure 3 The diagram shown is a schematic representation of a biof SDK module according to another exemplary embodiment. The internal core module of the biof SDK may include: Initialization Manager: Can be used to provide the biof_init() interface to complete filter connection, parameter configuration, heartbeat registration, etc.

[0059] Data callback engine: This can be used to support registering I / O data receiving callback functions io_data_callback(metadata, data) and asynchronously pushing I / O metadata and content. Metadata may include, for example, the start LBA for writing, the writing length (in bytes), timestamps, and tags (whether it is a bitmap re-transmission, compression flags, etc.).

[0060] Mode status listener: can be used to provide the on_mode_changed(mode) event, which is used to notify the disaster recovery system of the current working mode (mode).

[0061] Control command processor: It can be used to support the issuance of control commands such as biof_start_full_backup(), which is used to start a full backup.

[0062] Error recovery module: It can be used to provide error recovery mechanisms, such as supporting disconnection reconnection, data interruption resumption, CRC (Cyclic Redundancy Check) verification, etc.

[0063] The following implementation describes a data transmission process based on the foregoing embodiments, including the following steps: During the initialization phase, the disaster recovery system calls `biof_init()` to initialize the biof SDK. The biof SDK establishes a communication channel with the I / O Filter (e.g., Unix Socket or shared memory). It registers the I / O data reception callback function `io_data_callback()` and the mode change callback function `mode_changed_callback()`.

[0064] When the buffer utilization is less than 90%, it is in memory mode. The I / O filter intercepts write requests and copies the complete I / O data to the IO buffer. The xnet Client reads data from the IO Buffer and sends it via the xnet protocol; After receiving the data, the biof SDK calls the user-registered io_data_callback(metadata, data) to push a complete I / O copy.

[0065] When the I / O filter detects that the buffer usage is ≥90%, it automatically switches to bitmap mode. The biof SDK triggers the mode_changed_callback(MODE_BITMAP) event, where MODE_BITMAP represents the bitmap mode; Upon receiving the notification, the disaster recovery system stops expecting a complete data stream, starts the Bitmap receiving process, and records the start timestamp T1.

[0066] When running in bitmap mode, the I / O Filter only records the LBA change range and generates a sparse bitmap. The xnet Client uploads the bitmap to the disaster recovery system; The biof SDK pushes bitmap data via bitmap_data_callback(bitmap, timestamp).

[0067] The disaster recovery system parses the bitmap to identify all modified LBA ranges. Then, it sends a request to the business system to retrieve the difference data (which can be done via the xnet reverse channel).

[0068] The business system pushes the corresponding block of data when the system is idle to ensure eventual consistency.

[0069] When the recovery conditions are met, the business system switches back to memory mode. For example, if the IO buffer utilization is ≤30%, the I / O filter switches back to memory mode.

[0070] The biof SDK triggers mode_changed_callback(MODE_MEMORY) again, where MODE_MEMORY represents the memory mode; The disaster recovery system resumes receiving the complete I / O stream and completes the retransmission using the bitmap.

[0071] Corresponding to the embodiments of the foregoing methods, this specification also provides embodiments of a data transmission device and the terminal to which it is applied.

[0072] The embodiments of the data transmission device described in this specification can be applied to computer devices, such as servers or terminal devices. The device embodiments can be implemented in software, hardware, or a combination of both. Taking software implementation as an example, as a logical device, it is formed by the processor reading the corresponding computer program instructions from non-volatile memory into memory for execution. From a hardware perspective, such as... Figure 4 The diagram shown is a hardware structure diagram of a computer device containing the data transmission device according to an embodiment of this specification. Except for... Figure 4 In addition to the processor 410, memory 430, network interface 420, and non-volatile memory 440 shown, the server or electronic device where the device 431 is located in the embodiment may also include other hardware depending on the actual function of the computer device, which will not be described in detail here.

[0073] like Figure 5 As shown, Figure 5 This is a block diagram illustrating a data transmission apparatus according to an exemplary embodiment of this specification, the apparatus comprising: The first switching module 510 is used to switch from memory mode to bitmap mode when the memory usage rate is detected to be greater than or equal to a first usage rate threshold while in memory mode. Bitmap generation module 520 is used to generate a bitmap based on the logical block address change information corresponding to the target data in response to a write request for the target data when the bitmap mode is in operation. Bitmap sending module 530 is used to send bitmaps to the disaster recovery system; The request receiving module 540 is used to receive the difference data acquisition request sent by the disaster recovery system. The first data sending module 550 is used to send the target data corresponding to the difference data acquisition request to the disaster recovery system.

[0074] Optionally, the device may further include: The second switching module is used to switch from bitmap mode to memory mode if the memory usage rate is detected to be less than a second usage rate threshold when the bitmap mode is in operation.

[0075] Optionally, the device may further include: The copy module is used to copy target data to memory in response to write requests for target data when the system is in memory mode. The second data sending module is used to send data in memory to the disaster recovery system.

[0076] Optionally, the device may further include: The first notification sending module is used to send a bitmap mode switching notification to the disaster recovery system when the memory usage rate is detected to be greater than or equal to a first usage rate threshold while in memory mode.

[0077] Optionally, the device may further include: The second notification sending module, when in bitmap mode, sends a memory mode switching notification to the disaster recovery system if it detects that the memory usage rate is less than the second usage rate threshold.

[0078] Accordingly, this specification also provides an electronic device including a processor; a memory for storing processor-executable instructions; wherein the processor is configured to: in memory mode, if the memory utilization rate is detected to be greater than or equal to a first utilization rate threshold, switch from memory mode to bitmap mode; in bitmap mode, generate a bitmap based on logical block address change information corresponding to the target data in response to a write request for target data; send the bitmap to a disaster recovery system; receive a difference data acquisition request sent by the disaster recovery system; and send the target data corresponding to the difference data acquisition request to the disaster recovery system.

[0079] like Figure 6 As shown, Figure 6 This is a block diagram illustrating another data transmission apparatus according to an exemplary embodiment of this specification, the apparatus comprising: Bitmap receiving module 610 is used to receive bitmaps sent by the business system. The bitmaps are used to indicate logical block address change information. The bitmaps are sent by the business system when the memory usage rate is greater than or equal to the usage rate threshold. The request sending module 620 is used to send a difference data acquisition request to the business system based on the logical block address change information. The first data receiving module 630 is used to receive the target data corresponding to the difference data acquisition request sent by the business system.

[0080] Optionally, the request sending module may include: The first sending submodule is used to send a difference data acquisition request to the business system based on the logical block address change information when the computing resource utilization rate is less than the utilization rate threshold.

[0081] Optionally, the device may further include: The first notification receiving module is used to receive bitmap mode switching notifications sent by the business system. The bitmap mode switching notification indicates that the business system is in bitmap mode. The request sending module may include: The second sending submodule is used to send a difference data acquisition request to the business system based on the logical block address change information when the business system is determined to be in bitmap mode.

[0082] Optionally, the device may further include: The second notification receiving module is used to receive memory mode switching notifications sent by the business system. The memory mode switching notification indicates that the business system is in memory mode. The second data receiving module is used to receive data sent from the business system in memory when the business system is determined to be in memory mode.

[0083] Accordingly, this specification also provides an electronic device including a processor; a memory for storing processor-executable instructions; wherein the processor is configured to: receive a bitmap sent by a business system, the bitmap indicating logical block address change information, the bitmap being sent by the business system when memory usage is greater than or equal to a usage threshold; send a difference data acquisition request to the business system based on the logical block address change information; and receive target data corresponding to the difference data acquisition request sent by the business system.

[0084] According to the embodiments in this specification, in bitmap mode, the business system can generate a bitmap based on the logical block address change information corresponding to the target data in response to a write request for target data, and send it to the disaster recovery system. The disaster recovery system can then request the target data corresponding to the logical block address information from the business system based on the bitmap. This enables data synchronization between the business system and the disaster recovery system.

[0085] The specific implementation process of the functions and roles of each module in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0086] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0087] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0088] Other embodiments of this specification will readily occur to those skilled in the art upon consideration of the specification and practice of the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations that follow the general principles of this specification and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this specification are indicated by the following claims.

[0089] It should be understood that this specification is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this specification is limited only by the appended claims.

[0090] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A data transmission method applied to a service system, characterized in that, The method includes: In memory mode, if the detected memory usage is greater than or equal to a first usage threshold, switch from memory mode to bitmap mode. In bitmap mode, for a write request for target data, a bitmap is generated based on the logical block address change information corresponding to the target data; Send the bitmap to the disaster recovery system; Receive the differential data acquisition request sent by the disaster recovery system; Send the target data corresponding to the difference data acquisition request to the disaster recovery system.

2. The method of claim 1, wherein, The method further includes: When in bitmap mode, if memory usage is detected to be less than a second usage threshold, the system switches from bitmap mode to memory mode.

3. The method according to claim 1 or 2, characterized in that, The method further includes: In memory mode, for write requests to target data, the target data is copied to memory; The data in memory is sent to the disaster recovery system.

4. The method of claim 1, wherein, The method further includes: In memory mode, if the detected memory usage rate is greater than or equal to a first usage rate threshold, a bitmap mode switching notification is sent to the disaster recovery system.

5. The method of claim 2, wherein, The method further includes: In bitmap mode, if the memory usage is detected to be less than the second usage threshold, a memory mode switching notification is sent to the disaster recovery system.

6. A data transmission method applied to a disaster recovery system, characterized in that, The method includes: The system receives a bitmap sent by the business system. The bitmap is used to indicate logical block address change information. The bitmap is sent by the business system when the memory usage rate is greater than or equal to the usage rate threshold. Based on the logical block address change information, a difference data acquisition request is sent to the business system; Receive the target data corresponding to the difference data acquisition request sent by the business system.

7. The method of claim 6, wherein, The step of sending a difference data acquisition request to the business system based on the logical block address change information includes: If the computing resource utilization rate is less than the utilization rate threshold, a difference data acquisition request is sent to the business system based on the logical block address change information.

8. The method of claim 6, wherein, The method further includes: Receive a bitmap mode switching notification sent by the business system, wherein the bitmap mode switching notification indicates that the business system is in bitmap mode; The step of sending a difference data acquisition request to the business system based on the logical block address change information includes: Once it is determined that the business system is in bitmap mode, a difference data acquisition request is sent to the business system based on the logical block address change information.

9. The method of claim 6, wherein, The method further includes: Receive a memory mode switching notification sent by the business system, the memory mode switching notification indicating that the business system is in memory mode; Once it is determined that the business system is in memory mode, the system receives the data in memory sent by the business system.

10. A data transmission apparatus, characterized by comprising: The device includes: The first switching module is used to switch from memory mode to bitmap mode when the memory usage rate is detected to be greater than or equal to a first usage rate threshold while in memory mode. The bitmap generation module is used to generate a bitmap based on the logical block address change information corresponding to the target data in response to a write request for the target data when the bitmap mode is in progress. The bitmap sending module is used to send the bitmap to the disaster recovery system; The request receiving module is used to receive the difference data acquisition request sent by the disaster recovery system; The first data sending module is used to send the target data corresponding to the difference data acquisition request to the disaster recovery system.

11. A data transmission apparatus, characterized by comprising: The device includes: The bitmap receiving module is used to receive a bitmap sent by the business system. The bitmap is used to indicate logical block address change information. The bitmap is sent by the business system when the memory usage rate is greater than or equal to the usage rate threshold. The request sending module is used to send a difference data acquisition request to the business system based on the logical block address change information; The first data receiving module is used to receive the target data corresponding to the difference data acquisition request sent by the business system.

12. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store processor-executable instructions; The processor is configured to perform the data transmission method according to any one of claims 1 to 9.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to perform the data transmission method according to any one of claims 1 to 9.

Images