Data backup method and apparatus, computer device, and storage medium

Abstract

A data backup method and apparatus, a computer device, and a storage medium. The method comprises: when data backup needs to be performed on data to be backed up, a target backup proxy container in a target host machine is rebooted and mounts a backup storage directory, and then the target backup proxy container backs up said data from a database container to the backup storage directory. The database container does not need to be rebooted, thereby preventing the rebooting of a database container from affecting a database service, and solving the problem of the impact of the rebooting of a database container for data backup on a database service.

Description

Data backup methods, apparatus, computer equipment and storage media

[0001] This application claims priority to Chinese Patent Application No. 202411453149.5, filed on October 17, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of computer technology, such as a data backup method, apparatus, computer equipment, and storage medium. Background Technology

[0003] There are many database backup media, including Simple Storage Service (S3), Cloud Object Storage (COS) and other object storage backups, local file system backups, and Network File System (NFS). NFS has captured a large share of the backup market due to its advantages such as low cost, high availability, and easy scalability. However, in cloud environments, using NFS backups requires mounting directories to the database container, which causes the database container to restart, impacting database operations—something unacceptable to database users. Therefore, there is an urgent need for a data backup method that does not require restarting the database container. Summary of the Invention

[0004] This application provides a data backup method, apparatus, computer equipment, and storage medium to address the problem that restarting a database container during data backup affects database operations.

[0005] In a first aspect, this application provides a data backup method, the method comprising:

[0006] When the first host receives a data backup request corresponding to the data to be backed up, it determines the target host for performing the backup operation based on the available resource information of each host, wherein the first host can be any one of the hosts.

[0007] Based on the data backup request, the target backup agent container is scheduled to the target host machine. After the target backup agent container is restarted and the backup storage directory is mounted on the target host machine, the data to be backed up is backed up from the database container in the first host machine to the backup storage directory.

[0008] Secondly, this application provides a data backup device, the device comprising:

[0009] The algorithm module is configured to determine the target host machine for performing the backup operation based on the available resource information of each host machine when the first host machine receives a data backup request corresponding to the data to be backed up; wherein the first host machine is any one of the host machines.

[0010] The scheduling module is configured to schedule the target backup agent container to the target host machine according to the data backup request, and after the target backup agent container restarts and mounts the backup storage directory on the target host machine, it backs up the data to be backed up from the database container in the first host machine to the backup storage directory.

[0011] Thirdly, this application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-described data backup method.

[0012] Fourthly, this application also provides a computer storage medium storing computer-executable instructions for executing the above-described data backup method. Attached Figure Description

[0013] 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 this application.

[0014] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings, in which elements having the same reference numerals are designated as similar elements, and unless otherwise stated, the figures in the drawings are not intended to be limited in scale.

[0015] Figure 1 is an application environment diagram of a data backup method provided in an embodiment of this application;

[0016] Figure 2 is an application environment diagram of a data backup method provided in an embodiment of this application;

[0017] Figure 3 is a flowchart illustrating a data backup method provided in an embodiment of this application;

[0018] Figure 4 is a structural block diagram of a data backup device provided in an embodiment of this application;

[0019] Figure 5 is a schematic diagram of the internal structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0020] The following disclosure provides numerous different embodiments or examples for implementing various structures of this application. To simplify the disclosure, specific examples and arrangements are described below. Of course, these are merely examples. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0021] Figure 1 illustrates the application environment of a data backup method in one embodiment. Referring to Figure 1, the data backup method is applied to a data backup system. This data backup system includes a terminal 110, a host machine 120, and a cloud database 130. The terminal 110, host machine 120, and cloud database 130 are connected via a network. The terminal 110 can be a desktop terminal or a mobile terminal; a mobile terminal can be at least one of a mobile phone, tablet computer, or laptop computer. The host machine 120 and cloud database 130 can be implemented using independent servers or a server cluster consisting of multiple servers.

[0022] Referring to Figure 2, host machine 120 includes a host agent and a backup management system. For host machines containing data to be backed up, it also includes a database container storing the data. The host agent is responsible for calculating the latency between different host machines to form a host latency topology, and for counting the number and identities of database containers on each host machine (node) to form a database network topology. It also counts the resource information of each host machine to form a host resource topology. The backup management system includes a scheduling module and an algorithm module. The algorithm module is used to calculate the optimal host machine for scheduling the backup agent container based on preset rules, that is, to determine the target host machine for performing the backup operation. The scheduling module is used to schedule the backup agent container to the specified target host machine and destroy the backup agent container after the backup task is completed. Referring to Figure 2, the backup agent container in the target host machine is used to restart and mount the NFS backup storage directory in the cloud database. Then, the backup agent container can back up the data to be backed up stored in the database container to the NFS backup storage directory, thereby completing the data backup.

[0023] In one embodiment, Figure 3 is a flowchart illustrating a data backup method. Referring to Figure 3, a data backup method is provided. This embodiment mainly uses the application of this method to the host machine 120 in Figure 1 as an example. The data backup method includes, for example, the following steps:

[0024] Step S210: When the first host receives a data backup request corresponding to the data to be backed up, it determines the target host for performing the backup operation based on the available resource information of each host, wherein the first host can be any host.

[0025] For example, the backup management system in the first host machine receives a data backup request corresponding to the data to be backed up. The first host machine can be any host machine, and the data backup request can be a request initiated by the user to the first host machine through the terminal, or it can be a request generated by the first host machine periodically for unbacked-up data.

[0026] The first host machine determines the target host machine for performing the backup operation based on the available resource information of each host machine. The target host machine can be the first host machine or other hosts machine. The available resource information is used to indicate the service capabilities of the host machine. The host machine whose service capabilities meet the data backup requirements is determined as the target host machine.

[0027] Step S220: Based on the data backup request, the target backup agent container is scheduled to the target host machine. After the target backup agent container is restarted and the backup storage directory is mounted on the target host machine, the data to be backed up is backed up from the database container in the first host machine to the backup storage directory.

[0028] For example, the backup management system in the first host machine schedules the target backup agent container to the target host machine, which means allocating the target backup agent container to the target host machine. This involves creating a new backup agent container in the target host machine. The target backup agent container is a newly created backup agent container, which is different from the database container and is only used to perform data backup. By restarting the target backup agent container in the target host machine and mounting the backup storage directory, data backup can be achieved without restarting the database container in the first host machine. This avoids the database container restart affecting database services and solves the problem of data backup restarting database container affecting database services.

[0029] Compared with related technologies, the technical solution provided in this application has the following characteristics: When the first host receives a data backup request corresponding to the data to be backed up, the method provided in this application determines the target host for performing the backup operation based on the available resource information of each host, wherein the first host is any host; according to the data backup request, the target backup agent container is scheduled to the target host, and after the target backup agent container is restarted and the backup storage directory is mounted in the target host, the data to be backed up is backed up from the database container in the first host to the backup storage directory.

[0030] Based on the above method, when data backup is required, the target backup agent container in the target host machine is restarted and the backup storage directory is mounted. Then, the target backup agent container backs up the data to be backed up from the database container to the backup storage directory without restarting the database container. This avoids the database container restart affecting database services and solves the problem of data backup restart affecting database services.

[0031] In one embodiment, when the first host receives a data backup request corresponding to the data to be backed up, it determines the target host for performing the backup operation based on the available resource information of each host, including:

[0032] When the first host receives a data backup request corresponding to the data to be backed up, it obtains the available resource information of the first host, wherein the available resource information of each host includes the available resource information of the first host.

[0033] When the available resource information of the first host machine meets the scheduling requirements of the target backup agent container, the first host machine is determined as the target host machine for performing the backup operation.

[0034] For example, when the first host receives a data backup request, it first determines whether its available resources meet the scheduling requirements of the target backup agent container. If the available resources of the first host meet the scheduling requirements of the target backup agent container, the first host is selected as the target host and the first host performs the backup operation. This can save the interaction and scheduling process of the first host scheduling the target backup agent container to other hosts, thereby shortening the data backup time and improving the data backup efficiency.

[0035] In one embodiment, determining the first host machine as the target host machine for performing the backup operation when the available resource information of the first host machine meets the scheduling requirements of the target backup agent container includes:

[0036] When the available storage capacity of the first host machine is greater than the preset occupied capacity corresponding to the target backup agent container, and the number of existing backup agent containers in the first host machine is less than the preset number, the first host machine is determined as the target host machine for performing backup operations.

[0037] For example, available resource information includes available storage capacity and the number of existing backup agent containers. Available storage capacity is used to indicate the remaining available storage space on the host machine. The available storage capacity of the first host machine is compared with the preset occupied capacity corresponding to the target backup agent container to determine whether the available storage capacity of the first host machine supports the creation of the target backup agent container.

[0038] The number of existing backup agent containers in the first host machine is compared with the preset number to determine whether the number of existing backup agent containers in the first host machine has reached the preset number. The preset number is used to indicate the limit on the number of backup agent containers created in the host machine. The more backup agent containers created in the host machine, the greater the backup pressure on the host machine. Therefore, in order to alleviate the data backup pressure of a single host machine, a host machine with less data backup pressure is selected as the target host machine to reduce the data backup pressure of a single host machine and the network congestion caused by backup data, and to avoid the problem of a large number of idle network channels on other hosts machines. This can solve the problem of uneven data backup pressure on different hosts machines.

[0039] Therefore, when the available storage capacity of the first host machine is greater than the preset occupied capacity corresponding to the target backup agent container, and the number of existing backup agent containers in the first host machine is less than the preset number, it means that the first host machine itself meets the scheduling requirements of the target backup agent container. In this case, the first host machine can be preferentially determined as the target host machine for performing backup operations, which can solve the problem of high latency in database transmission caused by the backup agent container and the database container not being on the same host machine.

[0040] To minimize latency between the database container and the backup agent container, it is best to have them on the same host machine. The fewer backup agent containers on the same host machine, the better, as this will make full use of the disk read / write capabilities and network bandwidth of each host machine.

[0041] In one embodiment, after obtaining the available resource information of the first host machine when the first host machine receives a data backup request corresponding to the data to be backed up, the method further includes:

[0042] When the available resource information of the first host does not meet the scheduling requirements of the target backup agent container, the available resource information of multiple second host machines is obtained, wherein the second host machine is a host machine other than the first host machine;

[0043] The second host machine whose available resource information meets the scheduling requirements of the target backup agent container is determined as the target host machine for performing the backup operation.

[0044] For example, if the available storage capacity of the first host is less than or equal to the preset occupied capacity corresponding to the target backup agent container, and / or the number of existing backup agent containers in the first host is equal to the preset number, it means that the first host cannot support the creation of the target backup agent container. In this case, it is necessary to select another host as the target host. Therefore, the available resource information of multiple second hosts is obtained. The second host is any host other than the first host. Any second host whose available resource information meets the scheduling requirements of the target backup agent container can be selected as the target host.

[0045] In one embodiment, determining a second host machine whose available resource information matches the scheduling requirements of the target backup agent container as the target host machine for performing backup operations includes:

[0046] The second host machine whose available resource information meets the scheduling requirements of the target backup agent container is identified as a candidate host machine;

[0047] Among the multiple candidate host machines, the candidate host machine that is closest to the first host machine is determined as the target host machine for performing the backup operation.

[0048] For example, based on the previous embodiment, the target backup agent container is created on a second host machine that meets the scheduling requirements of the target backup agent container. At this time, the target backup agent container and the database container storing the data to be backed up are located on different hosts, which will result in high latency in transmitting the database.

[0049] Therefore, in order to reduce the data transmission latency caused by the backup agent container and the database container being located on different hosts, the second host that is closest to the first host and meets the scheduling requirements should be selected as the target host. That is, the second host whose available resource information meets the scheduling requirements of the target backup agent container is determined as the candidate host, and the candidate host that is closest to the first host is selected as the target host, so as to minimize the data transmission latency between the database container and the backup agent container.

[0050] In one embodiment, after scheduling the target backup agent container to the target host machine according to the data backup request, restarting the target backup agent container on the target host machine and mounting the backup storage directory, and backing up the data to be backed up from the database container in the first host machine to the backup storage directory, the method further includes:

[0051] Upon receiving a successful backup signal from the target backup agent container for the data to be backed up, the target backup agent container in the target host machine is destroyed.

[0052] For example, the backup management system in the first host machine will also destroy the target backup agent container in the target host machine when it receives a successful backup signal from the target host machine for the data to be backed up. That is, the backup agent container in the host machine will be destroyed after the backup operation is completed, so as to avoid the backup agent container without backup operation occupying the storage capacity of the target host machine for no reason, so as to release the storage space of the target host machine so that the data backup operation can continue to be performed later.

[0053] In one embodiment, the step of scheduling the target backup agent container to the target host machine according to the data backup request, causing the target backup agent container to restart and mount the backup storage directory on the target host machine, and then backing up the data to be backed up from the database container in the first host machine to the backup storage directory includes:

[0054] If the target host is the first host, the target backup agent container is scheduled to the first host according to the data backup request;

[0055] Restart the target backup agent container and mount the backup storage directory;

[0056] The target backup agent container is used to encrypt and pull the data to be backed up from the database container in the first host machine, and the data to be backed up is compressed and stored in the backup storage directory.

[0057] For example, when the first host is the target host, a target backup proxy container is created in the first host to schedule the target backup proxy container to the first host according to the data backup request. The target backup proxy container is restarted in the first host and the NFS backup storage directory in the cloud database is mounted. Then, the target backup proxy container encrypts and pulls the data to be backed up from the database container based on HyperText Transfer Protocol Secure (HTTPS), compresses it and stores it in the NFS backup storage directory, thereby completing the backup process of the data to be backed up. By restarting the target backup proxy container in the target host and mounting the backup storage directory, data backup can be achieved without restarting the database container in the first host, thereby avoiding the impact of database container restart on database services and solving the problem of data backup restart affecting database services.

[0058] Figure 3 is a flowchart illustrating a data backup method in one embodiment. It should be understood that although the steps in the flowchart of Figure 3 are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Furthermore, at least some of the steps in Figure 3 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0059] In one embodiment, as shown in FIG4, a data backup device is provided, comprising:

[0060] The algorithm module 310 is configured to determine the target host machine for performing the backup operation based on the available resource information of each host machine when the first host machine receives a data backup request corresponding to the data to be backed up; wherein the first host machine is any one of the host machines.

[0061] The scheduling module 320 is configured to schedule the target backup agent container to the target host machine according to the data backup request, and after the target backup agent container restarts and mounts the backup storage directory on the target host machine, it backs up the data to be backed up from the database container in the first host machine to the backup storage directory.

[0062] In one embodiment, the algorithm module 310 is configured as follows:

[0063] When the first host receives a data backup request corresponding to the data to be backed up, it obtains the available resource information of the first host, wherein the available resource information of each host includes the available resource information of the first host.

[0064] When the available resource information of the first host machine meets the scheduling requirements of the target backup agent container, the first host machine is determined as the target host machine for performing the backup operation.

[0065] In one embodiment, the algorithm module 310 is configured to determine the first host machine as the target host machine for performing the backup operation when the available resource information of the first host machine meets the scheduling requirements of the target backup agent container in the following manner:

[0066] When the available storage capacity of the first host machine is greater than the preset occupied capacity corresponding to the target backup agent container, and the number of existing backup agent containers in the first host machine is less than the preset number, the first host machine is determined as the target host machine for performing backup operations.

[0067] In one embodiment, the algorithm module 310 is further configured as follows:

[0068] When the available resource information of the first host does not meet the scheduling requirements of the target backup agent container, the available resource information of multiple second host machines is obtained, wherein the second host machine is a host machine other than the first host machine;

[0069] The second host machine whose available resource information meets the scheduling requirements of the target backup agent container is determined as the target host machine for performing the backup operation.

[0070] In one embodiment, the algorithm module 310 is configured to determine a second host machine whose available resource information meets the scheduling requirements of the target backup agent container as the target host machine for performing the backup operation by means of the following:

[0071] The second host machine whose available resource information meets the scheduling requirements of the target backup agent container is identified as a candidate host machine;

[0072] Among the multiple candidate host machines, the candidate host machine that is closest to the first host machine is determined as the target host machine for performing the backup operation.

[0073] In one embodiment, the scheduling module 320 is further configured to:

[0074] Upon receiving a successful backup signal from the target backup agent container for the data to be backed up, the target backup agent container in the target host machine is destroyed.

[0075] In one embodiment, the scheduling module 320 is configured as follows:

[0076] If the target host is the first host, the target backup agent container is scheduled to the first host according to the data backup request;

[0077] Restart the target backup agent container and mount the backup storage directory;

[0078] The target backup agent container is used to encrypt and pull the data to be backed up from the database container in the first host machine, and the data to be backed up is compressed and stored in the backup storage directory.

[0079] As shown in Figure 5, this application embodiment provides a computer device, including a processor 711, a communication interface 712, a memory 713, and a communication bus 714, wherein the processor 711, the communication interface 712, and the memory 713 communicate with each other through the communication bus 714; the memory 713 is used to store computer programs.

[0080] The processor 711, when executing the program stored in the memory 713, implements the data backup method provided in any of the foregoing method embodiments.

[0081] Those skilled in the art will understand that the structure shown in Figure 5 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. The actual computer device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0082] In one embodiment, the data backup device provided in this application can be implemented as a computer program, which can run on the computer device shown in FIG5. The memory of the computer device can store various program modules that make up the data backup device, such as the algorithm module 310 and scheduling module 320 shown in FIG4. The computer program composed of the various program modules causes the processor to execute the data backup methods of the various embodiments of this application described in this specification.

[0083] The computer device shown in Figure 5 can, through the algorithm module 310 in the data backup device shown in Figure 4, determine the target host for performing the backup operation based on the available resource information of each host when the first host receives a data backup request corresponding to the data to be backed up. The first host can be any host. The computer device can then, through the scheduling module 320, schedule the target backup agent container to the target host according to the data backup request. After the target backup agent container restarts and mounts the backup storage directory on the target host, it backs up the data to be backed up from the database container in the first host to the backup storage directory.

[0084] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the data backup method provided in any of the foregoing method embodiments.

[0085] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0086] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general-purpose hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as read-only memory (ROM) / random access memory (RAM), magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0087] The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “described” as used herein may also include the plural forms. The terms “comprising,” “including,” “containing,” and “having” are inclusive and therefore indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described herein are not construed as requiring them to be performed in a particular order described or illustrated unless the order of performance is explicitly indicated. It should also be understood that alternatives or substitutions may be used.

Claims

1. A data backup method, comprising: When the first host receives a data backup request corresponding to the data to be backed up, it determines the target host for performing the backup operation based on the available resource information of each host, wherein the first host can be any one of the hosts. Based on the data backup request, the target backup agent container is scheduled to the target host machine. After the target backup agent container is restarted and the backup storage directory is mounted on the target host machine, the data to be backed up is backed up from the database container in the first host machine to the backup storage directory.

2. The method of claim 1, wherein, When the first host receives a data backup request corresponding to the data to be backed up, determining the target host for performing the backup operation based on the available resource information of each host includes: When the first host receives a data backup request corresponding to the data to be backed up, it obtains the available resource information of the first host, wherein the available resource information of each host includes the available resource information of the first host. When the available resource information of the first host machine meets the scheduling requirements of the target backup agent container, the first host machine is determined as the target host machine for performing the backup operation.

3. The method of claim 2, wherein, The step of determining the first host machine as the target host machine for performing backup operations when the available resource information of the first host machine meets the scheduling requirements of the target backup agent container includes: When the available storage capacity of the first host machine is greater than the preset occupied capacity corresponding to the target backup agent container, and the number of existing backup agent containers in the first host machine is less than the preset number, the first host machine is determined as the target host machine for performing backup operations.

4. The method according to claim 2, after obtaining the available resource information of the first host machine when the first host machine receives a data backup request corresponding to the data to be backed up, the method further includes: When the available resource information of the first host does not meet the scheduling requirements of the target backup agent container, the available resource information of multiple second host machines is obtained, wherein the second host machine is a host machine other than the first host machine; The second host machine whose available resource information meets the scheduling requirements of the target backup agent container is determined as the target host machine for performing the backup operation.

5. The method of claim 4, wherein, The step of determining the second host machine whose available resource information meets the scheduling requirements of the target backup agent container as the target host machine for performing the backup operation includes: The second host machine whose available resource information meets the scheduling requirements of the target backup agent container is identified as a candidate host machine; Among the multiple candidate host machines, the candidate host machine that is closest to the first host machine is determined as the target host machine for performing the backup operation.

6. The method according to claim 1, wherein after scheduling the target backup agent container to the target host machine according to the data backup request, causing the target backup agent container to restart and mount the backup storage directory on the target host machine, and backing up the data to be backed up from the database container in the first host machine to the backup storage directory, the method further includes: Upon receiving a successful backup signal from the target backup agent container for the data to be backed up, the target backup agent container in the target host machine is destroyed.

7. The method of claim 1, wherein, The step of scheduling the target backup agent container to the target host machine according to the data backup request, restarting the target backup agent container on the target host machine and mounting the backup storage directory, and then backing up the data to be backed up from the database container in the first host machine to the backup storage directory includes: If the target host is the first host, the target backup agent container is scheduled to the first host according to the data backup request; Restart the target backup agent container and mount the backup storage directory; The target backup agent container is used to encrypt and pull the data to be backed up from the database container in the first host machine, and the data to be backed up is compressed and stored in the backup storage directory.

8. A data backup device, comprising: The algorithm module is configured to determine the target host machine for performing the backup operation based on the available resource information of each host machine when the first host machine receives a data backup request corresponding to the data to be backed up; wherein the first host machine is any one of the host machines. The scheduling module is configured to schedule the target backup agent container to the target host machine according to the data backup request, and after the target backup agent container restarts and mounts the backup storage directory on the target host machine, it backs up the data to be backed up from the database container in the first host machine to the backup storage directory.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the data backup method of any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the data backup method of any one of claims 1 to 7.

Images