Bandwidth management method and apparatus, computer device and storage medium

Abstract

The application 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 a bandwidth service of a cloud private line in the backup link by the backup end, and the target backup link is used for transmitting data generated by a production node of the request end to a backup node of the backup end through the cloud private line for backup; target configuration information of the target backup link and a query response sent by the backup end according to the query request are acquired; and 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 for controlling the bandwidth of the data transmitted by the target backup link through the cloud private line. The method can provide a speed-limited bandwidth service for a backup service, and effectively manage the speed-limited bandwidth service.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a bandwidth management method, apparatus, computer equipment, and storage medium. Background Technology

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

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

[0004] In existing technologies, when production nodes use backup services for database disaster recovery backups, the backup services will consume resources of other services, resulting in a decrease in the processing efficiency of other services. Summary of the Invention

[0005] Therefore, it is necessary to provide a bandwidth management method, apparatus, computer equipment, and storage medium to address the aforementioned technical problems, which can provide rate-limited bandwidth services for backup services and achieve effective management of rate-limited bandwidth services.

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

[0007] In response to a data backup request sent by the requesting end, the 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 cloud dedicated line in the backup link by the backup end, 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] Obtain the target configuration information of the target backup link and the query response sent by the backup end according to the query request;

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

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

[0011] If the number of historical bandwidth services included in the query response is 0, a creation instruction is sent to the backup terminal to instruct the backup terminal to create the target bandwidth service, and the target bandwidth identification information of the target bandwidth service sent by the backup terminal is obtained; wherein, the creation instruction includes the target configuration information;

[0012] If the query response includes at least one historical bandwidth service, the target bandwidth identification information of the target backup link is obtained based on the target configuration information and the historical attribute information of each of the historical bandwidth services.

[0013] The target bandwidth service is managed based on 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. The step of obtaining the target bandwidth identifier information of the target backup link based on the target configuration information and the historical attribute information of each of the historical bandwidth services includes:

[0015] If the target tuple information and each of the historical tuple information are different, a creation instruction is sent to the backup terminal to instruct the backup terminal to create the target bandwidth service; wherein, the creation instruction includes the target configuration information;

[0016] Obtain the target bandwidth identification information sent by the backup terminal.

[0017] In one embodiment, the target configuration information includes target tuple information and target bandwidth rate limiting information, and the historical attribute information includes historical configuration information and historical bandwidth identification information. The historical configuration information includes historical tuple information and historical bandwidth rate limiting information. The step of obtaining 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 includes:

[0018] Based on the target tuple information and each of the historical tuple information, candidate bandwidth services are determined from each of the historical bandwidth services; wherein the historical tuple information of the candidate bandwidth services 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 embodiment, managing the target bandwidth service based on the target bandwidth identification information includes:

[0021] If a change in the configuration information of the target backup link is detected, the corresponding target configuration information is obtained from the backup end based on the target bandwidth identification information, and the current configuration information of the target backup link is also obtained.

[0022] If the current configuration information and the target configuration information are different, an adjustment instruction is sent to the backup terminal to instruct the backup terminal 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 rate limit information, and the current configuration information includes current tuple information and current bandwidth rate limit information. The step of sending an adjustment command to the backup terminal when the current configuration information and the target configuration information differ includes:

[0024] If 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;

[0025] If the target tuple information and the current tuple information are the same, and the target bandwidth rate limit information and the current bandwidth rate limit information are different, a second adjustment instruction is sent to the backup terminal to instruct the backup terminal to update the target bandwidth rate limit information of the target bandwidth service to the current bandwidth rate limit information; wherein, the second adjustment instruction includes the current bandwidth rate limit information and the target bandwidth identification information.

[0026] In one embodiment, the step of responding to a 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 includes:

[0027] Based on the backup subnet information in the data backup request, control the backup node to activate the backup database;

[0028] Based on the data source subnet information in the data backup request, control the production node to deploy a data synchronization tool within the same subnet of the production database;

[0029] The target backup link is determined based on the production database, the data synchronization tool, and the backup database. The target backup link represents the link from the production database through the data synchronization tool to the local gateway, and then through the cloud dedicated line, the dedicated line gateway, and the cloud gateway to the backup database.

[0030] Secondly, this application provides a bandwidth management device, the device comprising:

[0031] The query module is used to respond to a 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; wherein, the query request is used to query the bandwidth service of the cloud dedicated line in the backup link by the backup end, 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] The acquisition module is used to acquire the target configuration information of the target backup link and the query response sent by the backup end according to the query request;

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

[0034] Thirdly, this application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described method.

[0035] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.

[0036] The aforementioned bandwidth management method, apparatus, computer equipment, and storage medium, in response to a 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 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. Based on the target configuration information and the query response, the target bandwidth service of the target backup link is managed, thereby enabling bandwidth limiting of the target backup link based on the target bandwidth service. This achieves bandwidth restriction of the data backup link, preventing other network services sharing the cloud dedicated line with the data backup service from being affected, and ensuring the stability and reliability of network transmission. This application embodiment, by limiting the cloud dedicated line bandwidth in the data backup link, compared to controlling data transmission speed using data synchronization tools, achieves transmission speed limitation at the network layer rather than the application layer, enabling more accurate control of the bandwidth used for data synchronization and expanding the scope of data bandwidth management. Furthermore, the bandwidth management method provided in this application embodiment can automatically adjust the management of the corresponding target bandwidth service based on the data backup request sent by the requesting end, achieving adaptive management of different data backup links corresponding to different requesting ends, and improving the effective control of bandwidth services. Attached Figure Description

[0037] Figure 1 This is a diagram illustrating the application environment of a bandwidth management method in one embodiment;

[0038] Figure 2 This is a diagram illustrating the application environment of the bandwidth management method in another embodiment;

[0039] Figure 3 This is one of the flowcharts illustrating a bandwidth management method in one embodiment;

[0040] Figure 4 This is a second flowchart illustrating a bandwidth management method in one embodiment;

[0041] Figure 5 This is the third flowchart of a bandwidth management method in one embodiment;

[0042] Figure 6 This is the fourth flowchart of a bandwidth management method in one embodiment;

[0043] Figure 7 This is the fifth flowchart of a bandwidth management method in one embodiment;

[0044] Figure 8 This is a flowchart of a bandwidth management method in one embodiment, number six.

[0045] Figure 9 This is the seventh flowchart of a bandwidth management method in one embodiment;

[0046] Figure 10 This is the eighth flowchart of a bandwidth management method in one embodiment;

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

[0048] Figure 12 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0050] The bandwidth management method provided in this application embodiment can be applied to, for example, Figure 1 The application environment shown. For example... Figure 1 and Figure 2 As shown, the application environment includes a disaster recovery platform 10, a requesting end 20, and a backup end 30. The disaster recovery platform 10 is connected to both the requesting end 20 and the backup end 30 via a network. The disaster recovery platform 10 responds to data backup requests sent by the requesting end 20, determines the target backup link corresponding to the data backup request, sends a query request to the backup end 30, obtains the target configuration information of the target backup link and the query response sent by the backup end 30 based on the query request, and manages the target bandwidth service of the target backup link based on the target configuration information and the query response. The production node 21 can be understood as the node that generates the source data to be backed up. For example, 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 data center, a private cloud, or other resource pool with data backup requirements. The requesting end 20 can be understood as the terminal or server corresponding to the production node 21, and the requesting end 20 is used to manage and control the production node 21. Backup node 31 is used to back up the source data. For example, backup node 31 can be a cloud data center, a private cloud, or other resource pool capable of backing up data. Backup terminal 30 can be understood as the terminal, server, or platform corresponding to backup node 31. Backup terminal 30 is used to manage and control backup node 31.

[0051] It is understood that the target backup link is used to transmit data generated by the production node 21 of the requesting end 20 to the backup node 31 of the backup end 30 via a cloud dedicated line for backup. For example, as shown... 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 to the local gateway 213 via the data synchronization tool 212, then to the dedicated line gateway 311 of the backup node 31 via the cloud dedicated line, and then to the backup database 313 via the cloud gateway 312.

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

[0053] In one embodiment, such as Figures 1 to 3 As shown, a bandwidth management method is provided, which is applied to... Figure 1 The following steps are used as an example of a disaster recovery platform, including 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] A data backup request indicates a request to back up data generated by the production node on the requesting end. For example, a data backup request includes data source subnet information, backup subnet information, and target bandwidth limiting information. The data source subnet information indicates the subnet segment to which the production node belongs, and can be represented in CIDR (Classless Inter-Domain Routing) format. The backup subnet information indicates the subnet segment to which the backup node belongs, and can also be represented in CIDR format. The target bandwidth limiting information indicates information related to bandwidth limiting of the target backup link. For example, the target bandwidth limiting information includes a bandwidth limit value and a bandwidth packet ID (Identity). The bandwidth limit value can be the maximum transmission speed of the target backup link set by the user, in MB / s; the bandwidth packet ID identifies the bandwidth packet, which is the bandwidth packet applied by the cloud leased line bandwidth limiting product purchased by the user.

[0056] In the application, after receiving a 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, the bandwidth limit value set by the user is adjusted, 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 leased line in the backup link on the backup end. The query request aims to query the bandwidth services already created on the backup end. Here, bandwidth service refers to the service that manages and controls the cloud leased line bandwidth of the backup link for data transmission between the production node and the backup node. The target backup link is used to transmit data generated by the production node on the requesting end to the backup node on the backup end via the cloud leased line for backup. The bandwidth services already created on the backup end may or may not include the target bandwidth service of the target backup link.

[0058] In the application, after receiving the initial data backup request from the requesting end, the disaster recovery platform can instruct the backup end to activate the backup database on the backup node and instruct the requesting end to deploy a data synchronization tool on the production node. This determines the target backup link corresponding to the data backup request; that is, from the production database on the production node, it sequentially goes through the data synchronization tool and the local gateway to the cloud dedicated line, and then sequentially through the dedicated line gateway and the cloud gateway on the backup node to the backup database. Furthermore, 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 check if the bandwidth service corresponding to the created cloud dedicated line exists.

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

[0060] Target configuration information represents information related to the configuration of the target backup link. For example, target configuration information includes target tuple information and target bandwidth limiting information. The target tuple information identifies the basic elements of the target backup link in network communication. For example, the target tuple information includes the source IP (Internet Protocol) address, source port, destination IP address, destination port, and transport protocol information of the target backup link. The source IP address, source port, destination IP address, destination port, and transport protocol are collectively referred to as a five-tuple. Target bandwidth limiting information represents information on limiting the cloud leased line bandwidth in the target backup link. For example, the target bandwidth limiting information includes the bandwidth limiting value and the bandwidth packet ID.

[0061] The query response is generated and sent by the backup endpoint based on the query request. The query response indicates whether the backup endpoint has a bandwidth service corresponding to a created cloud dedicated line. For example, if the backup endpoint has a created cloud dedicated line bandwidth service, the query response includes historical attribute information of the bandwidth service corresponding to the created cloud dedicated line, or simply referred to as the historical bandwidth service object, where the historical attribute information represents information related to the historical bandwidth service. As another example, if the backup endpoint does not have a bandwidth service corresponding to a created cloud dedicated line, the query response does not include the historical bandwidth service object.

[0062] S306: Manage the target bandwidth service of the target backup link based on the target configuration information and query response.

[0063] The target bandwidth service is used to manage the rate limiting of the cloud dedicated line bandwidth of the target backup link. For example, the target bandwidth service manages the rate limiting of the cloud dedicated line bandwidth of the target backup link according to a bandwidth rate limiting value, which is described above and will not be repeated here. In this embodiment, the bandwidth service can be understood as a service that limits the rate of the cloud dedicated line bandwidth of the backup link in the backup service.

[0064] In applications, the disaster recovery platform can manage the target bandwidth service based on the target configuration information and query responses. Managing the target bandwidth service can be understood as instructing the backup endpoint to create, update, and delete the target bandwidth service, etc., as detailed below.

[0065] The backup end can provide the target bandwidth service to the requesting end, so that, under the bandwidth rate limit of the target bandwidth service, the source data generated by the production node, such as the production database, can be backed up to the backup database of the backup node, thereby realizing data disaster recovery backup.

[0066] The aforementioned bandwidth management method, in response to a 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 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. Based on the target configuration information and the query response, it manages the target bandwidth service of the target backup link, thereby enabling bandwidth limiting of the target backup link based on the target bandwidth service. This achieves bandwidth restriction of the data backup link, preventing other network services sharing the cloud dedicated line with the data backup service from being affected, and ensuring the stability and reliability of network transmission. This embodiment of the application, by limiting the cloud dedicated line bandwidth in the data backup link, compared to controlling the data transmission speed using data synchronization tools (e.g., setting the number of parallel synchronization processes, the number of transmissions in a single batch, etc.), achieves transmission speed limitation at the network layer rather than the application layer, enabling more accurate control of the bandwidth used for data synchronization and expanding the scope of data bandwidth management. Furthermore, the bandwidth management method provided in this embodiment can automatically adjust the management of the corresponding target bandwidth service based on the data backup request sent by the requesting end, achieving adaptive management of different data backup links corresponding to different requesting ends, and improving the effective control of bandwidth services.

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

[0068] S402: If 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 the 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 query response includes 0 historical bandwidth services, it means that the backup end does not have a bandwidth service corresponding to the created cloud private line. In this case, the disaster recovery platform sends a creation command 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 command.

[0070] The creation command includes target configuration information. For example, the target configuration information includes target tuple information and target bandwidth limiting information. The target tuple information includes the source IP address, source port, destination IP address, destination port, and transport protocol information of the target backup link. The target bandwidth limiting information includes the bandwidth limit value and the bandwidth packet ID. See Table 1 below for examples of target configuration information.

[0071] Table 1

[0072]

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

[0074] In the application, after receiving the creation command, the backup terminal creates the target backup link and the target bandwidth service of the target backup link according to the target configuration information in the creation command, 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 and control the target bandwidth service based on the target bandwidth identification information. The target bandwidth identification information is used to identify the target bandwidth service.

[0075] S404: If the query response includes at least one historical bandwidth service, 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.

[0076] If the query response includes at least one historical bandwidth service, it means that the backup end has a bandwidth service corresponding to the created cloud private line, i.e., a 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] Historical attribute information is used to represent information related to historical bandwidth services. For example, historical attribute information includes historical configuration information and historical bandwidth identification information. The historical configuration information represents information related to the configuration of the historical bandwidth service, similar to the target configuration information for the target bandwidth service; see the previous introduction to target configuration information for details, which will not be repeated here. The historical bandwidth identification information is used to identify the historical bandwidth service.

[0078] S406: Manage target bandwidth services based on target bandwidth identification information.

[0079] In applications, the disaster recovery platform can manage the target bandwidth service provided by the backup end to the requesting end based on the target bandwidth identification information.

[0080] The aforementioned bandwidth management method, when the query response includes zero historical bandwidth services, sends a creation command to the backup end to instruct it to create a target bandwidth service and obtains the target bandwidth identifier information of the target bandwidth service sent by the backup end. When the query response includes at least one historical bandwidth service, it obtains the target bandwidth identifier information of the target backup link based on the target configuration information and the historical attribute information of each historical bandwidth service, and manages the target bandwidth service based on the target bandwidth identifier information. This method, by querying whether the backup end has created a historical bandwidth service, can achieve the reuse of historical bandwidth services, avoid over-configuration of bandwidth services, reduce resource consumption, and ensure the effective implementation of backup services and corresponding bandwidth services by creating or updating the target bandwidth service when no historical bandwidth service or no bandwidth service that meets backup requirements exists. In addition, this method manages bandwidth services through bandwidth identifier information, which helps to adjust and update bandwidth services in real time according to backup service requirements, improving the reliability of bandwidth services.

[0081] In one embodiment, such as Figure 5 As shown, the target configuration information includes target tuple information, and the historical attribute information includes historical tuple information. In step S404, the target bandwidth identification information of the target backup link is obtained based on the target configuration information and the historical attribute information of each historical bandwidth service, including the following steps S502 and S504.

[0082] S502: If the target tuple information and the information of each historical tuple are different, send a creation command to the backup end to instruct the backup end to create the target bandwidth service; wherein, the creation command includes target configuration information.

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

[0084] For example, 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 the comparison result. The comparison result indicates whether the target tuple information is the same as each historical tuple information. Taking a tuple information including five-tuple information, namely source IP address information, source port information, destination IP address information, destination port information, and transport protocol information, as an example, the disaster recovery platform compares the target five-tuple information and the historical five-tuple information one by one. If the target five-tuple information and the historical five-tuple information are different at least one time, it is determined that the target five-tuple information is different from that historical five-tuple information.

[0085] If the comparison result shows 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 command 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 command, and send 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 bandwidth management method described above sends a creation command to the backup end when the target tuple information and the information of each historical tuple are different. This command instructs the backup end to create a target bandwidth service and obtains the target bandwidth identification information sent by the backup end. In the absence of a historical bandwidth service that meets the data backup request, this method creates a new target bandwidth service. This allows the backup service to be provided while simultaneously limiting the bandwidth of the cloud private line in the target backup link. This reduces the impact of the backup service on the network transmission quality of other network services and improves the overall reliability of the system service.

[0087] In one embodiment, such as Figure 6 As shown, the target configuration information includes target tuple information and target bandwidth rate limit information, and the historical attribute information includes historical configuration information and historical bandwidth identifier information. The historical configuration information includes historical tuple information and historical bandwidth rate limit information. In step S404, the target bandwidth identifier information of the target backup link is obtained according to the target configuration information and the historical attribute information of each historical bandwidth service, including the following steps S602 and S604.

[0088] S602: Based on the target tuple information and the information of each historical tuple, determine the candidate bandwidth service from each historical bandwidth service; 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 shows 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 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] For example, determining a candidate bandwidth service from at least one candidate bandwidth service may include: comparing the candidate bandwidth service with the target bandwidth rate limit information; if there is a candidate bandwidth service that is identical to the target bandwidth rate limit information, then the candidate bandwidth service is determined as a candidate bandwidth service; if there is no candidate bandwidth service that is identical to the target bandwidth rate limit information, in this case, the disaster recovery platform determines any candidate bandwidth service as a 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 rate limit information of the candidate bandwidth service to the target bandwidth rate limit information according to the update bandwidth instruction; wherein, the update bandwidth instruction includes the historical bandwidth identification information and the target bandwidth rate 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 update bandwidth command to update the historical bandwidth rate limit information of the candidate bandwidth service to the target bandwidth rate limit information.

[0095] The bandwidth management method described above determines candidate bandwidth services from historical bandwidth services based on target tuple information and historical tuple information. The historical bandwidth identifier information of the candidate bandwidth services is then used as the target bandwidth identifier information. When a candidate bandwidth service with the same target tuple information exists, this method can avoid creating too many bandwidth services and reduce resource consumption by reusing the historical bandwidth services of the candidate bandwidth services. While providing backup services, it can also limit the bandwidth of the cloud private line in the target backup link by using the reused historical bandwidth services, thereby reducing the impact of the backup service on the network transmission quality of other network services and improving the overall reliability of the system service.

[0096] In one embodiment, such as Figure 7 As shown, step S406, which manages the target bandwidth service based on the target bandwidth identification information, includes the following steps S702 and S704.

[0097] S702: When a change in the configuration information of the target backup link is detected, the corresponding target configuration information is obtained from the backup end based on the target bandwidth identification information, as well as the current configuration information of the target backup link.

[0098] The current configuration information represents information related to the current configuration of the target backup link. For example, the current configuration information includes the current tuple information and the current bandwidth limit information of the target backup link; the current tuple information includes the current five-tuple information, namely, source IP address information, source port information, destination IP address information, destination port information, and transport 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 the target backup link is created. The target configuration information includes the target tuple information and target bandwidth limit information of the target backup link, as detailed in the previous section, and will not be repeated here.

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

