Bandwidth management method and device, computer equipment and storage medium

Abstract

The invention relates to a bandwidth management method and device, computer equipment and a storage medium. The method comprises the following steps: in response to a data backup request sent by a request end, determining a target backup link corresponding to the data backup request, and sending a query request to a backup end; wherein the query request is used for querying the bandwidth service of the backup end to the cloud special line in the backup link, and the target backup link is used for transmitting data generated by the production node of the request end to the backup node of the backup end through the cloud special line for backup; obtaining target configuration information of the target backup link and a query response sent by the backup end according to the query request; managing the target bandwidth service of the target backup link according to the target configuration information and the query response; wherein the target bandwidth service is used for managing and controlling the bandwidth of the target backup link for transmitting data through the cloud private line. By adopting the method, the speed-limiting bandwidth service can be provided for the backup service, and the effective management of the speed-limiting bandwidth service can be realized.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a bandwidth management method, device, computer equipment and storage medium. Background Art

[0002] With the development of database technology, database disaster recovery technology has emerged.

[0003] In related technologies, database disaster recovery technology usually provides users with cloud disaster recovery backup services (referred to as backup services) through a disaster recovery platform. Users can use backup services to synchronize the data of production databases, middleware and other services of production nodes to the resource pool of backup nodes for backup.

[0004] In the prior art, when a production node uses a backup service to perform database disaster recovery backup, the backup service will occupy resources of other services, resulting in a decrease in the processing efficiency of other services. Summary of the invention

[0005] Based on this, it is necessary to provide a bandwidth management method, device, computer equipment and storage medium to address the above technical problems, which can provide speed-limited bandwidth services for backup services and achieve effective management of speed-limited bandwidth services.

[0006] In a first aspect, the present application provides a bandwidth management method, the method comprising:

[0007] In response to a data backup request sent by a requesting end, a target backup link corresponding to the data backup request is determined, and a query request is sent to the backup end; wherein the query request is used to query the bandwidth service of the backup end for the cloud dedicated line in the backup link, and the target backup link is used to transmit the data generated by the production node of the requesting end to the backup node of the backup end via the cloud dedicated line for backup;

[0008] Acquire target configuration information of the target backup link and a query response sent by the backup end according to the query request;

[0009] The target bandwidth service of the target backup link is managed according to the target configuration information and the query response; wherein the target bandwidth service is used to control the bandwidth of the target backup link transmitting data through the cloud dedicated line.

[0010] In one embodiment, managing the target bandwidth service of the target backup link according to the target configuration information and the query response includes:

[0011] In the case that the number of historical bandwidth services included in the query response is 0, sending a creation instruction to the backup end to instruct the backup end to create the target bandwidth service, and obtaining the target bandwidth identification information of the target bandwidth service sent by the backup end; wherein the creation instruction includes the target configuration information;

[0012] In a case where the query response includes at least one historical bandwidth service, acquiring target bandwidth identification information of the target backup link according to the target configuration information and historical attribute information of each of the historical bandwidth services;

[0013] The target bandwidth service is managed according to the target bandwidth identification information.

[0014] In one embodiment, the target configuration information includes target tuple information, and the historical attribute information includes historical tuple information, wherein acquiring the target bandwidth identification information of the target backup link according to the target configuration information and the historical attribute information of each of the historical bandwidth services includes:

[0015] In the case where the target tuple information and each of the historical tuple information are different, sending a creation instruction to the backup end to instruct the backup end to create the target bandwidth service; wherein the creation instruction includes the target configuration information;

[0016] Acquire the target bandwidth identification information sent by the backup end.

[0017] In one embodiment, the target configuration information includes target tuple information and target bandwidth speed limit information, the historical attribute information includes historical configuration information and historical bandwidth identification information, the historical configuration information includes historical tuple information and historical bandwidth speed limit information, wherein, according to the target configuration information and the historical attribute information of each of the historical bandwidth services, acquiring the target bandwidth identification information of the target backup link includes:

[0018] Determine a candidate bandwidth service from each of the historical bandwidth services according to the target tuple information and each of the historical tuple information; wherein the historical tuple information of the candidate bandwidth service is the same as the target tuple information;

[0019] The historical bandwidth identification information of the candidate bandwidth service is determined as the target bandwidth identification information.

[0020] In one of the embodiments, managing the target bandwidth service according to the target bandwidth identification information includes:

[0021] When detecting that the configuration information of the target backup link changes, acquiring corresponding target configuration information from the backup end according to the target bandwidth identification information, and acquiring current configuration information of the target backup link;

[0022] In the case that the current configuration information and the target configuration information are different, an adjustment instruction is sent to the backup end to instruct the backup end to adjust the target bandwidth service; the adjustment instruction includes the current configuration information and the target bandwidth identification information.

[0023] In one embodiment, the target configuration information includes target tuple information and target bandwidth speed limit information, and the current configuration information includes current tuple information and current bandwidth speed limit information, wherein when the current configuration information and the target configuration information are different, sending an adjustment instruction to the backup end includes:

[0024] In the case where the target tuple information and the current tuple information are different, sending a first adjustment instruction to the backup end to instruct the backup end to delete the target bandwidth service according to the target bandwidth identification information, create a current bandwidth service of the target backup link according to the current configuration information, and send the current bandwidth identification information of the current bandwidth service; wherein the first adjustment instruction includes the current configuration information and the target bandwidth identification information;

[0025] When the target tuple information is the same as the current tuple information, and the target bandwidth speed limit information is different from the current bandwidth speed limit information, a second adjustment instruction is sent to the backup end to instruct the backup end to update the target bandwidth speed limit information of the target bandwidth service to the current bandwidth speed limit information; wherein the second adjustment instruction includes the current bandwidth speed limit information and the target bandwidth identification information.

[0026] In one embodiment, in response to the data backup request sent by the requesting end, determining the target backup link corresponding to the data backup request, and sending a query request to the backup end, comprises:

[0027] According to the backup subnet information in the data backup request, controlling the backup node to open a backup database;

[0028] According to the data source subnet information in the data backup request, control the production node to deploy a data synchronization tool in the same subnet as the production database;

[0029] The target backup link is determined according to the production database, the data synchronization tool and the backup database, wherein the target backup link represents a link from the production database via the data synchronization tool to the local gateway, and through the cloud dedicated line in sequence via the dedicated line gateway and the cloud gateway to the backup database.

[0030] In a second aspect, the present application provides a bandwidth management device, the device comprising:

[0031] A query module, configured to respond to a data backup request sent by a requesting end, determine a target backup link corresponding to the data backup request, and send a query request to a backup end; wherein the query request is used to query the bandwidth service of the backup end for the cloud dedicated line in the backup link, and the target backup link is used to transmit the data generated by the production node of the requesting end to the backup node of the backup end via the cloud dedicated line for backup;

[0032] An acquisition module, used to acquire target configuration information of the target backup link and a query response sent by the backup end according to the query request;

[0033] A management module is used to manage the target bandwidth service of the target backup link according to the target configuration information and the query response; wherein the target bandwidth service is used to control the bandwidth of the target backup link transmitting data through the cloud dedicated line.

[0034] In a third aspect, the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0035] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0036] The above-mentioned bandwidth management method, device, computer equipment and storage medium, in response to the data backup request sent by the requesting end, determine the target backup link corresponding to the data backup request, and send a query request to the backup end, obtain the target configuration information of the target backup link and the query response sent by the backup end according to the query request, and manage the target bandwidth service of the target backup link according to the target configuration information and the query response, so that the bandwidth of the target backup link can be limited based on the target bandwidth service, realizing the bandwidth limitation of the data backup link, avoiding the impact on other network services that share the cloud dedicated line with the data backup service, and ensuring the stability and reliability of network transmission. The embodiment of the present application limits the bandwidth of the cloud dedicated line in the data backup link. Compared with the use of data synchronization tools to control the data transmission speed, the embodiment of the present application realizes the transmission speed limitation from the network layer rather than the application layer, and can more accurately control the bandwidth used for data synchronization, expanding the scope of data bandwidth control. In addition, the bandwidth management method provided by the embodiment of the present application can automatically adjust and manage the corresponding target bandwidth service based on the data backup request sent by the requesting end, realizes the adaptive management of different data backup links corresponding to the data backup requests sent by different requesting ends, and improves the effective control of bandwidth services. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 A diagram of an application environment of a bandwidth management method in an embodiment;

[0038] Figure 2 A diagram showing an application environment of a bandwidth management method in another embodiment;

[0039] Figure 3 One of the flowcharts of a bandwidth management method in an embodiment;

[0040] Figure 4 FIG2 is a second flow chart of a bandwidth management method in an embodiment;

[0041] Figure 5 FIG3 is a flow chart of a bandwidth management method according to an embodiment of the present invention;

[0042] Figure 6 FIG4 is a fourth flow chart of a bandwidth management method in an embodiment;

[0043] Figure 7 FIG5 is a fifth flow chart of a bandwidth management method in an embodiment;

[0044] Figure 8 FIG6 is a sixth flow chart of a bandwidth management method in an embodiment;

[0045] Fig. 9 FIG7 is a flow chart of a bandwidth management method according to an embodiment;

[0046] Fig.10 FIG8 is a flow chart of a bandwidth management method according to an embodiment of the present invention;

[0047] Fig.11 is a structural block diagram of a bandwidth management device in one embodiment;

[0048] Fig.12 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0050] The bandwidth management method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Figure 1 and Figure 2 As shown, the application environment includes a disaster recovery platform 10, a request end 20 and a backup end 30. Among them, the disaster recovery platform 10 is connected to the request end 20 and the backup end 30 through the network respectively. The disaster recovery platform 10 is used to respond to the data backup request sent by the request end 20, determine the target backup link corresponding to the data backup request, and send a query request to the backup end 30, and obtain the target configuration information of the target backup link and the query response sent by the backup end 30 according to the query request, and manage the target bandwidth service of the target backup link according to the target configuration information and the query response. Among them, the production node 21 can be understood as a node that generates source data to be backed up. For example, the data generated by the production database 211, middleware, etc. in the production node 21 needs to be backed up. For example, the production node 21 can be a local computer room, a private cloud or other resource pool with data backup requirements. The request end 20 can be understood as a terminal or server corresponding to the production node 21, and the request end 20 is used to manage and control the production node 21. The backup node 31 is used to back up the source data. For example, the backup node 31 can be a cloud computer room, a private cloud, or other resource pool that can back up data. The backup end 30 can be understood as a terminal, server, or platform corresponding to the backup node 31. The backup end 30 is used to manage and control the backup node 31.

[0051] It can be understood that the target backup link is used to transmit the data generated by the production node 21 of the request end 20 to the backup node 31 of the backup end 30 via the cloud dedicated line for backup. Figure 2As shown, taking the scenario where the data generated by the production database 211 of the production node 21 needs to be backed up to the backup database 313 of the backup node 31 as an example, the target backup link refers to the data from the production database 211 of the production node 21 via the data synchronization tool 212 to the local gateway 213, and then through the cloud dedicated line to the dedicated gateway 311 of the backup node 31, and then through the cloud gateway 312 to the backup database 313.

[0052] Cloud dedicated line is a connection service between the user's local data center and VPC (Virtual Private Cloud). Cloud dedicated line products rely on the existing IT (Information Technology) infrastructure to flexibly build high-speed, low-latency, stable and secure exclusive connection channels on and off the cloud. One end of the dedicated line is connected to the local gateway 213 device, and the other end is connected to the dedicated line gateway 311, connecting the internal LAN of the user's local data center to the access point of the backup cloud to achieve intranet-level communication quality. In the embodiment of the present application, the cloud dedicated line can be understood as a dedicated line gateway 311 used to connect the local gateway 213 of the production node 21 and the backup node 31.

[0053] In one embodiment, Figures 1 to 3 As shown, a bandwidth management method is provided, which is applied to Figure 1 The disaster recovery platform in is taken as an example to illustrate, including the following steps S302 to S306.

[0054] S302: In response to the data backup request sent by the requesting end, determine the target backup link corresponding to the data backup request, and send a query request to the backup end.

[0055] The data backup request is used to indicate a request to back up the data generated by the production node of the requesting end. Exemplarily, the data backup request includes data source subnet information, backup subnet information, and target bandwidth speed limit information. Among them, the data source subnet information is used to indicate the subnet segment information to which the production node belongs, and can be expressed in CIDR (Classless Inter-Domain Routing) format. The backup subnet information is used to indicate the subnet segment information to which the backup node belongs, and can also be expressed in CIDR format. The target bandwidth speed limit information is used to indicate information related to bandwidth speed limit for the target backup link. Exemplarily, the target bandwidth speed limit information includes a bandwidth speed limit value and a bandwidth package ID (Identity). Among them, the bandwidth speed limit value can be the maximum transmission speed of the target backup link set by the user, in MB / s; the bandwidth package ID is used to identify the bandwidth package, which is the bandwidth package for which the cloud dedicated line bandwidth speed limit product purchased by the user acts.

[0056] In the application, after receiving the data backup request, the disaster recovery platform can determine whether the bandwidth limit value in the data backup request is greater than the maximum cloud dedicated line bandwidth corresponding to the bandwidth package ID based on the bandwidth package ID; if so, adjust the bandwidth limit value set by the user, and the adjusted bandwidth limit value is less than or equal to the maximum cloud dedicated line bandwidth corresponding to the bandwidth package ID.

[0057] The query request is used to query the bandwidth service of the cloud dedicated line in the backup link on the backup side. The query request is intended to query the bandwidth service that has been created on the backup side. Bandwidth service refers to the service that manages and controls the bandwidth of the cloud dedicated line of the backup link for data transmission between the production node and the backup node. The target backup link is used to transfer the data generated by the production node of the requesting side to the backup node of the backup side via the cloud dedicated line for backup. The bandwidth service that has been created on the backup side may include the target bandwidth service of the target backup link, or may not include the target bandwidth service of the target backup link.

[0058] In the application, after the disaster recovery platform receives the data backup request sent by the requesting end for the first time, the disaster recovery platform can instruct the backup end to open the backup database on the backup node, and instruct the requesting end to deploy the data synchronization tool on the production node, so as to determine the target backup link corresponding to the data backup request, that is, from the production database of the production node to the cloud dedicated line through the data synchronization tool and the local gateway, and then to the backup database through the dedicated line gateway and cloud gateway of the backup node. In addition, after receiving the data backup request, the disaster recovery platform can call the API (Application Program Interface) to send a query request to the backup end to query whether there is a bandwidth service corresponding to the created cloud dedicated line.

[0059] S304: Obtain target configuration information of the target backup link and a query response sent by the backup end according to the query request.

[0060] The target configuration information is used to represent information related to the target backup link configuration. Exemplarily, the target configuration information includes target tuple information and target bandwidth speed limit information. Among them, the target tuple information is used to identify the basic elements of the target backup link in network communication. Exemplarily, the target tuple information includes the source IP (Internet Protocol) address information, source port information, destination IP address information, destination port information and transmission protocol information of the target backup link. Among them, the source IP address, source port, destination IP address, destination port and transmission protocol are collectively referred to as a quintuple. The target bandwidth speed limit information is used to represent information on speed limiting the cloud dedicated line bandwidth in the target backup link. Exemplarily, the target bandwidth speed limit information includes a bandwidth speed limit value and a bandwidth package ID.

[0061] The query response is generated and sent by the backup end according to the query request. The query response is used to indicate the query result of whether there is a bandwidth service corresponding to the created cloud dedicated line on the backup end. Exemplarily, in the case that there is a bandwidth service corresponding to the created cloud dedicated line on the backup end, the query response includes the historical attribute information of the bandwidth service corresponding to the created cloud dedicated line, or simply referred to as the historical bandwidth service object, wherein the historical attribute information is used to indicate the information related to the historical bandwidth service. In another exemplary case, in the case that there is no bandwidth service corresponding to the created cloud dedicated line on the backup end, the query response does not include the historical bandwidth service object.

[0062] S306: managing the target bandwidth service of the target backup link according to the target configuration information and the query response.

[0063] The target bandwidth service is used to manage the speed limit of the cloud dedicated line bandwidth of the target backup link. Exemplarily, the target bandwidth service is used to manage the speed limit of the cloud dedicated line bandwidth of the target backup link according to the bandwidth speed limit value, wherein the bandwidth speed limit value can be found in the previous introduction and will not be repeated here. In the embodiment of the present application, the bandwidth service can be understood as a service that limits the speed of the cloud dedicated line bandwidth of the backup link in the backup service.

[0064] In the application, the disaster recovery platform can manage the target bandwidth service according to the target configuration information and query response. The management of the target bandwidth service can be understood as instructing the backup end to create the target bandwidth service, update the target bandwidth service, and delete the target bandwidth service, etc. For details, please refer to the following introduction.

[0065] The backup end can provide the target bandwidth service for the request end, so as to back up the source data generated by the production node, such as the production database, to the backup database of the backup node under the bandwidth limit condition of the target bandwidth service, thereby realizing data disaster recovery backup.

[0066] The above-mentioned bandwidth management method, in response to the data backup request sent by the requesting end, determines the target backup link corresponding to the data backup request, and sends a query request to the backup end, obtains the target configuration information of the target backup link and the query response sent by the backup end according to the query request, and manages the target bandwidth service of the target backup link according to the target configuration information and the query response, so that the bandwidth of the target backup link can be limited based on the target bandwidth service, realizing the bandwidth limitation of the data backup link, avoiding the impact of other network services that share the cloud dedicated line with the data backup service, and ensuring the stability and reliability of network transmission. The embodiment of the present application limits the bandwidth of the cloud dedicated line in the data backup link. Compared with using the data synchronization tool to control the data transmission speed (for example, setting the number of parallel synchronization processes, the number of single batch transmissions, etc.), the embodiment of the present application realizes the transmission speed limitation from the network layer rather than the application layer, and can more accurately control the bandwidth used for data synchronization, expanding the scope of data bandwidth control. In addition, the bandwidth management method provided in the embodiment of the present application can automatically adjust and manage the corresponding target bandwidth service based on the data backup request sent by the requesting end, realizes the adaptive management of different data backup links corresponding to the data backup requests sent by different requesting ends, and improves the effective control of bandwidth services.

[0067] In one embodiment, Figure 4 As shown, step S306, managing the target bandwidth service of the target backup link according to the target configuration information and the query response, includes the following steps S402 to S406.

[0068] S402: When the number of historical bandwidth services included in the query response is 0, send a creation instruction to the backup end to instruct the backup end to create a target bandwidth service, and obtain target bandwidth identification information of the target bandwidth service sent by the backup end; wherein the creation instruction includes target configuration information.

[0069] If the number of historical bandwidth services included in the query response is 0, it means that the backup end does not have the bandwidth service corresponding to the created cloud dedicated line. In this case, the disaster recovery platform sends a creation instruction to the backup end, thereby instructing the backup end to create the target bandwidth service corresponding to the target backup link according to the creation instruction.

[0070] The creation instruction includes target configuration information. Exemplarily, the target configuration information includes target tuple information and target bandwidth speed limit information, wherein the target tuple information includes source IP address information, source port information, destination IP address information, destination port information and transmission protocol information of the target backup link, and the target bandwidth speed limit information includes bandwidth speed limit value and bandwidth package ID. The target configuration information can be shown in Table 1 below.

[0071] Table 1

[0072]

[0073] String represents a string type, and Integer represents an integer type. For example, the transmission protocol information may include TCP (Transmission Control Protocol).

[0074] In the application, after receiving the creation instruction, the backup end creates the target backup link and the target bandwidth service of the target backup link according to the target configuration information in the creation instruction, and sends the target bandwidth identification information of the target bandwidth service to the disaster recovery platform, so that the disaster recovery platform can manage the target bandwidth service according to the target bandwidth identification information. Among them, the target bandwidth identification information is used to identify the target bandwidth service.

[0075] S404: When the query response includes at least one historical bandwidth service, obtain target bandwidth identification information of the target backup link according to the target configuration information and historical attribute information of each historical bandwidth service.

[0076] If the query response includes at least one historical bandwidth service, it means that there is a bandwidth service corresponding to the created cloud dedicated line on the backup side, that is, the historical bandwidth service. In this case, the disaster recovery platform can obtain the target bandwidth identification information of the target backup link based on the target configuration information and the historical attribute information of each historical bandwidth service, so as to manage the target bandwidth service according to the target bandwidth identification information.

[0077] The historical attribute information is used to indicate the information related to the historical bandwidth service. Exemplarily, the historical attribute information includes historical configuration information and historical bandwidth identification information, wherein the historical configuration information is used to indicate the information related to the historical bandwidth service configuration, which is similar to the target configuration information of the target bandwidth service. Please refer to the introduction of the target configuration information in the previous text, which will not be repeated here. The historical bandwidth identification information is used to identify the historical bandwidth service.

[0078] S406: Manage the target bandwidth service according to the target bandwidth identification information.

[0079] In the application, the disaster recovery platform can manage the target bandwidth service provided by the backup end to the request end according to the target bandwidth identification information.

[0080] The above-mentioned bandwidth management method, when the number of historical bandwidth services included in the query response is 0, sends a creation instruction to the backup end to instruct the backup end to create a target bandwidth service, and obtains the target bandwidth identification information of the target bandwidth service sent by the backup end; when the query response includes at least one historical bandwidth service, obtains the target bandwidth identification information of the target backup link according to the target configuration information and the historical attribute information of each historical bandwidth service, and manages the target bandwidth service according to the target bandwidth identification information. The method can realize the reuse of historical bandwidth services by querying whether there are created historical bandwidth services on the backup end, avoid over-configuration of bandwidth services, and reduce resource consumption; and when there are no historical bandwidth services or no bandwidth services that meet the backup requirements, the target bandwidth service is created or updated to ensure the effective implementation of the backup service and the corresponding bandwidth service; in addition, the method manages the bandwidth service through the bandwidth identification information, which is helpful to adjust and update the bandwidth service in real time according to the backup service requirements, and improves the reliability of the bandwidth service.

[0081] In one embodiment, Figure 5 As shown, the target configuration information includes target tuple information, and the historical attribute information includes historical tuple information. Step S404, obtaining the target bandwidth identification information of the target backup link according to the target configuration information and the historical attribute information of each historical bandwidth service, includes the following steps S502 and S504.

[0082] S502: When the target tuple information and each historical tuple information are different, a creation instruction is sent to the backup end to instruct the backup end to create a target bandwidth service; wherein the creation instruction includes target configuration information.

[0083] S504: Acquire target bandwidth identification information sent by the backup end.

[0084] Exemplarily, when the query response includes at least one historical bandwidth service, the disaster recovery platform compares the target tuple information of the target backup link with the historical tuple information of each historical bandwidth service and obtains a comparison result. The comparison result is used to indicate whether the target tuple information is the same as each historical tuple information. Taking the tuple information including five-tuple information, namely, source IP address information, source port information, destination IP address information, destination port information and transmission protocol information as an example, the disaster recovery platform compares the target five-tuple information with the historical five-tuple information one by one, and when there is at least one difference between the target five-tuple information and the historical five-tuple information, it is determined that the target five-tuple information is different from the historical five-tuple information.

[0085] If the comparison result is that the target tuple information is different from the historical tuple information, it means that the backup end does not have a historical bandwidth service for the target backup link. In this case, the disaster recovery platform sends a creation instruction to the backup end, thereby instructing the backup end to create the target backup link and the target bandwidth service of the target backup link according to the target configuration information in the creation instruction, and sends the target bandwidth identification information corresponding to the target bandwidth service to the disaster recovery platform, so that the disaster recovery platform can manage the target bandwidth service according to the target bandwidth identification information.

[0086] The above-mentioned bandwidth management method, when the target tuple information and each historical tuple information are different, sends a creation instruction to the backup end to instruct the backup end to create a target bandwidth service, and obtains the target bandwidth identification information sent by the backup end. In the case that there is no historical bandwidth service that meets the data backup request, the method creates a new target bandwidth service, thereby providing a backup service while being able to limit the bandwidth of the cloud dedicated line in the target backup link through the target bandwidth service, thereby reducing the impact of the backup service on the network transmission quality of other network services and improving the reliability of the overall system service.

[0087] In one embodiment, Figure 6 As shown, the target configuration information includes target tuple information and target bandwidth speed limit information, the historical attribute information includes historical configuration information and historical bandwidth identification information, and the historical configuration information includes historical tuple information and historical bandwidth speed limit information. Step S404, according to the target configuration information and the historical attribute information of each historical bandwidth service, obtains the target bandwidth identification information of the target backup link, including the following steps S602 and S604.

[0088] S602: Determine a candidate bandwidth service from each historical bandwidth service according to the target tuple information and each historical tuple information; wherein the historical tuple information of the candidate bandwidth service is the same as the target tuple information.

[0089] S604: Determine the historical bandwidth identification information of the candidate bandwidth service as the target bandwidth identification information.

[0090] If the comparison result is that the target tuple information is the same as the historical tuple information of at least one historical bandwidth service, it means that there is at least one historical bandwidth service (referred to as the candidate bandwidth service) for the target backup link on the backup end. In this case, a candidate bandwidth service is determined from the at least one candidate bandwidth service, and the historical bandwidth identification information of the candidate bandwidth service is determined as the target bandwidth identification information.

[0091] Exemplarily, determining a candidate bandwidth service from at least one candidate bandwidth service may include: comparing the candidate bandwidth service with the target bandwidth speed limit information respectively, and if there is a candidate bandwidth service with the same target bandwidth speed limit information, determining the candidate bandwidth service as the candidate bandwidth service; if there is no candidate bandwidth service with the same target bandwidth speed limit information, in this case, the disaster recovery platform determines any candidate bandwidth service as the candidate bandwidth service, determines the historical bandwidth identification information of the candidate bandwidth service as the target bandwidth identification information, and sends an update bandwidth instruction to the backup end to instruct the backup end to update the historical bandwidth speed limit information of the candidate bandwidth service to the target bandwidth speed limit information according to the update bandwidth instruction; wherein the update bandwidth instruction includes the historical bandwidth identification information and the target bandwidth speed limit information of the candidate bandwidth service, as shown in Table 2 below.

[0092] Table 2

[0093]

[0094] In the application, the backup end can call the API according to the bandwidth update instruction to update the historical bandwidth speed limit information of the candidate bandwidth service to the target bandwidth speed limit information.

[0095] The above-mentioned bandwidth management method determines a candidate bandwidth service from each historical bandwidth service according to the target tuple information and each historical tuple information, and determines the historical bandwidth identification information of the candidate bandwidth service as the target bandwidth identification information. When there is a candidate bandwidth service with the same target tuple information, the method can avoid creating too many bandwidth services by reusing the historical bandwidth service of the candidate bandwidth service, thereby reducing resource consumption. While providing backup services, the bandwidth of the cloud dedicated line in the target backup link can be limited by the reused historical bandwidth service, thereby reducing the impact of the backup service on the network transmission quality of other network services and improving the reliability of the overall system service.

[0096] In one embodiment, Figure 7 As shown, step S406, managing the target bandwidth service according to the target bandwidth identification information, includes the following steps S702 and S704.

[0097] S702: When it is detected that the configuration information of the target backup link has changed, the corresponding target configuration information is obtained from the backup end according to the target bandwidth identification information, and the current configuration information of the target backup link is obtained.

[0098] The current configuration information is used to indicate information related to the current configuration of the target backup link. Exemplarily, the current configuration information includes the current tuple information and the current bandwidth limit information of the target backup link; wherein the current tuple information includes the current five-tuple information, that is, the source IP address information, the source port information, the destination IP address information, the destination port information and the transmission protocol information; the current bandwidth limit information includes the current bandwidth limit value and the current bandwidth packet ID of the target backup link. The target configuration information is the configuration-related information when creating the target backup link. The target configuration information includes the target tuple information and the target bandwidth limit information of the target backup link. For details, please refer to the relevant introduction in the previous text, which will not be repeated here.

[0099] Exemplarily, changes in the configuration information of the target backup link include: changes in the bandwidth limit value of the target backup link (for example, the user modifies the bandwidth limit value on the disaster recovery platform through the request end), and changes in at least one of the synchronization port of the data synchronization tool in the target backup link.

[0100] In the application, when the disaster recovery platform detects that the configuration information of the target backup link has changed, it can obtain the corresponding target configuration information from the backup end according to the target bandwidth identification information, and obtain the current configuration information of the target backup link. It should be noted that the current configuration information does not need to rely on the target bandwidth identification information and can be directly obtained.

[0101] S704: When the current configuration information and the target configuration information are different, an adjustment instruction is sent to the backup end to instruct the backup end to adjust the target bandwidth service; the adjustment instruction includes the current configuration information and the target bandwidth identification information.

[0102] Exemplarily, taking the case where the target configuration information includes target tuple information and target bandwidth limit information, and the current configuration information includes current tuple information and current bandwidth limit information, the difference between the current configuration information and the target configuration information includes: the target tuple information is different from the current tuple information, and / or the target bandwidth limit information is different from the current bandwidth limit information.

[0103] Exemplarily, taking the case where the target tuple information includes the target quintuple information and the current tuple information includes the current quintuple information, the target tuple information being different from the current tuple information includes: the target quintuple information is different from at least one tuple information in the current quintuple information.

[0104] Exemplarily, taking the case where the target bandwidth limit information includes a target bandwidth limit value and a target bandwidth package ID, and the current bandwidth limit information includes a current bandwidth limit value and a current bandwidth package ID, the target bandwidth limit information is different from the current bandwidth limit information in that: the target bandwidth limit value is different from the current bandwidth limit value, and / or the target bandwidth package ID is different from the current bandwidth package ID.

[0105] In the application, the disaster recovery platform can call the API to obtain the target configuration information of the target backup link from the backup end according to the target bandwidth identification information, compare the current configuration information of the target backup link with the target configuration information, and send an adjustment instruction to the backup end when it is detected that the current configuration information and the target configuration information are different, so as to instruct the backup end to query the target bandwidth service according to the target bandwidth identification information in the adjustment instruction, and update the target bandwidth service according to the current configuration information in the adjustment instruction.

[0106] The above-mentioned bandwidth management method, when detecting that the configuration information of the target backup link has changed, obtains the corresponding target configuration information from the backup end according to the target bandwidth identification information, and obtains the current configuration information of the target backup link. When the current configuration information and the target configuration information are different, an adjustment instruction is sent to the backup end to instruct the backup end to adjust the target bandwidth service, thereby realizing real-time monitoring of the target bandwidth service of the target backup link, and when it is detected that the configuration information of the target backup link has changed, it can instruct the backup end to automatically adjust the corresponding target bandwidth service according to the target bandwidth identification information, thereby realizing synchronous update of the target bandwidth service, thereby realizing effective management of the cloud dedicated line bandwidth speed limit service corresponding to the backup service, ensuring that the data transmission speed limit of the backup link can continue to take effect, and improving the reliability of the system.

[0107] In one embodiment, Figure 8 As shown, the target configuration information includes target tuple information and target bandwidth limit information, and the current configuration information includes current tuple information and current bandwidth limit information. Step S704, when the current configuration information and the target configuration information are different, sends an adjustment instruction to the backup end, including the following steps S802 and S804.

[0108] S802: When the target tuple information and the current tuple information are different, a first adjustment instruction is sent to the backup end to instruct the backup end to delete the target bandwidth service according to the target bandwidth identification information, create the current bandwidth service of the target backup link according to the current configuration information, and send the current bandwidth identification information of the current bandwidth service; wherein the first adjustment instruction includes the current configuration information and the target bandwidth identification information.

[0109] In the application, after the disaster recovery platform obtains the target configuration information and the current configuration information, it compares the target tuple information and the current tuple information, and sends a first adjustment instruction to the backup end if the target tuple information and the current tuple information are different; correspondingly, after the backup end receives the first adjustment instruction, it queries and deletes the target bandwidth service according to the target bandwidth identification information in the first adjustment instruction, creates the current bandwidth service of the target backup link according to the current configuration information in the first adjustment instruction, and sends the current bandwidth identification information of the current bandwidth service to the disaster recovery platform, so that the disaster recovery platform can manage the current bandwidth service of the target backup link according to the current bandwidth identification information. Among them, the configuration information corresponding to the current bandwidth service is the current configuration information. Among them, the target bandwidth identification included in the first adjustment instruction can be seen in Table 3 below.

[0110] Table 3

[0111]

[0112] S804: When the target tuple information and the current tuple information are the same, and the target bandwidth speed limit information and the current bandwidth speed limit information are different, send a second adjustment instruction to the backup end to instruct the backup end to update the target bandwidth speed limit information of the target bandwidth service to the current bandwidth speed limit information; wherein the second adjustment instruction includes the current bandwidth speed limit information and the target bandwidth identification information.

[0113] In the application, after the disaster recovery platform obtains the target configuration information and the current configuration information, it compares the target tuple information and the current tuple information, and when the target tuple information and the current tuple information are the same, it continues to compare the target bandwidth speed limit information and the current bandwidth speed limit information, and when the target bandwidth speed limit information and the current bandwidth speed limit information are different, it sends a second adjustment instruction to the backup end; accordingly, after receiving the second adjustment instruction, the backup end queries the target bandwidth service according to the target bandwidth identification information in the second adjustment instruction, and updates the target bandwidth speed limit information in the target bandwidth service according to the current bandwidth speed limit information in the second adjustment instruction, and the updated bandwidth speed limit information of the target bandwidth service is the target bandwidth speed limit information.

[0114] The above-mentioned bandwidth management method, when the target tuple information and the current tuple information are different, sends a first adjustment instruction to the backup end to instruct the backup end to delete the target bandwidth service according to the target bandwidth identification information, and creates the current bandwidth service of the target backup link according to the current configuration information, and sends the current bandwidth identification information of the current bandwidth service; and when the target tuple information and the current tuple information are the same, and the target bandwidth speed limit information and the current bandwidth speed limit information are different, sends a second adjustment instruction to the backup end to instruct the backup end to update the target bandwidth speed limit information of the target bandwidth service to the current bandwidth speed limit information, thereby realizing real-time monitoring of the target backup link. Since the speed-limited bandwidth service of the cloud dedicated line acts on the specified five-tuple, when the tuple information of the backup link changes, the speed-limited bandwidth service is no longer valid for the backup link. In this regard, the bandwidth management method provided in the embodiment of the present application can, when the tuple information of the target backup link is monitored to change, send a first adjustment instruction to enable the backup end to delete the invalid speed-limited bandwidth service and reconfigure a new bandwidth service, thereby ensuring that the bandwidth speed limit of the backup link can continue to take effect and avoiding the impact of the backup service on other network services; and when the bandwidth speed limit information of the target backup link is monitored to change, the backup end can synchronously update the speed-limited bandwidth information of the speed-limited bandwidth service by sending a second adjustment instruction, thereby achieving effective control of the speed-limited bandwidth service of the backup link and improving the flexibility of bandwidth service configuration.

[0115] In one embodiment, step S302, in response to a data backup request sent by the requesting end, determines a target backup link corresponding to the data backup request, and sends a query request to the backup end, including the following steps: according to the backup subnet information in the data backup request, controls the backup node to open a backup database; according to the data source subnet information in the data backup request, controls the production node to deploy a data synchronization tool in the same subnet as the production database; determines a target backup link according to the production database, the data synchronization tool, and the backup database, the target backup link representing a link from the production database via the data synchronization tool to the local gateway, and through the cloud dedicated line in turn via the dedicated line gateway and the cloud gateway to the backup database.

[0116] Exemplarily, the data synchronization tool includes at least one of a data transmission service (DTS) and a cross-IDC (Internet Data Center) data synchronization component. The data synchronization tool may have the function of controlling the transmission speed, for example, setting the number of parallel threads for synchronization, the amount of data transmitted in each batch, etc.

[0117] The above-mentioned bandwidth management method controls the backup node to open the backup database according to the backup subnet information in the data backup request, controls the production node to deploy the data synchronization tool in the same subnet of the production database according to the data source subnet information in the data backup request, determines the target backup link according to the production database, the data synchronization tool and the backup database, realizes the deployment of the backup database and the data synchronization tool corresponding to the data backup request, so that the target backup link can be determined based on the deployed backup database and the data synchronization tool, and then the target bandwidth service can be provided based on the target backup link, and the source data generated by the production database can be backed up to the backup database under the bandwidth limit of the target bandwidth service, so as to realize data backup disaster recovery while reducing the impact of the backup service on the network transmission quality of other network services, thereby improving the overall service quality of the system.

[0118] In one embodiment, Fig. 9 and Fig.10 As shown, a bandwidth management method is provided, which is applied to Figure 1 and Figure 2 The database backup architecture shown is used as an example.

[0119] like Figure 2 As shown in Figure 1, the data synchronization tool is deployed at the production site and is responsible for extracting data from the production database and synchronizing it to the backup database. The network link for backup data transmission is as follows: Figure 2 As shown in the figure, the data is imported into the backup database through the local gateway, cloud dedicated line, dedicated line gateway, cloud gateway, etc. Cloud dedicated line provides a speed-limited bandwidth service. Users can specify a five-tuple to limit the bandwidth of the network link identified by the five-tuple.

[0120] Cloud dedicated line limits the speed of the database backup link of the disaster recovery platform through the speed-limiting bandwidth service. It mainly includes the following functions:

[0121] (1) Configuring the backup link: When users configure database backup tasks on the disaster recovery platform, they can specify parameters related to the backup speed limit.

[0122] The user configures the database backup task on the disaster recovery platform and fills in the relevant parameters. The parameters related to the speed limit are described as follows.

[0123] a. Data source subnet information: The subnet segment to which the production database belongs, expressed in CIDR format.

[0124] b. Backup subnet information: The subnet on the backup resource pool used to deploy the backup database.

[0125] c. Bandwidth limit value: The maximum transmission speed of the backup link set by the user, in MB / s.

[0126] d.Bandwidth package ID: The cloud dedicated line bandwidth package purchased by the user.

[0127] When the disaster recovery platform saves the backup task configuration, it needs to check whether the bandwidth limit value set by the user is greater than the bandwidth value corresponding to the cloud dedicated line bandwidth package ID. If so, the speed limit value needs to be reduced, otherwise the subsequent creation of the speed limit bandwidth will fail.

[0128] (2) Start backup speed limit: When starting a database backup task, create a speed limit bandwidth based on the backup speed limit parameters configured by the user and the five-tuple information of the backup link. Fig. 9 shown.

[0129] S902: The disaster recovery platform receives a data backup request sent by the requesting end.

[0130] S904: The disaster recovery platform opens a backup database at the backup node of the backup end according to the data backup request, and deploys a data synchronization tool in the same subnet of the production database of the production node.

[0131] S906: The disaster recovery platform obtains target configuration information of the target backup link corresponding to the data backup request.

[0132] The target configuration information includes target five-tuple information and target bandwidth speed limit information, wherein the target five-tuple information includes source IP address information, source port information, destination IP address information, destination port information and transmission protocol information. The target bandwidth speed limit information includes bandwidth speed limit value and bandwidth package ID.

[0133] S908: The disaster recovery platform sends a query request to the backup end and obtains a query response returned by the backup end to query whether the backup end has a bandwidth service corresponding to the created cloud dedicated line. If not, execute step S910. If yes, execute step S912.

[0134] S910: The disaster recovery platform sends a creation instruction to the backup end to instruct the backup end to create a target bandwidth service of the target backup link and send the target bandwidth identification information of the target bandwidth service to the disaster recovery platform. Then, step S918 is executed. The relevant information carried by the creation instruction can be seen in Table 1 above.

[0135] S912: The disaster recovery platform determines whether the historical five-tuple information of each historical bandwidth service in the query response is the same as the five-tuple information of the target backup link. If not, execute step S910; if yes, execute step S914.

[0136] S914: The disaster recovery platform determines whether the historical bandwidth speed limit value of each candidate bandwidth service is the same as the target bandwidth speed limit value of the target backup link. If not, execute step S916; if the historical bandwidth speed limit value of a candidate bandwidth service among the candidate bandwidth services is the same as the target bandwidth speed limit value of the target backup link, the historical bandwidth identification information of the candidate bandwidth service is used as the target bandwidth identification information, and execute step S918.

[0137] S916: The disaster recovery platform sends a bandwidth update instruction to the backup end, instructing the backup end to update the historical bandwidth speed limit value of a candidate bandwidth service to the target bandwidth speed limit value according to the bandwidth update instruction, and sends the bandwidth identification information of the candidate bandwidth service to the disaster recovery platform as the target bandwidth identification information. Then execute step S918.

[0138] S918: Record target bandwidth identification information.

[0139] (3) Update the backup speed limit: When the user modifies the speed limit parameters of the database backup link, or when the quintuple changes, the disaster recovery platform can update the speed limit bandwidth. Fig.10 shown.

[0140] S1002: The disaster recovery platform monitors the target backup link in real time.

[0141] S1004: When the disaster recovery platform detects that the user has modified the bandwidth speed limit value of the target backup link and / or the synchronization port of the data synchronization tool has changed, the current configuration information of the target backup link is obtained, and the target configuration information is obtained from the backup end according to the target bandwidth identification information.

[0142] The current configuration information includes the current five-tuple information and the current bandwidth speed limit information, and the current bandwidth speed limit information includes the current bandwidth speed limit value and the current bandwidth package ID. The target configuration information includes the target five-tuple information and the target bandwidth speed limit information, and the target bandwidth speed limit information includes the target bandwidth speed limit value and the target bandwidth package ID.

[0143] S1006: The disaster recovery platform determines whether the current five-tuple information is the same as the target five-tuple information. If so, execute step S1008; if not, execute step S1010.

[0144] S1008: The disaster recovery platform determines whether the current bandwidth speed limit value is the same as the target bandwidth speed limit value. If yes, the process returns to step S1002. If no, the process proceeds to step S1012.

[0145] S1010: The disaster recovery platform sends a first adjustment instruction to the backup end to instruct the backup end to delete the corresponding target bandwidth service according to the target bandwidth identification information in the first adjustment instruction, create a current bandwidth service according to the current configuration information in the first adjustment instruction, and send the current bandwidth identification information of the current bandwidth service to the disaster recovery platform.

[0146] S1012: The disaster recovery platform sends a second adjustment instruction to the backup end to instruct the backup end to query the target bandwidth service according to the target bandwidth identification information in the second adjustment instruction, and update the target bandwidth speed limit value of the target bandwidth service according to the current bandwidth speed limit value in the second adjustment instruction.

[0147] The bandwidth management method provided in the embodiment of the present application can limit the synchronization speed of the database backup link within a certain range by limiting the cloud dedicated line bandwidth used for database backup. Even during the peak period of production database business writing, the traffic passing through the network link will not exceed the speed-limited bandwidth. This can avoid the database backup task occupying too much bandwidth, thereby affecting the network transmission quality of other services. Compared with the speed control function of the data synchronization tool, the present application limits the transmission speed at the network transmission layer rather than the application layer, and can more accurately control the bandwidth used for data synchronization. In addition, when the speed limit parameters or quintuples of the backup link change, the method can make corresponding adjustments to the speed limit bandwidth, such as deleting the invalid speed limit bandwidth and reconfiguring the speed limit bandwidth, or synchronously updating the speed limit bandwidth, thereby ensuring that the speed limit can continue to take effect.

[0148] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0149] Based on the same inventive concept, the embodiment of the present application also provides a bandwidth management device for implementing the bandwidth management method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more bandwidth management device embodiments provided below can refer to the limitations of the bandwidth management method above, and will not be repeated here.

[0150] In one embodiment, Fig.11 As shown, a bandwidth management device 1100 is provided, including: a query module 1101, an acquisition module 1102 and a management module 1103. The query module 1101 is used to respond to the data backup request sent by the requesting end, determine the target backup link corresponding to the data backup request, and send a query request to the backup end; the query request is used to query the bandwidth service of the backup end for the cloud dedicated line in the backup link, and the target backup link is used to transmit the data generated by the production node of the requesting end to the backup node of the backup end via the cloud dedicated line for backup. The acquisition module 1102 is used to obtain the target configuration information of the target backup link and the query response sent by the backup end according to the query request. The management module 1103 is used to manage the target bandwidth service of the target backup link according to the target configuration information and the query response; the target bandwidth service is used to control the bandwidth of the target backup link to transmit data through the cloud dedicated line.

[0151] The bandwidth management device 1100, through the query module 1101, responds to the data backup request sent by the requesting end, determines the target backup link corresponding to the data backup request, and sends a query request to the backup end, obtains the target configuration information of the target backup link and the query response sent by the backup end according to the query request through the acquisition module 1102, and manages the target bandwidth service of the target backup link according to the target configuration information and the query response through the management module 1103, so that the bandwidth of the target backup link can be limited based on the target bandwidth service, realizing the bandwidth limitation of the data backup link, avoiding the impact on other network services that share the cloud dedicated line with the data backup service, and ensuring the stability and reliability of network transmission. The embodiment of the present application limits the bandwidth of the cloud dedicated line in the data backup link. Compared with using data synchronization tools to control the data transmission speed (for example, setting the number of parallel synchronization processes, the number of single batch transmissions, etc.), the embodiment of the present application realizes transmission speed limitation from the network layer rather than the application layer, which can more accurately control the bandwidth used for data synchronization and expand the scope of data bandwidth control. In addition, the bandwidth management method provided in the embodiment of the present application can automatically adjust and manage the corresponding target bandwidth service based on the data backup request sent by the requesting end, thereby realizing adaptive management of different data backup links corresponding to the data backup requests sent by different requesting ends, and improving the effective control of bandwidth services.

[0152] In one embodiment, the management module is further used to send a creation instruction to the backup end to instruct the backup end to create a target bandwidth service and obtain target bandwidth identification information of the target bandwidth service sent by the backup end when the number of historical bandwidth services included in the query response is 0; wherein the creation instruction includes target configuration information; when the query response includes at least one historical bandwidth service, obtain target bandwidth identification information of the target backup link according to the target configuration information and historical attribute information of each historical bandwidth service; and manage the target bandwidth service according to the target bandwidth identification information.

[0153] In one embodiment, the target configuration information includes target tuple information, and the historical attribute information includes historical tuple information, wherein the acquisition module is further used to send a creation instruction to the backup end to instruct the backup end to create a target bandwidth service when the target tuple information and each historical tuple information are different; wherein the creation instruction includes the target configuration information; and the target bandwidth identification information sent by the backup end is acquired.

[0154] In one embodiment, the target configuration information includes target tuple information and target bandwidth speed limit information, the historical attribute information includes historical configuration information and historical bandwidth identification information, the historical configuration information includes historical tuple information and historical bandwidth speed limit information, wherein the acquisition module is further used to determine a candidate bandwidth service from each historical bandwidth service based on the target tuple information and each historical tuple information; determine the historical bandwidth identification information of the candidate bandwidth service as the target bandwidth identification information; wherein the historical tuple information of the candidate bandwidth service is the same as the target tuple information.

[0155] In one embodiment, the management module is also used to obtain corresponding target configuration information from the backup end according to the target bandwidth identification information and obtain current configuration information of the target backup link when a change in configuration information of the target backup link is detected; when the current configuration information and the target configuration information are different, send an adjustment instruction to the backup end to instruct the backup end to adjust the target bandwidth service; the adjustment instruction includes the current configuration information and the target bandwidth identification information.

[0156] In one embodiment, the target configuration information includes target tuple information and target bandwidth speed limit information, and the current configuration information includes current tuple information and current bandwidth speed limit information, wherein the management module is further used to send a first adjustment instruction to the backup end when the target tuple information and the current tuple information are different, so as to instruct the backup end to delete the target bandwidth service according to the target bandwidth identification information, create the current bandwidth service of the target backup link according to the current configuration information, and send the current bandwidth identification information of the current bandwidth service; wherein the first adjustment instruction includes the current configuration information and the target bandwidth identification information.

[0157] The management module is also used to send a second adjustment instruction to the backup end when the target tuple information is the same as the current tuple information and the target bandwidth limit information is different from the current bandwidth limit information, so as to instruct the backup end to update the target bandwidth limit information of the target bandwidth service to the current bandwidth limit information; wherein the second adjustment instruction includes the current bandwidth limit information and the target bandwidth identification information.

[0158] In one embodiment, the query module is also used to control the backup node to open a backup database based on the backup subnet information in the data backup request; control the production node to deploy a data synchronization tool in the same subnet as the production database based on the data source subnet information in the data backup request; determine the target backup link based on the production database, the data synchronization tool and the backup database, and the target backup link represents a link from the production database via the data synchronization tool to the local gateway, and then through the cloud dedicated line, in turn through the dedicated line gateway and the cloud gateway to the backup database.

[0159] Each module in the above bandwidth management device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0160] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig.12 As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a bandwidth management method is implemented.

[0161] Those skilled in the art will understand that Fig.12 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0162] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps of the above method when executing the computer program.

[0163] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the aforementioned method are implemented.

[0164] In one embodiment, a computer program product is provided, comprising a computer program, which implements the steps of the aforementioned method when executed by a processor.

[0165] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0166] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0167] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0168] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A bandwidth management method, characterized in that: The method comprises: In response to a data backup request sent by a requesting end, a target backup link corresponding to the data backup request is determined, and a query request is sent to the backup end; wherein the query request is used to query the bandwidth service of the backup end for the cloud dedicated line in the backup link, and the target backup link is used to transmit the data generated by the production node of the requesting end to the backup node of the backup end via the cloud dedicated line for backup; Acquire target configuration information of the target backup link and a query response sent by the backup end according to the query request; The target bandwidth service of the target backup link is managed according to the target configuration information and the query response; wherein the target bandwidth service is used to control the bandwidth of the target backup link transmitting data through the cloud dedicated line.

2. The method according to claim 1, characterized in that: The managing the target bandwidth service of the target backup link according to the target configuration information and the query response includes: In the case that the number of historical bandwidth services included in the query response is 0, sending a creation instruction to the backup end to instruct the backup end to create the target bandwidth service, and obtaining the target bandwidth identification information of the target bandwidth service sent by the backup end; wherein the creation instruction includes the target configuration information; In a case where the query response includes at least one historical bandwidth service, acquiring target bandwidth identification information of the target backup link according to the target configuration information and historical attribute information of each of the historical bandwidth services; The target bandwidth service is managed according to the target bandwidth identification information.

3. The method according to claim 2, characterized in that The target configuration information includes target tuple information, and the historical attribute information includes historical tuple information, wherein acquiring the target bandwidth identification information of the target backup link according to the target configuration information and the historical attribute information of each of the historical bandwidth services includes: In the case where the target tuple information and each of the historical tuple information are different, sending a creation instruction to the backup end to instruct the backup end to create the target bandwidth service; wherein the creation instruction includes the target configuration information; Acquire the target bandwidth identification information sent by the backup end.

4. The method according to claim 2, characterized in that: The target configuration information includes target tuple information and target bandwidth speed limit information, the historical attribute information includes historical configuration information and historical bandwidth identification information, and the historical configuration information includes historical tuple information and historical bandwidth speed limit information, wherein acquiring the target bandwidth identification information of the target backup link according to the target configuration information and the historical attribute information of each of the historical bandwidth services includes: Determine a candidate bandwidth service from each of the historical bandwidth services according to the target tuple information and each of the historical tuple information; wherein the historical tuple information of the candidate bandwidth service is the same as the target tuple information; The historical bandwidth identification information of the candidate bandwidth service is determined as the target bandwidth identification information.

5. The method according to any one of claims 2 to 4, characterized in that: The managing the target bandwidth service according to the target bandwidth identification information includes: When detecting that the configuration information of the target backup link changes, acquiring corresponding target configuration information from the backup end according to the target bandwidth identification information, and acquiring current configuration information of the target backup link; In the case that the current configuration information and the target configuration information are different, an adjustment instruction is sent to the backup end to instruct the backup end to adjust the target bandwidth service; the adjustment instruction includes the current configuration information and the target bandwidth identification information.

6. The method according to claim 5, characterized in that The target configuration information includes target tuple information and target bandwidth speed limit information, and the current configuration information includes current tuple information and current bandwidth speed limit information, wherein, when the current configuration information and the target configuration information are different, sending an adjustment instruction to the backup end includes: In the case where the target tuple information and the current tuple information are different, sending a first adjustment instruction to the backup end to instruct the backup end to delete the target bandwidth service according to the target bandwidth identification information, create a current bandwidth service of the target backup link according to the current configuration information, and send the current bandwidth identification information of the current bandwidth service; wherein the first adjustment instruction includes the current configuration information and the target bandwidth identification information; When the target tuple information is the same as the current tuple information, and the target bandwidth speed limit information is different from the current bandwidth speed limit information, a second adjustment instruction is sent to the backup end to instruct the backup end to update the target bandwidth speed limit information of the target bandwidth service to the current bandwidth speed limit information; wherein the second adjustment instruction includes the current bandwidth speed limit information and the target bandwidth identification information.

7. The method according to any one of claims 1 to 4, characterized in that: The step of responding to the data backup request sent by the requesting end, determining a target backup link corresponding to the data backup request, and sending a query request to the backup end includes: According to the backup subnet information in the data backup request, control the backup node to open a backup database; According to the data source subnet information in the data backup request, control the production node to deploy a data synchronization tool in the same subnet as the production database; The target backup link is determined according to the production database, the data synchronization tool and the backup database, wherein the target backup link represents a link from the production database via the data synchronization tool to the local gateway, and through the cloud dedicated line in sequence via the dedicated line gateway and the cloud gateway to the backup database.

8. A bandwidth management device, characterized in that: The device comprises: A query module, configured to respond to a data backup request sent by a requesting end, determine a target backup link corresponding to the data backup request, and send a query request to a backup end; wherein the query request is used to query the bandwidth service of the backup end for the cloud dedicated line in the backup link, and the target backup link is used to transmit the data generated by the production node of the requesting end to the backup node of the backup end via the cloud dedicated line for backup; An acquisition module, used to acquire target configuration information of the target backup link and a query response sent by the backup end according to the query request; A management module is used to manage the target bandwidth service of the target backup link according to the target configuration information and the query response; wherein the target bandwidth service is used to control the bandwidth of the target backup link transmitting data through the cloud dedicated line.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images