CN114153660A - Database backup method, device, server and medium - Google Patents
Database backup method, device, server and medium Download PDFInfo
- Publication number
- CN114153660A CN114153660A CN202111473495.6A CN202111473495A CN114153660A CN 114153660 A CN114153660 A CN 114153660A CN 202111473495 A CN202111473495 A CN 202111473495A CN 114153660 A CN114153660 A CN 114153660A
- Authority
- CN
- China
- Prior art keywords
- backup
- recovery
- task
- resource instance
- request
- 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
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000011084 recovery Methods 0.000 claims abstract description 376
- 230000000977 initiatory effect Effects 0.000 claims abstract description 76
- 238000003860 storage Methods 0.000 claims abstract description 24
- 230000004044 response Effects 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 2
- 238000004519 manufacturing process Methods 0.000 abstract description 11
- 238000005516 engineering process Methods 0.000 abstract description 4
- 230000007774 longterm Effects 0.000 abstract description 4
- 230000014759 maintenance of location Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 4
- 238000013500 data storage Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1435—Saving, restoring, recovering or retrying at system level using file system or storage system metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The embodiment of the invention discloses a database backup method, a database backup device, a server and a medium, and relates to a database technology. The method comprises the following steps: responding to the initiated recovery request to generate a recovery task, and calling a recovery host according to the recovery task to recover the backed-up resource instance corresponding to the initiated recovery request to obtain a recovered resource instance; responding to the request for initiating the grid-cut backup to generate a grid-cut backup task, and calling a recovery host according to the grid-cut backup task to perform grid-cut backup on the recovered resource instance to obtain a resource instance file; and determining a backup strategy according to the recovery host and the resource instance file, and backing up the resource instance file based on the backup strategy. By executing the embodiment of the invention, the backup of the database file is completed on the basis of not influencing the performance of the production server, the problem that the data recovery result depends on an operating system and a database version is avoided, and the requirement of long-term storage of the database is met.
Description
Technical Field
Embodiments of the present invention relate to database technologies, and in particular, to a database backup method, apparatus, server, and medium.
Background
With the progress of science and technology and the rapid development of information technology, the importance of data security becomes more and more obvious. However, the importance of data backup, an important aspect of data security, is often ignored by people. Whenever data transmission, data storage and data exchange occur, data failure may occur. At this time, if data backup and data recovery means and measures are not taken, data loss may result. Sometimes the resulting loss is not compensated and measured.
At present, database backup usually adopts a hot backup mode, namely, backup is carried out in the normal operation process of a database server. The use of hot backups may lead to problems affecting data server performance. In addition, when the data backed up by the hot backup mode is restored, the restoration result depends on the version of the operating system and the version of the database of the restoration host. Different operating system versions and database versions all affect the final recovery result, so that the finally recovered data has the situations of incapability of being started from a database, incapability of being compatible with the versions and the like.
Disclosure of Invention
Embodiments of the present invention provide a database backup method, apparatus, server, and medium, which can avoid the problem that a hot backup method is used to backup a database to affect the performance of a production server, and a data recovery result depends on an operating system and a database version.
In a first aspect, an embodiment of the present invention provides a database backup method, including:
responding to a recovery request to generate a recovery task, and calling a recovery host to recover a backed-up resource instance corresponding to the recovery request according to the recovery task to obtain a recovered resource instance;
responding to a request for initiating a grid-cut backup to generate a grid-cut backup task, and calling the recovery host to perform grid-cut backup on the recovered resource instance according to the grid-cut backup task to obtain a resource instance file, wherein the request for initiating the grid-cut backup is used for requesting to export the recovered resource instance into the file;
and determining a backup strategy according to the recovery host and the resource instance file, and backing up the resource instance file based on the backup strategy.
In a second aspect, an embodiment of the present invention further provides a database backup apparatus, where the apparatus includes:
the resource recovery module is used for responding to a recovery request and generating a recovery task, and calling a recovery host according to the recovery task to recover a backed-up resource instance corresponding to the recovery request to obtain a recovered resource instance;
the grid-cut backup module is used for responding to a grid-cut backup initiating request to generate a grid-cut backup task, calling the recovery host to perform grid-cut backup on the recovered resource instance according to the grid-cut backup task to obtain a resource instance file, wherein the grid-cut backup initiating request is used for requesting to export the recovered resource instance to the file;
and the file backup module is used for determining a backup strategy according to the recovery host and the resource instance file and backing up the resource instance file based on the backup strategy.
In a third aspect, an embodiment of the present invention further provides a server, where the server includes:
one or more processors;
a memory for storing one or more computer programs,
when executed by the one or more processors, cause the one or more processors to implement a database backup method as in any embodiment of the invention.
In a fourth aspect, embodiments of the present invention further provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are used to perform a database backup method according to any of the embodiments of the present invention.
The embodiment of the invention provides a database backup method, a database backup device, a database backup server and a database backup medium, wherein a backup resource instance is recovered by calling a recovery host to obtain a recovered resource instance; and performing lattice-breaking backup on the recovered resource instance to obtain a resource instance file, determining a backup strategy according to the recovery host and the resource instance file, and backing up the resource instance file based on the backup strategy, so that the backup of the database file is completed on the basis of not influencing the performance of the production server, the problem that the data recovery result depends on an operating system and a database version is avoided, and the requirement of long-term storage of the database is met.
Drawings
Fig. 1 is a flowchart of a database backup method according to an embodiment of the present invention;
FIG. 2 is a flow chart of another database backup method according to an embodiment of the present invention;
FIG. 3 is a flowchart of another database backup method according to an embodiment of the present invention;
FIG. 4 is a flowchart of another database backup method according to an embodiment of the present invention;
FIG. 5 is a block diagram illustrating the results of a database backup device according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Fig. 1 is a flowchart of a database backup method according to an embodiment of the present invention, which is applicable to a case where a database is subjected to a cross-grid backup to store the database for a long time. The method may be performed by a database backup device, which may be implemented by software and/or hardware, and is typically deployed in a server.
It should be noted that the cross-grid backup is a logical backup manner, that is, exporting data in the database to a file by using a data pump (DATAPUMP) or an exp command, and backing up and saving the data in the form of a file. By adopting a grid-cut backup mode, the resource instance in the database is backed up in the form of a database file and is irrelevant to the database version or the operating system version, the defect that hot backup depends on the database version or the operating system is overcome, and the condition that finally recovered data cannot be stored or cannot be compatible with the version due to the influence of different operating system versions and database versions on the recovery result is avoided.
As shown in fig. 1, the method includes:
Wherein the initiating recovery request is a request sent by the front-end server to initiate a recovery operation of the backed-up resource instance. It should be noted that the resource instance may be a database resource and an instance, the resource is data, and the instance is composed of a series of background processes and a memory structure. Specifically, a user initiates a recovery request through front-end page configuration, and a front-end server submits the initiation recovery request to the unified backup recovery system UBRS through a web interface. For example, the web interface definition involved in initiating the recovery request includes the request method, request route, and request body. Wherein the request method may be a submit POST method. POST denotes submitting data to be processed to a server. Request routing may include resource type, resource instance identification, recovery, and job, among other things. The resource types comprise oracle, sql server and the like. The request body comprises a recovery data retention period and a recovery time point, and also defines the data format of the recovery data retention period and the recovery time point. For example, the format of the recovery time point may be 2021-09-0108: 00: 00.
The UBRS is an application program configured in the server for managing, scheduling, and controlling the computing resources in the server cluster. In embodiments of the present invention, the computing resource may be a recovery host. The recovery host is a host with backup and recovery software deployed in the cloud computing platform. Specifically, the recovery host is installed with a client, and the client primary key and an application primary key of the UBRS realize information interaction through an RPC (Remote Procedure Call Protocol) Protocol. And when the UBRS executes the recovery task, the recovery host is called by the RPC protocol to recover the backed-up data.
In the embodiment of the invention, the recovery task is a task for initiating the recovery host to recover the backed-up resource instance. It should be noted that the backed-up resource instance may be a resource instance that is backed up during the operation of the database server, and the backed-up resource instance exists on the recovery host. In order to reduce the influence on a production database host and a network when data is exported, the embodiment of the invention restores a backed-up resource instance needing to be stored for a long time to the current time point on a restoring host to obtain the restored resource instance, and then carries out subsequent backup operation on the restored resource instance through the restoring host. Wherein the production database is a database server in the user use environment.
It should be noted that, in the recovery process of initiating the resource instance backed up on the recovery host, the UBRS receives the request for initiating the recovery through the web interface, queries the recovery task table according to the resource instance identifier in the request for initiating the recovery, and detects whether a task conflict exists under the same resource instance according to the query result.
For example, the UBRS analyzes and initiates a recovery request to obtain a resource instance identifier, queries a recovery task table according to the resource instance identifier, and determines whether a corresponding resource instance is in operation or a completed recovery task according to a query result, thereby determining whether the resource instance is recovering or has completed recovery and is not cleaned. And if the resource instance is recovering or the resource instance is completely recovered and is not cleaned, determining that task conflicts exist under the same resource instance, and giving up the response to initiate the recovery request. And if the task conflict does not exist under the same resource instance, calling a recovery host through an RPC protocol to recover the resource instance which is backed up and corresponds to the resource instance identifier transmitted by the interface.
And step 120, responding to the request for initiating the grid-cut backup to generate a grid-cut backup task, and calling the recovery host to perform grid-cut backup on the recovered resource instance according to the grid-cut backup task to obtain a resource instance file.
Wherein the initiate a cross-grid backup request is a request sent by a front-end server to initiate export of a restored resource instance to a file. The ungated backup may be implemented using a data pump (DATAPUMP) or exp command to save the restored resource instance in the form of a file.
In the embodiment of the invention, the step of initiating the grid-cut backup request is to request for carrying out database grid-cut backup on the resource instances which are recovered on the recovery host, so as to export the data, the instances and the like of the recovered resource instances into a file, and store the recovered resource instances in the form of the file.
Specifically, a user initiates a cross-check backup request through front-end page configuration, and a front-end server submits the request for initiating the cross-check backup to the unified backup and recovery system UBRS through a web interface. For example, the web interface definition involved in initiating the cross-grid backup request includes a request method, a request route, and a request body. Wherein the request method may be a submit POST method. Request routing may include resource type, cut, backup, and job content. The resource types may include oracle, sql server, and the like. The request body comprises a recovery task identifier, a retention period of the backup data, a storage unit name of the backup data and a volume pool name, and also defines data formats of the recovery task identifier, the retention period of the backup data, the storage unit name of the backup data and the volume pool name.
In the embodiment of the invention, the grid-cut backup task is a task of initiating the recovery host to export the resources, the instances and the like in the recovered resource instances to the file. It should be noted that the restored resource instance may be database data obtained by restoring the backed-up resource instance that needs to be saved for a long time to the current time point by the restoration host. The resource instance file is the text that holds the data and instances of the restored resource instance.
It should be noted that, in the process of the ungated backup of the restored resource instance, the UBRS receives the request for initiating the ungated backup through the web interface. Inquiring a recovery task table according to a recovery task identifier in the request for initiating the lattice breaking backup to obtain a task state corresponding to the recovery task; if the task state does not meet the preset first condition, inquiring a dump backup task table according to the recovery task identifier, and acquiring a backup identifier and a backup state identifier corresponding to the recovery task; and when the backup identification and the backup state identification do not meet the preset second condition, executing the step of generating the lattice-breaking backup task according to the request for initiating the lattice-breaking backup.
For example, the analysis initiates the lattice-breaking backup request to obtain a recovery task identifier, a task state field of a recovery task table is inquired according to the recovery task identifier, and whether the recovery task exists or is running is judged according to the inquiry result. If yes, throwing an exception; otherwise, inquiring the is _ dump and the dump _ status fields of the recovery task in the dump backup task table, and determining whether the resource instance corresponding to the recovery task is successfully subjected to the grid-breaking backup according to the inquiry result. And if the resource instance corresponding to the recovery task is recovered and the cell-out backup is not successfully carried out, carrying out the cell-out backup on the resource instance. The recovery host corresponding to the recovery task can be called through an RPC protocol, and the recovered resource instance corresponding to the recovery task on the local computer is exported to a file to obtain a resource instance file.
The backup strategy is a strategy for backing up files, and specifically comprises backup initiating time, backup storage positions, storage rules, paths, storage time and the like. The backup policy may be stored through a backup policy table, in which the backup policy is stored in association with the recovery host name and the resource instance file name.
It should be noted that, when the backup policy table does not have the backup policy corresponding to the recovery host and the resource instance file, a new backup policy needs to be created for the resource instance file, and then the resource instance file is backed up based on the new backup policy. For example, the storage rules, the saving time, and the like may be determined according to the backup value of the resource instance file. The backup initiation time, the backup storage position, the path and the like of the resource instance file can be determined according to the idle resources of the recovery host.
Wherein the backup value is used to represent the importance of the resource instance. For example, the backup value of the resource instance can be calculated according to preset scoring rules by using factors such as data generation time, the state of the service to which the data belongs, the data level, and user viewing conditions.
Illustratively, the backup policy table is queried according to the recovery host name and the resource instance file name, whether a corresponding target backup policy exists is judged according to the query result, and if yes, the resource instance file is subjected to file backup through the recovery host based on the target backup policy. And if the corresponding target backup strategy does not exist, creating a backup strategy for the resource instance file according to the backup value of the resource instance file and the idle resource of the recovery host, updating the backup strategy id of the current dump backup task in the dump backup task table to the strategy id of the newly created backup strategy, and performing file backup on the resource instance file through the recovery host based on the newly created backup strategy. And updating the backup task id of the current dump backup task in the dump backup task table by the UBRS based on the file backup task id synchronized by the recovery host. Optionally, after the resource instance file is successfully backed up, the recovery host is called by an RPC protocol to remove the recovered resource instance of which the backup is completed, that is, to remove the resource instance recovered on the recovery host.
According to the technical scheme of the embodiment, the backed-up resource instance is restored by calling the restoration host to obtain the restored resource instance; and performing lattice-breaking backup on the recovered resource instance to obtain a resource instance file, determining a backup strategy according to the recovery host and the resource instance file, and backing up the resource instance file based on the backup strategy, so that the backup of the database file is completed on the basis of not influencing the performance of the production server, the problem that the data recovery result depends on an operating system and a database version is avoided, and the requirement of long-term storage of the database is met.
On the basis of the technical scheme, the method further limits that the backup resource instance corresponding to the initiated recovery request is recovered by calling the recovery host in response to the initiated recovery request. Fig. 2 is a flowchart of another database backup method according to an embodiment of the present invention. As shown in fig. 2:
Illustratively, when receiving the initiating recovery request, the UBRS queries the recovery task table according to the resource _ id in the initiating recovery request to check task conflicts under the same resource instance. For example, the status field of the resource instance in the recovery task table is queried according to the resource _ id in the initiated recovery request, and whether the corresponding resource instance is undergoing recovery or has completed recovery and is not cleaned is determined according to the query result.
Illustratively, when there is no task conflict, a new recovery task is added in the recovery task table. The resource instance identification (resource _ id), recovery time point (unity _ time) and recovery data retention period (retention) field contents in the content of the initiation recovery request are obtained. And querying the database instance table, the backup task table and/or the backup domain table to obtain relevant field information of a backup host (nbu _ master), a backup client (nbu _ client) and the like corresponding to the resource instance. And updating corresponding fields of newly added recovery tasks in the recovery task list according to relevant field information such as resource instance identification, recovery time points, recovery data retention periods, backup hosts, backup clients and the like. And inserting the updated recovery task into a recovery task queue, and updating the state field of the recovery task in the recovery task table into queue.
And 204, for the target recovery host with the idle resources, selecting one recovery task which meets the processing capacity of the target recovery host as a current recovery task according to the task sequence in the recovery task queue, and inquiring a database instance table according to a resource instance corresponding to the current recovery task to obtain database rule information.
Illustratively, the recovery host is targeted when there are free resources on the recovery host. According to the task sequence in the recovery task queue, selecting the recovery host identifier in the recovery task as the target recovery host, and selecting one of the recovery hosts which meets the processing capacity of the target recovery host as the current recovery task, and then initiating asynchronous recovery. The processing capability of the target recovery host may be satisfied, for example, that the computing resources of the target recovery host are sufficient to process the recovery task, or that the free resources of the target recovery host are sufficient to store the recovered resource instance. In the asynchronous recovery process, a database instance table is inquired according to a resource instance corresponding to the current recovery task, and database rule information required by recovery is obtained.
Illustratively, after database rule information required for recovery is queried, a state field of a current recovery task is updated to be in operation, a start time field (start _ time) is updated to be current time, a target recovery host corresponding to the current recovery task is called through an RPC protocol, and the current recovery task is operated based on the database rule information to recover a backed-up resource instance corresponding to an initiated recovery request to obtain a recovered resource instance. And acquiring the size and the state code of the recovered resource reported by the recovery host after the recovery is finished. And updating field information of the current recovery task, such as the state, the state code, the end time, the failure time, the resource size and the like in the recovery task table. And updating the size of the residual space of the target recovery host in the recovery host table based on the size of the recovered resource.
And 208, throwing the exception, and giving up responding to the initiated recovery request.
According to the technical scheme of the embodiment, the backed-up resource instance needing to be stored for a long time is restored to the current time point through the restoration host, and then the restored resource instance is subjected to cross-grid backup, so that backup on the production database is avoided, and the database backup is completed while the performance of the production database is not influenced.
On the basis of the technical scheme, the method calls the recovery host to perform the grid-cut backup on the recovered resource instance in response to the request for initiating the grid-cut backup. Fig. 3 is a flowchart of another database backup method according to an embodiment of the present invention. As shown in fig. 3:
Illustratively, the UBRS receives the request for initiating the ungated backup through the web interface, and parses the request for initiating the ungated backup to obtain the recovery task identifier, i.e., restore _ jobid. And querying the state field of the recovery task in the recovery task table according to the restore _ jobid to obtain the task state corresponding to the recovery task.
And 303, judging whether the task state meets a preset first condition, if not, executing a step 304, otherwise, executing a step 310.
The preset first condition is a condition for specifying the resource instances which cannot be subjected to the grid-cut backup based on the task state. For example, the preset first condition may be that a recovery task exists or is running. And if the task state meets a preset first condition, determining that the resource instance corresponding to the recovery task does not meet the requirements of the grid-cut backup. Otherwise, judging the recovery task based on a preset second condition, and determining whether the resource instance recovered by the recovery task can be subjected to the failure backup according to a judgment result.
Illustratively, for a recovery task corresponding to the recovery task identifier, whether the recovery task exists or is still running is detected according to the task state.
And step 304, acquiring the recovery task backup identification and the backup state identification.
And 305, judging whether the backup identifier and the backup state identifier meet a preset second condition, if not, executing step 306, otherwise, executing step 310.
The preset second condition is a condition for screening the resource instances which cannot be subjected to the grid-cut backup based on the backup identifier and the backup state identifier. For example, the preset second condition may be that the is _ dump field of the recovery task is true and the dump _ status is successful, which indicates that the resource instance corresponding to the recovery task has been subjected to the lattice-removal backup and the lattice-removal backup is successful. And if the backup identifier and the backup state identifier both meet the preset second condition, determining that the resource instance corresponding to the recovery task does not meet the requirements of the grid-cut backup. Otherwise, step 306 is performed.
For example, for a recovery task that meets a preset first condition, if one of the backup identifier and the backup state does not meet a preset second condition, it is determined that the resource instance corresponding to the recovery task has completed recovery but failed to perform the cross-grid backup. The UBRS performs the cut-back only on resource instances that have completed the restore and failed the cut-back.
Illustratively, if the resource instance corresponding to the recovery task in the request for initiating the grid-cut backup is completely recovered and the grid-cut backup is not successfully performed, a grid-cut backup task is created in a grid-cut backup task table, and each field of the grid-cut backup task is null or a default value. And updating the corresponding field of the newly-built cell-out backup task according to the content of the request for initiating the cell-out backup, and inserting the updated cell-out backup task into a backup task queue. Specifically, the restore _ jobid field of the newly created backout task is updated to the recovery task identifier transmitted in the request for initiating the backout. And inserting the updated lattice-breaking backup task into a backup task queue. At the same time, it is true to update the is _ dump field of the corresponding recovery task.
And 307, determining the recovery host with the idle resources as the current recovery host, and selecting a cell-out backup task which meets the processing capacity of the current recovery host as the current cell-out backup task according to the sequence of the tasks in the backup task queue.
It should be noted that, in the process of executing the backout-of-grid backup of the resource instance, the role of the recovery host is changed to the backup host, which is used for performing the backout-of-grid backup on the resource instance that has been recovered on the local computer. The processing capability of the current recovery host may be satisfied that the computing resources of the current recovery host are sufficient to handle the ungated backup task, or that the free resources of the current recovery host are sufficient to store the dump resource instance file, etc.
Illustratively, when a recovery host (which may also be referred to as a backup host at this time) has free resources, according to the order of tasks in the recovery task queue, a recovery host whose identification is free is selected, and one of the cut-off backup tasks that satisfies the processing capability of the recovery host is used as the current cut-off backup task, and then an asynchronous cut-off backup is initiated. And in the asynchronous grid-breaking backup process, updating the task state of the current grid-breaking backup task to be in operation.
And 308, calling the current recovery host to run the current grid-cut backup task so as to perform grid-cut backup on the recovered resource instance on the current recovery host to obtain a resource instance file.
Illustratively, the recovery host corresponding to the current cut-off backup task is taken as the current recovery host. The recovery host corresponding to the recovery task is the recovery host executing the recovery task. And calling the current recovery host to export the recovered resource instance to a file through an RPC protocol, thereby realizing dump backup of the resource instance and obtaining the resource instance file. And after the recovery host executes the run-out backup, reporting the storage path and the file size of the resource instance file to the UBRS. And updating the dump _ dir field of the current cut-off backup task by the UBRS based on the storage path, and updating the dump _ size field according to the file size of the resource instance file obtained by the backup of the current cut-off backup task.
It should be noted that the resources of the restore host support the asynchronous execution of multiple restore tasks or multiple backup tasks.
Illustratively, the backup policy table is queried based on the recovery host name and the resource instance file name to detect whether a corresponding backup policy exists. And if so, taking the inquired backup strategy as the backup strategy of the resource instance file. If not, a backup strategy is created based on the storage path of the resource file, the file size, and the free resources, the remaining space, etc. of the recovery host.
According to the technical scheme of the embodiment, the backed-up resource instances needing to be stored for a long time are restored to the current time point through the recovery host, and then the restored resource instances are exported to the file, so that the problem that the performance of the production host is affected due to the fact that the resource instances of the production environment are directly backed up is solved; in addition, the file backup mode is adopted, so that the situation that the recovered data can not be brought out of the database or can not be compatible with the version and the like due to the strong dependence of the resource instance on the operating system and the database version of the recovery host is avoided.
Fig. 4 is a flowchart of another database backup method according to an embodiment of the present invention. As shown in FIG. 4, the database backup method includes two processes of initiating 410 a restore of a resource instance and 420, and initiating a grid-cut backup of the restored resource instance. Wherein, step 410, initiating a recovery flow of the resource instance comprises:
Step 412, determining whether a task conflict exists, if yes, executing step 417, otherwise, executing step 413.
And step 413, adding a recovery task.
And 414, calling the recovery host by an RPC protocol to execute asynchronous recovery.
And 415, receiving the recovered resource size and the status code sent by the recovery host after the recovery is finished, and updating the task status based on the status code.
Specifically, the front-end server sends a request to initiate a recovery task to the UBRS through the web interface. The UBRS receives the request for initiating the recovery task, firstly, a recovery task table is inquired according to the resource _ id, whether the resource instance is recovering or not is judged, or the recovery is completed and the resource instance is not cleaned, so that the task conflict under the same resource instance is checked. If no task conflict exists, a new recovery task is added in the recovery task list, according to the content of the request for initiating the recovery task, the related field information of the resource instance identifier, the recovery time point, the recovery data retention period, the backup host, the backup client and the like of the new recovery task is updated, the task state of the new recovery task is updated to be in queue, and then asynchronous recovery is initiated. In the asynchronous recovery process, according to different resource types, a database instance table is inquired to obtain database rule information required by recovery of different resources, and the task state of a recovery task is updated to be in operation and the value of the starting time field is updated to be at the moment. And calling the recovery host by the RPC to execute asynchronous recovery, and acquiring the size of the recovered resource and the state code after the asynchronous recovery is finished. And finally, updating information such as the task state, the task state identification, the ending time, the failure time, the resource size and the like of the recovery task, and updating the space size of the recovery host. If the task conflict exists, the exception is thrown out, and the response to the request for initiating the recovery task is abandoned.
And, step 420, initiating a cut-out backup process of the restored resource instance includes:
step 421, receiving an initiate cross-grid backup request.
Step 423, determining whether the resource instance recovered by the recovery task has successfully performed the cross-grid backup, if so, performing step 428, otherwise, performing step 424.
Step 426, the recovery host is called by the RPC protocol to perform asynchronous cross-grid backup.
Specifically, the front-end server sends a request for initiating a cut-off backup task to the UBRS through the web interface. The UBRS receives a request for initiating a grid-cut backup task, checks whether the recovery task exists or is still in operation according to the transmitted restore _ job _ id, then checks the is _ dump and the dump _ status of the recovery task to judge whether the dump backup is already done and the dump is successful, and the UBRS only carries out the dump backup on the resource instances which are already restored and are not successfully carried out with the dump backup.
When the backup is started, a new grid-cut backup task is added in a grid-cut backup task table, the restore _ jobid attribute of the new grid-cut backup task is the recovery task identification of an incoming interface, the is _ dump attribute of the corresponding recovery task is updated to true, and then the grid-cut backup is carried out asynchronously. In asynchronous operation, marking the task state of the lattice-cut backup task as running, and calling a recovery host computer to execute dump operation on the recovered resource instance through an RPC protocol. And acquiring the storage position and the size of the resource instance file sent by the recovery host after the cut-off backup is finished, and updating the dump _ dir and the dump _ size attributes of the dump backup task.
And then judging whether a strategy for the grid-cut backup is established in a backup strategy table or not according to the recovery host name and the resource instance file name needing dump, if not, newly establishing a grid-cut backup strategy, updating the backup strategy identifier of the grid-cut backup task to be a corresponding strategy id, and then initiating file backup to backup the grid-cut resource instance file, and updating the backup task identifier of the grid-cut backup task to be a file backup task id. After the backup is finished, the recovery host is called through an RPC protocol to clean the files of which the dump backup is finished, namely, the resource instances recovered on the recovery host are recovered. Finally, the status code of the dump backup task is updated, the task status of the ump backup task is set to be completed, and the dump _ status of the recovery task is updated to be successful or failed.
Fig. 5 is a block diagram illustrating results of a database backup apparatus according to an embodiment of the present invention. The apparatus may be implemented by software and/or hardware and is typically configured in a server. The device realizes the lattice-breaking backup of the database to store the database for a long time by executing the database backup method provided by any embodiment of the invention. As shown in fig. 5, the apparatus includes: a resource restore module 510, a cut-out backup module 520, and a file backup module 530.
The resource recovery module 510 is configured to generate a recovery task in response to the initiation of the recovery request, and invoke a recovery host to recover the backed-up resource instance corresponding to the initiation of the recovery request according to the recovery task, so as to obtain a recovered resource instance;
a lattice-breaking backup module 520, configured to generate a lattice-breaking backup task in response to initiating a lattice-breaking backup request, and invoke the recovery host to perform lattice-breaking backup on the recovered resource instance according to the lattice-breaking backup task to obtain a resource instance file, where the initiating lattice-breaking backup request is used to request that the recovered resource instance is exported to the file;
the file backup module 530 is configured to determine a backup policy according to the recovery host and the resource instance file, and backup the resource instance file based on the backup policy.
The embodiment of the invention provides a database backup device, which is used for recovering a backed-up resource instance by calling a recovery host to obtain a recovered resource instance; and performing lattice-breaking backup on the restored resource instance to obtain a resource instance file, determining a backup strategy according to the restoration host and the resource instance file, and backing up the resource instance file based on the backup strategy, so that the backup of the database file is completed on the basis of not influencing the performance of the production server, the problem that the data restoration result depends on an operating system and a database version is avoided, and the requirement of long-term storage of the database is met.
Further, the apparatus further comprises:
and the conflict detection module is used for acquiring the initiated recovery request before responding to the initiated recovery request to generate the recovery task, inquiring the recovery task table according to the resource instance identifier in the initiated recovery request, and detecting whether the task conflict exists under the same resource instance according to the inquiry result.
Further, the resource recovery module 510 is specifically configured to:
creating a recovery task in a recovery task table, updating a corresponding field of the recovery task according to the content of the initiated recovery request, and inserting the updated recovery task into a recovery task queue;
for a target recovery host with idle resources, selecting a recovery task which meets the processing capacity of the target recovery host as a current recovery task according to the task sequence in the recovery task queue, and querying a database instance table according to a resource instance corresponding to the current recovery task to obtain database rule information;
and calling the target recovery host, and running the current recovery task based on the database rule information to recover the backed-up resource instance corresponding to the initiated recovery request to obtain a recovered resource instance.
Further, the apparatus further comprises:
the condition judgment module is used for acquiring the request for initiating the cell-out backup before responding to the request for initiating the cell-out backup and generating the cell-out backup task, and inquiring a recovery task table according to a recovery task identifier in the request for initiating the cell-out backup to obtain a task state corresponding to the recovery task;
if the task state does not meet a preset first condition, acquiring a recovery task backup identifier and a backup state identifier;
and if the backup identification and the backup state identification do not meet the preset second condition, executing a step of responding to the request for initiating the grid-cut backup to generate a grid-cut backup task.
Further, the lattice-cut backup module 520 is specifically configured to:
creating a lattice-breaking backup task in a lattice-breaking backup task table, updating a corresponding field of the lattice-breaking backup task according to the content of the lattice-breaking backup request, and inserting the updated lattice-breaking backup task into a backup task queue;
determining a recovery host with idle resources as a current recovery host, and selecting a grid-cut backup task which accords with the processing capacity of the current recovery host as a current grid-cut backup task according to the sequence of tasks in the backup task queue;
and calling the current recovery host to run the current grid-cut backup task so as to carry out grid-cut backup on the recovered resource instance on the current recovery host and obtain a resource instance file.
Optionally, the file backup module 530 is specifically configured to:
inquiring a preset backup strategy table according to the recovery host name and the resource instance file name, and determining whether a corresponding target backup strategy exists according to an inquiry result;
if yes, backing up the resource instance file based on the target backup strategy;
otherwise, creating a backup strategy for the resource instance file according to the backup value of the resource instance file and the idle resource of the recovery host, and backing up the resource instance file based on the newly created backup strategy.
Further, the apparatus further comprises:
and the resource clearing module is used for calling the recovery host to clear the recovered resource instances after the backup of the resource instance files is successful after the resource instance files are backed up based on the backup strategy.
The database backup device provided by the embodiment of the invention can execute the database backup method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Fig. 6 is a schematic structural diagram of a server according to an embodiment of the present invention, and as shown in fig. 6, the server includes a processor 60 and a memory 61; the number of the processors 60 in the server may be one or more, and one processor 60 is taken as an example in fig. 6; the processor 60 and the memory 61 in the server may be connected by a bus or other means, as exemplified by the bus connection in fig. 6.
The memory 61 is a computer-readable storage medium for storing software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the database backup method in the embodiment of the present invention (for example, the resource recovery module 510, the lattice-breaking backup module 520, and the file backup module 530 in the database backup apparatus). The processor 50 executes various functional applications of the server and data processing by executing software programs, instructions, and modules stored in the memory 51, that is, implements the above-described database backup method.
The memory 61 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 61 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 61 may further include memory located remotely from the processor 60, which may be connected to a server over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Embodiments of the present invention also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a database backup method, the method comprising:
responding to a recovery request to generate a recovery task, and calling a recovery host to recover a backed-up resource instance corresponding to the recovery request according to the recovery task to obtain a recovered resource instance;
responding to a request for initiating a grid-cut backup to generate a grid-cut backup task, and calling the recovery host to perform grid-cut backup on the recovered resource instance according to the grid-cut backup task to obtain a resource instance file, wherein the request for initiating the grid-cut backup is used for requesting to export the recovered resource instance into the file;
and determining a backup strategy according to the recovery host and the resource instance file, and backing up the resource instance file based on the backup strategy.
Of course, the storage medium provided by the embodiment of the present invention contains computer-executable instructions, and the computer-executable instructions are not limited to the operations of the method described above, and may also perform related operations in the database backup method provided by any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the database backup apparatus, each included unit and module are only divided according to functional logic, but are not limited to the above division as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A method for database backup, comprising:
responding to a recovery request to generate a recovery task, and calling a recovery host to recover a backed-up resource instance corresponding to the recovery request according to the recovery task to obtain a recovered resource instance;
responding to a request for initiating a grid-cut backup to generate a grid-cut backup task, and calling the recovery host to perform grid-cut backup on the recovered resource instance according to the grid-cut backup task to obtain a resource instance file, wherein the request for initiating the grid-cut backup is used for requesting to export the recovered resource instance into the file;
and determining a backup strategy according to the recovery host and the resource instance file, and backing up the resource instance file based on the backup strategy.
2. The method of claim 1, further comprising, prior to generating a recovery task in response to initiating a recovery request:
acquiring an initiating recovery request, inquiring a recovery task table according to a resource instance identifier in the initiating recovery request, and detecting whether task conflicts exist under the same resource instance according to an inquiry result.
3. The method according to claim 1, wherein the generating a recovery task in response to the initiation of the recovery request, and invoking a recovery host according to the recovery task to recover the backed-up resource instance corresponding to the initiation of the recovery request to obtain a recovered resource instance comprises:
creating a recovery task in a recovery task table, updating a corresponding field of the recovery task according to the content of the initiated recovery request, and inserting the updated recovery task into a recovery task queue;
for a target recovery host with idle resources, selecting a recovery task which meets the processing capacity of the target recovery host as a current recovery task according to the task sequence in the recovery task queue, and querying a database instance table according to a resource instance corresponding to the current recovery task to obtain database rule information;
and calling the target recovery host, and running the current recovery task based on the database rule information to recover the backed-up resource instance corresponding to the initiated recovery request to obtain a recovered resource instance.
4. The method of claim 1, further comprising, prior to generating a cut-back backup task in response to initiating a cut-back backup request:
acquiring a request for initiating the grid-off backup, and inquiring a recovery task table according to a recovery task identifier in the request for initiating the grid-off backup to obtain a task state corresponding to a recovery task;
if the task state does not meet a preset first condition, acquiring a recovery task backup identifier and a backup state identifier;
and if the backup identification and the backup state identification do not meet the preset second condition, executing a step of responding to the request for initiating the grid-cut backup to generate a grid-cut backup task.
5. The method of claim 1, wherein the generating a cut-off backup task in response to initiating a cut-off backup request, and invoking the recovery host to perform a cut-off backup on the recovered resource instance according to the cut-off backup task to obtain a resource instance file comprises:
creating a lattice-breaking backup task in a lattice-breaking backup task table, updating a corresponding field of the lattice-breaking backup task according to the content of the lattice-breaking backup request, and inserting the updated lattice-breaking backup task into a backup task queue;
determining a recovery host with idle resources as a current recovery host, and selecting a grid-cut backup task which accords with the processing capacity of the current recovery host as a current grid-cut backup task according to the sequence of tasks in the backup task queue;
and calling the current recovery host to run the current grid-cut backup task so as to carry out grid-cut backup on the recovered resource instance on the current recovery host and obtain a resource instance file.
6. The method of claim 1, wherein determining a backup policy from the recovery host and the resource instance file, and backing up the resource instance file based on the backup policy comprises:
inquiring a preset backup strategy table according to the recovery host name and the resource instance file name, and determining whether a corresponding target backup strategy exists according to an inquiry result;
if yes, backing up the resource instance file based on the target backup strategy;
otherwise, creating a backup strategy for the resource instance file according to the backup value of the resource instance file and the idle resource of the recovery host, and backing up the resource instance file based on the newly created backup strategy.
7. The method of any of claims 1-6, further comprising, after backing up the resource instance file based on the backup policy:
and after the resource instance file is successfully backed up, calling the recovery host to remove the recovered resource instance which is backed up.
8. A database backup apparatus, comprising:
the resource recovery module is used for responding to a recovery request and generating a recovery task, and calling a recovery host according to the recovery task to recover a backed-up resource instance corresponding to the recovery request to obtain a recovered resource instance;
the grid-cut backup module is used for responding to a grid-cut backup initiating request to generate a grid-cut backup task, calling the recovery host to perform grid-cut backup on the recovered resource instance according to the grid-cut backup task to obtain a resource instance file, wherein the grid-cut backup initiating request is used for requesting to export the recovered resource instance to the file;
and the file backup module is used for determining a backup strategy according to the recovery host and the resource instance file and backing up the resource instance file based on the backup strategy.
9. A server, characterized in that the server comprises:
one or more processors;
a memory for storing one or more computer programs,
when executed by the one or more processors, cause the one or more processors to implement the database backup method of any of claims 1-7.
10. A storage medium containing computer-executable instructions for performing the database backup method of any of claims 1-7 when executed by a computer processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111473495.6A CN114153660A (en) | 2021-11-29 | 2021-11-29 | Database backup method, device, server and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111473495.6A CN114153660A (en) | 2021-11-29 | 2021-11-29 | Database backup method, device, server and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114153660A true CN114153660A (en) | 2022-03-08 |
Family
ID=80452410
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111473495.6A Pending CN114153660A (en) | 2021-11-29 | 2021-11-29 | Database backup method, device, server and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114153660A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116016496A (en) * | 2023-01-30 | 2023-04-25 | 中国联合网络通信集团有限公司 | Real-time file synchronization method, device, equipment and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104166600A (en) * | 2014-08-01 | 2014-11-26 | 腾讯科技（深圳）有限公司 | Data backup and recovery methods and devices |
| CN104899333A (en) * | 2015-06-24 | 2015-09-09 | 浪潮(北京)电子信息产业有限公司 | Cross-platform migrating method and system for Oracle database |
| CN107526654A (en) * | 2017-08-05 | 2017-12-29 | 中山大学 | A kind of oracle database backup and reduction system based on webpage |
| CN112099989A (en) * | 2020-08-28 | 2020-12-18 | 中国—东盟信息港股份有限公司 | Disaster recovery, migration and recovery method for Kubernetes cloud native application |
| CN112214357A (en) * | 2020-10-30 | 2021-01-12 | 上海爱数信息技术股份有限公司 | HDFS data backup and recovery system and backup and recovery method |
| CN112214358A (en) * | 2020-10-30 | 2021-01-12 | 上海爱数信息技术股份有限公司 | Backup and recovery system and method for GaussDB distributed database |
-
2021
- 2021-11-29 CN CN202111473495.6A patent/CN114153660A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104166600A (en) * | 2014-08-01 | 2014-11-26 | 腾讯科技（深圳）有限公司 | Data backup and recovery methods and devices |
| CN104899333A (en) * | 2015-06-24 | 2015-09-09 | 浪潮(北京)电子信息产业有限公司 | Cross-platform migrating method and system for Oracle database |
| CN107526654A (en) * | 2017-08-05 | 2017-12-29 | 中山大学 | A kind of oracle database backup and reduction system based on webpage |
| CN112099989A (en) * | 2020-08-28 | 2020-12-18 | 中国—东盟信息港股份有限公司 | Disaster recovery, migration and recovery method for Kubernetes cloud native application |
| CN112214357A (en) * | 2020-10-30 | 2021-01-12 | 上海爱数信息技术股份有限公司 | HDFS data backup and recovery system and backup and recovery method |
| CN112214358A (en) * | 2020-10-30 | 2021-01-12 | 上海爱数信息技术股份有限公司 | Backup and recovery system and method for GaussDB distributed database |
Non-Patent Citations (1)
| Title |
|---|
| 高继民 等: "《Oracle数据库SQL和PL/SQL实例教程》", 30 June 2004, 西安电子科技大学出版社, pages: 5 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116016496A (en) * | 2023-01-30 | 2023-04-25 | 中国联合网络通信集团有限公司 | Real-time file synchronization method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109815049B (en) | Node downtime recovery method and device, electronic equipment and storage medium | |
| US11966301B2 (en) | System and method for managing and producing a dataset image across multiple storage systems | |
| JP5075736B2 (en) | System failure recovery method and system for virtual server | |
| CN107291787B (en) | Main and standby database switching method and device | |
| WO2016180160A1 (en) | Data snapshot recovery method and apparatus | |
| CN109542682B (en) | Data backup method, device, equipment and storage medium | |
| WO2017088681A1 (en) | Fault handling method and apparatus for gateway device | |
| US10725980B2 (en) | Highly available cluster agent for backup and restore operations | |
| CN110543386B (en) | Data storage method, device, equipment and storage medium | |
| US20240012715A1 (en) | Dataset image creation | |
| CN107656705B (en) | Computer storage medium and data migration method, device and system | |
| CN112463437B (en) | Service recovery method, system and related components of storage cluster system offline node | |
| US20030028594A1 (en) | Managing intended group membership using domains | |
| CN114153660A (en) | Database backup method, device, server and medium | |
| US8117181B2 (en) | System for notification of group membership changes in directory service | |
| CN116701063B (en) | Persistence method, device and system for internal memory state data for data language of digital networking | |
| CN111488195B (en) | Virtual machine cloning method, device, equipment and computer readable storage medium | |
| CN112333008A (en) | Cloud host complete machine backup and restoration method, device, equipment and storage medium | |
| WO2019178839A1 (en) | Method and device for creating consistency snapshot for distributed application and distributed system | |
| CN114201458B (en) | Information updating method, micro-service system and computer readable storage medium | |
| CN107908370B (en) | Data storage method and device | |
| WO2022135471A1 (en) | Multi-version concurrency control and log clearing method, node, device and medium | |
| CN113703946A (en) | Application recovery method and device, electronic equipment and computer readable storage medium | |
| JP5466740B2 (en) | System failure recovery method and system for virtual server | |
| CN111078465A (en) | Data recovery method and device and computer readable storage medium |
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 |