[0100] In application, when the disaster recovery platform detects a change in the configuration information of the target backup link, it can retrieve the corresponding target configuration information from the backup end based on the target bandwidth identifier information, and also obtain the current configuration information of the target backup link. It should be noted that the current configuration information does not depend on the target bandwidth identifier information and can be obtained directly.

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

[0102] For example, taking the target configuration information as including target tuple information and target bandwidth rate limit information, and the current configuration information as including current tuple information and current bandwidth rate 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 rate limit information is different from the current bandwidth rate limit information.

[0103] For example, taking the target tuple information as including target quintuple information and the current tuple information as including current quintuple information as an example, the difference between the target tuple information and the current tuple information includes: the target quintuple information and the current quintuple information are different from at least one of the tuple information.

[0104] For example, taking the target bandwidth rate limiting information as including the target bandwidth rate limiting value and the target bandwidth packet ID, and the current bandwidth rate limiting information as including the current bandwidth rate limiting value and the current bandwidth packet ID, the differences between the target bandwidth rate limiting information and the current bandwidth rate limiting information include: the target bandwidth rate limiting value is different from the current bandwidth rate limiting value, and / or, the target bandwidth packet ID is different from the current bandwidth packet 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 based on 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 if the current configuration information and the target configuration information are detected to be different. This instruction instructs the backup end to query the target bandwidth service based on the target bandwidth identification information in the adjustment instruction and update the target bandwidth service based on the current configuration information in the adjustment instruction.

[0106] The aforementioned bandwidth management method, upon detecting a change in the configuration information of the target backup link, retrieves the corresponding target configuration information from the backup end based on the target bandwidth identifier information, as well as the current configuration information of the target backup link. If the current configuration information differs from the target configuration information, an adjustment command is sent to the backup end to instruct it to adjust the target bandwidth service. This achieves real-time monitoring of the target bandwidth service of the target backup link. Furthermore, when a change in the configuration information of the target backup link is detected, the method can instruct the backup end to automatically adjust the corresponding target bandwidth service based on the target bandwidth identifier information, thus achieving synchronous updates of the target bandwidth service. This enables effective management of the cloud dedicated line bandwidth rate limiting service corresponding to the backup service, ensuring that the data transmission speed limit of the backup link remains in effect and improving system reliability.

[0107] In one embodiment, such as Figure 8 As shown, the target configuration information includes target tuple information and target bandwidth rate limit information, and the current configuration information includes current tuple information and current bandwidth rate limit information. In step S704, if the current configuration information and the target configuration information are different, an adjustment instruction is sent 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, and to create the current bandwidth service of the target backup link according to the current configuration information, and to 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 obtaining the target configuration information and the current configuration information, the disaster recovery platform compares the target tuple information and the current tuple information. If the target tuple information and the current tuple information are different, it sends a first adjustment command to the backup end. Correspondingly, after receiving the first adjustment command, the backup end queries and deletes the target bandwidth service according to the target bandwidth identifier information in the first adjustment command, and creates the current bandwidth service of the target backup link according to the current configuration information in the first adjustment command. It then sends the current bandwidth identifier 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 identifier information. The configuration information corresponding to the current bandwidth service is the current configuration information. The target bandwidth identifier included in the first adjustment command 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 rate limit information and the current bandwidth rate limit information are different, a second adjustment instruction is sent to the backup end to instruct the backup end to update the target bandwidth rate limit information of the target bandwidth service to the current bandwidth rate limit information; wherein, the second adjustment instruction includes the current bandwidth rate 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 with the current tuple information. If the target tuple information and the current tuple information are the same, it continues to compare the target bandwidth rate limit information with the current bandwidth rate limit information. If the target bandwidth rate limit information and the current bandwidth rate limit information are different, it sends a second adjustment instruction to the backup end. Correspondingly, after receiving the second adjustment instruction, the backup end queries the target bandwidth service according to the target bandwidth identifier information in the second adjustment instruction, and updates the target bandwidth rate limit information in the target bandwidth service according to the current bandwidth rate limit information in the second adjustment instruction. The updated bandwidth rate limit information of the target bandwidth service is the target bandwidth rate limit information.

[0114] The aforementioned 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 identifier information, create the current bandwidth service of the target backup link according to the current configuration information, and send the current bandwidth identifier information of the current bandwidth service; and when the target tuple information and the current tuple information are the same, but the target bandwidth rate limit information and the current bandwidth rate limit information are different, sends a second adjustment instruction to the backup end to instruct the backup end to update the target bandwidth rate limit information of the target bandwidth service to the current bandwidth rate limit information, thereby realizing real-time monitoring of the target backup link. Since the bandwidth limiting service of cloud private lines applies to a specified five-tuple, when the tuple information of the backup link changes, the bandwidth limiting service is no longer effective for the backup link. To address this, the bandwidth management method provided in this application can, upon detecting a change in the tuple information of the target backup link, send a first adjustment command to cause the backup end to delete the invalid bandwidth limiting service and reconfigure a new bandwidth service, ensuring that the bandwidth limiting of the backup link continues to be effective and avoiding the impact of the backup service on other network services. Furthermore, upon detecting a change in the bandwidth limiting information of the target backup link, a second adjustment command can be sent to enable the backup end to synchronously update the bandwidth limiting information of the bandwidth limiting service, achieving effective control over the bandwidth limiting 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 the 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 the 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; and determines the target backup link according to the production database, the data synchronization tool, and the backup database, wherein the target backup link represents the link from the production database through the data synchronization tool to the local gateway, and then through the cloud dedicated line, the dedicated line gateway, and the cloud gateway to the backup database.

[0116] For example, a 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 ability to control the transmission speed, such as setting the number of parallel threads for synchronization and the amount of data transmitted in each batch.

[0117] The aforementioned bandwidth management method controls backup nodes to activate backup databases based on backup subnet information in data backup requests, and controls production nodes to deploy data synchronization tools within the same subnet as the production database based on data source subnet information in the data backup requests. It determines the target backup link based on the production database, data synchronization tools, and backup database, thus enabling the deployment of the backup database and data synchronization tools corresponding to the data backup request. This allows for the determination of the target backup link based on the deployed backup database and data synchronization tools, and subsequently, the provision of target bandwidth services based on the target backup link. Within the bandwidth limitations of the target bandwidth service, the source data generated by the production database is backed up to the backup database. This achieves data backup disaster recovery while reducing the impact of backup services on the network transmission quality of other network services, thereby improving the overall service quality of the system.

[0118] In one embodiment, such as Figure 9 and Figure 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 for illustration.

[0119] like Figure 2 As shown, 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, the data passes through the local gateway, cloud private line, private line gateway, and cloud gateway in sequence before finally being imported into the backup database. The cloud private line provides bandwidth limiting services, allowing users to specify a 5-tuple to limit the bandwidth of the network link identified by that 5-tuple.

[0120] Cloud dedicated lines limit the bandwidth of database backup links on disaster recovery platforms. This primarily includes the following functions:

[0121] (1) Configure backup link: When configuring database backup tasks on the disaster recovery platform, users can specify relevant parameters for backup rate limit.

[0122] Users configure database backup tasks on the disaster recovery platform and fill in the relevant parameters. The parameters related to rate limiting are explained below.

[0123] a. Data source subnet information: The subnet segment to which the production database belongs, represented 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: The maximum transmission speed of this backup link set by the user, in MB / s.

[0126] d. Bandwidth Package ID: The cloud private 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 limit value needs to be reduced; otherwise, the creation of the bandwidth limit will fail.

[0128] (2) Start Backup Rate Limiting: When starting a database backup task, a rate-limiting bandwidth is created based on the user-configured backup rate limiting parameters and the five-tuple information of the backup link. Specifically, as follows... Figure 9 As shown.

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

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

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

[0132] The target configuration information includes target 5-tuple information and target bandwidth rate limiting information. The target 5-tuple information includes source IP address information, source port information, destination IP address information, destination port information, and transport protocol information. The target bandwidth rate limiting information includes the bandwidth rate limit value and the bandwidth packet ID.

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

[0134] S910: The disaster recovery platform sends a creation command to the backup terminal, instructing the backup terminal to create a target bandwidth service for 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 command can be found in Table 1 above.

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

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

[0137] S916: The disaster recovery platform sends an update bandwidth command to the backup terminal, instructing the backup terminal to update the historical bandwidth limit value of a candidate bandwidth service to the target bandwidth limit value according to the update bandwidth command, and send the bandwidth identification information of the candidate bandwidth service to the disaster recovery platform as the target bandwidth identification information. Then, step S918 is executed.

[0138] S918: Records target bandwidth identification information.

[0139] (3) Update Backup Rate Limits: When a user modifies the rate limit parameters of the database backup link, or when the five-tuple changes, the disaster recovery platform can update the rate limit bandwidth. Specifically, as follows... Figure 10 As shown.

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

[0141] S1004: When the disaster recovery platform detects that a user has modified the bandwidth limit value of the target backup link and / or the synchronization port of the data synchronization tool has changed, it obtains the current configuration information of the target backup link and retrieves the target configuration information from the backup end based on the target bandwidth identification information.

[0142] The current configuration information includes the current 5-tuple information and the current bandwidth rate limit information. The current bandwidth rate limit information includes the current bandwidth rate limit value and the current bandwidth packet ID. The target configuration information includes the target 5-tuple information and the target bandwidth rate limit information. The target bandwidth rate limit information includes the target bandwidth rate limit value and the target bandwidth packet ID.

[0143] S1006: The disaster recovery platform determines whether the current quintuple information and the target quintuple information are the same. If yes, proceed to step S1008; otherwise, proceed to step S1010.

[0144] S1008: The disaster recovery platform determines whether the current bandwidth limit and the target bandwidth limit are the same. If yes, it returns to step S1002. If no, it proceeds to step S1012.

[0145] S1010: The disaster recovery platform sends a first adjustment instruction to the backup end, instructing the backup end to delete the corresponding target bandwidth service according to the target bandwidth identifier information in the first adjustment instruction, create the current bandwidth service according to the current configuration information in the first adjustment instruction, and send the current bandwidth identifier 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, instructing 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 limit value of the target bandwidth service according to the current bandwidth limit value in the second adjustment instruction.

