CN111651303A - Database online backup and recovery method of distributed architecture and technical field - Google Patents
Database online backup and recovery method of distributed architecture and technical field Download PDFInfo
- Publication number
- CN111651303A CN111651303A CN202010645820.1A CN202010645820A CN111651303A CN 111651303 A CN111651303 A CN 111651303A CN 202010645820 A CN202010645820 A CN 202010645820A CN 111651303 A CN111651303 A CN 111651303A
- Authority
- CN
- China
- Prior art keywords
- backup
- distributed
- database
- cluster
- task
- 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 51
- 238000011084 recovery Methods 0.000 title claims abstract description 23
- 238000012545 processing Methods 0.000 claims abstract description 17
- 230000008569 process Effects 0.000 claims description 27
- 230000006870 function Effects 0.000 claims description 26
- 238000012790 confirmation Methods 0.000 claims description 13
- 230000000977 initiatory effect Effects 0.000 claims description 4
- 238000007726 management method Methods 0.000 description 11
- 230000004044 response Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 230000015572 biosynthetic process Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000003786 synthesis reaction Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- PCHJSUWPFVWCPO-UHFFFAOYSA-N gold Chemical compound [Au] PCHJSUWPFVWCPO-UHFFFAOYSA-N 0.000 description 1
- 239000010931 gold Substances 0.000 description 1
- 229910052737 gold Inorganic materials 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000004807 localization Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
Images
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/1456—Hardware arrangements for backup
-
- 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
-
- 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/1453—Management of the data involved in backup or backup restore using de-duplication of the data
-
- 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/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/80—Database-specific techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/82—Solving problems relating to consistency
Abstract
The invention discloses a distributed architecture database online backup and recovery method, which comprises the following steps: deploying a distributed cluster database: constructing a distributed cluster based on the cis components, improving the cis components in the distributed architecture, and adding new interface processing, wherein the interface processing comprises distributed backup cluster coordination service and a built-in hook processing function; deploying a linux kernel-based online backup module on each database system; the distributed backup cluster coordination service is utilized to complete the registration of the node service through the zookeeper, and the node service is provided for the subsequent backup; and according to the node service, carrying out data backup and quick pull-up of a backup database by using a built-in hook processing function. The invention realizes the high-efficiency backup and recovery of the distributed database through a new mode, so that the backup is easier, the second stored data can be quickly recovered and used, and a new distributed cluster can be formed.
Description
The invention belongs to the field of computers, and particularly relates to an online backup and recovery method of a distributed-architecture database PostgreSQL.
Background
The popularization and development of computers and the promotion of informatization enable various industries to greatly improve the production efficiency by means of the computers, wherein the database plays a role in supporting data storage. The database has been developed from the last 60 th century, the most prominent of which is the relational model, and the most elegant business database represents the leaderboard of the use of oracle in various industries more with its excellent performance and safety. But with the large environmental impact of autonomy, controllability and localization, databases represented by open-source relational databases PostgreSQL are more rapidly popularized and used. The effect of the internet now increases the index of the number of internet people, and the storage and retrieval of mass data are only insufficient by a single database, so that distributed databases have come into play, and the importance of data is self-evident, wherein the backup of the single database is relatively easy, but further research is needed to deal with the backup and quick recovery pull-up of the distributed databases.
Disclosure of Invention
The purpose of the invention is as follows: in order to overcome the defects in the prior art, an online backup and recovery method of a distributed-architecture database postgreSQL is provided, and efficient backup and recovery of the distributed database are realized through a new mode, so that backup is easier, second stored data can be quickly recovered and used, and a new distributed cluster can be formed.
The technical scheme is as follows: in order to achieve the above object, the present invention provides an online backup and recovery method for a database with a distributed architecture, comprising the following steps:
s1: deploying a distributed cluster database:
constructing a distributed cluster based on the cis components, modifying the cis components in the distributed architecture, and adding a new interface processing program, wherein the interface processing program comprises a distributed backup cluster coordination service module and a built-in hook processing function module;
s2: deploying a linux kernel-based online backup module on each database system;
s3: the distributed backup cluster coordination service is used for completing the registration of the service to the zookeeper, and the distributed backup cluster coordination service is used for providing service coordination among cluster nodes for the subsequent backup service;
s4: and according to the distributed backup cluster coordination service, carrying out data backup and quick pull-up of a backup database by using a built-in hook processing function.
Further, the data backup in step S3 is sequentially divided into a full backup and an incremental backup.
Further, the process of the full backup of the distributed database comprises:
a1: the management platform initiates a backup task, a master node registration task in the distributed backup cluster coordination service, and initiates backup preheating;
a2: the method comprises the steps that a slove node in a distributed backup cluster coordination server receives a task, enables a hook to process a function interface, forces a sync instruction to execute, writes data cached in a memory into a disk, writes new database IO operation into a cache in a transaction process, and submits a task completion instruction;
a3: and the master node in the distributed backup cluster coordination service receives the instruction of the task execution result of each slave node, initiates a confirmation backup instruction, calls a kernel module snapshot command by each slave node, initiates a full backup operation, and converts the volume device in a snapshot state into an incremental mode after the execution is finished.
Further, the incremental backup process of the distributed database includes:
b1: the management platform initiates an incremental backup task, a master node registration task in the distributed backup cluster coordination service, and backup preheating;
b2: the method comprises the steps that a slove node in the distributed backup cluster coordination service receives a task, enables a hook to process a function interface, forces a sync instruction to execute, writes data cached in a memory into a disk, writes new database IO operation into a cache in a transaction process, and submits a task completion instruction;
b3: and the master node in the distributed backup cluster coordination service receives the instruction of the task execution result of each slave node, initiates a confirmation backup instruction, calls a kernel module snapshot transferring command by each slave node, initiates an incremental backup operation, and transfers the volume device in a snapshot state to an incremental mode after the execution is finished.
Further, the process of quickly pulling up the distributed backup database in step S3 is as follows:
c1: a task management platform initiates a backup node recovery instruction;
c2: each node in the distributed backup cluster coordination service initiates zookeeper registration, wherein a master node is responsible for initiating a distributed backup library pull-up instruction;
c3: and each slove node quickly calls a database starting instruction in the standby library and pulls up the distributed coordination service cities.
The invention designs a method for backing up and pulling up a high-efficiency distributed database based on a status distributed architecture mode. Setting a hook processing function at the logic of the setup for carrying out table splitting, wherein the function forms a transaction for a data writing request, suspends a memory, and waits for a master node in a cluster to carry out a transaction completion submission instruction or automatically submits when the transaction is overtime within a limited time so as to prevent the task from being overtime and data loss. And a transaction cache concept is introduced to write and protect data and ensure the data consistency of cluster nodes. And constructing a distributed backup framework by using the zookeeper component to form a flow mode of primary backup preheating and primary confirmation backup. And a full distributed backup and incremental backup mode is provided, IO backup copy is reduced, and the use of a parallel backup deduplication technology is reduced. And providing the functions of quick recovery and pull-up of the backup cluster to form a new distributed cluster.
Has the advantages that: compared with the prior art, the invention has the following advantages:
1. the concept of transaction cache is introduced into the backup, so that the consistency of the produced distributed database is guaranteed, and the distributed database can be backed up under the normal operation without shutdown.
2. The backup preheating and the backup confirmation processing process are innovatively proposed, so that the consistency of backup data is more effectively guaranteed.
3. The deduplication technology is adopted in incremental backup data, so that the backup speed and performance are greatly improved.
4. The backup is also a distributed cluster mode different from the traditional single-library backup mode, the backup cluster is not an isolated database any more, but a pulled new distributed cluster can be quickly recovered, so that the backup cluster has integral clustering response capability, can provide production emergency response, can serve as a gold copy to be directly used or add part of nodes into the cluster to be used, enables backup data to be used by the existing technical means, and has practical value.
5. By the aid of the distributed backup cluster coordination service and the ingenious arrangement of the built-in hook processing function, efficient backup and recovery of the distributed database are achieved, backup is easier, second stored data can be quickly recovered and used, and a new distributed cluster can be formed.
Drawings
FIG. 1 is a schematic diagram of a distributed database full backup process;
FIG. 2 is a schematic diagram of a distributed database incremental backup process;
fig. 3 is a schematic diagram of a distributed backup database fast recovery pull-up process.
Detailed Description
The invention is further elucidated with reference to the drawings and the embodiments.
The distributed cluster constructed based on the facts component provides the database IO in the preheating process of the distributed backup task to perform the transaction operation of writing and caching through the built-in hook processing function, confirms the backup process and carries out snapshot on the volume equipment operated by the database. The backup task in the cluster is initiated by the master node, and the distributed coordination service in each distributed database node calls a snapshot instruction to complete the data backup through two stages of backup preheating and confirmation backup. When the backup database needs to be restored to provide service, the distributed coordination service program pulls up each database, and the backup cluster generator node coordinates the response of each slove node, so that a new database cluster is formed. The method comprises the steps of modifying components in a distributed architecture, adding new interface processing, and forming a background thread service program (called distributed backup cluster coordination service) and a hook function interface, wherein a new distributed backup cluster is formed among background thread services, distributed coordination is performed through zookeeper, the equipment state of the cluster is maintained, and the coordination processing work of a backup task is completed. Each database system needs to be provided with an online backup module based on a linux kernel, and the online backup module mainly has the functions of carrying out snapshot, trace block modification recording and backup data synthesis on volume equipment operated by the database and is matched with the execution of a backup task.
After the deployment of the database of the distributed cluster and the installation of the backup module are finished, the distributed backup cluster coordination server completes the first registration service through zookeeper, a leader of the cluster is generated through election, a subsequent backup task is registered by a leader node (namely a master node), and message response processing and distribution of the backup task are carried out on the slave node of the distributed database and message response of the slave node in the distributed cluster are processed. And each time the task is initiated to carry the task ID, accumulating the task ID from 0, and enabling the current task ID to be 0 when the task is failed to be initiated. The initiation of the full backup task may be performed if and only if the task ID is 0.
The first full backup process for a distributed database cluster is as follows: the management platform initiates a backup task, a master node in the distributed backup cluster coordination service acquires a task request, registers a new service node, sets the current task ID to be 0, and then performs self-increment on the current task ID. The method comprises the steps that a sleep node in each distributed backup cluster coordination server obtains notification information from a zookeeper, and when an ID is 0, a backup preheating task is initiated; firstly, setting a logic judgment mark executed by a callback function to be true so as to enable a hook function to be executed; then calling a system sync command to force the cache data to be written into a disk; at the moment, the hook function can write the new database IO operation into the memory for caching, the write operation is protected by the transaction, and the caching is cancelled until a task submitting instruction is received or the task is overtime; the slave node completes the task and submits a task completion instruction to the cluster master node; and after receiving the response of each slove node, the manager node initiates a backup confirmation task, and if the threshold value is exceeded (no response is given for 5min by default), the manager node cancels the backup task. When the slove node in the distributed backup cluster coordination service receives the backup task confirmation instruction again, the distributed coordination service calls the snapshot instruction to snapshot the storage device of the database, the application layer backup module performs full backup (the relevant information such as a backup host is issued by the management terminal, and each slave node is acquired through the zookeeper), and the backup completes the incremental command for calling the backup module in the kernel.
Then, the flow of backup of the incremental process distributed cluster database is as follows: the management platform initiates a backup task, a master in the distributed backup cluster coordination service acquires a task request, registers a new service node, sets a current task ID, and then performs self-increment on the current task ID. The method comprises the steps that a sleep node in each distributed backup cluster coordination server obtains a notification from a zookeeper, and when an ID (identity) is larger than 0, a backup preheating task is initiated; firstly, setting a logic judgment mark executed by a callback function to be true so as to enable a hook function to be executed; then calling a system sync command to force the cache data to be written into a disk; at the moment, the hook function can write the new database IO operation into the memory for caching, the write operation is protected by the transaction, and the caching is cancelled until a task submitting instruction is received or the task is overtime; completing the task, and submitting a task completion instruction to the cluster master; and after receiving the response of each slove node, the manager node initiates a backup confirmation task, and if the threshold value is exceeded (no response is given for 5min by default), the manager node cancels the backup task. When the slove node in the distributed backup cluster coordination service receives the backup task confirmation instruction again, the distributed coordination service calls a snapshot instruction, new snapshots are carried out on the storage devices of the database, the application layer backup module carries out incremental backup, and modified block data between the backup snapshot at the starting time point and the current backup snapshot at the ending time point are backed up on a backup host (relevant information such as the backup host is issued by a management terminal, and each slave node is acquired through zookeeper).
The process of rapidly restoring the pulled backup cluster is as follows: and the management end initiates a recovery mounting task of the backup cluster, each backup host calls a database starting command to quickly pull up the database for recovering the backup, and the status service of the cluster is pulled up and operated, so that the distributed backup cluster coordination service is recovered.
In combination with the above process, the present invention provides a method for online backup and recovery of a database with a distributed architecture, which comprises the following steps:
s1: deploying a distributed cluster database:
based on a distributed cluster constructed by the cis components, a new interface processing program is added for the reconstruction of the cis components in the distributed architecture, and the interface processing program comprises a distributed backup cluster coordination service module and a built-in hook processing function module;
s2: an online backup module based on a linux kernel is deployed on each database system, and mainly has the functions of snapshot, block modification record and data synthesis of equipment volumes and is matched with the completion of backup;
s3: the distributed backup cluster coordination service is used for completing the registration of the service to the zookeeper, and the distributed backup cluster coordination service is used for providing service coordination among cluster nodes for the subsequent backup service;
s4: and according to the node service, carrying out full backup and incremental backup of the distributed database cluster and quick recovery pull-up of a backup cluster database by using a built-in hook processing function.
As shown in fig. 1, when the ID =0 in the node service, the full backup of the distributed database is performed, and the specific process includes:
a1: the management platform initiates a backup task, a master node registration task in the distributed backup cluster coordination service, and initiates backup preheating;
a2: the method comprises the steps that a slove node in a distributed backup cluster coordination server receives a task, enables a hook to process a function interface, forces a sync instruction to execute, writes data cached in a memory into a disk, writes new database IO operation into a cache in a transaction process, and submits a task completion instruction;
a3: and the master node in the distributed backup cluster coordination service receives the instruction of the task execution result of each slave node, initiates a confirmation backup instruction, calls a kernel module snapshot command by each slave node, initiates a full backup operation, and converts the volume device in a snapshot state into an incremental mode after the execution is finished.
As shown in fig. 2, when the ID >0 in the node service, incremental backup of the distributed database is performed, and the specific process is as follows:
b1: the management platform initiates an incremental backup task, a master node registration task in the distributed backup cluster coordination service, and backup preheating;
b2: the method comprises the steps that a slove node in the distributed backup cluster coordination service receives a task, enables a hook to process a function interface, forces a sync instruction to execute, writes data cached in a memory into a disk, writes new database IO operation into a cache in a transaction process, and submits a task completion instruction;
b3: and the master node in the distributed backup cluster coordination service receives the instruction of the task execution result of each slave node, initiates a confirmation backup instruction, calls a kernel module snapshot transferring command by each slave node, initiates an incremental backup operation, and transfers the volume device in a snapshot state to an incremental mode after the execution is finished.
As shown in fig. 3, the procedure of quickly pulling up the distributed backup database in step S3 is as follows:
c1: a task management platform initiates a backup node recovery instruction;
c2: each node in the distributed backup cluster coordination service initiates zookeeper registration, wherein a master node is responsible for initiating a distributed backup library pull-up instruction;
c3: and each slove node quickly calls a database starting instruction in the standby library and pulls up the distributed coordination service cities.
Claims (5)
1. A method for online backup and recovery of a database with a distributed architecture is characterized by comprising the following steps:
s1: deploying a distributed cluster database:
constructing a distributed cluster based on the cis components, modifying the cis components in the distributed architecture, and adding a new interface processing program, wherein the interface processing program comprises a distributed backup cluster coordination service module and a built-in hook processing function module;
s2: deploying a linux kernel-based online backup module on each database system;
s3: the distributed backup cluster coordination service is used for completing the registration of the service to the zookeeper, and the distributed backup cluster coordination service is used for providing service coordination among cluster nodes for the subsequent backup service;
s4: and according to the distributed backup cluster coordination service, carrying out data backup and quick pull-up of a backup database by using a built-in hook processing function.
2. The method for online backup and recovery of a database in a distributed architecture according to claim 1, wherein the data backup in step S3 is sequentially divided into a full backup and an incremental backup.
3. The method for online backup and recovery of a database with a distributed architecture according to claim 2, wherein the flow of the full backup of the distributed database is as follows:
a1: the management platform initiates a backup task, a master node registration task in the distributed backup cluster coordination service, and initiates backup preheating;
a2: the method comprises the steps that a slove node in a distributed backup cluster coordination server receives a task, enables a hook to process a function interface, forces a sync instruction to execute, writes data cached in a memory into a disk, writes new database IO operation into a cache in a transaction process, and submits a task completion instruction;
a3: and the master node in the distributed backup cluster coordination service receives the instruction of the task execution result of each slave node, initiates a confirmation backup instruction, calls a kernel module snapshot command by each slave node, initiates a full backup operation, and converts the volume device in a snapshot state into an incremental mode after the execution is finished.
4. The method for online backup and recovery of a database with a distributed architecture according to claim 3, wherein the incremental backup of the distributed database is performed by:
b1: the management platform initiates an incremental backup task, a master node registration task in the distributed backup cluster coordination service, and backup preheating;
b2: the method comprises the steps that a slove node in the distributed backup cluster coordination service receives a task, enables a hook to process a function interface, forces a sync instruction to execute, writes data cached in a memory into a disk, writes new database IO operation into a cache in a transaction process, and submits a task completion instruction;
b3: and the master node in the distributed backup cluster coordination service receives the instruction of the task execution result of each slave node, initiates a confirmation backup instruction, calls a kernel module snapshot transferring command by each slave node, initiates an incremental backup operation, and transfers the volume device in a snapshot state to an incremental mode after the execution is finished.
5. The method for online backup and recovery of a database with distributed architecture according to claim 1, wherein the procedure of fast pulling up the distributed backup database in step S3 is as follows:
c1: a task management platform initiates a backup node recovery instruction;
c2: each node in the distributed backup cluster coordination service initiates zookeeper registration, wherein a master node is responsible for initiating a distributed backup library pull-up instruction;
c3: and each slove node quickly calls a database starting instruction in the standby library and pulls up the distributed coordination service cities.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010645820.1A CN111651303A (en) | 2020-07-07 | 2020-07-07 | Database online backup and recovery method of distributed architecture and technical field |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010645820.1A CN111651303A (en) | 2020-07-07 | 2020-07-07 | Database online backup and recovery method of distributed architecture and technical field |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111651303A true CN111651303A (en) | 2020-09-11 |
Family
ID=72350211
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010645820.1A Pending CN111651303A (en) | 2020-07-07 | 2020-07-07 | Database online backup and recovery method of distributed architecture and technical field |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111651303A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117521423A (en) * | 2024-01-05 | 2024-02-06 | 山东鑫林纸制品有限公司 | Intelligent prediction method and device for machine speed of corrugated paper processing and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104516791A (en) * | 2013-09-30 | 2015-04-15 | 贝壳网际（北京）安全技术有限公司 | Data processing method and device and electronic device |
| CN104781791A (en) * | 2011-12-05 | 2015-07-15 | 持续电信解决方案公司 | Universal pluggable cloud disaster recovery system |
| WO2016180160A1 (en) * | 2015-10-23 | 2016-11-17 | 中兴通讯股份有限公司 | Data snapshot recovery method and apparatus |
| CN110109778A (en) * | 2019-07-02 | 2019-08-09 | 南京云信达科技有限公司 | A kind of a large amount of small data file backup methods and restoration methods |
| CN110741350A (en) * | 2017-05-05 | 2020-01-31 | 皮沃塔尔软件公司 | Backup and restore architecture for distributed computing systems |
-
2020
- 2020-07-07 CN CN202010645820.1A patent/CN111651303A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104781791A (en) * | 2011-12-05 | 2015-07-15 | 持续电信解决方案公司 | Universal pluggable cloud disaster recovery system |
| CN104516791A (en) * | 2013-09-30 | 2015-04-15 | 贝壳网际（北京）安全技术有限公司 | Data processing method and device and electronic device |
| WO2016180160A1 (en) * | 2015-10-23 | 2016-11-17 | 中兴通讯股份有限公司 | Data snapshot recovery method and apparatus |
| CN110741350A (en) * | 2017-05-05 | 2020-01-31 | 皮沃塔尔软件公司 | Backup and restore architecture for distributed computing systems |
| CN110109778A (en) * | 2019-07-02 | 2019-08-09 | 南京云信达科技有限公司 | A kind of a large amount of small data file backup methods and restoration methods |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117521423A (en) * | 2024-01-05 | 2024-02-06 | 山东鑫林纸制品有限公司 | Intelligent prediction method and device for machine speed of corrugated paper processing and storage medium |
| CN117521423B (en) * | 2024-01-05 | 2024-04-05 | 山东鑫林纸制品有限公司 | Intelligent prediction method and device for machine speed of corrugated paper processing and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101719165B (en) | Method for realizing high-efficiency rapid backup of database | |
| EP2474919B1 (en) | System and method for data replication between heterogeneous databases | |
| CN103226502A (en) | Data disaster backup control system and data recovery method | |
| CN103647669A (en) | System and method for guaranteeing distributed data processing consistency | |
| CN105302667B (en) | High reliability data backup and restoration methods based on aggregated structure | |
| WO2019080335A1 (en) | Method for micro-service transformation of electricity trading function | |
| CN102033930A (en) | Distributed memory database system | |
| US20100082630A1 (en) | Persisting external index data in a database | |
| CN104239444B (en) | The consistent data protection of oracle database and the method for capture coherency state | |
| CN103197988A (en) | Data backup and recovery method, device and database system | |
| JPH0423144A (en) | Journal system | |
| CN102262591B (en) | Garbage collection method and system for memory copy system | |
| CN103823708B (en) | The method and apparatus that virtual machine read-write requests are processed | |
| CN103049317A (en) | Highly-concurrent data fast write system and method based on queues in cloud environment | |
| CN101945131A (en) | Storage virtualization-based data migration method | |
| CN115994053A (en) | Parallel playback method and device of database backup machine, electronic equipment and medium | |
| CN102024021A (en) | Method for logging metadata in logical file system | |
| CN111651303A (en) | Database online backup and recovery method of distributed architecture and technical field | |
| CN104142943B (en) | A kind of data-base capacity-enlarging method and a kind of database | |
| CN105938446B (en) | The data supported based on RDMA and hardware transactional memory replicate fault-tolerance approach | |
| CN107861838A (en) | Method and device of the automated back-up MySQL database from storehouse | |
| CN115098300B (en) | Database backup method, disaster recovery method, device and equipment | |
| CN101814043B (en) | Method for performing on-line recovery by using snapshot technology | |
| CN1316779C (en) | A data disaster recovery solution method producing no interlinked data reproduction | |
| US6076095A (en) | Method of one system of a multisystem environment taking over log entries owned by another system |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200911 |
|
| WD01 | Invention patent application deemed withdrawn after publication |