Backup method and device of data, server and readable storage medium

Abstract

The application provides a backup method and device of data, a server and a readable storage medium. The method comprises the following steps: 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 a first backup server. The first backup server acquires a first target storage path pre-stored in a 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 the first target storage path, and stores data, which is not successfully backed up by a second interface server, in the first backup request to the first target storage path corresponding to the backup server in the NAS. In the technical solution, when data recovery processing is performed on the first backup data in the subsequent process, the data is acquired only once in one storage address, and the efficiency of the data recovery processing is improved.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a data backup method, apparatus, server, and readable storage medium. Background Technology

[0002] Data backup is the foundation of disaster recovery. It refers to the process of copying all or part of a data set from the application host's hard drive or array to other storage media to prevent data loss due to operational errors or system failures. Backing up data enables timely recovery after data loss, effectively reducing losses caused by data loss and improving data security. Therefore, knowing how to back up data is crucial.

[0003] Currently, data backup mainly involves the system receiving a backup request from a user, randomly selecting one node in the system cluster as the master node, and the other nodes as slave nodes. The master node uses its own Roach tool to notify the other slave nodes to start their Roach tools, so that all nodes can retrieve the data to be backed up from their own database through their own Roach tools, and then transmit the data to be backed up to the server through the Man-Machine Language (MML) interface.

[0004] However, if the MML interface fails to function properly during the backup process and another MML interface is needed to continue the backup, the storage path cannot be guaranteed to be consistent between the two backup processes, resulting in low efficiency in restoring the backed-up data. Summary of the Invention

[0005] This application provides a data backup method, apparatus, server, and readable storage medium to solve the problem that in the prior art, when the MML interface cannot work properly during the backup process and other MML interfaces need to be used to continue the backup, the storage path of the two backup processes cannot be guaranteed to be consistent, resulting in low efficiency in the subsequent recovery of the backed-up data.

[0006] In a first aspect, embodiments of this application provide a data backup method applied to a first interface server in an interface server cluster, the interface server cluster including the first interface server and a second interface server, the method comprising:

[0007] Receive a first backup request sent by the first node server. The first backup request includes the identifier of the first data to be backed up and the data in the first data to be backed up that the second interface server failed to back up successfully.

[0008] Send 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 to obtain a first target storage path that is pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up. The first target storage path is the storage path when backing up the first data to be backed up.

[0009] Receive the first target storage path returned by the backup server;

[0010] The data that was not successfully backed up is stored in the network auxiliary storage (NAS) of the backup server corresponding to the first target storage path.

[0011] In one possible design of the first aspect, the method further includes:

[0012] Receive a second backup request sent by the second node server, the second backup request including second data to be backed up and an identifier of the second data to be backed up;

[0013] Based on the identifier 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. The second target storage path acquisition request is used to acquire the second target storage path, and the second storage path is used to store the second data to be backed up.

[0014] Receive the second target storage path returned by the backup server;

[0015] The second data to be backed up is stored in the NAS of the first backup server corresponding to the second target storage path.

[0016] 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 method further includes:

[0017] Receive a first data recovery request sent by the second node server, wherein the first data recovery request includes an identifier of the first target data;

[0018] Based on the first target path corresponding to the identifier of the first target data, the first target data is obtained from the NAS corresponding to the first target path;

[0019] The first target data is sent to the second node server.

[0020] In another possible design of the first aspect, before storing the unbacked-up data in the NAS of the backup server corresponding to the first target storage path, the method further includes:

[0021] Send a file system retrieval request to the backup server corresponding to the first target storage path. The file system retrieval request is used to retrieve the first file system corresponding to the second interface server in the backup server.

[0022] Receive the first file system sent by the backup server;

[0023] Accordingly, storing the data that was not successfully backed up to the NAS of the backup server corresponding to the first target storage path includes:

[0024] Mount the first file system and use the mounted first file system to store the data that was not successfully backed up to the NAS corresponding to the first target storage path.

[0025] Optionally, before receiving the second backup request sent by the second node server, the method further includes:

[0026] Send a file system creation request to the first backup server. The file system creation request is used to instruct the first backup server to create a second file system corresponding to the first interface server in the first backup server.

[0027] Receive the second file system sent by the first backup server;

[0028] Accordingly, storing the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path includes:

[0029] Mount the second file system and use the mounted second file system to store the second data to be backed up to the NAS corresponding to the second target storage path.

[0030] Secondly, embodiments of this application provide a data backup method, applied to a first backup server in a backup server cluster, the method comprising:

[0031] The first target storage path acquisition request is sent by the first interface server in the interface server cluster. The first target storage path acquisition request is used to obtain the first target storage path pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up. The first target storage path is the storage path when backing up the first data to be backed up.

[0032] Based on the first target storage path retrieval request, retrieve the first target storage path that is pre-stored in the storage path database;

[0033] Send the first target storage path to the first interface server.

[0034] In one possible design of the second aspect, the method further includes:

[0035] Receive a second target storage path acquisition request sent by the first interface server. The second target storage path acquisition request is used to acquire a second target storage path, and the second storage path is used to store the second data to be backed up.

[0036] Based on the second target storage path retrieval request, generate the second target storage path;

[0037] The second target storage path is stored in the storage path database and then sent to the first interface server.

[0038] Optionally, before receiving the second target storage path acquisition request sent by the first interface server, the method further includes:

[0039] Receive a file system creation request sent by the first interface server, the file system creation request being used to create a second file system corresponding to the first node server in the first backup server;

[0040] If the second file system does not exist, create the second file system and send it to the first interface server;

[0041] If the second file system exists, the second file system is sent to the first interface server.

[0042] In another possible design of the second aspect, before sending the first target storage path to the first interface server, the method further includes:

[0043] Receive a file system retrieval request sent by the first interface server, the file system retrieval request being used to retrieve the first file system corresponding to the second node server in the first backup server;

[0044] Send the first file system to the first interface server.

[0045] Thirdly, embodiments of this application provide a data backup device applied to a first interface server in an interface server cluster, the interface server cluster including the first interface server and a second interface server, the device comprising:

[0046] The receiving module is used to receive a first backup request sent by the first node server. The first backup request includes an identifier of the first data to be backed up and the data in the first data to be backed up that the second interface server failed to back up.

[0047] The sending module is used to send 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 to acquire a first target storage path pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up. The first target storage path is the storage path when backing up the first data to be backed up.

[0048] The receiving module is used to receive the first target storage path returned by the backup server;

[0049] The processing module is used to store the data that was not successfully backed up to the network attached storage (NAS) of the backup server corresponding to the first target storage path.

[0050] In one possible design of the third aspect, the receiving module is further configured to receive a second backup request sent by the second node server, the second backup request including second data to be backed up and an identifier of the second data to be backed up;

[0051] 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. 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.

[0052] The receiving module is also used to receive the second target storage path returned by the backup server;

[0053] The processing module is further configured to store the second data to be backed up into the NAS of the first backup server corresponding to the second target storage path.

[0054] Optionally, after storing the second data to be backed up into 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, wherein the first data recovery request includes an identifier of the first target data;

[0055] The processing module is further configured to obtain 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;

[0056] The sending module is further configured to send the first target data to the second node server.

[0057] In another possible design of the third aspect, before storing the unbacked-up data into 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, the file system acquisition request being used to acquire the first file system corresponding to the second interface server in the backup server;

[0058] The receiving module is also used to receive the first file system sent by the backup server;

[0059] Accordingly, the processing module is specifically used for:

[0060] Mount the first file system and use the mounted first file system to store the data that was not successfully backed up to the NAS corresponding to the first target storage path.

[0061] Optionally, before 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, the file system establishment request being used to instruct the first backup server to establish a second file system corresponding to the first interface server in the first backup server;

[0062] The receiving module is also used to receive the second file system sent by the first backup server;

[0063] Accordingly, the processing module is specifically used for:

[0064] Mount the second file system and use the mounted second file system to store the second data to be backed up to the NAS corresponding to the second target storage path.

[0065] Fourthly, embodiments of this application provide a data backup device applied to a first backup server in a backup server cluster, the device comprising:

[0066] The receiving module is used to receive a first target storage path acquisition request sent by the first interface server in the interface server cluster. The first target storage path acquisition request is used to acquire a first target storage path pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up. The first target storage path is the storage path when backing up the first data to be backed up.

[0067] The processing module is used to obtain the first target storage path pre-stored in the storage path database according to the first target storage path acquisition request;

[0068] The sending module is used to send the first target storage path to the first interface server.

[0069] 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, the second target storage path acquisition request being used to acquire a second target storage path, the second target storage path being used to store second data to be backed up;

[0070] The processing module is further configured to generate a second target storage path based on the request for obtaining the second target storage path;

[0071] The sending module is further configured to store the second target storage path in the storage path database and send it to the first interface server.

[0072] Optionally, before receiving the second target storage path acquisition 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, the file system establishment request being used to establish a second file system corresponding to the first node server in the first backup server;

[0073] The sending module is further configured to create the second file system when the second file system does not exist, and send the second file system to the first interface server;

[0074] The sending module is further configured to send the second file system to the first interface server when the second file system exists.

[0075] In another possible design of the fourth aspect, before 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, the file system acquisition request being used to acquire the first file system corresponding to the second node server in the first backup server;

[0076] The sending module is also used to send the first file system to the first interface server.

[0077] Fifthly, embodiments of this application provide a server, including: a processor, a transceiver, a memory, and computer program instructions stored in the memory and executable on the processor, wherein the processor executes the computer program instructions to implement the first aspect, the second aspect, and the methods possibly designed and provided in the first and second aspects.

[0078] In a sixth aspect, embodiments of this application may provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect, the second aspect, and the methods that may be designed and provided in the first and second aspects.

[0079] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, is used to implement the methods provided in the first aspect and various possible designs.

[0080] This application provides a data backup method, apparatus, server, and readable storage medium. The method includes: a first interface server receiving a first backup request sent by a first node server, and sending a first target storage path acquisition request to a first backup server. The first backup server, based on the received first target storage path acquisition request, acquires a first target storage path pre-stored in a storage path database and sends it to the first interface server. The first interface server receives the first target storage path and stores the data that the second interface server failed to back up in the first backup data carried in the first backup request into the NAS of the backup server corresponding to the first target storage path. This technical solution ensures that the interface server cluster stores the first backup data in the same storage address. During subsequent data recovery processing of the first backup data, data only needs to be retrieved once from one storage address, improving the efficiency of data recovery processing. Placing the first backup data in the same storage address also enables more effective data management, preventing data loss that may occur due to storing data in too many addresses, further improving data security. Attached Figure Description

[0081] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0082] Figure 1 A schematic diagram illustrating an application scenario of the data backup method provided in this application embodiment;

[0083] Figure 2 A flowchart illustrating an embodiment of the data backup method provided in this application;

[0084] Figure 3 A flowchart illustrating a second embodiment of the data backup method provided in this application.

[0085] Figure 4 A flowchart illustrating Embodiment 3 of the data backup method provided in this application;

[0086] Figure 5 A flowchart illustrating Embodiment 4 of the data backup method provided in this application;

[0087] Figure 6 A flowchart illustrating Embodiment 5 of the data backup method provided in this application;

[0088] Figure 7 A flowchart illustrating Embodiment Six of the data backup method provided in this application;

[0089] Figure 8 A flowchart illustrating Embodiment Seven of the data backup method provided in this application;

[0090] Figure 9 A schematic diagram of the structure of a data backup device according to an embodiment of this application;

[0091] Figure 10 A schematic diagram of the structure of the data backup device according to Embodiment 2 of this application;

[0092] Figure 11 This is a schematic diagram of the server structure provided in an embodiment of this application.

[0093] The accompanying drawings have illustrated specific embodiments of this disclosure, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this disclosure to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0094] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0095] Before introducing the embodiments of this application, the application background of the embodiments of this application will be explained first:

[0096] Network Attached Storage (NAS) is connected to a network and provides data storage capabilities, hence it is also called "network storage." NAS can solve many problems related to file storage, hierarchical access control, high-performance disk read / write, high-bandwidth network input / output, and data security. Therefore, it is typically used in dedicated data storage servers. Workstations or servers can access files on the NAS through Network File System (NFS) or Common Internet File System (CIFS). Backing up data to a NAS allows for timely data recovery after system data loss, effectively reducing losses due to data loss and further improving data security.

[0097] Currently, data backup mainly involves the system receiving a user's backup request, randomly selecting one node in the system cluster as the master node, and the other nodes as slave nodes. The master node outputs a start backup command to the Roach tool of that node, and through the Roach tool, notifies the Roach tools of the other slave nodes to start. This allows all nodes to retrieve the data to be backed up from their own database through their own started Roach tool, and then transmit the data to be backed up to the server through the MML interface for backup.

[0098] Furthermore, after a successful data backup, the system can receive a recovery request from the user, obtain the storage path address of the data to be recovered on the server based on the recovery request, retrieve the data to be recovered based on that storage address, and send it to the user.

[0099] However, if the MML interface malfunctions during the backup process, the backup of that node's data will fail. When using another MML interface to continue backing up this data, it cannot be guaranteed that the storage path of the data will be consistent between the two backups, resulting in poor fault tolerance in the backup process.

[0100] To address the aforementioned problems, the inventive concept of this application is as follows: If backup data exists in multiple storage paths, data needs to be retrieved from multiple addresses separately during data recovery, resulting in low recovery efficiency. Based on this, the inventors discovered that if the storage address of the backup data is stored in a storage path database when backing up data using the MML interface, then when an MML interface malfunctions and backup continues using another MML interface, the data is stored according to the storage address in the storage path database, thus solving the problem of low efficiency in restoring backed-up data in the prior art.

[0101] For example, the data backup method provided in this application embodiment can be applied to Figure 1The diagram shows one application scenario. Figure 1 This diagram illustrates an application scenario of the data backup method provided in this application, used to solve the aforementioned technical problems. Figure 1 As shown, this application scenario may include at least one node server (such as...) Figure 1 Node server 11, node server 12), and at least two interface servers (e.g., Figure 1 The system includes interface servers 13 and 14, at least one backup server (backup server 15 and backup server 16), and a storage path database 17. Node servers 11 and 12 form a node server cluster, interface servers 13 and 14 form an interface server cluster, and backup servers 15 and 16 form a backup server cluster.

[0102] Among them, the interface server can be a Backup Services Application Programming Interface (XBSA) server.

[0103] In this embodiment, the node server sends a backup request to the interface server. Upon receiving the backup request, the interface server sends a target storage path retrieval request to the backup server. After receiving the target storage path retrieval request, the backup server generates a target storage path for storing the backup data based on the target storage path, stores the target storage path in the storage path database, and sends it to the interface server. Upon receiving the target storage path from the backup server, the interface server stores the data to be stored in the NAS of the backup server corresponding to the target storage path.

[0104] Furthermore, when the interface server (e.g., interface server 1) malfunctions and cannot function properly, the node server generates a new backup request based on the data that was not successfully backed up in the backup data and sends it to the interface server (e.g., interface server 2) which is functioning normally. Upon receiving the new backup request, the interface server in normal working order sends a new target storage path retrieval request to the backup server. Upon receiving the new target storage path retrieval request, the backup server retrieves the target storage path for storing the data to be backed up from the storage path database and sends it to the interface server in normal working order. The interface server in normal working order, upon receiving the target storage path from the backup server, stores the data to be stored in the NAS of the backup server corresponding to the target storage path.

[0105] It should be noted that, in Figure 1In this context, the interface server and the node server can be independent and different servers, or the functions of the interface server and the node server can be integrated on the same server.

[0106] It should be understood that this application does not limit the number of backup servers, which can be determined based on the size of the data to be backed up.

[0107] The technical solution of this application will now be described in detail through specific embodiments.

[0108] It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0109] Figure 2 This is a flowchart illustrating an embodiment of the data backup method provided in this application. Figure 2 As shown, the data backup method may include the following steps:

[0110] S21. Receive the first backup request sent by the first node server.

[0111] In this step, when the first node server backs up the first data to be backed up through the second interface server, and the second node fails and cannot function properly, it can generate a first backup request based on the data in the first data to be backed up that was not successfully backed up, and send it to the first interface server. This first backup request includes the identifier of the first data to be backed up and the data in the first data that the second interface server failed to back up successfully. The first interface server then receives the first backup request from the first node server to facilitate subsequent backup of the data that was not successfully backed up in the first backup request.

[0112] The first data to be backed up can be a data stream, which can be obtained by splitting the data according to a preset data size by the first node server.

[0113] Optionally, the node server and the interface server are pre-bound.

[0114] S22. Send a request to obtain the first target storage path to any backup server in the backup server cluster.

[0115] In this step, after receiving the first backup request, the first interface server needs to obtain the storage path for backing up the first data to be backed up. Specifically, the first interface server sends a first target storage path retrieval request to any backup server in the backup server cluster. This first target storage path retrieval request is used to obtain the first target storage path pre-stored in the storage path database. This first target storage path is the storage path for backing up the first data to be backed up.

[0116] The first target storage path acquires an identifier including the first data to be backed up.

[0117] Optionally, the first interface server can connect to any backup server in the backup server cluster via Transmission Control Protocol (TCP), or it can connect via existing connection methods or protocols. This application does not impose any specific restrictions on this.

[0118] To illustrate this solution more clearly, this embodiment uses sending a first target storage path retrieval request to the first backup server in the backup server cluster as an example.

[0119] It should be understood that the first interface server can also send a first target storage path retrieval request to the second backup server or other backup servers in the backup server cluster.

[0120] For the first backup server, it receives the first target storage path retrieval request sent by the first interface server in the interface server cluster.

[0121] S23. Based on the first target storage path retrieval request, retrieve the first target storage path that is pre-stored in the storage path database.

[0122] In this step, after receiving the first target storage path retrieval request sent by the first interface server, the first backup server retrieves 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 retrieval request.

[0123] S24. Send the first target storage path to the first interface server.

[0124] For the first interface server, it receives the first target storage path returned by the first backup server.

[0125] S25. Store the data that was not successfully backed up to the NAS of the backup server corresponding to the first target storage path.

[0126] In this example, the data that was not successfully backed up is stored in the network-attached storage (NAS) of the first backup server.

[0127] The data backup method provided in this application embodiment involves a first interface server receiving a first backup request from a first node server and sending a first target storage path retrieval request to a first backup server. The first backup server, based on the received first target storage path retrieval request, retrieves a first target storage path pre-stored in a storage path database and sends it to the first interface server. The first interface server receives the first target storage path and stores the data that the second interface server failed to back up in the first backup request's first backup data into the NAS of the backup server corresponding to the first target storage path. This solution ensures that the interface server cluster stores the first backup data in the same storage address. During subsequent data recovery processing of this first backup data, data only needs to be retrieved once from a single storage address, improving the efficiency of data recovery. Placing the first backup data in the same storage address also enables more effective data management, preventing data loss due to excessive data storage locations and further enhancing data security.

[0128] Optionally, in some embodiments, the backup server cluster can be replicated to another cluster (e.g., the first backup server cluster) so that when the backup server cluster fails and cannot function properly, the interface server cluster can connect to the first backup server cluster to continue the data recovery process.

[0129] It should be understood that the first interface server can continue to back up the data after the second interface server fails during the data backup process, and can also directly receive backup requests sent by the node server and back up the data carried in the backup request.

[0130] Figure 3 This is a flowchart illustrating a second embodiment of the data backup method provided in this application. Figure 3 As shown, the data backup method may include the following steps:

[0131] S31. Receive the second backup request sent by the second node server.

[0132] In this step, when the second node server needs to back up the second data to be backed up, it can send a second backup request. This second backup request includes the second data to be backed up and its identifier. Correspondingly, the first interface server receives the second backup request sent by the second node server.

[0133] S32. Based on the identifier of the second data to be backed up, send a request to obtain the second target storage path to any backup server in the backup server cluster.

[0134] In this step, after receiving the second backup request, the first interface server needs to obtain the storage path used to store 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. This second target storage path acquisition request is used to obtain the second target storage path, which is used to store the second data to be backed up.

[0135] Optionally, the second target storage path acquisition request includes the type and size of the second data to be backed up.

[0136] To illustrate this solution more clearly, this embodiment uses sending a request to the first backup server in the backup server cluster to obtain the second target storage path as an example.

[0137] It should be understood that the first interface server can also send a second target storage path retrieval request to the second backup server or other backup servers in the backup server cluster.

[0138] For the first backup server, it receives the second target storage path acquisition request sent by the first interface server.

[0139] S33. Generate the second target storage path based on the request for the second target storage path.

[0140] In this step, after receiving the request to obtain the second target storage path, the first backup server needs to generate a storage address for backing up the second backup data based on the request.

[0141] In one possible implementation, the first backup server generates the second target storage path based on the type of the second backup data in the request, the size of the second backup data, and the space size of each partition in the NAS of the first backup server.

[0142] S34. Store the second target storage path in the storage path database and send it to the first interface server.

[0143] In this step, after generating the second target storage path, the second target storage path is stored in the storage path database so that if the first interface server fails, other interface servers can continue to back up the data that was not successfully backed up in the second backup data according to the second target storage path stored in the storage path database.

[0144] Furthermore, the second target storage path is sent to the first interface server so that the first interface server can subsequently store the second data to be backed up into the space corresponding to the second target storage path.

[0145] For the first interface server, it receives the second target storage path returned by the backup server.

[0146] S35. The second data to be backed up is stored in the NAS of the first backup server corresponding to the second target storage path.

[0147] The data backup method provided in this application embodiment involves a first interface server receiving a second backup request from a second node server. Based on the second data to be backed up carried in the second backup request, the first backup server sends a second target storage path retrieval request to the first backup server. The first backup server generates a second target storage path based on the received request and sends it to the first interface server. Upon receiving the second target storage path, the first interface server stores the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path. After generating the second target storage path, the first backup server stores it in a storage path database. This ensures that if the first interface server fails, other interface servers can continue to back up the data that was not successfully backed up in the second data to be backed up based on the second target storage path stored in the storage path database, guaranteeing that the second data to be backed up corresponds to only one storage address.

[0148] Furthermore, after backing up the data, in the event of unexpected situations such as loss or missing data originally stored in the node server, the data can be recovered.

[0149] Figure 4 This is a flowchart illustrating a third embodiment of the data backup method provided in this application. Figure 4 As shown, based on the above embodiments, after storing the second data to be backed up into the NAS of the first backup server corresponding to the second target storage path, the data backup method for the first interface server side may include the following steps:

[0150] S41. Receive the first data recovery request sent by the second node server.

[0151] In this step, when the first target data is lost, missing, or incorrectly modified beyond repair, and data recovery of the first target data is required, the second node server can send a first data recovery request to the first interface server. This first data recovery request includes the identifier of the first target data.

[0152] The first target data is the data that has already undergone the aforementioned backup process.

[0153] S42. Based on the first target path corresponding to the identifier of the first target data, obtain the first target data from the NAS corresponding to the first target path.

[0154] In this step, after the first interface server obtains the identifier of the first target data, it needs to obtain the address where the first target data is stored in the NAS.

[0155] In one possible implementation, the first interface server obtains the first target path corresponding to the identifier of the first target data based on the mapping relationship between data identifiers and paths. It should be understood that the mapping relationship between data identifiers and paths can be generated based on the identifier 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 described in the above embodiments, and the first target path in this embodiment is the storage address of the data to be backed up stored on the backup server.

[0156] S43. Send the first target data to the second node server.

[0157] In this embodiment, the first interface server receives a first data recovery request sent by the second node server. The data recovery request includes an identifier for first target data. Based on the first target path corresponding to the identifier of the first target data, the first target data is retrieved from the NAS corresponding to the first target path and then sent to the second node server. This embodiment only requires accessing one path and retrieving the data to be recovered from that path during data recovery, effectively improving data recovery efficiency and reducing the workload on the first interface server.

[0158] Figure 5 This is a flowchart illustrating Embodiment 4 of the data backup method provided in this application. Figure 5 As shown, based on the above embodiments, before storing the unbacked-up data into the NAS of the backup server corresponding to the first target storage path, the data backup method may include the following steps:

[0159] S51. Send a file system retrieval request to the backup server corresponding to the first target storage path.

[0160] To illustrate this solution more clearly, this embodiment uses the backup server corresponding to the first target storage path as an example for explanation.

[0161] It should be understood that the backup server corresponding to the first target storage path can also be the second backup server or other backup servers in the backup server cluster.

[0162] In this step, the first interface server can obtain the first file system of the second interface server in the backup server corresponding to the first target storage path, so as to store the data that the second interface server failed to back up in the first data to be backed up through the first file system.

[0163] The file system retrieval request is used to retrieve the first file system corresponding to the second interface server in the backup server.

[0164] For the first backup server, it receives the file system retrieval request sent by the first interface server.

[0165] S52, Send the first file system to the first interface server.

[0166] Furthermore, the first backup server obtains the first file system based on the file system retrieval request and sends the first file system to the first interface server.

[0167] For the first interface server, it receives the first file system sent by the first backup server.

[0168] Accordingly, S25 can be achieved through the following steps:

[0169] Mount a second file system and use the mounted second file system to store the second data to be backed up to the NAS corresponding to the second target storage path.

[0170] Figure 6 This is a flowchart illustrating Embodiment 4 of the data backup method provided in this application. Figure 6 As shown, based on the above embodiment, before receiving the second backup request sent by the second node server, the data backup method may include the following steps:

[0171] S61. Send a file system creation request to the first backup server.

[0172] In this step, the first interface server can obtain the second file system of the first interface server in the first backup server, so as to store the data that the second interface server failed to back up in the second backup data through the second file system.

[0173] The file system creation request is used to instruct the first backup server to create a second file system corresponding to the first interface server in the first backup server.

[0174] For the first backup server, it receives the file system creation request sent by the first interface server.

[0175] S62. If a second file system does not exist, create a second file system and send the second file system to the first interface server.

[0176] S63. If a second file system exists, send the second file system to the first interface server.

[0177] For the first node server, it receives the second file system sent by the backup server.

[0178] Accordingly, S35 can be implemented through the following steps:

[0179] Mount the first file system and use it to store the data that was not successfully backed up to the NAS corresponding to the first target storage path.

[0180] Figure 7 This is a flowchart illustrating Embodiment Six of the data backup method provided in this application. Figure 7 As shown, the data backup method may include the following steps:

[0181] S71. Send a file system creation request to the first backup server.

[0182] When the first interface server starts up, it sends a file system creation request to the first backup server.

[0183] For the first backup server, it receives the file system creation request sent by the first interface server.

[0184] S72. Based on the file system creation request, create the first file system in the NAS.

[0185] S73, Send the first file system to the first interface server.

[0186] For the first interface server, it receives the first file system.

[0187] S74. Send a backup start request to the first interface server.

[0188] In this step, the second node server needs to load libxbsa.so in order to send a second backup request to the first interface server.

[0189] For the first interface server, it then receives the second backup request.

[0190] S75. Mount the first file system and send a request to the first backup server to obtain the second target storage path.

[0191] For the first backup server, it receives the request to obtain the second target storage path.

[0192] S76. Generate the second target storage path based on the request for the second target storage path.

[0193] S77. Store the second target storage path in the storage path database and send it to the first interface server.

[0194] For the first interface server, it receives the second target storage path.

[0195] S78. Send the second backup data to the first interface server.

[0196] The second data to be backed up can be a data stream.

[0197] For the first interface server, it receives the second set of backup data.

[0198] S79. The second data to be backed up is stored in the NAS of the first backup server corresponding to the second target storage path.

[0199] S710 sends a backup completion request to the first interface server.

[0200] For the first interface server, it receives the backup completion request.

[0201] S711, Send a backup completion request to the first backup server.

[0202] For the first backup server, it receives the backup completion request.

[0203] S712, Unmount the first file system.

[0204] It should be understood that the backup start request, the second backup data, and the backup end request in the embodiments of this application together constitute the second backup request in the above embodiments.

[0205] Figure 8 This is a flowchart illustrating Embodiment Seven of the data backup method provided in this application. Figure 8 As shown, the data backup method may include the following steps:

[0206] S81, Send a data query command to the first interface server.

[0207] In this step, the second node server needs to load libxbsa.so.

[0208] The data query command is used to view the data in the NAS.

[0209] For the first interface server, it receives data query requests.

[0210] S82, Send a data query request to the first backup server.

[0211] For the first backup server, it receives data query requests.

[0212] S83. Based on the data query request, obtain the data information and send it to the first interface server.

[0213] For the first interface server, it receives data information.

[0214] S84. Send the data information to the second node server.

[0215] For the second node server, it receives data information.

[0216] S85, Mount the first file system.

[0217] S86. Determine the first target data based on the data information and generate a data acquisition request.

[0218] The data acquisition request includes the first target data.

[0219] S87. Send the data acquisition start request to the first interface server.

[0220] The data acquisition request includes the identifier of the first target data.

[0221] For the first interface server, it then receives data and begins the data acquisition request.

[0222] S88. Based on the first target path corresponding to the identifier of the first target data, obtain the first target data from the NAS corresponding to the first target path.

[0223] S89. Send the acquired first target data to the second node server.

[0224] S810: Send data to the first interface server to end the data acquisition request.

[0225] For the first interface server, receiving data completes the retrieval request.

[0226] It should be understood that the second-node server can repeatedly send the identifier of the target data to the first interface server. The first interface server retrieves the corresponding target data based on the received target data identifier and sends it to the second-node server. The retrieval request ends when the first interface server directly receives the data sent by the second-node server.

[0227] For the second node server, it receives the first target data.

[0228] S811, Unmount the first file system.

[0229] It should be understood that the data query request, data start acquisition request, and data end acquisition request in the embodiments of this application together constitute the first data recovery request in the above embodiments.

[0230] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0231] Figure 9 This is a schematic diagram of the structure of a data backup device according to an embodiment of this application. Figure 9 As shown, the data backup device is applied to the first interface server in the interface server cluster. The interface server cluster includes the first interface server and the second interface server. The data backup device includes:

[0232] The receiving module 91 is used to receive a first backup request sent by the first node server. The first backup request includes the identifier of the first data to be backed up and the data in the first data to be backed up that the second interface server failed to back up successfully.

[0233] The sending module 92 is used to send 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 to obtain the first target storage path pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up, and the first target storage path is the storage path when backing up the first data to be backed up.

[0234] The receiving module 91 is used to receive the first target storage path returned by the backup server.

[0235] Processing module 93 is used to store data that was not successfully backed up to the network-attached storage (NAS) of the backup server corresponding to the first target storage path.

[0236] In one possible design of this application embodiment, the receiving module 91 is further configured to receive a second backup request sent by the second node server, the second backup request including second data to be backed up and an identifier of the second data to be backed up.

[0237] The sending module 92 is also used 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. The second target storage path acquisition request is used to acquire the second target storage path, and the second target storage path is used to store the second data to be backed up.

[0238] The receiving module 91 is also used to receive the second target storage path returned by the backup server.

[0239] The processing module 93 is also used to store the second data to be backed up to the NAS of the first backup server corresponding to the second target storage path.

[0240] 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, the first data recovery request including the identifier of the first target data.

[0241] The processing module 93 is also used to obtain 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.

[0242] The sending module 92 is also used to send the first target data to the second node server.

[0243] In another possible design of this application embodiment, before storing the unbacked-up data into 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 acquisition request to the backup server corresponding to the first target storage path. The file system acquisition request is used to acquire the first file system corresponding to the second interface server in the backup server.

[0244] The receiving module 91 is also used to receive the first file system sent by the backup server.

[0245] Correspondingly, processing module 93 is specifically used for:

[0246] Mount the first file system and use it to store the data that was not successfully backed up to the NAS corresponding to the first target storage path.

[0247] 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. 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.

[0248] The receiving module 91 is also used to receive the second file system sent by the first backup server.

[0249] Correspondingly, processing module 93 is specifically used for:

[0250] Mount a second file system and use the mounted second file system to store the second data to be backed up to the NAS corresponding to the second target storage path.

[0251] The data backup device provided in this application embodiment can be used to execute the data backup method on the interface server side in any of the above embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0252] Figure 10This is a schematic diagram of the structure of a data backup device according to a second embodiment of this application. Figure 10 As shown, the data backup device is used on the first backup server in the backup server cluster, and the device includes:

[0253] The receiving module 101 is used to receive a first target storage path acquisition request sent by the first interface server in the interface server cluster. The first target storage path acquisition request is used to acquire a first target storage path that is pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up, and the first target storage path is the storage path when backing up the first data to be backed up.

[0254] The processing module 102 is used to obtain the first target storage path pre-stored in the storage path database according to the first target storage path acquisition request.

[0255] The sending module 103 is used to send the first target storage path to the first interface server.

[0256] In one possible design of this application embodiment, the receiving module 101 is further configured to receive a second target storage path acquisition request sent by the first interface server. 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.

[0257] The processing module 102 is also used to generate a second target storage path based on the request obtained from the second target storage path.

[0258] The sending module 103 is also used to store the second target storage path in the storage path database and send it to the first interface server.

[0259] Optionally, before receiving the second target storage path acquisition 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, the file system establishment request being used to establish a second file system corresponding to the first node server in the first backup server.

[0260] The sending module 103 is also used to create a second file system when the second file system does not exist, and send the second file system to the first interface server.

[0261] The sending module 103 is also used to send the second file system to the first interface server when the second file system exists.

[0262] In another possible design of this application embodiment, before sending the first target storage path 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. The file system acquisition request is used to acquire the first file system corresponding to the second node server in the first backup server.

[0263] The sending module 103 is also used to send the first file system to the first interface server.

[0264] The data backup device provided in this application embodiment can be used to execute the data backup method on the backup server side in any of the above embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0265] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. Additionally, these modules can be fully or partially integrated together, or implemented independently. The processing element mentioned here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through the integrated logic circuits in the hardware of the processor element or through software instructions.

[0266] Figure 11 This is a schematic diagram of the server structure provided in an embodiment of this application. Figure 11 As shown, the server may include: a processor 111, a memory 112, a transceiver 113, and computer program instructions stored on the memory 112 and executable on the processor 111. When the processor 111 executes the computer program instructions, it implements the data backup method provided in any of the foregoing embodiments.

[0267] Optionally, the various components of the server can be connected via a system bus.

[0268] The memory 112 can be a separate memory unit or a memory unit integrated into the processor. The number of processors can be one or more.

[0269] Optionally, the server may also include interfaces for interacting with other devices.

[0270] The transceiver 82 is used to communicate with other computers, and the transceiver 82 constitutes a communication interface.

[0271] Optionally, in terms of hardware implementation, the above Figure 9In the illustrated embodiment: receiving module 91 and transmitting module 92, and the above-mentioned Figure 10 In the illustrated embodiment: the receiving module 101 and the transmitting module 103 correspond to the transceiver 113 in this embodiment. Figure 9 The processing module 93 in the illustrated embodiment and the above-described Figure 10 The processing module 102 in the illustrated embodiment corresponds to the processor 111 in this embodiment.

[0272] It should be understood that the processor 111 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0273] The system bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The system bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus. Memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0274] All or part of the steps in the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above-described method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0275] The server provided in this application embodiment can be used to execute the data backup method provided in any of the above method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0276] This application provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to perform the aforementioned data backup method.

[0277] The aforementioned computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory, electrically erasable programmable read-only memory, erasable programmable read-only memory, programmable read-only memory, read-only memory, magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0278] Optionally, a readable storage medium can be coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Alternatively, the readable storage medium can be an integral part of the processor. Both the processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components within the device.

[0279] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the above-mentioned data backup method.

[0280] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A data backup method, characterized in that, The method is applied to a first interface server in an interface server cluster, the interface server cluster including the first interface server and a second interface server, and includes: Receive a first backup request sent by the first node server. The first backup request includes an identifier of the first data to be backed up and the data in the first data to be backed up that the second interface server failed to back up successfully. The first backup request is performed using the MML interface. Send 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 to obtain a first target storage path that is pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up. The first target storage path is the storage path when backing up the first data to be backed up. Receive the first target storage path returned by the backup server; The data that was not successfully backed up is stored in the network auxiliary storage (NAS) of the backup server corresponding to the first target storage path; Before storing the unbacked-up data in the NAS of the backup server corresponding to the first target storage path, the method further includes: Send a file system retrieval request to the backup server corresponding to the first target storage path. The file system retrieval request is used to retrieve the first file system corresponding to the second interface server in the backup server. Receive the first file system sent by the backup server; Accordingly, storing the data that was not successfully backed up to the NAS of the backup server corresponding to the first target storage path includes: Mount the first file system and use the mounted first file system to store the data that was not successfully backed up to the NAS corresponding to the first target storage path.

2. The method according to claim 1, characterized in that, The method further includes: Receive a second backup request sent by the second node server, the second backup request including second data to be backed up and an identifier of the second data to be backed up; Based on the identifier 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. The second target storage path acquisition request is used to acquire the second target storage path, and the second storage path is used to store the second data to be backed up. Receive the second target storage path returned by the backup server; The second data to be backed up is stored in the NAS of the first backup server corresponding to the second target storage path.

3. The method according to claim 2, characterized in that, 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 includes: Receive a first data recovery request sent by the second node server, wherein the first data recovery request includes an identifier of the first target data; Based on the first target path corresponding to the identifier of the first target data, the first target data is obtained from the NAS corresponding to the first target path; The first target data is sent to the second node server.

4. The method according to claim 2 or 3, characterized in that, Before receiving the second backup request sent by the second node server, the method further includes: Send a file system creation request to the first backup server. The file system creation request is used to instruct the first backup server to create a second file system corresponding to the first interface server in the first backup server. Receive the second file system sent by the first backup server; Accordingly, storing the second data to be backed up in the NAS of the first backup server corresponding to the second target storage path includes: Mount the second file system and use the mounted second file system to store the second data to be backed up to the NAS corresponding to the second target storage path.

5. A data backup method, characterized in that, The method, applied to the first backup server in a backup server cluster, includes: The first target storage path acquisition request is sent by the first interface server in the interface server cluster. The first target storage path acquisition request is used to obtain the first target storage path pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up. The first target storage path is the storage path when backing up the first data to be backed up. Before the first target storage path acquisition request sent by the first interface server in the receiving interface server cluster, the method further includes: the first interface server receiving a first backup request sent by the first node server, the first backup request including an identifier of the first data to be backed up and the data in the first data to be backed up that the second interface server failed to back up successfully, the first backup request being backed up using the MML interface; Based on the first target storage path retrieval request, retrieve the first target storage path that is pre-stored in the storage path database; Sending the first target storage path to the first interface server, so that the first interface server stores the data that was not successfully backed up to the network attached storage (NAS) of the backup server corresponding to the first target storage path, wherein, before storing the data that was not successfully backed up to the backup server corresponding to the first target storage path, the method further includes: receiving a file system acquisition request sent by the first interface server, the file system acquisition request being used to acquire a first file system corresponding to the second interface server in the backup server; sending the first file system to the first interface server, so that the first interface server stores the data that was not successfully backed up to the network attached storage (NAS) of the backup server corresponding to the first target storage path, including mounting the first file system on the first interface server, and using the mounted first file system to store the data that was not successfully backed up to the NAS corresponding to the first target storage path.

6. The method according to claim 5, characterized in that, The method further includes: Receive a second target storage path acquisition request sent by the first interface server. The second target storage path acquisition request is used to acquire a second target storage path, and the second storage path is used to store the second data to be backed up. Based on the second target storage path retrieval request, generate the second target storage path; The second target storage path is stored in the storage path database and then sent to the first interface server.

7. The method according to claim 6, characterized in that, Before receiving the second target storage path retrieval request sent by the first interface server, the method further includes: Receive a file system creation request sent by the first interface server, the file system creation request being used to create a second file system corresponding to the first node server in the first backup server; If the second file system does not exist, create the second file system and send it to the first interface server; If the second file system exists, the second file system is sent to the first interface server.

8. The method according to claim 5, characterized in that, Before sending the first target storage path to the first interface server, the method further includes: Receive a file system retrieval request sent by the first interface server, the file system retrieval request being used to retrieve the first file system corresponding to the second node server in the first backup server; Send the first file system to the first interface server.

9. A data backup device, characterized in that, A first interface server used in an interface server cluster, the interface server cluster including the first interface server and a second interface server, the device comprising: The receiving module is used to receive a first backup request sent by the first node server. The first backup request includes an identifier of the first data to be backed up and the data in the first data to be backed up that the second interface server failed to back up successfully. The first backup request is performed using the MML interface. The sending module is used to send 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 to acquire a first target storage path pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up. The first target storage path is the storage path when backing up the first data to be backed up. The receiving module is used to receive the first target storage path returned by the backup server; The processing module is used to store the data that was not successfully backed up to the network attached storage (NAS) of the backup server corresponding to the first target storage path; The processing module is used to store the data that failed to be backed up to the NAS of the backup server corresponding to the first target storage path before storing the data. The sending module is further configured to send a file system acquisition request to the backup server corresponding to the first target storage path, the file system acquisition request being used to acquire the first file system corresponding to the second interface server in the backup server; The receiving module is also used to receive the first file system sent by the backup server; The processing module is specifically used to mount the first file system and use the mounted first file system to store the data that was not successfully backed up to the NAS corresponding to the first target storage path.

10. A data backup device, characterized in that, The apparatus is used as a first backup server in a backup server cluster, and includes: The receiving module is used to receive a first target storage path acquisition request sent by the first interface server in the interface server cluster. The first target storage path acquisition request is used to acquire a first target storage path pre-stored in the storage path database. The first target storage path acquisition request includes the identifier of the first data to be backed up. The first target storage path is the storage path when backing up the first data to be backed up. Before receiving a first target storage path acquisition request sent by a first interface server in the interface server cluster, the receiving module is further configured for the first interface server to receive a first backup request sent by a first node server. The first backup request includes an identifier of the first data to be backed up and data in the first data to be backed up that the second interface server failed to back up successfully. The first backup request is performed using an MML interface. The processing module is used to obtain the first target storage path pre-stored in the storage path database according to the first target storage path acquisition request; The sending module is configured to send the first target storage path to the first interface server so that the first interface server stores the data that was not successfully backed up to the network attached storage (NAS) of the backup server corresponding to the first target storage path. Before storing the data that was not successfully backed up to the NAS of the backup server corresponding to the first target storage path, the receiving module is further configured to receive a file system acquisition request sent by the first interface server, the file system acquisition request being used to acquire a first file system corresponding to the second interface server in the backup server; and send the first file system to the first interface server. Specifically, the sending module is configured to send the first target storage path to the first interface server so that the first interface server mounts the first file system, and uses the mounted first file system to store the data that was not successfully backed up to the NAS corresponding to the first target storage path.

11. A server, comprising: A processor, a transceiver, a memory, and computer program instructions stored in the memory and executable on the processor, characterized in that the processor executes the computer program instructions to implement the data backup method as described in any one of claims 1 to 8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the data backup method as described in any one of claims 1 to 8.

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it is used to implement the data backup method as described in any one of claims 1 to 8.

Images