WO2022057028A1 - 一种数据库远程备份方法、装置和云端服务器 - Google Patents
一种数据库远程备份方法、装置和云端服务器 Download PDFInfo
- Publication number
- WO2022057028A1 WO2022057028A1 PCT/CN2020/125261 CN2020125261W WO2022057028A1 WO 2022057028 A1 WO2022057028 A1 WO 2022057028A1 CN 2020125261 W CN2020125261 W CN 2020125261W WO 2022057028 A1 WO2022057028 A1 WO 2022057028A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- backed
- data
- backup
- cloud database
- label
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000012545 processing Methods 0.000 claims description 17
- 230000003190 augmentative effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 239000011521 glass Substances 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
Definitions
- the present disclosure relates to the technical field of databases, and in particular, to a database remote backup method, device and cloud server.
- the methods for remote backup of resource databases to be backed up for non-main nodes are mainly as follows: the database broadcasts to the terminal the relevant information of resources to be backed up for non-main nodes, and the relevant information for resources to be backed up for non-main nodes is broadcast to the terminal.
- the information includes the non-master node database information of each network (such as the number of sub-channels, the starting position of resource blocks in sub-channels, the size of sub-channels, etc.) and the network data labels to be backed up for each network.
- the user can perform data backup through the resources to be backed up for the non-primary node in the database of the non-primary node of the corresponding network.
- the purpose of the present disclosure is to provide a database remote backup method, device and cloud server.
- the present disclosure provides a database remote backup method, the method comprising:
- the cloud database receives the backup request notification sent by the client, and the backup request notification includes the tag of the data to be backed up;
- the cloud database determines a first data label to be backed up that is different from the data label to be backed up in the at least one backup request notification received in the first time domain, where the end time of the first time domain is the end time of the cloud database. The moment when the backup of the data to be backed up is completed;
- the cloud database sends a first backup request notification, where the first backup request notification includes the first data label to be backed up and the data label to be backed up of the target end of the data to be backed up in the cloud database;
- the cloud database receives, from the backup node device, indication information of a first resource backed up based on the label of the first data to be backed up, where the first resource is used by the cloud database to send the data to be backed up.
- the present disclosure provides a database remote backup device, the device includes a receiving unit, a processing unit, and a sending unit:
- the receiving unit is configured to receive a backup request notification sent by the client, where the backup request notification includes a tag of data to be backed up;
- the processing unit is configured to determine a first data label to be backed up that is different from the data label to be backed up in the at least one backup request notification received in the first time domain, where the end time of the first time domain is the cloud database The time when the backup of the data to be backed up is completed;
- the sending unit is configured to send a first backup request notification, where the first backup request notification includes the first data label to be backed up and the data label to be backed up of the target end of the data to be backed up in the cloud database; and sending the first data tag to be backed up by the backup node device;
- the receiving unit is further configured to receive, from the backup node device, indication information of a first resource allocated based on the label of the first data to be backed up, where the first resource is used by the cloud database to send the to-be-backed up data tag. Backup data.
- embodiments of the present disclosure provide a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, which, when executed, cause a computer to execute the first aspect or any possible design of the first aspect
- the database remote backup method in is a third aspect.
- an embodiment of the present disclosure further provides a cloud server, where the cloud server includes a processor, a machine-readable storage medium, and a network interface, wherein the machine-readable storage medium, the network interface, and the processor are among the They are connected through a bus system, the network interface is used to communicate with at least one client, the machine-readable storage medium is used to store programs, instructions or codes, and the processor is used to execute the machine-readable storage medium.
- the present disclosure can send the second backup request notification through the above method when the requesting device belongs to the target end of the data to be backed up in the cloud database, informing the client of all the data determined by the cloud database.
- the first data tag to be backed up is used to ensure that the client that receives the notification of the second backup request will not use the first data tag to be backed up.
- the backup node device performs the backup work of the resources to be backed up for different clients, which can reduce the probability of backup errors performed by the non-primary node. And no additional operation by the user is required, which improves the user experience.
- FIG. 1 is a schematic diagram of an application scenario of a database remote backup system provided by an embodiment of the present disclosure
- FIG. 2 is a schematic flowchart of a database remote backup method provided by an embodiment of the present disclosure
- FIG. 3 is a schematic diagram of functional modules of a database remote backup device provided by an embodiment of the present disclosure
- FIG. 4 is a schematic structural block diagram of a cloud server for implementing the above-mentioned database remote backup method according to an embodiment of the present disclosure.
- FIG. 1 is an interactive schematic diagram of a database remote backup system 10 provided by an embodiment of the present disclosure.
- the database remote backup system 10 may include a cloud server 100 and a client 200 in communication with the cloud server 100 .
- the database remote backup system 10 shown in FIG. 1 is only a feasible example, and in other feasible embodiments, the database remote backup system 10 may also include only a part of the components shown in FIG. 1 or may also include other Part.
- the client 200 may include a mobile device, a tablet computer, a laptop computer, etc., or any combination thereof.
- mobile devices may include smart home devices, wearable devices, smart mobile devices, virtual reality devices, or augmented reality devices, etc., or any combination thereof.
- the smart home devices may include control devices of smart electrical devices, smart monitoring devices, smart TVs, smart cameras, etc., or any combination thereof.
- the wearable device may include a smart bracelet, smart shoelaces, smart glass, smart helmets, smart watches, smart clothing, smart backpacks, smart accessories, etc., or any combination thereof.
- a smart mobile device may include a smartphone, a personal digital assistant, a gaming device, etc., or any combination thereof.
- the virtual reality device and/or augmented reality device may include a virtual reality helmet, virtual reality glass, virtual reality patch, augmented reality helmet, augmented reality glass, or augmented reality patch, etc., or any combination thereof.
- virtual reality devices and/or augmented reality devices may include various virtual reality products and the like.
- the cloud server 100 and the client 200 in the database remote backup system 10 can cooperate to execute the database remote backup method described in the following method embodiments.
- the specific execution steps of the cloud server 100 and the client 200 please refer to the following Detailed description of method embodiments.
- FIG. 2 is a schematic flowchart of a database remote backup method provided by an embodiment of the present disclosure.
- the database remote backup method provided by this embodiment can be executed by the cloud server 100 shown in FIG. 1 .
- the remote backup method of the database will be introduced in detail.
- Step S110 the cloud database receives a backup request notification sent by the client, where the backup request notification includes a tag of data to be backed up;
- Step S120 the cloud database determines a first data label to be backed up that is different from the data label to be backed up in the at least one backup request notification received in the first time domain, wherein the end time of the first time domain is the The moment when the backup data of the cloud database to be backed up is completed;
- Step S130 the cloud database sends a first backup request notification, and the first backup request notification includes the first data label to be backed up and the data label to be backed up of the target end of the data to be backed up in the cloud database;
- Step S140 the cloud database sends the first data tag to be backed up to the backup node device
- Step S150 the cloud database receives, from the backup node device, indication information of a first resource backed up based on the label of the first data to be backed up, where the first resource is used by the cloud database to send the to-be-backed up data data.
- step S140 further includes:
- Step S141 the cloud database sends a first request to the backup node device, where the first request carries the first data tag to be backed up, and the first request is used to request the backup node device for a non-master node resources to be backed up.
- step S140 further includes:
- Step S142 When the request condition is satisfied, the cloud database sends the first data tag to be backed up to the backup node device; wherein the request condition includes at least one of the following conditions:
- the second time domain is greater than or equal to the first time threshold, and the second time domain is the time interval from the time when the cloud database sent the label of the data to be backed up to the backup node device last time to the current time;
- the first data label to be backed up is different from the second data label to be backed up, and the second data label to be backed up is the data label to be backed up sent by the cloud database to the backup node device last time.
- step S120 further includes:
- Step S121 the cloud database selects the first data tag to be backed up that is different from the data tag to be backed up in the at least one backup request notification from the set of data tags to be backed up, and the data tag in the at least one backup request notification is selected.
- the data labels to be backed up belong to the data label set to be backed up.
- the first backup request notification is further used to indicate at least one of the following information: a backup type of the cloud database, and a data tag of the cloud database to be backed up.
- the database remote backup device 300 can be divided into functional modules according to the method embodiment executed by the cloud server 100, that is, the database
- the following functional modules corresponding to the remote backup device 300 can be used to execute the various method embodiments executed by the cloud server 100 above.
- the database remote backup device 300 may include a receiving unit 310 , a processing unit 320 and a sending unit 330 . The functions of each functional module of the database remote backup device 300 are described in detail below.
- the receiving unit 310 may be configured to perform the above step S110, that is, configured to receive a backup request notification sent by the client, where the backup request notification includes a tag of data to be backed up. and is further configured to receive, from the backup node device, indication information of a first resource allocated based on the label of the first data to be backed up, wherein the first resource is used for the cloud database to send the data to be backed up.
- the processing unit 320 may be configured to perform the above step S120, that is, to determine a first data label to be backed up that is different from the data label to be backed up in the at least one backup request notification received in the first time domain, wherein the first data label to be backed up is different.
- the end time of the time domain is the time when the backup of the data to be backed up in the cloud database is completed.
- the sending unit 330 may be configured to perform the above-mentioned step S130, that is, to send a first backup request notification, where the first backup request notification includes the label of the first data to be backed up and the target of the data to be backed up in the cloud database and sending the first data label to be backed up to the backup node device.
- each module of the above apparatus is only a division of logical functions, and may be fully or partially integrated into a physical entity in actual implementation, or may be physically separated.
- these modules can all be implemented in the form of software calling through processing elements; they can also all be implemented in hardware; some modules can also be implemented in the form of calling software through processing elements, and some modules can be implemented in hardware.
- the receiving unit 310 may be a separately established processing element, or may be integrated into a certain chip of the above-mentioned apparatus to realize, in addition, it may also be stored in the memory of the above-mentioned apparatus in the form of program code, and processed by one of the above-mentioned apparatuses
- the element calls and executes the functions of the above receiving unit 310 .
- the implementation of other modules is similar.
- all or part of these modules can be integrated together, and can also be implemented independently.
- the processing element described herein may be an integrated circuit with signal processing capabilities.
- each step of the above-mentioned method or each of the above-mentioned modules can be completed by an integrated logic circuit of hardware in the processor element or an instruction in the form of software.
- the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more specific integrated circuits (application specific integrated circuit, ASIC), or, one or more microprocessors (digital signal processor, DSP), or, or, one or more field programmable gate arrays (field programmable gate array, FPGA) and so on.
- ASIC application specific integrated circuit
- DSP digital signal processor
- FPGA field programmable gate array
- the processing element may be a general-purpose processor, such as a central processing unit (central processing unit). unit, CPU) or other processor that can invoke program code.
- these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).
- SOC system-on-a-chip
- FIG. 4 shows a schematic diagram of the hardware structure of a cloud server 100 for implementing the above-mentioned control device provided by an embodiment of the present disclosure.
- the cloud server 100 may include a processor 110 , a machine-readable storage medium 120 , and a bus 130 and transceiver 140.
- At least one processor 110 executes computer-executable instructions stored in the machine-readable storage medium 120 (for example, included in the database remote backup apparatus 300 shown in FIG. 3 ), so that the processor 110 can execute the above method
- the processor 110, the machine-readable storage medium 120 and the transceiver 140 are connected through the bus 130, and the processor 110 can be used to control the transceiver 140 to send and receive actions, so as to communicate with the aforementioned client 200 to send and receive data.
- the processor may be a central processing unit (English: Central Processing Unit, CPU), and may also be other general-purpose processors, digital signal processors (English: Digital Signal Processor, DSP), application-specific integrated circuits (English: Application Specific Integrated Circuit, ASIC) and so on.
- a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the invention can be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
- Machine-readable storage medium 120 may include high-speed RAM memory, and may also include non-volatile storage NVM, such as at least one disk storage.
- the bus 130 may be an industry standard architecture (Industry Standard Architecture, ISA) bus, Peripheral Component Interconnect (PCI) bus or Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus, etc.
- ISA Industry Standard Architecture
- PCI Peripheral Component Interconnect
- EISA Extended Industry Standard Architecture
- the bus 130 may be classified into an address bus, a data bus, a control bus, and the like.
- the buses in the drawings of the present application are not limited to only one bus or one type of bus.
- an embodiment of the present disclosure further provides a readable storage medium, where computer-executable instructions are stored in the readable storage medium, and when a processor executes the computer-executable instructions, the above method for remote database backup is implemented.
- the above-mentioned readable storage medium may be implemented by any type of volatile or non-volatile storage device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM) , Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic Disk or Optical Disk.
- SRAM Static Random Access Memory
- EEPROM Electrically Erasable Programmable Read-Only Memory
- EPROM Erasable Programmable Read Only Memory
- PROM Programmable Read Only Memory
- ROM Read Only Memory
- Magnetic Memory Flash Memory
- Magnetic Disk Magnetic Disk or Optical Disk.
- a readable storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
本发明提供一种数据库远程备份方法、装置和云端服务器，所述方法包括：云端数据库接收客户端发送的备份请求通知，之后，云端数据库需要确定与第一时域内接收到的至少一个备份请求通知中的待备份数据标签不同的第一待备份数据标签；并发送携带有第一待备份数据标签的第一备份请求通知；以及云端数据库向备份节点设备发送第一待备份数据标签。备份节点设备可以根据第一待备份数据标签和客户端上报的待备份数据标签为云端数据库备份用于非主节点的待备份资源。上述方法能够将客户端请求备份的数据备份到其他目标终端，无需用户额外操作，提升了用户体验。
Description
本公开涉及数据库技术领域，具体而言，涉及一种数据库远程备份方法、装置和云端服务器。
现有技术中，用于非主节点的待备份资源数据库远程备份的方式主要如下：数据库向终端广播用于非主节点的待备份资源的相关信息，用于非主节点的待备份资源的相关信息中包括每个网络的非主节点数据库信息(如子信道数量、子信道中资源块起始位置、子信道大小等)和每个网络的网络待备份数据标签，通过网络待备份数据标签可以确定出对应网络的非主节点数据库信息，用户就可以通过对应网络的非主节点数据库中的用于非主节点的待备份资源进行数据备份。
然而在上述过程中，由于需要寻求非主节点的其他数据节点，往往需要用户进行手动选择以进行后续的备份操作，很可能出现被分配的非主节点并不指向待备份资源的情况，导致用于非主节点的待备份资源在备份时产生错误，造成用户的使用体验降低。
为了至少克服现有技术中的上述不足，本公开的目的在于提供一种数据库远程备份方法、装置和云端服务器。
第一方面，本公开提供一种数据库远程备份方法，所述方法包括：
云端数据库接收客户端发送的备份请求通知，所述备份请求通知中包括待备份数据标签；
所述云端数据库确定与第一时域内接收到的至少一个备份请求通知中的待备份数据标签不同的第一待备份数据标签，其中，所述第一时域的结束时刻为所述云端数据库的待备份数据备份完成的时刻；
所述云端数据库发送第一备份请求通知，所述第一备份请求通知中包括所述第一待备份数据标签和所述云端数据库的待备份数据的目标端的待备份数据标签；
所述云端数据库向备份节点设备发送所述第一待备份数据标签；
所述云端数据库从所述备份节点设备接收基于所述第一待备份数据标签备份的第一资源的指示信息，其中，所述第一资源用于所述云端数据库发送所述待备份数据。
第二方面，本公开提供了一种数据库远程备份装置，所述装置包括接收单元、处理单元以及发送单元：
所述接收单元，用于接收客户端发送的备份请求通知，所述备份请求通知中包括待备份数据标签；
所述处理单元，用于确定与第一时域内接收到的至少一个备份请求通知中的待备份数据标签不同的第一待备份数据标签，其中，所述第一时域的结束时刻为云端数据库的待备份数据备份完成的时刻；
所述发送单元，用于发送第一备份请求通知，所述第一备份请求通知中包括所述第一待备份数据标签和所述云端数据库的待备份数据的目标端的待备份数据标签；以及向备份节点设备发送所述第一待备份数据标签；
所述接收单元，还用于从所述备份节点设备接收基于所述第一待备份数据标签分配的第一资源的指示信息，其中，所述第一资源用于所述云端数据库发送所述待备份数据。
第三方面，本公开实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当其被执行时，使得计算机执行上述第一方面或者第一方面中任意一个可能的设计中的数据库远程备份方法。
第四方面，本公开实施例还提供一种云端服务器，所述云端服务器包括处理器、机器可读存储介质和网络接口，所述机器可读存储介质、所述网络接口以及所述处理器之间通过总线系统相连，所述网络接口用于与至少一个客户端通信连接，所述机器可读存储介质用于存储程序、指令或代码，所述处理器用于执行所述机器可读存储介质中的程序、指令或代码，以执行第一方面或者第一方面中任意一个可能的设计中的数据库远程备份方法。
基于上述任意一个方面，本公开通过上述方法，在请求设备属于所述云端数据库的待备份数据的目标端的情况下，可以发送所述第二备份请求通知，告知客户端所述云端数据库确定的所述第一待备份数据标签，以保证接收到所述第二备份请求通知的客户端不会使用所述第一待备份数据标签，进一步的，当请求资源的多个终端设备上报的待备份数据标签不同时，所述备份节点设备为不同的客户端进行待备份资源的备份工作，可以减少非主节点进行备份错误的概率。且无需用户额外操作，提升了用户体验。
图1为本公开实施例提供的数据库远程备份系统的应用场景示意图；
图2为本公开实施例提供的数据库远程备份方法的流程示意图；
图3为本公开实施例提供的数据库远程备份装置的功能模块示意图；
图4为本公开实施例提供的用于实现上述的数据库远程备份方法的云端服务器的结构示意框图。
下面结合说明书附图对本公开进行具体说明，方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。
图1是本公开一种实施例提供的数据库远程备份系统10的交互示意图。数据库远程备份系统10可以包括云端服务器100以及与所述云端服务器100通信连接的客户端200。图1所示的数据库远程备份系统10仅为一种可行的示例，在其它可行的实施例中，该数据库远程备份系统10也可以仅包括图1所示组成部分的其中一部分或者还可以包括其它的组成部分。
本实施例中，客户端200可以包括移动设备、平板计算机、膝上型计算机等或其任意组合。在一些实施例中，移动设备可以包括智能家居设备、可穿戴设备、智能移动设备、虚拟现实设备、或增强现实设备等，或其任意组合。在一些实施例中，智能家居设备可以包括智能电器设备的控制设备、智能监控设备、智能电视、智能摄像机等，或其任意组合。在一些实施例中，可穿戴设备可包括智能手环、智能鞋带、智能玻璃、智能头盔、智能手表、智能服装、智能背包、智能配件等，或其任何组合。在一些实施例中，智能移动设备可以包括智能手机、个人数字助理、游戏设备等，或其任意组合。在一些实施例中，虚拟现实设备和/或增强现实设备可以包括虚拟现实头盔、虚拟现实玻璃、虚拟现实贴片、增强现实头盔、增强现实玻璃、或增强现实贴片等，或其任意组合。例如，虚拟现实设备和/或增强现实设备可以包括各种虚拟现实产品等。
本实施例中，数据库远程备份系统10中的云端服务器100和客户端200可以通过配合执行以下方法实施例所描述的数据库远程备份方法，具体云端服务器100和客户端200的执行步骤部分可以参照以下方法实施例的详细描述。
为了解决前述背景技术中的技术问题，图2为本公开实施例提供的数据库远程备份方法的流程示意图，本实施例提供的数据库远程备份方法可以由图1中所示的云端服务器100执行，下面对该数据库远程备份方法进行详细介绍。
步骤S110，云端数据库接收客户端发送的备份请求通知，所述备份请求通知中包括待备份数据标签；
步骤S120，所述云端数据库确定与第一时域内接收到的至少一个备份请求通知中的待备份数据标签不同的第一待备份数据标签，其中，所述第一时域的结束时刻为所述云端数据库的待备份数据备份完成的时刻；
步骤S130，所述云端数据库发送第一备份请求通知，所述第一备份请求通知中包括所述第一待备份数据标签和所述云端数据库的待备份数据的目标端的待备份数据标签；
步骤S140，所述云端数据库向备份节点设备发送所述第一待备份数据标签；
步骤S150，所述云端数据库从所述备份节点设备接收基于所述第一待备份数据标签备份的第一资源的指示信息，其中，所述第一资源用于所述云端数据库发送所述待备份数据。
在一种可能的实施例中，步骤S140进一步包括：
步骤S141，所述云端数据库向备份节点设备发送第一请求，所述第一请求承载所述第一待备份数据标签，所述第一请求用于向所述备份节点设备请求用于非主节点的待备份资源。
在一种可能的实施例中，步骤S140进一步包括：
步骤S142：在满足请求条件的情况下，所述云端数据库向备份节点设备发送所述第一待备份数据标签；其中，所述请求条件包括下列条件中的至少一项：
第二时域大于或等于第一时间阈值，所述第二时域为所述云端数据库前一次向备份节点设备发送待备份数据标签的时刻到当前时刻的时间间隔；
所述第一待备份数据标签与第二待备份数据标签不同，所述第二待备份数据标签为所述云端数据库前一次向备份节点设备发送的待备份数据标签。
在一种可能的实施例中，步骤S120进一步包括：
步骤S121，所述云端数据库从待备份数据标签集合中选择与所述至少一个备份请求通知中的待备份数据标签不同的所述第一待备份数据标签，且所述至少一个备份请求通知中的待备份数据标签属于所述待备份数据标签集合。
在一种可能的实施例中，所述第一备份请求通知还用于指示下列信息中的至少一个：所述云端数据库的备份类型、所述云端数据库的待备份数据标签。
图3为本公开实施例提供的数据库远程备份装置300的功能模块示意图，本实施例可以根据上述云端服务器100执行的方法实施例对该数据库远程备份装置300进行功能模块的划分，也即该数据库远程备份装置300所对应的以下各个功能模块可以用于执行上述云端服务器100执行的各个方法实施例。其中，该数据库远程备份装置300可以包括接收单元310、处理单元320以及发送单元330，下面分别对该数据库远程备份装置300的各个功能模块的功能进行详细阐述。
接收单元310可以用于执行上述的步骤S110，即用于接收客户端发送的备份请求通知，所述备份请求通知中包括待备份数据标签。以及还用于从所述备份节点设备接收基于所述第一待备份数据标签分配的第一资源的指示信息，其中，所述第一资源用于所述云端数据库发送所述待备份数据。
处理单元320可以用于执行上述的步骤S120，即用于确定与第一时域内接收到的至少一个备份请求通知中的待备份数据标签不同的第一待备份数据标签，其中，所述第一时域的结束时刻为云端数据库的待备份数据备份完成的时刻。
发送单元330可以用于执行上述的步骤S130，即用于发送第一备份请求通知，所述第一备份请求通知中包括所述第一待备份数据标签和所述云端数据库的待备份数据的目标端的待备份数据标签；以及向备份节点设备发送所述第一待备份数据标签。
需要说明的是，应理解以上装置的各个模块的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且这些模块可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分模块通过处理元件调用软件的形式实现，部分模块通过硬件的形式实现。例如，接收单元310可以为单独设立的处理元件，也可以集成在上述装置的某一个芯片中实现，此外，也可以以程序代码的形式存储于上述装置的存储器中，由上述装置的某一个处理元件调用并执行以上接收单元310的功能。其它模块的实现与之类似。此外这些模块全部或部分可以集成在一起，也可以独立实现。这里所描述的处理元件可以是一种集成电路，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个模块可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指令完成。
例如，以上这些模块可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application
specific integrated circuit，ASIC)，或，一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field
programmable gate array，FPGA)等。再如，当以上某个模块通过处理元件调度程序代码的形式实现时，该处理元件可以是通用处理器，例如中央处理器(centralprocessing
unit，CPU)或其它可以调用程序代码的处理器。再如，这些模块可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
图4示出了本公开实施例提供的用于实现上述的控制设备的云端服务器100的硬件结构示意图，如图4所示，云端服务器100可包括处理器110、机器可读存储介质120、总线130以及收发器140。
在具体实现过程中，至少一个处理器110执行所述机器可读存储介质120存储的计算机执行指令（例如图3中所示的数据库远程备份装置300包括的），使得处理器110可以执行如上方法实施例的数据库远程备份方法，其中，处理器110、机器可读存储介质120以及收发器140通过总线130连接，处理器110可以用于控制收发器140的收发动作，从而可以与前述的客户端200进行数据收发。
处理器110的具体实现过程可参见上述云端服务器100执行的各个方法实施例，其实现原理和技术效果类似，本实施例此处不再赘述。
在上述的图4所示的实施例中，应理解，处理器可以是中央处理单元(英文：Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(英文：Digital
Signal Processor，DSP)、专用集成电路(英文：Application
SpecificIntegrated Circuit，ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合发明所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
机器可读存储介质120可能包含高速RAM存储器，也可能还包括非易失性存储NVM，例如至少一个磁盘存储器。
总线130可以是工业标准体系结构(Industry
Standard Architecture，ISA)总线、外部设备互连(Peripheral Component Interconnect，PCI)总线或扩展工业标准体系结构(Extended
Industry Standard Architecture，EISA)总线等。总线130可以分为地址总线、数据总线、控制总线等。为便于表示，本申请附图中的总线并不限定仅有一根总线或一种类型的总线。
此外，本公开实施例还提供一种可读存储介质，所述可读存储介质中存储有计算机执行指令，当处理器执行所述计算机执行指令时，实现如上数据库远程备份方法。
上述的可读存储介质可以是由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。可读存储介质可以是通用或专用计算机能够存取的任何可用介质。
最后应说明的是：以上各实施例仅用以说明本公开的技术方案，而非对其限制；尽管参照前述各实施例对本公开进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本公开各实施例技术方案的范围。
Claims (8)
- 一种数据库远程备份方法，其特征在于，所述方法包括：云端数据库接收客户端发送的备份请求通知，所述备份请求通知中包括待备份数据标签；所述云端数据库确定与第一时域内接收到的至少一个备份请求通知中的待备份数据标签不同的第一待备份数据标签，其中，所述第一时域的结束时刻为所述云端数据库的待备份数据备份完成的时刻；所述云端数据库发送第一备份请求通知，所述第一备份请求通知中包括所述第一待备份数据标签和所述云端数据库的待备份数据的目标端的待备份数据标签；所述云端数据库向备份节点设备发送所述第一待备份数据标签；所述云端数据库从所述备份节点设备接收基于所述第一待备份数据标签备份的第一资源的指示信息，其中，所述第一资源用于所述云端数据库发送所述待备份数据。
- 如权利要求1所述的方法，其特征在于，所述云端数据库向备份节点设备发送所述第一待备份数据标签，包括：所述云端数据库向备份节点设备发送第一请求，所述第一请求承载所述第一待备份数据标签，所述第一请求用于向所述备份节点设备请求用于非主节点的待备份资源。
- 如权利要求1或2所述的方法，其特征在于，所述云端数据库向备份节点设备发送所述第一待备份数据标签，包括：在满足请求条件的情况下，所述云端数据库向备份节点设备发送所述第一待备份数据标签；其中，所述请求条件包括下列条件中的至少一项：第二时域大于或等于第一时间阈值，所述第二时域为所述云端数据库前一次向备份节点设备发送待备份数据标签的时刻到当前时刻的时间间隔；所述第一待备份数据标签与第二待备份数据标签不同，所述第二待备份数据标签为所述云端数据库前一次向备份节点设备发送的待备份数据标签。
- 如权利要求1-3中任意一项所述的方法，其特征在于，所述云端数据库确定与第一时域内接收到的至少一个备份请求通知中的待备份数据标签不同的第一待备份数据标签，包括：所述云端数据库从待备份数据标签集合中选择与所述至少一个备份请求通知中的待备份数据标签不同的所述第一待备份数据标签，且所述至少一个备份请求通知中的待备份数据标签属于所述待备份数据标签集合。
- 如权利要求1-4中任意一所述的方法，其特征在于，所述第一备份请求通知还用于指示下列信息中的至少一个：所述云端数据库的备份类型、所述云端数据库的待备份数据标签。
- 一种数据库远程备份装置，其特征在于，所述装置包括接收单元、处理单元以及发送单元：所述接收单元，用于接收客户端发送的备份请求通知，所述备份请求通知中包括待备份数据标签；所述处理单元，用于确定与第一时域内接收到的至少一个备份请求通知中的待备份数据标签不同的第一待备份数据标签，其中，所述第一时域的结束时刻为云端数据库的待备份数据备份完成的时刻；所述发送单元，用于发送第一备份请求通知，所述第一备份请求通知中包括所述第一待备份数据标签和所述云端数据库的待备份数据的目标端的待备份数据标签；以及向备份节点设备发送所述第一待备份数据标签；所述接收单元，还用于从所述备份节点设备接收基于所述第一待备份数据标签分配的第一资源的指示信息，其中，所述第一资源用于所述云端数据库发送所述待备份数据。
- 一种计算机可读存储介质，其特征在于，用于存储指令/可执行代码，当所述指令/可执行代码被电子设备的处理器执行时，使得所述电子设备实现权利要求1-5中任一项所述的方法。
- 一种云端服务器，其特征在于，所述云端服务器包括处理器、机器可读存储介质和网络接口，所述机器可读存储介质、所述网络接口以及所述处理器之间通过总线系统相连，所述网络接口用于与至少一个客户端通信连接，所述机器可读存储介质用于存储程序、指令或代码，所述处理器用于执行所述机器可读存储介质中的程序、指令或代码，以执行权利要求1-5中任意一项的数据库远程备份方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010967224.5 | 2020-09-15 | ||
| CN202010967224.5A CN112084068A (zh) | 2020-09-15 | 2020-09-15 | 一种数据库远程备份方法、装置和云端服务器 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2022057028A1 true WO2022057028A1 (zh) | 2022-03-24 |
Family
ID=73736271
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2020/125261 WO2022057028A1 (zh) | 2020-09-15 | 2020-10-30 | 一种数据库远程备份方法、装置和云端服务器 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112084068A (zh) |
| WO (1) | WO2022057028A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117056133A (zh) * | 2023-10-12 | 2023-11-14 | 杭州浩联智能科技有限公司 | 一种基于分布式物联网架构的数据备份方法、装置及介质 |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113127551A (zh) * | 2021-04-25 | 2021-07-16 | 在秀网络科技(深圳)有限公司 | 一种取代前端设备的数据承载平台数据调取方法及系统 |
| CN115269263A (zh) * | 2022-06-09 | 2022-11-01 | 知学云(北京)科技股份有限公司 | 一种基于远程存储实现快速备份与恢复的数仓方法及系统 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103064757A (zh) * | 2012-12-12 | 2013-04-24 | 鸿富锦精密工业（深圳）有限公司 | 数据备份方法及系统 |
| CN105786646A (zh) * | 2016-02-25 | 2016-07-20 | 北京金山安全软件有限公司 | 一种数据备份方法、装置及电子设备 |
| CN107463465A (zh) * | 2017-07-20 | 2017-12-12 | 深圳互联先锋科技有限公司 | 远程备份数据库的方法及装置 |
| US20180032409A1 (en) * | 2016-07-26 | 2018-02-01 | Netapp, Inc. | Backup and recovery of application data of an application executing in a virtual machine |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2783109B2 (ja) * | 1993-03-04 | 1998-08-06 | 三菱電機株式会社 | データベースシステム退避装置及びデータベースシステム復元装置及びデータベースシステム移行装置 |
| JP2006352519A (ja) * | 2005-06-16 | 2006-12-28 | Nec Corp | データバックアップ装置、データバックアップ方法及びデータ復元方法 |
| CN101860559B (zh) * | 2009-04-08 | 2014-11-05 | 中兴通讯股份有限公司 | 基于对等网络的资源信息备份操作方法及对等网络 |
| CN105912424A (zh) * | 2011-09-30 | 2016-08-31 | 北京奇虎科技有限公司 | 一种基于云架构的终端程序快速备份及恢复方法 |
| US9449040B2 (en) * | 2012-11-26 | 2016-09-20 | Amazon Technologies, Inc. | Block restore ordering in a streaming restore system |
-
2020
- 2020-09-15 CN CN202010967224.5A patent/CN112084068A/zh not_active Withdrawn
- 2020-10-30 WO PCT/CN2020/125261 patent/WO2022057028A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103064757A (zh) * | 2012-12-12 | 2013-04-24 | 鸿富锦精密工业（深圳）有限公司 | 数据备份方法及系统 |
| CN105786646A (zh) * | 2016-02-25 | 2016-07-20 | 北京金山安全软件有限公司 | 一种数据备份方法、装置及电子设备 |
| US20180032409A1 (en) * | 2016-07-26 | 2018-02-01 | Netapp, Inc. | Backup and recovery of application data of an application executing in a virtual machine |
| CN107463465A (zh) * | 2017-07-20 | 2017-12-12 | 深圳互联先锋科技有限公司 | 远程备份数据库的方法及装置 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117056133A (zh) * | 2023-10-12 | 2023-11-14 | 杭州浩联智能科技有限公司 | 一种基于分布式物联网架构的数据备份方法、装置及介质 |
| CN117056133B (zh) * | 2023-10-12 | 2024-02-06 | 杭州浩联智能科技有限公司 | 一种基于分布式物联网架构的数据备份方法、装置及介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112084068A (zh) | 2020-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022057028A1 (zh) | 一种数据库远程备份方法、装置和云端服务器 | |
| US11632441B2 (en) | Methods, systems, and devices for electronic note identifier allocation and electronic note generation | |
| CN108984662B (zh) | 一种区块链数据同步方法 | |
| WO2019144761A1 (zh) | 一种数据同步方法和分布式系统、设备 | |
| CN109214632B (zh) | 一种风险控制方法及设备 | |
| US10417062B2 (en) | Method and apparatus of unloading out of memory processing flow to user space | |
| CN110018884B (zh) | 分布式事务处理方法、协调装置、数据库及电子设备 | |
| US20200163082A1 (en) | Transmission device, communication device, communication system, transmission method, and computer program product | |
| WO2022057096A1 (zh) | 一种云托管客户信息管理方法、装置及服务器 | |
| WO2021068605A1 (zh) | 数据持久化存储方法、装置、计算机设备及存储介质 | |
| US20170139808A1 (en) | Method and dispatcher node for server processing management | |
| CN112073215B (zh) | 一种实现应用的方法及业务控制器 | |
| WO2016176045A1 (en) | System, method, and apparatus for updating data in a distributed storage system | |
| CN115437709A (zh) | 应用首页闪屏资源的加载方法及装置 | |
| CN112379952B (zh) | 一种跨进程回调的实现方法 | |
| CN114900566A (zh) | 数据通信方法、装置、电子设备及介质 | |
| CN113207026A (zh) | 一种视频推荐方法、装置及云服务器 | |
| CN113286116B (zh) | 一种监控安全管理的信息提示方法、装置及云服务器 | |
| CN114090745A (zh) | 一种基于大数据的智能客服会话处理方法、系统及大数据中心 | |
| WO2022062179A1 (zh) | 一种云托管客户信息管理方法、装置及服务器 | |
| CN113794647A (zh) | 一种网络节点流控制方法、装置及云端服务器 | |
| CN114040022A (zh) | 一种数据传输方法、装置及云端服务器 | |
| CN108984450B (zh) | 数据传输方法、装置和设备 | |
| WO2022082967A1 (zh) | 一种视频会议信息传输方法、装置及系统 | |
| CN113784166A (zh) | 一种直播间流控制方法、装置及云直播服务器 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20953885 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 20953885 Country of ref document: EP Kind code of ref document: A1 |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 20953885 Country of ref document: EP Kind code of ref document: A1 |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 220923) |