Data recovery processing method and device, equipment and medium

Abstract

The invention discloses a data recovery processing method and device, equipment and a medium. The method comprises the following steps: acquiring at least one target end node of to-be-recovered data and at least one source end node corresponding to each target end node; for each target end node, according to the obtained configuration information of the target end node, detecting whether the target end node satisfies a cloning condition; and when the target end node meets the cloning condition, sending the address of the corresponding source end node to the target end node, so that the target end node clones the data of the corresponding source end node into the target end node. According to the embodiment of the invention, the convenience of data recovery can be improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a data recovery processing method, device, equipment and medium. Background Art

[0002] With the rapid development of distributed databases, distributed database operation and maintenance technologies have emerged. Data corruption due to human error, malicious damage, and storage media damage requires data recovery on the data nodes where the data is corrupted.

[0003] Currently, existing data recovery technologies achieve data recovery through NAS mounting or third-party storage vendors.

[0004] However, the operation and maintenance of the above data recovery technology is difficult, and the operation and maintenance process is cumbersome and prone to errors. Summary of the Invention

[0005] The present invention provides a data recovery processing method, device, equipment and medium. The embodiments of the present invention can improve the convenience of data recovery.

[0006] In a first aspect, an embodiment of the present invention provides a data recovery method, the method comprising:

[0007] Acquire at least one target end node of data to be recovered, and at least one source end node corresponding to each target end node;

[0008] For each target end node, based on the obtained configuration information of the target end node, detect whether the target end node meets the cloning conditions;

[0009] When the target node meets the cloning condition, the address of the corresponding source node is sent to the target node, so that the target node clones the data of the corresponding source node into the target node.

[0010] In a second aspect, an embodiment of the present invention further provides a data recovery processing device, the device comprising:

[0011] A node acquisition module, configured to acquire at least one target node of the data to be recovered and at least one source node corresponding to each target node;

[0012] A condition detection module is used to detect whether the target end node meets the cloning condition based on the obtained configuration information of the target end node;

[0013] The cloning module is used to send the address of the corresponding source node to the target node when the target node meets the cloning condition, so that the target node clones the data of the corresponding source node into the target node.

[0014] In a third aspect, an embodiment of the present invention further provides a data recovery processing device, the data recovery processing device comprising:

[0015] at least one processor; and

[0016] a memory communicatively connected to at least one processor; wherein,

[0017] The memory stores a computer program that can be executed by at least one processor. The computer program is executed by the at least one processor so that the at least one processor can execute the data recovery method of any embodiment of the present invention.

[0018] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the data recovery processing method of any embodiment of the present invention when executed.

[0019] The technical solution of the embodiment of the present invention can ensure that the data recovery operation can be performed between the correct nodes by obtaining the target end node of the data to be recovered and its corresponding source end node, thereby ensuring the accuracy and efficiency of data recovery, avoiding data cloning between wrong nodes, and reducing the complexity of operations; by detecting whether the target end node meets the cloning conditions, it can be ensured that the data cloning operation will not be performed on a node that does not meet the conditions; by sending the address of the source end node to the target end node, the data recovery operation can be automated, avoiding manual intervention, simplifying the data recovery process, improving operational efficiency, ensuring that data is cloned from the correct source end node to the target end node, and reducing the risk of human error.

[0020] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 A flowchart of a data recovery method provided by an embodiment of the present invention;

[0023] Figure 2 A flowchart of a data recovery method provided by an embodiment of the present invention;

[0024] Figure 3 A schematic structural diagram of a data recovery processing device provided by an embodiment of the present invention;

[0025] Figure 4 A schematic structural diagram of a data recovery processing device provided by an embodiment of the present invention. DETAILED DESCRIPTION

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

[0027] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] In the technical solutions of the embodiments of the present invention, the acquisition, storage and application of the data to be recovered and the configuration information involved all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0029] Figure 1 A flowchart of a data recovery method provided by an embodiment of the present invention. The embodiment of the present invention is applicable to data recovery processing. The method can be executed by a data recovery processing device, which can be implemented in the form of hardware and / or software.

[0030] See also Figure 1 The data recovery processing method shown includes:

[0031] S101: Acquire at least one target end node of data to be recovered, and at least one source end node corresponding to each target end node.

