CN103853837B - Oracle does not stop the table level back-up restoring method of Production database automatically - Google Patents
Oracle does not stop the table level back-up restoring method of Production database automatically Download PDFInfo
- Publication number
- CN103853837B CN103853837B CN201410097448.XA CN201410097448A CN103853837B CN 103853837 B CN103853837 B CN 103853837B CN 201410097448 A CN201410097448 A CN 201410097448A CN 103853837 B CN103853837 B CN 103853837B
- Authority
- CN
- China
- Prior art keywords
- backup
- data
- oracle
- client
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Do not stop the table level back-up restoring method of Production database automatically the present invention relates to a kind of Oracle, comprise the following steps：1) client backups to Oracle data by RMAN sbt physical backups modes the backup server of distal end；2) when needing to carry out table level recovery, client is obtained from backup server recovers data.Compared with prior art, the present invention can reach substantially reduces user's maintenance difficulties without manually operation oracle database, and need not stop Production database making production business not interrupt, backup cycle random time point can be returned to the purpose reported as precisely as possible for retrieving loss of data.
Description
Technical field
The present invention relates to a kind of database recovery technology, Production database is not stopped automatically more particularly, to a kind of Oracle
Table level back-up restoring method.
Background technology
The global relationship type numbers in 2012 announced according to most authoritative IT researchs with Gartner companies of counselor company
According to storehouse market survey report, calculated with software total income, Oracle continues position in occupation of first, and income part with 48.3%
Volume is more than the summation of four immediate rivals.It can thus be seen that as database king Oracle the whole world user
It is most.
Oracle data are deposited in the storage device of computer, and the overwhelming majority is stored in hard disk, and minority is stored in
In tape.Because the physical characteristic of computer in itself is determined, the data being stored thereon can be because the impact of various external causes
And it is unavailable.The physical damage and service life of such as storage device, electric power are interrupted suddenly, fire, earthquake etc. may all cause
The loss of data of storage on computers, so that the production service disconnection of Oracle user, loss can not be estimated.Lost in face of data
Mistake causes the challenge of service disconnection, and suitable and efficient Oracle Backup and Restore technologies are essential.In order to ensure
Oracle user data is continuously available, and best bet is exactly the storage of data multimachine, grasps when appearance production service disconnection or by mistake
Work cause table data not to when, it is recovered at once continue produce.
Oracle does physical backup recovery after 8i versions there is provided RMAN (Recovery Manager) instrument.RMAN
Data file, archive log file and the control file that can be constituted to oracle database do monolithic backup, the granularity of recovery
File-level can only be arrived.In order to more accurate restorative, recovers can be directed to when progress reparation oracle database extensive
Archive log after multiple backup set does rolling back action, reaches and returns to the desired database situation of user, subtracts as much as possible
Few loss of data and damage.But storage facility located at processing plant is made of this reset mode former machine recover to need to make the corresponding data file of table from
Line, needs to make whole data if table recovers one or more table data when the system table space such as system, sysaux
Storehouse example is restarted, and the business that like this will result in user is interrupted or partial interruption completely；And recovery granularity can only arrive table pair
This rank of the data file answered, it is impossible to required table data are accurately extracted and recovered.
Recover table data can not accurately be extracted into the defect recovered to solve above-mentioned physical backup, then can use
The mode that exp/imp backup logics recover.But backup logic recovers similar to physical backup recovery, if directly to storage facility located at processing plant
Recovery operation is carried out, is also to need to make the corresponding data file of table offline or even stop database, is also like this to cause
Customer service is interrupted.And backup logic recovers that the incomplete recovery of rollback can not be done for transaction journal, therefore compared to thing
Backup and Restore is managed, it recovers that time point when precision can only arrive Oracle backups.
Oracle is proposed the duplicate targets storage facility located at processing plant in same production server from 9i versions and aided in one
Storehouse.This scheme is directed to the backup set rewind journal of RMAN physical backups, and replicates the master library of random time point before current state
To an auxiliary auxiliary data base, have after duplicate is complete in production server current state storage facility located at processing plant A and
Roll back to the theassistant base B sometime put.But fine-grained one or more table data are arrived enough when user only needs to extract
When, it is impossible to operation system is connected into B, because the data produced without B state to current A condition, and maintain two numbers
According to storehouse, operation is also required to a large amount of CPU and memory source in production server.Therefore it is individually temporary with duplicate replicate datas storehouse
And it is infeasible.
It is traditional standby that summary Oracle physical backups, duplicate replicate datas storehouse and backup logic recover these
The advantage and disadvantage of part recovery scheme, can reach it is full-automatic, do not stop Production database, the table level of high accuracy is recovered to require, only use
A kind of Backup and Restore technology is unable to reach certainly.
The content of the invention
It is an object of the present invention to overcome the above-mentioned drawbacks of the prior art and provide one kind reduction database dimension
Shield difficulty, the Oracle that can return to backup cycle random time point do not stop the table level Backup and Restore side of Production database automatically
Method.
The purpose of the present invention can be achieved through the following technical solutions：
A kind of Oracle does not stop the table level back-up restoring method of Production database automatically, comprises the following steps：
1) client backups to Oracle data by RMAN sbt physical backups modes the backup server of distal end；
2) when needing to carry out table level recovery, client is obtained from backup server recovers data, specific as follows：
201) client is initiated to recover message；
202) manufacturing machine is received after recovery message, generates a standby storehouse；
203) the backup piece information for needing to recover is sent to client by oracle database loading sbt components, sbt components
End；
204) client initiates recovery request by network to backup server；
205) backup server is received after recovery request, is read from backup server data memory module and is recovered data,
And data return client will be recovered by network；
206) client is sent to oracle database by sbt components by data are recovered；
207) oracle database is received after recovery data, by the data recovery into standby storehouse；
208) in data being imported into storage facility located at processing plant from standby storehouse by exp/imp backup logics method；
209) standby storehouse, free system resources are deleted in manufacturing machine..
Described step 208) be specially：
Oracle database starts to open states, by exp backup logics the table data recovered will be needed to export, then will
Export result is recovered to imported into storage facility located at processing plant by imp logics.
Described step 1) be specially：
101) backup server is started；
102) client generation RMAN backup scripts；
103) oracle database loading sbt components；
104) client is from the interface Backup Data in sbt components, and transmits data to distal end by network
Backup server is backed up.
Described step 102) in RMAN backups combined using 0 grade of sbt backup completely and 1 grade of sbt differences incremental backup
Mode.
Compared with prior art, the invention has the advantages that：
1st, Oracle RMAN physical backups, duplicate are replicated and recovers data and exp/imp backup logics recovery phase
With reference to, and backup in remote storage server, when data are misused or lost in user's table, backup week can be returned to
Phase random time point table data.
2nd, the whole recovery process of the present invention is that program is full automatic without excessive manual intervention, greatly reduces user's operation
Trouble and maintenance difficulties.
3rd, whole recovery process of the invention need not stop Production database and restart monitoring server, make production business not
Interrupt, can so meet the recovery table data in the case where not influenceing customer service to run well.
4th, recovery of the invention only needs to recovery system table space and the corresponding user's table space of table.
Brief description of the drawings
Fig. 1 is backup schematic flow sheet of the invention；
Fig. 2 recovers schematic flow sheet for the present invention；
Fig. 3 is that Oracle table levels recover view.
Embodiment
The present invention is described in detail with specific embodiment below in conjunction with the accompanying drawings.The present embodiment is with technical solution of the present invention
Premised on implemented, give detailed embodiment and specific operating process, but protection scope of the present invention is not limited to
Following embodiments.
A kind of Oracle does not stop the table level back-up restoring method of Production database automatically, comprises the following steps：
1) client backups to Oracle data by RMAN sbt physical backups modes the backup server of distal end；
2) when needing to carry out table level recovery, client is obtained from backup server recovers data.
Oracle RMAN physical backups can distribute the local physical disk that disk passages backup to oracle server
In, in order to be able to support third party's backup software manufacturer to backup in remote storage server or tape, Oracle provides a set of official
Square interface incense part manufacturer voluntarily realizes, as distribution sbt (system backup to tape, system backup magnetic in backup script
Band) passage when Oracle can voluntarily call in loading sbt storehouses, the keyword and backup database in Backup and Restore script
Oracle data blocks, are so supplied to third party's backup software manufacturer storage tube by the corresponding interface of data cases recursive call
Reason.
The present invention is because can support " data recovery of random time point in a backup cycle " this utilization to file day
Will rollback characteristic, therefore remote storage server is backuped to by Oracle data, using the physical backup of RMAN sbt modes come
Processing.Recovery is that the data backed up are recovered in the case of the database corruption of user's production and operation, therefore is recovered
Premise be need backup.Oracle physical backup types have 0 grade of backup, 1 grade of difference incremental backup, 1 grade of sigma delta completely
Backup, because being not know when to be likely to cause the specific corrupted data of which block or loss in advance before backup, and works as
When backuping to remote storage server the rubbish that backup failure is now backed up is caused if some such as power-off, network connection disconnect
Rubbish data need to delete, therefore these comprehensive situations consider that we back up+1 grade of whole storehouse sbt difference completely from 0 grade of whole storehouse sbt
Incremental backup, Backup Data includes data file, archive log file and control file.In summary, whole backup procedure is such as
Shown in Fig. 1.
Exemplified by backing up completely, when backup, the steps is performed：
1) backup server program on remote storage server is started, for receiving the backup number that client is sended over
According to.
2) oracle server works as the client backuped, and client-side program is write script and called for RMAN, and RMAN is complete
Backup script is following (so that the database instance under linux environment is orcl as an example)：
Oracle also provides 1 grade of cumulative increment backup and 1 grade of difference incremental backup type, and each self-applying and characteristic are as follows：
1 grade of cumulative increment backup：Since being backup last full backup in data file all changes data block.Relatively
For this type of backup need more BACKUP TIMEs, but recovery time is relatively less.
1 grade of difference incremental backup：It is to be compared with Last Backup (either backup or incremental backup type completely),
Back up the data block changed in all data files.Relative accumulation incremental backup recovers, it is necessary to less BACKUP TIME
Time is longer.Backup is much higher relative to frequency is recovered, therefore we select this increment type, and its backup script is as follows：
3) when RMAN calls backup script above, Oracle can produce an entitled oracle_orcl of backup process
Process loading oracle sbt storehouses below user environment variable $ LD_LIBRARY_PATH paths are installed.Recursive call successively
Sbtinit2 (), sbtbackup (), sbtwrite (), sbtend () interface, by interprocess communication mode by data transfer
Give backup software client-side program.
4) client is from the interface in sbt storehouses to data, while all tables of SQL query backup database example,
And the corresponding user of these tables and table space information, and the backup storage server of distal end is transmitted data to by network and incited somebody to action
The sqlit databases that the information inquired is stored in backup storage server according to certain form (use by storage backup information
) in for user recover browse, complete backup.
The flow of recovery is：When user needs to do table level recovery, one recovery of Client Agent program creation is held
Traveling journey is used to recover.Which data file weight the table that this process is recovered as needed determines to need for the path recovered
Orientation path is, it is necessary to exclude which table space does not recover or not to replicate script to make RMAN duplicate, then restarts
RMAN programs call this script.RMAN is called after this script, and Oracle can produce a recovering process to load sbt
Sbt bank interfaces are called in storehouse, and now Oracle and client are wanted to look for client to recover executive process again by the communication between process
Data, client recovers executive process and looks for backup server to want data, then one-level by client, server network program module
Carry out data duplication recovery to one-level.The overall flow of recovery is as shown in Fig. 2 be described in detail below：
(1) client is initiated to recover message；
(2) client recovery executive process receives recovery message, and a standby storehouse is generated in manufacturing machine and RMAN recovers
Script, and start RMAN be duplicate replicate recovery；
(3) Oracle recovering process loading sbt storehouses；
(4) client is recovered to recover the message of which backup piece the need for executive process receives the transmission of sbt components；
(5) client recovers executive process to client network program module initiation recovery request；
(6) client network program module will recover number by network to the network program module request of backup server
According to；
(7) the network program module of backup server will recover data to the request of backup server data memory module again；
(8) backup server data memory module reads data from storage；
(9) the network program module of backup server receives the data that backup server data memory module is read；
(10) the network program module that client network program module receives backup server by network is sended over
Data；
(11) client recovery executive process receives the data that client network program module has been received by again；
(12) client recovery executive process sends data to sbt components；
(13) sbt components transfer data to Oracle recovering process, and Oracle recovering process restores data to this again
In ground storage；
(14) Oracle backups have been recovered and have had been started up open states, will be needed by exp backup logics
The table data of recovery export to a .dmp file, then this .dmp file is imported into storage facility located at processing plant by the recovery of imp logics,
Complete to recover, and standby storehouse is deleted to disk, CPU and the memory source for discharging manufacturing machine.
The inventive method is illustrated with instantiation below, wherein, step 1,2,3.1 and 3.2 are the methods in the standby storehouse of generation；Step
Rapid 4 be to recover interface to instruct user to operate；5 be to recover script example；6 be that standby storehouse has been recovered table data recovery to storage facility located at processing plant again
Scheme；7 be the resource release that manufacturing machine is done after user finishes the recovery of Oracle table levels.
1) characteristic that Oracle table levels of the present invention are recovered is need not to stop database even without making data file off line, and
And can be with rollback archive log repair data storehouse to any possible time point.Therefore by by the way of the recovery of RMAN physical backups
, it is necessary to create a standby storehouse (theassistant base) to be recovered in the server where original production machine.Standby storehouse is created (with tempdb
Exemplified by), it is necessary to which a pfile Parameter File starts standby storehouse, pfile Parameter Files mainly configure following items parameter：
"*.control_files"：Refer to the control filename in standby storehouse；
"*.db_block_size"：The block size of standby library database is referred to, value can be arranged to consistent with former storehouse；
"*.db_name"：The database instance title in standby storehouse；
"db_unique_name"：The standby assistance data library names that duplicate is replicated；
"db_file_name_convert"：The data file of storage facility located at processing plant is copied into the corresponding data file mesh of theassistant base
Under record, previous path be storage facility located at processing plant path, it is latter be theassistant base path because data file is not necessarily merely placed at a mesh
Record is following, therefore supports multigroup path, it is necessary to which odd number is storage facility located at processing plant path, and even number is theassistant base path；
"log_file_name_convert"：The online journal files of the redo of storage facility located at processing plant are copied into theassistant base corresponding
Under the online logfile directorys of redo, previous path be storage facility located at processing plant path, it is latter be theassistant base path because redo is online
Journal file is not necessarily merely placed at below a catalogue, therefore also supports multigroup path, consistent with last parameter, it is necessary to which odd number is
Storage facility located at processing plant path, even number is theassistant base path.
2) make to communicate normally, it is necessary in tnsnames.ora (without modification between standby storehouse secondary instance and production main frame
Listener.ora the related monitoring informations of standby storehouse secondary instance tempdb) are added.
3.1) need to create standby storehouse secondary instance tempdb cryptogam, addition password is the password text of " oracle "
Part.
If 3.2) it is windows that this, which recovers environment, in addition it is also necessary to create example service to Oracle with oradim programs.
4) select the corresponding table of correspondence user to be recovered in the recovery interface of backup software, given birth to orcl to be recovered
Produce testuserTablel, testuserTable2, testuserTable3 tri- below the testuser user of database
Exemplified by table, as shown in Figure 3.
5) when the recovery of Oracle table levels is carried out, this table related table space (system table space and table are only recovered
Corresponding table space), other table spaces will not recover.It is raw for orcl (exemplified by user name sys, password are admin) by storage facility located at processing plant
In product storehouse in addition to service system table space, also tri- user's table spaces of T01, T02, T03 have three tables
TestuserTablel, testuserTable2, testuserTable3 are present in T03.If now user needs to recover
This three tables, then only need to T01, T02 excluding duplicate replicate datas storehouse again, can so reduce recovery number
According to amount, time, memory space and the network bandwidth are saved, recovers script as follows：
Call recovery to replicate script below and recover data with Oracle and sbt interactions：
[oracle@linux dbs]export ORACLE_SID=tempdb
[oracle@linux dbs]rman target sys/admin@orcl AUXILIARY/@/opt/backup/
restoreTable.rcv
6) data recovery in standby storehouse is complete, behind log-on data storehouse to open, and the RMAN physical restorations in standby storehouse would have been completed,
Storage facility located at processing plant needs the table data recovered to exist in standby storehouse.During data are imported into storage facility located at processing plant by next step from standby storehouse, patrolled with exp/imp
Backup scenario is collected to handle.Table data exp export .dmp files are imported into local disk, then by this .dmp file first
In storage facility located at processing plant.When table data are imported into storage facility located at processing plant, if having a table of the same name or this table in storage facility located at processing plant in itself
It is not deleted, then needs first to fall this table renaming or drop in storage facility located at processing plant and then again recovered.
7) Oracle is carried out after table level recovery, the secondary instance of generation does not have practical function and also taken up interior
Deposit, CPU usage and disk storage space, therefore recovered suggestion standby storehouse cleared up.
Claims (2)
1. a kind of Oracle does not stop the table level back-up restoring method of Production database automatically, it is characterised in that this method will
Oracle RMAN physical backups, duplicate replicates recovery data and exp/imp backup logics recover to be combined, including with
Lower step：
1) client backups to Oracle data by RMAN sbt physical backups modes the backup server of distal end, specifically
For：
101) backup server is started；
102) client generation RMAN backup scripts, wherein, RMAN backups are increased using 0 grade of sbt backups completely and 1 grade of sbt difference
The mode that amount backup is combined；
103) oracle database loading sbt components；
104) client is from the interface Backup Data in sbt components, and transmits data to by network the backup of distal end
Server is backed up；
2) when needing to carry out table level recovery, client is obtained from backup server recovers data, specific as follows：
201) client is initiated to recover message；
202) manufacturing machine is received after recovery message, generates a standby storehouse；
203) the backup piece information for needing to recover is sent to client by oracle database loading sbt components, sbt components；
204) client initiates recovery request by network to backup server；
205) backup server is received after recovery request, is read from backup server data memory module and is recovered data, and led to
Data return client will be recovered by crossing network；
206) client is sent to oracle database by sbt components by data are recovered；
207) oracle database is received after recovery data, by the data recovery into standby storehouse；
208) in data being imported into storage facility located at processing plant from standby storehouse by exp/imp backup logics method；
209) standby storehouse, free system resources are deleted in manufacturing machine.
2. a kind of Oracle according to claim 1 does not stop the table level back-up restoring method of Production database automatically, its
It is characterised by, described step 208) be specially：
Oracle database starts to open states, by exp backup logics the table data recovered will be needed to export, then will export
As a result recover to imported into storage facility located at processing plant by imp logics.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410097448.XA CN103853837B (en) | 2014-03-17 | 2014-03-17 | Oracle does not stop the table level back-up restoring method of Production database automatically |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410097448.XA CN103853837B (en) | 2014-03-17 | 2014-03-17 | Oracle does not stop the table level back-up restoring method of Production database automatically |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103853837A CN103853837A (en) | 2014-06-11 |
| CN103853837B true CN103853837B (en) | 2017-07-28 |
Family
ID=50861492
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410097448.XA Active CN103853837B (en) | 2014-03-17 | 2014-03-17 | Oracle does not stop the table level back-up restoring method of Production database automatically |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103853837B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104239167A (en) * | 2014-09-25 | 2014-12-24 | 珠海市君天电子科技有限公司 | Backup method and backup device for database as well as electronic equipment |
| CN105045680B (en) * | 2015-07-10 | 2018-09-25 | 上海爱数信息技术股份有限公司 | A method of reaching dream database back-up data |
| CN105426269B (en) * | 2015-11-30 | 2018-10-12 | 上海爱数信息技术股份有限公司 | A kind of device and method promoting Oracle backup performances |
| CN105955843B (en) * | 2016-04-21 | 2019-05-28 | 久盈世纪（北京）科技有限公司 | A kind of method and apparatus for database recovery |
| CN106372170B (en) * | 2016-08-30 | 2020-02-14 | 上海爱数信息技术股份有限公司 | Method and system for recovering table in database and server with system |
| CN107179965B (en) * | 2017-04-25 | 2020-05-19 | 北京潘达互娱科技有限公司 | Database recovery method and device |
| CN107256182B (en) * | 2017-05-03 | 2020-09-08 | 上海上讯信息技术股份有限公司 | Method and device for restoring database |
| CN108255906B (en) * | 2017-05-04 | 2020-08-14 | 平安科技（深圳）有限公司 | Data additional recording method and device |
| CN107480221A (en) * | 2017-08-02 | 2017-12-15 | 福建星瑞格软件有限公司 | A kind of method of repair data storehouse table space |
| CN107562575A (en) * | 2017-09-12 | 2018-01-09 | 郑州云海信息技术有限公司 | A kind of method and system of oracle database backup |
| CN109086170A (en) * | 2018-08-15 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of data base backup recovery method and device |
| CN110309128B (en) * | 2019-07-05 | 2020-07-17 | 广东铭太信息科技有限公司 | Oracle backup file automatic importing device, implementation method thereof and method for importing backup file by using device |
| CN110704242B (en) * | 2019-09-24 | 2023-06-13 | 上海爱数信息技术股份有限公司 | Continuous data protection system and method |
| CN112214359A (en) * | 2020-10-30 | 2021-01-12 | 上海爱数信息技术股份有限公司 | Backup and recovery system and method for Oracle database |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6658589B1 (en) * | 1999-12-20 | 2003-12-02 | Emc Corporation | System and method for backup a parallel server data storage system |
| CN1329829C (en) * | 2004-11-29 | 2007-08-01 | 中兴通讯股份有限公司 | Back-up restoring method for user database |
| CN101794246B (en) * | 2010-02-24 | 2013-03-20 | 成都市华为赛门铁克科技有限公司 | Backup storage system, backup system, data backup method and recovery method |
-
2014
- 2014-03-17 CN CN201410097448.XA patent/CN103853837B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN103853837A (en) | 2014-06-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103853837B (en) | Oracle does not stop the table level back-up restoring method of Production database automatically | |
| CN105389230B (en) | A kind of continuous data protection system and method for combination snapping technique | |
| EP2619695B1 (en) | System and method for managing integrity in a distributed database | |
| CN101334797B (en) | Distributed file systems and its data block consistency managing method | |
| CN101739313B (en) | Method for protecting and restoring continuous data | |
| JP5254611B2 (en) | Metadata management for fixed content distributed data storage | |
| WO2016180160A1 (en) | Data snapshot recovery method and apparatus | |
| CN107256182B (en) | Method and device for restoring database | |
| CN106776121B (en) | Data disaster recovery device, system and method | |
| CN105446828A (en) | Database backup and recovery method, apparatus and system | |
| CN106815097A (en) | Database disaster tolerance system and method | |
| CN104252500A (en) | Method and device for carrying out fault repairing on database management platform | |
| CN103336728A (en) | Disk data recovery method | |
| CN107038091B (en) | A kind of Information Security protection system and electric power application system data guard method based on asynchronous remote mirror image | |
| US11010256B1 (en) | Method and system for implementing current, consistent, and complete backup copy by rolling a change log backwards against a storage device | |
| CN104660386A (en) | DB2 disaster recovery high-availability improving method based on Itanium platform | |
| CN108710550B (en) | Double-data-center disaster tolerance system for public security traffic management inspection and control system | |
| WO2024103594A1 (en) | Container disaster recovery method, system, apparatus and device, and computer-readable storage medium | |
| CN104850628A (en) | Data synchronization method and apparatus in database | |
| CN103793296A (en) | Method for assisting in backing-up and copying computer system in cluster | |
| US11042454B1 (en) | Restoration of a data source | |
| CN112948484A (en) | Distributed database system and data disaster recovery drilling method | |
| CN111125060A (en) | Database management method, system, device and storage medium | |
| KR20100061983A (en) | Method and system for operating management of real-time replicated database | |
| CN105630626A (en) | Transaction backup processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 201112 Shanghai, Minhang District, United Airlines route 1188, building second layer A-1 unit 8 Applicant after: SHANGHAI EISOO INFORMATION TECHNOLOGY CO., LTD. Address before: 200072 room 3, building 840, No. 101 Middle Luochuan Road, Shanghai, Zhabei District Applicant before: Shanghai Eisoo Software Co.,Ltd. |
|
| COR | Change of bibliographic data | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |