CN113391954A - High-availability data backup method and system based on distributed architecture - Google Patents
High-availability data backup method and system based on distributed architecture Download PDFInfo
- Publication number
- CN113391954A CN113391954A CN202110658850.0A CN202110658850A CN113391954A CN 113391954 A CN113391954 A CN 113391954A CN 202110658850 A CN202110658850 A CN 202110658850A CN 113391954 A CN113391954 A CN 113391954A
- Authority
- CN
- China
- Prior art keywords
- backup
- server
- data
- backup server
- agent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 21
- 230000005540 biological transmission Effects 0.000 claims description 6
- 230000005856 abnormality Effects 0.000 claims 1
- 230000002159 abnormal effect Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a high-availability data backup method and a system based on a distributed architecture, wherein the method comprises the following steps: step S1, registering all backup servers to a main server, wherein all the backup servers registered to the main server form a backup service pool; step S2, when executing the backup task, the agent sends a backup server acquisition request to the main server to acquire the backup server executing the backup task; step S3, the main server deduces the backup server of the current backup task according to the backup server information and returns to the agent of the backup task; step S4, the agent connects the corresponding backup server in the backup service pool according to the return information of the main server, and sends the backup data to the corresponding backup server; in step S5, the backup server writes the backup data into the backup data pool.
Description
Technical Field
The invention relates to the technical field of computer disaster recovery backup, in particular to a high-availability data backup method and system based on a distributed architecture.
Background
The existing traditional data backup method generally has a backup rule processed by a designated backup server, the proxy and the backup server are in a one-to-one relationship, the fixed corresponding relationship causes a single point fault to exist in the backup server, when the backup server is abnormal, data backup can not be carried out, the backup data is generally stored on the backup server, the service and the data are tightly coupled, and the abnormal backup server can cause the backup data to be unusable.
Disclosure of Invention
In order to overcome the defects in the prior art, the present invention provides a method and a system for backing up highly available data based on a distributed architecture, so as to solve the problems of single point failure of a backup server and tight coupling of backup service and backup data in the conventional data backup system.
To achieve the above object, the present invention provides a method for backing up highly available data based on a distributed architecture, which includes the following steps:
step S1, registering all backup servers to a main server, wherein all the backup servers registered to the main server form a backup service pool;
step S2, when executing the backup task, the agent sends a backup server acquisition request to the main server to acquire the backup server executing the backup task;
step S3, the main server deduces the backup server of the current backup task according to the backup server acquisition request, and returns to the proxy of the backup task;
step S4, the agent connects the corresponding backup server in the backup service pool according to the return information of the main server, and sends the backup data to the corresponding backup server;
in step S5, the backup server writes the backup data into the backup data pool.
Preferably, in step S1, the primary server receives the registration of each backup server, and records and updates the backup server list information.
Preferably, the backup server obtaining request includes the IP of the agent and the IP of the backup server currently allocated.
Preferably, in step S3, the main server deduces the backup server of the current backup task to return to the proxy according to the currently allocated backup server IP in the received backup server acquisition request and the recorded backup server list information.
Preferably, in step S3, the main server queries whether the backup server list exists according to the currently allocated backup server information, if so, returns relevant information to the agent, and if not, the backup server obtains that the backup server in the request is abnormal, and the main server re-elects a backup server and returns the IP and data transmission port of the backup server that is elected.
Preferably, the backup data pool is comprised of a plurality of storage pools and storage volumes.
Preferably, in step S5, after the backup server receives the backup data sent by the agent, the backup data is written to the storage volume through the ISCSI.
In order to achieve the above object, the present invention further provides a highly available data backup system based on a distributed architecture, including:
the main server is used for receiving the registration request of each backup server and recording and updating the list information of the backup servers; when a backup server acquisition request sent by an agent is received, a backup server of the current backup task is promoted according to the backup server acquisition request, and the backup server is returned to the agent;
the agent sends a backup server acquisition request to the main server to acquire a backup server executing the backup task when executing the backup task; when receiving the return information of the main server, connecting the corresponding backup server according to the return information of the main server, and sending backup data to the corresponding backup server;
the backup service pool is composed of a plurality of backup servers registered in the main server, and each backup server writes backup data into the backup data pool after receiving the backup data sent by the agent;
and the backup data pool is used for storing the backup data written by each backup server.
Preferably, the main server deduces the backup server of the current backup task to return to the agent according to the currently allocated backup server information in the received backup server acquisition request and the recorded backup server list information.
Preferably, the backup data pool is composed of a plurality of storage pools and storage volumes, and when the backup server receives the backup data sent by the agent, the backup data is written to the storage volumes through the ISCSI.
Compared with the prior art, the high-availability data backup method and system based on the distributed architecture solve the single-point fault of the backup server by constructing the backup service pool and decouple the backup service and the backup data in a remote mounting mode, thereby solving the problems of the single-point fault of the backup server and the tight coupling of the backup service and the backup data in the conventional data backup system.
Drawings
FIG. 1 is a flowchart illustrating steps of a method for backing up highly available data based on a distributed architecture according to the present invention;
FIG. 2 is a system architecture diagram of a highly available data backup system based on a distributed architecture according to the present invention;
fig. 3 is an architecture diagram of a highly available data backup system based on a distributed architecture according to an embodiment of the present invention.
Detailed Description
Other advantages and capabilities of the present invention will be readily apparent to those skilled in the art from the present disclosure by describing the embodiments of the present invention with specific embodiments thereof in conjunction with the accompanying drawings. The invention is capable of other and different embodiments and its several details are capable of modification in various other respects, all without departing from the spirit and scope of the present invention.
Fig. 1 is a flowchart illustrating steps of a method for backing up highly available data based on a distributed architecture according to the present invention. As shown in fig. 1, the present invention provides a method for backing up highly available data based on a distributed architecture, which includes the following steps:
step S1, register all backup servers to a Master server Master, and all the backup servers registered in the Master server form a backup service pool.
In the invention, the Master server has the main functions of serving as service discovery of backup servers and service monitoring of each backup server, specifically, receiving registration requests of each backup server, recording information of each backup server IP and data transmission ports thereof, and when monitoring that a certain backup server is abnormal, updating the backup server in a backup server list (deleting the information of the backup server from the backup server list) to provide corresponding backup server information for a backup task.
Each Backup server registered in the Master server forms a Backup service Pool, each node in the Pool is a Backup server, and the nodes in the Pool are registered on the Master server and managed by the Master server.
Step S2, when executing the backup task, the agent sends a backup server acquisition request to the Master server Master to acquire a backup server executing the backup task, where the backup server acquisition request at least includes an agent server IP and a currently allocated backup server IP.
In the invention, the agent is an agent for data backup, and the agent has the main functions of sending a request to the main server, obtaining backup server information from the main server Master and then sending backup data to the corresponding backup server. Generally, a backup rule is composed of a plurality of backup tasks, each backup task is processed by which backup server is determined by a main server, if a backup rule is allocated to a backup server, the backup server currently allocated is preferentially selected next time the main server elects, and only when the backup server currently allocated is abnormal, the main server reallocates other backup servers, so that the sent backup server acquisition request includes not only a proxy server IP but also a backup server IP currently allocated. That is, when the agent receives the backup task issuing notification and executes the backup task, the agent sends a backup server acquisition request at least including the agent server IP and the currently allocated backup server IP to the Master server, so as to acquire the backup server executing the backup task.
And step 3, the Master server Master promotes the backup server of the current backup task according to the backup server information in the obtained backup server acquisition request, and returns to the proxy of the backup task.
That is to say, when executing a certain backup task, the agent for data backup will first send a corresponding backup server acquisition request to the Master server Master according to the backup task, the Master server Master will deduce the backup server of the current backup task according to the backup server information, and return to the agent, where the returned information includes the IP and data transmission port of the deduced backup server, specifically, because the backup server acquisition request sent by the agent includes the currently allocated backup server information, the Master server Master will inquire whether the backup server list exists according to the backup server information, if the backup server list exists, return relevant information to the agent, if the backup server in the request sent by the agent is abnormal, that is, not in the backup server list of the Master server, the Master server will again deduce a backup server (generally speaking, a backup server with a small number of backup tasks), and returns the IP and data transfer ports of the backup server being promoted.
And step S4, the agent connects with the corresponding backup server according to the return information of the Master server and sends the backup data to the corresponding backup server.
In step S5, the backup server writes the backup data into the backup data pool.
In a specific embodiment of the present invention, the backup data Pool is storage Pool, and is composed of a plurality of storage pools and storage volumes, and when the backup server receives the backup data sent by the agent, the backup data is written to the storage volumes through an ISCSI (Internet small computer system interface).
Fig. 2 is a system architecture diagram of a highly available data backup system based on a distributed architecture according to the present invention. As shown in fig. 2, the present invention provides a highly available data backup system based on a distributed architecture, which includes:
a main server 20, configured to receive registration requests of the backup servers, and record and update backup server list information; and when receiving a backup server acquisition request sent by the agent, the backup server of the current backup task is promoted according to the backup server information and returned to the agent.
In the embodiment of the present invention, the main server 20, i.e. the Master, has a main function of serving as service discovery of the backup servers and service monitoring of each backup server, and specifically, the main server 20 receives a registration request of each backup server, records and updates backup server list information (in which information such as IP of each backup server and data transmission port thereof is recorded), so as to provide corresponding backup server information for the backup task. When a certain agent executes a certain backup task, a corresponding backup server acquisition request is sent to a Master server Master according to the backup task, the Master server Master infers a backup server of the current backup task according to backup server information in the backup server acquisition request, namely, whether the backup server information currently distributed in the backup server acquisition request exists in a backup server list is inquired, if the backup server information exists, relevant information is returned to the agent, if the backup server information in the request sent by the agent is abnormal, namely, the backup server information is not in the backup server list of the Master server Master, the Master server can again infer a backup server (generally, the backup server with few backup tasks is inferred), and the IP and the data transmission port of the inferred backup server are returned to the agent.
The agent 21, when executing the backup task, sends a backup server acquisition request to the main server 20 to acquire a backup server executing the backup task; when receiving the return information of the main server 20, connecting the corresponding backup server according to the return information of the main server Master, and sending the backup data to the corresponding backup server, where the backup server acquisition request at least includes the proxy server IP and the currently allocated backup server IP.
Specifically, the agent 21, i.e. agent, is an agent for data backup, and its main function is to send a request to the main server and send backup data to the corresponding backup server after obtaining backup server information from the main server Master. Generally, a backup rule is composed of a plurality of backup tasks, each backup task is processed by which backup server is determined by a main server, if a backup rule is allocated to a backup server, the backup server currently allocated is preferentially selected next time the main server elects, and only when the backup server currently allocated is abnormal, the main server reallocates other backup servers, so that the sent backup server acquisition request includes not only a proxy server IP but also a backup server IP currently allocated. That is, when the agent receives the backup task issuing notification and executes the backup task, the agent first sends a backup server acquisition request at least including the agent server IP and the currently allocated backup server IP to the Master server Master according to the backup task to acquire the backup server executing the backup task, when receiving the return information of the Master server, the agent sends a connection request to the corresponding backup server according to the return information to establish connection, and after establishing connection, the agent sends backup data to the backup server.
And a backup service pool 22, which is composed of a plurality of backup servers registered in the main server 20, and each backup server writes the backup data into the backup data pool after receiving the backup data transmitted by the agent 21.
That is, each Backup server sends a registration request to the main server 20 and registers in the main server 20, and all the Backup servers registered in the main server 20 form a Backup service Pool Backup Pool, that is, each Backup server serving as a node in the Pool is registered on the main server Master, managed by the main server Master, establishes a connection with an agent when receiving a connection request of the agent, and writes Backup data sent by the agent to a storage volume of the Backup data Pool through ISCSI after receiving the Backup data.
The backup data pool 23 is composed of a plurality of storage pools and storage volumes, and is used for storing backup data written by each backup server in the backup service pool.
Examples
Fig. 3 is an architecture diagram of a highly available data backup system based on a distributed architecture according to an embodiment of the present invention. In the present embodiment, the highly available data Backup system is composed of Master, agent, Backup Pool, and storage Pool. The Master is mainly used for discovering the service of the backup server, recording and updating the list information of the backup server and providing the backup server information for the backup task; agent is an agent for data backup, and the main function is to send backup data to a backup server after obtaining backup server information from Master; backup Pool is a Backup service Pool and consists of a plurality of Backup servers, and all nodes in the Pool are registered on a Master and managed by the Master; the storage Pool is a backup data Pool, which is composed of a plurality of storage pools and storage volumes and is used for storing backup data. The high-availability data backup process comprises the following steps:
the method comprises the following steps: the backup server registers with the Master.
Step two: and the Master updates the backup server information.
Step three: and the proxy acquires a backup server for executing the current backup task from the Master.
Step four: and the Master promotes the backup server of the current backup task according to the backup server information and returns the backup server to the agent.
Step five: the agent is connected with the backup server and sends backup data.
Step six: the backup server calls the ISCSI to write the backup data to the storage volume.
The foregoing embodiments are merely illustrative of the principles and utilities of the present invention and are not intended to limit the invention. Modifications and variations can be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the present invention. Therefore, the scope of the invention should be determined from the following claims.
Claims (10)
1. A high-availability data backup method based on a distributed architecture comprises the following steps:
step S1, registering all backup servers to a main server, wherein all the backup servers registered to the main server form a backup service pool;
step S2, when executing the backup task, the agent sends a backup server acquisition request to the main server to acquire the backup server executing the backup task;
step S3, the main server deduces the backup server of the current backup task according to the backup server acquisition request, and returns to the proxy of the backup task;
step S4, the agent connects the corresponding backup server in the backup service pool according to the return information of the main server, and sends the backup data to the corresponding backup server;
in step S5, the backup server writes the backup data into the backup data pool.
2. The method for backing up highly available data based on distributed architecture as claimed in claim 1, wherein: in step S1, the primary server receives the registration of each backup server, and records and updates the backup server list information.
3. The method for backing up highly available data based on distributed architecture as claimed in claim 2, wherein: the backup server acquisition request comprises the IP of the agent and the IP of the backup server which is distributed currently.
4. The method for backing up highly available data based on distributed architecture as claimed in claim 3, wherein: in step S3, the main server pushes the backup server of the current backup task back to the agent according to the currently allocated backup server IP in the received backup server acquisition request and the recorded backup server list information.
5. The method for backing up highly available data based on distributed architecture as claimed in claim 4, wherein: in step S3, the main server queries whether the backup server list exists according to the currently allocated backup server information, returns relevant information to the agent if the backup server list exists, and if the backup server list does not exist, the backup server obtains the backup server abnormality in the request, and the main server re-elects a backup server and returns the IP and data transmission port of the backup server that is elected.
6. The method for backing up highly available data based on distributed architecture as claimed in claim 1, wherein: the backup data pool is composed of a plurality of storage pools and storage volumes.
7. The method for backing up highly available data based on distributed architecture as claimed in claim 5, wherein: in step S5, after the backup server receives the backup data sent by the agent, the backup data is written to the storage volume through the ISCSI.
8. A highly available data backup system based on a distributed architecture, comprising:
the main server is used for receiving the registration request of each backup server and recording and updating the list information of the backup servers; when a backup server acquisition request sent by an agent is received, a backup server of the current backup task is promoted according to the backup server acquisition request, and the backup server is returned to the agent;
the agent sends a backup server acquisition request to the main server to acquire a backup server executing the backup task when executing the backup task; when receiving the return information of the main server, connecting the corresponding backup server according to the return information of the main server, and sending backup data to the corresponding backup server;
the backup service pool is composed of a plurality of backup servers registered in the main server, and each backup server writes backup data into the backup data pool after receiving the backup data sent by the agent;
and the backup data pool is used for storing the backup data written by each backup server.
9. The distributed architecture-based highly available data backup system of claim 8, wherein: and the main server deduces the backup server of the current backup task to return to the agent according to the currently allocated backup server information in the received backup server acquisition request and the recorded backup server list information.
10. The distributed architecture-based highly available data backup system of claim 8, wherein: and the backup data pool consists of a plurality of storage pools and a storage volume, and when the backup server receives the backup data sent by the agent, the backup data is written to the storage volume through ISCSI.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110658850.0A CN113391954A (en) | 2021-06-15 | 2021-06-15 | High-availability data backup method and system based on distributed architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110658850.0A CN113391954A (en) | 2021-06-15 | 2021-06-15 | High-availability data backup method and system based on distributed architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113391954A true CN113391954A (en) | 2021-09-14 |
Family
ID=77620982
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110658850.0A Pending CN113391954A (en) | 2021-06-15 | 2021-06-15 | High-availability data backup method and system based on distributed architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113391954A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558215A (en) * | 2018-12-10 | 2019-04-02 | 深圳市木浪云数据有限公司 | Backup method, restoration methods, device and the backup server cluster of virtual machine |
| CN109901951A (en) * | 2019-03-05 | 2019-06-18 | 山东浪潮云信息技术有限公司 | A kind of storage system and method for ceph company-data |
| CN110908833A (en) * | 2019-11-07 | 2020-03-24 | 苏州浪潮智能科技有限公司 | Data backup method, device and equipment and computer readable storage medium |
| CN111756841A (en) * | 2020-06-23 | 2020-10-09 | 中国平安财产保险股份有限公司 | Service implementation method, device, equipment and storage medium based on micro-service cluster |
-
2021
- 2021-06-15 CN CN202110658850.0A patent/CN113391954A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558215A (en) * | 2018-12-10 | 2019-04-02 | 深圳市木浪云数据有限公司 | Backup method, restoration methods, device and the backup server cluster of virtual machine |
| CN109901951A (en) * | 2019-03-05 | 2019-06-18 | 山东浪潮云信息技术有限公司 | A kind of storage system and method for ceph company-data |
| CN110908833A (en) * | 2019-11-07 | 2020-03-24 | 苏州浪潮智能科技有限公司 | Data backup method, device and equipment and computer readable storage medium |
| CN111756841A (en) * | 2020-06-23 | 2020-10-09 | 中国平安财产保险股份有限公司 | Service implementation method, device, equipment and storage medium based on micro-service cluster |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4433967B2 (en) | Heartbeat device via remote duplex link on multisite and method of using the same | |
| JP4637842B2 (en) | Fast application notification in clustered computing systems | |
| US7533181B2 (en) | Apparatus, system, and method for data access management | |
| US8615578B2 (en) | Using a standby data storage system to detect the health of a cluster of data storage servers | |
| US7447933B2 (en) | Fail-over storage system | |
| US8380951B1 (en) | Dynamically updating backup configuration information for a storage cluster | |
| KR102038527B1 (en) | Distributed cluster management system and method for thereof | |
| US7228352B1 (en) | Data access management system in distributed processing system | |
| EP2597818A1 (en) | Cluster management system and method | |
| US11184435B2 (en) | Message transmission method and apparatus in cluster file system | |
| CN106506490A (en) | A kind of Distributed Calculation control method and distributed computing system | |
| JP2006127201A (en) | Storage system and conduction confirmation method | |
| US7499987B2 (en) | Deterministically electing an active node | |
| JP4106014B2 (en) | Communication method and program in multi-node data processing system including at least one non-volatile data storage device | |
| US7805503B2 (en) | Capability requirements for group membership | |
| US8301750B2 (en) | Apparatus, system, and method for facilitating communication between an enterprise information system and a client | |
| US20110238959A1 (en) | Distributed controller, distributed processing system, and distributed processing method | |
| US8683154B2 (en) | Computer system and system control method | |
| WO2023134614A1 (en) | Processing of transaction | |
| CN113391954A (en) | High-availability data backup method and system based on distributed architecture | |
| US8074109B1 (en) | Third-party voting to select a master processor within a multi-processor computer | |
| CN112860480B (en) | Double-live storage system and data processing method thereof | |
| JP2007249659A (en) | System-switching method, computer system therefor, and program | |
| US7587466B2 (en) | Method and computer system for information notification | |
| CN113890875B (en) | Task allocation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210914 |
|
| RJ01 | Rejection of invention patent application after publication |