CN114095342A

CN114095342A - Method and device for realizing backup

Info

Publication number: CN114095342A
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: 2022-02-25
Anticipated expiration: 2041-10-21
Also published as: CN114095342B

Abstract

The application provides a method and a device for realizing backup, wherein the method is applied to a first CP (content provider), and comprises the following steps: when a plurality of second CPs fail or a link between UP indicated by the UP identifier in each second CP and the main CP disaster recovery group fails, acquiring a group identifier of the disaster recovery channel group bound with the address of each second CP according to the address of each second CP; determining a backup type provided for each second CP and a 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 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 service for UP corresponding to at least one UP identifier included in the backup CP disaster backup group.

Description

Method and device for realizing backup

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing backup.

Background

At present, when the insurmountable forces such as earthquake, fire and the like are faced, local data backup cannot guarantee that backup data are not lost, and the requirements of operators on high availability, real-time performance and safety of service systems cannot be met. In order to deal with the above situation and reduce enterprise loss, the industry proposes a technical idea of disaster recovery from different places.

The CP disaster recovery is a remote disaster recovery technology applied to the vBRAS forwarding and control separation networking. Multiple CPs are in Data centers (abbreviated as DC) with different address positions, and double-machine backup is carried out through the multiple CPs so as to realize remote disaster recovery, so that when one DC fails or has a disaster, another DC can quickly take over user services.

In a vBRAS forwarding and control separation networking, the existing CP disaster recovery mode comprises 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 specifically comprises the following steps: and respectively creating a CP disaster backup group in the two CPs which are mutually main and backup. And a main CP disaster backup group is established in the main CP, a backup CP disaster backup group is established in the backup CP, and the UP ranges managed by the main CP disaster backup group and the backup CP disaster backup group are consistent. When the main CP fails, the main CP disaster recovery group can not provide service for the user service on the UP continuously. At this time, the backup CP takes over the work of the main CP and starts the backup CP disaster backup group to manage the user service on UP.

Under the 1+1 backup type, the main CP and the standby CP are all the current working CP. The implementation process specifically comprises the following steps: two CP disaster recovery backup groups are respectively established in the main CP and the backup CP. The CP disaster backup groups with the same name in the main CP and the standby CP disaster backup groups are respectively used as the main CP disaster backup group and the standby CP disaster backup group, the UP ranges managed by the main CP disaster backup group and the standby CP disaster backup group are consistent, and the main and standby states of different CP disaster backup groups in the same CP are different. For example, a main CP in the DC1 creates a main CP disaster recovery group a and a backup CP disaster recovery group B, the UP ranges managed by the main CP disaster recovery group a are UP1 and UP2, and the UP ranges managed by the backup CP disaster recovery group B are UP3 and UP 4; similarly, the backup CP in the DC2 creates a backup CP disaster backup group a and a main CP disaster backup group B, the UP ranges managed by the backup CP disaster backup group a are UP1 and UP2, and the UP ranges managed by the main CP disaster backup group B are UP3 and UP 4. At the same time, different CPs manage user services on part of UP, reduce the service pressure of single points, and improve the utilization rate of network equipment.

The two backup types are both the CP device in one DC to provide backup service only for the CP device in the other DC at the same time, and the utilization rate of the device resource 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 an apparatus for implementing backup, so as to solve the problem that the utilization rate of device resources of a DC where a CP is backed up is low in the two existing backup types.

In a first aspect, the present application provides a method for implementing backup, where the method is applied to a first CP, where the first CP is located in a first DC, the first CP includes at least one CP backup disaster backup group, each CP backup disaster backup group and a main CP disaster backup group both include at least one UP identifier that is the same, the main CP disaster backup group is located in a second CP, and the second CP is located in a second DC, and the method includes:

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

determining a backup type provided for each second CP and a group identifier of a 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 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 service for UP corresponding to at least one UP identifier included in the backup CP disaster backup group.

In a second aspect, the present application provides a method for implementing backup, where the method is applied to a first CP, where the first CP is located in a first DC, the first CP includes a main CP disaster backup group, both the main CP disaster backup group and a CP backup disaster backup group include at least one UP identifier, the CP backup disaster backup group is located in a second CP, and the second CP is located in a second DC, and the method includes:

generating a heartbeat message, wherein the heartbeat message includes a working state of the first CP or a first link failure rate between the first CP and the UP indicated by the UP identifier in the 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 backup CP disaster backup group and provides service for an UP corresponding to at least one UP identifier included in the backup CP disaster backup group when determining that the first CP fails or a link between UPs indicated by the UP identifier in the primary CP disaster backup group fails according to the working state or the first link failure rate.

In a third aspect, the present application provides a device for implementing backup, where the device is applied to a first CP, the first CP is located in a first DC, the first CP includes at least one CP backup disaster backup group, each CP backup disaster backup group and a main CP disaster backup group both include at least one UP identifier that is the same, the main CP disaster backup group is located in a second CP, and the second CP is located in the second DC, and the device includes:

an obtaining unit, configured to, when multiple second CPs have a failure or a link between the UPs indicated by the UP identifier in the main CP disaster recovery group has a failure, obtain, according to an address of each second CP, a group identifier of the disaster recovery channel group bound to the address of each second CP;

a determining unit, 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 the backup CP disaster recovery group bound to the group identifier of the disaster recovery channel group;

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

In a fourth aspect, the present application provides a device for implementing backup, where the device is applied to a first CP, the first CP is located in a first DC, the first CP includes a main CP disaster backup group, both the main CP disaster backup group and a CP backup disaster backup group include at least one UP identifier, the CP backup group is located in a second CP, and the second CP is located in a second DC, and the device includes:

a generating unit, 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 a UP indicated by a UP identifier in a main CP disaster backup group;

a sending unit, 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 backup group when determining that the first CP has a failure or a link failure between UPs indicated by the UP identifier in the backup CP disaster backup group is determined according to the working state or the first link failure rate, and provides a service for a UP corresponding to at least one UP identifier included in the backup CP disaster backup group.

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, the processor being caused by the machine-executable instructions to perform the method provided by 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, the processor being caused by the machine-executable instructions to perform the method provided by the second aspect of the present application.

Therefore, by applying the method and the device for implementing backup provided by the present application, when multiple second CPs fail or a link between the UP indicated by the UP identifier in the main CP disaster backup group fails, the first CP obtains the group identifier of the disaster recovery channel group bound to the address of each second CP according to the address of each second CP; according to the group identification of the disaster tolerant 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 tolerant channel group; and according to the backup type, the first CP takes over the backup CP disaster recovery group and provides service for the UP corresponding to at least one UP identifier included in the backup CP disaster recovery group.

In this way, it is achieved that a CP within one DC can simultaneously provide backup services for CPs within N DCs at different geographical locations. 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 utilization rate of the equipment resource of the DC where the CP is located is low.

Drawings

Fig. 1 is a flowchart of a method for implementing backup according to an embodiment of the present application;

fig. 2 is a flowchart of another backup implementation method provided in an embodiment of the present application;

fig. 3 is a schematic diagram of an N:1 backup networking when multiple main CPs normally operate according to the embodiment of the present application;

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

fig. 5 is a structural diagram of an apparatus for implementing backup according to an embodiment of the present application;

fig. 6 is a structural diagram of another backup implementation apparatus provided in the embodiment of the present application;

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

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent 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 certain aspects of the present application, as detailed in the appended claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the 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 should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the corresponding listed items.

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

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

Step 110, when multiple second CPs fail or the link between the UPs indicated by the UP identifier in the second CP and the main CP disaster recovery group fails, acquiring the group identifier of the disaster recovery channel group bound to the address of each second CP according to the address of each second CP.

Specifically, the N:1 backup mesh network includes a plurality of CPs that are active and standby with each other, and each CP is in one DC. For example, the first CP is within a first DC, all other DCs except the first DC are collectively referred to as second DCs, and one second CP is included in each second DC. 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, a plurality of CPs are divided into the main and standby roles in advance according to the backup types. 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 main CP, and the first CP simultaneously provides backup services for the plurality of second CPs. And if the backup type is a 1+1 backup type, configuring the first CP as the main CP and the standby CP at the same time, and configuring the plurality of second CPs as the standby CP and the main CP. The first CP may inform that the 1:1 backup type and the 1+1 backup type are supported.

The main CP disaster backup group is configured in the main CP, the backup CP disaster backup group is configured in the backup CP, and the backup CP disaster backup groups which are mutually main and backup comprise the same at least one UP identification.

When a plurality of second CPs have faults or a link between the UPs indicated by the UP identifier in each second CP and the main CP disaster backup group has faults, the first CP locally obtains the group identifier of the disaster recovery channel group bound to 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 includes a process that the second CP and the first CP respectively receive a plurality of configuration instructions input by the user, and a process that the second CP and the first CP respectively establish the disaster recovery channel with the opposite end, configure the CP disaster recovery group locally, and bind the group identifier of the disaster recovery channel group with the group identifier of the CP disaster recovery group through the plurality of configuration instructions.

The following description will be given taking the second CP and the third CP as examples:

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

And according to the IP address of the first CP, the second CP and the first CP establish a disaster recovery channel, and the group identification of the disaster recovery channel group is bound 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 establishing the disaster recovery channel by the existing main CP and standby CP, and is not repeated here.

In one example, the group identifier of the disaster recovery channel group included in the first configuration instruction is a disaster recovery channel group1, and the address parameter includes an IP address of the first CP and an IP address of the second CP. And 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 of the disaster recovery channel 1 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 comprises a group identifier and address parameters of the disaster recovery channel group, and the address parameters comprise the IP address of the third CP and the IP address of the first CP.

And according to the IP address of the first CP, the third CP and the first CP establish a disaster recovery channel, and the group identification of the disaster recovery channel group is bound 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 establishing the disaster recovery channel by the existing main CP and standby CP, and is not repeated here.

In one example, the group identifier of the disaster recovery channel group included in the first configuration instruction is a disaster recovery channel group2, and the address parameter includes an IP address of the first CP and an IP address of the third CP. And 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 of the disaster recovery channel 2 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 comprises the name, the group identifier, the role and the UP identifier to be managed of the CP disaster recovery group.

And configuring the CP disaster backup group on the second CP according to the name, the group identifier and the role of the CP disaster backup group, wherein the CP disaster backup group has the name, the group identifier and the role, and the CP disaster backup group comprises an UP identifier to be managed.

In one example, the second CP configures the main CP disaster recovery group on the second CP according to the name, group identifier, and role of the CP disaster recovery group. For example, the name of the main CP disaster recovery group is group1, and the group identification is group-id 1.

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 comprises the name, the group identifier, the role of the CP disaster recovery group and the UP identifier to be managed.

And configuring a plurality of CP disaster backup groups on a third CP according to the backup type, the name of the CP disaster backup group, the group identifier and the role, wherein the CP disaster backup group has the name, the group identifier and the role, and the CP disaster backup group comprises the UP identifier to be managed.

In an example, if the backup type is 1+1 backup type, two CP disaster recovery groups are configured on the third CP, where one CP disaster recovery group is named group2, the group identifier is group-id2, and the role is main CP disaster recovery group; the name of the other CP disaster recovery group is group3, the group identification 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 identifier of the disaster recovery channel group and the group identifier of the CP disaster recovery group.

And the second CP binds the group identification of the disaster recovery channel group and the group identification of the CP disaster recovery group.

In one example, the second CP binds disaster recovery group1 with the group identification group1 of the main 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 identifier of the disaster recovery channel group and the group identifier of the CP disaster recovery group.

And the third CP binds the group identification of the disaster recovery channel group and the group identifications of the plurality of created CP disaster recovery groups.

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

The following description will be made by taking the first CP as an example:

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

And according to the IP address of the second CP, the first CP and the second CP establish a disaster recovery channel, and the group identification of the disaster recovery channel group is bound 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 establishing the disaster recovery channel by the existing main CP and standby CP, and is not repeated here.

In one example, the group identifier of the disaster recovery channel group included in the first configuration instruction is a disaster recovery channel group1, and the address parameter includes an IP address of the first CP and an IP address of the second CP. And 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 of the disaster recovery channel 1 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 a disaster recovery channel group2, 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 of the disaster recovery channel 2 is an IP address of a third CP (the third CP is one of the plurality of second CPs, and is described here as an example of the third CP). The disaster recovery channel 2 is bound with the disaster recovery channel group 2.

And the first CP receives a plurality of second configuration instructions input by the user again, 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 to be managed 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 identifier and the role, wherein each CP disaster recovery group has the name, the group identifier, the role and the provided backup type and comprises an UP identifier to be managed.

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 backup group is configured on the first CP, the name of the backup CP backup group is group1, and the group identifier is group-id 1.

In another example, if the backup type is 1+1 backup type, 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 name of the other CP disaster recovery group is group3, the group identification is group-id3, and the role is the main CP disaster recovery group.

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

And the first CP binds the group identification of the disaster recovery channel group with the group identification of at least one CP disaster recovery group.

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

In another example, if the backup type is 1+1 backup type, the first CP binds the disaster recovery channel group2 with the group identifier group2 of the backup CP disaster group and the group identifier group3 of the main CP disaster 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 locally bind the group identifier of the configured disaster recovery channel group and the group identifier of the CP disaster backup group, respectively, the UP indicated by the UP identifier in the CP disaster backup group establishes a CUSP channel with the CP where the main CP disaster backup group is located. The main and standby CP disaster backup groups inform the UP of the main and standby roles of the main and standby CP disaster backup groups through the CUSP channel. For UP, the CP in which the main CP disaster recovery group is located is the main CP, and the CP in which the backup CP disaster recovery group is located is the backup CP. Subsequently, the UP and the main CP perform interaction of the protocol packet and the service packet.

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 complete the user authentication and the application of the IP address, and the main CP generates a user table entry. The main CP sends down the user list item to UP through 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 carries out charging processing according to the statistical information.

The process from the UP and the main CP establishing the CUSP channel to the main CP sending the statistical information to the AAA server is the same as the existing process, and is only described briefly here.

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 or not through the heartbeat message.

Two second CPs (i.e., second CP, third CP) are taken as an example for explanation:

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 UP indicated by the UP identifier in the main CP disaster backup group and the second CP. Similarly, the third CP also generates a first heartbeat packet, where the first heartbeat packet includes a working state of the third CP or a first link failure rate between the third CP and the UP indicated by the UP identifier in the main CP disaster backup 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 failure rate of the first link from the heartbeat message.

In one implementation, if the working state of the CP is the unavailable state, the first CP determines that the second CP and the third CP are in failure, and performs the step.

In another implementation manner, the first CP obtains a second link failure rate between itself and the UP indicated by the UP identifier in the backup CP disaster backup group. If the first link failure rate is not less than a 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 performs this step.

Step 120, determining the backup type provided for each second CP and the group identifier of the backup CP disaster recovery group bound to the group identifier of the disaster recovery group according to the group identifier of the disaster recovery group.

Specifically, according to the description in step 110, after the first CP obtains the group identifier of the disaster recovery path 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 backup group bound to the group identifier of the disaster recovery path group are determined according to the group identifier of the disaster recovery path group.

Further, in an example, the group of the disaster tolerant channel group acquired by the first CP is identified as a disaster tolerant channel group 1. According to the disaster recovery channel group1, the first CP determines that the backup type provided by the first CP is a 1:1 backup type, and the group identifier of the backup CP disaster recovery group is group 1.

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

Step 130, 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 service for the UP corresponding to at least one UP identifier included in the backup CP disaster backup group.

Specifically, according to the description in step 120, after determining the backup type provided for each second CP and the group identifier of the backup CP disaster backup group, the first CP takes 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 provides service for the UP corresponding to at least one UP identifier included in the backup CP disaster backup group.

It can be understood that the first CP serves as a backup CP of the second CP, and the locally configured backup CP disaster backup group1 is the same as the main CP disaster backup group1 configured on the second CP, and both include the same UP flag.

Similarly, the first CP serves as a backup CP of the third CP, and the locally configured backup CP disaster backup group2 is the same as the main CP disaster backup group2 configured on the third CP, and both include the same UP identifier.

Therefore, the first CP can provide backup service for a plurality of failed main CPs at the same time, and can quickly take over the UP and the user service borne by the UP in the process of main-standby switching.

Therefore, by applying the backup implementation method provided by the present application, when multiple second CPs fail or a link between the UP indicated by the UP identifier in each second CP and the main CP disaster recovery group fails, the first CP obtains the group identifier of the disaster recovery channel group bound to the address of each second CP according to the address of each second CP; according to the group identification of the disaster tolerant 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 tolerant channel group; and according to the backup type, the first CP takes over the backup CP disaster recovery group and provides service for the UP corresponding to at least one UP identifier included in the backup CP disaster recovery group.

Another implementation method of backup provided in the embodiments of the present application is described in detail below. 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 the backup provided by the embodiment of the application may include the following steps.

Step 210, generating 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 the UP indicated by the UP identifier in the main CP disaster backup group.

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

Optionally, in this 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 the disaster recovery channel with the opposite end, configures the CP disaster recovery group locally, and binds the group identifier of the disaster recovery channel group with the group identifier of the CP disaster recovery group through the plurality of configuration instructions.

It should be noted that, in the foregoing embodiment, the process of receiving the configuration instruction of the second CP and the third CP serving as the main CP and performing local configuration according to the configuration instruction, and the process of interacting the heartbeat message with the first CP serving as the standby CP have been received in detail, and will not be repeated here.

The following describes in detail a method for implementing backup provided in the embodiments of the present application. Referring to fig. 3 and 4, fig. 3 is a schematic diagram of N:1 backup networking when multiple primary CPs provided by the embodiment of the present application normally operate, and fig. 4 is a schematic diagram of N:1 backup networking when multiple primary CPs provided by the embodiment of the present application fail.

The following description will be given taking an example in which three CPs are included in fig. 3 and 4.

1:1 backup is configured on CP1 and CP 3:

the CP1 receives a first configuration command input by a user, where the first configuration command includes a group identifier of the disaster tolerant group (disaster tolerant group1) and address parameters, and the address parameters include 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 command input by a user, where the first configuration command includes a group identifier of the disaster tolerant group (disaster tolerant group1) and address parameters, and the address parameters include an IP address (3.3.3.3) of the CP3 and an IP address (1.1.1.1) of the CP 1.

The CP1 and CP3 establish a disaster recovery channel 1 with the opposite end according to the IP address of the opposite end, and bind the group identifier of the disaster recovery channel group (disaster recovery channel group1) 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 establishing the disaster recovery channel by the existing main CP and standby CP, and is not repeated here.

The CP1 receives a second configuration command input by the user, the second configuration command includes a second group of parameters, the second group of parameters includes a name of the CP disaster recovery group (group1), a group identifier (group-id1), a role of the CP disaster recovery group (main CP disaster recovery group), and a UP identifier (UP1, UP2) of the admission management.

The CP3 receives a second configuration command input by the user, where the second configuration command includes a backup type and a second group of parameters, and the second group of parameters includes a name of the CP disaster recovery group (group1), a group identifier (group-id1), a role of the CP disaster recovery group (CP disaster recovery group), and a UP identifier (UP1, UP2) to be managed.

A main CP disaster recovery group with group identification of group-id1 and a backup CP disaster recovery group with group identification of group-id1 are respectively configured on the CP1 and the CP3, and the main and backup CP disaster recovery groups respectively comprise UP1 and UP 2.

The CP1 and CP3 both receive a third configuration command input by the user, where the third configuration command includes a group identifier of the disaster recovery channel group (disaster recovery channel group1) and a group identifier of the CP disaster recovery group (group-id 1).

The CP1 and the PC3 both bind the local disaster recovery group1 and the group-id 1.

1+1 backup is configured on CP2 and CP 3:

