CN108897638B - Data backup method and device, computer equipment and storage medium - Google Patents
Data backup method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN108897638B CN108897638B CN201810546827.0A CN201810546827A CN108897638B CN 108897638 B CN108897638 B CN 108897638B CN 201810546827 A CN201810546827 A CN 201810546827A CN 108897638 B CN108897638 B CN 108897638B
- Authority
- CN
- China
- Prior art keywords
- server
- servers
- data
- slave
- full
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a data backup method, a data backup device, computer equipment and a storage medium. The method comprises the following steps: acquiring a backup request; the backup request carries a database identifier and a data identifier to be backed up; acquiring corresponding data to be backed up based on the data to be backed up identifier; searching a full slave server, an incremental slave server and a plurality of master servers corresponding to the database identification; screening out at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server; and storing the data to be backed up to the screened at least one main server, backing up the data to be backed up to the full slave server in full and backing up the data to be backed up to the incremental slave server in incremental mode. By adopting the method, data storage on a plurality of servers can be balanced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data backup method and apparatus, a computer device, and a storage medium.
Background
With the rapid development of office automation and electronic commerce, enterprises pay more and more attention to databases. For important data, real-time backup of data in a database is often required. When the data volume of the data to be backed up is large, the database management personnel can store the data to be backed up into the databases on the plurality of servers. Multiple databases are typically deployed on each server. Because the databases for different services have different data storage requirements, the data storage capacity growth conditions are different. In a traditional mode, data storage amounts of different servers are usually unbalanced, and the situation that the data storage amounts on some servers tend to be saturated and the data storage amounts on some servers are low is easy to occur.
Disclosure of Invention
In view of the above, it is necessary to provide a data backup method, apparatus, computer device and storage medium capable of balancing data storage on a plurality of servers.
A method of data backup, the method comprising: acquiring a backup request; the backup request carries a database identifier and a data identifier to be backed up; acquiring corresponding data to be backed up based on the data to be backed up identifier; searching a full slave server, an incremental slave server and a plurality of master servers corresponding to the database identification; screening out at least one main server from the plurality of main servers according to the data storage capacity of the full-amount slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server; and storing the data to be backed up to the screened at least one main server, and backing up the data to be backed up to the full slave server in full and backing up to the incremental slave server in incremental mode.
In one embodiment, the screening at least one master server from the plurality of master servers according to the data storage capacity of the full slave server, the data storage capacity of the incremental slave server and the available capacity of each master server includes: calculating according to the data storage capacity of the full slave server and the data storage capacity of the incremental slave server to obtain a storage capacity increase rate corresponding to the database identifier; fitting according to the available capacity of each main server and the storage capacity growth rate to obtain the available duration of the available capacity of each main server; and screening at least one main server from the plurality of main servers according to the available capacity available time length of each main server.
In one embodiment, the screening at least one primary server from the plurality of primary servers according to the available capacity of each primary server comprises: sequencing the plurality of main servers according to the available capacity available duration of each main server; and taking the main servers with the preset number in the front after being sorted in the plurality of main servers as the screened main servers.
In one embodiment, the searching for the full slave server, the incremental slave server and the plurality of master servers corresponding to the database identification comprises: determining a database instance identifier corresponding to the database identifier; acquiring a target instance table corresponding to the database instance identifier; searching a full slave server identifier, an incremental slave server identifier and a plurality of master server identifiers contained in the target instance table; and determining corresponding full slave servers according to the full slave server identifications, determining corresponding incremental slave servers according to the incremental slave server identifications, and determining corresponding master servers according to each master server identification.
In one embodiment, the storing the data to be backed up to the screened at least one master server, and performing full backup and incremental backup on the data to be backed up to the full slave server and the incremental slave server includes: storing the data to be backed up to the screened at least one main server; compressing the data to be backed up stored in the screened at least one main server to obtain a compressed file packet; backing up the full amount of the compressed file package to the full amount slave server; and backing up the compressed file package to the increment slave server in an increment mode.
In one embodiment, the full slave server contains a compressed file package that has been fully backed up, and the method further comprises: receiving a recovery request uploaded by a terminal; the recovery request carries a database identifier and a recovery type; in response to the recovery request, searching a full number of slave servers and a plurality of master servers corresponding to the database identification; when the recovery type is a first type, sending the compressed file packets to be recovered in the full slave servers to the plurality of master servers, and analyzing the compressed file packets in the plurality of master servers; and when the recovery type is a second type, changing the full slave server into a master server, and analyzing the compressed file to be recovered in the full slave server.
In one embodiment, the recovering request further carries a timestamp, and the sending the full amount of compressed file packets to be recovered in the slave servers to the multiple master servers and analyzing the compressed file packets in the multiple master servers includes: determining a time interval corresponding to the timestamp; acquiring a plurality of compressed file packages to be recovered in the full slave server; the backup time corresponding to the compressed file package to be restored is in the time interval; sending the plurality of compressed file packages to be restored to at least one main server; and analyzing the compressed file in the main server which receives the compressed file to be restored.
A data backup apparatus, the apparatus comprising: the acquisition module is used for acquiring the backup request; the backup request carries a database identifier and a data identifier to be backed up; acquiring corresponding data to be backed up based on the data to be backed up identifier; the searching module is used for searching a full slave server, an incremental slave server and a plurality of main servers corresponding to the database identification; the screening module is used for screening at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server; and the backup module is used for storing the data to be backed up to the screened at least one main server, fully backing up the data to be backed up to the full slave server and incrementally backing up to the incremental slave server.
A computer device comprising a memory storing a computer program and a processor implementing the steps of the data backup method described in the various embodiments above when the processor executes the computer program.
A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the data backup method described in the various embodiments above.
In the data backup method, after the operation and maintenance server obtains the backup request, the operation and maintenance server can search the full slave server, the incremental slave server and the plurality of main servers corresponding to the database identifiers carried by the backup request, and obtain the data storage capacity or the available capacity of the storage servers. The operation and maintenance server can screen out at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server, store data to be backed up to the screened at least one main server, and back up the full slave servers and the incremental slave servers of the data to be backed up. The master server and the slave server perform full backup and incremental backup on the data to be backed up, so that the safety of the data can be effectively guaranteed, and the growing trend of the data storage capacity on each storage server can be better understood. The data to be backed up is stored to the main server with slow data growth or more available capacity, the overload condition of the main server is avoided, the utilization rate of each main server is balanced, and therefore data storage on a plurality of servers can be balanced.
Drawings
FIG. 1 is a diagram illustrating an exemplary implementation of a data backup method;
FIG. 2 is a flowchart illustrating a data backup method according to an embodiment;
FIG. 3 is a flowchart illustrating a data backup method according to another embodiment;
FIG. 4 is a block diagram of a data backup apparatus according to an embodiment;
FIG. 5 is a diagram of the internal structure of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The data backup method provided by the application can be applied to the application environment shown in fig. 1. Wherein, the terminal 102 communicates with the operation and maintenance server 104 through a network. The operation and maintenance server 104 may be in network communication with the storage server cluster 106. The terminal 102 may also communicate with the storage server cluster 106 over a network. Included in the storage server cluster 106 is, but is not limited to, a full slave server 106a, an incremental slave server 106b, and a plurality of master servers 106c. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the operation and maintenance server 104 may be implemented by an independent server or a server cluster formed by multiple servers. The terminal 102 sends a backup request to the operation and maintenance server 104, and the operation and maintenance server 104 may search the corresponding full-volume slave server 106a, the incremental slave server 106b, and the plurality of master servers 106c in the storage server cluster 106 according to the database identifier carried in the backup request. The operation and maintenance server 104 may screen at least one master server 106c from the plurality of master servers 106c based on the data storage capacity of the full slave server 106a, the data storage capacity of the incremental slave server 106b, and the available capacity of each master server 106c. The operation and maintenance server 104 may store the data to be backed up to the screened at least one master server 106c, and backup the data to be backed up to the full slave server 106a in full and backup the data to be backed up to the incremental slave server 106b in incremental.
In one embodiment, as shown in fig. 2, a data backup method is provided, which is described by taking the application of the method to the operation and maintenance server 104 in fig. 1 as an example, and includes the following steps:
And 204, acquiring corresponding data to be backed up based on the data to be backed up identifier.
A backup request refers to a request to backup data in a database. Database identification refers to an identification used to distinguish one database from other users. The database identifier may be comprised of one or more of letters, numbers, punctuation marks, and the like. For example, the database identifier may be a database name, an IP (Internet Protocol Address) Address or a port number of a server to which the database belongs. The identifier to be backed up may be a path for acquiring data to be backed up. The data to be backed up refers to data which needs to be stored and backed up.
In one embodiment, the terminal may call an API (Application Programming Interface) of the operation and maintenance server, and upload a backup request carrying a database identifier and data to be backed up to the operation and maintenance server for processing.
The main server is a storage server used for the database in a normal operation state. After the user authorizes the database, the user can access the database on the main server through the terminal, and add, delete, change and inquire the data in the database. The slave server refers to a storage server for backing up data in a database on the master server. The slave servers include a full slave server and an incremental slave server. The full slave server is a slave server for performing full backup, and the incremental slave server is a slave server for performing incremental backup. Full backup refers to making a complete copy of all data on the primary server at a point in time. The incremental backup refers to that after the last incremental backup, the incremental backup only needs to backup data which is increased or modified compared with the last incremental backup.
In one embodiment, finding the full slave server, the incremental slave server, and the plurality of master servers corresponding to the database identification comprises: determining a database instance identifier corresponding to the database identifier; acquiring a target instance table corresponding to the database instance identifier; searching a total slave server identifier, an incremental slave server identifier and a plurality of master server identifiers which are contained in a target instance table; and determining corresponding full slave servers according to the full slave server identifications, determining corresponding incremental slave servers according to the incremental slave server identifications, and determining corresponding master servers according to each master server identification.
Database instances (instances) refer to a series of processes in an operating system and the chunks of memory allocated for those processes. A database is a repository built on computer storage devices that organizes, stores, and manages data according to a data structure. Each database instance may correspond to multiple databases. The operation and maintenance server may create a database instance on the storage server, i.e., allocate a block of memory from the storage server, and then deploy the database on the allocated memory. The target instance table is a table in which information related to database instances is recorded. The database instance related information includes, but is not limited to, a full slave server identification, an incremental slave server identification, and a plurality of master server identifications. The full slave identification may be an IP address or port number of the full server, the incremental slave identification may be an IP address or port number of the incremental server, and the master identification may be an IP address or port number of the master server.
Backup attribute information such as backup state, backup latest time, backup frequency, backup retention days, next backup time and the like can be recorded in the target instance table. The backup attribute information may be information carried by the database application work order when the operation and maintenance server deploys the database and the user sends the database application work order through the terminal. The operation and maintenance server can also realize the backup of the data according to the backup attribute information recorded in the target instance table. The relation among the database, the database instance and the storage database can be clearly determined through the target instance table, so that the full-amount slave server, the incremental slave server and the plurality of main servers corresponding to the database identification can be quickly found.
And step 208, screening out at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server.
The data storage capacity refers to the memory occupied by the data stored on the server in full quantity or incremental quantity. The available capacity refers to the remaining available memory on the primary server. The operation and maintenance server can monitor the data storage capacity and the available capacity of each storage server in real time, and directly acquire the data storage capacity and the available capacity monitored in real time when receiving the backup request; it is also possible to query the data storage of the respective full slave server, incremental slave server and the available capacity of the plurality of master servers only upon receiving a backup request.
In one embodiment, the total capacity of each storage server may be the same or different. And the same storage server can be used as one of a full slave server, an incremental slave server and a master server aiming at different databases. That is, the data on each storage server may originate from multiple parties. Therefore, the data storage capacity and the available capacity of each storage server can be acquired, and all the storage servers can be comprehensively screened.
According to the data storage amount of the full slave server, the data storage amount of the incremental slave server and the available capacity of each master server, the trend of data growth in the master server can be calculated. When data is increased quickly or available capacity is small, the data storage capacity on the main server tends to be saturated, and the main server is easy to overload, so that the data to be backed up is required to be prevented from being stored in the main server; when the data increase is slow or the available capacity is large, it is indicated that the data storage capacity on the main server tends to be low, the utilization rate of the main server is low, and the data to be backed up can be preferentially stored in the main server.
Full backup refers to making a complete copy of all data on the primary server at a point in time. The incremental backup refers to that after the last incremental backup, the incremental backup only needs to backup data which is increased or modified compared with the last incremental backup. For example, the backup frequency may be every day, and the backup of the data to be backed up to the full slave server is to backup the newly added data to be backed up to the full slave server; when data to be backed up is incrementally backed up to the incremental slave server, not only the newly added data to be backed up at this time needs to be backed up to the incremental slave server, but also data backed up in the previous day including the period corresponding to the current backup day in the incremental slave server needs to be deleted, so that the incremental slave server only includes the data backed up in the period corresponding to the current backup day.
In one embodiment, storing the data to be backed up to the screened at least one master server, and backing up the data to be backed up to the full slave server in full and backing up to the incremental slave server in incremental manner includes: storing the data to be backed up to the screened at least one main server; compressing the data to be backed up stored in the screened at least one main server to obtain a compressed file packet; backing up the whole compressed file package to a full slave server; and performing incremental backup on the compressed file package to an incremental slave server.
A hot backup tool, for example, an xtrackup tool (a tool capable of performing physical backup of data without affecting data reading and writing during backup) may be invoked to copy and compress the data to be backed up. The backup data can be compressed in a streaming manner to obtain a compressed file packet in a tar (Linux system command) or xbstream (a data format of a compressed file) format. The data to be backed up is backed up in a mode of compressing the file packet, so that the memory occupied by the backup data is reduced, the compressed file packet can be encrypted more conveniently, and the safety of the data to be backed up is improved.
In the data backup method, after the operation and maintenance server obtains the backup request, the operation and maintenance server can search the full slave server, the incremental slave server and the plurality of main servers corresponding to the database identification carried by the backup request, and obtain the data storage capacity or the available capacity of the storage servers. The operation and maintenance server can screen out at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server, store data to be backed up to the screened at least one main server, and back up the full slave servers and the incremental slave servers of the data to be backed up. The master server and the slave server perform full backup and incremental backup on the data to be backed up, so that the safety of the data can be effectively guaranteed, and the growing trend of the data storage capacity on each storage server can be better understood. The data to be backed up is stored to the main server with slow data growth or more available capacity, the overload condition of the main server is avoided, the utilization rate of each main server is balanced, and therefore data storage on a plurality of servers can be balanced.
In one embodiment, screening at least one master server from a plurality of master servers based on a data storage capacity of a full slave server, a data storage capacity of an incremental slave server, and an available capacity of each master server comprises: calculating according to the data storage capacity of the full slave server and the data storage capacity of the incremental slave server to obtain the storage capacity increase rate corresponding to the database identification; fitting according to the available capacity and the storage capacity increase rate of each main server to obtain the available duration of the available capacity of each main server; and screening at least one main server from the plurality of main servers according to the available capacity and available time of each main server.
The data storage capacity of the full slave server corresponds to the current total data storage capacity of the plurality of master servers, and may be equal or positively correlated. The data storage capacity of the incremental slave servers corresponds to the data storage capacity increased in the preset period in the plurality of master servers, and may be equal to or positively correlated with each other. Since the data storage amount increased in the plurality of master servers within the preset period is not stable, but has a certain increasing trend or a decreasing trend, the storage amount increase rate corresponding to the plurality of master servers can be calculated according to the data storage amount of the full slave servers and the data storage amount of the incremental slave servers. For example, the data storage amount of the previous period of the full slave server is Q1, and the data storage amount of the current period of the full slave server is Q2; the data storage amount of the increment slave server in the previous period is Z1, and the data storage amount of the increment slave server in the current period is Z2. The newly-increased data storage capacity of the full slave server in one period is Q2-Q1; the increment is the new data storage amount Z2-Z1 from the server in one period. According to the formula
The storage increase rate p can be calculated.
And fitting according to the available capacity and the storage capacity increase rate of each main server to obtain the available duration of the available capacity of each main server. For example, if the data storage amount of the incremental slave server is W, the storage amount increase rate is p, the available capacity is S, the available capacity can be used for n cycles, and the cycle is T, assuming that the storage amount increase rate p is constant, the available capacity can be used by the following formulaNumber of cycles n: (1+p) W + (1+p) 2 W+(1+p) 3 W…+(1+p) n W = S, and after n is solved, the available time length of the available capacity of the primary server is nT.
In one embodiment, screening at least one primary server from a plurality of primary servers according to the available capacity of each primary server for an available duration comprises: sequencing the plurality of main servers according to the available capacity available duration of each main server; and taking the main servers with the preset number in front after being sorted in the plurality of main servers as the screened main servers. After the available time length of the available capacity of each main server is obtained through calculation, the main servers can be sorted according to the available time length from long to short, the main servers with the available time length larger than the preset length are screened out, the main servers with the available time length in the front preset number can also be screened out, and the screened main servers are used as the main servers for storing the data to be backed up.
In one embodiment, the operation and maintenance server may make a high availability switch to the storage server. The high availability switching means that when the main server is detected to be failed, the main server is automatically switched to the high availability cluster. A highly available cluster refers to a group of computer nodes that provide a set of network resources to a user as a whole. After the master server is switched to the full slave server, the switched full slave server is equivalent to the master server, and the terminal can access the database on the switched full slave server and add, delete, change and inquire data in the database. In the process of replacing the master server with the switched total slave servers, data to be stored are also generated, and in the process of restoring the master server again, the newly-added stored data are required to be restored.
In one embodiment, the full slave server contains the compressed file package that has been fully backed up, and the method further comprises: receiving a recovery request uploaded by a terminal; the recovery request carries the database identifier and the recovery type; in response to the recovery request, searching a full number of slave servers and a plurality of master servers corresponding to the database identification; when the recovery type is a first type, sending the compressed file packets to be recovered in the full slave servers to a plurality of master servers, and analyzing the compressed file packets in the master servers; and when the recovery type is a second type, changing the full slave server into the master server, and analyzing the compressed file to be recovered in the full slave server.
The recovery request refers to a request for the terminal to request to recover the primary server again. When the recovery type is the first type, it indicates that the failure of the original primary server has been solved, and normal operation can be performed. The compressed file packets to be recovered in the total number of slave servers are sent to the plurality of master servers, and the compressed file packets in the plurality of master servers are analyzed, so that the recovered data can be obtained in the original master server. When the recovery type is the second type, it indicates that the failure of the original primary server cannot be solved, and the switched full backup server needs to be formally converted into the primary server. And the total slave server is changed into the master server, and the compressed file to be recovered in the total slave server is analyzed, so that the recovered data is directly obtained from the total slave server. Further, a new full backup server may be allocated for the newly transformed primary server.
In one embodiment, the recovery request further carries a timestamp, and sends the compressed file packets to be recovered from the full slave servers to the plurality of master servers, and analyzes the compressed file packets in the plurality of master servers, including: determining a time interval corresponding to the timestamp; acquiring a plurality of compressed file packages to be recovered from a full slave server; the backup time corresponding to the compressed file package to be restored is in the time interval; sending a plurality of compressed file packets to be restored to at least one main server; and analyzing the compressed file in the main server which receives the compressed file to be restored.
The timestamp refers to the time to which the primary server requested by the user was restored. For example, on day 2/month 1 of 2018, the primary server may be restored to day 1/month 1 of 2018. The data stored in the main server from the 2 nd 1 st 2018 to the 1 st 2018 is emptied, and the recovered main server is in the state of the main server at the 1 st 2018.
In one embodiment, the operation and maintenance server may receive a deployment request uploaded by a terminal; the deployment request carries a database application work order; the operation and maintenance server responds to the deployment request and extracts database attribute information from the database application work order; the operation and maintenance server creates a database instance and an initial database corresponding to the database instance; the operation and maintenance server deploys the initial database according to the database attribute information to obtain a target database; when the operation and maintenance server detects that the target database is deployed, an authorization account corresponding to the target database is created; and the operation and maintenance server sends the authorized account to the terminal so that the terminal can access the target database through the authorized account. The database attribute information includes backup attribute information such as backup frequency and backup retention days.
In one embodiment, deploying the initial database according to the database attribute information to obtain the target database includes: and starting database functions such as an automatic backup function, an automatic verification function, a high availability switching function and the like of the initial database to obtain the target database. In the running process of the target database, the started database function can continuously provide stable service guarantee for the target database. For example, when a failure of the main server is detected, the main server is switched to the high available cluster in time; for another example, by checking various check indexes in the data backup process, such as whether to start backup, whether backup is successful, and the like, timely processing can be performed when an error occurs. The system can automatically process the abnormal conditions, inform database management personnel of manual intervention, check and repair problems, and redeploy the database when needed. By providing a closed-loop database operation and maintenance flow, the stability of the deployed database is guaranteed.
In one embodiment, as shown in fig. 3, another data backup method is provided, which is described by taking the application of the method to the operation and maintenance server 104 in fig. 1 as an example, and includes the following steps:
And 304, acquiring corresponding data to be backed up based on the data to be backed up identifier.
And step 312, determining corresponding full slave servers according to the full slave server identifications, determining corresponding incremental slave servers according to the incremental slave server identifications, and determining corresponding master servers according to each master server identification.
And step 314, calculating according to the data storage capacity of the full slave server and the data storage capacity of the incremental slave server to obtain the storage capacity increase rate corresponding to the database identification.
And step 316, fitting according to the available capacity and the storage capacity increase rate of each main server to obtain the available duration of the available capacity of each main server.
And 318, sequencing the plurality of main servers according to the available capacity available time of each main server.
And 320, taking the main servers with the preset number in front after the sequencing in the plurality of main servers as the screened main servers.
And 322, storing the data to be backed up to the screened at least one main server.
And 324, compressing the data to be backed up stored in the screened at least one main server to obtain a compressed file package.
Step 326, backup the whole compressed file package to the full slave server, and incremental backup the compressed file package to the incremental slave server.
In the data backup method, after the operation and maintenance server obtains the backup request, the operation and maintenance server can search the full slave server, the incremental slave server and the plurality of main servers corresponding to the database identification carried by the backup request, and obtain the data storage capacity or the available capacity of the storage servers. The operation and maintenance server can screen out at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server, store data to be backed up to the screened at least one main server, and back up the full slave servers and the incremental slave servers of the data to be backed up. By carrying out full backup and incremental backup after the data to be backed up is converted into the compressed file package, the safety of the data can be effectively guaranteed, and the memory required from the server and the incremental backup to the increment can be reduced. Through better understanding the increasing trend of the data storage quantity on each storage server, the data to be backed up is stored to the main server with long available time, the overload condition of the main server is avoided, the utilization rate of each main server is balanced, and therefore data storage on a plurality of servers can be balanced.
It should be understood that although the steps in the flowcharts of fig. 2 and 3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not limited to being performed in the exact order illustrated and, unless explicitly stated herein, may be performed in other orders. Moreover, at least some of the steps in fig. 2 and 3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 4, there is provided a data backup apparatus 400 comprising: an obtaining module 402, configured to obtain a backup request; the backup request carries a database identifier and a data identifier to be backed up; acquiring corresponding data to be backed up based on the data to be backed up identifier; a searching module 404, configured to search a full slave server, an incremental slave server, and multiple master servers corresponding to the database identifier; a screening module 406, configured to screen at least one master server from the plurality of master servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers, and the available capacity of each master server; the backup module 408 is configured to store the data to be backed up in the screened at least one master server, and perform full backup on the data to be backed up to a full slave server and incremental backup on an incremental slave server.
In one embodiment, the filtering module 406 is further configured to calculate, according to the data storage amount of the full slave server and the data storage amount of the incremental slave server, a storage amount increase rate corresponding to the database identifier; fitting according to the available capacity and the storage capacity increase rate of each main server to obtain the available duration of the available capacity of each main server; and screening at least one main server from the plurality of main servers according to the available capacity and available time of each main server.
In one embodiment, the filtering module 406 is further configured to rank the plurality of primary servers according to an available capacity available duration of each primary server; and taking the main servers with the preset number in front after being sorted in the plurality of main servers as the screened main servers.
In one embodiment, the backup module 408 is further configured to store the data to be backed up to the screened at least one primary server; compressing the data to be backed up stored in the screened at least one main server to obtain a compressed file packet; backing up the whole compressed file package to a full slave server; and performing incremental backup on the compressed file package to an incremental slave server.
In one embodiment, the full slave server contains the compressed file package which is fully backed up, and the device further comprises a recovery module for receiving a recovery request uploaded by the terminal; the recovery request carries the database identifier and the recovery type; in response to the recovery request, searching a full number of slave servers and a plurality of master servers corresponding to the database identification; when the recovery type is a first type, sending the compressed file packets to be recovered in the full slave servers to a plurality of master servers, and analyzing the compressed file packets in the master servers; and when the recovery type is a second type, changing the full slave server into the master server, and analyzing the compressed file to be recovered in the full slave server.
In one embodiment, the recovery request further carries a timestamp, and the recovery module is further configured to determine a time interval corresponding to the timestamp; acquiring a plurality of compressed file packages to be recovered from a full slave server; the backup time corresponding to the compressed file package to be restored is in the time interval; sending a plurality of compressed file packets to be restored to at least one main server; and analyzing the compressed file in the main server which receives the compressed file to be restored.
For specific limitations of the data backup device, reference may be made to the above limitations of the data backup method, which is not described herein again. The modules in the data backup apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. For example, the server may be the operation and maintenance server 104 in fig. 1. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data such as a target instance table. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a data backup method.
It will be appreciated by those skilled in the art that the configuration shown in fig. 5 is a block diagram of only a portion of the configuration associated with the present application, and is not intended to limit the computing device to which the present application may be applied, and that a particular computing device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a computer device comprising a memory storing a computer program and a processor implementing the following steps when the processor executes the computer program: acquiring a backup request; the backup request carries a database identifier and a data identifier to be backed up; acquiring corresponding data to be backed up based on the data to be backed up identifier; searching a full slave server, an incremental slave server and a plurality of master servers corresponding to the database identification; screening at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server; and storing the data to be backed up to the screened at least one main server, backing up the data to be backed up to the full slave server in full and backing up the data to be backed up to the incremental slave server in incremental mode.
In one embodiment, the step of screening out at least one primary server from the plurality of primary servers based on the data storage capacity of the full secondary server, the data storage capacity of the incremental secondary server, and the available capacity of each primary server, as implemented by the processor executing the computer program, comprises the steps of: calculating according to the data storage capacity of the full slave server and the data storage capacity of the incremental slave server to obtain the storage capacity increase rate corresponding to the database identification; fitting according to the available capacity and the storage capacity increase rate of each main server to obtain the available duration of the available capacity of each main server; and screening at least one main server from the plurality of main servers according to the available capacity and available time of each main server.
In one embodiment, the step of filtering out at least one primary server from the plurality of primary servers based on an available capacity availability duration of each primary server when the computer program is executed by the processor comprises the steps of: sequencing the plurality of main servers according to the available capacity available duration of each main server; and taking the main servers with the preset number in front after being sorted in the plurality of main servers as the screened main servers.
In one embodiment, the step of locating a full slave server, an incremental slave server, and a plurality of master servers corresponding to the database identification, as implemented by the processor executing the computer program, comprises the steps of: determining a database instance identifier corresponding to the database identifier; acquiring a target instance table corresponding to the database instance identifier; searching a full slave server identifier, an incremental slave server identifier and a plurality of master server identifiers contained in a target instance table; and determining corresponding full slave servers according to the full slave server identifications, determining corresponding incremental slave servers according to the incremental slave server identifications, and determining corresponding master servers according to each master server identification.
In one embodiment, the step of storing the data to be backed up to the screened at least one master server, fully backing up the data to be backed up to the full slave server and incrementally backing up the data to be backed up to the incremental slave server when the processor executes the computer program includes the following steps: storing the data to be backed up to the screened at least one main server; compressing the data to be backed up stored in the screened at least one main server to obtain a compressed file packet; backing up the whole compressed file package to a full slave server; and performing incremental backup on the compressed file package to an incremental slave server.
In one embodiment, the full slave server contains the compressed file package that has been fully backed up, and the processor when executing the computer program further performs the steps of: receiving a recovery request uploaded by a terminal; the recovery request carries the database identifier and the recovery type; in response to the recovery request, searching a full number of slave servers and a plurality of master servers corresponding to the database identification; when the recovery type is a first type, sending the compressed file packets to be recovered in the full slave servers to a plurality of master servers, and analyzing the compressed file packets in the master servers; and when the recovery type is a second type, changing the full slave server into the master server, and analyzing the compressed file to be recovered in the full slave server.
In one embodiment, the recovery request further carries a timestamp, and the step of sending the full amount of compressed file packets to be recovered from the servers to the plurality of primary servers and analyzing the compressed file packets in the plurality of primary servers when the processor executes the computer program includes the steps of: determining a time interval corresponding to the timestamp; acquiring a plurality of compressed file packages to be recovered from a full slave server; the backup time corresponding to the compressed file package to be restored is in the time interval; sending a plurality of compressed file packets to be restored to at least one main server; and analyzing the compressed file in the main server which receives the compressed file to be restored.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring a backup request; the backup request carries a database identifier and a data identifier to be backed up; acquiring corresponding data to be backed up based on the data to be backed up identifier; searching a full slave server, an incremental slave server and a plurality of master servers corresponding to the database identification; screening out at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server; and storing the data to be backed up to the screened at least one main server, backing up the data to be backed up to the full slave server in full and backing up the data to be backed up to the incremental slave server in incremental mode.
In one embodiment, the computer program when executed by the processor, performs the step of screening at least one primary server from a plurality of primary servers based on a data storage capacity of a full secondary server, a data storage capacity of an incremental secondary server, and an available capacity of each primary server, comprising the steps of: calculating according to the data storage capacity of the full slave server and the data storage capacity of the incremental slave server to obtain the storage capacity increase rate corresponding to the database identification; fitting according to the available capacity and the storage capacity increase rate of each main server to obtain the available duration of the available capacity of each main server; and screening at least one main server from the plurality of main servers according to the available capacity and available time of each main server.
In one embodiment, the step of screening out at least one primary server from the plurality of primary servers based on an available capacity availability duration of each primary server when the computer program is executed by the processor comprises the steps of: sequencing the plurality of main servers according to the available capacity available duration of each main server; and taking the main servers with the preset number in front after being sorted in the plurality of main servers as the screened main servers.
In one embodiment, the computer program when executed by the processor, performs the step of locating a full slave server, an incremental slave server, and a plurality of master servers corresponding to the database identification, comprising the steps of: determining a database instance identifier corresponding to the database identifier; acquiring a target instance table corresponding to the database instance identifier; the target instance table comprises a full slave server identifier, an incremental slave server identifier and a plurality of master server identifiers; and determining corresponding full slave servers according to the full slave server identifications, determining corresponding incremental slave servers according to the incremental slave server identifications, and determining corresponding master servers according to each master server identification.
In one embodiment, the computer program when executed by the processor, performs the steps of storing data to be backed up to the screened at least one master server, and backing up the full amount of data to be backed up to the full amount slave server and backing up the data to be backed up to the incremental slave server in an incremental manner, including the steps of: storing the data to be backed up to the screened at least one main server; compressing the data to be backed up stored in the screened at least one main server to obtain a compressed file packet; backing up the whole compressed file package to a full slave server; and performing incremental backup on the compressed file package to an incremental slave server.
In one embodiment, the full slave server contains a full backed-up compressed package of files, and the computer program when executed by the processor further performs the steps of: receiving a recovery request uploaded by a terminal; the recovery request carries the database identifier and the recovery type; in response to the recovery request, searching a full number of slave servers and a plurality of master servers corresponding to the database identification; when the recovery type is a first type, sending the compressed file packets to be recovered in the full slave servers to a plurality of master servers, and analyzing the compressed file packets in the master servers; and when the recovery type is a second type, changing the full slave server into the master server, and analyzing the compressed file to be recovered in the full slave server.
In one embodiment, the recovery request further carries a timestamp, and the step of sending the full amount of compressed file packets to be recovered from the servers to the plurality of primary servers and parsing the compressed file packets in the plurality of primary servers, when the computer program is executed by the processor, includes the steps of: determining a time interval corresponding to the timestamp; acquiring a plurality of compressed file packages to be recovered from a full slave server; the backup time corresponding to the compressed file package to be restored is in the time interval; sending a plurality of compressed file packets to be restored to at least one main server; and analyzing the compressed file in the main server which receives the compressed file to be restored.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
All possible combinations of the technical features in the above embodiments may not be described for the sake of brevity, but should be considered as being within the scope of the present disclosure as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method of data backup, the method comprising:
acquiring a backup request; the backup request carries a database identifier and a data identifier to be backed up;
acquiring corresponding data to be backed up based on the data to be backed up identifier;
searching a full slave server, an incremental slave server and a plurality of master servers corresponding to the database identification;
screening out at least one main server from the plurality of main servers according to the data storage capacity of the full-amount slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server, and the method comprises the following steps: calculating according to the data storage capacity of the full slave server and the data storage capacity of the incremental slave server to obtain the storage capacity increase rate corresponding to the database identification; fitting according to the available capacity of each main server and the storage quantity growth rate to obtain the available duration of the available capacity of each main server; screening out at least one main server from the plurality of main servers according to the available duration of the available capacity of each main server;
and storing the data to be backed up to the screened at least one main server, and backing up the data to be backed up to the full slave server in full and backing up to the incremental slave server in incremental mode.
2. The method of claim 1, wherein the screening out at least one primary server from the plurality of primary servers according to an available duration of available capacity of each of the primary servers comprises:
sequencing the plurality of main servers according to the available duration of the available capacity of each main server;
and taking the main servers with the preset number in the front after being sorted in the plurality of main servers as the screened main servers.
3. The method of claim 1, wherein the locating a full slave server, an incremental slave server, and a plurality of master servers corresponding to the database identification comprises:
determining a database instance identifier corresponding to the database identifier;
acquiring a target instance table corresponding to the database instance identifier;
searching a full slave server identifier, an incremental slave server identifier and a plurality of master server identifiers contained in the target instance table;
and determining corresponding full slave servers according to the full slave server identifications, determining corresponding incremental slave servers according to the incremental slave server identifications, and determining corresponding master servers according to each master server identification.
4. The method according to any one of claims 1 to 3, wherein the storing the data to be backed up to the screened at least one master server, and the full backup and incremental backup of the data to be backed up to the full slave server to the incremental slave server comprise:
storing the data to be backed up to the screened at least one main server;
compressing the data to be backed up stored in the screened at least one main server to obtain a compressed file packet;
backing up the full amount of the compressed file package to the full amount slave server;
and backing up the compressed file package to the increment slave server in an increment mode.
5. The method of claim 4, wherein the full slave server contains a full backup of compressed bundles of files, the method further comprising:
receiving a recovery request uploaded by a terminal; the recovery request carries a database identifier and a recovery type;
in response to the recovery request, searching a full number of slave servers and a plurality of master servers corresponding to the database identification;
when the recovery type is a first type, sending the compressed file packets to be recovered in the full slave servers to the plurality of master servers, and analyzing the compressed file packets in the plurality of master servers;
and when the recovery type is a second type, changing the full slave server into a master server, and analyzing the compressed file to be recovered in the full slave server.
6. The method according to claim 5, wherein the recovery request further carries a timestamp, and the sending the full amount of compressed file packets to be recovered from the slave servers to the plurality of master servers and parsing the compressed file packets in the plurality of master servers comprises:
determining a time interval corresponding to the timestamp;
acquiring a plurality of compressed file packages to be recovered in the full slave server; the backup time corresponding to the compressed file package to be restored is in the time interval;
sending the plurality of compressed file packages to be restored to at least one main server;
and analyzing the compressed file in the main server which receives the compressed file to be restored.
7. A data backup apparatus, characterized in that the apparatus comprises:
the acquisition module is used for acquiring the backup request; the backup request carries a database identifier and a data identifier to be backed up; acquiring corresponding data to be backed up based on the data to be backed up identifier;
the searching module is used for searching a full slave server, an incremental slave server and a plurality of main servers corresponding to the database identification;
the screening module is used for screening at least one main server from the plurality of main servers according to the data storage capacity of the full slave servers, the data storage capacity of the incremental slave servers and the available capacity of each main server, and comprises: calculating according to the data storage capacity of the full slave server and the data storage capacity of the incremental slave server to obtain the storage capacity increase rate corresponding to the database identification; fitting according to the available capacity of each main server and the storage capacity growth rate to obtain the available duration of the available capacity of each main server; screening at least one main server from the plurality of main servers according to the available duration of the available capacity of each main server;
and the backup module is used for storing the data to be backed up to the screened at least one main server, backing up the data to be backed up to the full slave server in a full amount and backing up the data to be backed up to the incremental slave server in an incremental manner.
8. The apparatus of claim 7, wherein the filtering module is further configured to rank the plurality of primary servers according to an available duration of available capacity of each of the primary servers; and taking the main servers with the preset number in the front after being sorted in the plurality of main servers as the screened main servers.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor when executing the computer program performs the steps of the method according to any of claims 1 to 6.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810546827.0A CN108897638B (en) | 2018-05-31 | 2018-05-31 | Data backup method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810546827.0A CN108897638B (en) | 2018-05-31 | 2018-05-31 | Data backup method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108897638A CN108897638A (en) | 2018-11-27 |
| CN108897638B true CN108897638B (en) | 2023-03-21 |
Family
ID=64343858
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810546827.0A Active CN108897638B (en) | 2018-05-31 | 2018-05-31 | Data backup method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108897638B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112306745B (en) * | 2019-07-26 | 2023-04-07 | 中移(苏州)软件技术有限公司 | Backup method and device and storage medium |
| CN110851305B (en) * | 2019-11-20 | 2023-06-16 | 东北石油大学 | Backup storage method and device for science and technology project files |
| CN113138877B (en) * | 2020-01-17 | 2024-04-19 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for managing backup systems |
| CN111290882B (en) * | 2020-02-11 | 2024-02-09 | 北京小米松果电子有限公司 | Data file backup method, data file backup device and electronic equipment |
| CN111541766A (en) * | 2020-04-21 | 2020-08-14 | 西安电子科技大学 | Multi-server communication connection method |
| CN111930566A (en) * | 2020-07-28 | 2020-11-13 | 友谊时光科技股份有限公司 | Data backup method and device, electronic equipment and storage medium |
| CN112269690A (en) * | 2020-11-17 | 2021-01-26 | 珠海大横琴科技发展有限公司 | Data backup method and device |
| CN113468153A (en) * | 2020-12-01 | 2021-10-01 | 王跃 | Medical data management system based on big data |
| CN112579362A (en) * | 2020-12-29 | 2021-03-30 | 广州鼎甲计算机科技有限公司 | Backup method, system, device and storage medium for Shentong database cluster |
| CN115373903A (en) * | 2022-08-30 | 2022-11-22 | 广州鼎甲计算机科技有限公司 | Logic backup method and device, computer equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104407945A (en) * | 2014-12-26 | 2015-03-11 | 北京奇虎科技有限公司 | Data backup method, data backup device and data backup system |
| CN105786646A (en) * | 2016-02-25 | 2016-07-20 | 北京金山安全软件有限公司 | Data backup method and device and electronic equipment |
| CN107659652A (en) * | 2017-09-28 | 2018-02-02 | 郑州云海信息技术有限公司 | A kind of method and device of cloud backup |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008085708A2 (en) * | 2006-12-21 | 2008-07-17 | Boxicom, Inc. | Data backup system and method associated therewith |
-
2018
- 2018-05-31 CN CN201810546827.0A patent/CN108897638B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104407945A (en) * | 2014-12-26 | 2015-03-11 | 北京奇虎科技有限公司 | Data backup method, data backup device and data backup system |
| CN105786646A (en) * | 2016-02-25 | 2016-07-20 | 北京金山安全软件有限公司 | Data backup method and device and electronic equipment |
| CN107659652A (en) * | 2017-09-28 | 2018-02-02 | 郑州云海信息技术有限公司 | A kind of method and device of cloud backup |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108897638A (en) | 2018-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108897638B (en) | Data backup method and device, computer equipment and storage medium | |
| CN108874644B (en) | Data monitoring method and device, computer equipment and storage medium | |
| CN110647438B (en) | Event monitoring method and device, computer equipment and storage medium | |
| CN109032824B (en) | Database verification method, database verification device, computer equipment and storage medium | |
| CN108769212B (en) | Data synchronization method and device, computer equipment and storage medium | |
| CN107844343B (en) | Upgrading system and method for complex server application system | |
| CN110764700B (en) | Data storage method and device, computer equipment and storage medium | |
| CN109992354B (en) | Container processing method, device, main body server, system and storage medium | |
| CN109739815B (en) | File processing method, system, device, equipment and storage medium | |
| CN108959385B (en) | Database deployment method, device, computer equipment and storage medium | |
| CN111143133B (en) | Virtual machine backup method and backup virtual machine recovery method | |
| CN108322533A (en) | Configuration and synchronization method between distributed type assemblies node based on operation log | |
| CN109460252B (en) | Configuration file processing method and device based on git and computer equipment | |
| CN110309109B (en) | Data monitoring method, device, computer equipment and storage medium | |
| CN108965383B (en) | File synchronization method and device, computer equipment and storage medium | |
| CN105550229A (en) | Method and device for repairing data of distributed storage system | |
| CN110781214A (en) | Database reading and writing method and device, computer equipment and storage medium | |
| CN111026767B (en) | Block chain data storage method and device and hardware equipment | |
| CN110750267A (en) | Service information updating method and device, computer equipment and storage medium | |
| CN112632375B (en) | Session information processing method, server and storage medium | |
| CN111078559A (en) | Method, device, medium and computer equipment for extracting function call in java code | |
| CN110727698A (en) | Database access method and device, computer equipment and storage medium | |
| CN103716384A (en) | Method and device for realizing cloud storage data synchronization in cross-data-center manner | |
| CN111767173A (en) | Network equipment data processing method and device, computer equipment and storage medium | |
| CN110737719A (en) | Data synchronization method, device, equipment 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |