CN115934414A - Data backup method, data recovery method, device, equipment and storage medium - Google Patents
Data backup method, data recovery method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115934414A CN115934414A CN202211397283.9A CN202211397283A CN115934414A CN 115934414 A CN115934414 A CN 115934414A CN 202211397283 A CN202211397283 A CN 202211397283A CN 115934414 A CN115934414 A CN 115934414A
- Authority
- CN
- China
- Prior art keywords
- data
- backup
- request
- target data
- storage
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 76
- 238000011084 recovery Methods 0.000 title claims description 79
- 230000001960 triggered effect Effects 0.000 claims abstract description 23
- 230000008569 process Effects 0.000 claims abstract description 17
- 238000012545 processing Methods 0.000 claims description 43
- 238000004590 computer program Methods 0.000 claims description 14
- 238000007906 compression Methods 0.000 claims description 7
- 230000006837 decompression Effects 0.000 claims description 6
- 230000006835 compression Effects 0.000 claims description 5
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 206010063385 Intellectualisation Diseases 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the disclosure provides a data backup method. The method comprises the following steps: sending a backup request to each storage node of the distributed database based on backup operation triggered by a user; the backup request carries data address information, and a corresponding relation between a storage node and an object cache node; receiving target data returned by each storage node; the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node; and sending the target data to a cloud storage for backup. By using the method, in the process of data backup, the data is backed up to the cloud storage through the object cache node, so that the data backup efficiency of the distributed database is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of databases, in particular to a data backup method, a data recovery method, a data backup device, a data recovery device, equipment and a storage medium.
Background
Today, mass data are generated every day in digitalization, intellectualization and informatization, and the processing capacity of a traditional database for the mass data reaches a bottleneck, so that a plurality of distributed databases are generated.
Compared with the traditional database, the distributed database stores data in a plurality of nodes to improve the performance of the database. The distributed database has the advantages that data are dispersed in each node, backed-up data are also distributed in disks of each node, and the data need to be aggregated into complete backup data during recovery, so that great inconvenience is brought to recovery, and particularly, the distributed database is a quite long process under the conditions of numerous nodes and extremely large data volume.
Disclosure of Invention
Embodiments of the present invention provide a data backup method, a data recovery method, an apparatus, a device, and a storage medium, which can improve data backup and recovery efficiency of a distributed database.
In a first aspect, an embodiment of the present disclosure provides a data backup method, where the method includes:
sending a backup request to each storage node of the distributed database based on backup operation triggered by a user; the backup request carries data address information, and a corresponding relation between a storage node and an object cache node;
receiving target data returned by each storage node; the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node;
and sending the target data to a cloud storage for backup.
In a second aspect, an embodiment of the present disclosure further provides a data recovery method, where the method includes:
generating a recovery request based on a user-triggered recovery operation;
acquiring target data from a cloud server according to the recovery request;
and restoring the target data to the storage nodes in the distributed database according to the restoring request.
In a third aspect, an embodiment of the present disclosure further provides a data backup apparatus, where the apparatus includes:
the request sending module is used for sending backup requests to all storage nodes of the distributed database based on backup operation triggered by a user; the backup request carries data address information, and a corresponding relation between a storage node and an object cache node;
the data receiving module is used for receiving the target data returned by each storage node; the target data are acquired by the storage node according to the data address information and are sent to the corresponding object cache nodes;
and the data backup module is used for sending the target data to a cloud storage for backup.
In a fourth aspect, an embodiment of the present disclosure further provides a data recovery apparatus, where the apparatus includes:
the request generation module is used for generating a recovery request based on recovery operation triggered by a user;
the data acquisition module is used for acquiring target data from the cloud server according to the recovery request;
and the data recovery module is used for recovering the target data to the storage nodes in the distributed database according to the recovery request.
In a fifth aspect, an embodiment of the present disclosure further provides an electronic device, including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the data backup method or the data recovery method provided by the embodiments of the present disclosure.
In a sixth aspect, the present disclosure also provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are used to implement the data backup method or the data recovery method provided by the present disclosure.
The embodiment of the disclosure provides a data backup method, a data recovery method, a device, equipment and a storage medium, wherein a backup request is sent to each storage node of a distributed database through a backup operation based on user triggering; the backup request carries data address information, and a corresponding relation between a storage node and an object cache node; receiving target data returned by each storage node; the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node; and sending the target data to a cloud storage for backup. By using the method, in the process of data backup, the data is backed up to the cloud storage through the object cache node, so that the data backup efficiency of the distributed database is improved.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
Fig. 1 is a schematic flow chart of a data backup method according to an embodiment of the present disclosure.
Fig. 2 is a schematic flow chart of a data recovery method provided in an embodiment of the present disclosure;
fig. 3 is a schematic flow chart of a data backup and recovery method according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart of a data backup and recovery method provided by an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a data backup device according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a data recovery apparatus according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence of the functions performed by the devices, modules or units.
It is noted that references to "a" or "an" in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will appreciate that references to "one or more" are intended to be exemplary and not limiting unless the context clearly indicates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
It is understood that before the technical solutions disclosed in the embodiments of the present disclosure are used, the type, the use range, the use scene, etc. of the personal information related to the present disclosure should be informed to the user and obtain the authorization of the user through a proper manner according to the relevant laws and regulations.
For example, in response to receiving an active request from a user, a prompt message is sent to the user to explicitly prompt the user that the requested operation to be performed would require the acquisition and use of personal information to the user. Thus, the user can autonomously select whether to provide personal information to software or hardware such as an electronic device, an application program, a server, or a storage medium that performs the operations of the disclosed technical solution, according to the prompt information.
As an optional but non-limiting implementation manner, in response to receiving an active request from the user, the manner of sending the prompt information to the user may be, for example, a pop-up window, and the prompt information may be presented in a text manner in the pop-up window. In addition, a selection control for providing personal information to the electronic device by the user's selection of "agreeing" or "disagreeing" can be carried in the pop-up window.
It is understood that the above notification and user authorization process is only illustrative and not limiting, and other ways of satisfying relevant laws and regulations may be applied to the implementation of the present disclosure.
It will be appreciated that the data involved in the subject technology, including but not limited to the data itself, the acquisition or use of the data, should comply with the requirements of the corresponding laws and regulations and related regulations.
Example one
Fig. 1 is a schematic flow chart of a data backup method provided by an embodiment of the present disclosure, where the embodiment of the present disclosure is applicable to a data backup situation, and the method may be executed by a data backup apparatus, where the apparatus may be implemented in a form of software and/or hardware, and optionally implemented by an electronic device, where the electronic device may be a mobile terminal, a PC terminal, or a server.
As shown in fig. 1, a data backup method provided in the embodiment of the present disclosure may specifically include the following steps:
s110, sending a backup request to each storage node of the distributed database based on backup operation triggered by a user; the backup request carries data address information, and the corresponding relation between the storage node and the object cache node.
In this embodiment, the storage node is a storage component of a distributed database, and generally has a plurality of storage nodes, and is responsible for storing and managing data in the database. The data address information contains data to be backed up and address information of the backup data in the storage node. The object cache node (hereinafter, referred to as cache node) is an integrated terminal node, and may include a plurality of cache nodes, and the object cache node integrates a command line tool for backup recovery, an object memory, and a data processing tool. The command line tool is used for generating and sending data backup and recovery requests, the object memory is used for caching data, and the data processing tool can perform functions of limiting current, encrypting and decrypting, compressing, data checking, deleting and the like on the data.
Specifically, as shown in fig. 3, a user initiates a backup operation on a front-end page, a Server receives a backup recovery operation request and then sends the backup recovery operation request to a cache node, and a command line tool in the cache node initiates a backup request to each storage node. It should be noted that there may be a plurality of cache nodes, where the backup request carries data to be backed up, address information of the backup data in the storage node, and a correspondence between the storage node and the cache node.
On the basis of the above embodiment, the sending of the backup request to each storage node of the distributed database according to the backup operation triggered by the user may specifically be as follows:
a1 Obtain backup granularity based on a user-triggered backup operation.
The backup granularity may be data to be backed up, and the backup granularity may be all data in the entire database or a part of data in the database (e.g., page data or table data). And obtaining the data to be backed up according to the backup operation cache node triggered by the user.
b1 According to the backup granularity, data address information is obtained, and a corresponding relation between the storage node and the object cache node is established.
Specifically, the address information of each data is obtained according to the information in the backup granularity, and meanwhile, the corresponding relationship between the storage node and the cache node is established, and each cache node is responsible for a data sending request or a data reading request of a part of the storage nodes, that is, the corresponding relationship between the object cache node and the storage node may be a one-to-one or one-to-many relationship. As shown in fig. 4, when the data size is particularly large, the cache node may perform one-to-one data receiving service with the storage node.
c1 Generate a backup request based on the data address information and the object relationship.
Wherein, the data address information and the object relation are added to the backup request.
d1 Send backup requests to storage nodes of the distributed database.
Specifically, the backup request is sent to each storage node of the distributed database at the same time. After receiving the backup request, the storage node searches whether the storage node contains data to be backed up according to the backup request, and if so, the data is sent to a cache node corresponding to the storage node.
In the technical scheme, one cache node serves one or more storage nodes by dynamically adjusting the cache nodes, so that data in the whole cluster is distributed, and the backup speed and efficiency of the whole cluster are improved.
And S120, receiving the target data returned by each storage node.
And the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node.
Specifically, data on a storage node is read as target data according to the data address information in the backup request, and then the target data is sent to a corresponding cache node according to the corresponding relationship between the storage node and the object cache node through the s3 protocol.
And S130, sending the target data to a cloud storage for backup.
Specifically, the cache node sends the target data to a cloud storage, and the data is backed up and stored in the cloud storage. Alternatively, processing such as deduplication processing, compression processing, encryption processing, and the like may be performed on the target data.
The embodiment of the disclosure provides a data backup method. Sending a backup request to each storage node of the distributed database through a backup operation based on user triggering; the backup request carries data address information, and a corresponding relation between a storage node and an object cache node; receiving target data returned by each storage node; the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node; and sending the target data to a cloud storage for backup. In the technical scheme, in the data backup process, the data are backed up to the cloud storage through the object cache node, so that the data backup efficiency of the distributed database is improved. On the basis of the above embodiment, the sending of the backup request to each storage node of the distributed database according to the backup operation triggered by the user may specifically be as follows:
a2 ) performs processing on the target data for at least one of: deduplication processing, compression processing and encryption processing.
b2 Send the processed target data to the cloud storage for backup.
Specifically, the deduplication process is a deletion process of the duplicated data, the compression process is a compression process of the data, and the encryption process is an encryption process of the data. The cache node sends the target data to a data processing tool through a Linux pipeline technology, and after the tool receives the data and performs operations such as deduplication processing, compression processing and encryption processing on the data, the processed target data is sent to a cloud storage for backup.
Example two
Fig. 2 is a schematic flow chart of a data recovery method provided by an embodiment of the present disclosure, where the embodiment of the present disclosure is applicable to a data recovery situation, and the method may be executed by a data recovery apparatus, where the apparatus may be implemented in a form of software and/or hardware, and optionally implemented by an electronic device, where the electronic device may be a mobile terminal, a PC terminal, or a server.
S210, a recovery request is generated based on recovery operation triggered by a user. The recovery request carries data address information and data identification information.
Specifically, the data address information may be address information of data at the storage node. The data identification information may be identification information of the data, such as a name, a file name, and the like of the data for indicating that specific data is identified. As shown in fig. 3, a user initiates a recovery operation on a front-end page, a Server receives a recovery operation request and then sends the recovery operation request to a cache node, and a command line tool in the cache node initiates a recovery request to a cloud storage. The recovery request carries data address information and data identification information.
And S220, acquiring target data from the cloud server according to the recovery request.
Specifically, the cache node reads the target data from the cloud storage according to the recovery request. The cache node through which the target data is recovered can be selected according to the actual situation of the server and the set selection logic.
On the basis of the above embodiment, the embodiment of the present disclosure may specifically be that the obtaining of the target data from the cloud server according to the recovery request is:
in this embodiment, the process of obtaining the target data from the cloud server according to the data identification information may be understood as follows: and sending the data identification information to a cloud server, searching target data by the cloud server according to the data identification information, and returning the target data to the cache node.
And S230, restoring the target data to the storage nodes in the distributed database according to the restoring request.
On the basis of the foregoing embodiment, the embodiment of the present disclosure may specifically be that the restoring the target data to the storage node in the distributed database according to the restoring request is: and restoring the target data to the storage nodes in the distributed database according to the data address information.
Specifically, the cache node sends the target data to the corresponding storage node according to the data address information, and the storage node stores the target data to the corresponding position according to the data address information. Alternatively, processing such as decompression processing and decryption processing may be performed on the target data.
On the basis of the foregoing embodiment, the restoring the target data to the storage node in the distributed database according to the restoration request specifically includes the following steps:
a3 Performing at least one of the following processes on the target data: decompression processing and decryption processing.
b3 According to the recovery request, the processed target data is recovered to a storage node in the distributed database.
Specifically, the decompression processing is to decompress the target data, and the decryption processing is to decrypt the data. And the cache node sends the target data to a data processing tool in the node, so that the data processing tool recovers the processed target data to a storage node in the distributed database after carrying out operations such as decompression processing, decryption processing and the like on the received data.
According to the data recovery method provided by the embodiment of the disclosure, a recovery request is generated through recovery operation triggered by a user; acquiring target data from a cloud server according to the recovery request; and restoring the target data to the storage nodes in the distributed database according to the restoring request. In the technical scheme, in the process of data recovery, the database recovery scheme of horizontally expanding a plurality of object cache nodes can be performed, and the data recovery efficiency of the distributed database is improved.
EXAMPLE III
Fig. 5 is a schematic structural diagram of a data backup device according to an embodiment of the present disclosure, and as shown in fig. 5, the device includes: a request sending module 310, a data receiving module 320, and a data backup module 330.
A request sending module 310, configured to send a backup request to each storage node of the distributed database based on a backup operation triggered by a user; the backup request carries data address information, and a corresponding relation between a storage node and an object cache node;
a data receiving module 320, configured to receive target data returned by each storage node; the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node;
the data backup module 330 is configured to send the target data to a cloud storage for backup.
According to the technical scheme provided by the embodiment of the disclosure, a backup request is sent to each storage node of a distributed database through backup operation triggered by a user; the backup request carries data address information, and a corresponding relation between a storage node and an object cache node; receiving target data returned by each storage node; the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node; and sending the target data to a cloud storage for backup. By using the method, the database backup scheme of horizontally expanding a plurality of object cache nodes can be carried out in the data backup process, and the data backup efficiency of the distributed database is improved.
Further, the request sending module 310 may be configured to:
acquiring backup granularity based on backup operation triggered by a user;
acquiring data address information according to the backup granularity, and establishing a corresponding relation between a storage node and an object cache node;
generating a backup request according to the data address information and the object relation;
and sending the backup request to each storage node of the distributed database.
Further, the data backup module 330 may be configured to:
performing processing on the target data for at least one of: deduplication processing, compression processing and encryption processing;
and sending the processed target data to a cloud storage for backup.
Example four
Fig. 6 is a schematic structural diagram of a data recovery apparatus according to an embodiment of the disclosure. As shown in fig. 6, the apparatus includes: a request generation module 410, a data acquisition module 420, and a data recovery module 430.
A request generation module 410, configured to generate a recovery request based on a recovery operation triggered by a user;
a data obtaining module 420, configured to obtain target data from a cloud server according to the recovery request;
the data recovery module 430 is configured to recover the target data to a storage node in the distributed database according to the recovery request.
According to the technical scheme provided by the embodiment of the disclosure, a recovery request is generated through recovery operation triggered by a user; acquiring target data from a cloud server according to the recovery request; and restoring the target data to the storage nodes in the distributed database according to the restoring request. In the technical scheme, in the process of data recovery, the database recovery scheme of horizontally expanding a plurality of object cache nodes can be performed, and the data recovery efficiency of the distributed database is improved.
Further, the data recovery module 430 may be configured to:
performing at least one of the following processes on the target data: decompression processing and decryption processing;
and restoring the processed target data to the storage nodes in the distributed database according to the restoring request.
It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are also only used for distinguishing one functional unit from another, and are not used for limiting the protection scope of the embodiments of the present disclosure.
EXAMPLE five
FIG. 7 illustrates a schematic diagram of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 6, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 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, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as a data backup method or a data restore method.
In some embodiments, the data backup method or the data recovery method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the above described method of area division of a photovoltaic power plant may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the data backup method or the data recovery method by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program 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, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic 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 a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, 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 may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, 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: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired result of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for data backup, comprising:
sending a backup request to each storage node of the distributed database based on backup operation triggered by a user; the backup request carries data address information, and a corresponding relation between a storage node and an object cache node;
receiving target data returned by each storage node; the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node;
and sending the target data to a cloud storage for backup.
2. The method of claim 1, wherein sending a backup request to storage nodes of the distributed database based on a user-triggered backup operation comprises:
acquiring backup granularity based on backup operation triggered by a user;
acquiring data address information according to the backup granularity, and establishing a corresponding relation between a storage node and an object cache node;
generating a backup request according to the data address information and the object relation;
and sending the backup request to each storage node of the distributed database.
3. The method of claim 1, wherein sending the target data to a cloud storage for backup comprises:
performing processing on the target data for at least one of: deduplication processing, compression processing and encryption processing;
and sending the processed target data to a cloud storage for backup.
4. A method for data recovery, comprising:
generating a recovery request based on a recovery operation triggered by a user;
acquiring target data from a cloud server according to the recovery request;
and restoring the target data to the storage nodes in the distributed database according to the restoring request.
5. The method of claim 4, wherein the recovery request carries data address information and data identification information;
acquiring target data from a cloud server according to the recovery request, wherein the acquisition comprises the following steps:
acquiring target data from a cloud server according to the data identification information;
restoring the target data to a storage node in a distributed database according to the restoration request, comprising:
and restoring the target data to a storage node in a distributed database according to the data address information.
6. The method of claim 4, wherein restoring the target data to storage nodes in a distributed database according to the restore request comprises:
performing at least one of the following processes on the target data: decompression processing and decryption processing;
and restoring the processed target data to the storage nodes in the distributed database according to the restoring request.
7. A data backup apparatus, comprising:
the request sending module is used for sending a backup request to each storage node of the distributed database based on backup operation triggered by a user; the backup request carries data address information and a corresponding relation between a storage node and an object cache node;
the data receiving module is used for receiving the target data returned by each storage node; the target data is acquired by the storage node according to the data address information and is sent to the corresponding object cache node;
and the data backup module is used for sending the target data to a cloud storage for backup.
8. A data recovery apparatus, comprising:
the request generation module is used for generating a recovery request based on recovery operation triggered by a user;
the data acquisition module is used for acquiring target data from the cloud server according to the recovery request;
and the data recovery module is used for recovering the target data to the storage nodes in the distributed database according to the recovery request.
9. An electronic device, characterized in that the electronic device comprises:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the data backup method of any one of claims 1-3 or the data restore method of any one of claims 4-6.
10. A computer-readable storage medium storing computer instructions for causing a processor to implement the data backup method of any one of claims 1 to 3 or the data restoration method of any one of claims 4 to 6 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211397283.9A CN115934414A (en) | 2022-11-09 | 2022-11-09 | Data backup method, data recovery method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211397283.9A CN115934414A (en) | 2022-11-09 | 2022-11-09 | Data backup method, data recovery method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115934414A true CN115934414A (en) | 2023-04-07 |
Family
ID=86649842
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211397283.9A Pending CN115934414A (en) | 2022-11-09 | 2022-11-09 | Data backup method, data recovery method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115934414A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116701053A (en) * | 2023-05-30 | 2023-09-05 | 杭州政云数据技术有限公司 | Method, device, equipment and medium for restoring data backup of production environment database |
| CN116881052A (en) * | 2023-09-07 | 2023-10-13 | 上海凯翔信息科技有限公司 | Data restoration system for distributed storage |
-
2022
- 2022-11-09 CN CN202211397283.9A patent/CN115934414A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116701053A (en) * | 2023-05-30 | 2023-09-05 | 杭州政云数据技术有限公司 | Method, device, equipment and medium for restoring data backup of production environment database |
| CN116701053B (en) * | 2023-05-30 | 2024-03-19 | 杭州政云数据技术有限公司 | Method, device, equipment and medium for restoring data backup of production environment database |
| CN116881052A (en) * | 2023-09-07 | 2023-10-13 | 上海凯翔信息科技有限公司 | Data restoration system for distributed storage |
| CN116881052B (en) * | 2023-09-07 | 2023-11-24 | 上海凯翔信息科技有限公司 | Data restoration system for distributed storage |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022126974A1 (en) | Kafka-based incremental data synchronization method and apparatus, device, and medium | |
| CN115934414A (en) | Data backup method, data recovery method, device, equipment and storage medium | |
| CN109144785B (en) | Method and apparatus for backing up data | |
| US20190317872A1 (en) | Database cluster architecture based on dual port solid state disk | |
| CN103716384A (en) | Method and device for realizing cloud storage data synchronization in cross-data-center manner | |
| KR20210102121A (en) | Information processing method, apparatus, device, and readable storage medium | |
| CN111338834B (en) | Data storage method and device | |
| CN113254267B (en) | Data backup method and device for distributed database | |
| CN109947736B (en) | Method and system for real-time computing | |
| US20230161664A1 (en) | Method of responding to operation, electronic device, and storage medium | |
| CN115086347B (en) | Data synchronization method, device, electronic equipment and storage medium | |
| CN112148705A (en) | Data migration method and device | |
| CN115510036A (en) | Data migration method, device, equipment and storage medium | |
| JP7307766B2 (en) | Traffic adjustment method, apparatus, electronic equipment, computer readable recording medium and computer program | |
| CN113448767B (en) | Distributed transaction database recovery method, device, equipment and storage medium | |
| CN115190125A (en) | Monitoring method and device for cache cluster | |
| CN114500443A (en) | Message pushing method, device, system, electronic equipment and storage medium | |
| CN109766363B (en) | Streaming data processing method, system, electronic device and storage medium | |
| CN110768855B (en) | Method and device for testing linkmzation performance | |
| CN108196979B (en) | Data backup method and device | |
| CN112235332A (en) | Read-write switching method and device for cluster | |
| CN118503298B (en) | Data processing method, device, equipment and storage medium based on double caches | |
| CN116860518A (en) | Data backup method, data recovery method, device, equipment and storage medium | |
| CN117056133B (en) | Data backup method, device and medium based on distributed Internet of things architecture | |
| CN115794485A (en) | Data recovery method, device, equipment and storage medium based on disaster recovery backup |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |