Data backup method and device, equipment and medium

Abstract

The invention discloses a data backup method and device, equipment and a medium. The method comprises the following steps: receiving a backup task sent by a management node; when it is determined that the backup task corresponds to the database agent node, backup configuration information is obtained; at the moment corresponding to the backup task, acquiring backup data corresponding to the backup task and stored in a source data node corresponding to the backup configuration information; and storing the backup data in the proxy data node. According to the embodiment of the invention, the processing speed of data backup and 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 backup method, device, equipment and medium. Background Art

[0002] With the rapid development of distributed databases, the operation and maintenance technology for distributed databases has emerged. Due to human error, malicious destruction and damage to storage media, data damage may occur, and data nodes need to be backed up and restored.

[0003] Currently, existing data backup and data recovery are handled individually for each node.

[0004] However, the above data backup and data recovery methods have complicated processes, low efficiency, and high difficulty in operation and maintenance. Summary of the invention

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

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

[0007] Receive backup tasks sent by the management node;

[0008] When it is determined that the backup task corresponds to the database proxy node, the backup configuration information is obtained;

[0009] At a time corresponding to the backup task, obtaining the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information;

[0010] Store the backup data in the proxy data node.

[0011] In a second aspect, an embodiment of the present invention further provides a data backup device, the device comprising:

[0012] A backup task receiving module, used to receive the backup tasks sent by the management node;

[0013] A configuration information acquisition module, used to acquire backup configuration information when it is determined that the backup task corresponds to the database proxy node;

[0014] A backup data acquisition module, used to acquire the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information at the time corresponding to the backup task;

[0015] The backup data storage module is used to store the backup data in the proxy data node.

[0016] In a third aspect, an embodiment of the present invention further provides a data backup device, the data backup device comprising:

[0017] at least one processor; and

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

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

[0020] 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 backup method of any embodiment of the present invention when executed.

[0021] The technical solution of the embodiment of the present invention can realize unified scheduling and management of backup tasks by receiving backup tasks sent by the management node, thereby improving the collaborative efficiency of data backup; by obtaining backup configuration information when the backup task corresponds to the proxy node, it can ensure the correctness and pertinence of the backup task and avoid erroneous data backup; by obtaining the backup data stored in the source data node at a specified time, it can realize timely backup of data and ensure the real-time and integrity of the data; by storing the backup data in the proxy data node, it can realize secure storage and distributed backup of data, thereby improving the processing speed of data backup and data recovery.

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

[0023] 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.

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

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

[0026] Figure 3A schematic diagram of a data backup and data recovery method provided by an embodiment of the present invention;

[0027] Figure 4 A schematic diagram of the structure of a data backup device provided by an embodiment of the present invention;

[0028] Figure 5 A schematic diagram of the structure of a data backup device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme 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 described embodiments 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 creative work should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first", "second", etc. in the specification 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 data 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 that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] In the technical solution of the embodiment of the present invention, the acquisition, storage and application of the data, backup configuration information, etc. involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

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

[0033] See also Figure 1 The data backup method shown includes:

[0034] S101. Receive a backup task sent by a management node.

[0035] The management node may be a node responsible for scheduling backup and recovery tasks and interacting with each database proxy node. The management node may receive instructions issued by the user through the graphical interface, verify the validity of the instructions, and pass the instructions to the corresponding database proxy node for execution. The management node may also summarize the task execution results of each database node and feed back the task execution results to the graphical interface for display.

[0036] The backup task may refer to a task for backing up data on a data node. The backup task may include a scheduled backup cycle and specifying data nodes that need to be backed up.

[0037] S102: When it is determined that the backup task corresponds to the database proxy node, the backup configuration information is obtained.

[0038] The database proxy node refers to the proxy module of each data node in the distributed database system, which is responsible for receiving and executing tasks issued by the management node, including data backup, recovery, and storage configuration update operations. When performing a backup task, the database proxy node backs up the data to a specified storage location; when performing a recovery task, the database proxy node can perform data recovery operations and ensure the consistency of the restored data.

