CN116795585A - Data backup system - Google Patents
Data backup system Download PDFInfo
- Publication number
- CN116795585A CN116795585A CN202210255976.8A CN202210255976A CN116795585A CN 116795585 A CN116795585 A CN 116795585A CN 202210255976 A CN202210255976 A CN 202210255976A CN 116795585 A CN116795585 A CN 116795585A
- Authority
- CN
- China
- Prior art keywords
- backup
- database
- task
- server
- condition
- 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
- 230000006978 adaptation Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000000034 method Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present disclosure proposes a data backup system comprising: the system comprises a scheduling server and a plurality of database servers, wherein the scheduling server is used for storing backup tasks corresponding to each database cluster respectively, and the backup tasks comprise executable time information; the backup device is used for determining a target backup task which can be issued according to the current time and sending the target backup task to the backup device; the backup device is used for executing backup operation on the database instance of the corresponding database cluster according to preset backup operation logic and the received backup task. Therefore, unified scheduling management of backup tasks of the database server and the scheduling server is realized, mutual interference of the backup tasks in the database server is avoided, performance of the server is improved, and the backup device is used for executing backup operation on database instances of corresponding database clusters according to preset backup operation logic and received backup tasks, so that efficiency is high.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a data backup system.
Background
In order to fully utilize server resources, most companies adopt a single-machine multi-instance deployment mode, so that problems are brought to instance backup of the server. For example, the instance backups may interfere with each other, consume resources of the server, and even affect the service.
Disclosure of Invention
The present disclosure provides a data backup system comprising: a scheduling server and a plurality of database servers, wherein each database server is provided with a backup device and a plurality of database instances, and each database instance in the plurality of database instances belongs to a different database cluster;
the scheduling server is used for storing backup tasks corresponding to each database cluster respectively, wherein the backup tasks comprise executable time information; the backup device is used for determining a target backup task which can be issued according to the current time and sending the target backup task to the backup device;
the backup device is used for executing backup operation on the database instance of the corresponding database cluster according to preset backup operation logic and the received backup task.
Optionally, the backup device is configured to send a backup task acquisition request to the scheduling server;
optionally, the scheduling server is configured to select a target backup task that can be issued according to the current time and the backup task acquisition request.
Optionally, the scheduling server is configured to save a backup task corresponding to any database cluster in response to the database cluster meeting a backup deployment condition.
Optionally, the backup task acquisition request includes a cluster identifier;
the scheduling server is used for searching the backup task corresponding to the cluster identifier from the stored backup tasks, and determining the target backup task which can be issued according to the current time and the searched executable time information of the backup task.
Optionally, the backup task acquisition request includes a database server identifier;
the scheduling server is used for searching the cluster identification matched with the database server identification according to the database server identification and the database configuration information; and the target backup task which can be issued is determined according to the current time and the searched executable time information of the backup task.
Optionally, the backup device is configured to send the backup task obtaining request to the scheduling server when the resource utilization rate of the database server where the backup device is located does not exceed a preset value.
Optionally, the backup device is configured to send the backup task obtaining request to the scheduling server when the backup device does not execute a backup task.
Optionally, the backup device is configured to record a backup condition of each database instance in the database server where the backup device is located; and the database instance meeting the backup condition is determined according to the backup condition of each recorded database instance, and the backup task acquisition request is generated according to the database cluster to which the database instance meeting the backup condition belongs.
Optionally, the backup device is configured to determine, when there are multiple database instances that satisfy the backup condition, a target database instance according to execution time of the executed backup task, and generate the backup task obtaining request for the target database instance.
Optionally, the backup device is configured to determine a target database instance according to the priority of the database cluster under the condition that there are multiple database instances that meet the backup condition, and generate the backup task acquisition request for the target database instance.
The data backup system provided by the disclosure realizes unified scheduling management of backup tasks of the database server and the scheduling server, avoids mutual interference of the backup tasks in the database server, improves the performance of the server, executes backup operation on database instances of corresponding database clusters based on preset backup operation logic and received backup tasks, has higher efficiency, enables the backup device to avoid task overlapping, ensures the reliability and flexibility of task backup and avoids task serial after the current task is completed, and in addition, in the data backup system, the scheduling server can actively issue backup tasks, and the backup device can actively acquire tasks to be backed up to the scheduling server.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.
Drawings
The foregoing and/or additional aspects and advantages of the present disclosure will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
fig. 1 is a block diagram of a data backup system according to an embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
A data backup system provided by the present disclosure is described in detail below with reference to the accompanying drawings.
Fig. 1 is a block diagram of a data backup system according to an embodiment of the present disclosure.
A data backup system 10 provided in an embodiment of the present disclosure includes: a dispatch server and a plurality of database servers.
As shown in fig. 1, the data backup system 10 includes a database server 1, a database server 2, a database server 3, a database server 4, and a database server 5. Wherein each database server comprises a backup device.
Each database server is provided with a backup device and a plurality of database examples, and each database example in the plurality of database examples belongs to a different database cluster.
Wherein a database cluster may be a collection of servers comprising a plurality of database servers. It should be noted that, since the plurality of database instances included in the database server belong to different database clusters, that is, the database server may also correspond to the plurality of database clusters.
For example, if the current data backup system includes database server a, database server B, database server C, database server D, database server E, database server F, database server G, and database server H, the database cluster W1 includes database server a, database server B, and database server C, the database cluster W2 includes database server a, database server D, and database server E, and the database cluster W3 includes database server a, database server F, database server G, and database server H. Database server a includes database instances Q1, Q2, Q3. Wherein, Q1 belongs to database cluster W1, Q2 belongs to database cluster W2, and Q3 belongs to database cluster W3.
The above example is only one illustrative illustration of the present disclosure and is not intended to be limiting of the present disclosure.
The scheduling server can store backup tasks corresponding to the database clusters respectively, wherein the backup tasks comprise executable time information; and the target backup task is used for determining the target backup task which can be issued according to the current time and sending the target backup task to the backup device.
The backup device can execute backup operation on the database instance of the corresponding database cluster according to preset backup operation logic and the received backup task.
Optionally, when any database cluster satisfies the backup deployment condition, the scheduling server may save the backup task corresponding to the database cluster.
As one possible implementation manner, the backup device may actively send a backup task acquisition request to the scheduling server, so that the scheduling server determines and issues a corresponding target backup task based on the backup task acquisition request. That is, alternatively, the backup apparatus may send a backup task acquisition request to the scheduling server, and then the scheduling server may select to determine the target backup task that can be issued according to the current time and the backup task acquisition request.
The backup task obtaining request may be a task obtaining request instruction, which may include a database server identifier, a cluster identifier, or the like, which is not limited herein.
The cluster identifier may be a unique characteristic information of the database cluster, which may be a specific number, or a character sequence, which is not limited herein.
The database server identifier may be a unique characteristic information of the database server, which may be a specific number, or a character sequence, which is not limited herein.
Optionally, the backup device may send the backup task obtaining request to the scheduling server when the resource utilization rate of the database server where the backup device is located does not exceed a preset value.
It is known that different database servers may have different available resources, such as storage resources, computing resources, etc., while different types of instances, or different numbers of instances, occupy different amounts of system resources. When the resource utilization rate of a certain database server is relatively low, it can be considered that the database server does not seriously interfere with other normal task instances in the database server if the backup task is started currently. Therefore, the backup device can send the backup task acquisition request to the scheduling server under the condition that the resource utilization rate of the database server does not exceed a preset value.
Or, the backup device may also send a backup task acquisition request to the scheduling server when the backup device does not execute the backup task. If the current target server does not have the backup task in the running state, it is stated that the target server is not interfered by other backup tasks when executing the backup task sent by the scheduling platform at the current moment.
Or, before sending the backup task obtaining request to the scheduling server, the backup device may first check the current state of the backup device, for example, whether the backup device needs maintenance at present, whether each module in the backup device, such as a calculation module, a timing module, a processing module, etc., has an abnormality, and whether the available memory space is sufficient. Thereby ensuring that the backup device achieves a good backup premise before backup.
Further, since the performance of different database servers may be different, the duration of processing the backup tasks may also be different. The backup device can also estimate the backup time length of the previous backup task by combining the performance and task type of the current database server and judge whether the previous backup task reaches the completion time by combining the time of receiving the backup task. If the previous backup task has reached the completion time, it may be determined that the current database server does not have a backup task in an operational state.
Further, the present disclosure will be described below in terms of a manner in which a backup device generates a backup task acquisition request after a backup condition is satisfied.
As a possible implementation manner, the backup device may record the backup condition of each database instance in the database server where the backup device is located; and determining the database instance meeting the backup condition according to the backup condition of each recorded database instance, and generating the backup task acquisition request according to the database cluster to which the database instance meeting the backup condition belongs.
The backup conditions corresponding to the different types of examples may be different or the same. The backup condition may be any condition that may trigger the backup of the instance, for example, may be that a specified time interval is reached, or a specified running period may be reached for the instance, or a new code increment corresponding to the instance may reach a set value, or the like.
Alternatively, backup conditions for different instances may also be determined based on the importance of the instance and the time the instance is running. For example, if the instance is important, the update is more frequent, and the corresponding backup period can be half a day backup or one day backup, etc.; if the instance's data is relatively less important and updated less frequently, the backup period may be a Monday backup or a half month backup, etc.
In the process of monitoring the instances in each database server, if a certain instance in a certain database server already reaches a backup condition, the backup device can consider that the current instance can be backed up, and then the backup task acquisition request can be generated according to the database cluster to which the database instance meeting the backup condition belongs.
In particular, there may be many instances in each database server, and the types of these instances may be the same or different. And the corresponding operating periods may be different due to the different types, resulting in the operating periods of different database servers being different. For example, the run time of an instance of type A may be 1-3 points, the run time of an instance of type B may be 3-6 points or 6-9 points, etc.
Optionally, the backup device may determine, in the case of having a plurality of database instances satisfying the backup condition, a target database instance according to the execution time of the executed backup task, and generate the backup task acquisition request for the target database instance.
Specifically, the backup device may periodically determine, under the condition that there are a plurality of database instances satisfying the backup condition, a target database instance according to the execution time of the executed backup task, and generate the backup task obtaining request for the target database instance.
It can be understood that, when the backup device generates the backup task acquisition request, the backup time of the backup task can be estimated, and the completion time of the backup task can be estimated according to the current time of sending the backup task.
The backup device can determine the progress status of the current backup task, that is, the completion degree of the backup task, according to the execution time of the executed backup task.
Optionally, the backup device may determine, in the case of having a plurality of database instances satisfying the backup condition, a target database instance according to the priority of the database cluster, and generate the backup task acquisition request for the target database instance.
Because the database server may include a plurality of database instances meeting the backup condition, the scheduling platform may determine the target database instance according to the priorities of the database clusters corresponding to the database instances, so as to obtain one target database instance with the highest priority from the plurality of database instances meeting the backup condition, and further generate the backup task obtaining request for the target database instance.
For example, the database server includes 5 database instances satisfying the backup condition, and each corresponding type a, b, c, d, e, and the priorities of the 5 database instance types are known from high to low: c. e, a, b, d, the backup device may determine the target database instance from the database instance c, and further generate the backup task obtaining request for the target database instance c.
Optionally, the backup task obtaining request includes a cluster identifier, and the scheduling server may find a backup task corresponding to the cluster identifier from the stored backup tasks, and determine the target backup task that may be issued according to the current time and the found executable time information of the backup task.
Specifically, the scheduling server may determine, according to the cluster identifiers corresponding to the saved backup tasks and the cluster identifier included in the current backup task acquisition request, a backup task currently corresponding to the cluster identifier.
For example, if the cluster identifier included in the current backup task obtaining request is S and the cluster identifiers corresponding to the currently stored backup tasks A1, A2, and A3 are S, X, and V, the backup task A1 with the cluster identifier S may be used as the backup task corresponding to the cluster identifier.
Further, after determining the backup task corresponding to the cluster identifier, executable time information corresponding to the current backup task is also required to be compared with the current time to determine whether the backup period of the backup task is currently available.
It should be noted that many backup tasks may be stored in the scheduling server, and cluster identifiers of the backup tasks may be the same or different. And the corresponding executable time information may be different for different backup tasks. For example, the executable time of the backup task A may be 1-3 points, the executable time of the backup task B may be 3-6 points or 6-9 points, etc. Therefore, the scheduling server can further determine whether the backup period of the backup task is currently performed according to the searched executable time information of the backup task.
The target backup task may be one or more. Specifically, the scheduling server may issue the target backup task to the database server corresponding to the cluster identifier, or may issue the target backup task only to the database server corresponding to the backup device that sends the backup task acquisition request.
Optionally, the backup task obtaining request includes a database server identifier, and the scheduling server may find a cluster identifier matched with the database server identifier according to the database server identifier and the database configuration information; and searching the backup task corresponding to the cluster identifier from the stored backup tasks, and determining the target backup task which can be issued according to the current time and the searched executable time information of the backup task.
The scheduling server can also find out the cluster identification matched with the database server identification according to the database server identification and the database configuration information.
It should be explained here that there are multiple database instances in one database server, and the database clusters corresponding to each database instance are different, that is, one database server identifier may correspond to multiple cluster identifiers. The database configuration information may include information of each database instance included in the database, and because each database instance corresponds to a database cluster, the scheduling server may find a cluster identifier matched with the database server identifier according to the database server identifier and the database configuration information.
For example, if the current database server is identified as Q and the database configuration information is Q1, Q2, Q3, Q4, where Q1, Q2, Q3, Q4 are examples deployed in the database server Q, the scheduling server may find the database clusters Q1, Q2, Q3, Q4 corresponding to Q1, Q2, Q3, Q4, and then may take the backup tasks corresponding to Q1, Q2, Q3, Q4 as the backup tasks corresponding to the cluster identifier Q.
Further, after determining the backup task corresponding to the database server identifier, executable time information corresponding to the current backup task is also required to be compared with the current time to determine whether the backup period of the backup task is currently available.
For example, if the current time is t1 and the executable times corresponding to Q1, Q2, Q3, and Q4 are t1, t2, t3, and t4, respectively, Q1 may be used as the target backup task that can be issued, which is not limited herein.
As another possible implementation manner, the scheduling server may determine, according to the currently saved backup task and the executable time information corresponding to the currently saved backup task, a target backup task to be issued currently.
Specifically, when the scheduling server issues the target backup task, the scheduling server may send an inquiry request to each database server to determine the current resource utilization rate of each database server and whether there is a backup task in an operation state, and further, if the current resource utilization rate of any database server at present meets a backup condition, or there is no backup task in an operation state, the scheduling server may determine the currently-issued target backup task according to the configuration information of the database server capable of issuing the backup task at present and each database instance deployed therein.
The data backup system provided by the disclosure realizes unified scheduling management of backup tasks of the database server and the scheduling server, avoids mutual interference of the backup tasks in the database server, improves the performance of the server, executes backup operation on database instances of corresponding database clusters based on preset backup operation logic and received backup tasks, has higher efficiency, enables the backup device to avoid task overlapping, ensures the reliability and flexibility of task backup and avoids task serial after the current task is completed, and in addition, in the data backup system, the scheduling server can actively issue backup tasks, and the backup device can actively acquire tasks to be backed up to the scheduling server.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A data backup system, comprising: a scheduling server and a plurality of database servers, wherein each database server is provided with a backup device and a plurality of database instances, and each database instance in the plurality of database instances belongs to a different database cluster;
the scheduling server is used for storing backup tasks corresponding to each database cluster respectively, wherein the backup tasks comprise executable time information; the backup device is used for determining a target backup task which can be issued according to the current time and sending the target backup task to the backup device;
the backup device is used for executing backup operation on the database instance of the corresponding database cluster according to preset backup operation logic and the received backup task.
2. The system of claim 1, wherein,
and the scheduling server is used for responding to the condition that any database cluster meets the backup deployment condition and storing the backup task corresponding to the database cluster.
3. The system of claim 1, wherein,
the backup device is used for sending a backup task acquisition request to the scheduling server;
and the scheduling server is used for selecting the target backup task which can be issued according to the current time and the backup task acquisition request.
4. The system of claim 3, wherein the backup task acquisition request includes a cluster identification;
the scheduling server is used for searching the backup task corresponding to the cluster identifier from the stored backup tasks, and determining the target backup task which can be issued according to the current time and the searched executable time information of the backup task.
5. The system of claim 3, wherein the backup task acquisition request includes a database server identification;
the scheduling server is used for searching the cluster identification matched with the database server identification according to the database server identification and the database configuration information; and the target backup task which can be issued is determined according to the current time and the searched executable time information of the backup task.
6. The system of claim 3, wherein the system comprises,
and the backup device is used for sending the backup task acquisition request to the scheduling server under the condition that the resource utilization rate of the database server where the backup device is positioned does not exceed a preset value.
7. The system of claim 3, wherein the system comprises,
and the backup device is used for sending the backup task acquisition request to the scheduling server under the condition that the backup device does not execute the backup task.
8. The system of claim 3, wherein the system comprises,
the backup device is used for recording the backup condition of each database instance in the database server where the backup device is located; and the database instance meeting the backup condition is determined according to the backup condition of each recorded database instance, and the backup task acquisition request is generated according to the database cluster to which the database instance meeting the backup condition belongs.
9. The system of claim 8, wherein,
the backup device is used for determining a target database instance according to the execution time of the executed backup task under the condition that a plurality of database instances meeting the backup condition exist, and generating the backup task acquisition request for the target database instance.
10. The system of claim 8, wherein,
the backup device is used for determining a target database instance according to the priority of the database cluster under the condition that a plurality of database instances meeting the backup condition exist, and generating the backup task acquisition request for the target database instance.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210255976.8A CN116795585A (en) | 2022-03-15 | 2022-03-15 | Data backup system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210255976.8A CN116795585A (en) | 2022-03-15 | 2022-03-15 | Data backup system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116795585A true CN116795585A (en) | 2023-09-22 |
Family
ID=88045519
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210255976.8A Pending CN116795585A (en) | 2022-03-15 | 2022-03-15 | Data backup system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116795585A (en) |
-
2022
- 2022-03-15 CN CN202210255976.8A patent/CN116795585A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6411982B2 (en) | Thread based governor for time scheduled process execution | |
| US8627322B2 (en) | System and method of active risk management to reduce job de-scheduling probability in computer clusters | |
| US20050010608A1 (en) | Job scheduling management method, system and program | |
| US20030097370A1 (en) | Database load distribution processing method and recording medium storing a database load distribution processing program | |
| CN111580990A (en) | Task scheduling method, scheduling node, centralized configuration server and system | |
| CN112905339B (en) | Task scheduling execution method, device and system | |
| CN102473134A (en) | Management server, management method, and management program for virtual hard disk | |
| CN109445927B (en) | Task management method and device for storage cluster | |
| CN111459641B (en) | Method and device for task scheduling and task processing across machine room | |
| CN110895488B (en) | Task scheduling method and device | |
| CN110895487A (en) | Distributed task scheduling system | |
| CN111416825A (en) | Inter-thread lock-free log management method and system, terminal and storage medium | |
| CN110895486A (en) | Distributed task scheduling system | |
| CN102081757A (en) | Report making method and system | |
| CN111580951A (en) | Task allocation method and resource management platform | |
| CN110895485A (en) | Task scheduling system | |
| CN110287159B (en) | File processing method and device | |
| CN116795585A (en) | Data backup system | |
| CN115858499A (en) | Database partition processing method and device, computer equipment and storage medium | |
| CN114692585A (en) | Table service processing method and system | |
| CN114546730A (en) | Data recovery processing method, device and system | |
| CN113342893A (en) | Node synchronization method and device based on block chain, storage medium and server | |
| CN112685334A (en) | Method, device and storage medium for block caching of data | |
| CN111240949B (en) | Method and device for determining software use frequency in domestic operating system | |
| CN117763051B (en) | Extensible CDC mode dream-reaching database synchronization system and application thereof |
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 |