Backup method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a backup method and device, computer equipment, a readable storage medium and a program product, the backup method and device are applied to a backup system, the backup system comprises three CPs and three UP pools, three disaster recovery groups are configured, each disaster recovery group takes one CP in the three CPs as a main CP and the other two CPs as standby CPs, the main CP in each disaster recovery group correspondingly bears one UP pool, and the UP pools are used for storing the UP pools. The method comprises the steps of receiving a master control switching request sent by at least one standby CP in a target disaster recovery backup group under the condition that a current master CP in the target disaster recovery backup group has a fault; the target disaster recovery unit is any one of the three disaster recovery units; determining a new main CP from the at least one standby CP according to the main control switching request; and sending a determination result to the new main CP, so that the new main CP bears the UP pool corresponding to the target disaster recovery unit. By adopting the method, the availability of the CP in a limit fault scene can be improved, and the reliability of user access is improved.

Description

Technical Field

[0001] The present application relates to the field of data communication technology, and in particular to a backup method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] vBRAS (virtual Broadband Remote Access Server) with separation of forwarding and control is an important service access network element in the metropolitan area network. vBRAS-CP (vBRAS Control Plane) is responsible for user access and centralized control; vBRAS-UP (vBRAS User Plane) is responsible for traffic forwarding.

[0003] The backup method in traditional scenarios is generally to configure two disaster recovery groups. Disaster recovery group 1 includes CP1 (primary) and CP2 (secondary), and disaster recovery group 1 manages UP pool 1; disaster recovery group 2 includes CP1 (secondary) and CP2 (primary), and disaster recovery group 2 manages UP pool 2. However, in this configuration mode, the reliability of CP is guaranteed by the 1:1 hot standby method in different computer rooms, and the primary and backup CPs are generally deployed in different core nodes. The number of users carried by CP is generally in the millions. If one CP fails and the other CP has problems, it will cause a large-scale network failure, and the reliability of user access is low. Summary of the invention

[0004] Based on this, it is necessary to provide a backup method, apparatus, computer equipment, computer-readable storage medium and computer program product to address the technical problems of the above method that easily cause large-scale network failures and low reliability of user access.

[0005] In a first aspect, the present application provides a backup method, which is applied to a backup system, wherein the backup system includes three CPs and three UP pools, and three disaster recovery groups are configured. Each disaster recovery group uses one of the three CPs as a main CP and the other two CPs as backup CPs. The main CP in each disaster recovery group corresponds to carrying a UP pool. The method includes:

[0006] In the event that the current master CP in the target disaster recovery group fails, receiving a master control switching request sent by at least one backup CP in the target disaster recovery group; the target disaster recovery group is any one of the three disaster recovery groups;

[0007] Determine a new master CP from the at least one standby CP according to the master control switching request;

[0008] The determination result is sent to the new primary CP, so that the new primary CP carries the UP pool corresponding to the target disaster recovery group.

[0009] In one embodiment, three user management virtual machines are deployed in each CP, and each user management virtual machine establishes a binding relationship with three UP pools respectively; each UP pool is actually carried by a user management virtual machine with a binding relationship in the main CP in the corresponding disaster recovery group;

[0010] The method further comprises:

[0011] Sending the determination result to the target user management virtual machine in the new primary CP, so that the target user management virtual machine carries the UP pool corresponding to the target disaster recovery group;

[0012] The target user management virtual machine is a user management virtual machine in the new primary CP that has a binding relationship with the UP pool corresponding to the target disaster recovery group.

[0013] In one embodiment, three CPs corresponding to each disaster recovery group are connected by heartbeat; the method further includes:

[0014] When at least one backup CP in the target disaster recovery group detects that the interruption duration of the heartbeat connection with the current primary CP exceeds a threshold, it is determined that the current primary CP is faulty.

[0015] In one embodiment, the method further comprises:

[0016] Upon receiving a master control switching request sent by two standby CPs in the target disaster recovery group, obtaining a current network status of each standby CP;

[0017] According to the current network status of each standby CP, a new master CP is determined from the two standby CPs.

[0018] In one embodiment, the method further comprises:

[0019] Obtain historical fault data of each backup CP;

[0020] A new master CP is determined from the two standby CPs according to the current network status and the historical fault data of each standby CP.

[0021] In one of the embodiments, the method is applied to an arbitration node in the backup system, and the arbitration node is IP-connected to the three UP pools and the three CPs.

[0022] In the second aspect, the present application also provides a backup device, which is applied to a backup system, wherein the backup system includes three CPs and three UP pools, and three disaster recovery groups are configured. Each disaster recovery group uses one of the three CPs as a main CP and the other two CPs as backup CPs. The main CP in each disaster recovery group corresponds to carrying a UP pool, and the device includes:

[0023] A receiving module, configured to receive a master control switching request sent by at least one backup CP in the target disaster recovery group when the current master CP in the target disaster recovery group fails; the target disaster recovery group is any one of the three disaster recovery groups;

[0024] A determination module, configured to determine a new master CP from the at least one standby CP according to the master control switching request;

[0025] The sending module is used to send the determination result to the new main CP, so that the new main CP carries the UP pool corresponding to the target disaster recovery group.

[0026] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0027] In the event that the current master CP in the target disaster recovery group fails, receiving a master control switching request sent by at least one backup CP in the target disaster recovery group; the target disaster recovery group is any one of the three disaster recovery groups;

[0028] Determine a new master CP from the at least one standby CP according to the master control switching request;

[0029] The determination result is sent to the new primary CP, so that the new primary CP carries the UP pool corresponding to the target disaster recovery group.

[0030] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0031] In the event that the current master CP in the target disaster recovery group fails, receiving a master control switching request sent by at least one backup CP in the target disaster recovery group; the target disaster recovery group is any one of the three disaster recovery groups;

[0032] Determine a new master CP from the at least one standby CP according to the master control switching request;

[0033] The determination result is sent to the new primary CP, so that the new primary CP carries the UP pool corresponding to the target disaster recovery group.

[0034] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0035] In the event that the current master CP in the target disaster recovery group fails, receiving a master control switching request sent by at least one backup CP in the target disaster recovery group; the target disaster recovery group is any one of the three disaster recovery groups;

[0036] Determine a new master CP from the at least one standby CP according to the master control switching request;

[0037] The determination result is sent to the new primary CP, so that the new primary CP carries the UP pool corresponding to the target disaster recovery group.

[0038] The above backup method, apparatus, computer equipment, storage medium and computer program product, when the current main CP in the target disaster recovery group fails, receives a master control switching request sent by at least one backup CP in the target disaster recovery group, wherein the target disaster recovery group is any one of the three disaster recovery groups; according to the master control switching request, a new main CP is determined from at least one backup CP, and the determination result is sent to the new main CP, so that the new main CP carries the UP pool corresponding to the target disaster recovery group. In the case of a failure of the current main CP in the target disaster recovery group, the method enables the available backup CP to send a master control switching request to select a new main CP, and even if two CPs fail, normal user access can be guaranteed, which greatly improves the availability of CPs in extreme failure scenarios and improves the reliability of user access. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 It is a structural schematic diagram of a backup method in the prior art;

[0040] Figure 2 A schematic diagram of a backup method in one embodiment;

[0041] Figure 3 A schematic diagram of the structure of the backup method improved by this application;

[0042] Figure 4 is a structural block diagram of a backup device in an embodiment;

[0043] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

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

[0045] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein.

[0046] vBRAS is an important service access network element in the metropolitan area network, including a control plane and a forwarding plane, and is deployed in a forwarding and control separation mode. The control plane is vBRAS Control Plane, referred to as CP; the forwarding plane is vBRAS User Plane, referred to as UP.

[0047] In traditional scenarios, the division and connection relationship of CP disaster recovery groups are as follows: Figure 1 As shown in the figure, two disaster recovery groups are configured. Disaster recovery group 1 includes CP1 (primary) and CP2 (secondary), and disaster recovery group 1 manages UP pool 1; disaster recovery group 2 includes CP1 (secondary) and CP2 (primary), and disaster recovery group 2 manages UP pool 2. In this configuration mode, each UP pool corresponds to only one disaster recovery group, that is, only one CP primary-backup relationship, ensuring that users of a single UP pool will not be scattered on different UPs, avoiding problems such as data fragmentation and difficulty in management. The backup CP backs up the user information of the primary CP in real time.

[0048] However, in this solution, the reliability of CP is guaranteed by the 1:1 hot standby method in different computer rooms, and the main and standby CPs are generally deployed in different core nodes. The number of users carried by CP is generally in the millions. Considering the problem of both core nodes failing (double CP failure) in extreme cases, all user data will be lost, and all users will need to dial back online, causing large-scale network failures and a wide range of failures.

[0049] Therefore, in order to reduce the impact of failures in extreme scenarios, this application proposes a control plane (CP) multi-active solution, which implements UP pool fault domain isolation and user load balancing by dividing the virtual machines within the control plane (CP), and combines data nodes and arbitration nodes to implement master-slave arbitration and data synchronization between CP nodes in the event of a failure, greatly improving user access reliability when dual data nodes (DC) fail in extreme scenarios.

[0050] In one embodiment, Figure 2As shown, a backup method is provided, which is applied to a backup system. The backup system includes three CPs and three UP pools, and three disaster recovery groups are configured. Each disaster recovery group uses one of the three CPs as the main CP and the other two CPs as backup CPs. The main CP in each disaster recovery group corresponds to carrying a UP pool. In this embodiment, the method includes the following steps:

[0051] Step S210: When the current master CP in the target disaster recovery group fails, a master control switching request sent by at least one backup CP in the target disaster recovery group is received.

[0052] The target disaster recovery group is any one of the three disaster recovery groups.

[0053] In a specific implementation, the backup system includes three CPs and three UP pools, which can form three disaster recovery groups. For each disaster recovery group, the three CPs are configured as a primary CP and two backup CPs, and each disaster recovery group carries a corresponding UP pool.

[0054] For example, suppose the three CPs are CP1, CP2 and CP3, and the three UP pools are UP pool 1, UP pool 2 and UP pool 3, then:

[0055] In disaster recovery group 1, CP1 is the primary, CP2 and CP3 are backups, and the primary CP1 takes over UP pool 1.

[0056] In disaster recovery group 2, CP2 is the primary, CP1 and CP3 are backups, and the primary CP 2 takes over UP pool 2.

[0057] In disaster recovery group 3, CP3 is the primary, CP1 and CP2 are backups, and the primary CP 3 takes over UP pool 3.

[0058] Under normal circumstances, the main CP1 in disaster recovery group 1 provides real-time hot backup of user data to backup CP2 and backup CP3 through the disaster recovery group channel. The main CP2 in disaster recovery group 2 provides real-time hot backup of user data to backup CP1 and backup CP2 through the disaster recovery group channel. The main CP3 in disaster recovery group 3 provides real-time hot backup of user data to backup CP1 and backup CP2 through the disaster recovery group channel.

[0059] In each disaster recovery group, each CP can monitor each other's status. When the backup CP in any disaster recovery group detects a failure in the main CP, it can send a master control switch request to the arbitration node of the backup system, so that the arbitration node can arbitrate and determine a new main CP. For example, in CP disaster recovery group 1, backup CP2 and backup CP3 detect that the main CP has failed, and will send a master control switch request to the arbitration node of the backup system.

[0060] Step S220: According to the master control switching request, a new master CP is determined from at least one backup CP.

[0061] In a specific implementation, after receiving a master control switching request sent by at least one backup CP, the arbitration node of the backup system can determine a new master CP from at least one backup CP according to a preset rule, or arbitrarily select a backup CP as the new master CP.

[0062] It can be understood that in some embodiments, when both the main CP and a backup CP in the target disaster recovery group fail, the arbitration node will receive a master control switching request sent by a backup CP. In this case, the backup CP can be directly determined as the new main CP. That is to say, when two CPs fail, the other CP is directly determined as the main CP to take over all users of the corresponding UP pool.

[0063] Step S230: Send the determination result to the new primary CP, so that the new primary CP carries the UP pool corresponding to the target disaster recovery group.

[0064] In a specific implementation, after a new primary CP is determined, the determination result may be sent to the new primary CP to notify the new primary CP to perform a primary-backup switch to carry users of the UP pool corresponding to the target disaster recovery group.

[0065] In the above backup method, when the current main CP in the target disaster recovery group fails, a master control switching request sent by at least one backup CP in the target disaster recovery group is received, wherein the target disaster recovery group is any one of the three disaster recovery groups; according to the master control switching request, a new main CP is determined from at least one backup CP, and the determination result is sent to the new main CP, so that the new main CP carries the UP pool corresponding to the target disaster recovery group. In the case of a failure of the current main CP in the target disaster recovery group, this method enables the available backup CP to send a master control switching request to select a new main CP, and even if two CPs fail, normal user access can be guaranteed, which greatly improves the availability of CPs in extreme failure scenarios and improves the reliability of user access.

[0066] In an exemplary embodiment, three user management virtual machines are deployed in each CP, and each user management virtual machine establishes a binding relationship with three UP pools respectively; each UP pool is actually carried by a user management virtual machine with a binding relationship in the main CP in the corresponding disaster recovery group.

[0067] The method also includes: sending the determination result to the target user management virtual machine in the new main CP so that the target user management virtual machine carries the UP pool corresponding to the target disaster recovery group; the target user management virtual machine is a user management virtual machine in the new main CP that has a binding relationship with the UP pool corresponding to the target disaster recovery group.

[0068] In some embodiments, each user virtual hypervisor is configured as one primary and one secondary.

[0069] Specifically, if Figure 3 As shown, three user management virtual machines are deployed in each CP, and each user management virtual machine establishes a binding relationship with three UP pools. It should be noted that establishing a binding relationship does not mean that actual load is carried out. The role of the binding relationship is to determine which user management virtual machine to select for actual load when performing active-standby switching. When used as a standby CP, even if there is a binding relationship, the UP pool is not actually carried. In other words, the actual load is that each UP pool is executed by the user management virtual machine with a binding relationship in the primary CP in the corresponding disaster recovery group.

[0070] For example, assume that in each CP, user management virtual machine 1, user management virtual machine 2, and user management virtual machine 3 are bound to UP pool 1, UP pool 2, and UP pool 3 respectively, then:

[0071] CP1 in disaster recovery group 1 is the primary one, and virtual machine 1 in primary CP1 carries users of UP pool 1.

[0072] CP2 in disaster recovery group 2 is the primary one, and virtual machine 2 in primary CP 2 carries users of UP pool 2.

[0073] CP3 in disaster recovery group 3 is the master, and virtual machine 3 in master CP 3 carries users of UP pool 3.

[0074] When the main CP1 in disaster recovery group 1 fails and the standby CP2 switches to the main CP, the virtual machine 1 in the new main CP2 will carry the users of UP pool 1. When the main CP3 in disaster recovery group 3 fails and the standby CP1 switches to the main CP, the virtual machine 3 in the new main CP1 will carry the users of UP pool 3. In other words, the three virtual machines in each CP have a one-to-one binding relationship with the three UP pools. If the CP is the main CP of a disaster recovery group, the corresponding virtual machine will be used to carry the corresponding UP pool. For example, if it is the main CP of disaster recovery group 1, virtual machine 1 will be used to carry UP pool 1; if it is the main CP of disaster recovery group 2, virtual machine 2 will be used to carry UP pool 2; if it is the main CP of disaster recovery group 3, virtual machine 3 will be used to carry UP pool 3.

[0075] Therefore, the determination result of the master CP is sent to the new master CP, and a target user management virtual machine having a binding relationship with the UP pool corresponding to the target disaster recovery group is established, so that the target user management virtual machine carries the UP pool corresponding to the target disaster recovery group.

[0076] In this embodiment, three user management virtual machines are deployed in each CP, and each user management virtual machine establishes a binding relationship with three UP pools respectively; each UP pool is actually carried by the user management virtual machine with a binding relationship in the main CP in the corresponding disaster recovery group. By dividing the virtual machines in the control plane (CP), the UP pool fault domain isolation can be achieved, thereby limiting the scope of the fault domain when a fault occurs, and improving the utilization rate of each CP, achieving the effect of user load balancing.

[0077] In an exemplary embodiment, the three CPs corresponding to each disaster recovery group are heartbeat connected; the method also includes: when at least one backup CP in the target disaster recovery group detects that the interruption duration of the heartbeat connection with the current main CP exceeds a threshold, determining that the current main CP is faulty.

[0078] In the specific implementation, Figure 3 As shown in the figure, a heartbeat connection is established between each CP for real-time synchronization of the CP working status. When the backup CP detects that the interruption time of the heartbeat connection with the current main CP exceeds the threshold, it can be determined that the current main CP is faulty, and a master control switching request is sent to the arbitration node of the backup system, and the arbitration node determines that the backup CP is promoted to the main CP.

[0079] In this embodiment, a heartbeat connection is established between each CP, and heartbeat signals are sent regularly to ensure that their respective working states are synchronized with each other. This method can provide timely feedback on the online status of the CP; through timely fault detection and automatic switching, it can be ensured that the system can still maintain normal operation in the event of a main CP failure, thereby improving the reliability of user access.

[0080] In an exemplary embodiment, the method further includes: upon receiving a master control switching request sent by two backup CPs in the target disaster recovery group, obtaining the current network status of each backup CP; and determining a new master CP from the two backup CPs according to the current network status of each backup CP.

[0081] In a specific implementation, when the received master control switching request includes master control switching requests of two standby CPs, it is necessary to select from the two standby CPs, and the specific selection basis can be the current network status of each standby CP. The current network status may include the status of multiple evaluation indicators, such as the current network link status, CPU status, etc. The network link status may include connectivity with other network devices, bandwidth utilization, packet loss rate, etc.; the CPU status may include CPU usage, load conditions, etc.

[0082] Specifically, by assigning weights to each evaluation indicator and weighting the scores of each evaluation indicator, a score for each backup CP can be obtained, and the backup CP with the highest score can be selected as the new main CP.

[0083] In this embodiment, the status of multiple backup CPs is evaluated through the network status, so as to select the main CP, which can reduce the risk of secondary failure caused by improper selection, reduce the possibility of users being affected, and improve the security and stability of the system.

[0084] In an exemplary embodiment, the method further includes: acquiring historical fault data of each standby CP; and determining a new master CP from two standby CPs according to the current network status and historical fault data of each standby CP.

[0085] In a specific implementation, when selecting the master CP from two standby CPs, in addition to the current network status of the two standby CPs, the historical fault data of the two standby CPs may also be considered. The historical fault data may include the running time, the number of faults, the fault recovery time, etc. The new master CP is selected in combination with the current network status and the historical fault data.

[0086] Specifically, the stability score of each backup CP can be determined based on historical fault data, and the performance score of each backup CP can be determined based on the current network status. The total score of each backup CP is obtained based on the weighted sum of the stability score and the performance score, and the backup CP with a higher total score is selected as the new main CP.

[0087] In this embodiment, by combining the current network status and historical fault data, the reliability and performance of the backup CP can be evaluated more comprehensively, thereby improving the accuracy of selecting a new primary CP.

[0088] In one embodiment, the present application proposes a control plane (CP) multi-active solution, which consists of three CPs forming a CP multi-active backup group, and each CP contains a data node. An arbitration node is configured in the CP multi-active backup group. During normal operation, the data is carried to different CPs with the UP pool as the granularity. Three user management virtual machines are deployed in each CP, and each user management virtual machine corresponds to a UP pool. Under normal circumstances, UP pool 1 establishes inter-CU channel connections with the three CPs, and UP pool 1 is managed by different user management virtual machines in the three CPs respectively, and decides on which CP's user management virtual machine to carry it based on the initial device configuration. At the same time, the arbitration node is used to determine the master-slave status of the CP in the multi-active backup group in real time. The data node in each CP ensures that the user data copy on the backup CP is consistent with the primary CP.

[0089] The arbitration node is connected to the three UP pools and three CPs using IP connections, and the underlying network IP is reachable. When the user management virtual machine of the primary CP in the multi-active backup group fails, the user management virtual machine of the standby CP issues a request to the arbitration node to upgrade to the primary. The arbitration node makes a decision on upgrading based on the current network link status, CPU status and other information of the standby CP, and returns the decision result to the user management virtual machine of the standby CP. The user management virtual machine in the standby CP is re-managed in the UP pool based on the decision result.

[0090] In order to facilitate those skilled in the art to understand the embodiments of the present application, Figure 3 The example of Figure 3 As shown in the figure, there are 3 CPs and 3 UP pools. Each CP contains 3 user-managed virtual machines (usually, the virtual machines themselves are one active and one standby). UP pool 1 belongs to disaster recovery group 1, and corresponds to virtual machine 1 of disaster recovery group 1, CP1 is the active device, and CP2 / CP3 are the standby devices; UP pool 2 belongs to disaster recovery group 2, and corresponds to virtual machine 2 of disaster recovery group 2, CP2 is the active device, and CP1 / CP3 are the standby devices; UP pool 3 belongs to disaster recovery group 3, and corresponds to virtual machine 3 of disaster recovery group 3, CP3 is the active device, and CP1 / CP2 are the standby devices.

[0091] Take UP pool 1 as an example: all UPs and three CPs in the pool establish CU channels, which are used to transmit control information and user information between CUs. Disaster recovery channels are established between CPs, and the backup CP synchronizes user information from the main CP in real time through the disaster recovery channel. At this time, the data copies in the user data nodes in the three CPs remain consistent. CP2 / CP3, as the disaster recovery of CP1, establishes a disaster recovery group connection with CP1 (the disaster recovery group connection in different disaster recovery groups is different, and the disaster recovery group connection requires the specified peer device IP). Heartbeat channels are configured between CPs to establish heartbeat connections and perform heartbeat detection for real-time synchronization of CP working status. When the heartbeat connections between the main CP and the two backup CPs are interrupted and timed out, the third-party arbitration node decides that the backup CP will be promoted to the main CP.

[0092] In the case of a failure of the primary CP in disaster recovery group 1 (single CP failure scenario), standby CP2 and standby CP3 detect that the heartbeat connection with the primary CP1 is interrupted, and determine that the primary CP has failed. The arbitration node determines that standby CP2 or standby CP3 will switch to the new primary CP (assuming that standby CP2 becomes the primary).

[0093] Assume that after CP2 is promoted to the main CP, CP2 also fails (double CP failure scenario), the third set of CP3 is directly promoted to the main CP, and the users of UP pool 1 carried by CP2 are switched to virtual machine 1 of CP3 to protect users from loss.

[0094] The solution proposed in this application has the following advantages: (1) ensuring balanced load distribution of users within the multi-active backup group and improving the utilization rate of each CP; (2) improving the availability of CP in extreme fault scenarios and coping with dual CP failures and dual DC (data node) power outage scenarios; (3) limiting the scope of the fault domain when a fault occurs.

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

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

[0097] In one embodiment, Figure 4 As shown, a backup device is provided, which is applied to a backup system. The backup system includes three CPs and three UP pools, and three disaster recovery groups are configured. Each disaster recovery group uses one CP of the three CPs as a main CP and the other two CPs as backup CPs. The main CP in each disaster recovery group carries a UP pool, including: a receiving module 410, a determining module 420 and a sending module 430, wherein:

[0098] The receiving module 410 is used to receive a master control switching request sent by at least one backup CP in the target disaster recovery group when the current master CP in the target disaster recovery group fails; the target disaster recovery group is any one of the three disaster recovery groups;

[0099] A determination module 420, configured to determine a new master CP from at least one backup CP according to a master control switching request;

[0100] The sending module 430 is used to send the determination result to the new primary CP, so that the new primary CP carries the UP pool corresponding to the target disaster recovery group.

[0101] In one of the embodiments, three user management virtual machines are deployed in each CP, and each user management virtual machine establishes a binding relationship with three UP pools respectively; each UP pool is actually carried by a user management virtual machine with a binding relationship in the main CP in the corresponding disaster recovery group; the sending module 430 is also used to send the determination result to the target user management virtual machine in the new main CP, so that the target user management virtual machine carries the UP pool corresponding to the target disaster recovery group; the target user management virtual machine is a user management virtual machine in the new main CP that establishes a binding relationship with the UP pool corresponding to the target disaster recovery group.

[0102] In one of the embodiments, a heartbeat connection is established between the three CPs corresponding to each disaster recovery group; the device further includes a detection module for determining that the current main CP is faulty when at least one backup CP in the target disaster recovery group detects that the interruption duration of the heartbeat connection with the current main CP exceeds a threshold.

[0103] In one embodiment, the determination module 420 is further used to obtain the current network status of each backup CP when receiving a master control switching request sent by two backup CPs in the target disaster recovery group; and determine a new master CP from the two backup CPs according to the current network status of each backup CP.

[0104] In one embodiment, the determination module 420 is further configured to obtain historical fault data of each standby CP; and determine a new master CP from two standby CPs according to the current network status and historical fault data of each standby CP.

[0105] In one of the embodiments, the device is applied to an arbitration node in a backup system, and the arbitration node is IP-connected to three UP pools and three CPs.

[0106] Each module in the above backup 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 operations corresponding to each module.

[0107] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 5As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device 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 and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a backup method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a key, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse, etc.

[0108] Those skilled in the art will understand that Figure 5 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.

[0109] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0110] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0111] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0112] 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, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

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

[0114] The technical features of the above embodiments may be combined arbitrarily. 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.

[0115] 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 backup method, characterized in that: Applied to a backup system, the backup system includes three CPs and three UP pools, and three disaster recovery groups are configured. Each disaster recovery group uses one of the three CPs as a main CP and the other two CPs as backup CPs. The main CP in each disaster recovery group carries a UP pool. The method includes: In the event that the current master CP in the target disaster recovery group fails, receiving a master control switching request sent by at least one backup CP in the target disaster recovery group; the target disaster recovery group is any one of the three disaster recovery groups; Determine a new master CP from the at least one standby CP according to the master control switching request; The determination result is sent to the new primary CP, so that the new primary CP carries the UP pool corresponding to the target disaster recovery group.

2. The method according to claim 1, characterized in that Three user management virtual machines are deployed in each CP, and each user management virtual machine establishes a binding relationship with the three UP pools respectively; each UP pool is actually carried by a user management virtual machine with a binding relationship in the main CP in the corresponding disaster recovery group; The method further comprises: Sending the determination result to the target user management virtual machine in the new primary CP, so that the target user management virtual machine carries the UP pool corresponding to the target disaster recovery group; The target user management virtual machine is a user management virtual machine in the new primary CP that has a binding relationship with the UP pool corresponding to the target disaster recovery group.

3. The method according to claim 1, characterized in that A heartbeat connection is established between the three CPs corresponding to each disaster recovery group; the method further comprises: When at least one backup CP in the target disaster recovery group detects that the interruption duration of the heartbeat connection with the current primary CP exceeds a threshold, it is determined that the current primary CP is faulty.

4. The method according to claim 1, characterized in that: The method further comprises: Upon receiving a master control switching request sent by two standby CPs in the target disaster recovery group, obtaining a current network status of each standby CP; According to the current network status of each of the standby CPs, a new master CP is determined from the two standby CPs.

5. The method according to claim 4, characterized in that The method further comprises: Obtain historical fault data of each backup CP; The new master CP is determined from the two standby CPs according to the current network status and the historical fault data of each standby CP.

6. The method according to any one of claims 1 to 5, characterized in that: The method is applied to an arbitration node in the backup system, and the arbitration node is connected to the three UP pools and the three CPs through IP.

7. A backup device, characterized in that: Applied to a backup system, the backup system includes three CPs and three UP pools, and three disaster recovery groups are configured. Each disaster recovery group uses one of the three CPs as a main CP and the other two CPs as backup CPs. The main CP in each disaster recovery group carries a UP pool. The device includes: A receiving module, configured to receive a master control switching request sent by at least one backup CP in the target disaster recovery group when the current master CP in the target disaster recovery group fails; the target disaster recovery group is any one of the three disaster recovery groups; A determination module, configured to determine a new master CP from the at least one standby CP according to the master control switching request; The sending module is used to send the determination result to the new main CP, so that the new main CP carries the UP pool corresponding to the target disaster recovery group.

8. 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 backup method according to any one of claims 1 to 6 are implemented.

9. 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 backup method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the backup method according to any one of claims 1 to 6 are implemented.

Images