CN1614566A - Back-up restoring method for user database - Google Patents
Back-up restoring method for user database Download PDFInfo
- Publication number
- CN1614566A CN1614566A CN 200410009905 CN200410009905A CN1614566A CN 1614566 A CN1614566 A CN 1614566A CN 200410009905 CN200410009905 CN 200410009905 CN 200410009905 A CN200410009905 A CN 200410009905A CN 1614566 A CN1614566 A CN 1614566A
- Authority
- CN
- China
- Prior art keywords
- database
- backup
- data base
- customer data
- restoring method
- 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
A method for restoring back-up of user's databank includes setting up spare databank of the user and the timing task to back up user's data on main used databank to local harddisc in assigned time or at lowload period of the system, receiving user's data in main used databank to spare databank, using the spare one to substitute the main used one at time when the main used can not be used because of the fault.
Description
Technical field
The present invention relates to field of mobile communication, refer more particularly to the back-up restoring method of mobile subscriber database.
Background technology
Customer data base belongs to a kind of equipment of core in entire switching network network system, subscriber database stores user's authentication information, basic CAMEL-Subscription-Information and supplementary service information, the security of customer data base, stability and reliability will directly have influence on security, stability and the reliability of entire switching network network system.
In order to strengthen the security reliability of customer data base, each manufacturer has taked various methods.The general mode of all taking two-shipper to add the magnetic battle array makes up the user data village, often used in village names platform of core network, is about to difference installation database example on two minicomputers, and database is created on the magnetic battle array.Have only a database instance on the machine to start under the normal condition, and another is in the adapter state always, if because faults such as network failure, minicomputer, system can realize automaticallying switch under the control of two-shipper management software, the two-shipper management software starts the database instance on the other minicomputer automatically, can not cause the interruption of system like this.If but the database on the magnetic battle array damages, even minicomputer is working properly, the delay situation of machine of total system can take place also.This just requires us to provide a kind of more efficiently method to be avoided the generation of this fault, and system failure time is tapered to minimum, thereby provides more safe and reliable service for the user.
Database Backup and recovery are unavoidable problem all in any one database application system.In any case, safety of data and real-time are to use one of target of pursuing forever.How reasonably arranging back-up plan also is a standard of database application quality.
In order further to strengthen the reliability of customer data base, the solution below having proposed.
Summary of the invention
Technical matters to be solved by this invention is to provide a kind of protection mechanism for exchange side core net customer data base; use this mechanism can improve the reliability of system greatly; system failure time is shortened to minimum, can also when the system failure takes place, will significantly reduce loss of user data and inconsistent.
Main method is applied under the two-shipper magnetic matrix ring border, on local hard drive, create a standby database, the user data that regularly will lead with database every day returns on the standby database, in case main with the database damage, just use standby database to take over main work with database.
Specifically, the present invention proposes a kind of back-up restoring method of customer data base, is used for making up under the two-shipper mode mobile subscriber database backup Restoration Mechanism, and this method comprises the steps:
(1) on first minicomputer (main frame) and second minicomputer (guest machine), creates mobile subscriber's standby database respectively;
(2) timed task is set, will leads the user data backup of usefulness database automatically to the local hard drive of main frame and the local hard drive of guest machine in the time of appointment;
(3) reduction is main with the user data in the database in standby database;
(4) when fault causes the master to use database unavailable, enable the standby database of main frame or the standby database of guest machine and substitute the main database of using.
User data backup comprises that to local hard drive the master who preserves a designated period uses database backup file in the described step (2).
The master of described designated period has nothing in common with each other with database backup file, and filename has certain rules.
Reduction is main in the described step (3) comprises that with the user data in the database user data library file that backup is come out by standby customer data base reduction script returns in the standby database.
User data backup comprises to local hard drive and leaving under the assigned catalogue in the described step (2).
Reduction is main in the described step (3) comprises the file of getting appointment under the designated directory with the user data in the database, returns in the standby database then.
Reduction is main in the described step (3) comprises the startup standby database with the user data in the database, carries out the data importing operation then, and operation to be imported is closed standby database after finishing.
Described step (2) comprises that also automatic copy portion is in tape.
Described step (2) also comprises carries out log record to whole backup, rejuvenation.
Described backup recovers to comprise that automated back-up recovers and manually backs up and recover.
Technique effect of the present invention is, has guaranteed main consistance with database and preliminary data database data basically, has significantly reduced the work of maintenance personnel amount, can guarantee professional continuity, and traffic affecting does not normally carry out basically.
Description of drawings
Fig. 1 is a synoptic diagram of the present invention.
Embodiment
Referring to Fig. 1, synoptic diagram of the present invention, wherein thick arrow has marked the backup rejuvenation of data.Among Fig. 1, the database master that first minicomputer 1 used for work uses server, database leaves on the magnetic battle array 2, during its operate as normal, the memory management functions of database db is provided for the user, on minicomputer 1, create a standby database db_bak4, its structure is the same with the master with database db, can with the main Database Backup document storage of using in local hard drive 4 and tape 3, utilize the backup file that produces that data are returned among the standby database dbbak4 of local hard drive 4 simultaneously on the minicomputer like this.Second minicomputer 5 is not the main database server of using, but can have access on the magnetic battle array 2 the main database of using, on second minicomputer, create a standby database dbbak6 so too, its structure is the same with the master with database db, can with the main Database Backup document storage of using in local hard drive 6 and tape 7, utilize the backup file that produces that data are returned among the standby database dbbak6 simultaneously on the minicomputer like this.
Technical scheme of the present invention is specific as follows:
1. on two minicomputer local hard drives, all created a standby customer data base.The main function of standby database is deposited user data.
2. on two minicomputers, timed task is set respectively, utilize timed task, system every day will be led user data backup with database to local hard drive 4 in the time of appointment, and reduction is main with the user data in the database once in the standby database of local hard drive 4 then.The standby database of local hard drive 6 does not start at ordinary times, just starts standby database when system is recovered, carries out the data importing operation then, and operation to be imported is closed standby database after finishing.Open the consumption that increases system resource with regard to not causing for a long time because of standby database like this.
For example first minicomputer, 1 backup in morning, Backup Data leaves under the assigned catalogue, backup file name such as db1.dmp; 1: 30, get the file of appointment under the designated directory, return in the standby database then; 2 of second minicomputer mornings begin backup; 2: 30 begin data are returned in the local standby database.Under backuping to assigned catalogue, in the specified file, file in the tape simultaneously.In whole backup rejuvenation, log record is arranged all.
Every day when system loading is light with the master of system with the user data backup of database to local hard drive, and then the user file that backup is come out by standby customer data base reduction script returns in the standby database.So just guaranteed main consistance basically with database and preliminary data database data.
4. preserve the main of a designated period and use database backup file on local hard drive, the backup file in each cycle all has nothing in common with each other, but filename all has certain rules.Standby system timing automatic every day backs up out the master and uses database backup file, utilizes the regularity of filename, covers the backup file that last one-period generates on the same day.Do like this and just significantly reduced the work of maintenance personnel amount.
For example: the naming rule of automated back-up filename is db+X.dmp (X is between 0～6)
Db0.dmp represents the file that last time, Sunday, automated back-up was generated
Db1.dmp represents the file that last time, Monday, automated back-up was generated
Db2.dmp represents the file that last time, Tuesday, automated back-up was generated
Db3.dmp represents the file that last time, Wednesday, automated back-up was generated
Db4.dmp represents the file that last time, Thursday, automated back-up was generated
Db5.dmp represents the file that last time, Friday, automated back-up was generated
Db6.dmp represents the file that last time, Saturday, automated back-up was generated
Automatically the backup file db1.dmp that generate this Monday will cover the file db1.dmp that generated last Monday.
5. the file that backs up out on being saved in local hard drive in, automatically copy is a in tape.
6. when the master on the magnetic battle array delays machine with database after, perhaps when disaster takes place, mainly become when unavailable with database, can pass through simple configuration, enable standby database and substitute to lead and use database.Can guarantee professional continuity like this, traffic affecting does not normally carry out basically.If can also work by first minicomputer with database is unavailable for the master of first minicomputer, can substitute the main database of using with the standby database of first minicomputer; If first minicomputer can not be worked, the standby database of first minicomputer can not use so, just substitutes first minicomputer work with second minicomputer, and the standby database of second minicomputer is as the main database of using.
7. whole backup rejuvenation all has log record
8. the backup Restoration Mechanism of total system not only comprises main automated back-up recovery with database, also allows the user to back up by manual mode and recovers the main database of using, and backup recovers standby database.
The present invention has carried out special description to a kind of method of the disclosed mobile core network data base backup recovery that relates to, those skilled in the art can understand, under the situation that does not depart from scope and spirit of the present invention, can carry out all conspicuous modification of form and details to it.Therefore, embodiment described above is illustrative and not restrictive, and under the situation that does not break away from the spirit and scope of the present invention, all variations and modification are all within the scope of the present invention.
Claims (10)
1. the back-up restoring method of a customer data base is used for making up mobile subscriber database backup Restoration Mechanism under the two-shipper mode, and this method comprises the steps:
(1) on two minicomputers, creates mobile subscriber's standby database respectively;
(2) timed task is set, will leads the user data backup of usefulness database automatically to the local hard drive of main frame and the local hard drive of guest machine in the time of appointment;
(3) reduction is main with the user data in the database in standby database;
(4) when fault causes the master to use database unavailable, enable the standby database of first minicomputer or the standby database of second minicomputer and substitute the main database of using.
2. the back-up restoring method of customer data base as claimed in claim 1 is characterized in that, user data backup comprises that to local hard drive the master who preserves a designated period uses database backup file in the described step (2).
3. the back-up restoring method of customer data base as claimed in claim 2 is characterized in that, the master of described designated period has nothing in common with each other with database backup file, and filename has certain rules.
4. the back-up restoring method of customer data base as claimed in claim 3, it is characterized in that reduction is main in the described step (3) comprises that with the user data in the database user data library file that backup is come out by standby customer data base reduction script returns in the standby database.
5. the back-up restoring method of customer data base as claimed in claim 1 is characterized in that, user data backup comprises under the assigned catalogue that leaves local hard drive in to local hard drive in the described step (2).
6. the back-up restoring method of customer data base as claimed in claim 5 is characterized in that, reduction is main in the described step (3) comprises the file of getting appointment under the designated directory with the user data in the database, returns in the standby database then.
7. the back-up restoring method of customer data base as claimed in claim 1, it is characterized in that reduction is main in the described step (3) comprises the startup standby database with the user data in the database, carries out the data importing operation then, operation to be imported is closed standby database after finishing.
8. the back-up restoring method of customer data base as claimed in claim 1 is characterized in that, described step (2) comprises that also automatic copy portion is in tape.
9. the back-up restoring method of customer data base as claimed in claim 1 is characterized in that, described step (2) also comprises carries out log record to whole backup, rejuvenation.
10. the back-up restoring method of customer data base as claimed in claim 1 is characterized in that, described backup recovers to comprise that automated back-up recovers and manually backs up and recover.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100099051A CN1329829C (en) | 2004-11-29 | 2004-11-29 | Back-up restoring method for user database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100099051A CN1329829C (en) | 2004-11-29 | 2004-11-29 | Back-up restoring method for user database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1614566A true CN1614566A (en) | 2005-05-11 |
| CN1329829C CN1329829C (en) | 2007-08-01 |
Family
ID=34763127
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100099051A Expired - Fee Related CN1329829C (en) | 2004-11-29 | 2004-11-29 | Back-up restoring method for user database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1329829C (en) |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100357901C (en) * | 2005-12-21 | 2007-12-26 | 华为技术有限公司 | Method for verifying data between main device and back-up device |
| CN100524237C (en) * | 2007-11-02 | 2009-08-05 | 西安三茗科技有限责任公司 | Computer hard disk data continuous time point storage and recovery method |
| CN101331458B (en) * | 2006-01-03 | 2011-10-05 | 伊姆西公司 | Continuous backup |
| CN101667181B (en) * | 2008-09-05 | 2011-12-21 | 华为技术有限公司 | Method, device and system for data disaster tolerance |
| CN1972360B (en) * | 2005-11-21 | 2012-01-04 | 夏普株式会社 | Data processing device |
| WO2012009913A1 (en) * | 2010-07-20 | 2012-01-26 | 中兴通讯股份有限公司 | Database backing-up and recovering method and device |
| CN102456066A (en) * | 2011-07-13 | 2012-05-16 | 北京壹人壹本信息科技有限公司 | Android-system-based device and data storage method |
| CN102591863A (en) * | 2011-01-06 | 2012-07-18 | 上海银晨智能识别科技有限公司 | Data processing method and device in comparison system |
| WO2012101540A1 (en) * | 2011-01-27 | 2012-08-02 | International Business Machines Corporation | Application recovery in file system |
| CN102637133A (en) * | 2012-03-12 | 2012-08-15 | 成都林海电子有限责任公司 | Method for automatically updating terminating machines of (L, S) waveband satellite mobile communication systems |
| CN102841823A (en) * | 2011-06-23 | 2012-12-26 | 鸿富锦精密工业（深圳）有限公司 | Data backup system and method |
| CN103488721A (en) * | 2013-09-12 | 2014-01-01 | 京信通信系统（中国）有限公司 | Database bisynchronous method and system for master and slave boards |
| CN103853837A (en) * | 2014-03-17 | 2014-06-11 | 上海爱数软件有限公司 | Oracle table-level backup and recovering method for full-automatic continuously producing databases |
| CN104035833A (en) * | 2013-03-07 | 2014-09-10 | 联发科技股份有限公司 | Method And System For Verifying Machine Readable Code Integrity |
| CN104516794A (en) * | 2014-12-12 | 2015-04-15 | 国家电网公司 | Database document backup method, device and system |
| CN105740101A (en) * | 2016-01-29 | 2016-07-06 | 青岛海尔智能家电科技有限公司 | Automatic backup and automatic restoration method and apparatus for MySQL database |
| CN106886555A (en) * | 2016-12-27 | 2017-06-23 | 苏州春禄电子科技有限公司 | A kind of anti-loss of data based on block chain technology and the data-storage system for damaging |
| CN107526654A (en) * | 2017-08-05 | 2017-12-29 | 中山大学 | A kind of oracle database backup and reduction system based on webpage |
| CN108628705A (en) * | 2018-04-10 | 2018-10-09 | 京信通信系统（中国）有限公司 | Database restoring method, device, computer equipment and storage medium |
| WO2021237431A1 (en) * | 2020-05-26 | 2021-12-02 | 深圳市欢太科技有限公司 | Data processing method and apparatus, processing device, and data storage system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FI105870B (en) * | 1997-03-21 | 2000-10-13 | Nokia Networks Oy | A method for preventing inconsistency between data in the master center and the backup center |
| US7043504B1 (en) * | 2000-04-10 | 2006-05-09 | International Business Machines Corporation | System and method for parallel primary and secondary backup reading in recovery of multiple shared database data sets |
| CN1109416C (en) * | 2000-04-25 | 2003-05-21 | 华为技术有限公司 | Method and equipment for swapping active with standby switches |
| CN100442253C (en) * | 2001-02-22 | 2008-12-10 | 北京北信源自动化技术有限公司 | Hot mirror image base driven hot back-up method of server data |
-
2004
- 2004-11-29 CN CNB2004100099051A patent/CN1329829C/en not_active Expired - Fee Related
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1972360B (en) * | 2005-11-21 | 2012-01-04 | 夏普株式会社 | Data processing device |
| CN100357901C (en) * | 2005-12-21 | 2007-12-26 | 华为技术有限公司 | Method for verifying data between main device and back-up device |
| CN101331458B (en) * | 2006-01-03 | 2011-10-05 | 伊姆西公司 | Continuous backup |
| CN100524237C (en) * | 2007-11-02 | 2009-08-05 | 西安三茗科技有限责任公司 | Computer hard disk data continuous time point storage and recovery method |
| CN101667181B (en) * | 2008-09-05 | 2011-12-21 | 华为技术有限公司 | Method, device and system for data disaster tolerance |
| WO2012009913A1 (en) * | 2010-07-20 | 2012-01-26 | 中兴通讯股份有限公司 | Database backing-up and recovering method and device |
| CN102591863A (en) * | 2011-01-06 | 2012-07-18 | 上海银晨智能识别科技有限公司 | Data processing method and device in comparison system |
| GB2501659A (en) * | 2011-01-27 | 2013-10-30 | Ibm | Application recovery in file system |
| WO2012101540A1 (en) * | 2011-01-27 | 2012-08-02 | International Business Machines Corporation | Application recovery in file system |
| GB2501659B (en) * | 2011-01-27 | 2017-12-27 | Ibm | Application recovery in file system |
| CN103329105A (en) * | 2011-01-27 | 2013-09-25 | 国际商业机器公司 | Application recovery in file system |
| US8560884B2 (en) | 2011-01-27 | 2013-10-15 | International Business Machines Corporation | Application recovery in a file system |
| US8566636B2 (en) | 2011-01-27 | 2013-10-22 | International Business Machines Corporation | Application recovery in a file system |
| CN103329105B (en) * | 2011-01-27 | 2016-01-20 | 国际商业机器公司 | Application recovery in file system |
| CN102841823A (en) * | 2011-06-23 | 2012-12-26 | 鸿富锦精密工业（深圳）有限公司 | Data backup system and method |
| CN102456066A (en) * | 2011-07-13 | 2012-05-16 | 北京壹人壹本信息科技有限公司 | Android-system-based device and data storage method |
| CN102637133B (en) * | 2012-03-12 | 2015-06-17 | 成都林海电子有限责任公司 | Method for automatically updating terminating machines of (L, S) waveband satellite mobile communication systems |
| CN102637133A (en) * | 2012-03-12 | 2012-08-15 | 成都林海电子有限责任公司 | Method for automatically updating terminating machines of (L, S) waveband satellite mobile communication systems |
| CN104035833A (en) * | 2013-03-07 | 2014-09-10 | 联发科技股份有限公司 | Method And System For Verifying Machine Readable Code Integrity |
| CN103488721A (en) * | 2013-09-12 | 2014-01-01 | 京信通信系统（中国）有限公司 | Database bisynchronous method and system for master and slave boards |
| CN103488721B (en) * | 2013-09-12 | 2017-01-18 | 京信通信系统（中国）有限公司 | Database bisynchronous method and system for master and slave boards |
| CN103853837A (en) * | 2014-03-17 | 2014-06-11 | 上海爱数软件有限公司 | Oracle table-level backup and recovering method for full-automatic continuously producing databases |
| CN104516794A (en) * | 2014-12-12 | 2015-04-15 | 国家电网公司 | Database document backup method, device and system |
| CN104516794B (en) * | 2014-12-12 | 2017-11-14 | 国家电网公司 | Backup method, the apparatus and system of database file |
| CN105740101A (en) * | 2016-01-29 | 2016-07-06 | 青岛海尔智能家电科技有限公司 | Automatic backup and automatic restoration method and apparatus for MySQL database |
| CN106886555A (en) * | 2016-12-27 | 2017-06-23 | 苏州春禄电子科技有限公司 | A kind of anti-loss of data based on block chain technology and the data-storage system for damaging |
| CN107526654A (en) * | 2017-08-05 | 2017-12-29 | 中山大学 | A kind of oracle database backup and reduction system based on webpage |
| CN108628705A (en) * | 2018-04-10 | 2018-10-09 | 京信通信系统（中国）有限公司 | Database restoring method, device, computer equipment and storage medium |
| CN108628705B (en) * | 2018-04-10 | 2021-01-15 | 京信通信系统（中国）有限公司 | Database recovery method and device, computer equipment and storage medium |
| WO2021237431A1 (en) * | 2020-05-26 | 2021-12-02 | 深圳市欢太科技有限公司 | Data processing method and apparatus, processing device, and data storage system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1329829C (en) | 2007-08-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1614566A (en) | Back-up restoring method for user database | |
| CN102681917B (en) | A kind of operating system and restorative procedure thereof | |
| CN106843750B (en) | Distributed storage system | |
| US7174547B2 (en) | Method for updating and restoring operating software in an active region of a network element | |
| CN103853837B (en) | Oracle does not stop the table level back-up restoring method of Production database automatically | |
| US20060235905A1 (en) | Method and system for preserving real-time access to a system in case of a disaster | |
| US7774315B1 (en) | Backup system | |
| CN104765652B (en) | A kind of data backup and data reconstruction method and device | |
| CN1106986A (en) | Restoration of a home location register in a mobile radio system | |
| CN103562904A (en) | Replaying jobs at a secondary location of a service | |
| CN101739313A (en) | Method for protecting and restoring continuous data | |
| CN101996094A (en) | Method and system for managing distributed resources | |
| CN110673982A (en) | Shared mysql database backup and recovery method and device | |
| CN111611108A (en) | Method and device for restoring virtual database | |
| CN112631831A (en) | Bare computer recovery method and system of service system | |
| CN110647425A (en) | Database recovery method and device | |
| CN110716828B (en) | Database real-time backup method | |
| CN109739687A (en) | A kind of snapshot management system and method based on Elasticsearch | |
| CN105988885A (en) | Compensation rollback-based operation system fault self-recovery method | |
| CN110688259B (en) | Private cloud backup recovery system and backup recovery method thereof | |
| Heegaard et al. | Survivability as a generalization of recovery | |
| CN111581013A (en) | System information backup and reconstruction method based on metadata and shadow files | |
| CN1505315A (en) | A data disaster recovery solution method producing no interlinked data reproduction | |
| WO2000019337A1 (en) | Backing up microsoft clustered database | |
| CN115408200A (en) | Data backup method and device for multiple storage engines, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: JINJIANG HIGH-TECH DEVELOPMENT OFFICE Free format text: FORMER OWNER: ZTE CORPORATION Effective date: 20131112 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518057 SHENZHEN, GUANGDONG PROVINCE TO: 362200 QUANZHOU, FUJIAN PROVINCE |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20131112 Address after: Jinjiang City, Fujian province 362200 Chongde road Quanzhou City No. 283 friends Jade Technology Building Patentee after: Jinjiang high and new technology development office Address before: 518057 Nanshan District, Guangdong high tech Industrial Park, science and Technology Industrial Park, ZTE building, block A, layer 6, layer Patentee before: ZTE Corporation |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20070801 Termination date: 20161129 |