[0032] The data to be recovered may refer to data that needs to be recovered due to data loss or corruption. For example, in a distributed database environment, data is typically distributed across multiple nodes, with each node managing a portion of the database. Data distributed across multiple nodes is called data sharding. When data on a node is lost or corrupted, the data stored on that node may be the data to be recovered, and the data on that node needs to be restored to ensure data integrity and availability.

[0033] The target node may be a node where data needs to be restored. The target node may be a node where data has been lost, damaged, or is inaccessible. The target node is used to store the restored data.

[0034] Among them, the source end node may refer to a node that stores normal data. During the data recovery process, the source end node provides cloned data for the target end node, and the source end node is the data source for data recovery. The at least one source end node corresponding to the target end node means that before data loss or data damage occurs, the original data of the target end node and the data stored on a source end node remain the same, or the original data of the target end node is divided into multiple copies of data, and multiple source end nodes respectively store copies of data that are identical to the original data. For example, in a distributed database, the data of node A is lost or damaged, and node B and node C respectively store copies of node A's data. When performing data recovery, node B and node C serve as source nodes, and node A serves as the target end node.

[0035] S102 : For each target end node, detect whether the target end node meets the cloning condition according to the acquired configuration information of the target end node.

[0036] Configuration information may refer to relevant status information of the target node. Configuration information may include data deletion status, cold data status, flashback status, resource status, and operating status. The data deletion status may refer to whether the data on the target node is allowed to be deleted or cleared; the cold data status may refer to whether the cold data on the target node is allowed to be restored; the flashback status may refer to whether the target node allows a flashback operation, which refers to restoring data to a certain historical point in time; the resource status may refer to whether the target node has sufficient storage space to perform data recovery tasks; and the operating status may refer to whether the target node is operating normally.

[0037] The cloning condition may refer to determining whether the target node allows data cloning. When the configuration information of the target node satisfies the preset cloning conditions, the cloning operation may continue; when at least one configuration information of the target node does not meet the preset cloning conditions, the cloning operation may be terminated. The cloning conditions may include the target node's data deletion status being that data deletion is allowed, the target node and the source node's cold data status being consistent, the flashback status being that the target node does not allow flashback operations, the resource status being that the target node has sufficient storage space for data cloning, and the operating status being that the target node is in normal operating state.

[0038] In a specific example, the target node's data deletion status is set to "allow data deletion" in order to clear the target node's data or database tables and ensure that the source node's data can be completely cloned to the target node. To maintain data recovery consistency, the target node's cold data status must be consistent with the source node's cold data status to prevent the cold data from being accidentally restored to the target node, resulting in inaccurate data status after recovery. The target node's flashback status is set to "not allowing flashback operations." If the target node allows flashback operations during data recovery, this may cause conflicts between data recovery and rollback, resulting in inconsistent recovered data or recovery failure.

[0039] Optionally, when the target node does not have sufficient storage space for data cloning, the target node may be expanded before data cloning.

[0040] S103: When the target node meets the cloning condition, the address of the corresponding source node is sent to the target node, so that the target node clones the data of the corresponding source node into the target node.

[0041] The address can refer to the network address or identifier of a data node. Sending the corresponding source node's address to the target node allows the target node to correctly clone data from the source node, ensuring the accuracy of the data cloning. For example, assuming the source node's address is 192.168.1.XXX, after the target node receives this address, it can connect to the source node via network communication, thereby initiating the data cloning operation.

[0042] Among them, cloning can refer to the process of copying data on the source node to the target node. Through the cloning operation, the target node can obtain a copy of the data of the source node, and the data to be recovered on the target node can be repaired. In a specific example, data cloning can be achieved through a cloning plug-in. The source node and the target node are respectively checked to see if the cloning plug-in is installed. If the cloning plug-in is not installed, the cloning plug-in is installed on the source node and the target node respectively. Data cloning is achieved through the cloning plug-in. After the cloning operation is completed, if the source node and the target node originally did not have the cloning plug-in installed, the cloning plug-in is uninstalled. If the source node and the target node originally had the cloning plug-in installed, the cloning plug-in is not uninstalled.

[0043] It can be seen that in the embodiment of the present application, by obtaining the target end node of the data to be recovered and its corresponding source end node, it can be ensured that the data recovery operation can be performed between the correct nodes, ensuring the accuracy and efficiency of data recovery, avoiding data cloning between wrong nodes, and reducing the complexity of operations; by detecting whether the target end node meets the cloning conditions, it can be ensured that the data cloning operation will not be performed on a node that does not meet the conditions; by sending the address of the source end node to the target end node, the data recovery operation can be automated, avoiding manual intervention, simplifying the data recovery process, improving operational efficiency, ensuring that the data is cloned from the correct source end node to the target end node, and reducing the risk of human error.

[0044] In an optional embodiment, "detecting whether the target end node meets the cloning condition based on the obtained configuration information of the target end node" is refined into "detecting whether each state includes the corresponding cloning state based on the obtained configuration information of the target end node; when each state meets the corresponding cloning state, determining that the target end node meets the cloning condition" to improve the data recovery processing operation.

[0045] It should be noted that for parts not described in detail in the embodiments of the present invention, reference may be made to the descriptions of other embodiments. Figure 2 The present invention provides a flowchart of a data recovery method.

[0046] See also Figure 2 The data recovery processing method shown includes:

[0047] S201: Acquire at least one target end node of data to be recovered, and at least one source end node corresponding to each target end node.

[0048] S202: For each target node, based on each state included in the acquired configuration information of the target node, detecting whether each state satisfies a corresponding clone state; the configuration information of the target node includes: data deletion state, cold data state, flashback state, resource state, and running state;

[0049] The detecting whether each state satisfies the corresponding cloning state may refer to whether each state in the configuration information of the target end node satisfies the state that allows the target end to perform data cloning.

[0050] S203: When all states satisfy the corresponding clone state, determine that the target end node meets the clone condition.

[0051] Specifically, only when all states in the configuration information of the target node meet the corresponding clone state can it be confirmed that the target node meets the cloning conditions. If as long as any state in the configuration information of the target node does not meet the corresponding clone state, it is determined that the target node does not meet the cloning conditions and the cloning is automatically terminated.

[0052] S204: When the target node meets the cloning condition, the address of the corresponding source node is sent to the target node, so that the target node clones the data of the corresponding source node into the target node.

[0053] It can be seen that in this embodiment, by detecting whether each state of the target end node meets the corresponding cloning conditions, the cloning operation can be controlled more accurately, avoiding the target end node from performing data cloning operations when it is not suitable for data cloning, and reducing the risk of cloning failure; by ensuring that each state of the target end node meets the cloning conditions, it can be ensured that the data cloning operation is performed in a suitable environment, thereby improving the success rate of the cloning operation and the accuracy of data recovery; when each state meets the cloning conditions, it can be reliably determined that the target end node meets the cloning requirements, avoiding the interruption of the cloning operation due to a single state not meeting the conditions, thereby improving the degree of automation and efficiency.

[0054] In some embodiments, based on each state included in the acquired configuration information of the target end node, detecting whether each state satisfies a corresponding clone state includes:

[0055] For the data deletion state, when the data deletion state of the target node is deletion allowed, determining whether the data deletion state of the target node satisfies the corresponding clone state;

[0056] Before the target node clones the data of the corresponding source node to the target node, the following steps are also included:

[0057] Control the target node to delete local data.

[0058] Specifically, if the data deletion status of the target node is allowed to be deleted, it means that the data of the target node can be deleted or overwritten to make room for the newly cloned data. If the data of the target node cannot be deleted or cleared, the data of the source node cannot be successfully cloned to the target node.

[0059] Before the target node clones the corresponding source node data to the target node, control the target node to delete the local data. If there is local data on the target node, data mixing, duplication, or incorrect updates may occur during the cloning process. The local data on the target node will not be directly used in subsequent operations. If these local data are retained, it will affect performance. For example, local data will occupy resources, affecting storage efficiency and data access speed.

[0060] It can be seen that in this embodiment, when the deletion status of the target end node is deletion allowed, it can ensure that there is no obstruction in the cloning process, avoiding the failure of the cloning operation due to non-permitted deletion; the prerequisite judgment of data cloning can be realized, so that the data cloning process can be started and executed smoothly, avoiding data cloning when the deletion conditions are not met; controlling the target end node to delete local data can avoid the conflict between the old data retained on the target end node and the source end data, ensuring that the status of the target end node meets the requirements of data cloning.

[0061] In some embodiments, based on each state included in the acquired configuration information of the target end node, detecting whether each state satisfies a corresponding clone state includes:

[0062] For the cold data status, obtain the cold data status of the source node;

[0063] When the cold data state of the target end node is consistent with the cold data state of the source end node, it is determined that the cold data state of the target end node satisfies the corresponding clone state.

[0064] Cold data refers to data that has not been accessed or modified for a long time.

[0065] During the data cloning process, the cold data state of the target node must be consistent with that of the source node. If the cold data state of the target node differs from that of the source node, unnecessary cold data will be mistakenly introduced during the data recovery process, affecting the accuracy of the target node data recovery.

[0066] It can be seen that in this embodiment, by ensuring that the cold data status of the target node and the source node are consistent, the problem of cloning data caused by inconsistent cold data status can be avoided, ensuring that the target node can clone data from the source node normally.

[0067] In some embodiments, based on each state included in the acquired configuration information of the target end node, detecting whether each state satisfies a corresponding clone state includes:

[0068] For the flashback state, obtain the cold data state of the source node;

[0069] When the flashback state of the target end node is prohibited, it is determined that the flashback state of the target end node satisfies the corresponding clone state.

[0070] When the flashback state is enabled, data can be restored to a previous point in time. The cold data state switch determines whether recovery operations are allowed on cold data. If the cold data state switch is on, recovery of cold data is allowed. If the cold data state switch is off, recovery of cold data is not allowed. When the flashback state of the target node is disabled, flashback operations are not allowed on the target node, which can avoid performing recovery operations that do not meet the requirements. Setting the flashback state of the target node to disabled means that the node cannot be rolled back to the state of a certain historical point in time, which can prevent historical data or inconsistent data from being restored to the target node.

[0071] It can be seen that in this embodiment, before the cloning operation, obtaining the cold data status of the source node can confirm whether the cold data needs to be restored and ensure that the data status of the source end meets the requirements of target end recovery; by prohibiting the flashback state of the target end node, it is ensured that the data cloning process is not interfered with by historical rollback operations, avoiding erroneous recovery to a certain historical time point, and ensuring the integrity and consistency of the data.

[0072] In some embodiments, before detecting, for each target end node, whether the target end node meets the cloning condition based on the acquired configuration information of the target end node, the process further includes:

[0073] For each target node, detect whether the target node and the source node corresponding to the target node are configured with a clone plug-in;

[0074] When a target node and a source node corresponding to the target node have nodes that are not configured with a clone plug-in, the control node installs the clone plug-in; wherein the clone plug-in is used to control the target node to clone data from the source node.

[0075] Optionally, when the target node and the source node are not configured with a clone plug-in, the control node installs the clone plug-in and completes cloning, and then uninstalls the plug-in of the target node and the source node; if the target node and the source node have already been configured with a clone plug-in, the uninstallation operation is not performed.

[0076] It can be seen that in this embodiment, checking whether the target node and the source node have installed the clone plug-in can avoid errors or failures due to the lack of plug-ins during the data cloning process, ensuring that the cloning operation can proceed smoothly; by automatically installing the clone plug-in, the data cloning process can be simplified to ensure that each node can successfully perform the clone operation.

[0077] In some embodiments, the source node is a data node of a distributed database, and the target node is a data node of a distributed database; the source node corresponds to at least one data shard, and the data shard corresponding to the target node includes the data shard corresponding to the corresponding source node.

[0078] Specifically, the source node and the target node are data nodes in a distributed database. The data stored in the source node and the target node can be data shards, and the data shards on the target node must be consistent with the data shards on the corresponding source node.

[0079] It can be seen that in this embodiment, the data recovery method provided by the embodiment of the present invention can be applied to a distributed database; data sharding is a way to manage data in a distributed database. The data shards of the source node and the target node are matched one by one, ensuring that the data at the source end can be accurately cloned to the target end, avoiding the risk of data inconsistency or loss.

[0080] Figure 3 A schematic diagram of the structure of a data recovery processing device provided by an embodiment of the present invention. The embodiment of the present invention is applicable to data recovery processing, the device can execute a data recovery processing method, and the device can be implemented in the form of hardware and / or software.

[0081] See also Figure 3 The data recovery processing device shown includes: a node acquisition module 301, a condition detection module 302 and a cloning module 303, wherein:

[0082] A node acquisition module, configured to acquire at least one target node of the data to be recovered and at least one source node corresponding to each target node;

[0083] A condition detection module is used to detect whether the target end node meets the cloning condition based on the obtained configuration information of the target end node;