[0147] The bandwidth management method provided in this application limits the cloud dedicated line bandwidth used during database backup, thus restricting the synchronization speed of the database backup link within a certain range. Even during peak periods of production database write operations, the traffic passing through the network link will not exceed the rate-limited bandwidth. This prevents excessive bandwidth consumption by the database backup task, which could negatively impact the network transmission quality of other services. Compared to the speed control functions of data synchronization tools, this application limits transmission speed at the network transport layer rather than the application layer, enabling more accurate control over the bandwidth used for data synchronization. Furthermore, when the rate-limiting parameters or 5-tuple of the backup link change, this method can adjust the rate-limited bandwidth accordingly. For example, it can delete invalid rate-limited bandwidth and reconfigure it, or synchronously update the rate-limited bandwidth, thereby ensuring that the speed limit remains effective.

[0148] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to 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. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0149] Based on the same inventive concept, this application also provides a bandwidth management device for implementing the bandwidth management method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more bandwidth management device embodiments provided below can be found in the limitations of the bandwidth management method described above, and will not be repeated here.

[0150] In one embodiment, such as Figure 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 a data backup request sent by a requesting end, determine the target backup link corresponding to the data backup request, and send a query request to the backup end; wherein the query request is used to query the bandwidth service of the cloud dedicated line in the backup link by the backup end, and the target backup link is used to transmit data generated by the production node of the requesting end to the backup node of the backup end for backup via the cloud dedicated line. The acquisition module 1102 is used to acquire 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; wherein the target bandwidth service is used to control the bandwidth of the target backup link transmitting data via the cloud dedicated line.

[0151] The bandwidth management device 1100 described above responds to a data backup request sent by the requesting end via a query module 1101, determines the target backup link corresponding to the data backup request, and sends a query request to the backup end. The acquisition module 1102 acquires the target configuration information of the target backup link and the query response sent by the backup end based on the query request. The management module 1103 manages the target bandwidth service of the target backup link based on the target configuration information and the query response. This allows for bandwidth limiting of the target backup link based on the target bandwidth service, achieving bandwidth restriction on the data backup link and preventing other network services sharing the cloud dedicated line with the data backup service from being affected, thus ensuring the stability and reliability of network transmission. This embodiment of the application, by limiting the cloud dedicated line bandwidth in the data backup link, compared to controlling data transmission speed using data synchronization tools (e.g., setting the number of parallel synchronization processes, the number of transmissions in a single batch, etc.), achieves transmission speed limitation at the network layer rather than the application layer. This allows for more accurate control of the bandwidth used for data synchronization and expands the scope of data bandwidth management. Furthermore, the bandwidth management method provided in this application can automatically adjust the management of the corresponding target bandwidth service based on the data backup request sent by the requesting end, thereby achieving adaptive management of different data backup links corresponding to different requesting ends and improving the effective control of bandwidth services.

[0152] In one embodiment, the management module is further configured to send a creation instruction to the backup end to instruct the backup end to create a target bandwidth service when the number of historical bandwidth services included in the query response is 0, and to obtain the target bandwidth identification information of the target bandwidth service sent by the backup end; wherein the creation instruction includes target configuration information; when the query response includes at least one historical bandwidth service, to obtain 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 to 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. The acquisition module is further configured to send a creation instruction to the backup end when the target tuple information and each historical tuple information are different, so as to instruct the backup end to create a target bandwidth service. The creation instruction includes target configuration information; and acquires the target bandwidth identification information sent by the backup end.

[0154] In one embodiment, the target configuration information includes target tuple information and target bandwidth rate limiting information, and the historical attribute information includes historical configuration information and historical bandwidth identification information. The historical configuration information includes historical tuple information and historical bandwidth rate limiting information. The acquisition module is further configured to determine candidate bandwidth services from each historical bandwidth service based on the target tuple information and each historical tuple information; and to determine the historical bandwidth identification information of the candidate bandwidth service as the target bandwidth identification information. 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 further configured to, upon detecting a change in the configuration information of the target backup link, obtain the corresponding target configuration information from the backup end based on the target bandwidth identification information, and obtain the current configuration information of the target backup link; if 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 rate limit information, and the current configuration information includes current tuple information and current bandwidth rate limit information. The management module is further configured to send a first adjustment instruction to the backup end when the target tuple information and the current tuple information are different, to instruct the backup end to delete the target bandwidth service according to the target bandwidth identification information, and to create the current bandwidth service of the target backup link according to the current configuration information, and to 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 terminal when the target tuple information and the current tuple information are the same, and the target bandwidth rate limit information and the current bandwidth rate limit information are different, so as to instruct the backup terminal to update the target bandwidth rate limit information of the target bandwidth service to the current bandwidth rate limit information; wherein, the second adjustment instruction includes the current bandwidth rate limit information and the target bandwidth identification information.

[0158] In one embodiment, the query module is further configured to control the backup node to activate the backup database based on the backup subnet information in the data backup request; control the production node to deploy a data synchronization tool within the same subnet of the production database based on the data source subnet information in the data backup request; and determine the target backup link based on the production database, the data synchronization tool, and the backup database. The target backup link represents the link from the production database through the data synchronization tool to the local gateway, and then through the cloud dedicated line, the dedicated line gateway, and the cloud gateway to the backup database.

[0159] Each module in the aforementioned bandwidth management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0160] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 12 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and databases. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a bandwidth management method.

[0161] Those skilled in the art will understand that Figure 12 The structure shown 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. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0162] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the aforementioned method.

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

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

[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, data stored, data displayed, 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 will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media 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), magnetic 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. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0167] The technical features of the above embodiments can be combined in any way. For the sake of brevity, 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 embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A bandwidth management method, characterized in that, The method includes: In response to a data backup request sent by the requesting end, the 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 cloud dedicated line in the backup link by the backup end, 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. Obtain the target configuration information of the target backup link and the query response sent by the backup end according to the query request; Based on the target configuration information and the query response, the target bandwidth service of the target backup link is managed; wherein, the target bandwidth service is used to control the bandwidth of the target backup link transmitting data through the cloud dedicated line; the management of the target bandwidth service of the target backup link based on the target configuration information and the query response includes: If the number of historical bandwidth services included in the query response is 0, a creation instruction is sent to the backup terminal to instruct the backup terminal to create the target bandwidth service, and the target bandwidth identification information of the target bandwidth service sent by the backup terminal is obtained; wherein, the creation instruction includes the target configuration information; If the query response includes at least one historical bandwidth service, the target bandwidth identification information of the target backup link is obtained based on the target configuration information and the historical attribute information of each of the historical bandwidth services. The target bandwidth service is managed based on the target bandwidth identification information.

2. The method according to claim 1, characterized in that, The target configuration information includes target tuple information, and the historical attribute information includes historical tuple information. The step of obtaining the target bandwidth identifier information of the target backup link based on the target configuration information and the historical attribute information of each historical bandwidth service includes: If the target tuple information and each of the historical tuple information are different, a creation instruction is sent to the backup terminal to instruct the backup terminal to create the target bandwidth service; wherein, the creation instruction includes the target configuration information; Obtain the target bandwidth identification information sent by the backup terminal.

3. The method according to claim 2, characterized in that, The target tuple information includes the source IP address information, source port information, destination IP address information, destination port information, and transmission protocol information of the target backup link.

4. The method according to claim 1, characterized in that, The target configuration information includes target tuple information and target bandwidth rate limiting information; the historical attribute information includes historical configuration information and historical bandwidth identifier information; the historical configuration information includes historical tuple information and historical bandwidth rate limiting information; wherein, obtaining the target bandwidth identifier information of the target backup link based on the target configuration information and the historical attribute information of each historical bandwidth service includes: Based on the target tuple information and each of the historical tuple information, candidate bandwidth services are determined from each of the historical bandwidth services; wherein the historical tuple information of the candidate bandwidth services 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 1-4, characterized in that, The management of the target bandwidth service based on the target bandwidth identification information includes: If a change in the configuration information of the target backup link is detected, the corresponding target configuration information is obtained from the backup end based on the target bandwidth identification information, and the current configuration information of the target backup link is also obtained. If the current configuration information and the target configuration information are different, an adjustment instruction is sent to the backup terminal to instruct the backup terminal 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 rate limit information, and the current configuration information includes current tuple information and current bandwidth rate limit information. The step of sending an adjustment command to the backup terminal when the current configuration information and the target configuration information differ includes: If 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; If the target tuple information and the current tuple information are the same, and the target bandwidth rate limit information and the current bandwidth rate limit information are different, a second adjustment instruction is sent to the backup terminal to instruct the backup terminal to update the target bandwidth rate limit information of the target bandwidth service to the current bandwidth rate limit information; wherein, the second adjustment instruction includes the current bandwidth rate limit information and the target bandwidth identification information.

7. The method according to any one of claims 1-4, characterized in that, The step of responding to a 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 includes: Based on the backup subnet information in the data backup request, control the backup node to activate the backup database; Based on the data source subnet information in the data backup request, control the production node to deploy a data synchronization tool within the same subnet of the production database; The target backup link is determined based on the production database, the data synchronization tool, and the backup database. The target backup link represents the link from the production database through the data synchronization tool to the local gateway, and then through the cloud dedicated line, the dedicated line gateway, and the cloud gateway to the backup database.

8. A bandwidth management device, characterized in that, The device includes: The query module is used to respond to a 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; wherein, the query request is used to query the bandwidth service of the cloud dedicated line in the backup link by the backup end, 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 is used to acquire 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 is used to manage the target bandwidth service of the target backup link based on 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; when the number of historical bandwidth services included in the query response is 0, a creation instruction is sent to the backup end to instruct the backup end to create the target bandwidth service, and the target bandwidth identification information of the target bandwidth service sent by the backup end is obtained; wherein the creation instruction includes the target configuration information; when the query response includes at least one historical bandwidth service, the target bandwidth identification information of the target backup link is obtained based on the target configuration information and the historical attribute information of each historical bandwidth service; and the target bandwidth service is managed based on the target bandwidth identification information.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

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

Images