Cross-machine-room data backup method, device and system and electronic equipment

Abstract

The invention discloses a cross-machine-room data backup method, device and system and electronic equipment. The method is applied to a cross-computer-room data backup system, and comprises the following steps: a source backup server obtains a data storage rule, and uniformly stores to-be-backed-up data on a plurality of cluster nodes of each application in a first computer room to a corresponding storage position of the source backup server according to the data storage rule, sending the data storage rule and the uniformly stored data to be backed up to a target backup server through a data backup link between the source backup server and the target backup server; the destination backup server receives the data storage rule and the to-be-backed-up data sent by the source backup server through the data backup link, and sends the to-be-backed-up data at each storage position to the cluster node of the corresponding application in the second machine room according to the data storage rule; and performing data backup on the cluster node of the application in the second machine room according to the to-be-backed-up data.

Description

Technical Field

[0001] The present application relates to the technical field of data storage, and in particular, to a cross-data center data backup method, apparatus, system, and electronic device. Background Art

[0002] Data disaster recovery refers to establishing a remote data system so that when the system fails, data security can be protected, and even uninterrupted application services can be provided.

[0003] In the cross-data center remote disaster recovery scenario, usually each application needs to establish at least one data backup link for cross-data center backup. Taking Figure 1 the scenario shown as an example, assume there are four applications, namely Jira, Wiki, Crowd, and NFS (Network File System). These four applications are deployed in a cluster mode in two data centers. If each cluster includes three cluster nodes, then when performing cross-data center backup, twelve data synchronization links need to be established and maintained.

[0004] It can be seen that in the prior art, when performing cross-data center data backup, the number of data path links to be maintained is related to the number of applications and the number of cluster nodes. As the number of applications and / or the number of cluster nodes increases, the number of data path links to be maintained will increase multiplicatively, which will occupy a relatively high operation and maintenance cost. Summary of the Invention

[0005] The purpose of the embodiments of the present application is to at least solve one of the above technical defects, and particularly provide a cross-data center data backup method, apparatus, system, and electronic device.

[0006] The embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, the embodiments of the present application provide a cross-data center data backup method, which is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in a first data center and a destination backup server located in a second data center. The cross-data center data backup method is executed by the source backup server, and the method includes:

[0008] Obtain a data storage rule, where the data storage rule includes a mapping relationship between the storage location of the data to be backed up and the cluster node where the data to be backed up is located;

[0009] According to the data storage rule, uniformly store the data to be backed up on multiple cluster nodes of each application in the first data center to the corresponding storage location of the source backup server;

[0010] Through the data backup link between the source backup server and the destination backup server, send the data storage rule and the data to be backed up stored uniformly to the destination backup server, so that the destination backup server distributes the data to be backed up to the cluster nodes of the corresponding application in the second computer room according to the data storage rule.

[0011] In a second aspect, an embodiment of the present application further provides a cross-computer-room data backup method, which is applied to a cross-computer-room data backup system. The cross-computer-room data backup system includes a source backup server located in a first computer room and a destination backup server located in a second computer room. The cross-computer-room data backup method is executed by the destination backup server, and the method includes:

[0012] Through the data backup link between the source backup server and the destination backup server, receive the data sent by the source backup server, where the data includes a data storage rule and data to be backed up;

[0013] According to the data storage rule, send the data to be backed up at each storage location to the cluster nodes of the corresponding application in the second computer room, so that the cluster nodes of the application in the second computer room perform data backup according to the data to be backed up.

[0014] In a third aspect, an embodiment of the present application further provides a cross-computer-room data backup device, which is applied to a cross-computer-room data backup system. The cross-computer-room data backup system includes a source backup server located in a first computer room and a destination backup server located in a second computer room. The cross-computer-room data backup device is applied to the source backup server, and the device includes:

[0015] A rule acquisition unit, configured to acquire a data storage rule, where the data storage rule includes a mapping relationship between a storage location of data to be backed up and a cluster node where the data to be backed up is located;

[0016] A unified storage unit, configured to uniformly store the data to be backed up on multiple cluster nodes of each application in the first computer room to the corresponding storage location of the source backup server according to the data storage rule;

[0017] A data sending unit, configured to send the data storage rule and the uniformly stored data to be backed up to the destination backup server through the data backup link between the source backup server and the destination backup server, so that the destination backup server distributes the data to be backed up to the cluster nodes of the corresponding application in the second computer room according to the data storage rule.

[0018] Fourth aspect, an embodiment of the present application further provides a cross-data center data backup device, which is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in a first data center and a destination backup server located in a second data center. The cross-data center data backup device is applied to the destination backup server, and the device includes:

[0019] A data receiving unit, configured to receive data sent by the source backup server through a data backup link between the source backup server and the destination backup server. The data includes a data storage rule and data to be backed up.

[0020] A data distribution unit, configured to send the data to be backed up at each storage location to cluster nodes of corresponding applications in the second data center according to the data storage rule, so that the cluster nodes of the applications in the second data center perform data backup according to the data to be backed up.

[0021] Fifth aspect, an embodiment of the present application further provides a cross-data center data backup system, which includes a source backup server and a destination backup server located in different data centers:

[0022] The source backup server is configured to establish a data backup link with the destination backup server and execute the cross-data center data backup method provided in the foregoing related embodiments.

[0023] The destination backup server is configured to execute the cross-data center data backup method provided in the foregoing related embodiments.

[0024] Sixth aspect, an embodiment of the present application further provides an electronic device, which includes:

[0025] A memory, storing computer-executable instructions;

[0026] A processor, when the computer-executable instructions are executed, causing the processor to execute the cross-data center data backup method.

[0027] Seventh aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores one or more programs. When the one or more programs are executed by an electronic device including multiple application programs, the electronic device is caused to execute the cross-data center data backup method.

[0028] At least one of the technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0029] The source backup server in the embodiment of the present application first obtains the data storage rule. On the one hand, by using the mapping relationship between the storage location of the data to be backed up and the cluster nodes where the data to be backed up is located in the data storage rule, the data to be backed up on multiple cluster nodes of each application in the first computer room is uniformly stored in the corresponding storage location of the source backup server. Furthermore, data cross-computer room transmission can be carried out through a single data backup link, reducing the link maintenance cost. On the other hand, during the data cross-computer room transmission process, the data storage rule and the uniformly stored data to be backed up are sent to the destination backup server together. In this way, the destination backup server can distribute the data to be backed up to the cluster nodes of the corresponding application in the second computer room according to the data storage rule, ensuring the accuracy of data distribution and thus improving the reliability of data backup. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The drawings described herein are used to provide a further understanding of the present application and form a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0031] Figure 1 is a schematic flow chart of cross-computer room data backup in the prior art;

[0032] Figure 2 is a schematic flow chart of a cross-computer room data backup method shown in the embodiment of the present application;

[0033] Figure 3 is a schematic flow chart of another cross-computer room data backup method shown in the embodiment of the present application;

[0034] Figure 4 is a schematic overall flow chart of cross-computer room data backup shown in the embodiment of the present application;

[0035] Figure 5 is a schematic structural diagram of a cross-computer room data backup device shown in the embodiment of the present application;

[0036] Figure 6 is a schematic structural diagram of another cross-computer room data backup device shown in the embodiment of the present application;

[0037] Figure 7 is a schematic structural diagram of an electronic device shown in the embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments of this application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.

[0039] The following will, with reference to the drawings, elaborate on the technical solutions provided by each embodiment of this application.

[0040] An embodiment of this application provides a cross-data center data backup method. As Figure 2 shown, a flowchart of a cross-data center data backup method in an embodiment of this application is provided. The method at least includes the following steps S210 to step S230:

[0041] Step S210: Obtain a data storage rule, where the data storage rule includes a mapping relationship between the storage location of the data to be backed up and the cluster nodes where the data to be backed up is located.

[0042] The cross-data center data backup method of the embodiment of this application is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in a first data center and a destination backup server located in a second data center. The cross-data center data backup method is executed by the source backup server. The source backup server can be any server with sufficient storage space in the first data center. For example, it can be a database server or a file system server.

[0043] In some scenarios, the source backup server can create a data storage rule in advance and store it locally. When performing cross-data center data backup, it obtains the data storage rule from local. In other scenarios, the source backup server can also create a data storage rule in real time. For example, it creates a data storage rule according to the application cluster architecture information, and the application cluster architecture information at least includes the cluster information of all applications in the first data center. For example, through the application cluster architecture information of the first data center, each cluster node where the same application is deployed in the first data center and the startup relationship between each cluster node can be obtained. The embodiment of this application can obtain its application cluster architecture information through the global network view of the first data center. The global network view can be understood as a data plane containing the full visualization information of the network of the first data center. Of course, the application cluster architecture information of the first data center can also be collected by a network controller, and the source backup server obtains the application cluster architecture information of the first data center by interacting with the network controller.

[0044] The data storage rule in the embodiment of the present application stipulates the mapping relationship between the storage location of the data to be backed up and the cluster node where the data to be backed up is located. Here, the storage location of the data to be backed up is obtained by the source backup server allocating its data storage space according to the set storage location allocation principle. The data storage space is, for example, disk space or a database. When the data storage space is disk space, the source backup server can create a directory, and then obtain the storage location for storing the data to be backed up of each collection node (the storage location at this time specifically refers to the relative path address of the disk space); when the data storage space is a database, the source backup server can create a database table, and then obtain the storage location for storing the data to be backed up of each collection node (the storage location at this time specifically refers to the positions of each element in the database table).

[0045] In this way, the data storage rule in the embodiment of the present application can be a directory structure or a table structure. For example, when the source backup server is a file system server, the data storage space of the file system server is disk space, and the data structure corresponding to the data storage rule is a directory structure. When the source backup server is a database server, the data storage space of the database server is a database, and the data structure corresponding to the data storage rule is a database table structure.

[0046] Step S220, uniformly store the data to be backed up on multiple cluster nodes of each application in the first computer room to the corresponding storage location of the source backup server according to the data storage rule.

[0047] The data storage rule stipulates the mapping relationship between the storage location and the cluster node. The source backup server can uniformly store the data to be backed up of each application in the first computer room according to this mapping relationship, providing a basic condition for cross-computer room data transmission through a single data backup link.

[0048] In the process of uniformly storing data in the computer room in the embodiment of the present application, in some scenarios, the data to be backed up on each cluster node can be directly written to the corresponding storage location by means of data push; for example, the source backup server sends the storage location corresponding to each cluster node to the cluster node, and the cluster node pushes its own data to be backed up to the storage location of the source backup server through a data push command.

[0049] In other scenarios, the data to be backed up on each cluster node can be directly written to the corresponding storage location by means of data pull; for example, the source backup server obtains the address information of the data to be backed up of each cluster node, and the source backup server pulls the data to be backed up corresponding to the address information to the storage location of the source backup server through a data pull command.

[0050] It can be understood that when the data to be backed up in the first computer room is uniformly stored on the source backup server through this step, the source backup server can also manage the triggering conditions for the unified storage of data in the computer room. The triggering conditions include, for example, single triggering conditions such as time conditions and command conditions, or combined triggering conditions. Those skilled in the art can set them according to specific backup requirements, and the embodiments of the present application do not make special limitations.

[0051] Step S230: Send the data storage rule and the data to be backed up for unified storage to the destination backup server through the data backup link between the source backup server and the destination backup server, so that the destination backup server distributes the data to be backed up to the cluster nodes of the corresponding applications in the second computer room according to the data storage rule.

[0052] In the embodiments of the present application, the source backup server can establish a data backup link with the destination backup server. The creation process of the data backup link is not described in detail in the embodiments of the present application, and those skilled in the art can implement it in combination with the prior art. Regarding the creation time of the data backup link, the embodiments of the present application do not make special limitations. Those skilled in the art can start creating the data backup link after the unified storage of the data to be backed up in the computer room, or can start creating the data backup link before the unified storage of the data to be backed up in the computer room. Those skilled in the art can flexibly select the creation time of the data backup link.

[0053] It can be seen that through a data backup link, the embodiments of the present application can complete the cross-computer-room transmission of data. Compared with the existing transmission solutions, the embodiments of the present application can significantly reduce the maintenance cost of the link.

[0054] In addition, the embodiments of the present application send the data storage rule and the stored data to be backed up to the destination backup server together, enabling the destination backup server to accurately distribute the data to be backed up to the cluster nodes of the corresponding applications in the second computer room according to the data storage rule, ensuring the reliability of data backup.

[0055] Such as Figure 2As can be seen from the cross-data center data backup method shown above, the source backup server in the embodiment of the present application first obtains the data storage rule. On the one hand, by using the mapping relationship between the storage location of the data to be backed up and the cluster nodes where the data to be backed up is located in the data storage rule, the data to be backed up on multiple cluster nodes of each application in the first data center is uniformly stored in the corresponding storage location of the source backup server. Furthermore, data cross-data center transmission can be performed through a single data backup link, reducing the link maintenance cost. On the other hand, during the data cross-data center transmission process, the data storage rule and the uniformly stored data to be backed up are sent to the destination backup server together, so that the destination backup server distributes the data to be backed up to the cluster nodes of the corresponding application in the second data center according to the data storage rule, ensuring the accuracy of data distribution and thus improving the reliability of data backup.

[0056] In some embodiments of the present application, the data storage rule in the above step S210 further includes the constraint relationship between storage locations. Then, when creating the data storage rule, the method further includes:

[0057] Group the cluster nodes in the first data center according to the application cluster architecture information of the first data center to obtain the grouping information of the cluster nodes;

[0058] According to the grouping information of the cluster nodes and the mapping relationship between the cluster nodes and the storage locations, obtain the grouping information of the storage locations, so as to obtain the constraint relationship between the storage locations through the grouping information of the storage locations.

[0059] As described above, the application cluster architecture information at least includes the cluster information of all applications in the first data center. Therefore, according to the application cluster architecture information, all cluster nodes deploying the same application can be obtained. Furthermore, by grouping all the cluster nodes in the first data center according to the deployed applications, multiple groups can be obtained, and each group corresponds to a different application. Combining with the mapping relationship between the cluster nodes and the storage locations specified in the data storage rule, the allocated storage addresses on the source backup server can be further grouped. In this way, the constraint relationship between the storage locations can be obtained according to the grouping information of the storage addresses. For example, a directory-form constraint relationship can be constructed according to the grouping information of the storage addresses, or a table-form constraint relationship can be constructed according to the grouping information of the storage addresses. In this way, when uniformly storing the data to be backed up of each cluster node, the target storage address can be quickly queried according to the constraint relationship of the storage addresses, saving the query time.

[0060] For example, if there are M applications in the first computer room and each application is deployed in N cluster nodes, then when the source backup server creates a data storage rule, it will create M * N storage addresses. When the number of applications and cluster nodes is large, the number of created storage addresses will increase exponentially. Then, how to quickly query the target storage address among a large amount of storage addresses will become a problem. To address this issue, in this embodiment, the constraint relationship between storage locations is further specified through the data storage rule, and the query efficiency of the destination storage address is improved through the constraint relationship between storage locations.

[0061] In some embodiments of the present application, after performing step S220, the cross-computer-room data backup method of the embodiments of the present application further includes:

[0062] Perform data verification on the data to be backed up stored in each storage location to obtain a verification result, where the verification result includes verification success and verification failure;

[0063] Update the data storage rule according to the verification result, or delete the data to be backed up stored in the storage location according to the verification result.

[0064] When uniformly storing the data to be backed up in the computer room, due to problems such as network quality or services in the computer room, some storage locations may not receive the data to be backed up, or the received data to be backed up has incomplete data. To address such problems, in this embodiment, data verification can be performed on the data to be backed up stored in each storage location according to the verification code. If the data to be backed up stored in a certain storage location is verified successfully, it means that the data to be backed up stored in this storage location is complete data. If the data to be backed up stored in a certain storage location is verified failed, it means that the data to be backed up stored in this storage location is incomplete data, or this storage location has not received the data. At this time, data retransmission can be started for the data to be backed up with verification failure to obtain complete data to be backed up and ensure the reliability of data backup.

[0065] In some application scenarios of this embodiment, updating the data storage rule according to the verification result specifically includes: when the verification result is verification success, the data storage rule is not updated;

[0066] When the verification result is verification failure, obtain the data to be backed up through the data retransmission strategy, and perform data verification on the data to be backed up after data retransmission. If the verification result is verification success, the data storage rule is not updated. If the verification result is still verification failure, the data storage rule is updated by deleting the storage location.

[0067] For example, if the data to be backed up stored at storage location A still fails the verification after data retransmission, it indicates that the data to be backed up stored at storage location A is incomplete. To ensure the reliability of data backup, the data to be backed up should not be enabled. Therefore, storage location A can be deleted from the data storage rule. It can be understood that when storage location A is deleted, the data to be backed up of the cluster node that has a mapping relationship with storage location A will also be deleted. For example, the directory corresponding to storage location A is deleted in the storage directory, or the table element corresponding to storage location A is deleted in the database table. In this way, when performing cross-data center data transmission, the updated data storage rule and the uniformly stored data to be backed up are transmitted. Since the data to be backed up stored at each storage address in the updated data storage rule is complete data, it can meet the reliability requirements of data backup. Therefore, the destination backup server can distribute the received data to be backed up according to the updated data storage rule.

[0068] It should be noted that when the source backup server of the embodiment of the present application updates the data storage rule, a new data storage rule should be created during the next round of cross-data center data backup to obtain the full amount of data to be backed up and avoid missing the backup of a certain / some cluster nodes of a certain / some applications.

[0069] In some other application scenarios of this embodiment, deleting the data to be backed up stored at the storage location according to the verification result specifically includes:

[0070] When the verification result is successful, the data to be backed up at the storage location is retained;

[0071] When the verification result is a failure, the data to be backed up is obtained through a data retransmission policy, and the data to be backed up after data retransmission is verified. If the verification result is successful, the data to be backed up at the storage location is retained. If the verification result is still a failure, the data to be backed up at the storage location is deleted.

[0072] For example, if the data to be backed up at storage location B still fails the verification after data retransmission, it indicates that the data to be backed up at storage location B is incomplete. To ensure the reliability of data backup, the data to be backed up should not be enabled. Therefore, storage location B can be emptied so that the data stored at storage location B is empty (NULL). In this way, when performing cross-data center data transmission, the original data storage rule and the uniformly stored data to be backed up are transmitted. Since the storage address B in the original data storage rule is empty, when the destination backup server distributes data, it should determine whether the data stored at the storage address to be distributed is empty. If it is empty, the cluster node corresponding to the storage address will not perform data backup this time to avoid using illegal data for data backup.

[0073] In some embodiments of the present application, in the above step S230, the data storage rule and the data to be backed up stored uniformly are sent to the destination backup server through the data backup link between the source backup server and the destination backup server, which specifically includes:

[0074] Compress the data storage rule and the data to be backed up stored uniformly to obtain compressed data;

[0075] Send the compressed data to the destination backup server through the data backup link.

[0076] In this embodiment, an existing compression scheme can be used to compress the data to be transmitted, and the transmission efficiency can be improved by transmitting the compressed data.

[0077] In some embodiments of the present application, after step S230 is executed, the cross-data center data backup method of the embodiments of the present application further includes:

[0078] After it is determined that the destination server has received successfully, delete the data to be backed up stored uniformly on the source backup server, so that the storage space allocated for cross-data center data backup on the source backup server can be emptied, without affecting the next round of cross-data center data backup.

[0079] The embodiments of the present application provide another cross-data center data backup method. As Figure 3 shown, a flowchart of another cross-data center data backup method in the embodiments of the present application is provided. The method at least includes the following steps S310 to step S320:

[0080] Step S310, receive the data sent by the source backup server through the data backup link between the source backup server and the destination backup server.

[0081] The data includes the data storage rule and the data to be backed up sent by the source backup server according to the cross-data center data backup methods of the foregoing embodiments.

[0082] When the source backup server performs data transmission through the data backup link, it will specify the specific location of the data transmission, and the destination backup server will save the data storage rule and the data to be backed up to the specified location of the destination backup server.

[0083] To ensure data reliability, after receiving the above data sent by the source backup server, the destination backup server will perform data verification on the received data. If the data verification fails, it will start the data retransmission strategy to request the source backup server to send the data. If the complete data is still not received based on the data retransmission strategy, a backup alarm will be triggered. If the complete data is received based on the data retransmission strategy, the destination backup server will perform data distribution.

[0084] Step S320: Send the data to be backed up at each storage location to the cluster nodes of the corresponding application in the second computer room according to the data storage rule, so that the cluster nodes of the application in the second computer room perform data backup based on the data to be backed up.

[0085] As described above, the data storage rule stipulates the mapping relationship between the storage location and the cluster node. The destination backup server can determine the cluster node in the second computer room corresponding to the data to be backed up at each storage location to accurately distribute the data.

[0086] The destination backup server in the embodiment of the present application can send the data to be backed up at each storage location to the corresponding cluster node through a data push command. Of course, the destination backup server can also distribute the data in other ways. For example, a data distribution task is constructed, and the data distribution task can distribute the data to be backed up through a parallel distribution strategy or a serial distribution strategy. In practical applications, those skilled in the art can flexibly design the real-time scheme of data distribution.

[0087] In some embodiments of the present application, the above step S320 of sending the data to be backed up at each storage location to the cluster nodes of the corresponding application in the second computer room according to the data storage rule specifically includes:

[0088] Determine whether the data to be backed up at each storage location is empty;

[0089] If it is empty, determine that the data to be backed up at the storage location is illegal;

[0090] If it is not empty, determine the target cluster node corresponding to the storage location according to the data storage rule, and send the data to be backed up at the storage location to the target cluster node in the second computer room.

[0091] As described above, when performing data verification on the data to be backed up in the computer room, if the data to be backed up at a certain / some storage locations is deleted, the cluster nodes mapped by these storage locations should not perform data backup in this round. In view of this situation, when the destination backup server distributes the data, it should judge whether each storage location is empty. If it is empty, it means that the data stored at the storage location is illegal and should not be used for data backup, so as to ensure the reliability of data backup.

[0092] The following combines Figure 4 The overall process schematic diagram of cross-computer room data backup shown in the figure to detail the cross-computer room data backup process of the embodiment of the present application.

[0093] In Figure 4In the scenario shown, it is assumed that there are four applications in the computer room, namely Jira, Wiki, Crowd, and NFS (Network File System). Each application is deployed on three different cluster nodes. Among them, Jira is a project and transaction tracking tool, which is widely used in work areas such as defect tracking, customer service, requirement collection, process approval, task tracking, project tracking, and agile management; Wiki is a hypertext system that is open on the network and allows multiple people to collaborate on creation; Crowd is a web-based single sign-on tool that can simplify application software solutions and identity authentication management; NFS is the basis of a distributed file system, which provides scalable access to distributed files through the network. Among them, the NFS application has a large disk space. Therefore, in Figure 4 In the scenario described, the NFS server in the first computer room (abbreviated as NFS server Server1 hereinafter) is used as the source backup server, and the NFS server in the second computer room (abbreviated as NFS server Server2 hereinafter) is used as the destination backup server.

[0094] An embodiment of the present application can pre-define a unified storage protocol for data to be backed up in the same computer room. Through this unified storage protocol, a data storage rule (i.e., directory structure) is created. On the one hand, the directory structure stipulates the mapping relationship between the relative path address of the data to be backed up in the disk space of the NFS server and the cluster node where the data to be backed up is located. On the other hand, it also stipulates the constraint relationship between cluster nodes. Specifically, this constraint relationship is manifested as the belonging relationship between cluster nodes and applications. That is, in Figure 4 In the scenario shown, the directory structure is a two-level directory structure. The first-level directory includes four directory entries, and each directory entry corresponds to one of the above four applications. The second-level directory includes twelve directory entries, and three of the twelve directory entries belong to the same first-level directory entry.

[0095] After the directory structure is created on the NFS server Server1 in the first computer room, the NFS server Server1 sends the relative path address corresponding to each second-level directory to the corresponding cluster node. Each cluster node of each application directly writes its own application data as the data to be backed up into the disk space corresponding to the relative path address of the NFS server Server1, so as to uniformly store the data to be backed up of all cluster nodes of the above four applications in the first computer room on the NFS server Server1. In addition, the NFS server Server1 also performs data verification on the received data to be backed up to ensure the reliability of data transmission in the computer room. After the NFS server Server1 obtains the data to be backed up of each cluster node of the above four applications, it compresses the directory structure and the uniformly stored data to be backed up to obtain compressed data.

[0096] In addition, the NFS server Server1 establishes a data backup link with the NFS server Server2 based on the SSL (Secure Socket Layer) protocol to ensure the security of cross-data center data transmission. After establishing the data backup link, the compressed data is sent to the NFS server in the second data center through this data backup link.

[0097] The NFS server Server2 decompresses the received compressed data and performs data verification on the decompressed data according to the check code. When the verification is successful, a data reception success message is sent to the NFS server Server1, so that the NFS server Server1 clears the data to be backed up stored uniformly in its disk space according to this data reception success message.

[0098] The NFS server Server2 determines the current target relative path to be distributed according to the mapping relationship between the relative path address of the data to be backed up specified by the directory structure and the cluster node where the data to be backed up is located, and then determines the cluster node corresponding to the data to be backed up stored in the disk space of the NFS server Server2 for each current target relative path to be distributed according to the above mapping relationship specified in the directory structure, and pushes the data to be backed up to the cluster nodes of the corresponding applications in the second data center. After each cluster node of each application receives the data to be backed up, it executes the data backup and data recovery processes. The specific processes can be implemented by those skilled in the art in combination with the prior art, and are not elaborated in this embodiment of the present application.

[0099] As can be seen from the above embodiments, the cross-data center data backup process of the embodiments of the present application only needs to complete the data transmission between data centers through one data backup link. In this way, the operation and maintenance personnel only need to maintain one data backup link, which can not only reduce the operation and maintenance cost, but also reduce the probability of data backup failure caused by link failure, thereby improving the reliability of data backup. In addition, the embodiments of the present application also perform data verification on the data transmission process within the data center and the data transmission process between data centers, further improving the reliability of data backup.

[0100] The embodiments of the present application also provide a cross-data center data backup device, which is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in the first data center and a destination backup server located in the second data center. As Figure 5 shown, a schematic structural diagram of a cross-data center data backup device in the embodiments of the present application is provided. The cross-data center data backup device 500 is applied to the source backup server. The device 500 includes a rule acquisition unit 510, a unified storage unit 520, and a data sending unit 530;

[0101] A rule acquisition unit 510 is configured to acquire a data storage rule, where the data storage rule includes a mapping relationship between a storage location of data to be backed up and a cluster node where the data to be backed up is located.

[0102] A unified storage unit 520 is configured to uniformly store the data to be backed up on multiple cluster nodes of each application in the first computer room to corresponding storage locations of the source backup server according to the data storage rule.

[0103] A data sending unit 530 is configured to send the data storage rule and the uniformly stored data to be backed up to the destination backup server through a data backup link between the source backup server and the destination backup server, so that the destination backup server distributes the data to be backed up to cluster nodes of corresponding applications in the second computer room according to the data storage rule.

[0104] In some embodiments of the present application, the data storage rule further includes a constraint relationship between storage locations, and the apparatus 500 further includes a rule creation unit, configured to group the cluster nodes in the first computer room according to the applications to which they belong when creating a data storage rule, to obtain grouping information of the cluster nodes; and obtain grouping information of the storage locations according to the grouping information of the cluster nodes and the mapping relationship between the cluster nodes and the storage locations, so as to obtain the constraint relationship between the storage locations through the grouping information of the storage locations.

[0105] In some embodiments of the present application, the unified storage unit 520 is further configured to, after uniformly storing the data to be backed up on multiple cluster nodes of each application in the first computer room to corresponding storage locations of the source backup server according to the data storage rule, perform data verification on the data to be backed up stored in each storage location to obtain a verification result; update the data storage rule according to the verification result, or delete the data to be backed up stored in the storage location according to the verification result.

[0106] In some embodiments of the present application, the verification result includes verification success and verification failure. Specifically, the unified storage unit 520 is configured to not update the data storage rule when the verification result is verification success; when the verification result is verification failure, obtain the data to be backed up through a data retransmission strategy, perform data verification on the data to be backed up after data retransmission, and if the verification result is still verification failure, update the data storage rule by deleting the storage location.

[0107] Alternatively, the unified storage unit 520 is specifically configured to retain the data to be backed up at the storage location when the verification result is successful; when the verification result is failed, obtain the data to be backed up through a data retransmission policy, and perform data verification on the data to be backed up after data retransmission. If the verification result is still failed, delete the data to be backed up at the storage location.

[0108] It can be understood that the above cross-data center data backup can implement each step of the cross-data center data backup method performed by the source backup server in the foregoing embodiments. The relevant explanations regarding the cross-data center data backup method performed by the source backup server are applicable to the cross-data center data backup device, and will not be elaborated here.

[0109] An embodiment of the present application further provides a cross-data center data backup device, which is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in a first data center and a destination backup server located in a second data center, as Figure 6 shown, a schematic structural diagram of a cross-data center data backup device in an embodiment of the present application is provided. The cross-data center data backup device 600 is applied to the destination backup server. The device 600 includes a data receiving unit 610 and a data distributing unit 620;

[0110] The data receiving unit 610 is configured to receive the data sent by the source backup server through a data backup link between the source backup server and the destination backup server, where the data includes a data storage rule and data to be backed up sent by the source backup server based on the cross-data center data backup method;

[0111] The data distributing unit 620 is configured to send the data to be backed up at each storage location to the cluster nodes of the corresponding application in the second data center according to the data storage rule, so that the cluster nodes of the application in the second data center perform data backup according to the data to be backed up.

[0112] In some embodiments of the present application, the data distributing unit 620 is specifically configured to determine whether the data to be backed up at each storage location is empty; if it is empty, determine that the data to be backed up at the storage location is illegal; if it is not empty, determine the target cluster node corresponding to the storage location according to the data storage rule, and send the data to be backed up at the storage location to the target cluster node in the second data center.

[0113] It can be understood that the above cross-data center data backup can implement each step of the cross-data center data backup method performed by the destination backup server in the foregoing embodiments. The relevant explanations regarding the cross-data center data backup method performed by the destination backup server are applicable to the cross-data center data backup device, and will not be elaborated here.

[0114] The embodiment of the present application further provides a cross-data center data backup system, which includes a source backup server and a destination backup server located in different data centers, where:

[0115] The source backup server is used to establish a data backup link with the destination backup server and execute the cross-data center data backup method performed by the source backup server in the foregoing embodiment;

[0116] The destination backup server is used to execute the cross-data center data backup method performed by the destination backup server in the foregoing embodiment.

[0117] For the application clusters located in different data centers in the embodiment of the present application, when the first application cluster provides application services in the first data center, the first application cluster does not provide application services in other data centers and is in a standby state. In actual applications, it can be determined which data center's application cluster provides application services according to application requirements.

[0118] Figure 7 It is a schematic structural diagram of an electronic device shown in an embodiment of the present application. Please refer to Figure 7 , at the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. Among them, the memory may include a memory, such as a high-speed random access memory (Random-Access Memory, RAM), and may also include a non-volatile memory, such as at least one disk memory, etc. Of course, the electronic device may also include other hardware required for other services.

[0119] The processor, network interface, and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, Figure 7 only a bidirectional arrow is used in

[0120] The memory is used to store programs. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory may include a memory and a non-volatile memory, and provide instructions and data to the processor.

[0121] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a cross-computer-room data backup device at the logical level. The processor executes the program stored in the memory and executes the cross-computer-room data backup method, specifically performing the following steps:

[0122] Obtain a data storage rule, where the data storage rule includes the mapping relationship between the storage location of the data to be backed up and the cluster nodes where the data to be backed up is located;

[0123] According to the data storage rule, uniformly store the data to be backed up on multiple cluster nodes of each application in the first computer room to the corresponding storage location of the source backup server;

[0124] Through the data backup link between the source backup server and the destination backup server, send the data storage rule and the uniformly stored data to be backed up to the destination backup server, so that the destination backup server distributes the data to be backed up to the cluster nodes of the corresponding application in the second computer room according to the data storage rule;

[0125] Alternatively, through the data backup link between the source backup server and the destination backup server, receive the data sent by the source backup server, where the data includes the data storage rule and the data to be backed up sent by the source backup server;

[0126] According to the data storage rule, send the data to be backed up at each storage location to the cluster nodes of the corresponding application in the second computer room, so that the cluster nodes of the application in the second computer room perform data backup according to the data to be backed up.

[0127] The above as in this application Figure 2 or Figure 3The method executed by the cross-data center data backup device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with the ability to process signals. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor or the instructions in the form of software. The above-mentioned processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by a combination of the hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above cross-data center data backup method.

[0128] The electronic device can also execute Figure 2 or Figure 3 the method executed by the cross-data center data backup device in Figure 2 or Figure 3 the illustrated embodiment, and implement the functions of the cross-data center data backup device in

[0129] Embodiments of the present application also propose a computer-readable storage medium that stores one or more programs. The one or more programs include instructions that, when executed by an electronic device including a plurality of application programs, can enable the electronic device to execute Figure 2 or Figure 3 the method executed by the cross-data center data backup device in the illustrated embodiment.

[0130] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) that contain computer-usable program code.

[0131] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It should be understood that each flow and / or block in the flowchart and / or block diagram, and combinations of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices produce means for implementing the functions specified in one Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0132] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory produce a manufactured article including instruction means that implement the functions specified in one Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0133] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are performed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0134] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0135] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0136] A computer-readable medium includes both permanent and non-permanent, removable and non-removable media and can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer-readable medium does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0137] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or apparatus comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or apparatus. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising the element.

[0138] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0139] The above are only the embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. A cross-data center data backup method is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in a first data center and a destination backup server located in a second data center. The cross-data center data backup method is executed by the source backup server, wherein, The method includes: Obtaining a data storage rule, where the data storage rule includes a mapping relationship between the storage location of the data to be backed up and the cluster nodes where the data to be backed up is located; According to the data storage rule, uniformly storing the data to be backed up on multiple cluster nodes of each application in the first computer room to the corresponding storage location of the source backup server; Through the data backup link between the source backup server and the destination backup server, sending the data storage rule and the uniformly stored data to be backed up to the destination backup server, so that the destination backup server distributes the data to be backed up to the cluster nodes of the corresponding application in the second computer room according to the data storage rule.

2. The cross-data center data backup method according to claim 1, wherein, The data storage rule further includes a constraint relationship between storage locations. When creating the data storage rule, the method further includes: Grouping the cluster nodes in the first computer room according to the applications to which they belong based on the application cluster architecture information of the first computer room to obtain grouping information of the cluster nodes; According to the grouping information of the cluster nodes and the mapping relationship between the cluster nodes and the storage locations, obtaining the grouping information of the storage locations, so as to obtain the constraint relationship between the storage locations through the grouping information of the storage locations.

3. The cross-data center data backup method according to claim 1, wherein, After uniformly storing the data to be backed up on multiple cluster nodes of each application in the first computer room to the corresponding storage location of the source backup server according to the data storage rule, the method further includes: Performing data verification on the data to be backed up stored in each storage location to obtain a verification result; Updating the data storage rule according to the verification result, or deleting the data to be backed up stored in the storage location according to the verification result.

4. The cross-data center data backup method according to claim 3, wherein, The verification result includes verification success or verification failure. Updating the data storage rule according to the verification result includes: When the verification result is verification success, the data storage rule is not updated; When the verification result is verification failure, obtaining the data to be backed up through a data retransmission strategy, performing data verification on the data to be backed up after data retransmission, and if the verification result is still verification failure, updating the data storage rule by deleting the storage location; Deleting the data to be backed up stored in the storage location according to the verification result includes: When the verification result is verification success, retaining the data to be backed up at the storage location; When the verification result is verification failure, obtaining the data to be backed up through a data retransmission strategy, performing data verification on the data to be backed up after data retransmission, and if the verification result is still verification failure, deleting the data to be backed up at the storage location.

5. A cross-data center data backup method is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in a first data center and a destination backup server located in a second data center. The cross-data center data backup method is executed by the destination backup server, wherein, The method includes: Receiving, through the data backup link between the source backup server and the destination backup server, the data sent by the source backup server, where the data includes the data storage rule and the data to be backed up sent by the source backup server based on the cross-computer-room data backup method according to any one of claims 1 to 4; According to the data storage rule, sending the data to be backed up at each storage location to the cluster nodes of the corresponding application in the second computer room, so that the cluster nodes of the application in the second computer room perform data backup according to the data to be backed up.

6. The cross-data center data backup method according to claim 5, wherein, Sending the data to be backed up at each storage location to the cluster nodes of the corresponding application in the second computer room according to the data storage rule includes: Determining whether the data to be backed up at each storage location is empty; If it is empty, determining that the data to be backed up at the storage location is illegal; If it is not empty, determining the target cluster node corresponding to the storage location according to the data storage rule, and sending the data to be backed up at the storage location to the target cluster node in the second computer room.

7. A cross-data center data backup device is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in a first data center and a destination backup server located in a second data center. The cross-data center data backup device is applied to the source backup server, wherein, The device includes: A rule acquisition unit, configured to acquire a data storage rule, where the data storage rule includes a mapping relationship between the storage location of the data to be backed up and the cluster node where the data to be backed up is located; A unified storage unit, configured to uniformly store the data to be backed up on multiple cluster nodes of each application in the first computer room to the corresponding storage location of the source backup server according to the data storage rule; A data sending unit, configured to send the data storage rule and the uniformly stored data to be backed up to the destination backup server through a data backup link between the source backup server and the destination backup server, so that the destination backup server distributes the data to be backed up to the cluster nodes of the corresponding application in the second computer room according to the data storage rule.

8. A cross-data center data backup device is applied to a cross-data center data backup system. The cross-data center data backup system includes a source backup server located in a first data center and a destination backup server located in a second data center. The cross-data center data backup device is applied to the destination backup server, wherein, The device includes: A data receiving unit, configured to receive the data sent by the source backup server through a data backup link between the source backup server and the destination backup server, where the data includes the data storage rule and the data to be backed up sent by the source backup server based on the cross-computer-room data backup method according to any one of claims 1 to 4; A data distribution unit, configured to send the data to be backed up at each storage location to the cluster nodes of the corresponding application in the second computer room, so that the cluster nodes of the application in the second computer room perform data backup according to the data to be backed up.

9. A cross-computer-room data backup system, the cross-computer-room data backup system includes a source backup server and a destination backup server located in different computer rooms, where: The source backup server is configured to establish a data backup link with the destination backup server and execute the cross-computer-room data backup method according to any one of claims 1 to 4; The destination backup server is configured to execute the cross-computer-room data backup method according to claim 5 or 6.

10. An electronic device, wherein, The electronic device includes: A memory, storing computer-executable instructions; A processor, when the computer-executable instructions are executed, causing the processor to execute the cross-computer-room data backup method according to any one of claims 1 to 4 or the cross-computer-room data backup method according to claim 5 or 6.

Images