[0084] The cloning module is used to send the address of the corresponding source node to the target node when the target node meets the cloning condition, so that the target node clones the data of the corresponding source node into the target node.

[0085] The technical solution of the embodiment of the present invention can ensure that the data recovery operation can be performed between the correct nodes by obtaining the target end node of the data to be recovered and its corresponding source end node, thereby ensuring the accuracy and efficiency of data recovery, avoiding data cloning between wrong nodes, and reducing the complexity of operations; by detecting whether the target end node meets the cloning conditions, it can be ensured that the data cloning operation will not be performed on a node that does not meet the conditions; by sending the address of the source end node to the target end node, the data recovery operation can be automated, avoiding manual intervention, simplifying the data recovery process, improving operational efficiency, ensuring that data is cloned from the correct source end node to the target end node, and reducing the risk of human error.

[0086] In some embodiments, the configuration information of the target node includes: data deletion status, cold data status, flashback status, resource status, and running status; based on the obtained configuration information of the target node, in terms of detecting whether the target node meets the cloning conditions, the condition detection module 302 is specifically configured to:

[0087] According to each state included in the obtained configuration information of the target end node, detecting whether each state satisfies the corresponding clone state;

[0088] When all states satisfy the corresponding clone state, it is determined that the target end node meets the clone condition.

[0089] In some embodiments, in terms of detecting whether each state includes each state in the acquired configuration information of the target end node and satisfies the corresponding clone state, the condition detection module 302 is specifically configured to:

[0090] For the data deletion state, when the data deletion state of the target node is deletion allowed, determining whether the data deletion state of the target node satisfies the corresponding clone state;

[0091] Before the target node clones the data of the corresponding source node to the target node, the following steps are also included:

[0092] Control the target node to delete local data.

[0093] In some embodiments, in terms of detecting whether each state includes each state in the acquired configuration information of the target end node and satisfies the corresponding clone state, the condition detection module 302 is specifically configured to:

[0094] For the cold data status, obtain the cold data status of the source node;

[0095] When the cold data state of the target end node is consistent with the cold data state of the source end node, it is determined that the cold data state of the target end node satisfies the corresponding clone state.

[0096] In some embodiments, in terms of detecting whether each state includes each state in the acquired configuration information of the target end node and satisfies the corresponding clone state, the condition detection module 302 is specifically configured to:

[0097] For the flashback state, obtain the cold data state of the source node;

[0098] When the flashback state of the target end node is prohibited, it is determined that the flashback state of the target end node satisfies the corresponding clone state.

[0099] In some embodiments, before detecting, for each target end node, whether the target end node meets the cloning condition based on the acquired configuration information of the target end node, the cloning module 303 is specifically configured to:

[0100] For each target node, detect whether the target node and the source node corresponding to the target node are configured with a clone plug-in;

[0101] When a target node and a source node corresponding to the target node have nodes that are not configured with a clone plug-in, the control node installs the clone plug-in; wherein the clone plug-in is used to control the target node to clone data from the source node.

[0102] In some embodiments, the source node is a data node of a distributed database, and the target node is a data node of a distributed database; the source node corresponds to at least one data shard, and the data shard corresponding to the target node includes the data shard corresponding to the corresponding source node.

[0103] The data recovery processing device provided by the embodiment of the present invention can execute the data recovery processing method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of executing the data recovery processing method.

[0104] Figure 4 A schematic structural diagram of a data recovery processing device provided by an embodiment of the present invention.

[0105] like Figure 4As shown, the data recovery processing device 400 includes at least one processor 401, and a memory connected to the at least one processor 401, such as a read-only memory (ROM) 402, a random access memory (RAM) 403, etc., wherein the memory stores a computer program that can be executed by the at least one processor, and the processor 401 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 402 or the computer program loaded from the storage unit 408 to the random access memory (RAM) 403. Various programs and data required for the operation of the data recovery processing device 400 can also be stored in the RAM 403. The processor 401, ROM 402 and RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 408 is also connected to the bus 404.

[0106] Multiple components in the data recovery processing device 400 are connected to the I / O interface 405, including: an input unit 406, such as a keyboard, a mouse, etc.; an output unit 407, such as various types of displays, speakers, etc.; a storage unit 408, such as a magnetic disk, an optical disk, etc.; and a communication unit 409, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 409 allows the data recovery processing device 400 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0107] Processor 401 can be various general-purpose and / or specialized processing components with processing and computing capabilities. Some examples of processor 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. Processor 401 performs the various methods and processes described above, such as the data recovery processing method.

[0108] In some embodiments, the data recovery processing method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as the storage unit 408. In some embodiments, part or all of the computer program can be loaded and / or installed on the data recovery processing device 400 via the ROM 402 and / or the communication unit 409. When the computer program is loaded into the RAM 403 and executed by the processor 401, one or more steps of the data recovery processing method described above can be performed. Alternatively, in other embodiments, the processor 401 can be configured to execute the data recovery processing method by any other appropriate means (for example, by means of firmware).

[0109] Various embodiments of the systems and techniques described above can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0110] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0111] In the context of the present invention, computer-readable storage media can be tangible media that can contain or store a computer program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Computer-readable storage media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, computer-readable storage media can be machine-readable signal media. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0112] In order to provide interaction with the user, the systems and techniques described herein can be implemented on an operation detection device, which has: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball), through which the user can provide input to the data recovery processing device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0113] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0114] A computing system may include clients and servers. The clients and servers are generally remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within a cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS (Virtual Private Server) services.

[0115] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0116] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A data recovery processing method, characterized in that: Applied to a management node, the method comprises: Acquire at least one target end node of data to be recovered, and at least one source end node corresponding to each of the target end nodes; For each of the target end nodes, detecting whether the target end node meets a cloning condition according to the acquired configuration information of the target end node; When the target node meets the cloning condition, the address of the corresponding source node is sent to the target node, so that the target node clones the data of the corresponding source node into the target node.

2. The method according to claim 1, characterized in that The configuration information of the target node includes: data deletion status, cold data status, flashback status, resource status and operation status; The step of detecting whether the target end node satisfies a cloning condition according to the acquired configuration information of the target end node includes: According to each state included in the acquired configuration information of the target end node, detecting whether each state satisfies a corresponding clone state; When each of the states satisfies the corresponding clone state, it is determined that the target end node satisfies the clone condition.

3. The method according to claim 2, characterized in that The detecting, according to each state included in the acquired configuration information of the target end node, whether each state satisfies a corresponding clone state includes: For the data deletion state, when the data deletion state of the target end node is deletion allowed, determining that the data deletion state of the target end node satisfies the corresponding clone state; Before the target end node clones the data of the corresponding source end node into the target end node, the method further includes: Control the target end node to delete local data.

4. The method according to claim 2, characterized in that: The detecting, according to each state included in the acquired configuration information of the target end node, whether each state satisfies a corresponding clone state includes: With respect to the cold data state, obtaining the cold data state of the source node; When the cold data state of the target end node is consistent with the cold data state of the source end node, it is determined that the cold data state of the target end node satisfies the corresponding clone state.

5. The method according to claim 2, characterized in that: The detecting, according to each state included in the acquired configuration information of the target end node, whether each state satisfies a corresponding clone state includes: With respect to the flashback state, obtaining the cold data state of the source node; When the flashback state of the target end node is prohibited, it is determined that the flashback state of the target end node satisfies the corresponding clone state.

6. The method according to claim 1, characterized in that Before detecting, for each of the target end nodes, whether the target end node meets the cloning condition according to the acquired configuration information of the target end node, the method further includes: For each of the target end nodes, detecting whether the target end node and the source end node corresponding to the target end node are configured with a clone plug-in; When there is a node in the target node and the source node corresponding to the target node that is not configured with a clone plug-in, the node is controlled to install a clone plug-in; wherein the clone plug-in is used to control the target node to clone data from the source node.

7. The method according to claim 1, characterized in that The source node is a data node of a distributed database, and the target node is a data node of a distributed database; the source node corresponds to at least one data shard, and the data shard corresponding to the target node includes the data shard corresponding to the corresponding source node.

8. A data recovery processing device, characterized in that: include: A node acquisition module, used to acquire at least one target end node of the data to be recovered, and at least one source end node corresponding to each of the target end nodes; A condition detection module, used for detecting, for each of the target end nodes, whether the target end node meets the cloning condition according to the acquired configuration information of the target end node; The cloning module is used to send the address of the corresponding source node to the target node when the target node meets the cloning condition, so that the target node clones the data of the corresponding source node into the target node.

9. A data recovery processing device, characterized in that: The data recovery processing device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the data recovery processing method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the data recovery processing method according to any one of claims 1 to 7 when executed.

Images