Management method of main and standby systems and related device

Abstract

The invention provides a method and a device for managing main and standby systems, which can automatically execute main and standby switching according to the collected information of the main and standby systems, are favorable for improving the management efficiency of the main and standby systems, are optional, and are favorable for saving the labor cost, thereby reducing the management cost. In addition to indicating the connectivity of the heartbeat link, the information of the main and standby systems can also indicate the resource use conditions of the main and standby systems, so that faults caused by resource overload can be avoided, and the reliability of the main and standby systems is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to management methods and related devices for primary and backup systems. Background Technology

[0002] A primary / standby system, also known as an off-site disaster recovery system, is a high-availability solution designed to improve system reliability and availability. It establishes a master-slave relationship between two or more systems, where one system (the primary system) handles all business requests, while one or more other systems (backup systems) act as backups to the primary system, preventing service interruption in the event of a primary system failure. The core principle of a primary / standby system is data synchronization and failover, ensuring that the backup system can quickly take over services and guarantee business continuity when the primary system fails.

[0003] With the development of cloud technology, primary and backup systems are generally virtual resources (such as virtual machines or virtual services) running in data centers. Furthermore, primary and backup systems typically run in physically separated data centers to provide resilience against regional disasters. When a failover is required between the primary and backup systems, the system maintenance engineer (operator) needs to log into the backup system's user interface (UI) to perform the failover operation, resulting in low management efficiency for the primary and backup systems. Summary of the Invention

[0004] This application provides a management method and related apparatus for a primary / backup system, which improves the management efficiency of the primary / backup system.

[0005] Firstly, this application provides a management method for a primary / backup system. The method is applied to a system comprising one or more network devices, a first data center, and a second data center connected by communication. The first data center runs a first virtual resource of the primary / backup system, and the second data center runs a second virtual resource of the primary / backup system. The first and second virtual resources are used to provide the same service (referred to as a first service) in a primary state, with the first virtual resource in a primary state and the second virtual resource in a standby state. This method can be executed by a first communication device. In the method provided in the first aspect, the first communication device can acquire information about the primary / backup system, including information about the first virtual resource and / or the second virtual resource. Then, the first communication device can switch the primary / backup relationship between the first virtual resource and the second virtual resource based on the information from the primary / backup system. The first communication device automatically performs the primary / backup switch based on the collected information from the primary / backup system, which is beneficial for improving the management efficiency of the primary / backup system and, optionally, for saving labor costs, thereby reducing management costs.

[0006] Optionally, the first data center and the second data center are connected in communication, and the first data center is connected in communication with all or some of the network devices in one or more network devices, and the second data center is connected in communication with all or some of the network devices in one or more network devices.

[0007] Optionally, the first and second data centers can be located in different regions or at physically separate sites.

[0008] Optionally, in the first and second virtual resources, the virtual resource in primary (or production) state is used to provide the first service, while the virtual resource in standby (or disaster recovery) state is used to provide protection or backup for the virtual resource in production. The first and second virtual resources provide the same service, which can be understood as having the same function or role (in primary state). This application does not limit the type of the first service; for example, the first service can be a deep packet inspection (DPI) service.

[0009] Optionally, in this application, switching the primary / standby relationship between the first virtual resource and the second virtual resource can mean that the first virtual resource is in standby mode and the second virtual resource is in primary mode.

[0010] In one possible implementation of the first aspect, the information of the first primary / backup system includes at least one of first information, second information, or third information. The first information indicates the connectivity of a communication link used to transmit service data of the first virtual resource; the second information indicates the connectivity of at least one heartbeat link, including a heartbeat link between the first virtual resource and the second virtual resource and / or at least one heartbeat link between the network device and the first virtual resource; and the third information indicates the performance of the first resource, which includes information technology (IT) resources allocated to the first virtual resource.

[0011] In addition to performing primary / backup switching based on communication links or heartbeat links, the first communication device can also perform primary / backup switching based on the performance of the resources allocated to the virtual resources, thereby helping to avoid a virtual resource from failing due to overload.

[0012] Optionally, the business data of the first virtual resource may include request data (or business requests) for accessing the services provided by the first virtual resource and / or service response data (or business responses) to the request data. IT resources may be replaced by physical resources. IT resources may include at least one of computing resources, storage resources, and network resources. The performance of IT resources includes the utilization rate of IT resources and / or the size (or available size) of IT resources.

[0013] In one possible implementation of the first aspect, the first virtual resource includes one or more first virtual components, and the performance of the first resource includes the performance of the resources allocated to each of the at least one first virtual component. This helps to prevent the first virtual resource from failing to provide the first service due to the failure of some virtual components (e.g., server components), thereby improving the reliability of the first primary / backup system.

[0014] Optionally, the third information may include the identifier of each of the first virtual components and the performance (or state of the state machine) of the resource.

[0015] Optionally, third-party information can be carried in the heartbeat message. For example, the option or tag length value (TLV) field of the heartbeat message can include third-party information. In this way, the heartbeat message is no longer limited to the basic functions of detecting heartbeats or keeping alive, nor is it limited to detecting link connectivity, but also has the ability to detect the performance of virtual resources or virtual components.

[0016] In one possible implementation of the first aspect, the third information indicates that the performance of the resources of at least one target virtual component in the first virtual component is inferior to a first performance threshold. Before switching the primary / backup relationship between the first virtual resource and the second virtual resource based on the information of the first primary / backup system, in the method provided in the first aspect, the first communication device can send a prompt message indicating that the resources of the target virtual component should be optimized. For example, the first communication device can send a prompt message to the terminal device used by the user to prompt the user to optimize the resources of the target virtual component. This is beneficial for solving the resource problem of the target component. When there are no other switching reasons (e.g., no link failure) and the resources of the target component are successfully expanded, the primary / backup relationship between the first virtual resource and the second virtual resource does not need to be switched, thus reducing the number of primary / backup switches and saving system resources.

[0017] In one possible implementation of the first aspect, switching the primary / backup relationship between the first virtual resource and the second virtual resource based on information from the first primary / backup system can be understood as switching the primary / backup relationship between the first virtual resource and the second virtual resource based on the information from the first primary / backup system satisfying a first condition. The first condition includes at least one of the following: the connectivity indicated by the first information is worse than a first connectivity threshold; the connectivity indicated by the second information is worse than a second connectivity threshold; or, the performance of the target resource indicated by the third information is worse than a performance threshold.

[0018] Optionally, the information of the first primary / backup system also includes the mastering capability information of the second virtual resource. This mastering capability information indicates the mastering capability of the second virtual resource or its ability to provide the first service as a primary device. The mastering capability information of the second virtual resource may indicate at least one of the following: the connectivity of the heartbeat link between the second virtual resource and the network device, the connectivity of the heartbeat link between the first and second virtual resources, or the performance of the second resource. Here, the second resource refers to the IT resource allocated to the second virtual resource.

[0019] Optionally, the first condition also includes the second virtual resource's ability to provide the first service, as indicated by the mastering capability information of the second virtual resource, being better than the capability threshold.

[0020] In one possible implementation of the first aspect, the first communication device can be a first network device among one or more of the network devices. The system further includes a communication device (referred to as a management device), which is connected to each of the one or more network devices. In this method, the first network device can send fourth information to the management device, the fourth information indicating a switch between the primary and backup relationships of the first virtual resource and the second virtual resource. The management device is used to send notification information to other network devices among the one or more network devices besides the first network device, based on the fourth information. The notification information indicates a switch between the primary and backup relationships of the first virtual resource and the second virtual resource. In this way, the first network device can, based on its arbitration result (i.e., performing a primary / backup switch on the first primary / backup system), notify other network devices through the management device to perform a primary / backup switch on the first primary / backup system in advance, thereby enabling proactive fault detection and prevention.

[0021] Optionally, the system includes N network devices. After receiving the fourth information sent by the first network device, the management device can, based on receiving the fourth information from M network devices, send notification information to the network devices other than these M network devices among the N network devices. This helps improve the reliability of primary / backup switching. Here, N is an integer greater than 1, and M is a positive integer less than N. In this way, the management device can, based on the arbitration results completed by some of the N network devices (i.e., performing primary / backup switching on the first primary / backup system), notify other network devices to perform primary / backup switching on the first primary / backup system in advance, enabling proactive fault detection and prevention.

[0022] Optionally, the management device is a third-party network management center or is deployed within a third-party network management center. This application does not limit the type of third-party network management center; for example, the third-party network management center can be a network cloud engine (NCE). In this application, the third-party network management center can also be referred to as a third-party management center.

[0023] In one possible implementation of the first aspect, the system further includes a communication device (e.g., a management device), wherein the first communication device described above can be the management device. The management device is connected to one or more of the network devices. In this method, the management device sends fifth information to each of the one or more network devices, the fifth information indicating a switch between the primary / standby relationship between the first virtual resource and the second virtual resource.

[0024] In this application, after receiving information (such as the notification information or the fifth information described above) indicating the switching of the primary / standby relationship between the first virtual resource and the second virtual resource, the network device can switch the primary / standby relationship between the first virtual resource and the second virtual resource.

[0025] In this application, based on the premise that the first virtual resource is in a primary state and the second virtual resource is in a standby state, the network device can switch the primary / standby relationship between the first and second virtual resources in various ways. For example, the network device can record that the first virtual resource is in a standby state and that the second virtual resource is in a primary state. Alternatively, the network device can send a first switchover instruction to the first virtual resource and a second switchover instruction to the second virtual resource, wherein the first switchover instruction indicates that the state of the first virtual resource be switched to a standby state, and the second switchover instruction indicates that the state of the second virtual resource be switched to a primary state.

[0026] In this application, based on the first virtual resource being in a primary state and the second virtual resource being in a standby state, the management device can switch the primary / standby relationship between the first and second virtual resources in various ways. For example, the management device can record that the first virtual resource is in a standby state and that the second virtual resource is in a primary state. For example, the network device can send a first switching instruction to the first virtual resource and a second switching instruction to the second virtual resource, wherein the first switching instruction is used to indicate that the state of the first virtual resource be switched to a standby state, and the second switching instruction is used to indicate that the state of the second virtual resource be switched to a primary state.

[0027] Optionally, after receiving a switching instruction (first switching instruction or second switching instruction), the virtual resource may send a status notification to the connected network device to indicate the switching of the primary / standby relationship between the first and second virtual resources.

[0028] In one possible implementation of the first aspect, the method involves a first communication device triggering data synchronization between the first and second virtual resources before switching the primary / backup relationship between the first and second virtual resources based on information from the first primary / backup system. This facilitates the normal provision of the first service by the second virtual resource, which is in a primary state, after the primary / backup relationship between the first and second virtual resources is switched.

[0029] In this application, the first communication device triggers the first virtual resource and the second virtual resource to perform data synchronization. This can be understood as the first communication device sending a first synchronization instruction and a second synchronization instruction to the first virtual resource and the second virtual resource, respectively. The first synchronization instruction and the second synchronization instruction are used to instruct the first virtual resource and the second virtual resource to perform data synchronization. For example, the first synchronization instruction is used to instruct the first virtual resource to send synchronization data to the second virtual resource, and the second synchronization instruction is used to instruct the second virtual resource to receive the synchronization data sent by the first virtual resource.

[0030] In one possible implementation of the first aspect, a third virtual resource of a second primary / backup system also runs on the first data center, and a fourth virtual resource of the second primary / backup system also runs on the second data center. The third virtual resource is in a standby state, and the fourth virtual resource is in a primary state. The third virtual resource and the fourth virtual resource are used to provide the same service (referred to as the second service) in the primary state.

[0031] In this way, before switching the primary / standby relationship between the first virtual resource and the second virtual resource, for either the first data center or the second data center, it not only runs the virtual resource in the primary state but also runs the virtual resource in the standby state. This helps to balance the resource utilization of the two data centers, thereby helping to avoid the resource allocation to the virtual component being too poor due to the excessive resource utilization of one data center, and thus helping to ensure the performance of the services provided by the primary / standby system.

[0032] In one possible implementation of the first aspect, the first virtual resource and the second virtual resource each include one or more virtual instances or one or more virtual services running on one or more virtual instances. This application does not limit the implementation of the virtual instances; for example, a virtual instance may be a virtual machine (VM), a container, or a bare metal server.

[0033] Secondly, this application provides a management method for a primary / backup system. The method is applied to a system including one or more network devices, a first data center, and a second data center connected by communication. The method can be executed by a second communication device. In this method, the second communication device can receive configuration information, and then, based on the configuration information, create a first virtual resource for the first primary / backup system and a second virtual resource for the second primary / backup system based on the resources of the first data center. The first primary / backup system also includes a third virtual resource created based on the resources of the second data center, and the second primary / backup system also includes a fourth virtual resource created based on the resources of the second data center. The first virtual resource and the second virtual resource are respectively in a production state and a disaster recovery state, and the third virtual resource and the fourth virtual resource are respectively in a disaster recovery state and a production state. The first virtual resource and the third virtual resource in the first primary / backup system are used to provide the same service (e.g., a first service) in the primary state, and the second virtual resource and the fourth virtual resource in the second primary / backup system are used to provide the same service (e.g., a second service) in the primary state.

[0034] In this way, for either the first or second data center, it operates not only virtual resources in primary mode but also virtual resources in standby mode. This helps to balance the resource utilization of the two data centers, effectively achieving load balancing between them. This helps prevent the performance of resources allocated to virtual components from being poor due to excessive resource utilization in one data center, thus ensuring the performance of services provided by the primary and standby systems. Optionally, when faced with a large number of service requests, load balancing between the two data centers can effectively alleviate the service communication pressure on one or more network devices, effectively reducing network problems caused by service congestion.

[0035] In one possible implementation of the second aspect, the first virtual resource and the second virtual resource in the first primary / backup system are respectively bound to the interface of the first network device in one or more of the network devices; the second virtual resource and the fourth virtual resource in the second primary / backup system are respectively bound to the interface of the second network device in one or more of the network devices.

[0036] Optionally, the system may also include a management unit, which is connected to each network device.

[0037] Optionally, the second communication device may be a management device or deployed in the same computer device as the management device, or the second communication device may be deployed on the first data center, for example, the second communication device may be the management platform of the first data center.

[0038] Thirdly, this application provides a computer device including a memory and a processor, the processor being configured to execute instructions stored in the memory to cause the computer device to perform the method as described in the first aspect or any implementation thereof.

[0039] Fourthly, this application provides a computing device cluster, including at least one computing device, each computing device including a memory and a processor; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the computing device cluster to perform the method as described in the first aspect or any implementation thereof, or the second aspect or any implementation thereof.

[0040] Fifthly, this application provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the processor performs the method described in the first aspect or any implementation thereof, or the second aspect or any implementation thereof.

[0041] In a sixth aspect, this application provides a computer program product containing program code that, when executed by a computer device, implements the method described in the first aspect or any implementation thereof, or the second aspect or any implementation thereof.

[0042] In a seventh aspect, this application provides a system comprising one or more communication devices, a first data center and a second data center connected in communication, wherein at least one of the communication devices is configured to perform the method as described in the first aspect or any implementation thereof, and / or the first data center is configured to perform the method as described in the second aspect or any implementation thereof.

[0043] Eighthly, this application provides a chip system including a processor and an interface circuit. The processor is coupled to a memory via the interface circuit. The processor executes program code in the memory to perform the methods described in the first aspect or any implementation thereof, or the second aspect or any implementation thereof. The chip system may be composed of chips or may include chips and other discrete devices.

[0044] Ninthly, this application provides a communication device, which can be the first communication device described in the first aspect. The first communication device is applied to a system including one or more network devices, a first data center and a second data center connected in communication. The first data center runs a first virtual resource of a first primary / backup system, and the second data center runs a second virtual resource of the first primary / backup system. The first virtual resource and the second virtual resource are used to provide the same services in a primary state, with the first virtual resource in a primary state and the second virtual resource in a standby state.

[0045] The first communication device includes a transceiver module and a processing module. The transceiver module is used to acquire information about the first primary / backup system, which includes information about the first virtual resource and / or the second virtual resource. The processing module is used to switch the primary / backup relationship between the first virtual resource and the second virtual resource based on the information from the first primary / backup system.

[0046] Information about the primary and backup systems, the first virtual resources, and the performance of the first virtual resources can be understood by referring to the relevant content in the first aspect or possible implementations of the first aspect.

[0047] Optionally, the processing module is specifically used to switch the primary / standby relationship between the first virtual resource and the second virtual resource based on the information from the first primary / standby system meeting a first condition. The first condition can be understood by referring to the relevant content in the first aspect.

[0048] Optionally, the communication device is a first network device among one or more network devices, and the system further includes a management device. The transceiver module is further configured to send fourth information to the management device, the fourth information being used to indicate a switch between the primary / standby relationship between the first virtual resource and the second virtual resource. The management device is configured to send notification information to the other network devices among the one or more network devices besides the first network device according to the fourth information, the notification information indicating a switch between the primary / standby relationship between the first virtual resource and the second virtual resource.

[0049] Optionally, the system further includes a management device, which can be the communication device. The management device is connected to one or more of the network devices respectively. The transceiver module is also used to send fifth information to the one or more network devices respectively. The fifth information is used to indicate the switching of the primary / standby relationship between the first virtual resource and the second virtual resource.

[0050] Optionally, before the processing module switches the primary / backup relationship between the first virtual resource and the second virtual resource based on the information of the first primary / backup system, the transceiver module is also used to trigger the first virtual resource and the second virtual resource to perform data synchronization.

[0051] Optionally, the first data center also runs a third virtual resource of the second primary / backup system, and the second data center also runs a fourth virtual resource of the second primary / backup system. The third virtual resource is in standby mode, and the fourth virtual resource is in primary mode. The third virtual resource and the fourth virtual resource are used to provide the same services in primary mode.

[0052] Optionally, the first virtual resource and the second virtual resource each include one or more virtual instances or one or more virtual services running on one or more virtual instances.

[0053] Tenthly, this application provides a communication device, which can be the second communication device described in the second aspect. This communication device can be applied to a system including one or more network devices, a first data center, and a second data center connected in communication. The communication device may include a transceiver module and a processing module. The transceiver module is used to receive configuration information. The processing module is used to create, based on the configuration information and the resources of the first data center, a first virtual resource for a first primary / backup system and a second virtual resource for a second primary / backup system. The first primary / backup system further includes a third virtual resource created based on the resources of the second data center, and the second primary / backup system further includes a fourth virtual resource created based on the resources of the second data center. The first virtual resource and the second virtual resource are respectively in a production state and a disaster recovery state, and the third virtual resource and the fourth virtual resource are respectively in a disaster recovery state and a production state. The first virtual resource and the third virtual resource in the first primary / backup system are used to provide the same service in the primary state, and the second virtual resource and the fourth virtual resource in the second primary / backup system are used to provide the same service in the primary state.

[0054] Optionally, the first virtual resource and the second virtual resource in the first primary / backup system are respectively bound to the interface of the first network device in one or more of the network devices.

[0055] Optionally, the second virtual resource and the fourth virtual resource in the second primary / backup system are respectively bound to the interface of one or more of the second network devices in the network devices.

[0056] Since the devices provided in this application can be used to execute the aforementioned corresponding methods, the technical effects and technical details that can be obtained by the devices in this application can be referred to the technical effects obtained by the aforementioned corresponding methods, and will not be repeated here. Attached Figure Description

[0057] Figure 1 This diagram illustrates a possible architecture for a single-backend system.

[0058] Figure 2-1 and Figure 2-2 Schematic diagrams of the system, including the primary and backup systems, are shown separately.

[0059] Figure 3-1 This schematically illustrates a system architecture that includes a primary and backup system.

[0060] Figure 3-2 and Figure 3-3 The possible contents of a heartbeat message are illustrated below;

[0061] Figure 4-1 and Figure 4-2The diagrams illustrate scenarios 1 and 2 of primary / standby switching, respectively.

[0062] Figure 5 This schematically illustrates one possible workflow for the management methods implemented at the front end;

[0063] Figure 6 This illustration shows one possible process for managing the primary and backup systems in Scenario 1.

[0064] Figure 7 This illustration shows one possible process for managing the primary and backup systems in Scenario 2.

[0065] Figure 8 This illustration shows another possible process of the method described in this application;

[0066] Figure 9-1 and Figure 9-2 The system architecture, including a dual-plane primary and backup system, is illustrated schematically.

[0067] Figure 10 The diagram illustrates the resource usage of a single-plane primary / standby system and a dual-plane primary / standby system.

[0068] Figure 11 This schematically illustrates one possible structure of a computing device;

[0069] Figure 12 This illustration schematically shows one possible structure for a cluster of computing devices;

[0070] Figure 13 This illustration shows the connection methods in a cluster of computing devices. Detailed Implementation

[0071] First, let me explain the meaning of some of the terms used in this application.

[0072] A virtual machine (VM) is a complete computer system with full hardware system functionality, running in a completely isolated environment, modeled through software. Any task that can be performed on a physical computer can also be performed in a VM. When creating a VM, a portion of the physical computer's hard drive and memory capacity is used as the VM's hard drive and memory. Each VM has its own independent hard drive and operating system, and can be operated just like a physical machine.

[0073] A container is a virtualization technology in computer operating systems that allows processes to run in a relatively independent and isolated environment (including an independent file system, namespace, resource view, etc.). This simplifies the software deployment process, enhances software portability and security, and improves the utilization of system resources. Container technology is widely used in service-oriented scenarios in the cloud computing field.

[0074] Virtual resources can be virtual instances, which include at least one of the following: virtual machines, containers, or bare metal servers. A virtual instance can run one or more applications (or virtual services) based on allocated IT resources.

[0075] The Remote Authentication Dial in User Service (RADIUS) system typically places clients on network attached storage (NAS) devices, which can be distributed throughout the network. It is responsible for transmitting user information to a designated RADIUS server and then processing the information returned from the server accordingly (such as accepting or rejecting user access).

[0076] A data center typically consists of one or more servers. Figure 1 This illustration only shows three servers in data center 1, which may include more or fewer servers. A server is an IT device that can provide IT resources. Optionally, IT resources include at least one of computing resources, storage resources, and network resources. One or more servers in data center 1 may run one or more virtual resources, which may be virtual instances or virtual services. It is assumed that virtual resource 1 in data center 1 can be used to provide one or more services (referred to as service 1). This application does not limit the type of service 1; for example, service 1 may include one or more of the following: traffic analysis, VoIP service monitoring, shared access monitoring, P2P service monitoring, user behavior analysis, or web push services.

[0077] Virtual resource 1 will be referred to as backend 1 in the following text. For example... Figure 1 As shown, the backend 1 can communicate with the frontend 1 to transmit service data. This service data may include a request message (or service request) forwarded by the frontend 1 to the backend 1 for accessing service 1, and / or a response message (or service response) sent by the backend to the frontend in response to the request. The frontend can be a network device; this application does not limit the type of network device. For example, the network device may include, but is not limited to, at least one of a gateway, switch, and router. The network device can be a physical device or a virtual device. In addition to establishing a link (referred to as a communication link) for transmitting service data, the backend 1 and the frontend 1 can also establish a link (referred to as a heartbeat link) for transmitting heartbeat messages. In the accompanying drawings, a dashed line with an arrow represents the heartbeat link, and a solid line with an arrow represents the communication link. When the backend 1 is unavailable, the heartbeat link malfunctions, and the backend 1 cannot provide the service; for example, it cannot receive service requests from the frontend 1 or cannot process service requests forwarded by the frontend.

[0078] Off-site disaster recovery systems, or primary / backup systems, are high-availability solutions designed to improve system reliability and availability. They establish a master-slave relationship between two or more systems, where one system (the primary system) handles all business requests, while one or more other systems (backup systems) act as backups to the primary system, preventing service interruption in the event of a primary system failure. The core principle of a primary / backup system is data synchronization and failover, ensuring that the backup system can quickly take over services and guarantee business continuity when the primary system fails.

[0079] Figure 2-1 and Figure 2-2 Schematic diagrams of systems including primary and backup systems are shown separately. For example... Figure 2-1 As shown, the system includes data centers 1 and 2, located at two physically separated sites (site 1 and site 2). Backend 1 runs on data center 1, and backend 2 runs on data center 2. Backend 1 and backend 2 have the same function or are both used to provide service 1, enabling resilience against regional disasters. Optionally, backend 1 and backend 2 are mirror images of each other. One backend is in active (or primary) mode, and the other is in standby (or backup) mode. Data synchronization, health monitoring, and function switching can be performed between backend 1 and backend 2. In the accompanying drawings, bold solid lines with arrows represent links used for transmitting synchronization data (called synchronization links). Backend 1 can send synchronization data traffic to backend 2 through the links represented by the bold solid lines, and communication traffic (e.g., service data) can be transmitted between backend 1 and frontend 1 through communication links corresponding to solid lines with bidirectional arrows. Figure 2-2 As shown, when backend 1 in data center 1 stops working due to an accident (such as fire, earthquake, equipment failure, human error, etc.), the entire application of business 1 can be switched to backend 2 in data center 2, so that business 1 can be resumed without interruption or in a short time, thereby ensuring the continuity of business 1 and the reliability of data. In this application, the backend in the primary state can also be called the production center, and the backend in the standby state can also be called the disaster recovery center.

[0080] As an example, the system provided in this application can be a Service Intelligence Gateway (SIG) system. The SIG system focuses on experience monetization and is committed to the commercial success of customers' fixed broadband (FBB) networks. With the rapid growth of home broadband users over the past two years, experience upgrades have become a new driving force for operators' home broadband services. SIG's key capabilities (such as proactive maintenance / network element quality analysis / precise home profiling / artificial intelligence (AI) learning and other detection technologies) can assist in providing intelligent and flexible service control methods to help commercial success. The SIG testing system includes a converged SA card-based intelligent broadband remote access server (iBRAS), operator standard edge (PE) card-based service awareness (SA), and standalone mode. The deep packet inspection (DPI) testing system can, in a sense, refer to the SIG testing system.

[0081] The off-site disaster recovery of the SIG system specifically refers to the off-site disaster recovery of the SIG backend (i.e., the versatile business platform, VBP). This is achieved by establishing two identical, one-to-one mirrored backends at two physically separated sites to withstand regional disasters. One backend is operational, while the other is in standby mode, allowing for data synchronization, health monitoring, and function switching between them. If one backend stops working due to an unexpected event (such as fire, earthquake, equipment failure, or human error), the entire application can switch to the other backend, enabling rapid business recovery and ensuring data reliability.

[0082] Figure 3-1 The system structure is illustrated schematically. For example... Figure 3-1 As shown, the production center and disaster recovery center each include multiple virtual components. Figure 3-1Taking multiple virtual components, including a RADIUS proxy server (RPD), a database (DB), a Hadoop distributed file system (HDFS), and a system general management server (SGMS), as an example, this application does not limit the number and type of virtual components in the production center and disaster recovery center. The main functions of RPD include user authentication, user authorization, and accounting management. DB can be a Gauss Database, which can efficiently and systematically store data, enabling faster and more convenient data management. HDFS refers to a distributed file system designed to run on commodity hardware. SGMS is used to monitor the status of each component in the background and can also provide time synchronization services for the primary and backup systems. The primary and backup systems 1 can include the background systems 1 and 2 described above.

[0083] like Figure 3-1 As shown, the production center and disaster recovery center can connect to front-end 1, and also to multiple front-ends, such as front-end 2 to front-end N. N can be a positive integer. The front-end can detect the status of the back-end in real time via a heartbeat link and prioritizes the production center for processing business data. When the production center is unavailable, the front-end will use the disaster recovery center to process data to ensure normal business processing. The production center and disaster recovery center detect each other's system availability in real time via a heartbeat link between their respective SGMS. When both the production center and disaster recovery center are functioning normally, data from the production center will be synchronized to the disaster recovery center, and data from the disaster recovery center's RPD can also be synchronized to the production center's RPD. When an anomaly is detected, the front-end can report an alarm, and the system maintenance engineer can manually perform a switchover operation through the disaster recovery center's back-end user interface (UI). After the switchover operation is completed, the original disaster recovery center continues to provide services.

[0084] The system uses the connectivity (or heartbeat connection status) of the heartbeat link to detect status. Based on the status detection results, the front-end and back-end, and the production center and disaster recovery center adjust data flow, control data synchronization, and select whether to report alarms, thereby achieving off-site disaster recovery capabilities. These are described in detail below. Figure 3-1 The detection process of various heartbeat links in China.

[0085] For example, the availability of the SGMS between the production center and the disaster recovery center can be determined through real-time detection of the heartbeat link (or heartbeat connection). This application does not limit the detection period of the heartbeat link (hereinafter referred to as the heartbeat detection period). As an example, the heartbeat detection period between SGMS can be 20 seconds. When the SGMS reports an alarm after 6 consecutive abnormal heartbeat detection results, the SGMS can display an alarm indicating that the remote device is unavailable on the local backend UI.

[0086] For example, the front-end can detect the availability of the back-end through a heartbeat link and determine which back-end is currently in use. This application does not limit the heartbeat detection period. As an example, the heartbeat detection period between the front-end and back-end SGMS can be 3 seconds (default value, which can be manually adjusted to an integer value between 3 and 9 seconds). When the heartbeat detection is abnormal for 9 consecutive seconds (default value, which can be manually adjusted to an integer value between 9 and 300 seconds), the front-end can report an alarm and display the status of the SGMS as abnormal or down on the front-end.

[0087] For example, the RPDs in the production center and the disaster recovery center use a heartbeat connection to monitor the availability of the other end in real time. This application does not limit the heartbeat detection period; for example, the heartbeat detection period between RPDs can be 3 seconds. When the heartbeat detection is abnormal for 15 consecutive seconds, the system can stop data synchronization between the production center RPD and the disaster recovery center RPD.

[0088] For example, the front-end can also detect the availability of RPDs via heartbeat connections and automatically determine the currently used RPD. This application does not limit the heartbeat detection period. As an example, the heartbeat detection period between the front-end and the RPD is 3 seconds (default value, which can be manually adjusted to an integer value between 3 and 9 seconds). When the heartbeat detection is abnormal for 9 consecutive seconds (default value, which can be manually adjusted to an integer value between 9 and 300 seconds), the front-end can report an alarm and display the status of the RPD as abnormal on the front-end. If the abnormal RPD belongs to the production center, the front-end can select the RPD in the disaster recovery center to provide services.

[0089] Optionally, if the production center and disaster recovery center are disconnected for more than a certain period of time (e.g., 24 hours), data synchronization between the two centers can be stopped, and SGMS can report an alarm. If data synchronization is required to be re-established, the disaster recovery relationship (or primary / standby relationship) must be terminated before it can be re-established.

[0090] When it's necessary to switch the primary / standby relationship between different backend systems in a primary / standby configuration, the system maintenance engineer (operator) needs to log in to the disaster recovery center's backend UI and execute the switchover operation. Both the production center and the disaster recovery center check their own status (abnormal or normal) and the connectivity of the heartbeat link, etc. Afterwards, both the production center and the disaster recovery center return the check results to the system maintenance engineer. The system maintenance engineer then determines whether to execute the switchover operation based on the check results. The switchover operation refers to changing the primary / standby relationship between different backend systems, such as switching a backend system that was originally in primary status to standby status, and vice versa. This switchover operation can be a normal switchover or an abnormal switchover. Normal switchovers are generally used for backend upgrade and cutover scenarios, while abnormal switchovers are generally used for production center failure scenarios.

[0091] Existing primary / standby system management methods cannot achieve automatic switching of primary / standby relationships between different backend systems. Even if a backend system in standby mode has synchronized data with the primary backend system, the need for system maintenance engineers to manually switch the primary / standby relationship results in low operational efficiency and impacts fault detection time. Furthermore, this approach does not meet the 99.999% reliability requirements of telecom operators.

[0092] Therefore, this application proposes that the front-end can obtain information about the primary and backup systems, and execute the primary and backup relationships between different back-end systems based on the information about the primary and backup systems, so as to realize the automatic switching of the primary and backup relationships and improve the management efficiency of the primary and backup systems.

[0093] The information for the primary and backup systems may include communication link information and / or heartbeat link information of the production center. Specifically, the communication link information indicates the connectivity between the front-end and the production center, while the heartbeat link information indicates the connectivity between the front-end and the production center. The communication link information can be understood by referring to the first piece of information described above, and the heartbeat link information can be understood by referring to the second piece of information described above.

[0094] Analysis revealed that even if individual components (or virtual components) in the production center fail, it is generally difficult to trigger a switchover between the primary and backup systems if the communication and heartbeat links are functioning normally, thus limiting the performance of the services provided by the primary and backup systems.

[0095] Therefore, this application proposes that the information obtained by the front-end from the primary and backup systems, in addition to the communication link information and / or heartbeat link information of the production center, may also include the status information (or state machine status) of the production center. The status information of the production center is used to indicate the status of the production center, and the status of the production center may include the health status of the production center and / or the performance of its resources. The status information of the production center may include health information and / or resource information. The health information of the production center is used to indicate the health status (normal or abnormal). The resource information of the production center is used to indicate the performance of the IT resources allocated to the production center; the resource information can refer to the third information described above.

[0096] Optionally, the information for the primary / backup system also includes the disaster recovery center's ability to become the primary device. This ability information indicates the disaster recovery center's capacity to become the primary device or its ability to provide services as the primary device. The disaster recovery center's ability to become the primary device may include at least one of the following: heartbeat link information, information about the link between the primary and backup systems, or the disaster recovery center's status information. The heartbeat link information indicates the connectivity of the heartbeat link between the front-end and the production center. The information about the link between the primary and backup systems indicates the connectivity of the communication link and / or heartbeat link between the production center and the disaster recovery center, which can be used to transmit synchronization data. The disaster recovery center's status information includes its health information and / or resource information. The health information indicates the disaster recovery center's health status (normal or abnormal). The resource information indicates the performance of the IT resources allocated to the disaster recovery center.

[0097] Optionally, the resource information in the backend is used to indicate the resources allocated by the backend to each of the one or more virtual components. This backend can be a production center or a disaster recovery center. For example, the status information in the backend may include the status information of each virtual component in at least one virtual component. The status information of a virtual component may include the identifier and status of the virtual component (or the state of the virtual component's state machine). The status of a virtual component includes its health status and resource performance. This at least one virtual component can be all or some of the virtual components in the backend, for example, including key virtual components in the backend.

[0098] Optionally, backend status information can be carried in heartbeat messages. For example, the status information of the production center and / or disaster recovery center can be carried in heartbeat messages. For instance, the option or tag length value (TLV) field of the heartbeat message can include the status information of the production center. In this way, heartbeat messages are no longer limited to the basic functions of detecting heartbeats or keep-alive, nor are they limited to detecting link connectivity; they also have the ability to detect the status of virtual resources or virtual components. Thus, heartbeat messages have evolved from simply detecting connectivity to being able to check not only connectivity but also the state of the backend or its virtual component's state machine. This allows the frontend to determine whether to switch the primary / standby relationship between different backends based on the connectivity check results and the status information of the backend or its virtual components.

[0099] For example, the status information in the background can include the status information of the database, the status information of HDFS, and the status information of the data collector. Figure 3-2 and Figure 3-3 The contents of the heartbeat message provided in this application are illustrated schematically, and the heartbeat message can be... Figure 3-1 The heartbeat message of any heartbeat link shown (e.g., heartbeat message between SGMS). Figure 3-2 As shown, compared to the original heartbeat message, the heartbeat message provided in this application may include virtual component status information. This status information may include a type field, a length field, and a value field. The type field indicates the type of the virtual component or serves as its identifier. Different values ​​of the type field indicate different virtual components. For example, when the type field value is 0x01, the status information is for the DB (Database); when it is 0x02, it is for HDFS (HDFS); and when it is 0x02, it is for the data collector. The length field in the status information indicates the length of the value field. The value of the value field indicates the status of the virtual component. For example, when the value field value is 0, it indicates that the corresponding virtual component is in a normal (up) state; when the value field value is 1, it indicates that the corresponding virtual component is in an abnormal (down) state.

[0100] A virtual resource or component being in a "normal" state can be understood as the virtual resource or component being in good health and / or its performance being better than a performance threshold. A virtual component being in an "abnormal" state can be understood as the virtual resource or component being in an abnormal health state and / or its performance being worse than a performance threshold. In some examples, the performance of a virtual resource or component may include resource utilization.

[0101] This application does not limit the type of heartbeat message. Optionally, the heartbeat message can be a Layer 1, Layer 2, or Layer 3 message in a four-layer network model. For example, the heartbeat message can be a keep-alive message of the Transmission Control Protocol (TCP).

[0102] The management methods for the primary and backup systems provided in this application are described below for Scenario 1 and Scenario 2, respectively. For example... Figure 4-1 As shown, Scenario 1 refers to a situation where the connectivity of the production center's heartbeat link is worse than a first connectivity threshold, and / or, the connectivity of the production center's communication link is worse than a second connectivity threshold. A heartbeat link connectivity worse than the first connectivity threshold can be understood as a heartbeat link failure or a sub-optimal state. Similarly, a communication link connectivity worse than the second connectivity threshold can be understood as a communication link failure or a sub-optimal state. Figure 4-2 As shown, Scenario 2 refers to an abnormal state of the target virtual component in the production center. The target virtual component can be one or more virtual components in the production center. Figure 4-2 Taking the target virtual components including DB and SGMS as an example, this application does not limit the number or type of target virtual components. The meaning of abnormal virtual component states can be found in the relevant content above, and will not be repeated here.

[0103] Figure 5 This schematically illustrates one possible workflow for the management approach executed in the front-end. Optional, Figure 5 The method shown can also be executed by a third-party network management center connected to the front end. For example... Figure 5 As shown, the method may include S501 to S509.

[0104] S501. Determine whether it is a primary / standby system. If yes, execute S502; otherwise, return.

[0105] The front-end can determine whether the system providing service 1 is the primary or backup system. If it determines that the primary or backup system provides service 1, it executes S502; otherwise, for example... Figure 1 As shown, if it is determined that backend 1 provides service 1, then return (or end) the request. Figure 5The method flow is shown below. In the following text, it is assumed that the primary / backup system includes backend 1 and backend 2.

[0106] S502, Obtain the primary / standby status;

[0107] The primary / standby status indicates that backend 1 is in primary status (i.e., the production center) and backend 2 is in standby status (i.e., the disaster recovery center).

[0108] S503. Determine whether heartbeat arbitration is enabled. If yes, execute S504; otherwise, return.

[0109] S504. Determine if the heartbeat message 1 from the disaster recovery center is normal. If yes, execute S505; otherwise, return.

[0110] The heartbeat message from the disaster recovery center (referred to as heartbeat message 1) can include the information about the disaster recovery center's ability to become the primary service provider, as described earlier. A normal heartbeat message 1 indicates that the disaster recovery center's ability to become the primary service provider is better than the capability threshold, meaning that service 1 can be provided normally when the disaster recovery center switches to primary status. An abnormal heartbeat message 1 indicates that the disaster recovery center's ability to become the primary service provider is worse than the capability threshold, meaning that service 1 may not be provided normally when the disaster recovery center switches to primary status. In this case, a primary / standby switchover may not be performed.

[0111] S505, Query the heartbeat message 2 of the production center;

[0112] Heartbeat message 2 can be a heartbeat message between the front end and the production center.

[0113] S506. Determine whether the virtual component is in normal condition based on heartbeat message 2. If yes, execute S507; otherwise, execute S509.

[0114] Heartbeat message 2 can include the status information of the production center introduced earlier. The front end can determine whether the status of the production center or the virtual component is normal based on the status information of the production center in heartbeat message 2.

[0115] S507. Determine whether the heartbeat link is normal based on heartbeat message 2. If yes, return; otherwise, execute S508.

[0116] The front-end can determine the health of the heartbeat link between itself and the production center based on heartbeat message 2. A healthy heartbeat link means its connectivity is better than the first connectivity threshold described earlier, in which case a primary / backup switchover is not required. An abnormal heartbeat link means its connectivity is worse than the first connectivity threshold described earlier (heartbeat link failure or sub-health), in which case S508 can be executed. A heartbeat link failure means the heartbeat link is disconnected. A sub-healthy heartbeat link means the heartbeat link is intermittent.

[0117] S508. Determine whether the heartbeat link has returned to normal. If yes, return; otherwise, execute S509.

[0118] The front-end can determine whether the heartbeat link between the front-end and the production center has returned to normal. If it has returned to normal, the primary / backup switchover can be skipped. If it is still abnormal, S509 can be executed.

[0119] S509, Perform master / slave switchover.

[0120] When the front-end determines the arbitration result, and the arbitration result indicates that a primary / standby switchover should be performed, the front-end can execute the primary / standby switchover. Specifically, the front-end can notify the disaster recovery center (i.e., back-end 2) to become the primary, and back-end 2 will notify each virtual component to switch to the primary state and begin processing the business data of business 1. The front-end can also notify the production center (i.e., back-end 1) to become the standby, and back-end 1 will notify each virtual component to switch to the standby state and begin backing up data. The front-end can refresh the primary / standby status, for example, recording back-end 1 as the standby state and back-end 2 as the primary state.

[0121] like Figure 5 As shown, the front-end can determine the arbitration result based on heartbeat messages and automatically perform primary / standby failover. Compared with the existing disaster recovery mechanism, the front-end adds the function of autonomously switching between the production center and the disaster recovery center based on the heartbeat arbitration mechanism. The heartbeat message is no longer only used for keep-alive, but can also send the status of virtual components in the back-end.

[0122] The following section describes the management methods for the primary and backup systems provided in this application, using different scenarios as examples.

[0123] First, we introduce the management method for the primary and backup systems in Scenario 1. Scenario 1 refers to a situation where the connectivity of the production center's heartbeat link is worse than a first connectivity threshold, and / or, the connectivity of the production center's communication link is worse than a second connectivity threshold. A heartbeat link connectivity worse than the first connectivity threshold can be understood as a heartbeat link failure or a sub-optimal state. A communication link connectivity worse than the second connectivity threshold can be understood as a communication link failure or a sub-optimal state.

[0124] The architecture of the production center and the disaster recovery center can remain unchanged. However, the heartbeat message can be updated with the status information of the virtual components. A new heartbeat arbitration mechanism is added to the front end. In scenario 1, the front end can identify scenario 1 based on the heartbeat message and automatically switch the primary / standby relationship between the production center and the disaster recovery center.

[0125] Figure 6 This illustration shows an example of a management method for a primary / standby system in Scenario 1. For example... Figure 6 As shown, the method may include S601 to S623.

[0126] S601, heartbeat message 3 is transmitted between backend 1 and backend 2;

[0127] Heartbeat message 3 can be understood as the heartbeat message transmitted on the heartbeat link (denoted as heartbeat link 3) between backend 1 and backend 2. For example, heartbeat link 3 may include the heartbeat link between the SGMS and / or the heartbeat link between the RPDs in the two backends described above.

[0128] S602, heartbeat message 1 is transmitted between backend 2 and frontend 1;

[0129] Heartbeat message 1 can be understood as the heartbeat message transmitted on the heartbeat link (denoted as heartbeat link 1) between backend 2 and frontend 1.

[0130] S603, heartbeat message 2 is transmitted between backend 1 and frontend 1;

[0131] Heartbeat message 2 can be understood as the heartbeat message transmitted on the heartbeat link (denoted as heartbeat link 2) between backend 1 and frontend 1.

[0132] The disaster recovery relationship between the databases and / or applications of Backend 1 and Backend 2 can be configured manually. For example, a maintenance engineer can configure Backend 1 as the primary state (i.e., the production center) and Backend 2 as the standby state (i.e., the disaster recovery center). After the disaster recovery relationship is established between Backend 1 and Backend 2, data baselines are established between the databases of the production center (i.e., DB) and the databases of the disaster recovery center, i.e., a disaster recovery relationship is established. The database of the production center is in a read-write state, and the database of the disaster recovery center is in a read-only state.

[0133] S604, Front-end 1 monitors heartbeat;

[0134] Frontend 1 can configure backend heartbeat detection, for example, configuring the heartbeat detection period. Frontend 1 can determine the connectivity of heartbeat link 1 based on heartbeat message 1, and determine the connectivity of heartbeat link 2 based on heartbeat message 2. Optionally, backend 1 and / or backend 2 can also report the connectivity detection results of heartbeat message 3 or heartbeat link 3 to frontend 1.

[0135] Optionally, as described above, heartbeat message 1 may also include the status information of background 2, and heartbeat message 2 may also include the status information of background 1. For example, the status information of the background may include the status of each virtual component in one or more virtual components, and the status of the virtual components includes their health status and resource performance, etc.

[0136] Optionally, as mentioned above, the foreground 1 can also detect the connectivity of the communication link between itself and the background 1.

[0137] This application does not limit the foreground to listen to heartbeat message 1, heartbeat message 2 and heartbeat message 3. Optionally, the foreground 1 can listen to at least one of these heartbeat messages.

[0138] S605, Backend 1 synchronizes all configuration data to Backend 2;

[0139] S606, Backend 2 restores all configuration data;

[0140] S607, Backend 1 synchronizes incremental configuration data to Backend 2;

[0141] S608, Background 2 restores incremental configuration data;

[0142] S609, Backend 1 synchronizes report data to Backend 2;

[0143] S610, Backend 2 restores report data;

[0144] This application does not limit the data types or timing of data synchronization between backend 1 and backend 2; the above are merely examples.

[0145] S611, Backend 1 notifies its virtual components that they are in production status;

[0146] This application does not limit the number and type of virtual components in the backend 1. For example, the backend 1 includes... Figure 3-1 The production center shown contains at least one of RPD, DB, HDFS, or SGMS.

[0147] S612, Backend 2 notifies its virtual components that they are in disaster recovery status;

[0148] This application does not limit the number and type of virtual components in the backend 2. For example, the backend 2 includes... Figure 3-1 The disaster recovery center shown contains at least one of RPD, DB, HDFS, or SGMS.

[0149] S613, An abnormality was detected in heartbeat link 2;

[0150] Suppose that at time T1, the foreground 1 determines that heartbeat link 2 is abnormal based on the detection result (e.g., the connectivity of heartbeat link 2 is worse than the first connectivity threshold). It can then determine whether to perform a master-slave switchover by combining the arbitration mechanism or the conditions for master-slave switchover. The conditions for master-slave switchover can be found in the relevant content above. For example, if the connectivity of heartbeat link 1 in background 2 is better than the second connectivity threshold, and background 2 is in a normal state, a master-slave switchover can be performed.

[0151] S614, Front-end 1 sends switch instruction 1 to back-end 2;

[0152] Switching indicator 1 can instruct background 2 to switch to primary mode.

[0153] S615, Backend 2 notifies its virtual components to switch to production status;

[0154] Assuming that the status of each virtual component in backend 2 is normal and the database backup is normal, backend 2 can start each virtual component from standby state to primary state according to switchover instruction 1.

[0155] S616, Backend 2 sends switch instruction 2 to backend 1;

[0156] After receiving the handover instruction 1, or after S615 or S616, backend 2 can send the handover instruction 2 to backend 1. The handover instruction 2 can instruct backend 1 to switch to standby mode.

[0157] Optionally, in S616, the foreground 1 can send the switching instruction 2 instead of the background 2. The foreground 1 can send the switching instruction 2 to the background 1 after S613, S614, or S617.

[0158] S617, Backend 2 sends feedback 1 to frontend 1;

[0159] After the background 2 switches to the primary state, it can send feedback 1 to the front end 1. Feedback 1 is used to indicate that the switch was successful.

[0160] S618, Backend 1 notifies its virtual components to switch to disaster recovery status;

[0161] After receiving the switching instruction 2, backend 1 can notify its virtual components to switch from primary to standby status.

[0162] S619, Backend 1 sends feedback 2 to Frontend 1;

[0163] After the background 1 switches to standby mode, it can send feedback 2 to the front end 1. Feedback 2 is used to indicate that the switch was successful.

[0164] S620, Front-end 1 updates primary / standby relationship;

[0165] After receiving feedback 1 and feedback 2, front-end 1 can update the primary / backup relationship between back-end 1 and back-end 2.

[0166] S617 and / or S619 are optional steps. Optionally, foreground 1 executes S620 after S613 or S614.

[0167] S621, Backend 1 synchronizes incremental data 1 to backend 2;

[0168] After receiving the switchover instruction 2, Backend 1 can incrementally synchronize incremental data 1 (such as incremental configuration data, incremental quality data, or incremental report analysis data) to the new production center (i.e., Backend 2).

[0169] S622, Background 2 restores incremental data 1;

[0170] Steps S621 and S622 are optional. Furthermore, this application does not limit S621 and S622 to be performed after S618 or S619; optionally, S621 and S622 can be performed after S616.

[0171] S623, Backend 2 synchronizes incremental data 2 to Backend 1.

[0172] After backend 2 switches to primary mode, it can process the data of business 1 and generate incremental data 2. Backend 2 can synchronize incremental data 2 to backend 1.

[0173] In some examples, after background 1 and background 2 are in standby and primary states respectively, it is possible to set no switchback. That is, when the heartbeat of the original production center (e.g., background 1) returns to normal, it continues to maintain the current working state (i.e., standby state). When the new production center (i.e., background 2) fails, a switchback is triggered, that is, background 1 and background 2 switch to primary and standby states respectively.

[0174] In some examples, after background 1 and background 2 are in standby and primary states respectively, a switchback can be configured. That is, when the original production center (e.g., background 1) resumes normal heartbeat, background 1 and background 2 switch to primary and standby states respectively. Optionally, the switchback can be performed as described in S613-S622, simply by swapping background 1 and background 2 in S613-S622. Optionally, after the original production center (e.g., background 1) resumes normal heartbeat, a delayed switchback can be configured, with the delay duration or the switchback timing adjustable.

[0175] The methods executed by other foreground processes in the system can be referenced. Figure 6 The execution method of the foreground 1 in the method shown should be understood.

[0176] The following describes the management method for the primary and backup systems in Scenario 2. (Optional) Figure 5 The method shown can also be executed by a third-party network management center connected to the front end. For example... Figure 7 As shown, the method may include S701 to S723.

[0177] Figure 7 The steps shown can be referenced. Figure 6 The corresponding steps shown can be understood. For example, S701 can be understood by referring to the relevant content of S601, which will not be repeated here. Figure 7 and Figure 6The difference in the method shown is that in S713, the abnormal situation identified by the front-end 1 is not that the connectivity of the heartbeat link 2 is worse than the first connectivity threshold. Instead, at time T2, the front-end 1 identifies an abnormality in the target virtual component based on the status information of the target virtual component in the heartbeat message 2. Then, it combines the arbitration mechanism or the conditions for primary / backup switchover to determine whether to perform primary / backup switchover. For example, if the connectivity of the heartbeat link 1 of the back-end 2 is better than the second connectivity threshold, and the status of the back-end 2 is normal, it can be determined to perform primary / backup switchover.

[0178] The target virtual component refers to all or some of the virtual components in backend 1. The status information and anomalies of the target virtual component can be understood by referring to the relevant content above, and will not be repeated here. For example, if the report database of backend 1 is queried three times in 20 consecutive seconds, its status will be abnormal in each query.

[0179] The methods executed by other foreground processes in the system can be referenced. Figure 6 The execution method of the foreground 1 in the method shown should be understood.

[0180] Optionally, based on the front-end detecting that the performance of a virtual component's resources in the production center is worse than the performance threshold, the front-end can notify the network administrator or maintenance engineer to optimize the resources of that virtual component, for example, by expanding its capacity.

[0181] Figure 8 This illustration shows another possible example of the method of this application. Figure 8 In this context, a third-party network management center can connect to backend 1 and backend 2 through one or more frontends respectively. For example... Figure 8 As shown, the method may include S801 to S806.

[0182] S801, Backend 1 reports resource information 1 to the third-party network management center;

[0183] S802, Backend 2 reports resource information 2 to the third-party network management center;

[0184] Resource information 1 indicates the performance of IT resources allocated by data center 1 to backend 1, and resource information 2 indicates the performance of IT resources allocated by data center 2 to backend 2. The performance of resources can be found in the relevant content above, and will not be elaborated upon here.

[0185] This application does not limit the method by which the backend reports resource information to the third-party network management center. For example, the backend can carry its own resource information in a heartbeat message sent to the frontend, and then the frontend can report the backend's resource information to the third-party network management center.

[0186] S803, the third-party network management center sends configuration information 1 to the backend 1;

[0187] S804, The third-party network management center sends configuration information 2 to the backend 2;

[0188] Assuming that at time T3, front-end 1 connects, the third-party network management center can decide to bind back-end 1 and back-end 2 to front-end 1 respectively. Subsequently, the third-party network management center can configure front-end 1 to bind to both back-end 1 and back-end 2, with back-end 1 as the primary and back-end 2 as the backup. The third-party network management center can also send configuration information 1 and configuration information 2 to back-end 1 and back-end 2 respectively, to configure back-end 1 and back-end 2 to bind to front-end 1 respectively, with back-end 1 as the primary and back-end 2 as the backup.

[0189] S805, the third-party network management center sends expansion instruction 1 to backend 1;

[0190] The third-party network management center can obtain the resource information 1 of the backend 1 multiple times. When the third-party network management center determines that the performance of the resources of the backend 1 is worse than the performance threshold based on the resource information 1, the third-party network management center can send the expansion instruction 1 to the backend 1. The expansion instruction 1 can instruct the maintenance engineer to expand the backend 1 or a part of the virtual components of the backend 1.

[0191] S806, the third-party network management center sends expansion instruction 2 to the backend 2.

[0192] The third-party network management center can obtain resource information 2 of the backend 2 multiple times. When the third-party network management center determines that the performance of the resources of the backend 2 is worse than the performance threshold based on the resource information 2, the third-party network management center can send expansion instruction 2 to the backend 2. Expansion instruction 2 can instruct the maintenance engineer to expand the backend 2 or a part of the virtual components of the backend 2.

[0193] Resources in production centers are generally involved in business processing, while resources in disaster recovery centers are only involved in periodic data backup. Taking the recommended deployment of servers as an example, the ratio of resource utilization of the data center where the production center is located to that of the data center where the disaster recovery center is located is about 7:2. In extreme scenarios, that is, when there is congestion in business data processing on the network, the resource utilization of the data center where the production center is located may even reach 100% or even be overloaded.

[0194] To avoid data center overload, such as Figure 9-1As shown, this application proposes that a single data center virtualizes two backends based on underlying server resources. For example, backend 1 and backend 3 are obtained based on the virtualization of resources in data center 1, and backend 2 and backend 4 are obtained based on the virtualization of resources in data center 2. Backend 1 and backend 2 are the primary and backup devices of the same primary / backup system (referred to as primary / backup system 1 or plane 1), while backend 3 and backend 4 are the backup and primary devices of the same primary / backup system (referred to as primary / backup system 2 or plane 2). In data center 1, backend 1 processes business operations, while backend 3 does not. In data center 2, backend 2 does not process business operations, but backend 1 does. The backends in primary mode in data center 1 and the backends in primary mode in data center 2 can be used to provide the same business, which helps reduce the processing pressure on a single data center and achieves load balancing between the two data centers. Figure 9-2 As shown, both Data Center 1 and Data Center 2 communicate with Front-end 1 for business purposes.

[0195] like Figure 10 As shown, in a single-plane deployment, where the backend in data center 1 provides services while the backend in data center 2 does not (i.e., the backend in a single data center works alone or independently), the resource consumption or utilization rate of data center 1 is 70% and that of data center 2 is 20%. In a dual-plane deployment, where the backends in data center 1 and data center 2 are mutually primary and backup, and both data center 1 and data center 2 have backends used for providing services, the resource consumption or utilization rate of data center 1 is 60% and that of data center 2 is 60%. This achieves data load sharing between the two backends, reduces the business processing pressure on a single data center, and optionally, also helps improve the data processing capabilities of the frontend.

[0196] In some examples, a third-party network management center can flexibly allocate resources to each backend based on the resource usage in data center 1 and data center 2, so as to achieve the effect of the two data centers working simultaneously and load balancing.

[0197] Optionally, backends in different primary / backup systems or different planes can be bound to different frontends. Figure 9-1 The diagram illustrates front-end 1 (denoted as R1), front-end 2 (denoted as R2), ..., and front-end 6 (denoted as R6). Data centers 1 and 2 are connected to each front-end via switches (SW). Furthermore, back-end 1 in data center 1 and back-end 2 in data center 2 can be bound to R1, R3, and R5 respectively, and back-end 3 in data center 1 and back-end 4 in data center 2 can be bound to R2, R4, and R6 respectively. The management method for primary / backup system 1 can be found in [reference needed]. Figure 6 or Figure 7 The method shown, correspondingly, Figure 6 or Figure 7 The multiple front-ends shown can include R1, R3, and R5. The management method for the primary / standby system 2 can be found in [reference needed]. Figure 6 or Figure 7 The method shown, correspondingly, Figure 6 or Figure 7 The backend 1 shown can be replaced with backend 4, backend 2 can be replaced with backend 3, and multiple frontends can be replaced with R2, R4 and R6.

[0198] For methods on how third-party network management centers can expand resources for backend 3 or backend 4, please refer to [the relevant documentation / reference]. Figure 8 To understand the method shown, simply... Figure 8 In the method shown, simply replace "Backend 1" and "Backend 2" with "Backend 4" and "Backend 3" respectively. You can refer to [link / reference] for details on "Backend 4" and "Backend 3". Figure 3-1 or Figure 4-1 or Figure 4-2 To understand the production center and disaster recovery center shown, refer to the examples in backend 3 for details. Figure 3-1 Understand the virtual components in the disaster recovery center shown.

[0199] Optionally, after the front-end is bound to two back-ends of the same primary / standby system, the primary / standby relationship between the two back-ends can be determined autonomously based on the resource usage of each data center monitored by the third-party network management center. For example, if the third-party network management center configures front-end 1 to bind to back-end 1 and back-end 2 respectively, and configures back-end 1 and back-end 2 to be in primary and standby states respectively, and if the third-party network management center configures front-end 2 to bind to back-end 3 and back-end 4 respectively, front-end 2 can automatically configure back-end 3 to standby state and back-end 4 to primary state based on the fact that the resource usage rate of data center 1 where back-end 3 is located is higher than that of data center 2 where back-end 4 is located, thereby achieving load balancing between data center 1 and data center 2. This application does not limit the type of resource usage monitored by the third-party network management center. For example, the third-party network management center can monitor one or more of the following IT resources in the back-end database through the data center's back-end resource black box: read / write (input / output, I / O) capability, available memory size, available hard disk space size, or number of central processing unit (CPU) threads and cores.

[0200] It should be noted that SGMS heartbeat can be designed with dual heartbeats, meaning that the SGMS heartbeat for each plane is maintained independently. Optionally, the front-end can be configured with dual planes, meaning a single front-end can divide the original cross-datacenter primary and backup back-ends into 1+1 symmetrical configuration planes based on resource abstraction and layering, serving as disaster recovery and production planes for each other. Optionally, data from the same front-end can be bound to different configuration planes based on the granularity of the service probe system (SPS). For example, R1 can be bound to back-end 1 through back-end 4, allowing different back-end resources to handle services from different SPSs. The front-end can be configured with production / disaster recovery dual planes, and the back-end can also form production / disaster recovery dual planes based on server virtual resource components. The front-end can configure back-end dual planes at the SPS granularity to achieve load balancing for back-end services.

[0201] In summary, the dual-plane solution provided in this application enables back-end systems in different data centers to have the ability to handle business data with a 1:1 load balancing, i.e., to process data simultaneously.

[0202] Optionally, the arbitration results of one or more backends (e.g., determining the primary / standby relationship between different backends in the same primary / standby system) can be linked to a third-party network management center, enabling it to instruct other backends to perform a primary / standby switchover on the primary / standby system based on the arbitration results of one or more backends. Since other backends can perform a primary / standby switchover on the primary / standby system before receiving the arbitration results, it facilitates the forward detection and migration of faults or sub-optimal conditions in other backends, thereby improving the processing efficiency of business data forwarded by other backends.

[0203] For example, suppose Figure 9-1 As shown, R1, R3, and R5 trigger the heartbeat arbitration result, determining to initiate a primary / standby switchover in primary / standby system 1, for example, S613 or S713. Then, they respectively send the arbitration result to the third-party network management center. Due to the asynchronous nature of message transmission, R2, R4, and R6 may not yet have detected any anomalies (faults or sub-health states) in the production center. At this time, the third-party network management center can directly issue a switchover command based on the arbitration result, achieving proactive fault detection. Alternatively, without relying on the third-party network management center, the backend receiving the switchover instruction can notify other frontends to perform the primary / standby switchover. For example, after receiving switchover instruction 1 from frontend 1, backend 2 can notify other bound frontends (such as frontends 3 and 5) to perform the primary / standby switchover.

[0204] As can be seen, this method only requires... Figure 6 or Figure 7 The method shown can be improved by adding a data push process between the third-party network management center and the front end, or a data push process between the back end and the front end.

[0205] To improve reliability, a third-party network management center or front-end can only perform a primary / backup switch based on receiving arbitration results or switchover instructions from at least X front-ends. X is a positive integer less than N. X can be predefined, set, or determined based on N and a percentage threshold. For example, X can be the integer part of the product of N and a percentage threshold. For instance, when X front-ends detect a production center failure or a sub-healthy state (including intermittent link interruptions), reaching the switchover condition, the third-party network management center can push the detection results to the remaining NX front-ends. The front-ends that haven't switched over will then complete the switchover based on the received results, achieving pre-detection and switchover of sub-health and failure conditions.

[0206] The apparatus provided in this application is described below.

[0207] The ninth aspect above provides a communication device, which can be any of the front-end or third-party network management centers described above. This communication device may include a transceiver module and a processing module. The communication device can perform... Figure 5 The method shown, or execution Figure 6 or Figure 7 The methods executed in the front-end 1 are as follows: The send / receive module is used to execute the send / receive operations in the corresponding methods, for example, executing S614, S617, and S619. The processing module is used to execute the internal operations in the system's hard methods, for example, executing S613 and S620. For details, please refer to the relevant descriptions in the aforementioned method examples.

[0208] This application also provides a communication device, which can be any of the background processes described above or used to run any background process. The communication device may include a transceiver module and a processing module. The communication device can perform... Figure 6 or Figure 7 The methods executed by backend 1 or backend 2. The send / receive module is used to execute the send / receive operations in the corresponding methods, and the processing module is used to execute the internal operations in the system's methods. Please refer to the relevant descriptions in the aforementioned method examples for details.

[0209] In this application, the internal operation or action can be other operations besides the sending and receiving operations in the flowchart of the communication method, for example, the steps described by the arrowed curves in the flowchart.

[0210] It should be noted that the above system architecture, device, or module structure is merely an example and should not constitute a specific limitation. Modules within the system architecture, device, or module can be added, removed, or merged as needed. Furthermore, the operation and / or function of each module in the system or device are for implementing the corresponding process of the corresponding method; for the sake of brevity, they will not be elaborated upon here.

[0211] See Figure 11 , Figure 11This is a schematic diagram of the structure of a computing device provided in this application. For example... Figure 11 As shown, the computing device 11 includes a processor 111, a communication interface 112, and a memory 113. The processor 111, the communication interface 112, and the memory 113 communicate with each other via a bus 114. The computing device 11 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the computing device 11.

[0212] Bus 114 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 11 The bus 114 may be represented by a single line, but this does not mean that there is only one bus or one type of bus. The bus 114 may include a path for transmitting information between various components of the computing device 11 (e.g., memory 113, processor 111, communication interface 112).

[0213] The processor 111 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0214] Memory 113 may include volatile memory, such as random access memory (RAM). Processor 111 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0215] The memory 113 stores executable program code, which the processor 111 executes to implement the functions of the aforementioned transceiver module and processing module, respectively. That is, the memory 113 stores instructions for executing the above methods.

[0216] The communication interface 113 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the computing device 11 and other devices or communication networks.

[0217] This application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0218] like Figure 12 As shown, the computing device cluster includes at least one computing device 11. The memory 113 of one or more computing devices 11 in the computing device cluster may store the same instructions for performing the above-described methods.

[0219] In some possible implementations, the memory 113 of one or more computing devices 11 in the computing device cluster may also store partial instructions for executing the above-described methods. In other words, a combination of one or more computing devices 11 can jointly execute the instructions for executing the above-described methods.

[0220] It should be noted that the memories 113 in different computing devices 11 within the computing device cluster can store different instructions, each used to execute a portion of the functions of the communication device. That is, the instructions stored in the memories 113 of different computing devices 11 can implement the functions of one or more modules in the transceiver module and the processing module.

[0221] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc. Figure 13 One possible implementation is shown. For example... Figure 13 As shown, the two computing devices 11A and 11B are connected via a network. Specifically, they are connected to the network through communication interfaces in each computing device. In this possible implementation, the memory 113 in computing device 11A stores instructions for performing the functions of the transceiver module. Meanwhile, the memory 113 in computing device 11B stores instructions for performing the functions of the processing module.

[0222] Figure 13 The connection method between the computing device clusters shown can be based on the fact that the method provided in this application requires a large amount of computation, so the functions implemented by the processing module are delegated to the computing device 11B.

[0223] It should be understood that Figure 13The functions of computing device 11A shown can also be performed by multiple computing devices 11. Similarly, the functions of computing device 11B can also be performed by multiple computing devices 11.

[0224] This application is not limited to the device used to run the backend or third-party network management center. In some examples, the backend or third-party network management center runs on one or more devices within the infrastructure, or on one or more devices outside the infrastructure. Optionally, the device used to run the backend or third-party network management center includes... Figure 11 or Figure 12 or Figure 13 As shown.

[0225] This application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions capable of running on a computing device or stored on any usable medium. When the computer program product is run on at least one computing device, it causes the at least one computing device to perform all or some of the steps in any of the above-described method examples.

[0226] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center that includes one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to perform all or part of the steps in any of the above method examples.

[0227] In the above examples, the descriptions of each example have their own emphasis. For parts not detailed in one example, please refer to the relevant descriptions in other examples. It should be noted that, for the sake of simplicity, the aforementioned method examples are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the examples described in the specification are preferred examples, and the actions and modules involved are not necessarily essential to this application.

[0228] In the examples provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device examples described above are merely illustrative; the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interface; the indirect coupling or communication connection of devices or units may be electrical or other forms.

[0229] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this example solution according to actual needs.

[0230] The terms "first," "second," "third," "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to those processes, methods, products, or apparatuses. The term "multiple" appearing in the embodiments of this application refers to two or more. It should be understood that the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects are in an "or" relationship.

[0231] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims

1. A management method of a primary / backup system, characterized by, The method is applied to a system comprising one or more network devices connected in communication, a first data center and a second data center, the first data center running a first virtual resource of a first active-standby system, the second data center running a second virtual resource of the first active-standby system, the first virtual resource and the second virtual resource being used in a master state to provide the same service, the first virtual resource being in the master state and the second virtual resource being in a standby state, the method comprising: obtaining information of the first active-standby system, the information of the first active-standby system comprising information of the first virtual resource and / or information of the second virtual resource; switching a master-standby relationship between the first virtual resource and the second virtual resource according to the information of the first active-standby system.

2. The method of claim 1, wherein, The information of the first active-standby system comprises at least one of: first information indicating connectivity of a communication link used for transmitting service data of the first virtual resource; second information indicating connectivity of at least one heartbeat link, the at least one heartbeat link comprising a heartbeat link between the first virtual resource and the second virtual resource and / or a heartbeat link between at least one of the network devices and the first virtual resource; third information indicating performance of a first resource, the first resource comprising information technology (IT) resources allocated to the first virtual resource.

3. The method of claim 2, wherein, The first virtual resource comprises one or more first virtual components, and the performance of the first resource comprises performance of resources allocated to each of the at least one first virtual component.

4. The method of claim 3, wherein, The third information indicates that performance of resources of a target virtual component of the at least one first virtual component is worse than a first performance threshold, and before the switching of the master-standby relationship between the first virtual resource and the second virtual resource according to the information of the first active-standby system, the method further comprises: sending prompt information indicating optimization of the resources of the target virtual component.

5. The method according to any one of claims 2-4, characterized in that, The switching of the master-standby relationship between the first virtual resource and the second virtual resource according to the information of the first active-standby system comprises: switching the master-standby relationship between the first virtual resource and the second virtual resource based on the information of the first active-standby system satisfying a first condition, the first condition comprising at least one of: the connectivity indicated by the first information being worse than a first connectivity threshold, the connectivity indicated by the second information being worse than a second connectivity threshold, or the performance of the resources indicated by the third information being worse than a performance threshold.

6. The method of any one of claims 1-5, applied to a first network device of the one or more network devices, the system further comprising a communication device connected to the one or more network devices respectively, the method further comprising: sending fourth information to the communication device, the fourth information being used to indicate switching the master-slave relationship between the first virtual resource and the second virtual resource, the communication device being configured to send notification information to one or more network devices other than the first network device according to the fourth information, the notification information indicating switching the master-slave relationship between the first virtual resource and the second virtual resource.

7. The method according to any one of claims 1-5, characterized in that, The system further comprises a communication device, and the method is applied to the communication device, the communication device being connected to one or more network devices respectively, and the method further comprises: sending fifth information to the one or more network devices respectively, the fifth information being used to indicate switching the master-slave relationship between the first virtual resource and the second virtual resource.

8. The method according to any one of claims 1-7, characterized in that, Before switching the master-slave relationship between the first virtual resource and the second virtual resource according to the information of the first master-slave system, the method further comprises: triggering the first virtual resource and the second virtual resource to perform data synchronization.

9. The method according to any one of claims 1-8, characterized in that, The first data center further runs a third virtual resource of a second master-slave system, and the second data center further runs a fourth virtual resource of the second master-slave system, the third virtual resource being in a standby state and the fourth virtual resource being in a master state, and the third virtual resource and the fourth virtual resource are used to provide the same service in the master state.

10. The method according to any one of claims 1-9, characterized in that, The first virtual resource and the second virtual resource respectively comprise one or more virtual instances or one or more virtual services running on one or more virtual instances.

11. A management method of a master-slave system, characterized by, The method is applied to a system, the system comprising one or more network devices, a first data center and a second data center connected in communication, and the method comprises: receiving configuration information; creating a first virtual resource of a first master-slave system and a second virtual resource of a second master-slave system based on the resources of the first data center according to the configuration information, the first master-slave system further comprising a third virtual resource created based on the resources of the second data center, and the second master-slave system further comprising a fourth virtual resource created based on the resources of the second data center, the first virtual resource and the second virtual resource being in a production state and a disaster recovery state respectively, the third virtual resource and the fourth virtual resource being in a disaster recovery state and a production state respectively, the first virtual resource and the third virtual resource in the first master-slave system being used to provide the same service in the master state, and the second virtual resource and the fourth virtual resource in the second master-slave system being used to provide the same service in the master state.

12. The method of claim 11, wherein, The first virtual resource and the second virtual resource in the first master-slave system are respectively bound to an interface of a first network device in the one or more network devices; The second virtual resource and the fourth virtual resource in the second master-slave system are respectively bound to an interface of a second network device in the one or more network devices.

13. A computer device, comprising: comprising a memory and a processor for executing instructions stored in the memory to cause the computer device to perform the method of any of claims 1-10.

14. A cluster of computing devices, characterized in that, comprising at least one computing device, each of the computing devices comprising a memory and a processor; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the method of any of claims 1-12.

15. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, when the computer program is executed by a processor, the processor executes the method of any of claims 1-12.

16. A system, comprising: comprising one or more communication devices connected in communication, a first data center and a second data center, at least one of the communication devices configured to perform the method of any of claims 1-10, and / or the first data center configured to perform the method of claim 11 or 12.

Images