the CP2 receives a first configuration command input by a user, where the first configuration command includes a group identifier of the disaster tolerant group (disaster tolerant group 2) and address parameters, and the address parameters include 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 command input by a user, where the first configuration command includes a group identifier of the disaster tolerant group (disaster tolerant group 2) and address parameters, and the address parameters include an IP address (3.3.3.3) of the CP3 and an IP address (2.2.2.2) of the CP 2.

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

The CP2 receives a second configuration command input by a user, where the second configuration command includes a backup type and a second group of parameters, and the second group of parameters includes a name of a CP disaster recovery group (group2, group3), a group identifier (group-id2, group-id3), a role of the CP disaster recovery group (main CP disaster recovery group, backup CP disaster recovery group), and a UP identifier of a standby pipe (UP3, UP4, UP5, UP 6).

The CP3 receives a second configuration command input by a user, where the second configuration command includes a backup type and a second group of parameters, and the second group of parameters includes a name of a CP disaster recovery group (group2, group3), a group identifier (group-id2, group-id3), a role of the CP disaster recovery group (main CP disaster recovery group, backup CP disaster recovery group), and a UP identifier of a standby pipe (UP3, UP4, UP5, UP 6).

A main CP disaster recovery group with group identification of group-id2 and a standby CP disaster recovery group with group-id3 are configured on a CP2, wherein the main CP disaster recovery group comprises UP3 and UP4, and the standby CP disaster recovery group comprises UP5 and UP 6; a main CP disaster recovery group with group identification of group-id3 and a standby CP disaster recovery group with group-id2 are configured on a CP3, wherein the main CP disaster recovery group comprises UP5 and UP6, and the standby CP disaster recovery group comprises UP3 and UP 4.

The CP2 and the CP3 both receive a third configuration command input by the user, where the third configuration command includes a group identifier of the disaster recovery channel group (disaster recovery channel group 2) and a group identifier of the CP disaster recovery group (group-id2 and group-id 3).

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

In the embodiment of the present application, a disaster recovery channel group view is newly added in the CP3, a function of receiving a first configuration instruction, a second configuration instruction, and a third configuration instruction is added under the view, and a function of executing a corresponding action according to the first configuration instruction, the second configuration instruction, and the third configuration instruction is added. Thus, a plurality of CP disaster recovery groups can be configured on CP3, and the CP disaster recovery groups share one disaster recovery channel. In practical application, each CP can be added with a disaster recovery channel group view.

After each CP passes the configuration, the backup situation table is recorded locally.

Backup scenarios recorded in CP1 table 1:

table 1CP1 backup situation 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 (main) binding disaster tolerant channel group1

Backup scenarios recorded in CP2 table 2:

table 2CP2 backup situation 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 group	group2 (main) and group3 (standby) binding disaster tolerant channel group2

Backup scenarios recorded in CP3 table 3:

table 3CP3 backup situation 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 tolerant channel group1
		1+1 disaster recovery group	group2 (backup) and group3 (main) bound disaster recovery channel group2

After the foregoing configuration, the host goes online through CP1, CP2 as shown in FIG. 3. When the CP1 or CP2 fails, or the link between the CP1 and the UP fails, or the link between the CP2 and the UP fails, the CP3 determines the backup type provided for the CP1 and the CP2 and the group identifier of the backup CP disaster backup group according to the group identifier of the disaster recovery channel group. As shown in fig. 4, according to the backup type, the CP3 takes over group1 and group2 and provides service for the corresponding UP identified in group1 and group 2.

Based on the same inventive concept, the embodiment of the application also provides a backup implementation device corresponding to the backup implementation method. Referring to fig. 5, fig. 5 is a structural diagram of an implementation apparatus for backup provided in the embodiment of the present application. The device is applied to a first CP, the first CP is located in a first DC, the first CP comprises at least one backup CP disaster backup group, each backup CP disaster backup group and one main CP disaster backup group both comprise at least one same UP identifier, the main CP disaster backup group is located in a second CP, the second CP is located in a second DC, and the device comprises:

a first obtaining unit 510, configured to, when multiple second CPs have a failure or a link between a UP indicated by a UP identifier in each second CP and the main CP disaster recovery group has a failure, 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;

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

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

Optionally, the apparatus further comprises: a receiving unit (not shown in the figure), configured to receive a plurality of first configuration instructions input by a user, where each first configuration instruction includes a first group parameter for configuring different disaster recovery channel groups, each first group parameter 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 and a second group of parameters used for configuring different CP disaster recovery groups, and each second group of parameters includes a name, a group identifier, a role of a CP disaster recovery group, and an UP identifier to be managed;

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

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 a disaster recovery channel group and a group identifier of at least one CP disaster recovery group;

a binding unit (not shown in the figure), configured to perform a binding process on the group identifier of the disaster recovery channel group and the group identifier of the at least one CP disaster recovery group.

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

the device 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;

alternatively, the first and second electrodes may be,

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 main CP disaster backup group;

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

a second determining unit (not shown in the figure), configured to determine, 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, a link failure between the UP in each second CP and the main CP disaster backup group.

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, if the backup type is a 1+1 backup type, locally configure the main CP disaster recovery group and the backup CP disaster recovery group;

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

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

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

Therefore, by applying the backup implementation apparatus provided by the present application, when multiple second CPs fail or a link between the UP indicated by the UP identifier in each second CP and the main CP disaster recovery group fails, the first CP obtains the group identifier of the disaster recovery group bound to the address of each second CP according to the address of each second CP; according to the group identification of the disaster tolerant 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 tolerant channel group; and according to the backup type, the first CP takes over the backup CP disaster recovery group and provides service for the UP corresponding to at least one UP identifier included in the backup CP disaster recovery group.

Based on the same inventive concept, the embodiment of the application also provides a backup implementation device corresponding to the backup implementation method. Referring to fig. 6, fig. 6 is a structural diagram of another backup implementation apparatus provided in the embodiment of the present application. The device is applied to a first CP, where the first CP is located in a first DC, the first CP includes a main CP disaster backup group, both the main CP disaster backup group and a CP backup disaster backup group include at least one UP identifier, the CP backup disaster backup group is located in a second CP, and the second CP is located in a second DC, and the device includes:

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 a UP indicated by a UP identifier in a main CP disaster backup 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 backup group when determining that the first CP fails or a link between UPs indicated by the UP identifier in the main CP disaster backup group is failed according to the working state or the first link failure rate, and provides a service for a UP corresponding to at least one UP identifier included in the backup CP disaster backup group

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 group parameter for configuring a disaster recovery channel group, the first group parameter 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 building unit (not shown in the figure), configured to build 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 group of parameters for configuring the CP disaster recovery group, and the second group of parameters includes a name, a group identifier, a role of the CP disaster recovery group, and an UP identifier to be managed;

a configuration unit (not shown in the figure), configured to configure a CP disaster recovery group locally according to a name, a group identifier, and a 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 pipe to be managed;

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;

a binding unit (not shown in the figure), configured to perform a binding process on the group identifier of the disaster recovery channel group and the group identifier of the CP disaster recovery 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, if the backup type is a 1+1 backup type, respectively bind the group identifier of the disaster recovery channel group with the group identifier of the created main CP disaster backup group and the group identifier of the backup CP disaster backup group.

Based on the same inventive concept, the embodiment of the present application further 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 an implementation method of the backup provided by the embodiment of the present application. The N:1 backup implementation apparatus shown in fig. 5 and fig. 6 can be implemented by using a network device hardware structure shown in fig. 7.

The computer-readable storage medium 730 may include a Random Access Memory (RAM) or a Non-volatile Memory (NVM), such as at least one disk Memory. Optionally, the computer-readable storage medium 730 may also be at least one memory device located remotely from the processor 710.

The Processor 710 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

In the embodiment of the present application, the processor 710 reads the machine executable instructions stored in the machine readable storage medium 730, and the machine executable instructions cause the processor 710 to implement the method for implementing the backup described in the embodiment of the present application and the transceiver 720 to execute.

Additionally, the present embodiment provides a machine-readable storage medium 530, wherein the machine-readable storage medium 730 stores machine executable instructions, which 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 present embodiment.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.

For the embodiment of the implementation apparatus and the machine-readable storage medium for backup, since the content of the related method is substantially similar to that of the foregoing method embodiment, the description is relatively simple, and for the relevant points, reference may be made to part of the description of the method embodiment.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A method for implementing backup is applied to a first CP, the first CP is positioned in a first 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 positioned in a second CP, and the second CP is positioned in a second DC, the method comprises the following steps:

2. The method according to claim 1, wherein when multiple second CPs fail or a link between a UP indicated by a UP identifier in each second CP and the main CP disaster recovery group fails, before acquiring a group identifier of the disaster recovery group bound to the address of each second CP according to the 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 and an address parameter of a disaster recovery channel group, and the address parameters comprise an IP address of a second CP and an IP address of the first CP;

establishing a disaster tolerant channel with each second CP according to the IP address of the second CP, wherein the disaster tolerant channel is provided with a group identifier of the disaster tolerant 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 the name, group identification and role of the CP disaster recovery group and the UP identification to be managed;

according to the backup type, the name of the CP disaster backup group, the group identifier and the role, a plurality of CP disaster backup groups are configured locally, each CP disaster backup group has the name, the group identifier and the role and the provided backup type, and each CP disaster backup group comprises the UP identifier to be managed;

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 group.

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

receiving heartbeat messages sent by each second CP through a heartbeat channel, wherein the heartbeat messages comprise the working state of the second CP;

if the working state of the second CP is the unavailable state, determining that the second CP has a fault;

alternatively, the first and second electrodes may be,

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

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

and if the first link failure rate is not less than a preset failure threshold value and the second link failure rate is less than the failure threshold value, determining the link failure between each second CP and the UP in the main CP disaster backup 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 according to claim 5, wherein the locally configuring a plurality of CP disaster recovery groups according to the backup type, the name of the CP disaster recovery group, the group identifier, and the role specifically includes:

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

the binding the group identifier of the disaster recovery channel group and the group identifier of the at least one CP disaster recovery group specifically includes:

if the backup type is a 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. A method for implementing backup is applied to a first CP, the first CP is positioned in a first DC, the first CP comprises a main CP disaster backup group, both the main CP disaster backup group and a backup CP disaster backup group comprise the same at least one UP identifier, the backup CP disaster backup group is positioned in a second CP, and the second CP is positioned in the second DC, the method comprises the following steps:

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 comprises a group identifier and address parameters of the disaster recovery channel group, and the address parameters comprise an IP address of the second CP and an IP address of the first CP;

establishing a disaster tolerant channel with the second CP according to the IP address of the second CP, wherein the disaster tolerant channel has a group identifier of the disaster tolerant 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 comprises the name, the group identifier, the role of the CP disaster recovery group and the UP identifier to be managed;

according to the name, the group identifier and the role of the CP disaster backup group, locally configuring the CP disaster backup group, wherein the CP disaster backup group has the name, the group identifier and the role, and comprises the UP identifier to be managed;

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

and binding the group identification of the disaster recovery channel group with the group identification 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 any of claims 7-9, wherein the second configuration instructions further comprise backup types, the backup types comprising a 1:1 backup type and a 1+1 backup type.

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

the binding the group identifier of the disaster recovery channel group and the group identifier of the CP disaster recovery group specifically includes:

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

12. A device for implementing backup, where the device is applied to a first CP, the first CP is located in a first DC, the first CP includes at least one CP backup disaster recovery group, each CP backup disaster recovery group and a CP master disaster recovery group both include the same at least one UP identifier, the CP backup disaster recovery group is located in a second CP, and the second CP is located in a second DC, and the device includes:

13. A device for implementing backup, where the device is applied to a first CP, the first CP is located in a first DC, the first CP includes a main CP disaster backup group, both the main CP disaster backup group and a backup CP disaster backup group include at least one UP identifier, the backup CP disaster backup group is located in a second CP, and the second CP is located in a second DC, and the device includes: