CN101043310B - Image backup method for dual-core control of core controlled system - Google Patents
Image backup method for dual-core control of core controlled system Download PDFInfo
- Publication number
- CN101043310B CN101043310B CN2007100988158A CN200710098815A CN101043310B CN 101043310 B CN101043310 B CN 101043310B CN 2007100988158 A CN2007100988158 A CN 2007100988158A CN 200710098815 A CN200710098815 A CN 200710098815A CN 101043310 B CN101043310 B CN 101043310B
- Authority
- CN
- China
- Prior art keywords
- service
- core
- kernel
- kernel service
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Abstract
The invention relates to the communication technology field, especially relates to two-core control mirror backup method. The method adopts the mechanism of the mirror heat backup, the core service allocates two independent mirror services, and it stores the control data for the core service and provides the data analysis and data acquisition for the core service, and at the same time, it shares the data service of core service to reduce the work of core service. In the system without adopting two-core backup system, when the single core control sever happens fault and refresh resetting, it can obtain the running information from the mirror service to keep the system running cautiously. For the non-core control module, if it needs heating backup or sharing load, the main core service coordinate and control it. The invention adopts the mirror service to help the core service to finish the data backup and data analysis to improve the reliability and the flexibility of whole system.
Description
Technical field
The invention belongs to the software communication technical field, particularly a kind of two-core control mirror backup method of core control system.
Background technology
The tradition core control system often adopts single double-core control system, and in order to finish the switching of main preparation system, these two core control systems are synchronous except finishing heartbeat, determine the current active and standby state of using; Two core systems also have the real time data of preserving local terminal separately simultaneously, do not influence already present business in order to prevent active and standby switching, and the real time data that will carry out two core control systems simultaneously in real time is synchronous.If lock in time is too short, then the operating efficiency of two core control systems will be subjected to very big influence, if lock in time is excessive, then can't guarantee all current seamless switchings that have business.
And the present invention is in core control system, the core Control Server is responsible for controlling the operation of whole system, be unique in the whole system can not simultaneous two modules of working simultaneously, be the unique Single Point of Faliure of whole system, therefore need realize the hot backup of core Control Server by active/standby mode.When the Core server of working broke down, system should be able to monitor automatically, reports to the police, switch, and can move sustainedly and stably to guarantee whole system, and guarantee that current ongoing meeting is not affected, and whole system can be carried out seamless switching.
Simultaneously, even the double-core server breaks down simultaneously, also can return to normal working condition rapidly at short notice and do not influence current ongoing meeting as far as possible.Therefore, the present invention adopts the mechanism of mirror heat backup, for Core server disposes two independently mirror image servers, preserved the control data of Core server respectively and the function of data analysis and data acquisition is provided for kernel service, share the data, services work of kernel service simultaneously, alleviate the load of kernel service.Even the double-core service is broken down simultaneously, also can from any one mirroring service, obtain real-time running data and recovery system operation immediately immediately.
After adopting the mirror back-up mode, the reliability of whole system is significantly promoted, even the single core control system breaks down, also can obtain data and recovery system operation immediately immediately from mirroring service.
In addition, if each non-core module need be done redundancy backup, then finish in the control of kernel service with under coordinating.The arrangement of the various tasks of non-core module all has the master to dispatch with nucleus module, guarantees the live load and the normal operation of all non-core modules.
Summary of the invention
The two-core control mirror backup method that the purpose of this invention is to provide a kind of core control system is characterized in that comprising following backup mode:
1) two-node cluster hot backup, be meant the system that has higher requirements for system stable operation, kernel service adopts two-node cluster hot backup (active/standby) mode to dispose, and active and standbyly is deployed in respectively on the two-server with kernel service, active and standbyly keeps data sync with kernel service;
2) unit double-core Hot Spare is meant for the less one-of-a-kind system of capacity, also can be in two kernel services of same Core server deploy, and the active and standby each other relation of using in case the kernel service of main usefulness is broken down, is then enabled the spare core service immediately;
3) unit single core backup is meant and only disposes a kernel service on unit, in case it breaks down, restart this kernel service immediately, obtain real-time operation information immediately from mirroring service, the normal operation of recovery system does not immediately influence the current meeting operation of handling;
4) backup of non-core module, carry out the non-core module of Hot Spare for needs, by main with kernel service control its active and standby with relation and real time data synchronously and upgrade, and carry out the non-core module of cluster backup for needs, coordinate and dispatch with kernel service by main.
Described two-node cluster hot backup, the system that has higher requirements for system stable operation, kernel service adopts two-node cluster hot backup (active/standby) mode to dispose, active and standbyly be deployed on the two-server respectively with kernel service, active and standbyly keep data sync with kernel service, in case the master unusual cisco unity malfunction occurs with kernel service,, guarantee the entire domain normal use of recovery fully at short notice then by its function of spare core service take-over.
Described two-node cluster hot backup, system will dispose two mirroring services, each mirroring service simultaneously to main with kernel service login and subscription incident to obtain the real time execution information of whole system.
Described two-node cluster hot backup, active and standby with adopting the heartbeat line to connect between the server, the heartbeat line should be isolated with the network environment of whole system operation, if the master is broken down with kernel service, then diagnose the spare core Service Activation, guarantee the whole system normal use of recovery fully at short notice by heartbeat.
Described two-node cluster hot backup, Be Controlled unit all in the system are all logined with kernel service to main, switch in case active and standby using taken place in kernel service, then the master after switching sends heartbeat and other control request with kernel service immediately, and accepts the control of master with kernel service.
Described recover to switch be meant that two kernel services can be not reciprocity, one of them priority is higher, as long as the high kernel service operate as normal of priority it just must be main using.
Described recover to switch have only the high kernel service of priority to break down just to enable the low core of priority to be engaged in, in case the high kernel service of priority returns to normal operating state, then automatically it is switched to the main state of using.
The two-core control mirror backup method of described core control system is characterized in that described system operating procedure is as follows:
Kernel service started when 1) system moved;
2) be set to standby and the notice opposite end;
3) kernel service sends heartbeat to another kernel service;
4) if heartbeat has response, and opposite end service is main usefulness, so then remains on and do not use state.Regularly send heartbeat to the opposite end, if not response of heartbeat so just self is set to main usefulness, and the notice opposite end;
5) obtain real time data to mirroring service;
6) notify all clients entities of having logined to switch;
7) remain on the main state of using, regularly send heartbeat message to the opposite end;
8) if heartbeat responds and the opposite end is main usefulness, then turn back to step 2), continue operation.Turn back to heartbeat does not have response then turns back to step 7) and continue operation if heartbeat is reactionless, if heartbeat responds and the opposite end be not main with then turn back to step 7) and continue to move.
Compared with prior art, beneficial effect of the present invention is:
Adopt mirroring service to assist kernel service to finish the function of data backup and data analysis, thereby greatly improved the reliability and the flexibility of whole system.
Description of drawings
Fig. 1 is the fundamental diagram of a kind of two-core control mirror backup method of the present invention;
Fig. 2 is the flow chart of data sync between the kernel service of a kind of two-core control mirror backup method of the present invention and mirroring service;
Fig. 3 is the active and standby main flow chart that obtains real-time running data with kernel service to mirroring service in back that switches of a kind of two-core control mirror backup method of the present invention;
Fig. 4 is system's operational flow diagram of a kind of two-core control mirror backup method of the present invention.
Embodiment
The present invention relates to a kind of two-core control mirror backup method, the invention will be further described below in conjunction with the drawings and specific embodiments, but not as a limitation of the invention.
In the implementation case, the back-up job principle as shown in Figure 1.In the present embodiment, kernel service provides the interface of service data inquiry and data change notice, the real time data of inquiring about all operations to the master with kernel service when mirroring service starts, and in running, subscribe to the data variation notification event of kernel service always, keep data sync at any time with kernel service.See also Fig. 2, step is as follows:
Steps A-1: mirroring service is sent logging request to the spare core service;
Steps A-2: the spare core service returns to mirroring service to login failure information;
Steps A-3: if login-timeout does not have response, mirroring service is then to another kernel service request login;
Steps A-4: the master will login successful information with kernel service and return to mirroring service;
Steps A-5: mirroring service is to the main kernel service subscription data Notification of Changes incident of using;
Steps A-6: the master will subscribe to successful information with kernel service and return to mirroring service;
Steps A-7: mirroring service is to the main current service data of kernel service acquisition request of using;
Steps A-8: the master returns to mirroring service with kernel service with current service data;
Steps A-9: main with the kernel service distributing data change notification time;
Steps A-10: the master changes with kernel service notice mirroring service data.
In the implementation case, when masterslave switchover took place, the master after switching obtained real-time service data to any one mirroring service immediately with kernel service.See also Fig. 3, step is as follows:
Step B-1: the master after the switching uses kernel service to mirroring service 1 acquisition request service data;
Step B-2: if the not response of pleading in the steps A-1 then sends the service data request to mirroring service 2;
Step B-3: the master of mirroring service 2 after switching sends the information of accepting request with kernel service;
Step B-4: the master of mirroring service 2 after switch obtains service data with kernel service;
Step B-5: the master after the switching is subjected to moving the data of returning from mirroring service 2 with kernel service;
Step B-6: the master of mirroring service 2 after switch obtains service data with kernel service;
Step B-7: the master after the switching is subjected to moving the data of returning from mirroring service 2 with kernel service, and system replys operate as normal immediately;
The operation of whole system, referring to Fig. 4, step is as follows:
Step 401: kernel service started when system moved;
Step 402: be arranged at standby and the notice opposite end;
Step 403: kernel service sends heartbeat to another kernel service;
Step 404: when judging heartbeat response is arranged all, execution in step 405 if heartbeat is responded, otherwise execution in step 406;
Step 405: replying message according to heartbeat is main usefulness all when judging the other side, is execution in step 407 then, otherwise execution in step 406;
Step 406: self be set to main usefulness, and the notice opposite end;
Step 407: remain on stand-by state, regularly send heartbeat to the opposite end;
Step 408: obtain real time data to mirroring service;
Step 409: all clients entities that notice has been logined switch;
Step 410: judging whether heartbeat responds, is execution in step 411 then, otherwise execution in step 409;
Step 411: replying message according to heartbeat is main usefulness all when judging the other side, is execution in step 402 then, otherwise execution in step 409.
The key technology that is meant active and standby handoff functionality that automaticallyes switch is how active and standby kernel service determines a side to be operational mode, and the opposing party is a standby mode.
Two Core servers are by being independent of the heartbeat line interconnection of whole network.Because the caused unnecessary system of potential miscommunication is switched, many communication paths of different medium should be arranged in order to reduce, active and standby with the path that should have many to send heartbeat message between the server, many heartbeat lines can be arranged.
For handoff functionality is finished in cooperation, the heartbeat signal state between the kernel service is divided into 4 kinds:
Initial condition: do not find the other side's kernel service.
Wait state: find the other side's kernel service but not affirmation of both sides.
The main state of use: find the other side's kernel service and confirmed that this kernel service is main usefulness, perhaps confirm overtime become automatically to lead use kernel service, this is a stable state.
Stand-by state: find the other side's kernel service, and confirmed that this kernel service is standby, this is a stable state.
Manual switching state: send the Manual Switch order to the other side, do not obtain the state of answering.(manual switching refers to that the keeper passes through current two kernel services of webmaster order request and switches main usefulness/standby mode mutually)
In the implementation case, the manual switchover function is provided, the system manager can main with the kernel service load when excessive or other suitable in, realize manual switchover.
At the service data synchronization aspects, the real-time running data of whole system and configuration data are stored in the kernel service, need the data sync of the kernel service of the active and standby usefulness of assurance.Active and standby with mirroring service by subscribing to main all incidents with kernel service, keep and main mirror image data with kernel service, in case switch, the spare core service obtains main real time data with kernel service from standby mirroring service immediately.
If manual switchover, active and standbyly before switching initiatively carry out data sync with the kernel service meeting.
If automatically switch, illustrate original main with kernel service with mainly therefore can not obtain data from main with kernel service again with mirroring service cisco unity malfunction, but from the standby current service data of mirroring service acquisition.
At the configuration data synchronization aspects, when network management system is revised system configuration, always revise main configuration with side.During configuration modification, main with kernel service meeting issue configuration modification incident, the incident of configuration modification is received in prepped side mirroring service meeting immediately.
If manual switchover, active and standbyly before switching can initiatively carry out the center configuration data sync with core.
If automatically switch, illustrate that original master with kernel service cisco unity malfunction, therefore can not obtain the center configuration data from main with kernel service again, but from the current configuration data of mirroring service acquisition.
Kernel service can be configured data sync when starting automatically.
All non-core modules regularly send heartbeat message to primary and backup kernel service, and the master responds the heartbeat success after receiving heartbeat message with kernel service immediately, after the spare core service receives heartbeat message, then responds the heartbeat failure immediately.Non-core module can judge which is that the master uses kernel service, and which is the spare core service according to the response of heartbeat.Also can all non-core modules of proactive notification when simultaneously, kernel service switches.
Claims (3)
1. the two-core control mirror backup method of a core control system, it is characterized in that it being the interface that service data inquiry and data change notice are provided by Core server, during the mirroring service program start, to main real time data of inquiring about all operations with kernel service, and in running, subscribe to the data variation notification event of kernel service always, keep data sync at any time with kernel service; Comprise two-node cluster hot backup, unit double-core Hot Spare and the backup of unit single core;
Described two-node cluster hot backup is meant that kernel service adopts the two-node cluster hot backup mode to dispose, and active and standbyly is deployed on the two-server respectively with kernel service; Dispose two mirroring services simultaneously, each mirroring service simultaneously to main with kernel service login and subscription incident to obtain the real time execution information of whole system;
Described unit double-core Hot Spare is meant in two kernel services of same Core server deploy, and is active and standby each other with relation, in case the kernel service of main usefulness is broken down, then enables the spare core service immediately;
Described two-node cluster hot backup and unit double-core Hot Spare operating procedure are as follows:
Kernel service started when 1) system moved;
2) be set to standby and the notice opposite end;
3) kernel service sends heartbeat to another kernel service;
4) if heartbeat has response, and opposite end service is main usefulness, remains on stand-by state so, regularly sends heartbeat to the opposite end, turns back to step 3) and continues operation; If heartbeat is response not, so just self be set to main usefulness, and the notice opposite end;
5) obtain real time data to mirroring service;
6) notify all clients entities of having logined to switch;
7) remain on the main state of using, regularly send heartbeat message to the opposite end;
8) if heartbeat responds and the opposite end is main usefulness, then turn back to step 2), continue operation, turn back to step 7) if heartbeat is reactionless and continue operation, if heartbeat responds the opposite end be not main with then turn back to step 7) and continue to move;
Described kernel service provides the interface of service data inquiry and data change notice;
To main real time data of inquiring about all operations with kernel service, and subscribe to the data variation notification event of kernel service in running when described mirroring service starts always, keep the data sync with kernel service at any time, concrete steps are as follows:
A1) mirroring service is sent logging request to the spare core service;
A2) the spare core service returns to mirroring service to login failure information;
A3) if login-timeout does not have response, mirroring service is then to another kernel service request login;
A4) master will login successful information with kernel service and return to mirroring service;
A5) mirroring service is to the main kernel service subscription data Notification of Changes incident of using;
A6) master will subscribe to successful information with kernel service and return to mirroring service;
A7) mirroring service is to the main current service data of kernel service acquisition request of using;
A8) master returns to mirroring service with kernel service with current service data;
A9) main with the kernel service distributing data change notification time;
A10) master changes with kernel service notice mirroring service data;
In the described two-node cluster hot backup,,, guarantee the entire domain normal use of recovery fully at short notice then by its function of spare core service take-over in case the master unusual cisco unity malfunction occurs with kernel service;
Described unit single core backup, be meant and on unit, only dispose a kernel service, in case it breaks down, restart this kernel service immediately, from mirroring service, obtain real-time operation information immediately, the normal operation of recovery system does not immediately influence the current meeting operation of handling;
Carry out the non-core module of Hot Spare for needs, by main with kernel service control its active and standby with relation and real time data synchronously and upgrade, and carry out the non-core module of cluster backup for needs, coordinate and dispatch with kernel service by main.
2. according to the two-core control mirror backup method of the described core control system of claim 1, it is characterized in that described two-node cluster hot backup, active and standby with adopting the heartbeat line to connect between the server, the heartbeat line should be isolated with the network environment of whole system operation, if the master is broken down with kernel service, then diagnose the spare core Service Activation, guarantee the whole system normal use of recovery fully at short notice by heartbeat.
3. according to the two-core control mirror backup method of the described core control system of claim 1, it is characterized in that described two-node cluster hot backup, Be Controlled unit all in the system are all logined with kernel service to main, in case kernel service takes place active and standby with switching, then the master after switching sends heartbeat and other control request and accepts main control with kernel service with kernel service immediately.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100988158A CN101043310B (en) | 2007-04-27 | 2007-04-27 | Image backup method for dual-core control of core controlled system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100988158A CN101043310B (en) | 2007-04-27 | 2007-04-27 | Image backup method for dual-core control of core controlled system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101043310A CN101043310A (en) | 2007-09-26 |
| CN101043310B true CN101043310B (en) | 2010-09-08 |
Family
ID=38808549
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007100988158A Expired - Fee Related CN101043310B (en) | 2007-04-27 | 2007-04-27 | Image backup method for dual-core control of core controlled system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101043310B (en) |
Families Citing this family (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101742231B (en) * | 2008-11-25 | 2012-04-25 | 北京视博数字电视科技有限公司 | Equipment management method and system and server thereof |
| CN101771563B (en) * | 2008-12-30 | 2012-07-25 | 北大方正集团有限公司 | Method for monitoring network service program |
| CN101989084B (en) * | 2009-07-29 | 2012-05-23 | 中国铝业股份有限公司 | Data release system for thermal power station and matched system |
| CN101887256B (en) * | 2010-05-11 | 2012-06-13 | 深圳绿拓科技有限公司 | Concentrated-distributed wireless control system and controller |
| CN101984582B (en) * | 2010-11-16 | 2014-12-17 | 中兴通讯股份有限公司 | Mirror image method, device and communication equipment for circuit emulation service |
| CN102402220B (en) * | 2011-01-21 | 2013-10-23 | 南京航空航天大学 | Load sharing fault tolerant flight control system and fault detection method |
| CN102999395B (en) * | 2011-09-09 | 2016-05-18 | 腾讯科技（北京）有限公司 | A kind of data read-write method and system |
| CN103001787B (en) * | 2011-09-16 | 2016-08-03 | 中国银联股份有限公司 | System and method for data processing centre's disaster-tolerant backup |
| CN102546250B (en) * | 2011-12-31 | 2014-06-18 | 山东中创软件商用中间件股份有限公司 | File publishing method and system based on main/standby mechanism |
| CN102945193B (en) * | 2012-10-24 | 2018-11-16 | 广州市动景计算机科技有限公司 | A kind of restoration methods and electronic equipment of operation data |
| CN103838642B (en) * | 2012-11-26 | 2018-03-13 | 腾讯科技（深圳）有限公司 | A kind of data reconstruction method, device and system |
| CN103279386A (en) * | 2013-06-09 | 2013-09-04 | 浪潮电子信息产业股份有限公司 | Method for achieving high availability of computer operation scheduling system |
| CN104426968B (en) * | 2013-08-30 | 2019-05-24 | 腾讯科技（深圳）有限公司 | Data managing method and device |
| CN103425553B (en) * | 2013-09-06 | 2015-01-28 | 哈尔滨工业大学 | Duplicated hot-standby system and method for detecting faults of duplicated hot-standby system |
| CN103546914B (en) * | 2013-10-21 | 2017-07-21 | 大唐移动通信设备有限公司 | A kind of method and device of the active and standby management of HSS |
| CN103701667A (en) * | 2013-12-27 | 2014-04-02 | 乐视网信息技术（北京）股份有限公司 | Method, device and system for monitoring heartbeat of server |
| CN104503932B (en) * | 2015-01-07 | 2017-11-24 | 加弘科技咨询(上海)有限公司 | More mainboard server main substrate Management Controller referee methods and system |
| US9836368B2 (en) * | 2015-10-22 | 2017-12-05 | Netapp, Inc. | Implementing automatic switchover |
| CN105516365A (en) * | 2016-01-22 | 2016-04-20 | 浪潮电子信息产业股份有限公司 | Method for managing a distributed type mirror image storage block device based on network |
| CN107241295A (en) * | 2016-03-28 | 2017-10-10 | 阿里巴巴集团控股有限公司 | Encryption management method and device, control cluster |
| CN105974906B (en) * | 2016-05-12 | 2019-12-17 | 深圳市中工巨能科技有限公司 | Double-monitoring-activating measurement and control device |
| CN109271274B (en) * | 2018-11-13 | 2022-02-11 | 天津津航计算技术研究所 | Dual-computer hot standby method of embedded system |
| CN109615836A (en) * | 2018-12-27 | 2019-04-12 | 讯之美物联网服务有限公司 | A kind of method of one key of collaborative alarm |
| CN110417584A (en) * | 2019-07-10 | 2019-11-05 | 南京南瑞继保电气有限公司 | A kind of two-shipper main/standby switching method based on multi-link election mechanism |
| CN111284429B (en) * | 2020-01-23 | 2022-06-24 | 博泰车联网科技(上海)股份有限公司 | Vehicle alarm method, vehicle-mounted equipment, computer storage medium and system |
| CN111554368B (en) * | 2020-04-27 | 2023-07-28 | 贵州精准健康数据有限公司 | System and method for intercommunication between public health system and medical system |
| CN113346983B (en) * | 2021-08-03 | 2021-11-02 | 浙江国利信安科技有限公司 | EPA equipment with mirror redundancy and EPA system |
| CN114138366A (en) * | 2021-11-30 | 2022-03-04 | 驭势（上海）汽车科技有限公司 | Service control method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN2257937Y (en) * | 1995-05-18 | 1997-07-16 | 浙江大学 | Multi-user system data dual real time duplicating instrument |
| EP1533701A1 (en) * | 2003-11-24 | 2005-05-25 | TSX Inc. | System and method for failover |
| CN1787446A (en) * | 2005-12-09 | 2006-06-14 | 深圳市台电实业有限公司 | Electronic conference system and method for multi main machine coordination working |
| CN1829168A (en) * | 2006-04-12 | 2006-09-06 | 深圳市台电实业有限公司 | Conference system and its double computer heat backup operating method for managing system software |
-
2007
- 2007-04-27 CN CN2007100988158A patent/CN101043310B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN2257937Y (en) * | 1995-05-18 | 1997-07-16 | 浙江大学 | Multi-user system data dual real time duplicating instrument |
| EP1533701A1 (en) * | 2003-11-24 | 2005-05-25 | TSX Inc. | System and method for failover |
| CN1787446A (en) * | 2005-12-09 | 2006-06-14 | 深圳市台电实业有限公司 | Electronic conference system and method for multi main machine coordination working |
| CN1829168A (en) * | 2006-04-12 | 2006-09-06 | 深圳市台电实业有限公司 | Conference system and its double computer heat backup operating method for managing system software |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101043310A (en) | 2007-09-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101043310B (en) | Image backup method for dual-core control of core controlled system | |
| CN100362482C (en) | Dual-machine back-up realizing method and system | |
| CN103199972A (en) | Double machine warm backup switching method and warm backup system achieved based on SOA and RS485 bus | |
| CN106375342A (en) | Zookeeper-technology-based system cluster method and system | |
| CN101621394B (en) | Disaster-tolerant system for processing telephone traffic data | |
| CN103346903A (en) | Dual-machine backup method and device | |
| US8032786B2 (en) | Information-processing equipment and system therefor with switching control for switchover operation | |
| CN101110776B (en) | Backup method, backup device and backup system for data business | |
| CN102752093B (en) | Based on the data processing method of distributed file system, equipment and system | |
| CN106850255B (en) | Method for implementing multi-machine backup | |
| US20080163248A1 (en) | System and method for completeness of tcp data in tcp ha | |
| CN102388570B (en) | Single board running method and system under active-standby mode | |
| WO2007048319A1 (en) | A disaster recovery system and method of service controlling device in intelligent network | |
| JP2560687B2 (en) | Communication method with line | |
| CN110677282B (en) | Hot backup method of distributed system and distributed system | |
| CN102055950B (en) | MCU backup method and equipment in video conference | |
| US10929254B2 (en) | Data processing system providing service continuity protection | |
| CN101753339B (en) | Method for realizing conference backup function of multi-point control unit and system thereof | |
| CN107040403A (en) | The method that Distributed system reliability is improved based on DDS technologies | |
| WO2006005251A1 (en) | Method and system for carrying out the function of switching in a communication system | |
| CN111262892B (en) | Multi-ROS service discovery system | |
| CN102045187A (en) | Method and equipment for realizing HA (high-availability) system with checkpoints | |
| CN102932118B (en) | The method and system of the active and standby ruling of a kind of two-shipper | |
| CN102055605A (en) | Disaster tolerance system and method applied to AAA (authentication, authorization and accounting) server | |
| CN101217591A (en) | A method and system realizing snooping data storage |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100908 Termination date: 20160427 |