CN105045680A

CN105045680A - Data backup method for DM database

Info

Publication number: CN105045680A
Application number: CN201510404633.3A
Authority: CN
Inventors: 吴庆勇
Original assignee: Shanghai Eisoo Software Co Ltd
Current assignee: Shanghai Eisoo Software Co Ltd
Priority date: 2015-07-10
Filing date: 2015-07-10
Publication date: 2015-11-11
Anticipated expiration: 2035-07-10
Also published as: CN105045680B

Abstract

The invention relates to a data backup method for a DM database. The method comprises the following steps of: a1) creating a backup time point object, establishing a connection between an SBT end and a third-party backup end, and creating a database instance object; a2) sending a backup set by the SBT (System Backup to Tape) end through an sbtbackup interface, wherein the backup set comprises a plurality of backup piece files and a meta file (metadata file) of the backup set; a3) receiving the backup set by the third-party backup end, creating corresponding backup piece objects and meta file object in the database instance object, and recording a backup piece name of each backup piece object; a4) segmenting the backup piece objects and the meta file object received by the third-party backup end into corresponding backup piece data block objects and meta data block objects; a5) sending the backup piece data block objects and the meta data block objects to a data storage center by the third-party backup end; and a6) after backup completion, releasing backup resources. Compared to the prior art, the method has the advantages of high data storage reliability, high recovery efficiency and the like.

Description

A kind of method reaching dream database back-up data

Technical field

The present invention relates to database backup method, especially relate to a kind of method reaching dream database back-up data.

Background technology

Since prism door event, the tide cry of infotech production domesticization is constantly surging, after Microsoft's Windows8 operating system is not shortlisted for government procurement ranks, from application, middleware to basic software and hardware, the product of nearly all aspect is all at acceleration localization process.In February, 2014, China set up centralized network security and information-based leading group, and Xi Jinping points out that will there be oneself technology in construction network power, has technology really up to the mark.The supporting dynamics of country to domestic IT enterprises as can be seen here.

Domestic Database manufacturer reaches high-performance data base management system 7.0 version that dream is proposed complete independent intellectual property right, is called for short DM7.DM7 supports third party's backup, provides the read-write interface DMSBTAPI that a set of Backup and Restore is relevant.Meanwhile, it is compulsory that third party realizes the name of DMSBTAPI dynamic base, and be dmsbtex.dll under windows platform, other non-windows platforms (linux or unix platform) are libdmsbtex.so.Dynamic base is deployed in below the system directory bin reaching dream, when reaching dream Backup and Restore, this dynamic base can be loaded.

The backup reaching dream database at present provides local disk and tape two kinds backup, and third party's backup and the tape backup reaching dream and provide use identical read-write interface DMSBTAPI.Local disk backup just backs up data to local disk, damages, the situation such as the collapse of operating system if there is local disk, and the data of backup are just lost, and can not ensure the safe and reliable of data; If at every turn by the Data Migration of backup to other positions, the workload of this cost data library manager again.Tape backup can back up data to tape, brings more safe and reliable deposit position to data, but the throughput speed of tape will be weaker than disk, and the failure rate of machinery of tape is higher.

Summary of the invention

The object of this invention is to provide a kind of method reaching dream database back-up data, solution reaches when dream backups to local disk and occurs that data can not safe and reliablely store on the one hand; Solve on the other hand and reach the slow problem of handling up bringing Backup and Restore when dream backups to tape, the failure rate simultaneously eliminated because of tape is higher, the embarrassment cannot recovered when there is data disaster.

Object of the present invention can be achieved through the following technical solutions:

Reach a method for dream database back-up data, the method backs up end by SBT end with third party and realizes data and transmit, and comprises the following steps:

A1) create BACKUP TIME point object, set up the connection that SBT end and third party back up end, creation database instance objects;

A2) SBT end sends backup set by sbtbackup interface, and this backup set comprises the meta file (meta data file) of some backup piece files and this backup set;

A3) third party backs up termination and receives backup set, creates corresponding backup piece object and meta file object, and record the backup title of each backup piece object under database instance object;

A4) third party backs up end and the backup piece object received and meta file object is divided into corresponding backup piece data block object and meta data block object;

A5) third party backs up end and backup piece data block object and meta data block object is sent to data storage center;

A6) after having backed up, release resource backup.

Described BACKUP TIME point object record has current backup type, and is stored in data storage center.

The Log backup sheet object that described backup piece object generates when comprising data backup sheet object and backup.

Restoration methods corresponding to the method is specially:

B1) obtain the time point object that need recover, set up the connection that SBT end and third party back up end;

B2) third party backs up end from data storage center, obtains meta data block object, recovers meta file object;

B3) data backup sheet object is recovered: recover meta file object, third party backs up end and from data storage center, obtains corresponding backup piece data block object according to the backup title to be restored of SBT end transmission, by server pipeline sends to SBT hold after organizing according to the data receiver length of SBT end to each backup piece data block object;

B4) Log backup sheet object is recovered;

B5), after having recovered, release recovers resource.

The connection that the described SBT of foundation end and third party back up end is specially:

101) third party backs up end establishment and holds mutual server pipeline with SBT, and this server pipeline is in waiting status;

102) create backup thread startup backup or create recovery thread and start recovery;

103) held the initial message sent by server conduit acceptor SBT, realize connecting.

Described step b3) in, often recover all to re-create server pipeline in a backup piece Object Process.

Compared with prior art, the present invention adopts third party to back up, and back up data to data storage center, data storage center is the storage medium in strange land, disk is made soft Raid, on its basis, builds volume management disk, fast quick-recovery when so both having ensured data disaster occurs, also ensure that the security of data, reliability, there is following beneficial effect:

1. the method meet backup manufacturer generally back up the requirement reaching dream database;

2. data base administrator's migration data this method solves the position insecurity reaching the deposit data that the backup of dream local disk generates, if can increase workload;

3. this method solve throughput speed when reaching dream tape backup slow, and tape failure rate of machinery is higher, easily occurs needing can not recover data when recovering;

4. the present invention adopts third party to back up, instead of adopts and reach the backup scenario that dream itself provides, can well the data security of management database, reduces each database manufacturer and increases R&D costs in order to data security.

Accompanying drawing explanation

Fig. 1 is that third party of the present invention backs up process flow diagram;

Fig. 2 is that third party of the present invention recovers process flow diagram.

Embodiment

Below in conjunction with the drawings and specific embodiments, the present invention is described in detail.The present embodiment is implemented premised on technical solution of the present invention, give detailed embodiment and concrete operating process, but protection scope of the present invention is not limited to following embodiment.

The present embodiment provides a kind of method reaching dream database back-up data, mainly reaches dream database by pipeline Backup and Restore, uses the read-write interface reaching the DMSBTAPI that dream provides to realize, specifically comprises:

1, third party's backup reaches dream database: third party initiates backup request by the SQL statement reaching dream, reaches dream database and starts a Backup and Restore process and load SBT dynamic base carries out data transmission by pipeline.

Shown in composition graphs 1, elaboration SBT end and third party back up data transmission procedure between end.

1) SBT end

SBT end provides the interface of DMSBTAPI, carries out context initialization, newly-built backup piece and write the processes such as data by these interfaces.SBT end backup flow process is as follows:

1. initialization context;

sbtinit(initins,&initouts)；

2. backup procedure initialization;

sbtinit2(init2ins,&init2outs)；

3. a newly-built backup piece;

sbtbackup(SBTFILE_DATAFILE,“DB_DAMENG_..._XXXXXX.bak”)；

4. write data, the content of buffer writes the backup piece of sbtbackup establishment;

sbtwrite(buffer,length)；

……

5. a backup piece Backup end, closes backup piece;

sbtclose()；

6. the information of current end backup piece is got;

sbtinfo(&sbtobjinfos)；

As there are the data that do not backed up or needing to write meta file, return 3.;

7. meta file is backed up;

sbtbackup(SBTFILE_DATAFILE,“DB_DAMENG_..._XXXXXX.meta”)；

sbtwrite(buffer,length)；

……

sbtclose()；

8. the resource of backup is discharged;

Sbtend (FALSE); If // backup failure, then sbtend (TRUE);

2) third party backs up end

Third party backs up end and had both provided the associative operation mutual with SBT, also provides the operation mutual with data storage center.Concrete operations are as follows:

1. BACKUP TIME point object is created;

Often initiate once to back up just corresponding generation time point object, the type of this time point object record current backup also sends to data storage center.

2. creation database instance objects;

Each database instance can produce a database instance objects at each time point, before transmission database instance object is to data storage center, need the operation of execution as follows: to be first create the server pipeline mutual with SBT and allow pipeline be in waiting status; Next creates backup thread, uses SQL statement to start backup procedure in thread; Be finally receive the initial message that SBT sends to server pipeline, represent that third party backs up end and SBT end can formal communication.

3. backup piece or meta object is created;

Reach dream DB Backup and generate a complete backup set, a backup set comprises the meta file of some backup piece files and this backup set.Can distinguish backup piece or meta file according to the backup file type that the sbtbackup interface of SBT sends over, transmission backup piece object or meta object are to data storage center.

4. the data block object of backup piece or meta is created;

Data block is sent data block to data storage center in the mode of an object by data block object, sends data block back up end to third party according to the sbtwrite interface of SBT by pipeline.

2, third party recovers to reach dream database: third party initiates recovery request by the DMRMAN process reaching dream, reaches dream database and starts a Backup and Restore process and load SBT dynamic base carries out data transmission by pipeline.

Shown in composition graphs 2, set forth data transmission procedure between SBT end and third party's reset terminal.

1) SBT end

SBT end provides the interface of DMSBTAPI, by processes such as these interfaces carry out that context initialization, date restoring and data are read.It is as follows that SBT end recovers flow process:

The first, recover meta data file and it is verified;

1. initialization context;

sbtinit(initins,&initouts)；

2. reduction process initialization;

sbtinit2(init2ins,&init2outs)；

3. open and read meta file, filename uses the meta filename returned in sbtinit2 herein, ignores directory information;

sbtrestore(“DB_DAMENG_..._XXXXXX.meta”)；

sbtread(buffer,length)；

sbtclose()；

4. the resource of recovery is discharged;

Sbtend (FALSE); If // recover unsuccessfully, then sbtend (TRUE);

The second, reduction backup set process, carries out off line restoring data by DMRMAN process;

1. initialization context;

sbtinit(initins,&initouts)；

2. reduction process initialization;

sbtinit2(init2ins,&init2outs)；

sbtrestore(“DB_DAMENG_..._XXXXXX.meta”)；

sbtread(buffer,length)；

sbtclose()；

4. open and specify backup piece file, use filename to use the filename (SBTBFINFO_NAME) returned by sbtinfo during backup herein, the backup piece of reduction does not comprise in backup procedure the backup piece producing daily record;

sbtrestore(“DB_DAMENG_..._XXXXXX.bak”)；

5. read data;

sbtread(buffer,length)；

……

6. a backup piece Backup end;

sbtclose()；

There is no the data of reducing as existed, returning 4.;

7. the resource of recovery is discharged;

Sbtend (FALSE); If // recover unsuccessfully, then sbtend (TRUE);

3rd, recover data procedures, carry out off-line recovery Log backup sheet by DMRMAN process, the backup log can reformed in backup set during recovery, by database recovery to state during backup;

1. initialization context;

sbtinit(initins,&initouts)；

2. reduction process initialization;

sbtinit2(init2ins,&init2outs)；

sbtrestore(“DB_DAMENG_..._XXXXXX.meta”)；

sbtread(buffer,length)；

sbtclose()；

The backup piece file of daily record is produced, the filename (SBTBFINFO_NAME) returned by sbtinfo when using filename to be also and to use backup herein when 4. opening backup;

sbtrestore(“DB_DAMENG_..._XXXXXX_1.bak”)；

5. read data;

sbtread(buffer,length)；

……

6. a backup piece Backup end;

sbtclose()；

There is no the daily record data reduced as existed, returning 4.;

7. the resource of recovery is discharged;

Sbtend (FALSE); If // recover unsuccessfully, then sbtend (TRUE);

3) third party's reset terminal (namely third party backs up end)

Third party's reset terminal needs to process the associative operation mutual with SBT equally, also needs to process the operation mutual with data storage center.Concrete operations are as follows:

1. the time point object of recovery is obtained;

The time point object needed is recovered, as selected complete BACKUP TIME point to recover, as long as recover this time point object according to the time point object selected; If select Delta Time point object to recover, then all time point objects before recovering once completely between BACKUP TIME point object to this time point object.

2. instance database object is recovered;

The first, recover the data block of meta object, for inspection;

Each recovery instance database, needs the data block first recovering meta file object, needs executable operations as follows before recovery: be first create the server pipeline mutual with SBT and allow pipeline be in waiting status; Next creates reduction thread, uses DMRMAN process initiation reduction process in thread; Be finally receive the initial message that SBT sends to server pipeline, represent that third party's reset terminal and SBT end can formal communication.

The second, backup piece under restore database example, but the backup piece of the daily record generated when not comprising backup;

Under restore database example, backup piece operating process is as follows: first, recovers the data block of meta file object; Secondly, the filename (SBTBFINFO_NAME) returned according to sbtinfo recovers the object of backup piece, sends the data block that the backup title recovered recovers under corresponding backup piece object by the sbtrestore interface of SBT at every turn; Finally, often recover all to need to re-create lower server pipeline in a backup piece process, because the client pipeline in SBT can disconnect, the data block recovered receives according to the size needed in sbtread interface, but the size that each data storage center sends may not meet the length that sbtread receives, need third party's reset terminal effectively to organize, ensure the consistance of database.

3rd, produce Log backup sheet during backup under restore database example;

When recovering Log backup sheet, the recovery operation of needs is as follows: be first create the server pipeline mutual with SBT and allow pipeline be in waiting status; Next creates to recover thread, uses DMRMAN process initiation rejuvenation in thread; Be finally recover meta file object and Log backup sheet object, the operation that data block is recovered is identical with data backup sheet object recover data blocks.

With an instantiation, above-mentioned back-up restoring method is described below.

Suppose have to reach a dream DB Backup task job, this job has and N number ofly reaches dream example, explain with one of them DM1 example, and the Log backup sheet file (DB_DAMENG_20150405_021221_000343_1.bak) of meta data file (DB_DAMENG_20150405_021221_000343.meta), data backup sheet file (DB_DAMENG_20150405_021221_000343.bak) and generation when backing up in the backup set of this DM1 instance backup generation.This job performs once BACKUP TIME point tp1, N incremental backup time point completely, and this enforcement reaches the method for dream database back-up data for primary complete BACKUP TIME point tp1 explanation.

1, third party's backup procedure citing

1) create a complete BACKUP TIME point object objtp1, it have recorded the time point tp1 of backup;

2) create a database instance objects objdm1, it have recorded the database instance dm1 of backup; Create server pipeline server_pipe simultaneously and create backup thread thread1, in thread thread1, using on-line backup SQL statement " backupdatabasefullbackupset ' DAMENG_BAK_2015_04_05_02_12_21 ' devicetypetape " to initiate backup;

3) the backup piece filename sended over according to SBT or meta filename creation database backup piece object or meta object are objbak, objbak_1 and objmeta;

4) a backup piece object or meta object have data, and with one of them objbak object, the data block object of generation has objdata1, objdata2...objdataN.Reach the data block that dream sends and maximumly can reach 64M, and this data storage center only accepts the data block of 3M, carry out Data Segmentation be sent to data storage center so need third party to back up end.

2, third party's rejuvenation citing

1) a complete BACKUP TIME point object objtp1 is obtained;

2) obtain the database instance object objdm1 recovered, rejuvenation is as follows:

1. objmeta is recovered for checking the integrality of data, create server pipeline server_pipe1 and create reduction thread thread1, in thread thread1, use the prototype statement " restoredatabase'C: dmdbms data DM1 dm.ini'frombackupset ' DB_DAMENG_20150405_021221_000343.meta ' devicetypetape " of going back of DMRMAN process to initiate reduction; Then the data block under this object is sent according to objmeta object;

2. need to re-create pipeline server_pipe2 before recovering objbak object, because pipeline after 1. having recovered objmeta can disconnect; First again recover the data block of objmeta object, and then recover the data block of objbak object;

3. need before recovering objbak_1 object to create server pipeline server_pipe3 and create to recover thread thread2, use in thread thread2 the recovery statement of DMRMAN process " recoverdatabase'C: dmdbms data DM1 dm.ini'frombackupset ' DB_DAMENG_20150405_021221_000343.meta ' devicetypetape " initiate to recover.First recover the data block under objmeta object, then recover the data block under objbak_1 object, for the backup log reformed in backup set, state when returning to backup.

Claims

1. reach a method for dream database back-up data, it is characterized in that, the method backs up end by SBT end with third party and realizes data and transmit, and comprises the following steps:

A2) SBT end sends backup set by sbtbackup interface, and this backup set comprises the meta file of some backup piece files and this backup set;

A6) after having backed up, release resource backup.

2. the method reaching dream database back-up data according to claim 1, is characterized in that, described BACKUP TIME point object record has current backup type, and is stored in data storage center.

3. the method reaching dream database back-up data according to claim 1, is characterized in that, the Log backup sheet object generated when described backup piece object comprises data backup sheet object and backup.

4. the method reaching dream database back-up data according to claim 3, is characterized in that, restoration methods corresponding to the method is specially:

B4) Log backup sheet object is recovered;

B5), after having recovered, release recovers resource.

5. the method reaching dream database back-up data according to claim 1 or 4, is characterized in that, the connection that the described SBT of foundation end and third party back up end is specially:

6. the method reaching dream database back-up data according to claim 5, is characterized in that, described step b3) in, often recover all to re-create server pipeline in a backup piece Object Process.