Hot backup two-layer main and standby information processing system and hot backup method thereof

Abstract

The invention discloses a hot backup two-layer main and standby information processing system and a hot backup method thereof, the system comprises a control center A and a control center B which are mutually main and standby, the control center comprises two business devices which are mutually main and standby, and the business devices are mutually called partner business devices; the main and standby switching between the control centers is controlled by a user, the main and standby switching of the service equipment is completed through a negotiation process, the service equipment inquires the current main control center ID, namely the CoreID, from the control center to which the service equipment belongs after being started, and if the CoreID is the control center to which the service equipment belongs, the service equipment is the main service equipment or the standby service equipment. And then the two service devices query the main and standby states of the partner service device, and if the partner service device does not respond within the set time, the partner service device queries that the initiator itself is the main service device and the partner service device is the standby service device. According to the invention, hot backup design is carried out for the two-layer main / standby information processing system, so that automatic backup of service data and main / standby switching of service equipment caused by switching of a control center can be carried out by the two-layer main / standby information processing system.

Description

Technical Field

[0001] The invention relates to the field of network communication applications, in particular to a hot backup two-layer active-standby information processing system and a hot backup method thereof. Background Art

[0002] The existing solution can only support hot backup of information processing systems with one control center. However, as the reliability requirements of business functions increase, some business systems will use a two-layer active-standby mechanism, which requires not only active-standby hot backup design for business equipment, but also active-standby hot backup design for the upper-layer control center. When the active-standby control center switches, the existing solution may cause data asynchrony or business equipment cannot switch status normally, affecting the business functions of the information processing system. Summary of the invention

[0003] Purpose of the invention: The purpose of the present invention is to provide a hot backup method in a two-layer active-standby information processing system to solve the problems of automatic backup and active-standby switching of hot backup in the two-layer active-standby information processing system.

[0004] Technical solution: The hot backup two-layer active-standby information processing system of the present invention comprises control centers which are mutually active and standby, each control center comprises two business devices which are mutually active and standby, and are called partner business devices; the main business device under the main control center performs business processing functions;

[0005] The active / standby switching between control centers is controlled by the user, and the active / standby switching of service equipment is completed through a negotiation process, which includes:

[0006] After each service device is started, it queries the control center to which it belongs for the ID of the current main control center, i.e., CoreID. If the CoreID is that of the control center to which it belongs, the service device is the main service device or the backup service device. It sends a message to its partner service device to query its main and backup status. If its partner service device does not respond within the set time, it is the main service device itself, and its partner service device is offline or a backup service device. Otherwise, it is the backup service device itself, and its partner service device is the main service device.

[0007] If the CoreID is not the control center to which it belongs, the service device is an external service device.

[0008] Furthermore, the data generated by the main service device when executing service processing is synchronized to the backup service device and the external service device, and the backup service device and the external service device assemble the data into the local data area.

[0009] Furthermore, the main service device periodically sends keep-alive messages to the backup service device and the external service device. When the backup service device does not receive the keep-alive message from the main service device within a set time, it is considered that the main service device is faulty.

[0010] Furthermore, when the main service device fails, the backup service device switches its own status to the main service device, reports messages and status service data to the control center to which it belongs, and starts the service processing function.

[0011] Furthermore, when the master-slave switch of the control center occurs, the service equipment under the current master control center is switched to the external service equipment state.

[0012] Furthermore, when the master-slave switch of the control center occurs, the business equipment under the current backup control center switches to the main business equipment or the backup business equipment, sends its own device ID to its partner business equipment, determines that the business equipment with a smaller device ID switches to the waiting synchronization state, synchronizes data with the current main control center, and switches to the main business equipment after the data synchronization is completed; the main business equipment sends a keep-alive message to its partner business equipment, and its partner business equipment switches to the backup business equipment.

[0013] Further, for each service device, after startup, it queries the control center to which it belongs for the ID of the current main control center, i.e., CoreID. If the CoreID is that of the control center to which it belongs, the service device is the main service device or the backup service device. It sends a message to its partner service device to query its main and backup status. If its partner service device does not respond within the set time, it itself is the main service device, and its partner service device is offline or a backup service device. Otherwise, it itself is a backup service device, and its partner service device is the main service device, including:

[0014] If two business devices that serve as master and backup to each other simultaneously send messages to their partner business devices to inquire about the master and backup status, the business device that receives the query request first is called the first business device. If it determines that its own device ID is larger, it is the backup business device and does not respond to the query request from its partner business device; if it determines that its own device ID is smaller, it is the master business device and responds to the query request from its partner business device.

[0015] The hot backup method of the two-layer active-standby information processing system of the present invention comprises control centers which are mutually active and standby, each control center comprises two business devices which are mutually active and standby, and are called partner business devices; the main business device under the main control center performs business processing functions;

[0016] The active / standby switching between control centers is controlled by the user, and the active / standby switching of service equipment is completed through a negotiation process, which includes:

[0017] After each service device is started, it queries the control center to which it belongs for the ID of the current main control center, i.e., CoreID. If the CoreID is that of the control center to which it belongs, the service device is the main service device or the backup service device. It sends a message to its partner service device to query its main and backup status. If its partner service device does not respond within the set time, it is the main service device itself, and its partner service device is offline or a backup service device. Otherwise, it is the backup service device itself, and its partner service device is the main service device.

[0018] If the CoreID is not the control center to which it belongs, the service device is an external service device.

[0019] The electronic device described in the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is loaded into the processor, the hot backup method of the two-layer active-standby information processing system is implemented.

[0020] The computer-readable storage medium of the present invention stores a computer program, and when the computer program is executed by a processor, the hot backup method of the two-layer active-standby information processing system is implemented.

[0021] Beneficial effect: Compared with the prior art, the advantages of the present invention are: the present invention designs a hot backup method for an information processing system having two control centers that serve as primary and backup to each other and two business devices that serve as primary and backup to each other under each control center, so that it can perform rapid primary and backup switching, automatic backup of business data, and primary and backup switching of business equipment caused by switching of the control center, ensuring that the current business process can continue during the primary and backup switching process. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a schematic diagram of the two-layer active-standby information processing system of the present invention;

[0023] Figure 2 A flowchart of system startup according to an embodiment of the present invention;

[0024] Figure 3 A flowchart of conflict handling for startup of primary and backup service devices according to an embodiment of the present invention;

[0025] Figure 4 This is a processing flow chart of a main service device failure according to an embodiment of the present invention;

[0026] Figure 5 This is a hot backup flow chart when the primary and standby control centers switch according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] The technical solution of the present invention is further described below in conjunction with the accompanying drawings.

[0028] like Figure 1 The figure shows a two-layer active-standby information processing system described in this embodiment. In the system, there are two control centers A and B that are active and standby to each other. Inside A, there are two business devices A1 and A2 that are active and standby to each other. Inside B, there are also two business devices B1 and B2 that are active and standby to each other. For the convenience of description, A1 and A2 are called partner business devices, and correspondingly, B1 and B2 are also called partner business devices.

[0029] First, the business equipment needs to be configured with data. Taking A1 as an example, the data to be configured includes:

[0030] ① The IP address and ServiceID of the service device A1. The ServiceID is globally unique in the system. In this embodiment, for the convenience of discussion, it is assumed that the ServiceID of A1 is smaller than the ServiceID of A2.

[0031] ②IP address of partner business device A2.

[0032] ③CoreID of the control center A to which it belongs.

[0033] ④IP addresses of business devices B1 and B2.

[0034] ⑤IP address of control center B.

[0035] 1. The business equipment startup process in the main control center, such as Figure 2 shown.

[0036] (1) In this embodiment, it is assumed that the user selects control center A as the main control center, and A starts.

[0037] (2) After service device A1 is started, it sends a master / slave query request to control center A.

[0038] (3) After receiving the master-slave query request, control center A sends the CoreID of the current master control center, that is, A's CoreID, to A1 through a master-slave notification message according to the user's settings.

[0039] (4) After receiving the master-slave query response message, A1 determines that it is the CoreID of the control center A to which it belongs. In order to obtain whether A2 is already the BeMaster, it will send a message message WhoIsMaster to A2, which carries A1's ServiceID, asking whether the other party is the master device, and set the timer T_waitMaster to wait for a response. If T_waitMaster times out, it is considered that A2 has not started or A2 cannot respond. A1 will switch to the main business device (BeMaster), turn on all business functions, and start the timer T_alive to periodically send keep-alive messages to A2, B1 and B2.

[0040] A2 sends a ThisIsMaster response after receiving WhoIsMaster only when A2 itself is BeMaster. If A1 receives A2's ThisIsMaster response, it means A2 is already the master service device. At this time, A1 can only be a backup service device, so it switches to BeSlave state.

[0041] The situation where A1 and A2 send WhoIsMaster at the same time and cause a conflict is discussed below.

[0042] (5) During the execution of business processing, when data changes, A1 sends business data update messages to A2, B1, and B2. After receiving the messages, the receiver assembles the data locally for future use when switching to the main business device to maintain business continuity.

[0043] (6) At a later time, A2 starts up and sends a master / slave query message to control center A to determine its own master / slave status. After receiving the master / slave notification message from A, it determines the CoreID carried in the message. If it is A's CoreID, it sends a WhoIsMaster message to partner service device A1.

[0044] (7) After receiving WhoIsMaster, A1 sends ThisIsMaster to A2 because A1 is already the master service device. After receiving it, A2 sets its own master-slave status to BeSlave and starts the timer T_waitAlive to detect whether A1 sends keep-alive messages regularly.

[0045] 2. The service equipment startup process under the backup control center, such as Figure 2 shown.

[0046] (1) The user sets control center B as the backup control center, starts B, and indicates in the startup parameters that the current main control center is A.

[0047] (2) After B1 starts, it sends a master / slave query to B according to the configured CoreID. B sends the CoreID of the current master control center A to B1 through a master / slave notification message.

[0048] (3) B1 determines that the CoreID in the master-slave notification message is not the CoreID of its own center B, and switches to the BeExtern state.

[0049] (4) The process after B2 is turned on is the same as B1.

[0050] 3. The conflict handling process between A1 and A2, such as Figure 3 shown.

[0051] Consider a special case where A1 and A2 send WhoIsMaster requests to each other almost at the same time, resulting in a conflict. The processing flow is as follows.

[0052] Figure 3 The vertical direction is the time axis. Assume that at time t1, A1 and A2 send WhoIsMaster messages to each other almost simultaneously.

[0053] (1) For A2, A2 receives the WhoIsMaster message sent by A1 at time t2. After comparing A1's ServiceID carried in the latter message with its own ServiceID, A2 finds that its ServiceID is greater. A2 determines that the other party (A1) should switch to the main service device first. Therefore, A2 will not respond to the message, turn off the timer T_waitmaster, switch to the BeSlave state, and start T_waitAlive.

[0054] (2) For A1, A1 receives the WhoIsMaster message sent by A2 at time t3. Based on the fact that A2's ServiceID carried in the message is larger than its own, A1 determines that the other party is not the master service device and that it should be the master service device. Therefore, A1 switches to the BeMaster state, immediately turns off the timer T_waitmaster, and sends a keep-alive message KeepAlive to A2; the subsequent business data sent is synchronized to A2.

[0055] 4. Processing flow when main business equipment fails in the main control center, such as Figure 4 shown.

[0056] At a certain point in time, the main business device A1 fails (for example, it is shut down / disconnected from the network, etc.), causing A2 to not receive a keep-alive message within the T_waitAlive timer. A2 then believes that A1 is faulty and that it should be the master, so it updates its status to BeMaster, reports a message to the master device A, and starts the business function based on the assembled business data.

[0057] 5. Hot backup process when the main and standby control centers switch, such as Figure 5 shown.

[0058] (1) At the beginning of the process, A is the main control center and control center B is the backup control center. B1 and B2 are both started and both are in the BeExtern state. A1 is in the BeMaster state and A2 is in the BeSlave state. Because A1 sends a keepalive message KeepAlive to B1 and B2, B1 and B2 know that the current main service device is A1 and A1's IP address.

[0059] (2) Under user operation, the main control center switches to B. At this time, A1 and A2 under A will receive the main-backup switch notification, which carries the CoreID of the new main control center B. After receiving it, A1 and A2 determine that the control center has switched and update their own status to BeExtern.

[0060] (3) B1 and B2 under control center B also receive the master-slave switch notification, which carries the CoreID of the new master control center B. Taking B2 as an example, after receiving it, B2 determines that it is the CoreID of the control center B to which it belongs, so it needs to switch to BeMaster or BeSlave. In order to determine the master-slave relationship between B1 and B2, B2 sends a PollReq message to B1, carrying B2's ServiceID. Start timer T_waitpoll.

[0061] (4) If B1 is started, after receiving PollReq, it fills the smaller ServiceID between B1 and B2 into PollRsp and sends it to B2.

[0062] (5) After B2 receives PollRsp, there are two situations:

[0063] (a) If the ServiceID carried in it is its own, it means that it should be the future host. At this time, it will send a cross-area data synchronization request (CrossSyncReq) to the original host A1, requiring A1 to send a cross-area data synchronization response (CrossSyncRsp). This message sends the data of the unfinished process to B2. B2 sets the timer T_crsArea to wait for the response and switches to the WaitCrossSyncRsp state.

[0064] (b) If the ServiceID carried in PollRsp is not its own, B2 maintains the BeExtern state unchanged.

[0065] (6) After B2 receives the cross-zone data synchronization response (CrossSyncRsp) sent by A1, it performs the following operations:

[0066] (6-1) Data assembly and switching to the master business device (BeMaster) state;

[0067] (6-2) Immediately send a KeepAlive to the partner service device B1 and start the timer T_alive. After the timeout, send a KeepAlive again.

[0068] (6-3) Execute business operations and send business data synchronization messages to B1, A1, and A. At this time, B2 has switched to the BeMaster state and becomes the master business device. After receiving the KeepAlive message sent by B2, B1 switches to BeSlave. At this point, the cross-control center switch is completed;

[0069] (6-4) If B2 does not receive PollRsp before the T_waitpoll timer times out, it means that B1 is offline. At this time, B2 directly switches to the BeMaster state and becomes the main service device.

[0070] The hot backup method of the two-layer active-standby information processing system of the present invention comprises control centers which are mutually active and standby, each control center comprises two business devices which are mutually active and standby, and are called partner business devices; the main business device under the main control center performs business processing functions;

[0071] The active / standby switching between control centers is controlled by the user, and the active / standby switching of service equipment is completed through a negotiation process, which includes:

[0072] After each service device is started, it queries the control center to which it belongs for the ID of the current main control center, i.e., CoreID. If the CoreID is that of the control center to which it belongs, the service device is the main service device or the backup service device. It sends a message to its partner service device to query its main and backup status. If its partner service device does not respond within the set time, it is the main service device itself, and its partner service device is offline or a backup service device. Otherwise, it is the backup service device itself, and its partner service device is the main service device.

[0073] If the CoreID is not the control center to which it belongs, the service device is an external service device.

[0074] The electronic device described in the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is loaded into the processor, the hot backup method of the two-layer active-standby information processing system is implemented.

[0075] The computer-readable storage medium of the present invention stores a computer program, and when the computer program is executed by a processor, the hot backup method of the two-layer active-standby information processing system is implemented.

[0076] The computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, flash memory, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0077] The processor is used to execute the computer program stored in the memory to implement each step of the method involved in the above embodiment.

Claims

1. A hot backup layer 2 active / standby information processing system, characterized in that: The system includes control centers that are mutually primary and backup, and each control center includes two business devices that are mutually primary and backup, which are called partner business devices. The main business device under the main control center performs business processing functions; The active / standby switching between control centers is controlled by the user, and the active / standby switching of service equipment is completed through a negotiation process, which includes: After each service device is started, it queries the control center to which it belongs for the ID of the current main control center, i.e., CoreID. If the CoreID is that of the control center to which it belongs, the service device is the main service device or the backup service device. It sends a message to its partner service device to query its main and backup status. If its partner service device does not respond within the set time, it is the main service device itself, and its partner service device is offline or a backup service device. Otherwise, it is the backup service device itself, and its partner service device is the main service device. If the CoreID is not the control center to which it belongs, the service device is an external service device.

2. The hot backup layer 2 active / standby information processing system according to claim 1, characterized in that: The data generated by the main service device when executing service processing is synchronized to the backup service device and the external service device, and the backup service device and the external service device assemble the data into the local data area.

3. The hot backup layer 2 active / standby information processing system according to claim 1, characterized in that: The main service device sends keep-alive messages to the backup service device and external service devices regularly. When the backup service device does not receive the keep-alive message from the main service device within the set time, it is considered that the main service device is faulty.

4. The hot backup layer 2 active / standby information processing system according to claim 3 is characterized in that: When the main service device fails, the backup service device switches its status to the main service device, reports messages and status service data to the control center to which it belongs, and starts the service processing function.

5. The hot backup layer 2 active / standby information processing system according to claim 1, characterized in that: When the active / standby switchover of the control center occurs, the service equipment under the current active control center switches to the external service equipment state.

6. The hot backup layer 2 active / standby information processing system according to claim 1, characterized in that: When the master-slave switch of the control center occurs, the business equipment under the current standby control center switches to the master business equipment or the standby business equipment, sends its own device ID to its partner business equipment, and the business equipment with a smaller device ID switches to the waiting synchronization state, synchronizes data with the current main control center, and switches to the master business equipment after the data synchronization is completed; the master business equipment sends a keep-alive message to its partner business equipment, and its partner business equipment switches to the standby business equipment.

7. The hot backup layer 2 active / standby information processing system according to claim 1, characterized in that: For each service device, after startup, it queries the control center to which it belongs for the ID of the current main control center, that is, CoreID. If the CoreID is that of the control center to which it belongs, the service device is the main service device or the backup service device. It sends a message to its partner service device to query its main and backup status. If its partner service device does not respond within the set time, it is the main service device itself, and its partner service device is offline or a backup service device. Otherwise, it is the backup service device itself, and its partner service device is the main service device, including: If two business devices that serve as master and backup to each other simultaneously send messages to their partner business devices to inquire about the master and backup status, the business device that receives the query request first is called the first business device. If it determines that its own device ID is larger, it is the backup business device and does not respond to the query request from its partner business device; if it determines that its own device ID is smaller, it is the master business device and responds to the query request from its partner business device.

8. A hot backup method for a layer 2 active / standby information processing system, characterized in that: The system includes control centers that are mutually primary and backup, and each control center includes two business devices that are mutually primary and backup, which are called partner business devices. The main business device under the main control center performs business processing functions; The active / standby switching between control centers is controlled by the user, and the active / standby switching of service equipment is completed through a negotiation process, which includes: After each service device is started, it queries the control center to which it belongs for the ID of the current main control center, i.e., CoreID. If the CoreID is that of the control center to which it belongs, the service device is the main service device or the backup service device. It sends a message to its partner service device to query its main and backup status. If its partner service device does not respond within the set time, it is the main service device itself, and its partner service device is offline or a backup service device. Otherwise, it is the backup service device itself, and its partner service device is the main service device. If the CoreID is not the control center to which it belongs, the service device is an external service device.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the computer program is loaded into the processor, the hot backup method of the layer-2 active-standby information processing system according to claim 8 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the hot backup method of the layer-2 active-standby information processing system according to claim 8 is implemented.

Images