CN105446828A - Database backup and recovery method, apparatus and system - Google Patents
Database backup and recovery method, apparatus and system Download PDFInfo
- Publication number
- CN105446828A CN105446828A CN201410523108.9A CN201410523108A CN105446828A CN 105446828 A CN105446828 A CN 105446828A CN 201410523108 A CN201410523108 A CN 201410523108A CN 105446828 A CN105446828 A CN 105446828A
- Authority
- CN
- China
- Prior art keywords
- database
- full backup
- backup
- time point
- recovery
- 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.)
- Granted
Links
Abstract
Embodiments of the present invention disclose a database backup and recovery method, apparatus and system. When recovering a to-be-recovered database, data recovery is performed on the to-be-recovered database by using full backup data of the last full backup time of the to-be-recovered database and record data of the to-be recovered database between the last full backup time and a recovery target time point. By applying the method, apparatus and system disclosed by the embodiments of the present invention, it is avoided that the data between the database recovery target time point and the last database full backup time point before the database recovery target time point is lost as when being recovered, the database is recovered by using only data of the last database full backup before the database recovery target time point when performing recovery on a database, only the last database full backup data before the database recovering target time point is used, the loss of the data between the database recovering target time point and the last database full backup time point before the database recovering target time point is avoided.
Description
Technical field
The present invention relates to computer information safety technique field, particularly a kind of DB Backup, restoration methods, Apparatus and system.
Background technology
Along with the development of computer technology and Internet technology, the importance of information security becomes clear day by day.Database is also more and more paid attention to as an important content of information security.Database refer to longer-term storage in computing machine in a organized way, sharable data acquisition.If do not backed up database, so when database makes a mistake, just can not recover database, thus cause the loss of database data, the loss now caused cannot make up.
A kind of DB Backup conventional in prior art and restoration methods, pre-set database full-volume BACKUP TIME point, when the time arrives the database full-volume BACKUP TIME point pre-set, full backup is carried out to database, generate database full-volume Backup Data, so-called full backup refers to and backs up completely whole database.When database goes wrong, the last database full-volume Backup Data before object time point is recovered in usage data storehouse, recovers database.
But, database go wrong need to recover database time, apply above-mentioned DB Backup and restoration methods, can only by the state of the last database full-volume BACKUP TIME point before the recovering state of database to database recovery object time point, full backup is taken time longer, resource consumption is larger, therefore the time interval of adjacent twice full backup is long, and when there is database recovery demand during full backup, the last time that can obtain complete database full-volume Backup Data is after for a long time, the mass data of the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point is often caused to recover, therefore the mode of full backup has more defect and unsafe factor to exist.
Summary of the invention
The object of the embodiment of the present invention is to provide a kind of DB Backup, restoration methods, Apparatus and system, to prevent when database recovers, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.
For achieving the above object, the embodiment of the invention discloses a kind of database backup method, comprising:
According to the full backup time point of each database in database group, respectively at its full backup time point, full backup is carried out to each database;
Between the twice full backup time adjacent to arbitrary database, record the amendment to this database, generate record data.
Preferably, described database group, comprising:
Under multi-tenant environment, be respectively the set of a database existed independent of other tenants of every tenant's configuration.
Preferably, the full backup time point of each database in described database group pre-sets;
Or described full backup time point, determined by policy management element.
Preferably, described policy management element determines described full backup time point, comprising:
Described policy management element is according to the full backup time interval of each database in the database group preset, or according to the database number in database group, or the storage size of each database, or the Modification Frequency of database, determines the full backup time point of each database in database group.
Preferably, described policy management element determines described full backup time point, comprising:
Described policy management element is according to the BACKUP TIME interval of the database in described database group, calculate the number that each BACKUP TIME point intends the database starting full backup, if database number is greater than default threshold value, then the full backup time point start time of database maximum for storage space of database is moved to the second start time forward or backward.
Preferably, described method also comprises:
Incremental backup is carried out to described record data.
Preferably, described incremental backup is carried out to described record data, comprising:
In real time incremental backup is carried out to described record data;
Or
The incremental backup time point pre-set, carries out incremental backup to described record data.
Preferably, described method also comprises:
Incremental backup data before current last full backup is deleted.
Preferably, described by the incremental backup data deletion before current last full backup, comprising:
After completing n-th full backup, the incremental backup data between n-th full backup and (n-1)th full backup is deleted, wherein, n=2,3,4 ...
For achieving the above object, the embodiment of the invention discloses a kind of database restoring method, comprising:
Receive database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Full backup data before obtaining described recovery object time point T0, the last full backup time T1 of database to be restored;
According to the record data between described full backup data and T0 to T1, treat restore database and carry out date restoring.
Preferably, described according to the record data between described full backup data and T0 to T1, treat restore database and carry out date restoring, comprising:
Utilize the full backup data of the last full backup time T1 of database to be restored, by database recovery to be restored to T1 moment state;
Utilize the record data between T0 to T1, by database recovery to be restored to T0 moment state.
For achieving the above object, the embodiment of the invention discloses a kind of DB Backup device, comprising: full backup module, record data generation module, wherein,
Described full backup module, for the full backup time point according to each database in database group, carries out full backup to each database at its full backup time point respectively;
Described record data generation module, between the twice full backup time adjacent to arbitrary database, records the amendment to this database, generates record data.
Preferably, described database group, comprising:
Under multi-tenant environment, be respectively the set of a database existed independent of other tenants of every tenant's configuration.
Preferably, the full backup time point of each database in described database group pre-sets;
Or described full backup time point, determined by policy management element.
Preferably, described policy management element determines described full backup time point, comprising:
Described policy management element is according to the full backup time interval of each database in the database group preset, or according to the database number in database group, or the storage size of each database, or the Modification Frequency of database, determines the full backup time point of each database in database group.
Preferably, described policy management element, determine described full backup time point, comprising:
Described policy management element is according to the BACKUP TIME interval of the database in described database group, calculate the number that each BACKUP TIME point intends the database starting full backup, if database number is greater than default threshold value, then the full backup time point start time of database maximum for storage space of database is moved to the second start time forward or backward.
Preferably, described device also comprises: incremental backup module, wherein,
Described incremental backup module, for carrying out incremental backup to described record data.
Preferably, described incremental backup module, specifically for:
In real time incremental backup is carried out to described record data;
Or
The incremental backup time point pre-set, carries out incremental backup to described record data.
Preferably, described device also comprises: removing module, wherein,
Described removing module, for deleting the incremental backup data before current last full backup.
Preferably, described removing module, specifically for:
After completing n-th full backup, the incremental backup data between n-th full backup and (n-1)th full backup is deleted, wherein, n=2,3,4 ...
For achieving the above object, the embodiment of the invention discloses a kind of database recovery device, comprising: determination module, full backup acquisition module and recovery module, wherein,
Described determination module, for receiving database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Described full backup acquisition module, for before obtaining described recovery object time point T0, the full backup data of the last full backup time T1 of database to be restored;
Described recovery module, for according to the record data between described full backup data and T0 to T1, treats restore database and carries out date restoring.
Preferably, described recovery module, specifically for:
Utilize the full backup data of the last full backup time T1 of database to be restored, by database recovery to be restored to T1 moment state;
Utilize the record data between T0 to T1, by database recovery to be restored to T0 moment state.
For achieving the above object, the embodiment of the invention discloses a kind of data base backup recovery system, comprising: any one of any one and above-mentioned database recovery device of above-mentioned DB Backup device.
For achieving the above object, the embodiment of the invention discloses a kind of data base backup recovery system, comprising: full backup module, record data generation module, determination module, full backup acquisition module and recovery module,
Described full backup module, for the full backup time point according to database, carries out full backup to database at its each full backup time point;
Described record data generation module, between the time to adjacent twice full backup of database, or the amendment of omnidistance record to this database, generate record data;
Described determination module, for receiving database recovery instruction, determines the recovery object time point of database to be restored;
Described full backup acquisition module, for before obtaining described recovery object time point, the full backup data of database to be restored the last full backup time;
Described recovery module, for before obtaining described full backup data and recovering object time point to described recovery object time point, record data between time of the last full backup of database to be restored, treat restore database according to these record data and carry out date restoring.
For achieving the above object, the embodiment of the invention discloses a kind of data base backup recovery system, comprising: full backup module, record data generation module, determination module, full backup acquisition module and recovery module,
Described full backup module, for the full backup time point according to each database in database group, carries out full backup to each database at its full backup time point respectively;
Described record data generation module, between the time to adjacent twice full backup of arbitrary database, records the amendment to this database, generates record data;
Described determination module, for receiving database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Described full backup acquisition module, for before obtaining described recovery object time point T0, the full backup data of the last full backup time T1 of database to be restored;
Described recovery module, for according to the record data between described full backup data and T0 to T1, treats restore database and carries out date restoring.
As seen from the above technical solutions, embodiments provide a kind of DB Backup, restoration methods, Apparatus and system, according to the full backup time point of each database in database group, respectively at its full backup time point, full backup is carried out to each database; Between the twice full backup time adjacent to arbitrary database, record the amendment to this database, generate record data.When database goes wrong, the last database full-volume Backup Data before database usage data storehouse recovery object time point and this secondary data storehouse full backup are recovered to the record data that the database recovery object time puts database, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
The schematic flow sheet of a kind of database backup method that Fig. 1 provides for the embodiment of the present invention;
The schematic flow sheet of the another kind of database backup method that Fig. 2 provides for the embodiment of the present invention;
The schematic flow sheet of another database backup method that Fig. 3 provides for the embodiment of the present invention;
The schematic flow sheet of a kind of database restoring method that Fig. 4 provides for the embodiment of the present invention;
The structural representation of a kind of DB Backup device that Fig. 5 provides for the embodiment of the present invention;
The structural representation of the another kind of DB Backup device that Fig. 6 provides for the embodiment of the present invention;
The structural representation of another DB Backup device that Fig. 7 provides for the embodiment of the present invention;
The structural representation of a kind of database recovery device that Fig. 8 provides for the embodiment of the present invention.
Embodiment
Embodiments provide a kind of data base backup recovery system, this system comprises: full backup module, record data generation module, determination module, full backup acquisition module and recovery module, wherein,
Full backup module, for the full backup time point according to database, carries out full backup to database at its each full backup time point;
Record data generation module, between the time point to adjacent twice full backup of database, or the amendment of omnidistance record to this database, generate record data;
Determination module, for receiving database recovery instruction, determines the recovery object time point of database to be restored;
Full backup acquisition module, for before obtaining described recovery object time point, the full backup data of database to be restored the last full backup time;
Recover module, for before obtaining described full backup data and recovering object time point to described recovery object time point, record data between time of the last full backup of database to be restored, treat restore database according to these record data and carry out date restoring.
Embodiments provide a kind of data base backup recovery system, this system comprises: full backup module, record data generation module, determination module, full backup acquisition module and recovery module, wherein,
Full backup module, for the full backup time point according to each database in database group, carries out full backup to each database at its full backup time point respectively;
Record data generation module, between the time to adjacent twice full backup of arbitrary database, records the amendment to this database, generates record data;
Determination module, for receiving database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Full backup acquisition module, for before obtaining described recovery object time point T0, the full backup data of the last full backup time T1 of database to be restored;
Recover module, for according to the record data between described full backup data and T0 to T1, treat restore database and carry out date restoring.
Embodiments provide a kind of DB Backup, restoration methods, Apparatus and system, wherein,
Database backup method comprises: according to the full backup time point of database, carries out full backup to database at its each full backup time point; Between the time point to adjacent twice full backup of database, or the amendment of omnidistance record to this database, generate record data.
Database restoring method comprises: receive database recovery instruction, determine the recovery object time point of database to be restored; Full backup data before obtaining described recovery object time point, the database to be restored the last full backup time; Record data between time before obtaining described full backup data and recovering object time point to described recovery object time point, the last full backup of database to be restored, treat restore database according to these record data and carry out date restoring.
Embodiments provide a kind of DB Backup, restoration methods, Apparatus and system, wherein,
Database backup method comprises: according to the full backup time point of each database in database group, carries out full backup respectively to each database at its full backup time point; Between the time to adjacent twice full backup of arbitrary database, record the amendment to this database, generate record data.
Database restoring method comprises: receive database recovery instruction, and determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored; Full backup data before obtaining described recovery object time point T0, the last full backup time T1 of database to be restored; According to the record data between described full backup data and T0 to T1, treat restore database and carry out date restoring.
Wherein, full backup refers to and is backing up completely certain database in database group.Record data can be transaction journals.In actual applications, to the amendment of database, carry out recording the transaction journal that can adopt database, so-called transaction journal is a file separated with database file, it is used to the file of the update status of database of record, it can stylus point to any operation of database, and the result of record to be saved in independently in file.
When database goes wrong, the last database full-volume Backup Data before database usage data storehouse recovery object time point and this secondary data storehouse full backup are recovered to the record data that the database recovery object time puts database, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
Below by specific embodiment, the present invention is described in detail.
The schematic flow sheet of a kind of database backup method that Fig. 1 provides for the embodiment of the present invention, can comprise:
S101: according to the full backup time point of each database in database group, carries out full backup to each database at its full backup time point respectively;
Wherein, the full backup time point of each database in database group can for pre-setting.
Particularly, database group is under the environment of many tenants, is respectively the set of a database existed independent of other tenants of every tenant's configuration;
Exemplary, in embodiments of the present invention, tentation data storehouse group comprises: the database that name is called the database of Management System of Plot Estate, name is called X supermarket commodity and name are called the human resource management database of Y company.
Be called that Management System of Plot Estate is described for the name of database below,
Suppose that the full backup time point to Management System of Plot Estate database pre-sets is: 0:00,6:00,12:00 and 18:00 of every day, namely every day 4 full backup database Management System of Plot Estates, 6 hours, each full backup interval.
There are 7 tables in this Management System of Plot Estate database, be respectively: table 1A, table 1B, table 1C, table 1D, table 1E, table 1F and table 1G.
Wherein, show to record No. ID, infrastructure management company, title, address, telephone number and establishment time in 1A;
Record owner No. ID, name, move in the time in table 1B, room number, building number and No. ID, community;
Record infrastructure management company employee No. ID, name, responsible project in table 1C, be responsible for No. ID, community, home address and telephone number;
No. ID, recording cell, cell name, responsible official, creation data and subdistrict position in table 1D;
No. ID, recording user, name, password, user name and authority in table 1E;
Building number, No. ID, community, the number of plies and the built time is recorded in table 1F;
Record room number, Lou Hao, No. ID, community in table 1G, whether move in and user ID.
Suppose that the state of certain day this Management System of Plot Estate database of 6:00 is as follows:
Table 1A
| Cid | Cname | Cads | Cnum | Ctime |
| 1 | Safety property | Beijing is exposed to the sun | 85510000 | 2003-10-3 |
| 2 | For your property | Haidian, Beijing | 88520101 | 2005-12-5 |
Table 1B
| Yid | Yname | Ytime | Room | Louyu | Xid |
| 1 | Zhang San | 2006-10-3 | 101 | 1 | 1 |
| 2 | Li Si | 2006-5-6 | 201 | 2 | 2 |
Table 1C
| Wid | Wname | Xiangmu | Xid | Wads | Wnum |
| 1 | King five | Maintenance | 1 | Handan, Hebei | 15910101223 |
| 2 | Zhao six | Security | 2 | Shandong Zibo | 13652365986 |
Table 1D
| Xid | Xname | Wname | Xdate | Weizhi |
| 1 | Community, Mingguang City | Qian great | 2003-8-8 | Beijing is exposed to the sun |
| 2 | Build community | Sun great | 2004-5-7 | Haidian, Beijing |
Table 1E
| Tid | Tname | Tpas | Tnum | Quanxian |
| 1 | Admin | Admin | Admin | Admin |
| 2 | User | User | User | Guest |
Table 1F
| Louyu | Xid | Lnum | Date |
| 1 | 1 | 3 | 2005-5-4 |
| 2 | 1 | 3 | 2005-5-6 |
| 1 | 2 | 3 | 2004-6-5 |
| 2 | 2 | 3 | 2005-8-4 |
Table 1G
| Room | Louyu | Xid | YN | Tid |
| 101 | 1 | 1 | Y | 1 |
| 201 | 1 | 1 | N |
| 301 | 1 | 1 | N | |
| 101 | 2 | 1 | N | |
| 201 | 2 | 1 | N | |
| 301 | 2 | 1 | N | |
| 101 | 1 | 2 | N | |
| 201 | 1 | 2 | N | |
| 301 | 1 | 2 | N | |
| 101 | 2 | 2 | N | |
| 201 | 2 | 2 | Y | 2 |
| 301 | 2 | 2 | N |
Management System of Plot Estate database under this state is carried out a full backup, generates the full backup data of this Management System of Plot Estate database of 6:00.
The full backup time point of each database in database group also can: determine by pre-setting a policy management element.
Concrete, pre-set a policy management element, policy management element is according to the full backup time interval of each database in the database group preset, or according to the database number in database group, or the storage size of each database, or the Modification Frequency of database, determines the full backup time point of each database in database group.Policy management element can also according to the BACKUP TIME interval of the database in described database group, calculate the number that each BACKUP TIME point intends the database starting full backup, if database number is greater than default threshold value, then the full backup time point start time of database maximum for storage space of database is moved to the second start time forward or backward.
Concrete, under multi-tenant environment, be a database existed independent of other tenants of every tenant's configuration.For at least one or multiple database backs up time, the full backup time interval of different databases is come, instead of backing up at the same time as far as possible simultaneously.
Particularly, we can, from the time of creation database, be set to carry out full backup every a fixing time period to this database.Due under multi-tenant environment, for the time of each tenant's creation database is unfixed, therefore the full backup time point of each database, normally isolated.But also there will be, the database of certain time point full backup too much brings the situation of pressure to occur to backup server, therefore a policy management element is set, for the full backup time point of the database cluster of whole backup server manages, make the BACKUP TIME point of each tenant different, the time point of full backup is able to equilibrium assignment.
Particularly, policy management element determines that the full backup time point of each database is: according to the full backup time interval of each database preset, according to the number of database, the Modification Frequency of database, the factors such as the size of storage space of database are determined.
Particularly, in the full backup time interval of each database, user or native system can be had to carry out artificial or automatic calculating and setting.
Particularly, policy management element has how many databases to start full backup according to each BACKUP TIME point of the BACKUP TIME interval calculation of all databases, if database number is greater than default threshold value, then the full backup time point start time of database maximum for storage space of database is moved to the second start time forward or backward.Such as, under multi-tenant environment, establishment has 3 databases altogether, and the full backup time interval of database 1 is 3 hours, and storage space is 5G; The full backup time interval of database 2 is 2 hours, and storage space is 6G; The full backup time interval of database 3 is 1 hour, and storage space is 7G.Suppose that the very first time starting point of 3 databases is intended carrying out full backup when being separately positioned on 1 point, 2 points, 3 o'clock, policy management element calculates, 3 databases will be had to start full backup when 4 o'clock simultaneously, if the threshold value preset is 2,3 are greater than default threshold value 2, so the very first time starting point that storage space is the maximum data storehouse 3 of 7G by policy management element postpones half an hour backward.
S102: between the twice full backup time adjacent to arbitrary database, record the amendment to this database, generates record data.
Exemplary, to the amendment that above-mentioned Management System of Plot Estate database carries out, can adopt and carry out record based on the mode changed before and after data, as shown in table 2:
Table 2
| Time | Table name | Row name | Line number | Before change | After change |
| 8:10 | Table 1B | Room | 1 | 101 | 301 |
| 8:10 | Table 1G | YN | 1 | Y | N |
| 8:10 | Table 1G | Tid | 1 | 1 | |
| 8:10 | Table 1G | YN | 3 | N | Y |
| 8:10 | Table 1G | Tid | 3 | 1 | |
| 9:20 | Table 1A | Cid | 3 | 3 | |
| 9:20 | Table 1A | Cname | 3 | Permanent really property | |
| 9:20 | Table 1A | Cads | 3 | Beijing is exposed to the sun | |
| 9:20 | Table 1A | Cnum | 3 | 85514520 | |
| 9:20 | Table 1A | Ctime | 3 | 2004-5-6 | |
| 12:25 | Table 1C | Wid | 1 | 1 | |
| 12:25 | Table 1C | Wname | 1 | King five | |
| 12:25 | Table 1C | Xiangmu | 1 | Maintenance | |
| 12:25 | Table 1C | Xid | 1 | 1 | |
| 12:25 | Table 1C | Wads | 1 | Handan, Hebei | |
| 12:25 | Table 1C | Wnum | 1 | 15910101223 |
To the amendment that Management System of Plot Estate database carries out, the mode based on statement can also be adopted to carry out record,
8:10, update ' show 1B ' setRoom=' 301 ' whereYname=' Zhang San ';
Update ' shows 1G ' setYN=' N ' andTid=" whereRoom=' 101 ' ANDLouyu=' 1 ';
Update ' shows 1G ' setYN=' Y ' andTid=' 1 ' whereRoom=' 301 ' ANDLouyu=' 1 ';
9:20, insertinto ' show 1A ' values (' 3 ', ' permanent really property ', ' Chaoyang, Beijing ', ' 85514520 ', ' 2004-5-6 ');
12:25, deletefrom ' show 1C ' whereWname=' king five ';
In actual applications, to the amendment of database, carry out recording the transaction journal that can adopt database, so-called transaction journal is a file separated with database file, it is used to the file of the update status of database of record, it can stylus point to any operation of database, and the result of record to be saved in independently in file.
It should be noted that, not to the amendment of database in the application, the mode of carrying out recording limits, and any possible implementation can be applied in the application.
It should be noted that, the above-mentioned name for database is called that Management System of Plot Estate is described, and is only an instantiation, and the restriction of paired not the application.
The present invention is embodiment illustrated in fig. 1 in application, according to the full backup time point of each database in database group, carries out full backup respectively to each database at its full backup time point; Between the twice full backup time adjacent to arbitrary database, record the amendment to this database, generate record data.When database goes wrong, the last database full-volume Backup Data before database usage data storehouse recovery object time point and this secondary data storehouse full backup are recovered to the record data that the database recovery object time puts database, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.
The schematic flow sheet of the another kind of database backup method that Fig. 2 provides for the embodiment of the present invention, the present invention is embodiment illustrated in fig. 2 on basis embodiment illustrated in fig. 1, increases S103: carry out incremental backup to described record data.
Wherein, the data that incremental backup was revised after referring to the last backup of each only backup, can carry out incremental backup in real time to described record data.
Considering in actual applications, in real time incremental backup being carried out, occupying system resources to record data, in order to save taking of system resource, incremental backup time point can be pre-set, carrying out incremental backup to recording the incremental backup time point that data are pre-setting.
Suppose that the incremental backup time point pre-set is: 2:00,4:00,8:00,9:00,10:00,14:00,16:00,20:00 and 22:00 of every day,
Then to the amendment that above-mentioned Management System of Plot Estate database carries out, the incremental backup that record data are carried out is respectively:
Carry out first time incremental backup at 8:00, to the amendment of Management System of Plot Estate database 6:00-8:00, the record data of generation carry out incremental backup,
Carry out second time incremental backup at 9:00, to the amendment of Management System of Plot Estate database 8:00-9:00, the record data of generation carry out incremental backup,
Carry out third time incremental backup at 10:00, to the amendment of Management System of Plot Estate database 9:00-10:00, the record data of generation carry out incremental backup,
Carry out the 4th incremental backup at 14:00, to the amendment of Management System of Plot Estate database 12:00-14:00, the record data of generation carry out incremental backup.
It should be noted that, the above-mentioned name for database is called that Management System of Plot Estate is described, and is only an instantiation, and the restriction of paired not the application.
The present invention is embodiment illustrated in fig. 2 in application, when database goes wrong, the last database full-volume Backup Data before database usage data storehouse recovery object time point and this secondary data storehouse full backup are recovered to the record data that the database recovery object time puts database, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.And the record data generated are backed up, prevents the loss owing to recording data, the generation of the situation causing database not repair.
Consider in actual applications, the number of times carrying out incremental backup is more, the incremental backup data generated more takies disk space, in order to reduce taking of disk space, the embodiment of the present invention also provides another database backup method, shown in Figure 3, the present invention is embodiment illustrated in fig. 3 on basis embodiment illustrated in fig. 2, increases S104: the incremental backup data before current last full backup deleted.
Concrete, after completing a full backup, when data base administrator confirms this full backup success and the database of this full backup time point is errorless, the incremental backup data before this full backup time point can be deleted.In actual applications, after completing n-th full backup, the incremental backup data between n-th full backup and (n-1)th full backup and/or differential backup data can be deleted, wherein, n=2,3,4 ...
The present invention is embodiment illustrated in fig. 3 in application, decreases due to multiple incremental backup, makes incremental backup data the taking disk space generated.
The schematic flow sheet of a kind of database restoring method that Fig. 4 provides for the embodiment of the present invention, can comprise:
S201: receive database recovery instruction, determines the recovery object time point T0 of database to be restored;
Wherein, database recovery instruction comprises the mark of database to be restored, and this mark can be the title of database in actual applications.
Exemplary, be called that Management System of Plot Estate is described for the name of database below.
In embodiments of the present invention, under normal circumstances, by database recovery to current time, namely can recover object time point T0 and refer to current time, such as, when running into the situation such as power failure, computing machine down machine, need the database returning to current time.
In some cases, also need by before database recovery to current time sometime, the application is also applicable to, specify recover the object time point T0 situation.Such as: current time is 13:00, data base administrator carries out data check to Management System of Plot Estate and finds that its data make a mistake, the analysis found that, divide the data of this database to make a mistake from 10:20, therefore need the date restoring of this database to 10:20.
Also such as, Database Systems find that when carrying out self-inspection error in data appears in certain full backup data, when so present in database recovery system prepares to repair this mistake, recover object time point T0 by determining according to the BACKUP TIME of database to be restored.
Also such as, user oneself goes back on one's word to after database read-write operation, and when to wish database recovery to the state of certain time point of past that oneself is wished, present in database recovery system obtains the recovery object time point T0 of the database to be restored that a user informs.
S202: full backup data before obtaining described recovery object time point T0, the last full backup time T1 of database to be restored;
10:20 is put release time, the full backup that the last database full-volume backup before first finding 10:20 is carried out for 6:00 according to S201 established data storehouse.
S203: according to the record data between described full backup data and T0 to T1, treats restore database and carries out date restoring.
Wherein, information described in record data is the full backup database deadline T1 of the last time, to the data of modifying to database received between the date restoring instruction time.
Concrete, utilize the full backup data of the last full backup time T1 of database to be restored, by database recovery to be restored to T1 moment state;
Utilize the record data between T0 to T1, by database recovery to be restored to T0 moment state.
First, utilize the full backup data of 6:00 that Management System of Plot Estate database recovery is as follows to the state of 6:00:
Table 1A
| Cid | Cname | Cads | Cnum | Ctime |
| 1 | Safety property | Beijing is exposed to the sun | 85510000 | 2003-10-3 |
| 2 | For your property | Haidian, Beijing | 88520101 | 2005-12-5 |
Table 1B
| Yid | Yname | Ytime | Room | Louyu | Xid |
| 1 | Zhang San | 2006-10-3 | 101 | 1 | 1 |
| 2 | Li Si | 2006-5-6 | 201 | 2 | 2 |
Table 1C
| Wid | Wname | Xiangmu | Xid | Wads | Wnum |
| 1 | King five | Maintenance | 1 | Handan, Hebei | 15910101223 |
| 2 | Zhao six | Security | 2 | Shandong Zibo | 13652365986 |
Table 1D
| Xid | Xname | Wname | Xdate | Weizhi |
| 1 | Community, Mingguang City | Qian great | 2003-8-8 | Beijing is exposed to the sun |
| 2 | Build community | Sun great | 2004-5-7 | Haidian, Beijing |
Table 1E
| Tid | Tname | Tpas | Tnum | Quanxian |
| 1 | Admin | Admin | Admin | Admin |
| 2 | User | User | User | Guest |
Table 1F
| Louyu | Xid | Lnum | Date |
| 1 | 1 | 3 | 2005-5-4 |
| 2 | 1 | 3 | 2005-5-6 |
| 1 | 2 | 3 | 2004-6-5 |
| 2 | 2 | 3 | 2005-8-4 |
Table 1G
| Room | Louyu | Xid | YN | Tid |
| 101 | 1 | 1 | Y | 1 |
| 201 | 1 | 1 | N | |
| 301 | 1 | 1 | N | |
| 101 | 2 | 1 | N | |
| 201 | 2 | 1 | N | |
| 301 | 2 | 1 | N |
| 101 | 1 | 2 | N | |
| 201 | 1 | 2 | N | |
| 301 | 1 | 2 | N | |
| 101 | 2 | 2 | N | |
| 201 | 2 | 2 | Y | 2 |
| 301 | 2 | 2 | N |
Record data between recycling 6:00 to 10:20, that is: the data to Management System of Plot Estate database update of 8:10 record, the data to Management System of Plot Estate database update of 9:20 record.
Date restoring is carried out to Management System of Plot Estate database.
Management System of Plot Estate database recovery is as follows to the state of 9:20:
Table 1A
| Cid | Cname | Cads | Cnum | Ctime |
| 1 | Safety property | Beijing is exposed to the sun | 85510000 | 2003-10-3 |
| 2 | For your property | Haidian, Beijing | 88520101 | 2005-12-5 |
| 3 | Permanent really property | Beijing is exposed to the sun | 85514520 | 2004-5-6 |
Table 1B
| Yid | Yname | Ytime | Room | Louyu | Xid |
| 1 | Zhang San | 2006-10-3 | 301 | 1 | 1 |
| 2 | Li Si | 2006-5-6 | 201 | 2 | 2 |
Table 1C
| Wid | Wname | Xiangmu | Xid | Wads | Wnum |
| 1 | King five | Maintenance | 1 | Handan, Hebei | 15910101223 |
| 2 | Zhao six | Security | 2 | Shandong Zibo | 13652365986 |
Table 1D
| Xid | Xname | Wname | Xdate | Weizhi |
| 1 | Community, Mingguang City | Qian great | 2003-8-8 | Beijing is exposed to the sun |
| 2 | Build community | Sun great | 2004-5-7 | Haidian, Beijing |
Table 1E
| Tid | Tname | Tpas | Tnum | Quanxian |
| 1 | Admin | Admin | Admin | Admin |
| 2 | User | User | User | Guest |
Table 1F
| Louyu | Xid | Lnum | Date |
| 1 | 1 | 3 | 2005-5-4 |
| 2 | 1 | 3 | 2005-5-6 |
| 1 | 2 | 3 | 2004-6-5 |
| 2 | 2 | 3 | 2005-8-4 |
Table 1G
| Room | Louyu | Xid | YN | Tid |
| 101 | 1 | 1 | N | |
| 201 | 1 | 1 | N | |
| 301 | 1 | 1 | Y | 1 |
| 101 | 2 | 1 | N | |
| 201 | 2 | 1 | N |
| 301 | 2 | 1 | N | |
| 101 | 1 | 2 | N | |
| 201 | 1 | 2 | N | |
| 301 | 1 | 2 | N | |
| 101 | 2 | 2 | N | |
| 201 | 2 | 2 | Y | 2 |
| 301 | 2 | 2 | N |
Due at 9:20 to 10:20, do not modify to Management System of Plot Estate database, therefore the state of 10:20 Management System of Plot Estate database is identical with the state of 9:20 Management System of Plot Estate database.So far, the date restoring of Management System of Plot Estate database completes.
When by database recovery to current time, ideally, can be identical with the database data of current time T2 with the database data of current time T2 immediate T3 time, but likely transaction log backup not in time, cause the database finally returning to the T3 time, early than the database data of T2 time, variant with the database of T2 time.
Citing 1:
Suppose have first full backup to be completed in the T0 time, second full backup time starts from the T1 time, to terminate in the T4 time, when second full backup database has not yet backed up, user in T2 time requirement by database recovery to the T2 time, but the transaction journal of T2 time have one not yet record enter, for meeting the demand of user, technical scheme of the present invention can realize returning to database early than the T3 time of T2 time to user.After the T2 time receives the database recovery request of user, search the full backup database of the last time, i.e. the database of T0 time, search the transaction journal of the last record, find not have the transaction journal of T2 time, the transaction journal of the last is T3 time point.The data operation information of the database described in the transaction journal of T0 time to T3 time, progressively returns to the database of T3 time point by the database of T0 time, namely reduction obtains and T2 time immediate T3 temporal database.In citing 1, time T0<T1<T3<T2LEssT. LTssT.LTT4.
Citing 2:
Suppose have first full backup to be completed in the T0 time, second full backup time starts from the T1 time, and terminate in the T4 time, third time full backup is not yet started during T2 time after the T4 time, user in T2 time requirement by database recovery to the T2 time, but the transaction journal of T2 time has one not yet to record, the last transaction journal is the transaction journal of T3 time, for meeting the demand of user, technical scheme of the present invention can realize returning to database early than the T3 time of T2 time to user.After the T2 time receives the database recovery request of user, search the full backup database of the last time, i.e. the database of T4 time, search the transaction journal of the last record, find not have the transaction journal of T2 time, the transaction journal of the last is T3 time point.The data operation information of the database described in the transaction journal of T4 time to T3 time, progressively returns to the database of T3 time point by the database of T4 time, namely reduction obtains and T2 time immediate T3 temporal database.In citing 2, time T0<T1<T4<T3LEssT. LTssT.LTT2.
It should be noted that, the above-mentioned name for database is called that Management System of Plot Estate is described, and is only an instantiation, and the restriction of paired not the application.
The present invention is embodiment illustrated in fig. 4 in application, when database goes wrong, the last database full-volume Backup Data before database usage data storehouse recovery object time point and this secondary data storehouse full backup are recovered to the record data that the database recovery object time puts database, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.
Corresponding with above-mentioned embodiment of the method, the embodiment of the present invention also provides data backup device and Data Recapture Unit.
The structural representation of a kind of DB Backup device that Fig. 5 provides for the embodiment of the present invention, can comprise: full backup module 301 and record data generation module 302,
Wherein, full backup module 301, for the full backup time point according to each database in database group, carries out full backup to each database at its full backup time point respectively; Wherein,
Database group is: under multi-tenant environment, is respectively the set of a database existed independent of other tenants of every tenant's configuration.
The full backup time point of each database in database group, can pre-set, also can be that a policy management element by pre-setting is determined, policy management element can according to the full backup time interval of each database in the database group preset, or determine according to the storage size of the database number in database group and each database.
Particularly, policy management element, can according to the full backup time interval of each database in the database group preset, or according to the database number in database group, or the storage size of each database, or the Modification Frequency of database, determines the full backup time point of each database in database group.
Particularly, policy management element, can also according to the BACKUP TIME interval of the database in described database group, calculate the number that each BACKUP TIME point intends the database starting full backup, if database number is greater than default threshold value, then the full backup time point start time of database maximum for storage space of database is moved to the second start time forward or backward.
Record data generation module 302, between the twice full backup time adjacent to arbitrary database, records the amendment to this database, generates record data.
The present invention is embodiment illustrated in fig. 5 in application, at the full backup time point according to each database in database group, carries out full backup respectively to each database at its full backup time point; Between to adjacent twice full backup of arbitrary database, record the amendment to this database, generate record data.When database goes wrong, the last database full-volume Backup Data before database usage data storehouse recovery object time point and this secondary data storehouse full backup are recovered to the record data that the database recovery object time puts database, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.
The structural representation of the another kind of DB Backup device that Fig. 6 provides for the embodiment of the present invention, the present invention is embodiment illustrated in fig. 6 on basis embodiment illustrated in fig. 5, increases incremental backup module 303, wherein,
Incremental backup module 303, for carrying out incremental backup to described record data.
The incremental backup module 303 of the embodiment of the present invention, specifically may be used for:
In real time incremental backup is carried out to described record data;
Or
The incremental backup time point pre-set, carries out incremental backup to described record data.
The present invention is embodiment illustrated in fig. 6 in application, when database goes wrong, the last database full-volume Backup Data before database usage data storehouse recovery object time point and this secondary data storehouse full backup are recovered to the record data that the database recovery object time puts database, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.And the record data generated are backed up, prevents the loss owing to recording data, the generation of the situation causing database not repair.
The structural representation of another DB Backup device that Fig. 7 provides for the embodiment of the present invention, the present invention is embodiment illustrated in fig. 7 on basis embodiment illustrated in fig. 6, increases removing module 304, wherein,
Removing module 304, for deleting the incremental backup data before current last full backup.
The removing module 304 of the embodiment of the present invention, specifically may be used for:
After completing n-th full backup, the incremental backup data between n-th full backup and (n-1)th full backup is deleted, wherein, n=2,3,4 ...
The present invention is embodiment illustrated in fig. 7 in application, decreases due to multiple incremental backup, makes incremental backup data the taking disk space generated.
The structural representation of a kind of database recovery device that Fig. 8 provides for the embodiment of the present invention, can comprise: determination module 401, full backup acquisition module 402 and recovery module 403, wherein,
Determination module 401, for receiving database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Full backup acquisition module 402, for before obtaining described recovery object time point T0, the full backup data of the last full backup time T1 of database to be restored;
Recover module 403, for according to the record data between described full backup data and T0 to T1, treat restore database and carry out date restoring.
The recovery module 403 of the embodiment of the present invention, specifically may be used for:
Utilize the full backup data of the last full backup time T1 of database to be restored, by database recovery to be restored to T1 moment state;
Utilize the record data between T0 to T1, by database recovery to be restored to T0 moment state.
The present invention is embodiment illustrated in fig. 8 in application, when database goes wrong, the last database full-volume Backup Data before database usage data storehouse recovery object time point and this secondary data storehouse full backup are recovered to the record data that the database recovery object time puts database, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.
The embodiment of the present invention also provides a kind of data base backup recovery system, comprises any one and above-mentioned database recovery device of above-mentioned DB Backup device any one.
The embodiment of the present invention also provides a kind of data base backup recovery system, comprising: full backup module, record data generation module, determination module, full backup acquisition module and recovery module, wherein,
Described full backup module, for the full backup time point according to database, carries out full backup to database at its each full backup time point;
Described record data generation module, between the time to adjacent twice full backup of database, or the amendment of omnidistance record to this database, generate record data;
Described determination module, for receiving database recovery instruction, determines the recovery object time point of database to be restored;
Described full backup acquisition module, for before obtaining described recovery object time point, the full backup data of database to be restored the last full backup time;
Described recovery module, for before obtaining described full backup data and recovering object time point to described recovery object time point, record data between time of the last full backup of database to be restored, treat restore database according to these record data and carry out date restoring.
The embodiment of the present invention also provides a kind of data base backup recovery system, comprising: full backup module, record data generation module, determination module, full backup acquisition module and recovery module, wherein,
Described full backup module, for the full backup time point according to each database in database group, carries out full backup to each database at its full backup time point respectively;
Described record data generation module, between the time to adjacent twice full backup of arbitrary database, records the amendment to this database, generates record data;
Described determination module, for receiving database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Described full backup acquisition module, for before obtaining described recovery object time point T0, the full backup data of the last full backup time T1 of database to be restored;
Described recovery module, for according to the record data between described full backup data and T0 to T1, treats restore database and carries out date restoring.
The data base backup recovery system that the application embodiment of the present invention provides, avoid when database recovery, the last database full-volume Backup Data that usage data storehouse is recovered before object time point recovers database, the loss of data between the last database full-volume BACKUP TIME point before database recovery object time point to database recovery object time point.
It should be noted that, in this article, the such as relational terms of first and second grades and so on is only used for an entity or operation to separate with another entity or operational zone, and not necessarily requires or imply the relation that there is any this reality between these entities or operation or sequentially.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thus make to comprise the process of a series of key element, method, article or equipment and not only comprise those key elements, but also comprise other key elements clearly do not listed, or also comprise by the intrinsic key element of this process, method, article or equipment.When not more restrictions, the key element limited by statement " comprising ... ", and be not precluded within process, method, article or the equipment comprising described key element and also there is other identical element.
Each embodiment in this instructions all adopts relevant mode to describe, between each embodiment identical similar part mutually see, what each embodiment stressed is the difference with other embodiments.Especially, for device embodiment, because it is substantially similar to embodiment of the method, so description is fairly simple, relevant part illustrates see the part of embodiment of the method.
One of ordinary skill in the art will appreciate that all or part of step realized in said method embodiment is that the hardware that can carry out instruction relevant by program has come, described program can be stored in computer read/write memory medium, here the alleged storage medium obtained, as: ROM/RAM, magnetic disc, CD etc.
The foregoing is only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.All any amendments done within the spirit and principles in the present invention, equivalent replacement, improvement etc., be all included in protection scope of the present invention.
Claims (25)
1. a database backup method, is characterized in that, described method comprises:
According to the full backup time point of each database in database group, respectively at its full backup time point, full backup is carried out to each database;
Between the twice full backup time adjacent to arbitrary database, record the amendment to this database, generate record data.
2. method according to claim 1, is characterized in that, described database group, comprising:
Under multi-tenant environment, be respectively the set of a database existed independent of other tenants of every tenant's configuration.
3. method according to claim 1 and 2, is characterized in that, the full backup time point of each database in described database group pre-sets;
Or described full backup time point, determined by policy management element.
4. method according to claim 3, is characterized in that, described policy management element determines described full backup time point, comprising:
Described policy management element is according to the full backup time interval of each database in the database group preset, or according to the database number in database group, or the storage size of each database, or the Modification Frequency of database, determines the full backup time point of each database in database group.
5. method according to claim 3, is characterized in that, described policy management element determines described full backup time point, comprising:
Described policy management element is according to the BACKUP TIME interval of the database in described database group, calculate the number that each BACKUP TIME point intends the database starting full backup, if database number is greater than default threshold value, then the full backup time point start time of database maximum for storage space of database is moved to the second start time forward or backward.
6. method according to claim 1, is characterized in that, described method also comprises:
Incremental backup is carried out to described record data.
7. method according to claim 6, is characterized in that, describedly carries out incremental backup to described record data, comprising:
In real time incremental backup is carried out to described record data;
Or
The incremental backup time point pre-set, carries out incremental backup to described record data.
8. method according to claim 6, is characterized in that, described method also comprises:
Incremental backup data before current last full backup is deleted.
9. method according to claim 8, is characterized in that, described by the incremental backup data deletion before current last full backup, comprising:
After completing n-th full backup, the incremental backup data between n-th full backup and (n-1)th full backup is deleted, wherein, n=2,3,4 ...
10. a database restoring method, is characterized in that, described method comprises:
Receive database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Full backup data before obtaining described recovery object time point T0, the last full backup time T1 of database to be restored;
According to the record data between described full backup data and T0 to T1, treat restore database and carry out date restoring.
11. methods according to claim 10, is characterized in that, described according to the record data between described full backup data and T0 to T1, treat restore database and carry out date restoring, comprising:
Utilize the full backup data of the last full backup time T1 of database to be restored, by database recovery to be restored to T1 moment state;
Utilize the record data between T0 to T1, by database recovery to be restored to T0 moment state.
12. 1 kinds of DB Backup devices, is characterized in that, described device comprises: full backup module, record data generation module, wherein,
Described full backup module, for the full backup time point according to each database in database group, carries out full backup to each database at its full backup time point respectively;
Described record data generation module, between the twice full backup time adjacent to arbitrary database, records the amendment to this database, generates record data.
13. devices according to claim 12, is characterized in that, described database group, comprising:
Under multi-tenant environment, be respectively the set of a database existed independent of other tenants of every tenant's configuration.
14. devices according to claim 12 or 13, it is characterized in that, the full backup time point of each database in described database group pre-sets;
Or described full backup time point, determined by policy management element.
15. devices according to claim 14, is characterized in that, described policy management element determines described full backup time point, comprising:
Described policy management element is according to the full backup time interval of each database in the database group preset, or according to the database number in database group, or the storage size of each database, or the Modification Frequency of database, determines the full backup time point of each database in database group.
16. devices according to claim 14, is characterized in that, described policy management element, determine described full backup time point, comprising:
Described policy management element is according to the BACKUP TIME interval of the database in described database group, calculate the number that each BACKUP TIME point intends the database starting full backup, if database number is greater than default threshold value, then the full backup time point start time of database maximum for storage space of database is moved to the second start time forward or backward.
17. devices according to claim 12, is characterized in that, described device also comprises: incremental backup module, wherein,
Described incremental backup module, for carrying out incremental backup to described record data.
18. devices according to claim 17, is characterized in that, described incremental backup module, specifically for:
In real time incremental backup is carried out to described record data;
Or
The incremental backup time point pre-set, carries out incremental backup to described record data.
19. devices according to claim 19, is characterized in that, described device also comprises: removing module, wherein,
Described removing module, for deleting the incremental backup data before current last full backup.
20. devices according to claim 19, is characterized in that, described removing module, specifically for:
After completing n-th full backup, the incremental backup data between n-th full backup and (n-1)th full backup is deleted, wherein, n=2,3,4 ...
21. 1 kinds of database recovery devices, is characterized in that, described device comprises: determination module, full backup acquisition module and recovery module, wherein,
Described determination module, for receiving database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Described full backup acquisition module, for before obtaining described recovery object time point T0, the full backup data of the last full backup time T1 of database to be restored;
Described recovery module, for according to the record data between described full backup data and T0 to T1, treats restore database and carries out date restoring.
22. devices according to claim 21, is characterized in that, described recovery module, specifically for:
Utilize the full backup data of the last full backup time T1 of database to be restored, by database recovery to be restored to T1 moment state;
Utilize the record data between T0 to T1, by database recovery to be restored to T0 moment state.
23. 1 kinds of data base backup recovery systems, comprise any one DB Backup device of claim 12 to 20 and any one database recovery device of claim 21 and 22.
24. 1 kinds of data base backup recovery systems, is characterized in that, described system comprises: full backup module, record data generation module, determination module, full backup acquisition module and recovery module, wherein,
Described full backup module, for the full backup time point according to database, carries out full backup to database at its each full backup time point;
Described record data generation module, between the time to adjacent twice full backup of database, or the amendment of omnidistance record to this database, generate record data;
Described determination module, for receiving database recovery instruction, determines the recovery object time point of database to be restored;
Described full backup acquisition module, for before obtaining described recovery object time point, the full backup data of database to be restored the last full backup time;
Described recovery module, for before obtaining described full backup data and recovering object time point to described recovery object time point, record data between time of the last full backup of database to be restored, treat restore database according to these record data and carry out date restoring.
25. 1 kinds of data base backup recovery systems, is characterized in that, described system comprises: full backup module, record data generation module, determination module, full backup acquisition module and recovery module, wherein,
Described full backup module, for the full backup time point according to each database in database group, carries out full backup to each database at its full backup time point respectively;
Described record data generation module, between the time to adjacent twice full backup of arbitrary database, records the amendment to this database, generates record data;
Described determination module, for receiving database recovery instruction, determine the recovery object time point T0 of database to be restored, described database recovery instruction comprises the mark of database to be restored;
Described full backup acquisition module, for before obtaining described recovery object time point T0, the full backup data of the last full backup time T1 of database to be restored;
Described recovery module, for according to the record data between described full backup data and T0 to T1, treats restore database and carries out date restoring.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410523108.9A CN105446828B (en) | 2014-09-30 | 2014-09-30 | A kind of DB Backup, restoration methods, apparatus and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410523108.9A CN105446828B (en) | 2014-09-30 | 2014-09-30 | A kind of DB Backup, restoration methods, apparatus and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105446828A true CN105446828A (en) | 2016-03-30 |
| CN105446828B CN105446828B (en) | 2019-05-31 |
Family
ID=55557061
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410523108.9A Active CN105446828B (en) | 2014-09-30 | 2014-09-30 | A kind of DB Backup, restoration methods, apparatus and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105446828B (en) |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105955845A (en) * | 2016-04-26 | 2016-09-21 | 浪潮电子信息产业股份有限公司 | Data recovery method and device |
| CN106201780A (en) * | 2016-07-08 | 2016-12-07 | 浪潮通用软件有限公司 | A kind of historical data method of reducing |
| CN106648980A (en) * | 2016-12-12 | 2017-05-10 | 北京雷石天地电子技术有限公司 | Backup and recovery method and backup and recovery device for high-availability server databases in offline places |
| CN106776120A (en) * | 2016-11-24 | 2017-05-31 | 珠海市魅族科技有限公司 | The method and device of data recovery |
| CN107229540A (en) * | 2017-06-06 | 2017-10-03 | 贵州易鲸捷信息技术有限公司 | A kind of database restoring method and system based on time point |
| WO2017215432A1 (en) * | 2016-06-15 | 2017-12-21 | 腾讯科技（深圳）有限公司 | Data retracement method, device and system |
| CN107515801A (en) * | 2017-09-13 | 2017-12-26 | 绿金在线电子商务有限公司 | A kind of data self-repairing method based on relevant database |
| CN108156264A (en) * | 2018-03-06 | 2018-06-12 | 爱普（福建）科技有限公司 | A kind of method of data synchronization towards dual-computer redundancy |
| CN108241555A (en) * | 2016-12-26 | 2018-07-03 | 阿里巴巴集团控股有限公司 | A kind of backup of distributed data base, restoration methods, device and server |
| CN108511035A (en) * | 2017-02-23 | 2018-09-07 | 仁智(苏州)医学研究有限公司 | A kind of data managing method and device of hospital information system |
| CN109101369A (en) * | 2018-08-21 | 2018-12-28 | 郑州云海信息技术有限公司 | A kind of sustainable protection method, system and device of business host data |
| CN109408283A (en) * | 2018-09-04 | 2019-03-01 | 深圳市宝德计算机系统有限公司 | A kind of method of server data protection, equipment and storage medium |
| CN110263095A (en) * | 2019-05-31 | 2019-09-20 | 众安在线财产保险股份有限公司 | Backup and recovery method, apparatus, computer equipment and storage medium |
| CN110673985A (en) * | 2019-09-20 | 2020-01-10 | 深圳创维－Rgb电子有限公司 | Method for automatically backing up version library, storage medium and server |
| CN110784499A (en) * | 2018-07-30 | 2020-02-11 | 华为技术有限公司 | Data backup method and terminal equipment |
| CN110941509A (en) * | 2019-11-08 | 2020-03-31 | 北京浪潮数据技术有限公司 | Database backup method, device, equipment and storage medium of cloud platform |
| CN111176889A (en) * | 2019-12-11 | 2020-05-19 | 天翼电子商务有限公司 | Automatic backup recovery device and method |
| CN111209267A (en) * | 2019-12-23 | 2020-05-29 | 中国建设银行股份有限公司 | Information providing method, system, device and storage medium |
| CN111611108A (en) * | 2020-05-21 | 2020-09-01 | 云和恩墨(北京)信息技术有限公司 | Method and device for restoring virtual database |
| US11320978B2 (en) | 2018-12-20 | 2022-05-03 | Nutanix, Inc. | User interface for database management services |
| USD956776S1 (en) | 2018-12-14 | 2022-07-05 | Nutanix, Inc. | Display screen or portion thereof with a user interface for a database time-machine |
| US11604762B2 (en) | 2018-12-27 | 2023-03-14 | Nutanix, Inc. | System and method for provisioning databases in a hyperconverged infrastructure system |
| US11604806B2 (en) | 2020-12-28 | 2023-03-14 | Nutanix, Inc. | System and method for highly available database service |
| US11604705B2 (en) | 2020-08-14 | 2023-03-14 | Nutanix, Inc. | System and method for cloning as SQL server AG databases in a hyperconverged system |
| US11640340B2 (en) | 2020-10-20 | 2023-05-02 | Nutanix, Inc. | System and method for backing up highly available source databases in a hyperconverged system |
| US11803368B2 (en) | 2021-10-01 | 2023-10-31 | Nutanix, Inc. | Network learning to control delivery of updates |
| US11816066B2 (en) | 2018-12-27 | 2023-11-14 | Nutanix, Inc. | System and method for protecting databases in a hyperconverged infrastructure system |
| US11892918B2 (en) | 2021-03-22 | 2024-02-06 | Nutanix, Inc. | System and method for availability group database patching |
| WO2024027314A1 (en) * | 2022-07-30 | 2024-02-08 | 超聚变数字技术有限公司 | Backup data recovery method and computing device |
| US11907167B2 (en) | 2020-08-28 | 2024-02-20 | Nutanix, Inc. | Multi-cluster database management services |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1659522A (en) * | 2002-04-19 | 2005-08-24 | 电脑联合想象公司 | Method and system for disaster recovery |
| CN101067818A (en) * | 2007-06-06 | 2007-11-07 | 中国工商银行股份有限公司 | Data incremental backup and recovery method applied to data bank |
| US8260750B1 (en) * | 2009-03-16 | 2012-09-04 | Quest Software, Inc. | Intelligent backup escalation system |
| CN103118011A (en) * | 2013-01-12 | 2013-05-22 | 合肥华云通信技术有限公司 | Method for protecting customer data in multi-tenant environment |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
-
2014
- 2014-09-30 CN CN201410523108.9A patent/CN105446828B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1659522A (en) * | 2002-04-19 | 2005-08-24 | 电脑联合想象公司 | Method and system for disaster recovery |
| CN101067818A (en) * | 2007-06-06 | 2007-11-07 | 中国工商银行股份有限公司 | Data incremental backup and recovery method applied to data bank |
| US8260750B1 (en) * | 2009-03-16 | 2012-09-04 | Quest Software, Inc. | Intelligent backup escalation system |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
| CN103118011A (en) * | 2013-01-12 | 2013-05-22 | 合肥华云通信技术有限公司 | Method for protecting customer data in multi-tenant environment |
Cited By (39)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105955845A (en) * | 2016-04-26 | 2016-09-21 | 浪潮电子信息产业股份有限公司 | Data recovery method and device |
| US10956374B2 (en) | 2016-06-15 | 2021-03-23 | Tencent Technology (Shenzhen) Company Limited | Data recovery method, apparatus, and system |
| WO2017215432A1 (en) * | 2016-06-15 | 2017-12-21 | 腾讯科技（深圳）有限公司 | Data retracement method, device and system |
| CN106201780A (en) * | 2016-07-08 | 2016-12-07 | 浪潮通用软件有限公司 | A kind of historical data method of reducing |
| CN106776120A (en) * | 2016-11-24 | 2017-05-31 | 珠海市魅族科技有限公司 | The method and device of data recovery |
| CN106648980A (en) * | 2016-12-12 | 2017-05-10 | 北京雷石天地电子技术有限公司 | Backup and recovery method and backup and recovery device for high-availability server databases in offline places |
| CN108241555A (en) * | 2016-12-26 | 2018-07-03 | 阿里巴巴集团控股有限公司 | A kind of backup of distributed data base, restoration methods, device and server |
| CN108241555B (en) * | 2016-12-26 | 2022-03-01 | 阿里巴巴集团控股有限公司 | Backup and recovery method and device of distributed database and server |
| CN108511035A (en) * | 2017-02-23 | 2018-09-07 | 仁智(苏州)医学研究有限公司 | A kind of data managing method and device of hospital information system |
| CN107229540A (en) * | 2017-06-06 | 2017-10-03 | 贵州易鲸捷信息技术有限公司 | A kind of database restoring method and system based on time point |
| CN107515801A (en) * | 2017-09-13 | 2017-12-26 | 绿金在线电子商务有限公司 | A kind of data self-repairing method based on relevant database |
| CN108156264A (en) * | 2018-03-06 | 2018-06-12 | 爱普（福建）科技有限公司 | A kind of method of data synchronization towards dual-computer redundancy |
| CN108156264B (en) * | 2018-03-06 | 2021-01-26 | 爱普（福建）科技有限公司 | Data synchronization method oriented to dual-computer redundancy |
| CN110784499A (en) * | 2018-07-30 | 2020-02-11 | 华为技术有限公司 | Data backup method and terminal equipment |
| CN110784499B (en) * | 2018-07-30 | 2021-08-20 | 华为技术有限公司 | Data backup method and terminal equipment |
| CN109101369A (en) * | 2018-08-21 | 2018-12-28 | 郑州云海信息技术有限公司 | A kind of sustainable protection method, system and device of business host data |
| CN109408283A (en) * | 2018-09-04 | 2019-03-01 | 深圳市宝德计算机系统有限公司 | A kind of method of server data protection, equipment and storage medium |
| USD956776S1 (en) | 2018-12-14 | 2022-07-05 | Nutanix, Inc. | Display screen or portion thereof with a user interface for a database time-machine |
| US11907517B2 (en) | 2018-12-20 | 2024-02-20 | Nutanix, Inc. | User interface for database management services |
| US11320978B2 (en) | 2018-12-20 | 2022-05-03 | Nutanix, Inc. | User interface for database management services |
| US11860818B2 (en) | 2018-12-27 | 2024-01-02 | Nutanix, Inc. | System and method for provisioning databases in a hyperconverged infrastructure system |
| US11604762B2 (en) | 2018-12-27 | 2023-03-14 | Nutanix, Inc. | System and method for provisioning databases in a hyperconverged infrastructure system |
| US11816066B2 (en) | 2018-12-27 | 2023-11-14 | Nutanix, Inc. | System and method for protecting databases in a hyperconverged infrastructure system |
| CN110263095B (en) * | 2019-05-31 | 2021-10-01 | 众安在线财产保险股份有限公司 | Data backup and recovery method and device, computer equipment and storage medium |
| CN110263095A (en) * | 2019-05-31 | 2019-09-20 | 众安在线财产保险股份有限公司 | Backup and recovery method, apparatus, computer equipment and storage medium |
| CN110673985A (en) * | 2019-09-20 | 2020-01-10 | 深圳创维－Rgb电子有限公司 | Method for automatically backing up version library, storage medium and server |
| CN110673985B (en) * | 2019-09-20 | 2023-12-26 | 深圳创维－Rgb电子有限公司 | Method for automatically backing up version library, storage medium and server |
| CN110941509A (en) * | 2019-11-08 | 2020-03-31 | 北京浪潮数据技术有限公司 | Database backup method, device, equipment and storage medium of cloud platform |
| CN111176889A (en) * | 2019-12-11 | 2020-05-19 | 天翼电子商务有限公司 | Automatic backup recovery device and method |
| CN111209267A (en) * | 2019-12-23 | 2020-05-29 | 中国建设银行股份有限公司 | Information providing method, system, device and storage medium |
| CN111209267B (en) * | 2019-12-23 | 2024-01-30 | 中国建设银行股份有限公司 | Information providing method, system, device and storage medium |
| CN111611108A (en) * | 2020-05-21 | 2020-09-01 | 云和恩墨(北京)信息技术有限公司 | Method and device for restoring virtual database |
| US11604705B2 (en) | 2020-08-14 | 2023-03-14 | Nutanix, Inc. | System and method for cloning as SQL server AG databases in a hyperconverged system |
| US11907167B2 (en) | 2020-08-28 | 2024-02-20 | Nutanix, Inc. | Multi-cluster database management services |
| US11640340B2 (en) | 2020-10-20 | 2023-05-02 | Nutanix, Inc. | System and method for backing up highly available source databases in a hyperconverged system |
| US11604806B2 (en) | 2020-12-28 | 2023-03-14 | Nutanix, Inc. | System and method for highly available database service |
| US11892918B2 (en) | 2021-03-22 | 2024-02-06 | Nutanix, Inc. | System and method for availability group database patching |
| US11803368B2 (en) | 2021-10-01 | 2023-10-31 | Nutanix, Inc. | Network learning to control delivery of updates |
| WO2024027314A1 (en) * | 2022-07-30 | 2024-02-08 | 超聚变数字技术有限公司 | Backup data recovery method and computing device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105446828B (en) | 2019-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105446828A (en) | Database backup and recovery method, apparatus and system | |
| CN106407356B (en) | Data backup method and device | |
| CN108376109B (en) | Apparatus and method for copying volume of source array to target array, storage medium | |
| CN103853837B (en) | Oracle does not stop the table level back-up restoring method of Production database automatically | |
| CN105550062B (en) | The data reflow method restored based on continuous data protection and time point browsing | |
| US10162714B2 (en) | Methods and systems for restoring data containers in a storage system | |
| JP5646639B2 (en) | Backup using metadata virtual hard drive and differential virtual hard drive | |
| CN102891849B (en) | Service data synchronization method, data recovery method, data recovery device and network device | |
| WO2018098972A1 (en) | Log recovery method, storage device and storage node | |
| CN106021016A (en) | Virtual point in time access between snapshots | |
| US8578203B2 (en) | Providing a backup service from a remote backup data center to a computer through a network | |
| CN103678036B (en) | A kind of backup method found based on virtual machine operation information data | |
| CN105302667A (en) | Cluster architecture based high-reliability data backup and recovery method | |
| CN105593829A (en) | Excluding file system objects from raw image backups | |
| CN102411524A (en) | Snapshot volume data copying method | |
| CN104461773A (en) | Backup deduplication method of virtual machine | |
| CN104750755A (en) | Method and system for recovering data after switching between main database and standby database | |
| CN107533495A (en) | Technology for data backup and resume | |
| CN110825546A (en) | Recovery method, system and equipment terminal for high-availability database cluster | |
| CN105022680A (en) | Data backup method and device | |
| CN109739691A (en) | DB Backup and restoration methods, device, terminal device and storage medium | |
| US20160026536A1 (en) | Recovery path selection during database restore | |
| CN106502830B (en) | A kind of method for restoring system backup based on Btrfs file system | |
| CN106294013B (en) | A kind of different data disaster tolerance method and systems backed up between domain | |
| CN104978279A (en) | Continuous data protection method based on data block |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |