CN114095342B

CN114095342B - Backup realization method and device

Info

Publication number: CN114095342B
Application number: CN202111228742.6A
Authority: CN
Inventors: 盛朋朋; 许豫飞
Original assignee: New H3C Big Data Technologies Co Ltd
Current assignee: New H3C Big Data Technologies Co Ltd
Priority date: 2021-10-21
Filing date: 2021-10-21
Publication date: 2023-12-26
Anticipated expiration: 2041-10-21
Also published as: CN114095342A

Abstract

The application provides a backup realization method and device, wherein the method is applied to a first CP, and comprises the following steps: when a plurality of second CPs fail or a link between each second CP and UP indicated by UP identification in a main CP disaster recovery group fails, acquiring a group identification of a disaster recovery channel group bound with the address of each second CP according to the address of each second CP; according to the group identification of the disaster recovery channel group, determining the backup type provided for each second CP and the group identification of the backup CP disaster recovery group bound with the group identification of the disaster recovery channel group; and taking over the backup CP disaster backup group corresponding to the group identifier of the backup CP disaster backup group according to the backup type, and providing business service for UP corresponding to at least one UP identifier included in the backup CP disaster backup group.

Description

Backup realization method and device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a backup implementation method and apparatus.

Background

At present, when facing the irresistible force of earthquakes, fires and the like, local data backup cannot ensure that backup data is not lost, and the requirements of operators on high availability, real-time performance and safety of a service system cannot be met. In order to cope with the above situation and reduce enterprise loss, the industry proposes a technical idea of disaster recovery in different places.

The CP disaster recovery is a remote disaster recovery technology applied to the vBRAS forwarding and control separation networking. In a Data Center (English: data Center, abbreviated as DC) with multiple CPs at different address positions, dual-machine backup is performed through the CPs so as to realize remote disaster recovery, so that when one DC fails or disasters occur, the other DC can rapidly take over user service.

In the vbas forwarding and control separation networking, the existing CP disaster recovery mode includes a 1:1 backup type and a 1+1 backup type.

Under the 1:1 backup type, the main CP is the current working CP, and the standby CP is used for backup. The implementation process is specifically as follows: and creating a CP disaster recovery backup group in each of the two CPs which are the main and backup. And creating a main CP disaster recovery backup group in the main CP, and creating a backup CP disaster recovery backup group in the backup CP, wherein the UP range of the management of the main and backup CP disaster recovery backup groups is consistent. When the primary CP fails, the primary CP disaster recovery group cannot continue to provide service for the user service on the UP. At this time, the backup CP takes over the work of the primary CP, and starts the user service on the backup CP disaster backup group connection pipe UP.

Under the 1+1 backup type, the primary and backup CPs are all current working CPs. The implementation process is specifically as follows: two CP disaster recovery backup groups are respectively created in the primary and backup CPs. The same-name CP disaster recovery backup groups in the main and backup CPs are respectively used as a main CP disaster recovery backup group and a backup CP disaster recovery backup group, the UP ranges managed by the main and backup CP disaster recovery backup groups are consistent, and the main and backup states of different CP disaster recovery backup groups in the same CP are different. For example, a main CP in DC1 creates a main CP disaster recovery group a and a backup CP disaster recovery group B, where UP ranges managed by the main CP disaster recovery group a are UP1 and UP2, and UP ranges managed by the backup CP disaster recovery group B are UP3 and UP4; similarly, the backup CP in the DC2 creates a backup CP disaster recovery group a and a primary CP disaster recovery group B, the UP ranges managed by the backup CP disaster recovery group a are UP1 and UP2, and the UP ranges managed by the primary CP disaster recovery group B are UP3 and UP4. At the same time, different CPs manage user services on the UP part, so that the service pressure of a single point is reduced, and the utilization rate of network equipment is improved.

The two backup types are that the CP equipment in one DC only provides backup service for the CP equipment in the other DC at the same time, and the equipment resource utilization rate of the DC where the backup CP is located is low.

Disclosure of Invention

In view of this, the present application provides a method and apparatus for implementing backup, which are used to solve the problem that in the existing two backup types, the device resource utilization rate of the DC where the backup CP is located is low.

In a first aspect, the present application provides a backup implementation method, where the method is applied to a first CP, where the first CP is in a first DC, where the first CP includes at least one backup CP disaster recovery group, each backup CP disaster recovery group includes at least one UP identifier that is the same as one primary CP disaster recovery group, where the primary CP disaster recovery group is in a second CP, and where the second CP is in a second DC, where the method includes:

when a plurality of second CPs fail or a link between each second CP and UP indicated by UP identification in a main CP disaster recovery group fails, acquiring a group identification of a disaster recovery channel group bound with the address of each second CP according to the address of each second CP;

according to the group identification of the disaster recovery channel group, determining the backup type provided for each second CP and the group identification of the backup CP disaster recovery group bound with the group identification of the disaster recovery channel group;

And taking over the backup CP disaster recovery backup group corresponding to the group identifier of the backup CP disaster recovery backup group according to the backup type, and providing business service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group.

In a second aspect, the present application provides a backup implementation method, where the method is applied to a first CP, where the first CP is in a first DC, where the first CP includes a primary CP disaster recovery group, where the primary CP disaster recovery group and a backup CP disaster recovery group each include the same at least one UP identifier, where the backup CP disaster recovery group is in a second CP, and where the second CP is in a second DC, where the method includes:

generating a heartbeat message, wherein the heartbeat message comprises the working state of the first CP or a first link failure rate between the first CP and UP indicated by UP identification in a main CP disaster recovery group;

and sending the heartbeat message to a second CP through a heartbeat channel, so that the second CP takes over the standby CP disaster recovery group and provides service for UP corresponding to at least one UP identifier included in the standby CP disaster recovery group when determining the first CP fault or the link fault between the first CP and UP indicated by the UP identifier in the main CP disaster recovery group according to the working state or the first link fault rate.

In a third aspect, the present application provides an implementation apparatus for backup, where the apparatus is applied to a first CP, where the first CP is in a first DC, where the first CP includes at least one backup CP disaster recovery group, where each backup CP disaster recovery group includes at least one UP identifier that is the same as one primary CP disaster recovery group, where the primary CP disaster recovery group is in a second CP, and where the second CP is in a second DC, where the apparatus includes:

an obtaining unit, configured to obtain, according to an address of each second CP, a group identifier of a disaster recovery channel group bound to the address of each second CP when a plurality of second CPs fail or a link between each second CP and a UP indicated by the UP identifier in the master CP disaster recovery group fails;

the determining unit is used for determining the backup type provided for each second CP and the group identifier of the backup CP disaster recovery group bound with the group identifier of the disaster recovery channel group according to the group identifier of the disaster recovery channel group;

and the take-over unit is used for taking over the backup CP disaster recovery backup group corresponding to the group identifier of the backup CP disaster recovery backup group according to the backup type and providing business service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group.

In a fourth aspect, the present application provides a backup implementation apparatus, where the apparatus is applied to a first CP, where the first CP is in a first DC, where the first CP includes a primary CP disaster recovery group, where the primary CP disaster recovery group and a backup CP disaster recovery group each include the same at least one UP identifier, where the backup CP disaster recovery group is in a second CP, where the second CP is in a second DC, and the apparatus includes:

The generating unit is used for generating a heartbeat message, wherein the heartbeat message comprises the working state of the first CP or a first link failure rate between the first CP and UP indicated by UP identification in the main CP disaster recovery group;

and the sending unit is used for sending the heartbeat message to a second CP through a heartbeat channel, so that the second CP takes over the standby CP disaster recovery group and provides service for UP corresponding to at least one UP identifier included in the standby CP disaster recovery group when determining the first CP fault or the link fault between the first CP and UP indicated by the UP identifier in the main CP disaster recovery group according to the working state or the first link fault rate.

In a fifth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided in the first aspect of the present application.

In a sixth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided in the second aspect of the present application.

Therefore, by applying the backup realization method and device provided by the application, when a plurality of second CPs fail or a link between each second CP and UP indicated by UP identification in a main CP disaster recovery group fails, the first CP acquires the group identification of the disaster recovery channel group bound with the address of each second CP according to the address of each second CP; according to the group identification of the disaster recovery channel group, the first CP determines the backup type provided for each second CP and the backup CP disaster backup group bound with the group identification of the disaster recovery channel group; and according to the backup type, the first CP takes over the backup CP disaster recovery backup group and provides business service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group.

In this way, it is achieved that CPs within one DC can provide backup services for CPs within N DCs at different geographical locations simultaneously. The method solves the problems that in the existing 1:1 backup type and 1+1 backup type, the CP in one DC can only provide backup service for the CP in the other DC at the same time, and the equipment resource utilization rate of the DC where the backup CP is located is lower.

Drawings

Fig. 1 is a flowchart of a backup implementation method provided in an embodiment of the present application;

FIG. 2 is a flowchart of another backup implementation method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a backup networking of N:1 when a plurality of primary CPs provided in the embodiment of the present application work normally;

FIG. 4 is a schematic diagram of N:1 backup networking when multiple primary CPs fail according to an embodiment of the present application;

fig. 5 is a block diagram of a backup implementation device according to an embodiment of the present application;

FIG. 6 is a block diagram of another backup implementation device according to an embodiment of the present application;

fig. 7 is a hardware structure of a network device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the corresponding listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The following describes in detail a backup implementation method provided in the embodiment of the present application. Referring to fig. 1, fig. 1 is a flowchart of a backup implementation method provided in an embodiment of the present application. The method is applied to the first CP. The implementation method of backup provided by the embodiment of the application may include the following steps.

And 110, when a plurality of second CPs fail or a link between each second CP and UP indicated by UP identification in the main CP disaster recovery backup group fails, acquiring a group identification of a disaster recovery channel group bound with the address of each second CP according to the address of each second CP.

Specifically, in the n:1 backup networking, a plurality of CPs that are primary and backup to each other are included, and each CP is in one DC. For example, the first CP is located within the first DCs, and all other DCs except the first DC are collectively referred to as second DCs, each of which includes one second CP therein. It is understood that the second DC may include a third DC, a fourth DC, etc., and the second CP includes a third CP, a fourth CP, etc.

In the embodiment of the application, the multiple CPs are divided into master and backup roles in advance according to the backup type. For example, if the backup type is a 1:1 backup type, the first CP is configured as a backup CP, the plurality of second CPs are configured as a primary CP, and the first CP provides backup services for the plurality of second CPs at the same time. If the backup type is 1+1, the first CPs are configured as the main CPs and the standby CPs at the same time, and the plurality of second CPs are configured as the standby CPs and the main CPs. The first CP may notify to support a 1:1 backup type and a 1+1 backup type.

And configuring a main CP disaster recovery backup group in the main CP, configuring a backup CP disaster recovery backup group in the backup CP, wherein the disaster recovery backup groups which are the main and backup each other comprise the same at least one UP identifier.

When a plurality of second CPs fail or a link between each second CP and UP indicated by UP identification in a main CP disaster recovery backup group fails, the first CP locally acquires the group identification of the disaster recovery channel group bound with the address of each second CP according to the address (specifically, IP address) of each second CP.

Further, before executing the step, the method further comprises a process that the second CP and the first CP respectively receive a plurality of configuration instructions input by a user, and a process that the second CP and the first CP respectively establish disaster recovery channels with opposite ends, configure a CP disaster recovery group locally and bind group identifiers of the disaster recovery channel group with group identifiers of the CP disaster recovery group through the plurality of configuration instructions.

The following description will take the second CP and the third CP as examples:

the second CP receives a first configuration instruction input by a user, wherein the first configuration instruction comprises a first group of parameters for configuring the disaster recovery channel group, the first group of parameters comprise a group identifier of the disaster recovery channel group and an address parameter, and the address parameter comprises an IP address of the second CP and an IP address of the first CP.

And establishing a disaster recovery channel by the second CP and the first CP according to the IP address of the first CP, and binding the group identification of the disaster recovery channel group with the established disaster recovery channel. The disaster recovery channel comprises a heartbeat channel, a plurality of data backup channels and a disaster recovery protection channel. The process of establishing the disaster recovery channel is the same as that of the existing active-standby CP, and will not be repeated here.

In one example, the group identifier of the disaster recovery channel group included in the first configuration instruction is disaster recovery channel group 1, and the address parameter includes an IP address of the first CP and an IP address of the second CP. According to the address parameters, the second CP and the first CP establish a disaster recovery channel 1, wherein the address of one end of the disaster recovery channel 1 is the IP address of the second CP, and the address of the other end is the IP address of the first CP. The disaster recovery channel 1 is bound with the disaster recovery channel group 1.

The third CP receives a first configuration instruction input by a user, wherein the first configuration instruction comprises a first group of parameters for configuring the disaster recovery channel group, the first group of parameters comprise a group identifier of the disaster recovery channel group and an address parameter, and the address parameter comprises an IP address of the third CP and an IP address of the first CP.

And establishing a disaster recovery channel by the third CP and the first CP according to the IP address of the first CP, and binding the group identification of the disaster recovery channel group with the established disaster recovery channel. The disaster recovery channel comprises a heartbeat channel, a plurality of data backup channels and a disaster recovery protection channel. The process of establishing the disaster recovery channel is the same as that of the existing active-standby CP, and will not be repeated here.

In one example, the group identifier of the disaster recovery channel group included in the first configuration instruction is disaster recovery channel group 2, and the address parameter includes an IP address of the first CP and an IP address of the third CP. According to the address parameters, the third CP and the first CP establish a disaster recovery channel 2, wherein the address of one end of the disaster recovery channel 2 is the IP address of the third CP, and the address of the other end is the IP address of the first CP. The disaster recovery channel 2 is bound with the disaster recovery channel group 2.

And the second CP receives a second configuration instruction input by the user again, wherein the second configuration instruction comprises a second group of parameters for configuring the CP disaster recovery group, and the second group of parameters comprise the name, the group identifier, the role and the UP identifier of the standby pipe of the CP disaster recovery group.

And configuring the CP disaster recovery group on the second CP according to the name, the group identifier and the role of the CP disaster recovery group, wherein the CP disaster recovery group has the name, the group identifier and the role, and the CP disaster recovery group comprises the UP identifier of the waiting management.

In one example, the second CP configures a primary CP disaster recovery group on the second CP according to the name, group identification, role of the CP disaster recovery group. For example, the primary CP disaster recovery group is named group1 and the group identification is group-id1.

And the third CP receives a second configuration instruction input by the user again, wherein the second configuration instruction comprises a backup type and a second group of parameters for configuring the CP disaster recovery group, and the second group of parameters comprise the name, the group identifier, the role and the UP identifier of the standby management.

And configuring a plurality of CP disaster recovery groups on a third CP according to the backup type, the names of the CP disaster recovery groups, the group identifications and the roles, wherein the CP disaster recovery groups have the names, the group identifications and the roles, and the CP disaster recovery groups comprise UP identifications to be managed.

In one example, if the backup type is 1+1, configuring two CP disaster recovery groups on a third CP, where one CP disaster recovery group is named group2, the group identifier is group-id2, and the role is the primary CP disaster recovery group; the other CP disaster recovery group is named group3, the group identifier is group-id3, and the role is the backup CP disaster recovery group.

And the second CP receives a third configuration instruction input by the user again, wherein the third configuration instruction comprises the group identification of the disaster recovery channel group and the group identification of the CP disaster recovery group.

And the second CP carries out binding processing on the group identifier of the disaster recovery channel group and the group identifier of the CP disaster recovery backup group.

In one example, the second CP binds disaster recovery channel group1 with group identification group1 of the primary CP disaster recovery group.

And the third CP receives a third configuration instruction input by the user again, wherein the third configuration instruction comprises the group identification of the disaster recovery channel group and the group identification of the CP disaster recovery group.

And the third CP carries out binding processing on the group identification of the disaster recovery channel group and the group identifications of the created plurality of CP disaster recovery backup groups.

In one example, if the backup type is 1+1, the third CP binds the disaster recovery channel group2 with the group identifier group2 of the primary CP disaster recovery group and the group identifier group3 of the backup CP disaster recovery group, respectively.

The following description will take the first CP as an example:

the first CP receives a plurality of first configuration instructions input by a user, wherein each first configuration instruction comprises a first group of parameters for configuring a disaster recovery channel group, each first group of parameters comprises a group identifier of the disaster recovery channel group and address parameters, and each address parameter comprises an IP address of a second CP and an IP address of the first CP.

According to the IP address of a second CP, the first CP establishes a disaster recovery channel with the second CP, and binds the group identification of the disaster recovery channel group with the established disaster recovery channel. The disaster recovery channel comprises a heartbeat channel, a plurality of data backup channels and a disaster recovery protection channel. The process of establishing the disaster recovery channel is the same as that of the existing active-standby CP, and will not be repeated here.

In one example, the group identifier of the disaster recovery channel group included in the first configuration instruction is disaster recovery channel group 1, and the address parameter includes an IP address of the first CP and an IP address of the second CP. According to the address parameters, the first CP and the second CP establish a disaster recovery channel 1, wherein the address of one end of the disaster recovery channel 1 is the IP address of the first CP, and the address of the other end is the IP address of the second CP. The disaster recovery channel 1 is bound with the disaster recovery channel group 1.

In another example, the group identifier of the disaster recovery channel group included in the first configuration instruction is disaster recovery channel group 2, and the address parameter includes an IP address of the first CP and an IP address of the third CP. According to the address parameters, the first CP and the third CP establish a disaster recovery channel 2, where an address at one end of the disaster recovery channel 2 is an IP address of the first CP, and an address at the other end is an IP address of a third CP (the third CP is one of the plurality of second CPs, and here, the third CP is taken as an example). The disaster recovery channel 2 is bound with the disaster recovery channel group 2.

The first CP receives a plurality of second configuration instructions input by a user again, wherein each second configuration instruction comprises a backup type and a second group of parameters for configuring the CP disaster recovery group, and each second group of parameters comprises the name, the group identifier, the role and the UP identifier of the standby pipe of the CP disaster recovery group.

And configuring a plurality of CP disaster recovery groups on the first CP according to the backup type, the name of the CP disaster recovery group, the group identification and the role, wherein each CP disaster recovery group has the name, the group identification, the role and the backup type, and each CP disaster recovery group comprises the UP identification of the standby management.

The backup types include a 1:1 backup type and a 1+1 backup type.

In one example, if the backup type is a 1:1 backup type, a backup CP disaster recovery group is configured on the first CP, where the CP disaster recovery group is named group1 and the group identifier is group-id1.

In another example, if the backup type is 1+1, two CP disaster recovery groups are configured on the first CP, where one CP disaster recovery group is named group2, the group identifier is group-id2, and the role is a backup CP disaster recovery group; the other CP disaster recovery group is named group3, the group identifier is group-id3, and the role is the master CP disaster recovery group.

The first CP receives a plurality of third configuration instructions input by a user again, wherein each third configuration instruction comprises a group identifier of the disaster recovery channel group and a group identifier of at least one CP disaster recovery group.

And the first CP carries out binding processing on the group identifier of the disaster recovery channel group and the group identifier of at least one CP disaster recovery backup group.

In one example, if the backup type is a 1:1 backup type, the first CP binds the disaster recovery channel group1 with a group identifier group1 of the backup CP disaster recovery group.

In another example, if the backup type is 1+1, the first CP binds the disaster recovery channel group2 with the group identifier group2 of the backup CP disaster recovery group and the group identifier group3 of the primary CP disaster recovery group, respectively.

It should be noted that, according to the description of the foregoing embodiment, after the first CP, the second CP, and the third CP bind the group identifier of the configured disaster recovery channel group with the group identifier of the CP disaster recovery group locally, the UP indicated by the UP identifier in the CP disaster recovery group establishes a CUSP channel with the CP where the master/slave CP disaster recovery group is located. And the master-slave CP disaster recovery backup group informs the UP of the master-slave roles of the master-slave CP disaster recovery backup group through the CUSP channel. And for UP, the CP where the main CP disaster backup group is located is the main CP, and the CP where the backup CP disaster backup group is located is the backup CP. Subsequently, the UP and the main CP perform interaction of protocol messages and service messages.

After the protocol message sent by the user terminal is sent to the main CP through UP, the main CP interacts with the AAA server and the DHCP server to finish the user authentication and the application of the IP address, and the main CP generates the user list item. The master CP issues the user entries to the UP through the CUSP channel. Subsequently, the UP can forward the service message according to the user table entry. The UP reports the statistical information of the user flow to the main CP at regular time through the CUSP channel, so that the main CP sends the statistical information to the AAA server, and the AAA server performs charging processing according to the statistical information.

The process from the UP and the master-slave CP to establish the CUSP channel to the master CP to send the statistical information to the AAA server is the same as the existing process, and only a simple description is provided herein.

Further, before executing the step, the method further includes a process that the second CP periodically sends a heartbeat message to the first CP, and the first CP determines whether to execute the active-standby switching through the heartbeat message.

Two second CPs (i.e., a second CP and a third CP) are illustrated as examples:

the second CP generates a first heartbeat message, wherein the first heartbeat message comprises the working state of the second CP or the first link failure rate between the second CP and UP indicated by UP identification in the main CP disaster recovery group. Similarly, the third CP also generates a first heartbeat message, where the first heartbeat message includes a working state of the third CP or a first link failure rate between the third CP and an UP indicated by an UP identifier in the active CP disaster recovery group.

And sending heartbeat messages to the first CP by the second CP and the third CP through the heartbeat channel.

And the first CP receives the heartbeat message through the heartbeat channel and acquires the working state of the CP or the first link failure rate from the heartbeat message.

In one implementation, if the working state of the CP is an unavailable state, the first CP determines that the second CP and the third CP are faulty, and executes the step.

In another implementation, the first CP obtains a second link failure rate between itself and the UP indicated by the UP identity in the backup CP disaster recovery group. If the first link failure rate is not less than the preset failure threshold (e.g., 80%) and the second link failure rate is less than the failure threshold, the first CP determines that the second CP and the third CP are failed, and executes the step.

And 120, determining the backup type provided for each second CP and the group identification of the backup CP disaster recovery backup group bound with the group identification of the disaster recovery channel group according to the group identification of the disaster recovery channel group.

Specifically, according to the description of step 110, after the first CP obtains the group identifier of the disaster recovery channel group bound to the address of each second CP, the backup type provided by the first CP for each second CP and the group identifier of the backup CP disaster recovery group bound to the group identifier of the disaster recovery channel group are determined according to the group identifier of the disaster recovery channel group.

Further, in one example, the group identifier of the disaster recovery channel group acquired by the first CP is disaster recovery channel group1. According to the disaster recovery channel group1, the first CP determines that the backup type provided by the first CP for the second CP is 1:1 backup type, and the group identifier of the backup CP disaster recovery group is group1.

In another example, the group identifier of the disaster recovery channel group acquired by the first CP is disaster recovery channel group2. According to the disaster recovery channel group2, the first CP determines that the backup type provided by itself for the third CP is a 1+1 backup type, and the group identifier of the backup CP disaster recovery group is group2.

And 130, taking over the backup CP disaster recovery backup group corresponding to the group identifier of the backup CP disaster recovery backup group according to the backup type, and providing business service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group.

Specifically, according to the description of step 120, after the first CP determines the backup type provided for each second CP and the group identifier of the backup CP disaster recovery group, according to the backup type, the backup CP disaster recovery group corresponding to the group identifier of the backup CP disaster recovery group is taken over, and service is provided for the UP corresponding to at least one UP identifier included in the backup CP disaster recovery group.

It can be understood that, the first CP is used as a backup CP of the second CP, and the backup CP disaster recovery group1 configured locally is the same as the primary CP disaster recovery group1 configured on the second CP, and both include the same UP identifier.

Similarly, the first CP is used as a backup CP of the third CP, and the backup CP disaster recovery group2 configured locally is the same as the master CP disaster recovery group2 configured on the third CP, and all include the same UP identifier.

Therefore, the first CP can provide backup service for a plurality of main CPs with faults at the same time, and can rapidly take over UP and user services borne on the UP in the process of switching the main CPs and the backup CPs.

Therefore, by applying the backup implementation method provided by the application, when a plurality of second CPs fail or a link between each second CP and UP indicated by UP identification in the main CP disaster recovery group fails, the first CP acquires the group identification of the disaster recovery channel group bound with the address of each second CP according to the address of each second CP; according to the group identification of the disaster recovery channel group, the first CP determines the backup type provided for each second CP and the backup CP disaster backup group bound with the group identification of the disaster recovery channel group; and according to the backup type, the first CP takes over the backup CP disaster recovery backup group and provides business service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group.

The following describes in detail another implementation method of backup provided in the embodiment of the present application. Referring to fig. 2, fig. 2 is a flowchart of another implementation method of backup according to an embodiment of the present application. The method is applied to the first CP. The implementation method of backup provided by the embodiment of the application may include the following steps.

Step 210, generating a heartbeat message, where the heartbeat message includes a working state of the first CP or a first link failure rate between the first CP and an UP indicated by an UP identifier in the master CP disaster recovery device group.

Step 220, sending the heartbeat message to a second CP through a heartbeat channel, so that the second CP takes over the standby CP disaster recovery group and provides service for an UP corresponding to at least one UP identifier included in the standby CP disaster recovery group when determining the first CP failure or a link failure between the first CP and the UP indicated by the UP identifier in the main CP disaster recovery group according to the working state or the first link failure rate.

Optionally, in the embodiment of the present application, the method further includes a process that the first CP receives a plurality of configuration instructions input by a user, and a process that the first CP establishes a disaster recovery channel with an opposite terminal through the plurality of configuration instructions, configures a CP disaster recovery group locally, and binds a group identifier of the disaster recovery channel group with a group identifier of the CP disaster recovery group.

In the foregoing embodiments, the process of receiving the configuration instruction of the second CP and the third CP, which are the primary CPs, and performing the local configuration according to the configuration instruction, and the process of interacting with the heartbeat message between the first CP, which is the standby CP, have been received in detail, and will not be described here.

The implementation method of backup provided in the embodiment of the present application is described in detail below. Referring to fig. 3 and fig. 4, fig. 3 is a schematic diagram of n:1 backup networking when a plurality of primary CPs provided in the embodiment of the present application work normally, and fig. 4 is a schematic diagram of n:1 backup networking when a plurality of primary CPs provided in the embodiment of the present application fail.

Three CPs are illustrated in fig. 3 and 4.

Configuration 1:1 backup on CP1, CP 3:

the CP1 receives a first configuration instruction input by a user, where the first configuration instruction includes a group identifier of a disaster recovery channel group (disaster recovery channel group 1) and an address parameter, and the address parameter includes an IP address (1.1.1.1) of the CP1 and an IP address (3.3.3.3) of the CP 3.

The CP3 receives a first configuration instruction input by a user, where the first configuration instruction includes a group identifier of a disaster recovery channel group (disaster recovery channel group 1) and an address parameter, and the address parameter includes an IP address (3.3.3.3) of the CP3 and an IP address (1.1.1.1.1) of the CP 1.

And the CP1 and the CP3 establish a disaster recovery channel 1 with the opposite end according to the IP address of the opposite end, and bind the group identification (disaster recovery channel group 1) of the disaster recovery channel group with the established disaster recovery channel 1.

The disaster recovery channel comprises a heartbeat channel, a plurality of data backup channels and a disaster recovery protection channel. The process of establishing the disaster recovery channel is the same as that of the existing active-standby CP, and will not be repeated here.

The CP1 receives a second configuration instruction input by the user, where the second configuration instruction includes a second set of parameters, where the second set of parameters includes a name of the CP disaster recovery group (group 1), a group identifier (group-id 1), a role of the CP disaster recovery group (main CP disaster recovery group), and UP identifiers (UP 1, UP 2) of the standby.

The CP3 receives a second configuration instruction input by the user, where the second configuration instruction includes a backup type and a second set of parameters, and the second set of parameters includes a name (group 1) of the CP disaster recovery group, a group identifier (group-id 1), a role (backup CP disaster recovery group) of the CP disaster recovery group, and UP identifiers (UP 1, UP 2) of the standby nanotubes.

And respectively configuring a main CP disaster recovery group with a group identifier of group-id1 and a standby CP disaster recovery group with a group identifier of group-id1 on the CP1 and the CP3, wherein the main and standby CP disaster recovery groups comprise UP1 and UP2.

And the CP1 and the CP3 both receive a third configuration instruction input by a user, wherein the third configuration instruction comprises a group identifier (disaster recovery channel group 1) of the disaster recovery channel group and a group identifier (group-id 1) of the CP disaster recovery backup group.

And the CP1 and the PC3 bind the local disaster recovery channel group 1 with the group-id 1.

Configuring 1+1 backup on CP2 and CP 3:

the CP2 receives a first configuration instruction input by a user, where the first configuration instruction includes a group identifier of a disaster recovery channel group (disaster recovery channel group 2) and an address parameter, and the address parameter includes an IP address (2.2.2.2) of the CP2 and an IP address (3.3.3.3) of the CP 3.

The CP3 receives a first configuration instruction input by a user, where the first configuration instruction includes a group identifier of a disaster recovery channel group (disaster recovery channel group 2) and an address parameter, and the address parameter includes an IP address (3.3.3.3) of the CP3 and an IP address (2.2.2.2) of the CP 2.

And the CP2 and the CP3 establish a disaster recovery channel 2 with the opposite end according to the IP address of the opposite end, and bind the group identification (disaster recovery channel group 2) of the disaster recovery channel group with the established disaster recovery channel 2.

The CP2 receives a second configuration instruction input by the user, where the second configuration instruction includes a backup type and a second set of parameters, and the second set of parameters includes a name (group 2, group 3) of the CP disaster recovery group, a group identifier (group-id 2, group-id 3), roles (primary CP disaster recovery group, backup CP disaster recovery group) of the CP disaster recovery group, and UP identifiers (UP 3, UP4, UP5, UP 6) of the standby pipe.

The CP3 receives a second configuration instruction input by the user, where the second configuration instruction includes a backup type and a second set of parameters, where the second set of parameters includes a name of the CP disaster recovery group (group 2, group 3), a group identifier (group-id 2, group-id 3), roles of the CP disaster recovery group (primary CP disaster recovery group, backup CP disaster recovery group), and UP identifiers of the standby pipes (UP 3, UP4, UP5, UP 6).

Configuring a main CP disaster recovery group with a group identifier of group-id2 and a backup CP disaster recovery group with a group-id3 on the CP2, wherein the main CP disaster recovery group comprises UP3 and UP4, and the backup CP disaster recovery group comprises UP5 and UP6; and configuring a main CP disaster recovery group with a group identifier of group-id3 and a backup CP disaster recovery group with a group-id2 on the CP3, wherein the main CP disaster recovery group comprises UP5 and UP6, and the backup CP disaster recovery group comprises UP3 and UP4.

And the CP2 and the CP3 both receive a third configuration instruction input by a user, wherein the third configuration instruction comprises a group identifier (disaster recovery channel group 2) of the disaster recovery channel group and a group identifier (group-id 2 and group-id 3) of the CP disaster backup group.

And the CP1 and the PC3 bind the local disaster recovery channel group2 with the group-id2 and the group-id 3.

In this embodiment of the present application, a view of a disaster recovery channel group is newly added in CP3, and functions of receiving a first configuration instruction, a second configuration instruction, and a third configuration instruction, and executing corresponding actions according to the first configuration instruction, the second configuration instruction, and the third configuration instruction are added under the view. Therefore, a plurality of CP disaster recovery groups can be configured on the CP3, and the plurality of CP disaster recovery groups share one disaster recovery channel. In practical application, each CP may add a disaster recovery channel group view.

After each CP is configured as described above, the backup condition table is recorded locally.

Backup case recorded in CP1 table 1:

table 1CP1 backup status table

	CP1
		IP address	1.1.1.1
Disaster recovery channel group1	Local-IP：1.1.1.1-Peer-IP：3.3.3.3
		1:1 disaster recovery backup group	group1 (Master) binding disaster recovery channel group1

Backup case recorded in CP2 table 2:

table 2CP2 backup status table

	CP2
		IP address	2.2.2.2
Disaster recovery channel group2	Local-IP：2.2.2.2-Peer-IP：3.3.3.3
		1+1 disaster recovery backup group	grouP2 (primary) and group3 (backup) binding disaster recovery channel group2

Backup case recorded in CP3 table 3:

table 3CP3 backup status table

	CP3
		IP address	3.3.3.3
Disaster recovery channel group1	Local-IP：3.3.3.3-Peer-IP：1.1.1.1
		Disaster recovery channel group2	Local-IP：3.3.3.3-Peer-IP：2.2.2.2
1:1 disaster recovery backup group	group1 (backup) binding disaster recovery channel group1
		1+1 disaster recovery backup group	group2 (backup) and group3 (primary) binding disaster recovery channel group2

After the foregoing configuration, as shown in fig. 3, the host is brought on line through CP1, CP 2. When the CP1 or the CP2 fails, or a link between the CP1 and the UP fails, or a link between the CP2 and the UP fails, the CP3 determines the backup type provided for the CP1 and the CP2 and the group identification of the backup group according to the group identification of the disaster recovery channel group. As shown in fig. 4, CP3 takes over group1 and group2 according to the backup type, and provides business services for UP corresponding to UP id in group1 and group 2.

Based on the same inventive concept, the embodiment of the application also provides a backup realization device corresponding to the backup realization method. Referring to fig. 5, fig. 5 is a block diagram of a backup implementation device according to an embodiment of the present application. The device is applied to a first CP, the first CP is in a first DC, the first CP includes at least one backup CP disaster recovery group, each backup CP disaster recovery group and one primary CP disaster recovery group include the same at least one UP identifier, the primary CP disaster recovery group is in a second CP, the second CP is in a second DC, the device includes:

a first obtaining unit 510, configured to obtain, according to an address of each second CP, a group identifier of a disaster recovery channel group bound to the address of each second CP when a plurality of second CPs fail or a link between each second CP and an UP indicated by the UP identifier in the master CP disaster recovery group fails;

A first determining unit 520, configured to determine, according to the group identifier of the disaster recovery channel group, a backup type provided for each second CP and a group identifier of a backup CP disaster recovery group bound to the group identifier of the disaster recovery channel group;

and a take-over unit 530, configured to take over, according to the backup type, a backup CP disaster recovery backup group corresponding to a group identifier of the backup CP disaster recovery backup group, and provide a service for an UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group.

Optionally, the apparatus further comprises: a receiving unit (not shown in the figure) for receiving a plurality of first configuration instructions input by a user, where each first configuration instruction includes a first set of parameters for configuring different disaster recovery channel groups, each first set of parameters includes a group identifier of a disaster recovery channel group and an address parameter, and the address parameter includes an IP address of a second CP and an IP address of the first CP;

a building unit (not shown in the figure) configured to build a disaster recovery channel with each second CP according to the IP address of the second CP, where the disaster recovery channel has a group identifier of the disaster recovery channel group;

the receiving unit (not shown in the figure) is further configured to receive a plurality of second configuration instructions input by the user, where each second configuration instruction includes a backup type, a second set of parameters for configuring different CP disaster recovery groups, and each second set of parameters includes a name of the CP disaster recovery group, a group identifier, a role, and an UP identifier of a waiting tube;

A configuration unit (not shown in the figure) configured to locally configure a plurality of CP disaster recovery groups according to the backup type, the name, the group identifier, and the role of the CP disaster recovery group, where each CP disaster recovery group has a name, a group identifier, a role, and a provided backup type, and each CP disaster recovery group includes the UP identifier of the standby pipe;

the receiving unit (not shown in the figure) is further configured to receive a plurality of third configuration instructions input by the user, where each third configuration instruction includes a group identifier of the disaster recovery channel group and a group identifier of at least one CP disaster recovery group;

and a binding unit (not shown in the figure) for binding the group identifier of the disaster recovery channel group with the group identifier of the at least one CP disaster recovery backup group.

Optionally, the receiving unit (not shown in the figure) is further configured to receive, through a heartbeat channel, a heartbeat packet sent by each second CP, where the heartbeat packet includes an operating state of the second CP;

the apparatus further comprises: a second determining unit (not shown in the figure) configured to determine that the second CP is faulty if the working state of the second CP is an unavailable state;

or,

the receiving unit (not shown in the figure) is further configured to receive, through the heartbeat channel, a heartbeat packet sent by each second CP, where the heartbeat packet includes a first link failure rate between the second CP and an UP in the primary CP disaster recovery device group;

The apparatus further comprises: a second obtaining unit (not shown in the figure) for obtaining a second link failure rate with the UP belonging to the backup CP disaster recovery group;

a second determining unit (not shown in the figure) configured to determine a link failure between each second CP and an UP in the primary CP disaster recovery group if the first link failure rate is not less than a preset failure threshold and the second link failure rate is less than the failure threshold.

Optionally, the disaster recovery channel includes a heartbeat channel, a plurality of data backup channels, and a disaster recovery protection channel.

Optionally, the backup types include a 1:1 backup type and a 1+1 backup type.

Optionally, the configuration unit (not shown in the figure) is specifically configured to locally configure the primary CP disaster recovery group and the backup CP disaster recovery group if the backup type is a 1+1 backup type;

if the backup type is 1:1 backup type, locally configuring a backup CP disaster recovery group;

the binding unit (not shown in the figure) is specifically configured to bind the group identifier of one disaster recovery channel group with the group identifier of the created primary CP disaster recovery group and the group identifier of the backup CP disaster recovery group, respectively, if the backup type is a 1+1 backup type;

And if the backup type is 1:1 backup type, binding the group identifier of the disaster recovery channel group with the group identifier of the created backup CP disaster recovery backup group.

Therefore, by applying the backup implementation device provided by the application, when a plurality of second CPs fail or a link between each second CP and UP indicated by UP identification in a main CP disaster recovery group fails, the first CP acquires the group identification of the disaster recovery channel group bound with the address of each second CP according to the address of each second CP; according to the group identification of the disaster recovery channel group, the first CP determines the backup type provided for each second CP and the backup CP disaster backup group bound with the group identification of the disaster recovery channel group; and according to the backup type, the first CP takes over the backup CP disaster recovery backup group and provides business service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group.

Based on the same inventive concept, the embodiment of the application also provides a backup realization device corresponding to the backup realization method. Referring to fig. 6, fig. 6 is a block diagram of another backup implementation device according to an embodiment of the present application. The device is applied to a first CP, the first CP is in a first DC, the first CP comprises a main CP disaster recovery group, the main CP disaster recovery group and a standby CP disaster recovery group both comprise the same at least one UP identifier, the standby CP disaster recovery group is in a second CP, the second CP is in a second DC, and the device comprises:

A generating unit 610, configured to generate a heartbeat packet, where the heartbeat packet includes a working state of the first CP or a first link failure rate between the first CP and an UP indicated by an UP identifier in the active CP disaster recovery group;

a sending unit 620, configured to send the heartbeat packet to a second CP through a heartbeat channel, so that the second CP takes over the backup CP disaster recovery group and provides a service for an UP corresponding to at least one UP identifier included in the backup CP disaster recovery group when determining the first CP failure or a link failure between the first CP and the UP indicated by the UP identifier in the primary CP disaster recovery group according to the working state or the first link failure rate

Optionally, the apparatus further comprises: a receiving unit (not shown in the figure) configured to receive a first configuration instruction input by a user, where the first configuration instruction includes a first set of parameters for configuring a disaster recovery channel group, where the first set of parameters includes a group identifier of the disaster recovery channel group and an address parameter, and the address parameter includes an IP address of the second CP and an IP address of the first CP;

a setting unit (not shown in the figure) configured to set up a disaster recovery channel with the second CP according to the IP address of the second CP, where the disaster recovery channel has a group identifier of the disaster recovery channel group;

The receiving unit (not shown in the figure) is further configured to receive a second configuration instruction input by the user, where the second configuration instruction includes a second set of parameters for configuring the CP disaster recovery group, and the second set of parameters includes a name, a group identifier, a role, and an UP identifier of a waiting tube of the CP disaster recovery group;

a configuration unit (not shown in the figure) configured to configure a CP disaster recovery group locally according to the name, the group identifier and the role of the CP disaster recovery group, where the CP disaster recovery group has the name, the group identifier and the role, and the CP disaster recovery group includes the UP identifier of the waiting nanotube;

the receiving unit (not shown in the figure) is further configured to receive a third configuration instruction input by the user, where the third configuration instruction includes a group identifier of the disaster recovery channel group and a group identifier of the CP disaster recovery group;

and the binding unit (not shown in the figure) is used for binding the group identifier of the disaster recovery channel group with the group identifier of the CP disaster recovery backup group.

Optionally, the second configuration instruction further includes a backup type, where the backup type includes a 1:1 backup type and a 1+1 backup type.

the binding unit (not shown in the figure) is specifically configured to bind the group identifier of the disaster recovery channel group with the created group identifier of the primary CP disaster recovery group and the group identifier of the backup CP disaster recovery group, respectively, if the backup type is a 1+1 backup type.

Based on the same inventive concept, the present embodiment also provides a network device, as shown in fig. 7, including a processor 710, a transceiver 720, and a machine-readable storage medium 730, where the machine-readable storage medium 730 stores machine-executable instructions capable of being executed by the processor 710, and the processor 710 is caused by the machine-executable instructions to perform the implementation method of the backup provided by the embodiment of the present application. The implementation device of the n:1 backup shown in fig. 5 and 6 can be implemented by adopting a hardware structure of the network device shown in fig. 7.

The computer readable storage medium 730 may include a random access Memory (e.g., random Access Memory, or simply, RAM) or a nonvolatile Memory (e.g., NVM), such as at least one magnetic disk Memory. Optionally, the computer readable storage medium 730 may also be at least one storage device located remotely from the processor 710.

The processor 710 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (English: digital Signal Processor; DSP; for short), an application specific integrated circuit (English: application Specific Integrated Circuit; ASIC; for short), a Field programmable gate array (English: field-Programmable Gate Array; FPGA; for short), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

In this embodiment, processor 710, by reading machine-executable instructions stored in machine-readable storage medium 730, is caused by the machine-executable instructions to implement processor 710 itself and invoke transceiver 720 to perform the implementation of the backup described in the previous embodiments of this application.

Additionally, embodiments of the present application provide a machine-readable storage medium 530, the machine-readable storage medium 730 storing machine-executable instructions that, when invoked and executed by the processor 710, cause the processor 710 itself and the invoking transceiver 720 to perform the implementation of the backup described in the previous embodiments of the present application.

The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

For the implementation of the backup and the machine-readable storage medium embodiments, since the method content involved is substantially similar to the method embodiments described above, the description is relatively simple, and references to the relevant portions of the method embodiments are only needed.

The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.

Claims

1. The method for realizing backup is characterized in that the method is applied to a first CP, the first CP is located in a first data center DC, the first CP comprises at least one backup CP disaster recovery group, each backup CP disaster recovery group and one main CP disaster recovery group comprise the same at least one UP identifier, the main CP disaster recovery group is located in a second CP, and the second CP is located in a second DC, and the method comprises the following steps:

taking over the backup CP disaster recovery backup group corresponding to the group identifier of the backup CP disaster recovery backup group according to the backup type, and providing service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group;

the CP is a device applied to the vBRAS forwarding and control separation networking.

2. The method of claim 1, wherein when the plurality of second CPs fail or a link between each second CP and an UP indicated by an UP identifier in the master CP disaster recovery device group fails, before acquiring a group identifier of the disaster recovery channel group bound to an address of each second CP according to an address of each second CP, the method further comprises:

receiving a plurality of first configuration instructions input by a user, wherein each first configuration instruction comprises a first group of parameters for configuring different disaster recovery channel groups, each first group of parameters comprises a group identifier of the disaster recovery channel group and an address parameter, and the address parameter comprises an IP address of a second CP and an IP address of the first CP;

establishing a disaster recovery channel with each second CP according to the IP address of the second CP, wherein the disaster recovery channel is provided with a group identifier of the disaster recovery channel group;

Receiving a plurality of second configuration instructions input by the user, wherein each second configuration instruction comprises a backup type and a second group of parameters for configuring different CP disaster recovery groups, and each second group of parameters comprises a name, a group identifier, a role and an UP identifier of a waiting management;

configuring a plurality of CP disaster recovery groups locally according to the backup type, the name, the group identifier and the role of the CP disaster recovery group, wherein each CP disaster recovery group has the name, the group identifier, the role and the backup type provided, and each CP disaster recovery group comprises the UP identifier of the waiting tube;