[0039] Among them, the backup configuration information may refer to the configuration information required for the backup operation, and the backup configuration may include the data node corresponding to the backup task, the target node for storing the backup data, and the storage type, wherein the storage type may refer to the technology or format used to store the backup data, and the storage type may include storage types such as network storage and distributed storage; network storage may include NAS (Network Attached Storage) and SAN (Storage Area Network), etc., and distributed storage may include Ceph and HDFS (Hadoop Distributed File System), etc.

[0040] S103. At a time corresponding to the backup task, obtain the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information.

[0041] The source data node may refer to a database node that needs to back up and / or restore data. The source data node includes data to be backed up, and during the data restoration process, the backup data may be restored from the source data node to the proxy data node.

[0042] The backup data may refer to the data that is extracted from the source data node through the backup task and needs to be backed up. The purpose of the backup data is to prevent data loss or damage. It represents the database status at a specific time or period. The backup data is usually stored in a designated backup storage device or storage location to facilitate data recovery when the data is lost or damaged.

[0043] S104: Store the backup data in the proxy data node.

[0044] The proxy data node may refer to a node for storing backup data. The main function of the proxy data node is to serve as a storage space for storing data obtained and backed up from the source data node. After the backup process is completed, the data is stored on the proxy data node until a restore operation is required.

[0045] It can be seen that in the embodiments of the present application, by receiving the backup tasks sent by the management node, unified scheduling and management of the backup tasks can be achieved, thereby improving the collaborative efficiency of data backup; by obtaining the backup configuration information when the backup tasks correspond to the proxy nodes, the correctness and pertinence of the backup tasks can be ensured, thereby avoiding erroneous data backup; by obtaining the backup data stored in the source data node at the specified time, timely backup of the data can be achieved, thereby ensuring the real-time and integrity of the data; by storing the backup data in the proxy data node, secure storage and distributed backup of the data can be achieved, thereby improving the processing speed of data backup and data recovery.

[0046] In an optional embodiment, "determining that the backup task corresponds to the database proxy node" is refined into "when the backup task includes a specified range, obtaining the node level corresponding to the specified range; wherein the specified node level includes: cluster level, shard level, computer room level and node level; obtaining the node range to which the database proxy node belongs in the node level; detecting whether the node range is consistent with the specified range; when the node range is consistent with the specified range, determining that the backup task corresponds to the database proxy node" to improve the data backup operation.

[0047] It should be noted that for the parts not described in detail in the embodiments of the present invention, reference may be made to the descriptions of other embodiments. Figure 2 A flowchart of a data backup method provided by an embodiment of the present invention.

[0048] See also Figure 2 The data backup method shown includes:

[0049] S201. Receive a backup task sent by a management node.

[0050] S202. When the backup task includes a specified range, obtain a node level corresponding to the specified range; wherein the specified node level includes: cluster level, shard level, computer room level and node level.

[0051] The specified range can refer to the range of data nodes that need to be backed up. The specified range determines the range of nodes, shards, computer rooms, or clusters that need to be backed up. The specified range is used to accurately target data backup or recovery tasks to the required parts.

[0052] The node level may refer to the operation scope of a single database node in a distributed database cluster. For example, if a database cluster has multiple nodes, each node stores different shard data. If the user only needs to back up the data of a specific node, or needs to restore the data of a specific node, the node level can be specified to ensure that only the data of the node is operated.

[0053] The cluster level may refer to the scope of operating the entire distributed database cluster as a unit. When the backup or recovery task is performed at the cluster level, it means that the operation will affect all nodes in the entire database cluster. For example, when a database system fails, the user may need to restore the data of the entire database cluster to a certain moment, and the cluster-level operation can act on each node of the entire database cluster.

[0054] The shard level may refer to the scope of backup or recovery operations on a specific shard in a database cluster. For example, if a database cluster is divided into multiple shards, each shard stores data in a different area. When data in a specific area is damaged, the user can only restore the data of the shard without restoring the data of the entire cluster.

[0055] The computer room level may refer to the data management scope of the computer room level physically deployed in the database cluster. For example, assuming that the database cluster includes computer room A and computer room B, if computer room A fails, the user can restore the data of computer room A to the most recent backup through computer room level recovery operations without affecting the data of computer room B.

[0056] The node level may be the range covered by a specific node in a backup or recovery task. For example, there are multiple nodes in a database cluster, and when a backup task or recovery task specifies a specific node range, only the node will execute the backup task or recovery task.

[0057] S203: Obtain the node range to which the database proxy node belongs in the node level.

[0058] The node range may refer to a range of specific data nodes that need to be backed up.

[0059] S204: Check whether the node range is consistent with the specified range.

[0060] Specifically, detecting whether the node range is consistent with the specified range may refer to detecting whether the node range for executing the specific backup task is consistent with the preset specified range.

[0061] S205: When the node range is consistent with the specified range, determine that the backup task corresponds to the database proxy node, and obtain backup configuration information.

[0062] Specifically, the purpose of detecting whether the node range is consistent with the specified range is to ensure that the backup task is only executed on the nodes that need to be operated within the task range. The backup operation will only continue to be executed when the actual range of the node matches the specified range of the task. When the detected node range is consistent with the specified range, it means that the nodes within the node range are the backup task execution nodes, and the backup configuration information can be loaded and applied to ensure that the task can be performed on the correct node and the backup task is executed as expected.

[0063] S206. At a time corresponding to the backup task, obtain the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information.

[0064] S207: Store the backup data in the proxy data node.

[0065] It can be seen that in this embodiment, by obtaining the node level corresponding to the specified range, it can be ensured that the backup task can be accurately applied to the nodes in the predetermined range, thereby avoiding the problem of range mismatch when the backup task is executed; by clearly specifying the node level as cluster level, shard level, computer room level or node level, it can be flexibly adapted to distributed database systems of different scales and complexities, ensuring that the backup task is executed within the appropriate hierarchical range; by obtaining the node range to which the database proxy node belongs within the specified node level, it can be clarified whether the node meets the conditions for the execution of the backup task; by detecting whether the node range is consistent with the specified range, it can be ensured that the backup task is only executed on nodes that meet the conditions, avoiding the task from being erroneously executed on nodes that do not meet the conditions, thereby ensuring the correctness of the task and the consistency of the data; by confirming that the task is only executed when the node range is consistent, unnecessary resource consumption can be avoided, ensuring that the backup task is only performed on appropriate nodes.

[0066] In some embodiments, at a time corresponding to the backup task, obtaining backup data corresponding to the backup task and stored in a source data node corresponding to the backup configuration information includes:

[0067] When the update mode corresponding to the backup task is periodic update, the timer starts;

[0068] When the timing duration reaches the period corresponding to the backup task, it is determined that the time corresponding to the backup task has arrived, and the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information is obtained.

[0069] The update mode may refer to a mode of automatically executing a backup task. The update mode may determine the update frequency and update trigger conditions of the backup data. Different update modes are suitable for different data recovery requirements. For example, periodic update is suitable for data scenarios that require regular backup, while demand update is suitable for scenarios that require backup based on actual changes.

[0070] The periodic update may refer to updating the backup data at a fixed time interval. The periodic update may be performed automatically without manual intervention, and the periodic update performs the backup task based on a preset periodic time.

[0071] The timing duration may refer to the duration calculated from the starting point when the backup task is triggered.

[0072] It can be seen that in this embodiment, by using the periodic update method, the backup task can be executed regularly and the backup data can be updated synchronously, ensuring that the data always maintains the latest backup status within the regular period and reducing omissions or losses; through precise timing, it can be ensured that the backup task is carried out according to the scheduled cycle without relying on human intervention, avoiding missing the backup time, thereby improving the reliability and automation of the backup task; by automatically acquiring backup data, the complexity of manual operations is reduced, and accurate data can be efficiently acquired from the source data node, ensuring the integrity and consistency of data backup.

[0073] In some embodiments, at a time corresponding to the backup task, obtaining backup data corresponding to the backup task and stored in a source data node corresponding to the backup configuration information includes:

[0074] When the update mode corresponding to the backup task is demand update, determine the time corresponding to the backup task, and obtain the backup data corresponding to the backup task stored in the source data node corresponding to the backup configuration information; the backup data corresponding to the backup task includes the backup data corresponding to the supervision time point.

[0075] Among them, demand update can refer to performing backup based on external requests or certain special demand triggers. Demand update is suitable for scenarios where scheduled backup is not required but backup is performed according to actual needs. For example, in some regulatory scenarios, since some data is constantly changing, but the data content at a certain point in history needs to be obtained, the data content at a certain point in history needs to be backed up.

[0076] The supervision time point may refer to a specific moment or time point at which a user needs to back up or restore data according to data supervision requirements.

[0077] It can be seen that in this embodiment, backup data is obtained by updating on demand to ensure that backup operations are performed only when actually needed, avoiding invalid frequent backups, thereby improving system efficiency and saving storage resources; by including backup data at regulatory time points, it can be ensured that data backup meets regulatory requirements, ensure that the status of data at a specific time point is accurately recorded, ensure compliance with compliance requirements, and enhance the traceability and compliance of data recovery.

[0078] In some embodiments, the backup configuration information includes: a correspondence between database proxy nodes and source data nodes to be backed up.

[0079] Specifically, the corresponding relationship between the database proxy node and the source data node with backup can refer to

[0080] It can be seen that in this embodiment, by clarifying the correspondence between the database proxy node and the source data node, it can ensure that the backup task is accurately assigned to the correct node for execution, avoiding the backup data from being mistakenly stored in irrelevant nodes, thereby improving the efficiency and accuracy of the backup process.

[0081] In some embodiments, after storing the backup data in the proxy data node, the method further includes:

[0082] Receive recovery tasks sent by the management node;

[0083] When it is determined that the recovery task corresponds to the database proxy node, the backup configuration information is obtained;

[0084] The backup data corresponding to the recovery task is sent to the source data node corresponding to the backup configuration information for storage.

[0085] The recovery task may refer to the process of restoring a database or data node based on previously backed-up data when data is lost or damaged. The goal of the recovery task is to restore the data to the state at the time of the backup.

[0086] In a specific example, in a distributed database, when executing a recovery task, in order to ensure the consistency of transactions, it can be achieved in the following way: dependent files include active transaction files, data files and log files, wherein the active transaction file can be a file with the maximum GTID (GlobalTransaction Identifier) ​​for periodically recording the active transactions and consistency moments of the distributed system, and the active transaction can refer to an uncommitted distributed transaction; the data file can refer to a data file backed up by a database node; the log file can refer to a log file backed up by a database node. The recovery time is reset to the active transaction time, and after the end time of the database node backup data record, the ddbbinlog tool is used to apply the data to the specified time point through the log file; before the end time of the database node backup data record, the ddbbinlog tool is used to generate a reverse log file, and the log file is used to apply the data to the specified time point. After each database node is restored to the consistency moment through the data and binlog, the active transaction at that time needs to be processed, and the database node does not filter the transaction, but has the transaction rollback. After recovery to the consistency moment, the active transactions recorded in the active transaction file are parsed through ddbbinlog to generate reverse SQL, which is then executed on the database node.

[0087] It can be seen that in this embodiment, by matching between the recovery task and the database proxy node, it can ensure that the recovery task is only executed on the corresponding node, avoid the task being erroneously sent to irrelevant nodes, and ensure the accuracy of the recovery process; by accurately sending the recovery data to the specified source data node, it can ensure that the recovery operation will correctly restore the data to the expected location, ensure data consistency and integrity, and thus avoid data loss or damage caused by erroneous recovery.

[0088] In some embodiments, the database proxy node and the management node belong to a distributed storage system.

[0089] It can be seen that in this embodiment, by incorporating the database proxy node and the management node into the distributed storage system, distributed management and processing of data can be achieved, thereby improving the scalability and fault tolerance of the data backup method provided by the embodiment of the present invention.

[0090] In a specific example, Figure 3A schematic diagram of a data backup and data recovery method provided for an embodiment of the present invention, wherein storage configuration may refer to backup configuration information, and the user configures the storage configuration for each node of the distributed database cluster according to actual conditions, supporting one configuration for a distributed cluster, different configurations for each shard, different configurations for each computer room, and different configurations for each database node. The user can use a graphical user interface to send the configured storage configuration to each database node through a management node and load it; the graphical interface may refer to a unified entry for users to manage distributed database storage configurations, providing the functions of importing, viewing, updating, and deleting storage configurations, and the user can operate this module with one click, and the user's operations through the graphical interface are converted into instructions, which are sent to the management node after verification, and the information summarized by the management node is received, and the details of the results of the distributed database backup and recovery are displayed on the graphical interface; the management node is used to interact with each database node, send the storage configuration plug-in to each node, and the management node receives instructions from the graphical interface, It includes adding, updating and deleting configuration plug-ins, and sending them to each node for execution. The execution results are summarized and returned to the graphical interface. The management node sends database backup and recovery tasks to each node for execution, and the execution results are summarized and returned to the graphical interface for display. The database agent is integrated on each node of the distributed database. An agent module is deployed on each node. The module is used to receive various tasks sent by the management node, load the newly added configuration plug-in, replace the configuration plug-in that stores the update, and delete the configuration plug-in to be deleted. For the backup tasks sent by the management node, the agent module uploads the backed-up data to the specified storage according to the configuration plug-in. For the recovery tasks sent by the management node, the agent module will download the data from the specified storage according to the configuration plug-in for recovery, and use the consistency algorithm to enable the large-scale cluster of distributed databases to be easily and quickly restored to the consistency moment.

[0091] Figure 4 A structural diagram of a data backup device provided by an embodiment of the present invention. The embodiment of the present invention is applicable to data backup situations, the device can execute a data backup method, and the device can be implemented in the form of hardware and / or software.

[0092] See also Figure 4 The data backup device shown includes: a backup task receiving module 401, a configuration information obtaining module 402, a backup data obtaining module 403 and a backup data storage module 404, wherein:

[0093] A backup task receiving module, used to receive the backup tasks sent by the management node;

[0094] A configuration information acquisition module, used to acquire backup configuration information when it is determined that the backup task corresponds to the database proxy node;

[0095] A backup data acquisition module, used to acquire the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information at the time corresponding to the backup task;

[0096] The backup data storage module is used to store the backup data in the proxy data node.

[0097] The technical solution of the embodiment of the present invention can realize unified scheduling and management of backup tasks by receiving backup tasks sent by the management node, thereby improving the collaborative efficiency of data backup; by obtaining backup configuration information when the backup task corresponds to the proxy node, it can ensure the correctness and pertinence of the backup task and avoid erroneous data backup; by obtaining the backup data stored in the source data node at a specified time, it can realize timely backup of data and ensure the real-time and integrity of the data; by storing the backup data in the proxy data node, it can realize secure storage and distributed backup of data, thereby improving the processing speed of data backup and data recovery.

[0098] In some embodiments, in determining the correspondence between the backup task and the database proxy node, the configuration information acquisition module 402 is specifically used to:

[0099] When the backup task includes a specified range, obtain the node level corresponding to the specified range; wherein the specified node level includes: cluster level, shard level, computer room level and node level;

[0100] Get the node range to which the database proxy node belongs in the node level;

[0101] Check whether the node range is consistent with the specified range;

[0102] When the node range is consistent with the specified range, it is determined that the backup task corresponds to the database proxy node.

[0103] In some embodiments, at the time corresponding to the backup task, in terms of obtaining the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information, the backup data obtaining module 403 is specifically used to:

[0104] When the update mode corresponding to the backup task is periodic update, the timer starts;

[0105] When the timing duration reaches the period corresponding to the backup task, it is determined that the time corresponding to the backup task has arrived, and the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information is obtained.

[0106] In some embodiments, at the time corresponding to the backup task, in terms of obtaining the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information, the backup data obtaining module 403 is specifically used to:

[0107] When the update mode corresponding to the backup task is demand update, determine the time corresponding to the backup task, and obtain the backup data corresponding to the backup task stored in the source data node corresponding to the backup configuration information; the backup data corresponding to the backup task includes the backup data corresponding to the supervision time point.

[0108] In some embodiments, in terms of backing up configuration information, the configuration information acquisition module 402 is specifically used to:

[0109] The correspondence between the database proxy nodes and the source data nodes to be backed up.

[0110] In some embodiments, after storing the backup data in the proxy data node, the backup data storage module 404 is further specifically configured to:

[0111] Receive recovery tasks sent by the management node;

[0112] When it is determined that the recovery task corresponds to the database proxy node, the backup configuration information is obtained;

[0113] The backup data corresponding to the recovery task is sent to the source data node corresponding to the backup configuration information for storage.

[0114] In some embodiments, the database proxy node and the management node belong to a distributed storage system.

[0115] The data backup device provided in the embodiment of the present invention can execute the data backup method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the data backup method.

[0116] Figure 5 A schematic diagram of the structure of a data backup device provided by an embodiment of the present invention.

[0117] like Figure 5 As shown, the data backup device 500 includes at least one processor 501, and a memory connected to the at least one processor 501, such as a read-only memory (ROM) 502, a random access memory (RAM) 503, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 501 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 502 or the computer program loaded from the storage unit 508 to the random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the data backup device 500 can also be stored. The processor 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 508 is also connected to the bus 504.

[0118] Multiple components in the data backup device 500 are connected to the I / O interface 505, including: an input unit 506, such as a keyboard, a mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a disk, an optical disk, etc.; and a communication unit 509, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 509 allows the data backup device 500 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0119] The processor 501 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 501 executes the various methods and processes described above, such as a data backup method.

[0120] In some embodiments, the data backup method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on the data backup device 500 via the ROM 502 and / or the communication unit 509. When the computer program is loaded into the RAM 503 and executed by the processor 501, one or more steps of the data backup method described above may be performed. Alternatively, in other embodiments, the processor 501 may be configured to perform the data backup method in any other appropriate manner (e.g., by means of firmware).

[0121] Various implementations of the systems and techniques described above herein 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), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including 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.

[0122] 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, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0123] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

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

[0125] The systems and techniques described herein may be implemented in a computing system that includes backend 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 frontend components (e.g., a user computer with a graphical user interface or a 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 backend components, middleware components, or frontend components. The components of the system may 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.

[0126] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS (Virtual Private Server) services.

[0127] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0128] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A data backup method, characterized in that: Applied to a database proxy node, the method includes: Receive backup tasks sent by the management node; When it is determined that the backup task corresponds to the database proxy node, acquiring backup configuration information; At a time corresponding to the backup task, acquiring backup data corresponding to the backup task and stored in a source data node corresponding to the backup configuration information; The backup data is stored in the proxy data node.

2. The method according to claim 1, characterized in that The determining that the backup task corresponds to the database proxy node includes: When the backup task includes a specified range, obtaining a node level corresponding to the specified range; wherein the specified node level includes: cluster level, shard level, computer room level and node level; Obtaining the node range to which the database proxy node belongs in the node level; Check whether the node range is consistent with the specified range; When the node range is consistent with the specified range, it is determined that the backup task corresponds to the database proxy node.

3. The method according to claim 1, characterized in that At a time corresponding to the backup task, acquiring backup data corresponding to the backup task and stored in a source data node corresponding to the backup configuration information, including: When the update mode corresponding to the backup task is periodic update, start timing; When the timing duration reaches the period corresponding to the backup task, it is determined that the time corresponding to the backup task has arrived, and the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information is obtained.

4. The method according to claim 1, characterized in that: At a time corresponding to the backup task, acquiring backup data corresponding to the backup task and stored in a source data node corresponding to the backup configuration information, including: When the update mode corresponding to the backup task is demand update, determine the time when the backup task arrives, and obtain the backup data corresponding to the backup task stored in the source data node corresponding to the backup configuration information; the backup data corresponding to the backup task includes the backup data corresponding to the supervision time point.

5. The method according to claim 1, characterized in that The backup configuration information includes: a correspondence between database proxy nodes and source data nodes to be backed up.

6. The method according to claim 1, characterized in that After storing the backup data in the proxy data node, the method further includes: Receiving the recovery task sent by the management node; When it is determined that the recovery task corresponds to the database proxy node, acquiring backup configuration information; The backup data corresponding to the recovery task is sent to the source data node corresponding to the backup configuration information for storage.

7. The method according to claim 1, characterized in that The database proxy node and the management node belong to a distributed storage system.

8. A data backup device, characterized in that: include: A backup task receiving module, used to receive the backup tasks sent by the management node; A configuration information acquisition module, configured to acquire backup configuration information when it is determined that the backup task corresponds to the database proxy node; A backup data acquisition module, used to acquire, at a time corresponding to the backup task, the backup data corresponding to the backup task and stored in the source data node corresponding to the backup configuration information; The backup data storage module is used to store the backup data in the proxy data node.

9. A data backup device, characterized in that: The data backup 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 backup 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 backup method according to any one of claims 1 to 7 when executed.

Images