CN109739691A - DB Backup and restoration methods, device, terminal device and storage medium - Google Patents
DB Backup and restoration methods, device, terminal device and storage medium Download PDFInfo
- Publication number
- CN109739691A CN109739691A CN201811645760.2A CN201811645760A CN109739691A CN 109739691 A CN109739691 A CN 109739691A CN 201811645760 A CN201811645760 A CN 201811645760A CN 109739691 A CN109739691 A CN 109739691A
- Authority
- CN
- China
- Prior art keywords
- file
- backup
- database
- node
- library
- 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.)
- Pending
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses DB Backups and restoration methods, device, terminal device and storage medium.The database backup method comprises determining that and records the backup starting point of each node in source database；The corresponding library file of the source database is backuped into target database；Determine and record the Backup end point of each node in the source database, the recovery for the target database based on the backup starting point, library file and Backup end point progress database.It can be improved the accuracy to source database backup using this method.
Description
Technical field
The present embodiments relate to database technical field more particularly to DB Backups and restoration methods, device, terminal
Equipment and storage medium.
Background technique
With the rapid development of office automation and e-commerce, enterprise is higher and higher to the dependence of information system, number
Take on important role as the core of information system according to library, and DB Backup is the important hand of Database Systems disaster tolerance
Section.DB Backup includes on-line backup, i.e., the backup carried out in the case where database operates normally.
In order to ensure the consistency of data after target data library backup, traditional copy backup is to rely on Backup Data library text
The sequence of part ensures, it is ensured that online log file is backed up prior to data file, finally using recording in online log file
System generates log serial number when checkpoint, i.e. CKPT_LSN carries out the recovery of database as the starting point of recovery.
But for Real Application Clusters (Real Application Cluster, RAC) environment, each node has
The online log file of oneself, during on-line backup, the backup of each node online log file causes always there are the time difference
Backup to the CKPT_LSN in target database in the online log file of each node can there is a situation where it is inconsistent, if directly it is extensive
Multiple, then the data that will lead to after restoring are inconsistent.
Summary of the invention
The embodiment of the invention provides DB Backups and restoration methods, device, terminal device and storage medium, solve
Because each node standby Time Inconsistency leads to the technical problem that data are inconsistent after restoring in RAC environment.
In a first aspect, the embodiment of the invention provides a kind of database backup methods, comprising:
Determine and record the backup starting point of each node in source database；
The corresponding library file of the source database is backuped into target database；
The Backup end point of each node in the source database is determined and recorded, so that the target database is based on described
Backup starting point, library file and Backup end point carry out the recovery of database.
Optionally, the backup starting point for determining and recording each node in source database, comprising:
Using the checkpoint log serial number of node each in source database as backup starting point；
The backup starting point is recorded in the corresponding library file of the source database.
Optionally, the Backup end point for determining and recording each node in the source database, comprising:
According to the corresponding file journalization sequence number of each node, Backup end point, the file journalization sequence number are determined
Log serial number when journal file is completed is stored in for log；
Record the Backup end point.
Optionally, described according to the corresponding file journalization sequence number of each node, determine Backup end point, comprising:
Obtain the file journalization sequence number of each node in database；
Maximum file journalization sequence number is chosen from each file journalization sequence number；
Using the maximum file journalization sequence number as Backup end point.
Optionally, after the Backup end point for determining and recording each node in the source database, further includes:
The corresponding archive log file backup of each node of backup condition will be met in source database to the target
Database.
Optionally, the library file include data file, control file, the corresponding online log file of each node and/or
The corresponding configuration file of each node.
Second aspect, the embodiment of the invention also provides a kind of database restoring methods, comprising:
Obtain predetermined backup starting point and Backup end point and the library file backed up from source database and filing
Journal file；
Storage location based on target database modifies the file path information in the library file, obtains target library text
Part；
According to the archive log file, object library file, backup starting point and Backup end point carry out the extensive of database
It is multiple.
Optionally, the library file include data file, control file, the corresponding online log file of each node and/or
The corresponding configuration file of each node；Correspondingly, the storage location based on target database modifies the text in the library file
Part routing information, obtains object library file, comprising:
Target is revised as in the path for controlling data file recorded in file and configuration file and journal file respectively
The corresponding address information of the storage location of database, obtains object library file.
The third aspect, the embodiment of the invention also provides a kind of DB Backup devices, comprising:
First obtains module, for determining and recording the backup starting point of each node in source database；
Library file backup module, for the corresponding library file of the source database to be backuped to target database；
Second obtains module, for determining and recording the Backup end point of each node in the source database, for described
Target database carries out the recovery of database based on the backup starting point, library file and Backup end point.
Fourth aspect, the embodiment of the invention also provides a kind of database recovery devices, comprising:
Third obtain module, for obtain predetermined backup starting point and Backup end point and from source database it is standby
The library file and archive log file of part；
Modified module modifies the file path information in the library file for the storage location based on target database,
Obtain object library file；
Recovery module is used for according to the archive log file, object library file, backup starting point and Backup end point,
Carry out the recovery of database.
5th aspect, the embodiment of the invention also provides a kind of terminal devices, comprising:
One or more processors；
Storage device, for storing one or more programs；
One or more of programs are executed by one or more of processors, so that one or more of processors
Realize database backup method provided in an embodiment of the present invention or database restoring method.
6th aspect, the embodiment of the invention also provides a kind of computer readable storage mediums, are stored thereon with computer
Program, the program realize database backup method provided in an embodiment of the present invention or database recovery side when being executed by processor
Method.
The embodiment of the invention provides DB Backup and restoration methods, device, terminal device and storage medium, databases
Backup method determines and records the backup starting point of each node in source database first；Then by the corresponding library of the source database
File backup is to target database；Determine and record the Backup end point of each node in the source database, finally for described
Target database carries out the recovery of database based on the backup starting point, library file and Backup end point.Utilize above-mentioned technology
Scheme can be improved the accuracy to source database backup, avoid because the BACKUP TIME of each node is inconsistent in source database
Lead to the technical problem that data are inconsistent.
Detailed description of the invention
Fig. 1 a is a kind of flow diagram for database backup method that the embodiment of the present invention one provides；
Fig. 1 b is the RAC system architectural schematic that the embodiment of the present invention one provides；
Fig. 2 is a kind of flow diagram of database backup method provided by Embodiment 2 of the present invention；
Fig. 3 is a kind of flow diagram for database restoring method that the embodiment of the present invention three provides；
Fig. 4 is a kind of structural schematic diagram for DB Backup device that the embodiment of the present invention four provides；
Fig. 5 is a kind of structural schematic diagram for database recovery device that the embodiment of the present invention five provides；
Fig. 6 is a kind of structural schematic diagram for terminal device that the embodiment of the present invention six provides.
Specific embodiment
The present invention is described in further detail with reference to the accompanying drawings and examples.It is understood that this place is retouched
The specific embodiment stated is used only for explaining the present invention rather than limiting the invention.It also should be noted that in order to just
Only the parts related to the present invention are shown in description, attached drawing rather than entire infrastructure.
It should be mentioned that some exemplary embodiments are described as before exemplary embodiment is discussed in greater detail
The processing or method described as flow chart.Although operations (or step) are described as the processing of sequence by flow chart,
Many of these operations can be implemented concurrently, concomitantly or simultaneously.In addition, the sequence of operations can be pacified again
Row.The processing can be terminated when its operations are completed, it is also possible to have the additional step being not included in attached drawing.Institute
Stating processing can correspond to method, function, regulation, subroutine, subprogram etc..
Embodiment one
Fig. 1 a is a kind of flow diagram for database backup method that the embodiment of the present invention one provides, and this method is applicable
In back up to database the case where, specifically, this method is applicable to the case where backup of online copy is carried out to database.
This method can be executed by DB Backup device, wherein the device can be implemented by software and/or hardware, and generally integrated
On the terminal device, terminal device includes but is not limited in the present embodiment: laptop, desktop computer or server etc. are set
It is standby.
As shown in Figure 1a, a kind of database backup method that the embodiment of the present invention one provides, includes the following steps:
S101, the backup starting point for determining and recording each node in source database.
In the present embodiment, source database can be understood as the database of pending DB Backup.Node is understood that
For database instance in database.Backup starting point can be understood as carrying out recovery starting point when database recovery.
Database backup method in the present embodiment can be applied under RAC environment, be readily applicable to non-RAC environment.
Wherein, RAC environment may be considered example more than one, the system of single database.Multiple database instances can be same
When access, modify the data of the same database.User can log in any one database instance in cluster, obtain complete
Database service.Data file, control file are only a in group system, no matter there is several nodes, these nodes are all
Coequally use these files.Each node has oneself independent online log and archive log.
Fig. 1 b is the RAC system architectural schematic that the embodiment of the present invention one provides, and as shown in Figure 1 b, client 11 can
With the database file 14 shared by first node 12 or the access of second node 13.13 equality of first node 12 and second node
Ground uses the data file and control file in shared database file 14.First node 12 and second node 13 exist respective
Corresponding archive log file and online log file.
When carrying out DB Backup, this step can determine that backup corresponding to each node originates in source database first
Point.The specific means that can not be determined herein to backup starting point is defined, and those skilled in the art can be according to practical feelings
Condition chooses corresponding means and determines backup starting point.Such as, data can be carried out using journal file when carrying out database recovery
The recovery in library, therefore this step can be using journal file and the corresponding log serial number of data file as backup starting point.Wherein,
Journal file and the corresponding log serial number of data file may be considered the moment be based on journal file can recover data
File.
Journal file can be divided into online log file and archive log file, for storing data the transaction journal in library,
To be able to carry out fault recovery when breaking down and media failure.Online log file refers in database operational process
The log of generation.When user adds in the database, deletes, modifies object, or change data, database all can be according to specific
Format, by these operation execute results be written in current online log file.Online log file is mainly used for counting
According to the backup, reduction and recovery in library.
When archive log file refers to that database is run under archive mode, redoes log and continuously copied to filing day
The part of will file, using archive log, database can be restored to the eve of failure generation, can also revert to specified
Time point.
Log serial number (Log Sequence Number, LSN) is the numerical value for being distributed and being safeguarded automatically by database, tool
There is automatic incremental, globally unique characteristic.Each LSN value represents a physics affairs of data store internal generation.Physics thing
Business (Physical Transaction, ptx) is a series of set of modification physical data page operations of data store internal, with data
Affairs (Transaction) concept is corresponding in base management system, has atomicity, order, the characteristics such as can not cancel.Data
Library generates LSN when checkpoint, is named as CKPT_LSN.The data page of the physics affairs modification of all LSN≤CKPT_LSN,
Disk all is written from buffer area.This step can be using LSN when generating checkpoint as backup starting point.
In determining source database after the backup starting point of each node, it can back up each node determined is corresponding
Initial point is recorded, and is not defined herein to the specific means of record, can such as be recorded each backup starting point determined
Into the library file of source database, it is then copied to target database, is counted so that target database is based on backup starting point
According to the recovery in library；It can also be recorded by user, when target database carries out database recovery, directly acquire user's input
Backup starting point, for target database carry out database recovery.
It should be noted that because needing to complete using archive log when target database carries out the recovery of database,
Therefore under the present embodiment when carrying out DB Backup needs that database server is made to run on archive mode.It is understood that
Database can be run under archive mode and non-archive mode, and under non-archive mode, database will can only redo log write-in
It is stored in online log file；Under archive mode, database will can redo log write-in online log file simultaneously and return
It is stored respectively in shelves journal file.
S102, the corresponding library file of the source database is backuped into target database.
In the present embodiment, library file can be understood as the file in database.Library file may include data file, control
File, the corresponding online log file of each node and/or the corresponding configuration file of each node processed etc..Target database is understood that
For the database of pending database recovery.
After the corresponding backup starting point of each node for determining source database, this step can execute source data library of libraries
The back-up job of file.That is, the corresponding library file of source database can be backuped to target database by this step.Wherein back up
The particular content of library file can be not construed as limiting, and those skilled in the art can according to need the online day in backup source database
Will file, data file, control file and configuration file.If RAC environment, then need to copy the library text on all nodes
Part.
The backup means of library file are not defined herein, such as can be backed up or be led to by the order of operating system
The mode remotely sent is crossed to be backed up.
S103, the Backup end point for determining and recording each node in the source database, for the target database base
The recovery of database is carried out in the backup starting point, library file and Backup end point.
In the present embodiment, Backup end point can be understood as carry out database recovery when recovery terminal.
After the corresponding library file of source database is backuped to target database, this step may further determine that source database
In each node Backup end point, herein not to determining that the determination means of Backup end point of each node in source database limit
Fixed, those skilled in the art can set according to actual needs, as long as guaranteeing that all logs are all deposited before Backup end point
In journal file.Such as, all operation logs can be input to corresponding log sequence when journal file by this step
Row number is as Backup end point.
It is understood that the Backup end point of each node can be identical, it, can be to each section when determining Backup end point
The log serial number of point is analyzed, to determine Backup end point.
A kind of database backup method that the embodiment of the present invention one provides, it is first determined and record each node in source database
Backup starting point；Then the corresponding library file of the source database is backuped into target database；Finally determine and record institute
State the Backup end point of each node in source database, for the target database be based on the backup starting point, library file and
The recovery of Backup end point progress database.Using the above method, it can be improved the accuracy to source database backup, avoid
Because of the inconsistent technical problem for causing data inconsistent of the BACKUP TIME of each node in source database.
Embodiment two
Fig. 2 is a kind of flow diagram of database backup method provided by Embodiment 2 of the present invention, and the present embodiment two exists
It is optimized on the basis of the various embodiments described above.In the present embodiment, the backup of each node in source database will be determined and recorded
Starting point, optimization include: using the checkpoint log serial number of node each in source database as backup starting point；By the backup
Starting point is recorded in the corresponding library file of the source database.
Further, the present embodiment will also determine and record the Backup end point of each node in the source database, optimization
It include: that Backup end point, the file journalization Serial No. day are determined according to the corresponding file journalization sequence number of each node
Will is stored in log serial number when journal file is completed；Record the Backup end point.
On the basis of above-mentioned optimization, the Backup end point for determining and recording each node in the source database it
Afterwards, also optimization includes:
The corresponding archive log file backup of each node of backup condition will be met in source database to the target
Database.
Further, the library text piece optimization is included that data file, control file, each node are corresponding by the present embodiment
Machine journal file and/or the corresponding configuration file of each node.
The not yet detailed content of the present embodiment please refers to embodiment one.
As shown in Fig. 2, a kind of database backup method provided by Embodiment 2 of the present invention, includes the following steps:
S201, using the checkpoint log serial number of node each in source database as backup starting point.
In the present embodiment, checkpoint log serial number can be understood as log serial number when database generates checkpoint.
This step can be originated when determining backup starting point using the checkpoint log serial number of each node as backup
Point, to guarantee the consistency of data.
Specifically, this step can obtain the inspection of each node in source database by any node in access source database
Log serial number is made an inventory of, then using the corresponding checkpoint log serial number of each node as backup starting point.
S202, the backup starting point is recorded in the corresponding library file of the source database.
After determining the corresponding backup starting point of each node, source can be recorded in each backup starting point by this step
In the corresponding library file of database, the specific location that backup starting point is recorded can not be limited herein, as long as in target data
When library carries out the recovery of database, each backup starting point can be found.Illustratively, each backup starting point can be remembered
It records in data file.
S203, the corresponding library file of the source database is backuped to target database, library file includes data file, control
File, the corresponding online log file of each node and/or the corresponding configuration file of each node processed.
In the present embodiment, particular content included by data file, control file, online log file and configuration file
It is not construed as limiting, can be determined according to the type of database.Such as, data file can be understood as in database library for storing data
Data file.Control file can be understood as in database for recording and safeguarding the physical structure of database.Configuration text
Part can be understood as the file of database of record configuration information in database.
After having determined and recorded the backup starting point of each node, this step can execute the backup operation of library file.This
The library file that step is backed up may include data file, control file, the corresponding online log file of each node and/or each section
The corresponding configuration file of point.
It is understood that the content specifically included in library file can be determined according to actual needs, if RAC
Environment then can back up full content in source database, such as that data file, control file, each node is corresponding
Online log file and the corresponding configuration file of each node back up to target database.
S204, according to the corresponding file journalization sequence number of each node, determine Backup end point, the file journalization sequence
Row number is log serial number when log is stored in journal file completion.
In the present embodiment, file journalization sequence number can be understood as all logs in database before the log serial number
It is stored in journal file.
This step can determine backup knot when determining Backup end point according to the corresponding file journalization sequence number of each node
Beam spot is specific to determine that means are not construed as limiting herein.The case where as that can be restored according to needed for target database, determines specific determine
Means.Such as, this step can be using file journalization sequence number maximum in each node as Backup end point.
Further, according to the corresponding file journalization sequence number of each node, Backup end point is determined, comprising:
Obtain the file journalization sequence number of each node in database；
Maximum file journalization sequence number is chosen from each file journalization sequence number；
Using the maximum file journalization sequence number as Backup end point.
Wherein, maximum file journalization sequence number can be understood as the corresponding file journalization sequence number of each node being compared
Afterwards, the maximum file journalization sequence number of the numerical value selected.
S205, the Backup end point is recorded.
After determining complete part end point, this step can be recorded the Backup end determined point.It is not right herein
The concrete mode of record is defined, and can also be can store in terminal device by user record.When terminal device accesses mesh
When marking database progress database recovery, the recovery of database can be carried out based on the Backup end point of record.
S206, the corresponding archive log file backup of each node of backup condition will be met in source database to described
Target database.
In the present embodiment, the particular content for backing up condition can be not construed as limiting, and those skilled in the art can be according to reality
Border demand determines backup condition.Such as back up the filter condition that condition can be archive log file.It can will return in the present embodiment
The initial range of shelves journal file is as backup condition.The selection of initial range is not construed as limiting herein, can such as be originated backup
Initial range of the point as archive log file.
After determining Backup end point, this step obtains the archive log file of each node of source database, then will filing
Journal file backups to target database, so that target database carries out the recovery of database.It is understood that this step
It can be by whole archive log file backups of each node to target database, correspondingly, backup condition is whole archive logs
File.
The specific means of backup archive log file is not defined herein, the means of backup archive log file can be with
Used means when referring to backup library file.
The present embodiment is illustratively described below:
Present embodiments provide a kind of database backup method, the sequence of the database backup method backup database regardless of
Successively, the range that database recovery is limited by backup starting point and Backup end point, solves in RAC environment because each node is copied
The inconsistent problem of data caused by shellfish BACKUP TIME is inconsistent.
The database backup method requires database server to run under archive mode.Because of the recovery of database, need
It to be completed using archive log.
Specifically database backup method is as follows:
One, copy work before record copies starting point, that is, determine and record each node in source database backup starting
Point:
Use current CHECKPOINT information as copy backup starting point, specific implementation can be will be current
CHECKPOINT information is recorded in control page, is recorded as LSN_ARR_FOR_COPY.
Two, work is copied:
Online log file, data file, control file and configuration file in duplication source data library as needed.If
For RAC environment, then need to copy the library file on all nodes.
Three, copy end point is taken after copying work, that is, determines and records the Backup end of each node in the source database
Point:
Use current FILE LSN (i.e. file journalization sequence number) as copy end point record.Specific implementation, is to pass through
It executes SQL statement query result and returns to each node maximum FILE LSN, be restored to maximum LSN value as using filing, this is standby
Part end point is voluntarily recorded as COPY_LSN_MAX by user.
A kind of database backup method provided by Embodiment 2 of the present invention embodies library file, backup starting point determines
Operation, Backup end point determine operation, and also optimization includes archive log file backup operation.It can be according to source using this method
The checkpoint log serial number of each node determines backup starting point in database, and library is recorded in the backup starting point determined
Then library file is backuped to target database by file, so that target database is when carrying out database recovery, determine recovery
Starting point；After library file is backuped to target database, Backup end point is determined according to the file journalization sequence number of each node, for
Target database determines the end point restored when carrying out database recovery；Backup condition will finally be met in source database
Archive log file backup is to target database, with the recovery for carrying out database.Duplication source data library file in this method
Sequence in no particular order, the recovery range of target database is limited by backup starting point and Backup end point, can effectively be solved
Certainly under RAC environment because each node copy BACKUP TIME it is inconsistent caused by the inconsistent technical problem of data, improve database
The efficiency of on-line backup.
Embodiment three
Fig. 3 is a kind of flow diagram for database restoring method that the embodiment of the present invention three provides, and this method is applicable
In restore to database the case where, this method can be executed by database recovery device, and wherein the device can be by software
And/or hardware realization, and be typically integrated on terminal device, terminal device includes but is not limited in the present embodiment: notebook
The equipment such as computer, desktop computer or server.
As shown in figure 3, a kind of database restoring method that the embodiment of the present invention three provides, includes the following steps:
S301, obtain predetermined backup starting point and Backup end point and from the library file of source database backup and
Archive log file.
In the present embodiment, backup starting point can be understood as carry out database recovery when recovery starting point.Backup end
Point can be understood as carrying out the recovery terminal when recovery of database.Wherein, backup starting point and Backup end point can be number
It is predetermined according to the library backup stage.Source database can be understood as the database of pending DB Backup.Library file can be with
The file being interpreted as in database.Library file may include data file, control file, the corresponding online log file of each node
And/or corresponding configuration file of each node etc..Journal file can be divided into online log file and archive log file, for depositing
The transaction journal of database is stored up, to be able to carry out fault recovery when breaking down and media failure.Archive log file can
When referring to that database is run under archive mode, the part for continuously being copied to archive log file is redo log, is utilized
Archive log, database can be restored to the eve of failure generation, can also revert to specified time point.
When carrying out database recovery, backup starting point and Backup end point can be obtained first, to determine the model restored
It encloses；Library file and archive log file are obtained, the recovery of database can be executed.
File path information in S302, the storage location modification library file based on target database, obtains target library text
Part.
In the present embodiment, storage location can be understood as the address that library file is stored in target database.File path
Information can be understood as the address information of file included by library file.Object library file can be understood as file in library file
Routing information is formed by file after modifying.
It is understood that library file can store at the different location of target database, therefore carrying out library file
When file path information is modified, path modification can be carried out according to the storage location of corresponding contents in library file.Illustratively, originally
The path of data file and journal file in the control file stored in database can be revised as data file and day by step
Actual address of the will file in target database.
It is understood that unlimited periodical repair changes library file and obtains backup starting point, Backup end point and filing day herein
The sequence of will file.Backup starting point, Backup end point and archive log file can also the acquisitions when carrying out database recovery.
S303, according to the archive log file, object library file, backup starting point and Backup end point carry out data
The recovery in library.
This step can be executed and be operated from local archive log file access pattern when carrying out database recovery.It is being counted
According to library recovery when, backup starting point and Backup end point are for determining the range restored, archive log file and target library text
Part is used to complete the recovery of database.
Exemplary description is carried out to database restoring method in the present embodiment below:
1, modification control file, data file, journal file path are actual address in configuration file；
2, the initial range of archive log needed for checking, and the copy targeting archive log file from source database；
3, target database is executed restores from local archive log, and after the recovery operation for completing copy library, database is available.
Exemplary description is carried out below for the whole process of DB Backup and database recovery:
By taking the database of two nodes as an example, the storage condition of each file is as follows in database:
Source database:
The path of configuration file:
EP01:E:\rac\test\rac630_cfg1\dm.ini；
EP02:E:\rac\test\rac630_cfg2\dm.ini。
Control file path: E: rac test rac630 dm.ctl.
The catalogue of data file :+rac_data/rac_data/rac630.
The path of online log file:
EP01:+rac_log0/rac630/log/log101.log
+rac_log0/rac630/log/log102.log；
EP02:+rac_log0/rac630/log/log201.log
+rac_log0/rac630/log/log202.log。
Local archive log file and remote archive logfile directory:
EP01:E:\rac\test\rac630_cfg1\arch_local
E:\rac\test\rac630_cfg1\arch_remote；
EP02:E:\rac\test\rac630_cfg2\arch_local
E:\rac\test\rac630_cfg2\arch_remote。
Object library:
The path of configuration file:
EP01:F:\rac\test\rac630_cfg1\dm.ini；
EP02:F:\rac\test\rac630_cfg2\dm.ini。
Control file path: F: rac test rac630 dm.ctl.
The catalogue of data file :+rac_data/rac_data/rac630.
Online log file path:
EP01:+rac_log0/rac630/log/log101.log
+rac_log0/rac630/log/log102.log；
EP02:+rac_log0/rac630/log/log201.log
+rac_log0/rac630/log/log202.log。
Local archive log file and remote archive logfile directory:
EP01:F:\rac\test\rac630_cfg1\arch_local
F:\rac\test\rac630_cfg1\arch_remote；
EP02:F:\rac\test\rac630_cfg2\arch_local
F:\rac\test\rac630_cfg2\arch_remote。
1, the copy procedure of source database:
Backup starting point is recorded before 1 > copy:
System function SP_BACKUP_COPY_BEGIN () is such as executed, control page is recorded in current CHECKPOINT information
In, and it is output to client, it is recorded as LSN_ARR_FOR_COPY.
2 > duplication source data library file process:
All library files in duplication source data library, including online log file, data file, control file and configuration file
Deng copying target database corresponding position to.The copy sequence of file is in no particular order.
After 3 > copy library file, Backup end point is recorded:
System function SF_BACKUP_COPY_END () is such as executed, each node maximum FILE_LSN (i.e. file journalization is taken out
Sequence number), and record, it is denoted as COPY_LSN_MAX；
2, target database recovery process:
File routing information is currently practical path in all configuration file dm.ini of 1 > modification:
Such as CTL_PATH by it is original E: rac test rac630 dm.ctl be revised as F: rac test
rac630\dm.ctl；
File routing information in 2 > modification control file dm.ctl:
A > execution is such as issued orders, and dm.ctl is converted to txt format content:
Dmctlcvt.exe type=1src=E: rac test rac630 dm.ctl dest=F: rac test
rac630\dmctl.txt；
File path is consistent with the Actual path at place in b > modification dmctl.txt, if RAC data text in target database
Part catalogue is consistent with source database, then does not need to modify；
C > execution is such as issued orders, and modified dmctl.txt is reconverted into dm.ctl:
Dmctlcvt.exe type=2src=F: rac test rac630 dmctl.txt dest=E: rac
test\rac630\dm.ctl；
3 > prepare archive log file:
Using the archive log file of dmrachk tool lookup target copy, (local archive file is remote on source database
Journey archive file, the two select one), BEGIN_LSN value on present node is arranged in BEGIN_LSN.Wherein, BEGIN_LSN can be with
Be considered the backup starting point of archive log file, specific setting content is not construed as limiting, can using backup starting point as
BEGIN_LSN。
For this sentences local archive file, it is as follows to execute order:
Dmrachk arch_path=E: rac test rac630_cfg1 arch_local BEGIN_LSN=LSN_
ARR_FOR_COPY[0]；Output_fil=F: rac test rac630_cfg1 arch_local_out.txt；
Dmrachk arch_path=E: rac test rac630_cfg2 arch_local BEGIN_LSN=LSN_
ARR_FOR_COPY[1]；Output_fil=F: rac test rac630_cfg2 arch_local_out.txt.
The archive log file for needing to copy is listed on implementing result output file arch_local_out.txt.By these
Destination path of the archive log file copy to target database.
It executes in 4 > target database and restores from local archive log:
Off line tool dmrman completion such as can be used, after the completion of recovery, object library can normal use.Execute order such as
Under:
restore database'F:\rac\test\rac630_cfg1\dm.ini'for copy recover；
recover database'F:\rac\test\rac630_cfg1\dm.ini'with archivedir'F:\
Rac test rac630_cfg1 arch_local', ' F: rac test rac630_cfg2 arch_local'until
COPY_LSN_MAX；
recover database'F:\rac\test\rac630_cfg1\dm.ini'update db_magic。
The embodiment of the present invention three provide a kind of database restoring method, obtain first predetermined backup starting point with
Backup end point and the library file and archive log file backed up from source database；It is then based on the storage position of target database
The file path information modified in the library file is set, object library file is obtained；Finally according to the archive log file, target
Library file, backup starting point and Backup end point, carry out the recovery of database.It, can be based on predetermined using the above method
Backup starting point, Backup end point and from source database back up library file and archive log file complete database it is extensive
It is multiple, it avoids because of each node standby Time Inconsistency under RAC environment, the inconsistent technical problem of caused data improves number
The accuracy rate restored according to library.
Further, the library file include data file, control file, the corresponding online log file of each node and/
Or the corresponding configuration file of each node；Correspondingly, the storage location based on target database is modified in the library file
File path information, obtains object library file, comprising:
Target is revised as in the path for controlling data file recorded in file and configuration file and journal file respectively
The corresponding address information of the storage location of database, obtains object library file.
Wherein, particular content included by data file, control file, online log file and configuration file does not limit
It is fixed, it can be determined according to the type of database.Such as, data file can be understood as in database the data in library for storing data
File.Control file can be understood as in database for recording and safeguarding the physical structure of database.Configuration file can be with
It is interpreted as the file of database of record configuration information in database.
In the present embodiment library file may include data file, control file, the corresponding online log file of each node and/
Or the corresponding configuration file of each node.The content that particular content included by library file is backed up when can be according to DB Backup
It determines, is not construed as limiting herein.
It, can be by data file recorded in control file and configuration file when target database carries out database recovery
It is revised as the actual address in target database with the path of journal file, to obtain object library file.
Further, target database is revised as in the path for controlling data file recorded in file and journal file
The corresponding address information of storage location, comprising:
Control file is subjected to clear text format conversion, obtains controlling file in plain text；
It is revised as the storage of target database in the path that the plaintext is controlled to data file and journal file in file
The corresponding address information in position obtains modified plaintext control file.
The modified plaintext control file is subjected to ciphertext format conversion corresponding with clear text format conversion.
It is understood that can be added when control file stores in the database with predetermined cipher mode
It is close, to guarantee the safety of data.Therefore when that will control that path is modified in file, control file first can be subjected to lattice
Formula conversion, is converted to the format that can be read, and then carries out the modification of file path information.
Example IV
Fig. 4 is a kind of structural schematic diagram for DB Backup device that the embodiment of the present invention four provides, and the device is applicable
In back up to database the case where, specifically, which is applicable to carry out online copy to database
The case where backup.Wherein the device can be implemented by software and/or hardware, and be typically integrated on terminal device.
As shown in figure 4, the DB Backup device includes: the first acquisition module 41, library file backup module 42 and second
Obtain module 43；
Wherein, first module 41 is obtained, for determining and recording the backup starting point of each node in source database；
Library file backup module 42, for the corresponding library file of the source database to be backuped to target database；
Second obtains module 43, for determining and recording the Backup end point of each node in the source database, for institute
State the recovery that target database carries out database based on the backup starting point, library file and Backup end point.
In the present embodiment, which passes through the first acquisition module 41 first and determines and records source database
In each node backup starting point；The corresponding library file of the source database is backuped to secondly by library file backup module 42
Target database；The Backup end point of each node in the source database is determined and recorded finally by the second acquisition module 43,
Recovery for the target database based on the backup starting point, library file and Backup end point progress database.
A kind of DB Backup device is present embodiments provided, the accuracy to source database backup is can be improved, avoids
Because of the BACKUP TIME inconsistent technical problem for causing data inconsistent of each node in source database.
Further, first module 41 is obtained, be specifically used for: by the checkpoint log serial number of node each in source database
As backup starting point；
The backup starting point is recorded in the corresponding library file of the source database.
Further, second module 43 is obtained, comprising:
Determination unit, for determining Backup end point, the text according to the corresponding file journalization sequence number of each node
Part log serial number is log serial number when log is stored in journal file completion；
Recording unit, for recording the Backup end point.
Further, it is determined that unit, is specifically used for:
Obtain the file journalization sequence number of each node in database；
Maximum file journalization sequence number is chosen from each file journalization sequence number；
Using the maximum file journalization sequence number as Backup end point.
Further, DB Backup device, further includes:
Archival back-up module, for the Backup end point for determining and recording each node in the source database it
Afterwards, the corresponding archive log file backup of each node of backup condition will be met in source database to the target data
Library.
Further, library text piece optimization includes data file, control file, each node correspondence in library file backup module 42
Online log file and/or the corresponding configuration file of each node.
Database backup method provided by any embodiment of the invention can be performed in above-mentioned DB Backup device, has and holds
The corresponding functional module of row method and beneficial effect.
Embodiment five
Fig. 5 is a kind of structural schematic diagram for database recovery device that the embodiment of the present invention five provides.The device is applicable
In restore to database the case where, wherein the device be can be implemented by software and/or hardware, and be typically integrated in terminal device
On.
As shown in figure 5, the database recovery device includes: that third obtains module 51, modified module 52 and recovery module 53；
Wherein, third obtains module 51, for obtaining predetermined backup starting point and Backup end point and from source
The library file and archive log file of DB Backup；
Modified module 52 modifies the letter of the file path in the library file for the storage location based on target database
Breath, obtains object library file；
Recovery module 53, for according to the archive log file, object library file, backup starting point and Backup end
Point carries out the recovery of database.
In the present embodiment, which obtains module 51 by third first and obtains predetermined backup
Starting point and Backup end point and the library file and archive log file backed up from source database；Then pass through modified module 52
Storage location based on target database modifies the file path information in the library file, obtains object library file；Finally lead to
Over recovery module 53 carries out database according to the archive log file, object library file, backup starting point and Backup end point
Recovery.
A kind of database recovery device is present embodiments provided, it can be based on predetermined backup starting point, backup knot
Beam spot and from source database back up library file and archive log file complete database recovery, avoid under RAC environment because
Each node standby Time Inconsistency, the inconsistent technical problem of caused data, improves the accuracy rate of database recovery.
Further, library file includes data file, control file, the corresponding online log file of each node and/or each
The corresponding configuration file of node；Correspondingly, modified module 52, is specifically used for: will be remembered in control file and configuration file respectively
The corresponding address information of storage location of target database is revised as in the data file of record and the path of journal file, obtains target
Library file.
Database restoring method provided by any embodiment of the invention can be performed in above-mentioned database recovery device, has and holds
The corresponding functional module of row method and beneficial effect.
Embodiment six
Fig. 6 is a kind of structural schematic diagram for terminal device that the embodiment of the present invention six provides, as shown in fig. 6, the present invention is real
The terminal device for applying the offer of example four includes: one or more processors 61 and storage device 62；Processor in the terminal device
61 can be one or more, in Fig. 6 by taking a processor 61 as an example；Storage device 62 is for storing one or more programs；
One or more of programs are executed by one or more of processors 61, so that one or more of processors 61 are realized
Database backup method or database restoring method as described in any one of embodiment of the present invention.
The terminal device can also include: input unit 63 and output device 64.
Processor 61, storage device 62, input unit 63 and output device 64 in terminal device can by bus or
Other modes connect, in Fig. 6 for being connected by bus.
Storage device 62 in the terminal device is used as a kind of computer readable storage medium, can be used for storing one or more
A program, described program can be software program, computer executable program and module, and such as the embodiment of the present invention one is implemented
Corresponding program instruction/the module of two data presented library backup method of example is (for example, in attached DB Backup device shown in Fig. 4
Module, comprising: first obtain module 41, library file backup module 42 and second obtain module 43)；Or such as the embodiment of the present invention
The three corresponding program instruction/modules of database restoring method provided are (for example, in database recovery device described in attached drawing 5
Module, comprising: third obtains module 51, modified module 52 and recovery module 53).Processor 61 is stored in storage dress by operation
Software program, instruction and the module in 62 are set, thereby executing the various function application and data processing of terminal device, i.e., in fact
Database backup method or database restoring method in existing above method embodiment.
Storage device 62 may include storing program area and storage data area, wherein storing program area can storage program area,
Application program needed at least one function；Storage data area, which can be stored, uses created data etc. according to terminal device.
It can also include nonvolatile memory in addition, storage device 62 may include high-speed random access memory, for example, at least one
A disk memory, flush memory device or other non-volatile solid state memory parts.In some instances, storage device 62 can
It further comprise the memory remotely located relative to processor 61, these remote memories can be by network connection to setting
It is standby.The example of above-mentioned network includes but is not limited to internet, intranet, local area network, mobile radio communication and combinations thereof.
Input unit 63 can be used for receiving the number or character information of input, and generate the user setting with terminal device
And the related key signals input of function control.Output device 64 may include that display screen etc. shows equipment.
Also, when one or more included program of above-mentioned terminal device is held by one or more of processors 61
When row, program is proceeded as follows:
Determine and record the backup starting point of each node in source database；
The corresponding library file of the source database is backuped into target database；
The Backup end point of each node in the source database is determined and recorded, so that the target database is based on described
Backup starting point, library file and Backup end point carry out the recovery of database.
Alternatively, when one or more included program of above-mentioned terminal device is held by one or more of processors 61
When row, program is proceeded as follows:
Obtain predetermined backup starting point and Backup end point and the library file backed up from source database and filing
Journal file；
Storage location based on target database modifies the file path information in the library file, obtains target library text
Part；
According to the archive log file, object library file, backup starting point and Backup end point carry out the extensive of database
It is multiple.
Embodiment seven
The embodiment of the present invention seven provides a kind of computer readable storage medium, is stored thereon with computer program, the journey
For executing database backup method when sequence is executed by processor, this method comprises:
Determine and record the backup starting point of each node in source database；
The corresponding library file of the source database is backuped into target database；
The Backup end point of each node in the source database is determined and recorded, so that the target database is based on described
Backup starting point, library file and Backup end point carry out the recovery of database.
Optionally, it can be also used for executing data provided by any embodiment of the invention when which is executed by processor
Library backup method.
Alternatively, the embodiment of the present invention seven provides a kind of computer readable storage medium, it is stored thereon with computer program,
For executing database restoring method when the program is executed by processor, this method comprises:
Obtain predetermined backup starting point and Backup end point and the library file backed up from source database and filing
Journal file；
Storage location based on target database modifies the file path information in the library file, obtains target library text
Part；
According to the archive log file, object library file, backup starting point and Backup end point carry out the extensive of database
It is multiple.
Optionally, it can be also used for executing data provided by any embodiment of the invention when which is executed by processor
Library restoration methods.
The computer storage medium of the embodiment of the present invention, can be using any of one or more computer-readable media
Combination.Computer-readable medium can be computer-readable signal media or computer readable storage medium.It is computer-readable
Storage medium for example may be-but not limited to-the system of electricity, magnetic, optical, electromagnetic, infrared ray or semiconductor, device or
Device, or any above combination.The more specific example (non exhaustive list) of computer readable storage medium includes: tool
There are electrical connection, the portable computer diskette, hard disk, random access memory (Random Access of one or more conducting wires
Memory, RAM), read-only memory (Read Only Memory, ROM), erasable programmable read only memory (Erasable
Programmable Read Only Memory, EPROM), flash memory, optical fiber, portable CD-ROM, light storage device, magnetic storage
Device or above-mentioned any appropriate combination.Computer readable storage medium, which can be, any includes or storage program has
Shape medium, the program can be commanded execution system, device or device use or in connection.
Computer-readable signal media may include in a base band or as carrier wave a part propagate data-signal,
Wherein carry computer-readable program code.The data-signal of this propagation can take various forms, including but unlimited
In: electromagnetic signal, optical signal or above-mentioned any appropriate combination.Computer-readable signal media can also be that computer can
Any computer-readable medium other than storage medium is read, which can send, propagates or transmit and be used for
By the use of instruction execution system, device or device or program in connection.
The program code for including on computer-readable medium can transmit with any suitable medium, including but not limited to:
Wirelessly, electric wire, optical cable, radio frequency (Radio Frequency, RF) etc. or above-mentioned any appropriate combination.
The computer for executing operation of the present invention can be write with one or more programming languages or combinations thereof
Program code, described program design language include object oriented program language-such as Java, Smalltalk, C++,
It further include conventional procedural programming language-such as " C " language or similar programming language.Program code can be with
It fully executes, partly execute on the user computer on the user computer, being executed as an independent software package, portion
Divide and partially executes or executed on a remote computer or server completely on the remote computer on the user computer.?
Be related in the situation of remote computer, remote computer can pass through the network of any kind --- including local area network (LAN) or
Wide area network (WAN) --- it is connected to subscriber computer, or, it may be connected to outer computer (such as utilize Internet service
Provider is connected by internet).
Note that the above is only a better embodiment of the present invention and the applied technical principle.It will be appreciated by those skilled in the art that
The invention is not limited to the specific embodiments described herein, be able to carry out for a person skilled in the art it is various it is apparent variation,
It readjusts and substitutes without departing from protection scope of the present invention.Therefore, although being carried out by above embodiments to the present invention
It is described in further detail, but the present invention is not limited to the above embodiments only, without departing from the inventive concept, also
It may include more other equivalent embodiments, and the scope of the invention is determined by the scope of the appended claims.
Claims (12)
1. a kind of database backup method characterized by comprising
Determine and record the backup starting point of each node in source database；
The corresponding library file of the source database is backuped into target database；
The Backup end point of each node in the source database is determined and recorded, so that the target database is based on the backup
Starting point, library file and Backup end point carry out the recovery of database.
2. the method according to claim 1, wherein the backup for determining and recording each node in source database
Starting point, comprising:
Using the checkpoint log serial number of node each in source database as backup starting point；
The backup starting point is recorded in the corresponding library file of the source database.
3. the method according to claim 1, wherein described determine and record each node in the source database
Backup end point, comprising:
According to the corresponding file journalization sequence number of each node, Backup end point, the file journalization Serial No. day are determined
Will is stored in log serial number when journal file is completed；
Record the Backup end point.
4. according to the method described in claim 3, it is characterized in that, described according to the corresponding file journalization sequence of each node
Number, determine Backup end point, comprising:
Obtain the file journalization sequence number of each node in database；
Maximum file journalization sequence number is chosen from each file journalization sequence number；
Using the maximum file journalization sequence number as Backup end point.
5. according to the method described in claim 1, in the Backup end for determining and recording each node in the source database
After point, further includes:
The corresponding archive log file backup of each node of backup condition will be met in source database to the target data
Library.
6. the method according to claim 1, wherein the library file includes data file, control file, each section
The corresponding online log file of point and/or the corresponding configuration file of each node.
7. a kind of database restoring method characterized by comprising
The library file and archive log for obtaining predetermined backup starting point and Backup end point and being backed up from source database
File；
Storage location based on target database modifies the file path information in the library file, obtains object library file；
According to the archive log file, object library file, backup starting point and Backup end point carry out the recovery of database.
8. the method according to the description of claim 7 is characterized in that the library file includes data file, control file, each section
The corresponding online log file of point and/or the corresponding configuration file of each node；Correspondingly, the storage based on target database
The file path information in the library file is modified in position, obtains object library file, comprising:
Target data is revised as in the path for controlling data file recorded in file and configuration file and journal file respectively
The corresponding address information of the storage location in library, obtains object library file.
9. a kind of DB Backup device characterized by comprising
First obtains module, for determining and recording the backup starting point of each node in source database；
Library file backup module, for the corresponding library file of the source database to be backuped to target database；
Second obtains module, for determining and recording the Backup end point of each node in the source database, for the target
Database carries out the recovery of database based on the backup starting point, library file and Backup end point.
10. a kind of database recovery device characterized by comprising
Third obtain module, for obtain predetermined backup starting point and Backup end point and from source database backup
Library file and archive log file；
Modified module is modified the file path information in the library file for the storage location based on target database, is obtained
Object library file；
Recovery module, for according to the archive log file, object library file, backup starting point and Backup end point to be carried out
The recovery of database.
11. a kind of terminal device characterized by comprising
One or more processors；
Storage device, for storing one or more programs；
When one or more of programs are executed by one or more of processors, so that one or more of processors are real
Database now such as database backup method as claimed in any one of claims 1 to 6 or as described in any in claim 7-8 is extensive
Compound method.
12. a kind of computer readable storage medium, is stored thereon with computer program, which is characterized in that the program is by processor
It realizes when execution such as database backup method as claimed in any one of claims 1 to 6 or as described in any in claim 7-8
Database restoring method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811645760.2A CN109739691A (en) | 2018-12-30 | 2018-12-30 | DB Backup and restoration methods, device, terminal device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811645760.2A CN109739691A (en) | 2018-12-30 | 2018-12-30 | DB Backup and restoration methods, device, terminal device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109739691A true CN109739691A (en) | 2019-05-10 |
Family
ID=66362709
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811645760.2A Pending CN109739691A (en) | 2018-12-30 | 2018-12-30 | DB Backup and restoration methods, device, terminal device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109739691A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110879783A (en) * | 2019-11-21 | 2020-03-13 | 上海达梦数据库有限公司 | Program testing method, device, equipment and storage medium |
| CN111078719A (en) * | 2019-12-31 | 2020-04-28 | 北京互金新融科技有限公司 | Data recovery method and device, storage medium and processor |
| CN112380058A (en) * | 2020-11-12 | 2021-02-19 | 上海上讯信息技术股份有限公司 | File recovery method and equipment |
| CN112463457A (en) * | 2020-12-10 | 2021-03-09 | 上海爱数信息技术股份有限公司 | Data protection method, device, medium and system for guaranteeing application consistency |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101136783A (en) * | 2007-10-15 | 2008-03-05 | 中兴通讯股份有限公司 | Backup, recovery method and apparatus for network management system to configure data |
| CN101324857A (en) * | 2007-06-11 | 2008-12-17 | 英华达（上海）科技有限公司 | Method of data backup and reduction |
| CN108416040A (en) * | 2018-03-14 | 2018-08-17 | 上海达梦数据库有限公司 | A kind of database recovering method, device, terminal device and storage medium |
| CN108664359A (en) * | 2018-05-23 | 2018-10-16 | 上海达梦数据库有限公司 | A kind of database restoring method, device, equipment and storage medium |
| CN108920522A (en) * | 2018-06-04 | 2018-11-30 | 上海点融信息科技有限责任公司 | Data processing method, system and computer readable storage medium for database |
-
2018
- 2018-12-30 CN CN201811645760.2A patent/CN109739691A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101324857A (en) * | 2007-06-11 | 2008-12-17 | 英华达（上海）科技有限公司 | Method of data backup and reduction |
| CN101136783A (en) * | 2007-10-15 | 2008-03-05 | 中兴通讯股份有限公司 | Backup, recovery method and apparatus for network management system to configure data |
| CN108416040A (en) * | 2018-03-14 | 2018-08-17 | 上海达梦数据库有限公司 | A kind of database recovering method, device, terminal device and storage medium |
| CN108664359A (en) * | 2018-05-23 | 2018-10-16 | 上海达梦数据库有限公司 | A kind of database restoring method, device, equipment and storage medium |
| CN108920522A (en) * | 2018-06-04 | 2018-11-30 | 上海点融信息科技有限责任公司 | Data processing method, system and computer readable storage medium for database |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110879783A (en) * | 2019-11-21 | 2020-03-13 | 上海达梦数据库有限公司 | Program testing method, device, equipment and storage medium |
| CN110879783B (en) * | 2019-11-21 | 2023-09-08 | 上海达梦数据库有限公司 | Program testing method, device, equipment and storage medium |
| CN111078719A (en) * | 2019-12-31 | 2020-04-28 | 北京互金新融科技有限公司 | Data recovery method and device, storage medium and processor |
| CN112380058A (en) * | 2020-11-12 | 2021-02-19 | 上海上讯信息技术股份有限公司 | File recovery method and equipment |
| CN112463457A (en) * | 2020-12-10 | 2021-03-09 | 上海爱数信息技术股份有限公司 | Data protection method, device, medium and system for guaranteeing application consistency |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11669414B2 (en) | External dynamic virtual machine synchronization | |
| US20200364194A1 (en) | Migration of a database management system to cloud storage | |
| US10169163B2 (en) | Managing backup operations from a client system to a primary server and secondary server | |
| US8090917B2 (en) | Managing storage and migration of backup data | |
| US8438136B2 (en) | Backup catalog recovery from replicated data | |
| JP5646639B2 (en) | Backup using metadata virtual hard drive and differential virtual hard drive | |
| CN109739691A (en) | DB Backup and restoration methods, device, terminal device and storage medium | |
| US20180225177A1 (en) | Migrating content and metadata from a backup system | |
| US20180285202A1 (en) | External fallback system for local computing systems | |
| US9348827B1 (en) | File-based snapshots for block-based backups | |
| US20160266980A1 (en) | Collaborative restore in a networked storage system | |
| CN104216793B (en) | Application Backup, the method and apparatus recovered | |
| US9275060B1 (en) | Method and system for using high availability attributes to define data protection plans | |
| KR100961739B1 (en) | Maintaining consistency for remote copy using virtualization | |
| US10409691B1 (en) | Linking backup files based on data partitions | |
| CN107046811A (en) | One introduces a collection storage device sends the clone file of source file and source file to the method, source storage device and backup storage device of backup storage device | |
| US9146816B2 (en) | Managing system image backup | |
| US20200081629A1 (en) | Performing a recovery copy command to restore a safeguarded copy backup to a production volume | |
| US8285680B2 (en) | Individual object restore | |
| US10387262B1 (en) | Federated restore of single instance databases and availability group database replicas | |
| JP2007323657A (en) | Method and system for storing transient state information, and computer program | |
| US9858209B1 (en) | Method and apparatus for restoring de-duplicated data | |
| US11099942B2 (en) | Archival to cloud storage while performing remote backup of data | |
| CN115955488A (en) | Distributed storage copy cross-computer room placement method and device based on copy redundancy | |
| US11262934B2 (en) | Deletion of stored data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190510 |
|
| RJ01 | Rejection of invention patent application after publication |