receiving a plurality of third configuration instructions input by the user, wherein each third configuration instruction comprises a group identifier of a disaster recovery channel group and a group identifier of at least one CP disaster recovery group;

and binding the group identifier of the disaster recovery channel group with the group identifier of the at least one CP disaster recovery backup group.

3. The method of claim 1, wherein when a plurality of second CPs fail or a link between each second CP and an UP indicated by an UP identifier in a master CP disaster recovery group fails, before acquiring a group identifier of a disaster recovery channel group bound to an address of each second CP according to an address of each second CP, the method further comprises:

Receiving a heartbeat message sent by each second CP through a heartbeat channel, wherein the heartbeat message comprises the working state of the second CP;

if the working state of the second CP is an unavailable state, determining that the second CP is faulty;

or,

receiving a heartbeat message sent by each second CP through the heartbeat channel, wherein the heartbeat message comprises a first link failure rate between the second CP and UP in a main CP disaster recovery group;

acquiring a second link failure rate between the backup node and UP belonging to the backup CP disaster recovery group;

and if the first link failure rate is not smaller than a preset failure threshold value and the second link failure rate is smaller than the failure threshold value, determining the link failure between each second CP and UP in the main CP disaster recovery group.

4. The method of claim 2, wherein the disaster recovery channel comprises a heartbeat channel, a plurality of data backup channels, and a disaster recovery protection channel.

5. The method of any of claims 1-4, wherein the backup types include a 1:1 backup type and a 1+1 backup type.

6. The method of claim 2, wherein the locally configuring a plurality of CP disaster recovery backup groups according to the backup type, the name, the group identifier, and the role of the CP disaster recovery backup group specifically includes:

If the backup type is 1+1 backup type, configuring a main CP disaster recovery backup group and a backup CP disaster recovery backup group locally;

the binding process is performed on the group identifier of the disaster recovery channel group and the group identifier of the at least one CP disaster recovery backup group, and specifically includes:

if the backup type is 1+1 backup type, respectively binding the group identifier of one disaster recovery channel group with the group identifier of the created main CP disaster recovery backup group and the group identifier of the backup CP disaster recovery backup group;

7. The method for realizing backup is characterized in that the method is applied to a first CP, the first CP is located in a first data center DC, the first CP comprises a main CP disaster recovery group, the main CP disaster recovery group and a standby CP disaster recovery group both comprise the same at least one UP identifier, the standby CP disaster recovery group is located in a second CP, and the second CP is located in a second DC, and the method comprises the following steps:

Sending the heartbeat message to a second CP through a heartbeat channel, so that the second CP obtains a group identifier of a disaster recovery channel group bound with an address of a first CP according to the address of the first CP when determining the first CP fault or the link fault between the first CP and UP indicated by the UP identifier in a main CP disaster recovery group according to the working state or the first link fault rate; according to the group identification of the disaster recovery channel group, determining a backup type provided for the first CP and a backup CP disaster recovery group bound with the group identification of the disaster recovery channel group; taking over the backup CP disaster recovery backup group according to the backup type, and providing business service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group;

8. The method of claim 7, wherein prior to generating the heartbeat message, the method further comprises:

receiving a first configuration instruction input by a user, wherein the first configuration instruction comprises a first group of parameters for configuring a disaster recovery channel group, the first group of parameters comprise a group identifier of the disaster recovery channel group and an address parameter, and the address parameter comprises an IP address of the second CP and an IP address of the first CP;

Establishing a disaster recovery channel with the second CP according to the IP address of the second CP, wherein the disaster recovery channel is provided with a group identifier of the disaster recovery channel group;

receiving a second configuration instruction input by the user, wherein the second configuration instruction comprises a second group of parameters for configuring the CP disaster recovery group, and the second group of parameters comprise the name, the group identifier, the role and the UP identifier of the standby pipe of the CP disaster recovery group;

a CP disaster recovery group is configured locally according to the name, the group identifier and the role of the CP disaster recovery group, wherein the CP disaster recovery group has the name, the group identifier and the role, and the CP disaster recovery group comprises the UP identifier of the waiting-to-be-received pipe;

receiving a third configuration instruction input by the user, wherein the third configuration instruction comprises a group identifier of a disaster recovery channel group and a group identifier of a CP disaster recovery group;

and binding the group identifier of the disaster recovery channel group with the group identifier of the CP disaster recovery backup group.

9. The method of claim 8, wherein the disaster recovery channel comprises a heartbeat channel, a plurality of data backup channels, and a disaster recovery protection channel.

10. The method of claim 9, wherein the second configuration instruction further comprises a backup type, the backup type comprising a 1:1 backup type and a 1+1 backup type.

11. The method of claim 10, wherein the locally configuring the CP disaster recovery backup group according to the name, the group identifier, and the role of the CP disaster recovery backup group specifically includes:

the binding process is performed on the group identifier of the disaster recovery channel group and the group identifier of the CP disaster recovery backup group, and specifically includes:

if the backup type is 1+1 backup type, binding the group identifier of the disaster recovery channel group with the group identifier of the created main CP disaster recovery backup group and the group identifier of the backup CP disaster recovery backup group respectively.

12. An implementation apparatus for backup, where the apparatus is applied to a first CP, where the first CP is in a first DC, where the first CP includes at least one backup CP disaster recovery group, where each backup CP disaster recovery group includes at least one UP identifier that is the same as one primary CP disaster recovery group, where the primary CP disaster recovery group is in a second CP, and where the second CP is in a second DC, where the apparatus includes:

13. The device is applied to a first CP, the first CP is located in a first data center DC, the first CP includes a primary CP disaster recovery group, the primary CP disaster recovery group and a backup CP disaster recovery group each include the same at least one UP identifier, the backup CP disaster recovery group is located in a second CP, and the second CP is located in a second DC, the device includes:

a sending unit, configured to send the heartbeat packet to a second CP through a heartbeat channel, so that the second CP obtains, according to an address of the first CP, a group identifier of a disaster recovery channel group bound to the address of the first CP when determining that the first CP fails or that a link between the first CP and an UP indicated by the UP identifier in a master CP disaster recovery group fails according to the working state or the first link failure rate; according to the group identification of the disaster recovery channel group, determining a backup type provided for the first CP and a backup CP disaster recovery group bound with the group identification of the disaster recovery channel group; taking over the backup CP disaster recovery backup group according to the backup type, and providing business service for UP corresponding to at least one UP identifier included in the backup CP disaster recovery backup group;