CN106445738B - Database backup method and device - Google Patents
Database backup method and device Download PDFInfo
- Publication number
- CN106445738B CN106445738B CN201610821056.2A CN201610821056A CN106445738B CN 106445738 B CN106445738 B CN 106445738B CN 201610821056 A CN201610821056 A CN 201610821056A CN 106445738 B CN106445738 B CN 106445738B
- Authority
- CN
- China
- Prior art keywords
- backup
- data table
- database
- historical data
- data
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000004140 cleaning Methods 0.000 claims description 9
- 238000013144 data compression Methods 0.000 claims description 9
- 238000011084 recovery Methods 0.000 abstract description 19
- 238000005192 partition Methods 0.000 description 5
- 238000007726 management method Methods 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 230000002354 daily effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 238000012546 transfer 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/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
- 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/22—Indexing; Data structures therefor; Storage structures
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a database backup method and a device, wherein data tables in a database are classified into a historical data table and a real-time service data table; carrying out full backup on the service data table; performing incremental backup on the historical data table; and storing the backed-up service data table and the backed-up historical data table into a medium to complete the backup of the database. Because the historical data in the large mysql database occupies a large amount of storage space and the real-time service data is less, the historical data table and the real-time service table are backed up separately, so that the data volume of each backup can be reduced, the backup time and the recovery time can be shortened, and the backup speed can be accelerated. Therefore, the database backup under the mysql large-scale database scene is realized quickly, the backup recovery time is shortened, the occupied space of the backup file is reduced, and the backup recovery efficiency and the safety guarantee capability of the database are improved.
Description
Technical Field
The present invention relates to the field of database backup technologies, and in particular, to a database backup method and apparatus.
Background
Data backup is a disaster-tolerant basis, and refers to a process of copying all or part of a data set from an application host to another storage medium in order to prevent data loss caused by system misoperation or system failure. Mysql is an open source relational database management system (RDBMS) that uses the most common database management language, Structured Query Language (SQL), to perform database management, providing a community open source version of Mysql. The backup worker provided has mysqldump, mysqlhothcopy, text backup. Mysqlhotcpy supports only myisam engine backup in community open source versions. The Mysqldump command is a logical backup tool of the mysql, can realize backup of database level and table level, and dumps the table structure and data into an sql to text file during backup. Mysqldump can provide control parameters for database consistent backup, and incremental backup of the inodb engine table can be realized by combining binlog files.
The large database scene is characterized by large data volume which is basically higher than TB level, the current mysql database usually adopts a transactional inodb engine table, and mysql innardb engine tables can be backed by mysql self-contained mysql, a third-party tool xtrabeckup and the like. Because the xtrabackup is used for backing up physical files of the database, backed-up data sets cannot be compressed, a transfer space is needed during backup, and when the storage space of a database server is tight, a plurality of problems can be caused by the adoption of the method.
Disclosure of Invention
The invention aims to provide a database backup method and a database backup device, and aims to solve the problems of long backup period, long recovery period and large occupied space of backup files in the conventional mysql large-scale database scene.
In order to solve the above technical problem, the present invention provides a database backup method, including:
classifying data tables in a database into a historical data table and a real-time service data table;
carrying out full backup on the service data table;
performing incremental backup on the historical data table;
and storing the backed-up business data table and the backed-up historical data table into a medium to complete the backup of the database.
Optionally, the performing incremental backup on the historical data table includes:
determining the current day data and the newly added alternate day historical data in the historical data table;
and respectively backing up the current day data and the newly added alternate day historical data.
Optionally, after the backup of the newly added alternate day history data, the method further includes:
and naming the backup file according to a preset naming rule.
Optionally, before the storing the backed-up business data table and the historical data table into a medium, the method further includes:
and performing data compression on the service data table and the historical data table.
Optionally, the method further comprises:
and when the preset conditions are met, cleaning the overdue data.
The invention also provides a database backup device, comprising:
the classification module is used for classifying the data tables in the database into a historical data table and a real-time service data table;
the full backup module is used for performing full backup on the service data table;
the incremental backup module is used for carrying out incremental backup on the historical data table;
and the storage module is used for storing the backed-up business data table and the backed-up historical data table into a medium to complete the backup of the database.
Optionally, the incremental backup module specifically includes: determining the current day data and the newly added alternate day historical data in the historical data table; and the module is used for respectively backing up the current day data and the newly added alternate day historical data.
Optionally, the method further comprises:
and the naming module is used for naming the backup file according to a preset naming rule after the newly added alternate-day historical data is backed up.
Optionally, the method further comprises:
and the data compression module is used for performing data compression on the business data table and the historical data table before the backed-up business data table and the historical data table are stored in a medium.
Optionally, the method further comprises:
and the cleaning module is used for cleaning the overdue data when the preset conditions are met.
The database backup method and the database backup device classify the data tables in the database into a historical data table and a real-time service data table; carrying out full backup on the service data table; performing incremental backup on the historical data table; and storing the backed-up service data table and the backed-up historical data table into a medium to complete the backup of the database. Because the historical data in the large mysql database occupies a large amount of storage space and the real-time service data is less, the historical data table and the real-time service table are backed up separately, so that the data volume of each backup can be reduced, the backup time and the recovery time can be shortened, and the backup speed can be accelerated. Therefore, the database backup under the mysql large-scale database scene is realized quickly, the backup recovery time is shortened, the occupied space of the backup file is reduced, and the backup recovery efficiency and the safety guarantee capability of the database are improved.
Drawings
In order to more clearly illustrate the embodiments or technical solutions of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a flow chart of one embodiment of a database backup method provided by the present invention;
FIG. 2 is a flow chart of another embodiment of a database backup method provided by the present invention;
fig. 3 is a block diagram of a database backup apparatus according to an embodiment of the present invention.
Detailed Description
Generally, mysql databases used by a generation system all make backup strategies, but the data volume of the mysql large-scale databases is large in scenes, and the backup tools which can be provided by the mysql serving as an open source database are limited, so that the database backup time is long, the backup files occupy large space, and the normal business operation of the database is influenced for a long time during backup. The core of the invention is to provide a database backup method and a database backup device so as to improve the backup efficiency.
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 shows a flowchart of a specific embodiment of a database backup method provided by the present invention, where the method includes:
step S101: classifying data tables in a database into a historical data table and a real-time service data table;
step S102: carrying out full backup on the service data table;
step S103: performing incremental backup on the historical data table;
step S104: and storing the backed-up business data table and the backed-up historical data table into a medium to complete the backup of the database.
The database backup method provided by the invention classifies the data tables in the database into a historical data table and a real-time service data table; carrying out full backup on the service data table; performing incremental backup on the historical data table; and storing the backed-up service data table and the backed-up historical data table into a medium to complete the backup of the database. Because the historical data in the large mysql database occupies a large amount of storage space and the real-time service data is less, the historical data table and the real-time service table are backed up separately, so that the data volume of each backup can be reduced, the backup time and the recovery time can be shortened, and the backup speed can be accelerated. Therefore, the database backup under the mysql large-scale database scene is realized quickly, the backup recovery time is shortened, the occupied space of the backup file is reduced, and the backup recovery efficiency and the safety guarantee capability of the database are improved.
The data tables in the mysql database are classified into a historical data table and a business data table. Usually, a large amount of storage space is occupied by historical data in a large mysql database, a few business real-time data tables are used, a backup program is combined with a mysql backup tool to complete scheduling of backup, and database backup is automatically completed by inputting the historical data, the business tables, backup conditions and the like. Therefore, the historical data table and the real-time service table are backed up separately, the data volume of each backup can be reduced, the backup and recovery time can be shortened, and the backup speed can be accelerated.
On the basis of the above embodiment, the incremental backup of the historical data table in the database backup method provided by the present invention may specifically be:
determining the current day data and the newly added alternate day historical data in the historical data table;
and respectively backing up the current day data and the newly added alternate day historical data.
Further, after the backup of the new alternate day history data, the method further comprises:
and naming the backup file according to a preset naming rule.
The method comprises the following steps of separately backing up a historical table and a service table in a large database, combining daily data of the service data table and the historical data with mysql binlog to complete full and incremental backups, and backing up the historical data of the historical table separately every other day, wherein the historical data comprises the following steps: the No. 7/month 2 backup method is characterized in that the historical partition data of the No. 7/month 1 is backed up, the data of the No. 7/month 1 cannot be changed, a single backup file is formed after backup, an independent naming rule is given to the backup file, the file is compressed and then is placed in a backup storage medium (such as a tape library), and the whole backup process is completed. The backup program realized according to the process greatly shortens the backup time and improves the backup efficiency.
On the basis of any of the above embodiments, the database backup method provided by the present invention may further include, before storing the backed-up service data table and the backed-up history data table in a medium:
and performing data compression on the service data table and the historical data table.
Preferably, this embodiment may further include: and when the preset conditions are met, cleaning the overdue data.
The method can be realized by specifically adopting a backup tool myqldump of mysql, the myqldump can realize the consistent export of data, the exported file is a text file, the compression can be realized to a greater extent, and the realization of a rapid database data backup strategy can be realized by adopting different parameters for the myqldump according to a service scene.
As shown in fig. 2, a flowchart of another specific embodiment of the database backup method provided by the present invention includes:
step S201: determining a database needing to be backed up; determining a historical data table list; determining a history table building table and a data query rule: a day table, a month table, a partition table, etc.; determining a historical table data insertion rule;
step S202: classifying data tables in a database into a historical data table and a real-time service data table;
step S203: carrying out full backup on the service data table;
the real-time business table data can be subjected to full-table backup combined with binlog file backup to complete full-increment backup.
Step S204: performing incremental backup on the historical data table;
historical data of the historical table is backed up, the independent historical physical table can be backed up in a whole table, a partition table/a large table can be backed up according to a specified query condition according to a date range, and theoretically, the data table or partition data to be backed up cannot be changed (a backup strategy of alternate days is adopted), so that a consistent backup condition can be removed, and the specified condition backup is prevented from influencing the table.
History table backup the current day data backup has 2 cases: the independent historical physical table and the real-time business table can be backed up simultaneously; when tables such as a range partition table/a large table are exported according to conditions, mysqldump limitation (the condition of a single table cannot be specified during multi-table backup) causes the need of independent backup, and the recovery operation is very troublesome.
Step S205: and storing the backed-up business data table and the backed-up historical data table into a medium to complete the backup of the database.
In the following, the database backup apparatus provided in the embodiment of the present invention is introduced, and the database backup apparatus described below and the database backup method described above may be referred to correspondingly.
Fig. 3 is a block diagram of a database backup apparatus according to an embodiment of the present invention, where, referring to fig. 3, the database backup apparatus may include:
the classification module 100 is configured to classify data tables in the database into a historical data table and a real-time service data table;
a full backup module 200, configured to perform full backup on the service data table;
an incremental backup module 300, configured to perform incremental backup on the historical data table;
the storage module 400 is configured to store the backed-up service data table and the backed-up historical data table in a medium, so as to complete the backup of the database.
On the basis of the foregoing embodiment, in the database backup device provided by the present invention, the incremental backup module specifically includes: determining the current day data and the newly added alternate day historical data in the historical data table; and the module is used for respectively backing up the current day data and the newly added alternate day historical data.
Further, this embodiment may further include:
and the naming module is used for naming the backup file according to a preset naming rule after the newly added alternate-day historical data is backed up.
On the basis of any of the above embodiments, the database backup apparatus provided by the present invention may further include:
and the data compression module is used for performing data compression on the business data table and the historical data table before the backed-up business data table and the historical data table are stored in a medium.
As a specific implementation, this embodiment may further include:
a cleaning module for cleaning the overdue data when the preset condition is satisfied
The data backup device provided by the application can be used for quickly realizing the backup of the database in the mysql large-scale database scene, reducing the backup recovery time, reducing the occupation of the backup file space, and improving the backup recovery efficiency and the safety guarantee capability of the database.
Taking a specific project as an example, the annual capacity of a database to be backed up of the project is predicted to be 2.5T, wherein the business table data is only about 5G, the rest data is all historical data, the historical data generated every day is calculated to be about 10G, if full-library backup is carried out, the backup rate is about 5 hours, and backed-up files can be stored in no space; the strategy of using the sublist backup only needs to be done for less than half an hour every day, and the time efficiency is obvious. The automation is realized after processing each backup process by writing scripts, the control of the parameters of the backup commands is refined, the backup can be completed on the premise of less influence on the database, the prior recovery of the business data table can also be realized in the corresponding database recovery process, the historical data can be subsequently and slowly recovered under the condition of not influencing the business, and the business system can be ensured to be recovered to be normally used as soon as possible.
In summary, the conventional mysql database backup scheme is that backup of the whole database is performed through tools such as mysql, which results in the problems of long backup time and large influence on the database. Meanwhile, the method and the device reduce the recovery time of the backup and reduce the space occupation of the backup files, thereby improving the backup efficiency. In addition, the corresponding database recovery process can also realize the advanced recovery of the service data table, and the historical data can be recovered slowly in the follow-up process under the condition of not influencing the service, thereby ensuring that the service system can be recovered to be normally used as soon as possible.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The database backup method and device provided by the invention are described in detail above. The principles and embodiments of the present invention are explained herein using specific examples, which are presented only to assist in understanding the method and its core concepts. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
Claims (8)
1. A method for database backup, comprising:
classifying data tables in a database into a historical data table and a real-time service data table;
carrying out full backup on the service data table;
performing incremental backup on the historical data table;
storing the backed-up business data table and the historical data table into a medium to complete the backup of the database;
wherein the performing incremental backup on the historical data table comprises:
removing the consistency backup condition;
determining the current day data and the newly added alternate day historical data in the historical data table;
and respectively backing up the current day data and the newly added alternate day historical data.
2. The database backup method of claim 1, further comprising, after backing up the new alternate day history data:
and naming the backup file according to a preset naming rule.
3. The database backup method according to claim 1 or 2, characterized in that before storing the backed up business data table and the history data table in a medium, it further comprises:
and performing data compression on the service data table and the historical data table.
4. The database backup method of claim 3, further comprising:
and when the preset conditions are met, cleaning the overdue data.
5. A database backup apparatus, comprising:
the classification module is used for classifying the data tables in the database into a historical data table and a real-time service data table;
the full backup module is used for performing full backup on the service data table;
the incremental backup module is used for carrying out incremental backup on the historical data table;
the storage module is used for storing the backed-up business data table and the historical data table into a medium to complete the backup of the database;
the incremental backup module specifically comprises: determining the current day data and the newly added alternate day historical data in the historical data table; a module for respectively backing up the current day data and the newly added alternate day historical data;
the method also comprises a module for removing the consistent backup condition before determining the current day data in the historical data table and adding the alternate day historical data.
6. The database backup apparatus of claim 5, further comprising:
and the naming module is used for naming the backup file according to a preset naming rule after the newly added alternate-day historical data is backed up.
7. The database backup apparatus according to any one of claims 5 or 6, further comprising:
and the data compression module is used for performing data compression on the business data table and the historical data table before the backed-up business data table and the historical data table are stored in a medium.
8. The database backup apparatus of claim 7, further comprising:
and the cleaning module is used for cleaning the overdue data when the preset conditions are met.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610821056.2A CN106445738B (en) | 2016-09-13 | 2016-09-13 | Database backup method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610821056.2A CN106445738B (en) | 2016-09-13 | 2016-09-13 | Database backup method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106445738A CN106445738A (en) | 2017-02-22 |
| CN106445738B true CN106445738B (en) | 2020-10-16 |
Family
ID=58167964
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610821056.2A Active CN106445738B (en) | 2016-09-13 | 2016-09-13 | Database backup method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106445738B (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107247639A (en) * | 2017-05-03 | 2017-10-13 | 上海动联信息技术股份有限公司 | A kind of efficient backup method of mysql databases |
| CN110019477A (en) * | 2017-12-27 | 2019-07-16 | 航天信息股份有限公司 | A kind of method and system carrying out big data processing using HIVE backup table |
| CN108491294B (en) * | 2018-03-15 | 2022-11-25 | 中国银行股份有限公司 | Database backup method, device and system |
| CN110209528B (en) * | 2018-11-30 | 2022-10-28 | 腾讯科技（深圳）有限公司 | Data backup method, device, server and storage medium |
| CN110597669B (en) * | 2019-09-20 | 2022-10-11 | 中国银行股份有限公司 | Bank historical data parameterized backup recovery method and device |
| CN110995723A (en) * | 2019-12-11 | 2020-04-10 | 深圳物讯科技有限公司 | Method for preventing loss of big data transmission data across public security boundary |
| CN111143365B (en) * | 2019-12-26 | 2023-08-18 | 深圳前海环融联易信息科技服务有限公司 | Data sub-table method, device, computer equipment and storage medium |
| CN111324485A (en) * | 2020-01-20 | 2020-06-23 | 杭州安恒信息技术股份有限公司 | Data information backup method, device, equipment and storage medium of data table |
| CN112131051B (en) * | 2020-09-29 | 2023-08-22 | 中国银行股份有限公司 | Data backup method and device based on parameterized configuration |
| CN112650622A (en) * | 2020-12-24 | 2021-04-13 | 江苏云柜网络技术有限公司 | Data backup and recovery system and method suitable for intelligent express cabinet service |
| CN112925677A (en) * | 2021-03-10 | 2021-06-08 | 福建宁德核电有限公司 | Backup equipment, automatic backup system and method for non-safety-level DCS historical data |
| CN113515374B (en) * | 2021-05-18 | 2024-02-27 | 中国工商银行股份有限公司 | Data processing method and device, electronic equipment and computer readable storage medium |
| CN113377872B (en) * | 2021-06-25 | 2024-02-27 | 北京红山信息科技研究院有限公司 | Offline synchronization method, device and equipment of online system data in big data center |
| CN114328005B (en) * | 2021-09-08 | 2022-08-26 | 深圳市木浪云科技有限公司 | Method and system for incremental backup of container data |
| CN114138554B (en) * | 2021-11-22 | 2022-08-09 | 深圳互信互通科技有限公司 | Wireless AP configuration information backup and system recovery control system |
| CN114020539B (en) * | 2022-01-05 | 2022-03-18 | 国家超级计算天津中心 | Block storage self-adaptive backup system based on cloud environment |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN202134001U (en) * | 2011-03-07 | 2012-02-01 | 浪潮(北京)电子信息产业有限公司 | Executable file backup device |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101499070A (en) * | 2008-02-02 | 2009-08-05 | 北京城市学院 | History and real-time data access system and method based on open database interface |
| CN101354713A (en) * | 2008-09-08 | 2009-01-28 | 大唐软件技术股份有限公司 | Method and system for storing data |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
| CN104182295B (en) * | 2013-05-27 | 2018-11-02 | 阿里巴巴集团控股有限公司 | A kind of data back up method and device |
| CN105320576A (en) * | 2014-05-30 | 2016-02-10 | 中国电信股份有限公司 | Device and method for database backup |
| CN104036001B (en) * | 2014-06-13 | 2017-05-10 | 上海新炬网络信息技术有限公司 | Dynamic hotlist priority scheduling based quick data cleaning method |
| CN104572867A (en) * | 2014-12-18 | 2015-04-29 | 上海新炬网络信息技术有限公司 | Data processing method based on Oracle |
| CN104850598B (en) * | 2015-04-28 | 2017-11-14 | 江苏瑞中数据股份有限公司 | A kind of real-time data base back-up restoring method |
| CN105302667B (en) * | 2015-10-12 | 2018-05-04 | 国家计算机网络与信息安全管理中心 | High reliability data backup and restoration methods based on aggregated structure |
-
2016
- 2016-09-13 CN CN201610821056.2A patent/CN106445738B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN202134001U (en) * | 2011-03-07 | 2012-02-01 | 浪潮(北京)电子信息产业有限公司 | Executable file backup device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106445738A (en) | 2017-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106445738B (en) | Database backup method and device | |
| US9183268B2 (en) | Partition level backup and restore of a massively parallel processing database | |
| US9256665B2 (en) | Creation of inverted index system, and data processing method and apparatus | |
| WO2019148713A1 (en) | Sql statement processing method and apparatus, computer device, and storage medium | |
| CN109885642B (en) | Hierarchical storage method and device for full-text retrieval | |
| CN105955843A (en) | Method and device used for database recovery | |
| CN105353988A (en) | Metadata reading and writing method and device | |
| CN111666266A (en) | Data migration method and related equipment | |
| CN110750517B (en) | Data processing method, device and equipment of local storage engine system | |
| US10229142B2 (en) | Method and system for handling binary large objects | |
| CN111143323B (en) | MPP database management method, device and system | |
| CN104063468A (en) | Data report automatic generating and extracting method and device | |
| CN110704442A (en) | Real-time acquisition method and device for big data | |
| WO2018019310A1 (en) | Big data system data backup and recovery methods and devices, and computer storage medium | |
| CN103678041A (en) | Incremental backup method and system | |
| CN113094442A (en) | Full data synchronization method, device, equipment and medium | |
| CN112948504A (en) | Data acquisition method and device, computer equipment and storage medium | |
| CN105808451A (en) | Data caching method and related apparatus | |
| US10877881B2 (en) | In-place garbage collection of a sharded, replicated distributed state machine based on mergeable operations | |
| CN109376148B (en) | Data processing method and device for slow change dimension table and electronic equipment | |
| CN111026783A (en) | Anti-jamming data storage method, system and device | |
| CN107341255B (en) | Key value data processing method and device and electronic equipment | |
| CN113032385B (en) | Easily-extensible configurable data backup system and method | |
| CN113377777A (en) | Data loading method, data loading device, computer program product and storage medium | |
| CN110019507B (en) | Data synchronization method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200916 Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |