CN116244109A - Data backup method and device, server and readable storage medium - Google Patents

Data backup method and device, server and readable storage medium Download PDF

Info

Publication number
CN116244109A
CN116244109A CN202111516343.XA CN202111516343A CN116244109A CN 116244109 A CN116244109 A CN 116244109A CN 202111516343 A CN202111516343 A CN 202111516343A CN 116244109 A CN116244109 A CN 116244109A
Authority
CN
China
Prior art keywords
storage path
data
server
target storage
backup
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
Application number
CN202111516343.XA
Other languages
Chinese (zh)
Inventor
蒋思慧
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chengdu TD Tech Ltd
Original Assignee
Chengdu TD Tech Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Chengdu TD Tech Ltd filed Critical Chengdu TD Tech Ltd
Priority to CN202111516343.XA priority Critical patent/CN116244109A/en
Publication of CN116244109A publication Critical patent/CN116244109A/en
Pending legal-status Critical Current

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
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application provides a data backup method, a device, a server and a readable storage medium, wherein the method comprises the following steps: the first interface server receives a first backup request sent by the first node server, and sends a first target storage path acquisition request to the first backup server. The first backup server acquires a first target storage path pre-stored in the storage path database according to the received first target storage path acquisition request, and sends the first target storage path to the first interface server. The first interface server receives a first target storage path, and stores the data which is not successfully backed up by the second interface server in the first data to be backed up carried by the first backup request into the NAS of the backup server corresponding to the first target storage path. In the technical scheme, when the data recovery processing is carried out on the first data to be backed up later, only one data is needed to be obtained in one storage address, so that the efficiency of the data recovery processing is improved.

Description

Data backup method and device, server and readable storage medium
Technical Field
The present invention relates to the field of data management technologies, and in particular, to a data backup method, a data backup device, a server, and a readable storage medium.
Background
Data backup is the basis of disaster recovery, which is the process of copying all or part of data sets from the hard disk or array of an application host to other storage media in order to prevent the data loss caused by misoperation or system failure of the system. The data can be timely recovered after being lost, so that the loss caused by the data loss is effectively reduced, and the safety of the data is improved. Therefore, how to backup data is very important.
At present, after a system receives a backup request of a user, one node in a system cluster is selected as a master node, other nodes are slave nodes, and the master node informs the other slave nodes of the start of the reach tool through the reach tool of the master node, so that all nodes acquire data to be backed up from a database of the master node through the reach tool of the master node, and the data to be backed up is transmitted to a server side for backup through a Man-Machine Language (MML) interface.
However, in the backup process, the MML interface cannot work normally, and when the backup needs to be continued by using other MML interfaces, the consistency of the storage paths of the two backup processes cannot be ensured, so that the subsequent recovery efficiency of the backed-up data is lower.
Disclosure of Invention
The application provides a data backup method, device, server and readable storage medium, which are used for solving the problem that in the prior art, an MML interface cannot work normally in the backup process, and when other MML interfaces are needed to be used for continuing backup, the consistency of storage paths in the two backup processes cannot be ensured, so that the subsequent recovery efficiency of the backed-up data is lower.
In a first aspect, an embodiment of the present application provides a data backup method, which is applied to a first interface server in an interface server cluster, where the interface server cluster includes the first interface server and a second interface server, and the method includes:
receiving a first backup request sent by a first node server, wherein the first backup request comprises an identifier of first data to be backed up and data which is not backed up successfully by a second interface server in the first data to be backed up;
a first target storage path acquisition request is sent to any backup server in a backup server cluster, wherein the first target storage path acquisition request is used for acquiring a first target storage path stored in a storage path database in advance, the first target storage path acquisition request comprises an identifier of the first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up;
Receiving the first target storage path returned by the backup server;
and storing the data which is not successfully backed up to a network attached storage NAS of a backup server corresponding to the first target storage path.
In one possible design of the first aspect, the method further comprises:
receiving a second backup request sent by a second node server, wherein the second backup request comprises second data to be backed up and an identifier of the second data to be backed up;
according to the identification of the second data to be backed up, a second target storage path acquisition request is sent to any backup server in the backup server cluster, wherein the second target storage path acquisition request is used for acquiring a second target storage path, and the second target storage path is used for storing the second data to be backed up;
receiving the second target storage path returned by the backup server;
and storing the second data to be backed up to the NAS of the first backup server corresponding to the second target storage path.
Optionally, after the storing the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path, the method further includes:
Receiving a first data recovery request sent by the second node server, wherein the first data recovery request comprises an identifier of first target data;
acquiring the first target data from the NAS corresponding to the first target path according to the first target path corresponding to the identifier of the first target data;
and sending the first target data to the second node server.
In another possible design of the first aspect, before the storing the data that is not backed up successfully in the NAS of the backup server corresponding to the first target storage path, the method further includes:
sending a file system acquisition request to a backup server corresponding to the first target storage path, wherein the file system acquisition request is used for acquiring a first file system corresponding to the second interface server in the backup server;
receiving the first file system sent by the backup server;
correspondingly, the storing the data that is not successfully backed up in the NAS of the backup server corresponding to the first target storage path includes:
and mounting the first file system, and storing the unsuccessfully backed up data to the NAS corresponding to the first target storage path by using the mounted first file system.
Optionally, before the receiving the second backup request sent by the second node server, the method further includes:
sending a file system establishment request to the first backup server, wherein the file system establishment request is used for indicating the first backup server to establish a second file system corresponding to the first interface server in the first backup server;
receiving the second file system sent by the first backup server;
correspondingly, the storing the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path includes:
and mounting the second file system, and storing second data to be backed up into the NAS corresponding to the second target storage path by using the mounted second file system.
In a second aspect, an embodiment of the present application provides a data backup method, which is applied to a first backup server in a backup server cluster, where the method includes:
receiving a first target storage path acquisition request sent by a first interface server in an interface server cluster, wherein the first target storage path acquisition request is used for acquiring a first target storage path stored in a storage path database in advance, the first target storage path acquisition request comprises an identifier of first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up;
Acquiring the first target storage path pre-stored in a storage path database according to the first target storage path acquisition request;
and sending the first target storage path to the first interface server.
In one possible design of the second aspect, the method further comprises:
receiving a second target storage path acquisition request sent by the first interface server, wherein the second target storage path acquisition request is used for acquiring a second target storage path, and the second target storage path is used for storing second data to be backed up;
generating a second target storage path according to the second target storage path acquisition request;
and storing the second target storage path into the storage path database and sending the second target storage path to the first interface server.
Optionally, before the receiving the second target storage path obtaining request sent by the first interface server, the method further includes:
receiving a file system establishment request sent by the first interface server, wherein the file system establishment request is used for establishing a second file system corresponding to the first node server in the first backup server;
When the second file system does not exist, the second file system is built, and the second file system is sent to the first interface server;
and when the second file system exists, sending the second file system to the first interface server.
In another possible design of the second aspect, before the sending the first target storage path to the first interface server, the method further includes:
receiving a file system acquisition request sent by the first interface server, wherein the file system acquisition request is used for acquiring a first file system corresponding to the second node server in the first backup server;
and sending the first file system to the first interface server.
In a third aspect, an embodiment of the present application provides a data backup device, which is applied to a first interface server in an interface server cluster, where the interface server cluster includes the first interface server and a second interface server, and the device includes:
the receiving module is used for receiving a first backup request sent by a first node server, wherein the first backup request comprises an identifier of first data to be backed up and data which is not backed up successfully by a second interface server in the first data to be backed up;
The system comprises a sending module, a backup server cluster and a storage path database, wherein the sending module is used for sending a first target storage path acquisition request to any backup server in the backup server cluster, the first target storage path acquisition request is used for acquiring a first target storage path pre-stored in the storage path database, the first target storage path acquisition request comprises an identifier of first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up;
the receiving module is used for receiving the first target storage path returned by the backup server;
and the processing module is used for storing the data which is not successfully backed up to the network attached storage NAS of the backup server corresponding to the first target storage path.
In one possible design of the third aspect, the receiving module is further configured to receive a second backup request sent by a second node server, where the second backup request includes second data to be backed up and an identifier of the second data to be backed up;
the sending module is further configured to send a second target storage path acquisition request to any backup server in the backup server cluster according to the identifier of the second data to be backed up, where the second target storage path acquisition request is used to acquire a second target storage path, and the second target storage path is used to store the second data to be backed up;
The receiving module is further configured to receive the second target storage path returned by the backup server;
and the processing module is further configured to store the second data to be backed up to a NAS of the first backup server corresponding to the second target storage path.
Optionally, after the second data to be backed up is stored in the NAS of the first backup server corresponding to the second target storage path, the receiving module is further configured to receive a first data recovery request sent by the second node server, where the first data recovery request includes an identifier of the first target data;
the processing module is further configured to obtain, according to a first target path corresponding to the identifier of the first target data, the first target data from a NAS corresponding to the first target path;
the sending module is further configured to send the first target data to the second node server.
In another possible design of the third aspect, before the storing the data that is not backed up successfully in the NAS of the backup server corresponding to the first target storage path, the sending module is further configured to send a file system acquisition request to the backup server corresponding to the first target storage path, where the file system acquisition request is used to acquire a first file system corresponding to the second interface server in the backup server;
The receiving module is further configured to receive the first file system sent by the backup server;
correspondingly, the processing module is specifically configured to:
and mounting the first file system, and storing the unsuccessfully backed up data to the NAS corresponding to the first target storage path by using the mounted first file system.
Optionally, before the receiving the second backup request sent by the second node server, the sending module is further configured to send a file system establishment request to the first backup server, where the file system establishment request is used to instruct the first backup server to establish a second file system corresponding to the first interface server in the first backup server;
the receiving module is further configured to receive the second file system sent by the first backup server;
correspondingly, the processing module is specifically configured to:
and mounting the second file system, and storing second data to be backed up into the NAS corresponding to the second target storage path by using the mounted second file system.
In a fourth aspect, an embodiment of the present application provides a data backup device, which is applied to a first backup server in a backup server cluster, where the device includes:
The receiving module is used for receiving a first target storage path acquisition request sent by a first interface server in the interface server cluster, wherein the first target storage path acquisition request is used for acquiring a first target storage path stored in a storage path database in advance, the first target storage path acquisition request comprises an identifier of the first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up;
the processing module is used for acquiring the first target storage path pre-stored in a storage path database according to the first target storage path acquisition request;
and the sending module is used for sending the first target storage path to the first interface server.
In one possible design of the fourth aspect, the receiving module is further configured to receive a second target storage path acquisition request sent by the first interface server, where the second target storage path acquisition request is used to acquire a second target storage path, and the second target storage path is used to store second data to be backed up;
the processing module is further configured to generate a second target storage path according to the second target storage path acquisition request;
The sending module is further configured to store the second target storage path to the storage path database, and send the second target storage path to the first interface server.
Optionally, before receiving the second target storage path obtaining request sent by the first interface server, the receiving module is further configured to receive a file system establishment request sent by the first interface server, where the file system establishment request is used to establish a second file system corresponding to the first node server in the first backup server;
the sending module is further configured to establish the second file system when the second file system does not exist, and send the second file system to the first interface server;
the sending module is further configured to send the second file system to the first interface server when the second file system exists.
In another possible design of the fourth aspect, before the sending the first target storage path to the first interface server, the receiving module is further configured to receive a file system acquisition request sent by the first interface server, where the file system acquisition request is used to acquire a first file system corresponding to the second node server in the first backup server;
The sending module is further configured to send the first file system to the first interface server.
In a fifth aspect, embodiments of the present application provide a server, including: a processor, a transceiver, a memory and computer program instructions stored on the memory and executable on the processor for implementing the first aspect, the second aspect and the methods provided in each possible design of the first aspect and the second aspect when the computer program instructions are executed by the processor.
In a sixth aspect, embodiments of the present application may provide a computer-readable storage medium having stored therein computer-executable instructions for implementing the methods provided by the first aspect, the second aspect, and each possible design in the first aspect and the second aspect when executed by a processor.
In a seventh aspect, embodiments of the present application provide a computer program product comprising a computer program for implementing the method provided by the first aspect and each possible design when executed by a processor.
The embodiment of the application provides a data backup method, a device, a server and a readable storage medium, wherein the method comprises the following steps: the first interface server receives a first backup request sent by the first node server, and sends a first target storage path acquisition request to the first backup server. The first backup server acquires a first target storage path pre-stored in the storage path database according to the received first target storage path acquisition request, and sends the first target storage path to the first interface server. The first interface server receives a first target storage path, and stores the data which is not successfully backed up by the second interface server in the first data to be backed up carried by the first backup request into the NAS of the backup server corresponding to the first target storage path. According to the technical scheme, the interface server cluster can be guaranteed to store the first data to be backed up to the same storage address, and when the data recovery processing is carried out on the first data to be backed up subsequently, only one data is needed to be obtained in one storage address, so that the efficiency of the data recovery processing is improved. The first data to be backed up can be placed at the same storage address, so that the data can be managed more effectively, the problem of data loss possibly caused by excessive addresses for storing the data is prevented, and the safety of the data is further improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
Fig. 1 is a schematic view of an application scenario of a data backup method provided in an embodiment of the present application;
fig. 2 is a flowchart of an embodiment one of a method for backing up data according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a second embodiment of a data backup method provided in the embodiment of the present application;
fig. 4 is a schematic flow chart of a third embodiment of a data backup method provided in the embodiment of the present application;
fig. 5 is a flowchart of a fourth embodiment of a method for backing up data according to the embodiment of the present application;
fig. 6 is a flowchart of a fifth embodiment of a method for backing up data according to the embodiments of the present application;
fig. 7 is a flowchart of a sixth embodiment of a method for backing up data according to the embodiment of the present application;
fig. 8 is a flowchart of a seventh embodiment of a method for backing up data according to the embodiment of the present application;
FIG. 9 is a schematic structural diagram of a first embodiment of a data backup device according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a second embodiment of a data backup device according to the embodiment of the present application;
Fig. 11 is a schematic structural diagram of a server according to an embodiment of the present application.
Specific embodiments of the present disclosure have been shown by way of the above drawings and will be described in more detail below. These drawings and the written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the disclosed concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
Before describing the embodiments of the present application, an application background of the embodiments of the present application will be explained first:
the network attached storage (Network Attached Storage, NAS) is connected to a network and has a data storage function, and is also referred to as "network storage". NAS can solve various problems such as file storage, hierarchical rights management, high-performance disk read-write, high-bandwidth Network input/output, and data security, and thus is generally applied to a dedicated data storage server, where a workstation or server may access a NAS through a Network File System (NFS) or a common internet file system (Common Internet File System, CIFS). The data can be timely recovered after the data of the system is lost by backing up the data into the NAS, so that the loss caused by the data loss is effectively reduced, and the safety of the data is further improved.
At present, after a system receives a backup request of a user, one node in a system cluster is selected as a master node, other nodes are slave nodes, the master node outputs a backup starting instruction to a reach tool of the node, and the reach tool of the other slave nodes is informed to start through the reach tool, so that all the nodes acquire data to be backed up from a database of the node through the reach tool started by the master node, and the data to be backed up is transmitted to a server side through an MML interface for backup.
Further, after the data is successfully backed up, the system can receive a recovery request sent by the user, acquire the storage path address of the data to be recovered at the server according to the recovery request, acquire the data to be recovered according to the storage path address, and send the data to be recovered to the user
However, when the node MML interface is abnormal and cannot work normally in the backup process, the backup data of the node fails to be backed up. When the data is continuously backed up by using other MML interfaces, the consistency of the storage paths of the data in the two backup processes cannot be ensured, and the problem of poor fault tolerance in the backup process exists.
In view of the above problems, the inventive concept of the present application is as follows: if there are multiple storage paths for the backup data, the backup data needs to be acquired from multiple addresses when being restored, which results in low restoration processing efficiency. Based on this, the inventor finds that if the storage address of the backup data is stored in the storage path database when the MML interface is used for backing up the data, when the MML interface is abnormal and the other MML interfaces are used for continuing to backup, the problem of low recovery efficiency of the backed up data in the prior art can be solved by storing the data according to the storage address in the storage path database.
The data backup method provided in the embodiment of the present application may be applied to an application scenario schematic shown in fig. 1. Fig. 1 is a schematic application scenario diagram of a data backup method according to an embodiment of the present application, so as to solve the above technical problems. As shown in fig. 1, the application scenario may include at least one node server (e.g., node server 11, node server 12 in fig. 1), at least two interface servers (e.g., interface server 13, interface server 14 in fig. 1), at least one backup server (backup server 15, backup server 16), and a storage path database 17. Wherein node servers 11 and 12 constitute a node server cluster, interface servers 13 and 14 constitute an interface server cluster, and backup servers 15 and 16 constitute a backup server cluster.
The interface server may program an interface (Backup Services Applications Programming Interface, XBSA) server for the backup service application.
In the embodiment of the application, the node server sends a backup request to the interface server, and after receiving the backup request, the interface server sends a target storage path acquisition request to the backup server. After receiving the target storage path acquisition request, the backup server generates a target storage path for storing the backup data according to the target storage path, stores the target storage path into a storage path database, and sends the target storage path to the interface server. And the interface server receives the target storage path sent by the backup server and stores the data to be stored into the NAS of the backup server corresponding to the target storage path.
Further, when the interface server (for example, the interface server 1) fails and cannot work normally, the node server generates a new backup request according to the data which is not backed up successfully in the data to be backed up, and sends the new backup request to the interface server (for example, the interface server 2) in a normal working state. And after receiving the new backup request, the interface server in the normal working state sends a new target storage path acquisition request to the backup server. And after receiving the new target storage path acquisition request, the backup server acquires a target storage path for storing the data to be backed up from a storage path database and sends the target storage path to the interface server in the normal working state. And the interface server in a normal working state receives the target storage path sent by the backup server, and stores the data to be stored into the NAS of the backup server corresponding to the target storage path.
In fig. 1, the interface server and the node server may be separate servers, or the functions of the interface server and the functions of the node server may be integrated into the same server.
It should be appreciated that the number of backup servers is not limited in this application, and may be determined according to the size of the data to be backed up.
The following describes the technical scheme of the present application in detail through specific embodiments.
It should be noted that the following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.
Fig. 2 is a flowchart of an embodiment one of a data backup method provided in the embodiment of the present application. As shown in fig. 2, the backup method of data may include the steps of:
s21, receiving a first backup request sent by a first node server.
In this step, the first node server backs up the first data to be backed up through the second interface server, and when the second node fails and cannot work normally, a first backup request can be generated according to the data which is not backed up successfully in the first data to be backed up, and the first backup request is sent to the first interface server. The first backup request comprises an identification of the first data to be backed up and data which is not backed up successfully by the second interface server in the first data to be backed up. For the first interface server, a first backup request sent by the first node server is received, so that the data which is not successfully backed up in the first backup request can be backed up later.
The first data to be backed up may be a data stream, which may be obtained by splitting data by the first node server according to a preset data size.
Optionally, the node server and the interface server are bound in advance.
S22, a first target storage path acquisition request is sent to any backup server in the backup server cluster.
In this step, after receiving the first backup request, the first interface server needs to acquire a storage path when backing up the first data to be backed up. Specifically, the first interface server sends a first target storage path acquisition request to any backup server in the backup server cluster, where the first target storage path acquisition request is used to acquire a first target storage path stored in the storage path database in advance, and the first target storage path is a storage path when the first data to be backed up is backed up.
The first target storage path obtains an identification including first data to be backed up.
Optionally, the first interface server is connected to any backup server in the backup server cluster through a transmission control protocol (Transmission Control Protocol, TCP), or may be connected by a connection manner or a protocol existing in the prior art, which is not specifically limited in this application.
To more clearly illustrate this solution, this embodiment is described by taking, as an example, sending a first target storage path acquisition request to a first backup server in a backup server cluster.
It should be appreciated that the first interface server may also be configured to send a first target storage path retrieval request to a second backup server or other backup servers in the backup server cluster.
For the first backup server, a first target storage path retrieval request sent by a first interface server in the cluster of interface servers is received.
S23, acquiring a first target storage path stored in a storage path database in advance according to the first target storage path acquisition request.
In this step, after obtaining the first target storage path obtaining request sent by the first interface server, the first backup server obtains the first target storage path from the storage path database according to the identifier of the first data to be backed up in the target storage path obtaining request.
S24, the first target storage path is sent to the first interface server.
For the first interface server, a first target storage path returned by the first backup server is received.
S25, storing the data which is not successfully backed up to the NAS of the backup server corresponding to the first target storage path.
In this example, that is, the data that was not successfully backed up is stored in the network attached storage NAS of the first backup server.
According to the data backup method, a first interface server receives a first backup request sent by a first node server, and sends a first target storage path acquisition request to the first backup server. The first backup server acquires a first target storage path pre-stored in the storage path database according to the received first target storage path acquisition request, and sends the first target storage path to the first interface server. The first interface server receives a first target storage path, and stores the data which is not successfully backed up by the second interface server in the first data to be backed up carried by the first backup request into the NAS of the backup server corresponding to the first target storage path. In the scheme, the interface server cluster can be ensured to store the first data to be backed up to the same storage address, and when the data recovery processing is carried out on the first data to be backed up subsequently, only one data is required to be obtained in one storage address, so that the efficiency of the data recovery processing is improved. The first data to be backed up can be placed at the same storage address, so that the data can be managed more effectively, the problem of data loss caused by excessive addresses of data storage is prevented, and the safety of the data is further improved.
Optionally, in some embodiments, the backup server cluster may be copied to another cluster (e.g., the first backup server cluster), so that when the backup server cluster fails and cannot work normally, the interface server cluster may connect with the first backup server cluster, and continue to complete the data recovery processing.
It should be understood that the first interface server may continue to backup the data after the second interface server fails in the data backup process, or may directly receive the backup request sent by the node server, and backup the data carried in the backup request.
Fig. 3 is a flowchart of a second embodiment of a data backup method according to the embodiment of the present application. As shown in fig. 3, the backup method of data may include the steps of:
s31, receiving a second backup request sent by the second node server.
In this step, when the second node server needs to backup the second data to be backed up, a second backup request may be sent to the second node server, where the second backup request includes the second data to be backed up and an identifier of the second data to be backed up. Correspondingly, for the first interface server, a second backup request sent by the second node server is received.
S32, according to the identification of the second data to be backed up, a second target storage path acquisition request is sent to any backup server in the backup server cluster.
In this step, after receiving the second backup request, the first interface server needs to acquire a storage path for storing the second data to be backed up. Specifically, the first interface server sends a second target storage path acquisition request to any backup server in the backup server cluster, where the second target storage path acquisition request is used to acquire a second target storage path, and the second target storage path is used to store second data to be backed up.
Optionally, the second target storage path acquisition request includes a type and a size of the second data to be backed up.
To more clearly illustrate this solution, this embodiment is illustrated by sending a second target storage path acquisition request to a first backup server in a backup server cluster.
It should be appreciated that the first interface server may also be configured to send a second target storage path retrieval request to a second backup server or other backup servers in the backup server cluster.
And for the first backup server, receiving a second target storage path acquisition request sent by the first interface server.
S33, generating a second target storage path according to the second target storage path acquisition request.
In this step, after the first backup server receives the second target storage path acquisition request, a storage address for backing up the second backup data needs to be generated according to the second target storage path acquisition request.
In one possible implementation, the first backup server generates the second target storage path according to the type of the second backup data in the second target storage path acquisition request, the size of the second backup data, and the space size of each partition in the NAS of the first backup server.
S34, storing the second target storage path into a storage path database and sending the second target storage path to the first interface server.
In this step, after the second target storage path is generated, the second target storage path is stored in the storage path database, so that after the first interface server fails, other interface servers can continue to backup the data which is not successfully backed up in the second data to be backed up according to the second target storage path stored in the storage path database.
Further, the second target storage path is sent to the first interface server, so that the subsequent first interface server stores the second data to be backed up into a space corresponding to the second target storage path according to the second target storage path.
For the first interface server, a second target storage path returned by the backup server is received.
And S35, storing the second data to be backed up into the NAS of the first backup server corresponding to the second target storage path.
According to the data backup method, the first interface server receives the second backup request sent by the second node server, and sends a second target storage path acquisition request to the first backup server according to second data to be backed up carried in the second backup request. And the first backup server generates a second target storage path according to the received second target storage path acquisition request and sends the second target storage path to the first interface server. After receiving the second target storage path, the first interface server stores the second data to be backed up into the NAS of the first backup server corresponding to the second target storage path. After the first backup server generates the second target storage path, the second target storage path is stored in the storage path database, so that after the first interface server fails, other interface servers can continue to backup the data which is not successfully backed up in the second data to be backed up according to the second target storage path stored in the storage path database, and the condition that the second data to be backed up corresponds to only one storage address is ensured.
Furthermore, after the data is backed up, when unexpected situations such as loss or missing of the data stored in advance in the node server occur, the data can be recovered.
Fig. 4 is a flowchart of a third embodiment of a data backup method according to the embodiment of the present application. As shown in fig. 4, after storing the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path on the basis of the foregoing embodiment, the backup method of the data may include the following steps for the first interface server side:
s41, receiving a first data recovery request sent by the second node server.
In this step, when the second node server loses, loses or performs error modification on the first target data, and cannot recover the first target data, the second node server may send a first data recovery request to the first interface server. The first data recovery request includes an identification of the first target data.
The first target data is the data subjected to the backup processing.
S42, acquiring the first target data from the NAS corresponding to the first target path according to the first target path corresponding to the identification of the first target data.
In this step, after the first interface server obtains the identifier of the first target data, it is necessary to obtain the address where the first target data is stored in the NAS.
In one possible implementation manner, the first interface server obtains a first target path corresponding to the identifier of the first target data according to the mapping relationship between the identifier of the data and the path. It should be appreciated that the mapping relationship between the identification of the data and the path may be generated based on the identification of the data to be backed up and the target storage path. In other words, the first target data in this embodiment is the data to be backed up in the backup process in the foregoing embodiment, and the first target path in this embodiment is the storage address of the backup server where the data to be backed up is stored.
S43, the first target data are sent to the second node server.
In this embodiment of the present application, the first interface server receives a first data recovery request sent by the second node server, where the data recovery request includes an identifier of first target data, acquires, according to a first target path corresponding to the identifier of the first target data, the first target data from NAS corresponding to the first target path, and sends the first target data to the second node server. When the data is recovered, only one path is needed to be accessed, and the data to be recovered is obtained from the path, so that the data recovery efficiency is effectively improved, and the service pressure of the first interface server is reduced.
Fig. 5 is a flowchart of a fourth embodiment of a data backup method according to the embodiment of the present application. As shown in fig. 5, on the basis of the foregoing embodiment, before storing the data that is not successfully backed up in the NAS of the backup server corresponding to the first target storage path, the backup method of the data may include the following steps:
s51, sending a file system acquisition request to a backup server corresponding to the first target storage path.
For the sake of clarity in describing the present solution, in this embodiment, the backup server corresponding to the first target storage path is taken as the first backup server for illustration.
It should be understood that the backup server corresponding to the first target storage path may also be a second backup server or other backup servers in the backup server cluster.
In this step, the first interface server may acquire a first file system of the second interface server in the backup server corresponding to the first target storage path, so as to store, by using the first file system, data that is not successfully backed up by the second interface server in the first data to be backed up.
The file system acquisition request is used for acquiring a first file system corresponding to the second interface server in the backup server.
For the first backup server, a file system acquisition request sent by the first interface server is received.
S52, sending the first file system to the first interface server.
Further, the first backup server obtains the first file system according to the file system obtaining request, and sends the first file system to the first interface server.
For the first interface server, a first file system sent by the first backup server is received.
Accordingly, S25 may be implemented by:
and mounting a second file system, and storing second data to be backed up into the NAS corresponding to the second target storage path by using the mounted second file system.
Fig. 6 is a flowchart of a fourth embodiment of a data backup method according to the embodiment of the present application. As shown in fig. 6, on the basis of the above embodiment, before receiving the second backup request sent by the second node server, the backup method of data may include the following steps:
s61, sending a file system establishment request to the first backup server.
In this step, the first interface server may acquire a second file system of the first interface server in the first backup server, so as to store, by using the second file system, data that is not successfully backed up by the second interface server in the second data to be backed up.
The file system establishment request is used for indicating the first backup server to establish a second file system corresponding to the first interface server in the first backup server.
For the first backup server, a file system establishment request sent by the first interface server is received.
And S62, when the second file system does not exist, the second file system is built, and the second file system is sent to the first interface server.
And S63, when the second file system exists, the second file system is sent to the first interface server.
For the first node server, the receiving backup server sends a second file system.
Accordingly, S35 may be implemented by:
and mounting the first file system, and storing the data which is not successfully backed up to the NAS corresponding to the first target storage path by using the mounted first file system.
Fig. 7 is a flowchart of a sixth embodiment of a method for backing up data according to the embodiment of the present application. As shown in fig. 7, the backup method of data may include the steps of:
s71, sending a file system establishment request to the first backup server.
When the first interface server is started, a file system establishment request is sent to the first backup server.
For the first backup server, a file system establishment request sent by the first interface server is received.
S72, according to the file system establishment request, a first file system is established in the NAS.
S73, sending the first file system to the first interface server.
For the first interface server, a first file system is received.
And S74, sending a backup start request to the first interface server.
In this step, the second node server needs to load libxbsa.so. in order to send the second backup request with the first interface server.
For the first interface server, a second backup request is received.
S75, mounting the first file system, and sending a second target storage path acquisition request to the first backup server.
For the first backup server, a second target storage path retrieval request is received.
S76, generating a second target storage path according to the second target storage path acquisition request.
And S77, storing the second target storage path into a storage path database and sending the second target storage path to the first interface server.
For the first interface server, a second target storage path is received.
And S78, sending the second data to be backed up to the first interface server.
Wherein the second data to be backed up may be a data stream.
For the first interface server, second data to be backed up is received.
S79, storing the second data to be backed up into the NAS of the first backup server corresponding to the second target storage path.
S710, sending a backup ending request to the first interface server.
For the first interface server, a backup end request is received.
And S711, sending a backup ending request to the first backup server.
For the first backup server, a backup end request is received.
S712, the first file system is detached and mounted.
It should be understood that the backup start request, the second backup data, and the backup end request in the embodiments of the present application collectively constitute the second backup request in the above embodiments.
Fig. 8 is a flowchart of a seventh embodiment of a method for backing up data according to the embodiment of the present application. As shown in fig. 8, the backup method of data may include the steps of:
s81, sending a data query instruction to the first interface server.
In this step, the second node server needs to load libxbsa.
Wherein the data query instruction is used to view data in the NAS.
For the first interface server, a data query request is received.
S82, sending a data query request to the first backup server.
For the first backup server, a data query request is received.
S83, acquiring data information according to the data query request, and sending the data information to the first interface server.
For the first interface server, data information is received.
And S84, transmitting the data information to the second node server.
For the second node server, data information is received.
S85, mounting the first file system.
S86, determining first target data according to the data information, and generating a data acquisition start request.
Wherein the data start acquisition request includes first target data.
S87, sending a data start acquisition request to the first interface server.
Wherein the data start acquisition request includes an identification of the first target data.
For the first interface server, a data start acquisition request is received.
S88, acquiring the first target data from the NAS corresponding to the first target path according to the first target path corresponding to the identification of the first target data.
S89, the acquired first target data is sent to a second node server.
S810, sending a data end acquisition request to a first interface server.
For the first interface server, a data end acquisition request is received.
It should be appreciated that the second node server may cycle to send the identification of the target data to the first interface server. The first interface server acquires corresponding target data according to the received identification of the target data and sends the corresponding target data to the second node server, and the data end acquisition request sent by the second node server is directly received.
For the second node server, first target data is received.
S811, the first file system is detached and mounted.
It should be understood that the data query request, the data start acquisition request, and the data end acquisition request in the embodiments of the present application collectively constitute the first data recovery request in the above embodiments.
The following are device embodiments of the present application, which may be used to perform method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.
Fig. 9 is a schematic structural diagram of a first embodiment of a data backup device according to an embodiment of the present application. As shown in fig. 9, the backup apparatus of data is applied to a first interface server in an interface server cluster, the interface server cluster includes the first interface server and a second interface server, and the backup apparatus of data includes:
The receiving module 91 is configured to receive a first backup request sent by a first node server, where the first backup request includes an identifier of first data to be backed up and data that is not successfully backed up by a second interface server in the first data to be backed up.
The sending module 92 is configured to send a first target storage path obtaining request to any backup server in the backup server cluster, where the first target storage path obtaining request is used to obtain a first target storage path that is pre-stored in a storage path database, the first target storage path obtaining request includes an identifier of first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up.
And the receiving module 91 is configured to receive the first target storage path returned by the backup server.
And the processing module 93 is configured to store the data that is not successfully backed up to the network attached storage NAS of the backup server corresponding to the first target storage path.
In one possible design of the embodiment of the present application, the receiving module 91 is further configured to receive a second backup request sent by the second node server, where the second backup request includes the second data to be backed up and an identifier of the second data to be backed up.
The sending module 92 is further configured to send a second target storage path acquisition request to any backup server in the backup server cluster according to the identifier of the second data to be backed up, where the second target storage path acquisition request is used to acquire a second target storage path, and the second target storage path is used to store the second data to be backed up;
the receiving module 91 is further configured to receive a second target storage path returned by the backup server.
The processing module 93 is further configured to store the second data to be backed up to a NAS of the first backup server corresponding to the second target storage path.
Optionally, after storing the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path, the receiving module 91 is further configured to receive a first data recovery request sent by the second node server, where the first data recovery request includes an identifier of the first target data.
The processing module 93 is further configured to obtain, according to a first target path corresponding to the identifier of the first target data, the first target data from NAS corresponding to the first target path.
The sending module 92 is further configured to send the first target data to the second node server.
In another possible design of this embodiment of the present application, before storing the data that is not successfully backed up in the NAS of the backup server corresponding to the first target storage path, the sending module 92 is further configured to send a file system obtaining request to the backup server corresponding to the first target storage path, where the file system obtaining request is used to obtain a first file system corresponding to the second interface server in the backup server.
The receiving module 91 is further configured to receive the first file system sent by the backup server.
Correspondingly, the processing module 93 is specifically configured to:
and mounting the first file system, and storing the data which is not successfully backed up to the NAS corresponding to the first target storage path by using the mounted first file system.
Optionally, before receiving the second backup request sent by the second node server, the sending module 92 is further configured to send a file system establishment request to the first backup server, where the file system establishment request is used to instruct the first backup server to establish a second file system corresponding to the first interface server in the first backup server.
The receiving module 91 is further configured to receive the second file system sent by the first backup server.
Correspondingly, the processing module 93 is specifically configured to:
and mounting a second file system, and storing second data to be backed up into the NAS corresponding to the second target storage path by using the mounted second file system.
The data backup device provided in the embodiment of the present application may be used to execute the data backup method on the interface server side in any of the above embodiments, and its implementation principle and technical effects are similar and will not be described herein again.
Fig. 10 is a schematic structural diagram of a second embodiment of a data backup device according to the embodiment of the present application. As shown in fig. 10, the backup apparatus of data is applied to a first backup server in a backup server cluster, and the apparatus includes:
The receiving module 101 is configured to receive a first target storage path acquisition request sent by a first interface server in the interface server cluster, where the first target storage path acquisition request is used to acquire a first target storage path that is pre-stored in a storage path database, where the first target storage path acquisition request includes an identifier of first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up.
The processing module 102 is configured to obtain, according to the first target storage path obtaining request, a first target storage path that is stored in advance in the storage path database.
And the sending module 103 is configured to send the first target storage path to the first interface server.
In one possible design of the embodiment of the present application, the receiving module 101 is further configured to receive a second target storage path obtaining request sent by the first interface server, where the second target storage path obtaining request is used to obtain a second target storage path, and the second target storage path is used to store second data to be backed up.
The processing module 102 is further configured to generate a second target storage path according to the second target storage path acquisition request.
The sending module 103 is further configured to store the second target storage path in the storage path database, and send the second target storage path to the first interface server.
Optionally, before receiving the second target storage path obtaining request sent by the first interface server, the receiving module 101 is further configured to receive a file system establishment request sent by the first interface server, where the file system establishment request is used to establish a second file system corresponding to the first node server in the first backup server.
The sending module 103 is further configured to establish a second file system when the second file system does not exist, and send the second file system to the first interface server.
The sending module 103 is further configured to send the second file system to the first interface server when the second file system exists.
In another possible design of the embodiment of the present application, before the first target storage path is sent to the first interface server, the receiving module 101 is further configured to receive a file system acquisition request sent by the first interface server, where the file system acquisition request is used to acquire a first file system corresponding to the second node server in the first backup server.
The sending module 103 is further configured to send the first file system to the first interface server.
The data backup device provided in the embodiment of the present application may be used to execute the backup method for backing up data on the server side in any of the foregoing embodiments, and its implementation principle and technical effects are similar and will not be described herein again.
It should be noted that, it should be understood that the division of the modules of the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. In addition, all or part of the modules may be integrated together or may be implemented independently. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in a software form.
Fig. 11 is a schematic structural diagram of a server according to an embodiment of the present application. As shown in fig. 11, the server may include: the computer program comprises a processor 111, a memory 112, a transceiver 113 and computer program instructions stored on the memory 112 and executable on the processor 111, wherein the processor 111 implements the data backup method provided by any of the foregoing embodiments when executing the computer program instructions.
Alternatively, the above devices of the server may be connected by a system bus.
The memory 112 may be a separate memory unit or may be a memory unit integrated into the processor. The number of processors is one or more.
Optionally, the server may also include interfaces to interact with other devices.
The transceiver 82 is used to communicate with other computers, and the transceiver 82 constitutes a communication interface.
Alternatively, in a hardware implementation, in the embodiment shown in fig. 9, the foregoing description is provided: a receiving module 91 and a transmitting module 92, and in the embodiment shown in fig. 10 described above: the receiving module 101, the transmitting module 103 corresponds to the transceiver 113 in the present embodiment, and the processing module 93 in the embodiment shown in fig. 9 and the processing module 102 in the embodiment shown in fig. 10 correspond to the processor 111 in the present embodiment.
It should be appreciated that the processor 111 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor or in a combination of hardware and software modules within a processor.
The system bus may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The system bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus. The memory may include random access memory (random access memory, RAM) and may also include non-volatile memory (NVM), such as at least one disk memory.
All or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a readable memory. The program, when executed, performs steps including the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape, floppy disk, optical disk, and any combination thereof.
The server provided in the embodiment of the present application may be used to execute the data backup method provided in any of the above method embodiments, and its implementation principle and technical effects are similar, and are not described herein again.
Embodiments of the present application provide a computer-readable storage medium having stored therein computer instructions that, when executed on a computer, cause the computer to perform a method of backing up the data described above.
The computer readable storage medium described above may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as static random access memory, electrically erasable programmable read-only memory, magnetic memory, flash memory, magnetic disk or optical disk. A readable storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.
In the alternative, a readable storage medium is coupled to the processor such that the processor can read information from, and write information to, the readable storage medium. In the alternative, the readable storage medium may be integral to the processor. The processor and the readable storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC). The processor and the readable storage medium may reside as discrete components in a device.
Embodiments of the present application also provide a computer program product, where the computer program product includes a computer program, where the computer program is stored in a computer readable storage medium, and at least one processor may read the computer program from the computer readable storage medium, and the at least one processor may implement a method for backing up data when the computer program is executed.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (14)

1. A method of backing up data, characterized in that it is applied to a first interface server in an interface server cluster, said interface server cluster comprising said first interface server and a second interface server, said method comprising:
receiving a first backup request sent by a first node server, wherein the first backup request comprises an identifier of first data to be backed up and data which is not backed up successfully by a second interface server in the first data to be backed up;
a first target storage path acquisition request is sent to any backup server in a backup server cluster, wherein the first target storage path acquisition request is used for acquiring a first target storage path stored in a storage path database in advance, the first target storage path acquisition request comprises an identifier of the first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up;
Receiving the first target storage path returned by the backup server;
and storing the data which is not successfully backed up to a network attached storage NAS of a backup server corresponding to the first target storage path.
2. The method according to claim 1, wherein the method further comprises:
receiving a second backup request sent by a second node server, wherein the second backup request comprises second data to be backed up and an identifier of the second data to be backed up;
according to the identification of the second data to be backed up, a second target storage path acquisition request is sent to any backup server in the backup server cluster, wherein the second target storage path acquisition request is used for acquiring a second target storage path, and the second target storage path is used for storing the second data to be backed up;
receiving the second target storage path returned by the backup server;
and storing the second data to be backed up to the NAS of the first backup server corresponding to the second target storage path.
3. The method of claim 2, wherein after storing the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path, the method further comprises:
Receiving a first data recovery request sent by the second node server, wherein the first data recovery request comprises an identifier of first target data;
acquiring the first target data from the NAS corresponding to the first target path according to the first target path corresponding to the identifier of the first target data;
and sending the first target data to the second node server.
4. The method of claim 1, wherein prior to storing the non-backup successful data in the NAS of the backup server corresponding to the first target storage path, the method further comprises:
sending a file system acquisition request to a backup server corresponding to the first target storage path, wherein the file system acquisition request is used for acquiring a first file system corresponding to the second interface server in the backup server;
receiving the first file system sent by the backup server;
correspondingly, the storing the data that is not successfully backed up in the NAS of the backup server corresponding to the first target storage path includes:
and mounting the first file system, and storing the unsuccessfully backed up data to the NAS corresponding to the first target storage path by using the mounted first file system.
5. A method according to claim 2 or 3, wherein prior to said receiving said second backup request sent by said second node server, said method further comprises:
sending a file system establishment request to the first backup server, wherein the file system establishment request is used for indicating the first backup server to establish a second file system corresponding to the first interface server in the first backup server;
receiving the second file system sent by the first backup server;
correspondingly, the storing the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path includes:
and mounting the second file system, and storing second data to be backed up into the NAS corresponding to the second target storage path by using the mounted second file system.
6. A method of backing up data for a first backup server in a backup server cluster, the method comprising:
receiving a first target storage path acquisition request sent by a first interface server in an interface server cluster, wherein the first target storage path acquisition request is used for acquiring a first target storage path stored in a storage path database in advance, the first target storage path acquisition request comprises an identifier of first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up;
Acquiring the first target storage path pre-stored in a storage path database according to the first target storage path acquisition request;
and sending the first target storage path to the first interface server.
7. The method of claim 6, wherein the method further comprises:
receiving a second target storage path acquisition request sent by the first interface server, wherein the second target storage path acquisition request is used for acquiring a second target storage path, and the second target storage path is used for storing second data to be backed up;
generating a second target storage path according to the second target storage path acquisition request;
and storing the second target storage path into the storage path database and sending the second target storage path to the first interface server.
8. The method of claim 7, wherein prior to receiving the second target storage path acquisition request sent by the first interface server, the method further comprises:
receiving a file system establishment request sent by the first interface server, wherein the file system establishment request is used for establishing a second file system corresponding to the first node server in the first backup server;
When the second file system does not exist, the second file system is built, and the second file system is sent to the first interface server;
and when the second file system exists, sending the second file system to the first interface server.
9. The method of claim 6, wherein prior to the sending the first target storage path to the first interface server, the method further comprises:
receiving a file system acquisition request sent by the first interface server, wherein the file system acquisition request is used for acquiring a first file system corresponding to the second node server in the first backup server;
and sending the first file system to the first interface server.
10. A data backup apparatus for use with a first interface server in an interface server cluster, the interface server cluster comprising the first interface server and a second interface server, the apparatus comprising:
the receiving module is used for receiving a first backup request sent by a first node server, wherein the first backup request comprises an identifier of first data to be backed up and data which is not backed up successfully by a second interface server in the first data to be backed up;
The sending module is used for sending a first target storage path acquisition request to any backup server in the backup server cluster, wherein the first target storage path acquisition request is used for acquiring a first target storage path stored in a storage path database in advance, the first target storage path acquisition request comprises an identifier of the first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up;
the receiving module is used for receiving the first target storage path returned by the backup server;
and the processing module is used for storing the data which is not successfully backed up to the network attached storage NAS of the backup server corresponding to the first target storage path.
11. A data backup apparatus for use with a first backup server in a backup server cluster, the apparatus comprising:
the receiving module is used for receiving a first target storage path acquisition request sent by a first interface server in the interface server cluster, wherein the first target storage path acquisition request is used for acquiring a first target storage path stored in a storage path database in advance, the first target storage path acquisition request comprises an identifier of first data to be backed up, and the first target storage path is a storage path when the first data to be backed up is backed up;
The processing module is used for acquiring the first target storage path pre-stored in a storage path database according to the first target storage path acquisition request;
and the sending module is used for sending the first target storage path to the first interface server.
12. A server, comprising: a processor, a transceiver, a memory and computer program instructions stored on the memory and executable on the processor, wherein the processor is configured to implement a method of backing up data as claimed in any one of claims 1 to 9 when executing the computer program instructions.
13. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for implementing a method of backing up data as claimed in any one of claims 1 to 9.
14. A computer program product comprising a computer program for implementing a method of backup of data as claimed in any one of claims 1 to 9 when executed by a processor.
CN202111516343.XA 2021-12-08 2021-12-08 Data backup method and device, server and readable storage medium Pending CN116244109A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111516343.XA CN116244109A (en) 2021-12-08 2021-12-08 Data backup method and device, server and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111516343.XA CN116244109A (en) 2021-12-08 2021-12-08 Data backup method and device, server and readable storage medium

Publications (1)

Publication Number Publication Date
CN116244109A true CN116244109A (en) 2023-06-09

Family

ID=86628287

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111516343.XA Pending CN116244109A (en) 2021-12-08 2021-12-08 Data backup method and device, server and readable storage medium

Country Status (1)

Country Link
CN (1) CN116244109A (en)

Similar Documents

Publication Publication Date Title
US11163653B2 (en) Storage cluster failure detection
CN105830033B (en) System and method for supporting persistent storage versioning and integrity in a distributed data grid
EP3185125B1 (en) Data backup method, system, node and computer storage media
CN109033328B (en) Access request processing method, device, equipment and readable storage medium
CN109783014B (en) Data storage method and device
CN111124755A (en) Cluster node fault recovery method and device, electronic equipment and storage medium
US20190227710A1 (en) Incremental data restoration method and apparatus
US11184435B2 (en) Message transmission method and apparatus in cluster file system
CN109165112B (en) Fault recovery method, system and related components of metadata cluster
WO2011109049A1 (en) Method and apparatus of backing-up subversion repository
CN108133034B (en) Shared storage access method and related device
WO2021082925A1 (en) Transaction processing method and apparatus
CN112261114A (en) Data backup system and method
WO2017054643A1 (en) Data recovery method and file server
CN116701518A (en) Database cluster deployment method and device, computer equipment and storage medium
CN116244109A (en) Data backup method and device, server and readable storage medium
CN115658390A (en) Container disaster tolerance method, system, device, equipment and computer readable storage medium
JP6376626B2 (en) Data storage method, data storage device, and storage device
CN115470041A (en) Data disaster recovery management method and device
CN113596195B (en) Public IP address management method, device, main node and storage medium
CN115314361A (en) Server cluster management method and related components thereof
CN112202601B (en) Application method of two physical node mongo clusters operated in duplicate set mode
CN114281600A (en) Disaster recovery backup and recovery method, device, equipment and storage medium
CN113157392A (en) High-availability method and equipment for mirror image warehouse
CN116820430B (en) Asynchronous read-write method, device, computer equipment and 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