CN101729290A - Method and device for realizing business system protection - Google Patents
Method and device for realizing business system protection Download PDFInfo
- Publication number
- CN101729290A CN101729290A CN200910110488A CN200910110488A CN101729290A CN 101729290 A CN101729290 A CN 101729290A CN 200910110488 A CN200910110488 A CN 200910110488A CN 200910110488 A CN200910110488 A CN 200910110488A CN 101729290 A CN101729290 A CN 101729290A
- Authority
- CN
- China
- Prior art keywords
- node
- secondary node
- operation system
- host node
- database
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Selective Calling Equipment (AREA)
Abstract
The invention discloses a method and a device for realizing business system protection; a main node provides service for a service system, and the data of the main node is backed up to a spare node; the method comprises the following steps: a monitoring node detects whether the main node has faults; when the main node has the faults, the monitoring node controls the spare node for providing service for the service system; when the main node has the faults, the spare node is switched to the main node and replaces the main node for providing service for the service system, so as to ensure the service system to work continuously when accidents happen and avoid loss caused by users.
Description
Technical field
The present invention relates to realize the method and the device of operation system protection.
Background technology
A lot of key business systems needed run without interruption in 24 hours, the OSS of telecommunications for example, the operation system of bank etc.These key business systems will be even of short duration quitting work all will bring very big loss to enterprise.In order to reduce the out-of-work probability of happening of system as far as possible, need take the precautionary measures in advance at the various fortuitous events that may occur, when accident takes place, reduce various accidents to greatest extent and cause the out-of-work possibility of operation system.
Summary of the invention
The object of the present invention is to provide method and the device of realizing the operation system protection, when guaranteeing unexpected the generation, operation system works on.
The invention provides a kind of method that realizes operation system protection, host node provides service for operation system, and the data of described host node are backuped to secondary node, and this method comprises:
Monitor node detects whether fault of described host node;
When described host node fault, described monitor node is controlled described secondary node and is provided service for described operation system.
Further, the data of described host node being backuped to secondary node comprises:
The database of described host node records journal file with data modification;
The database backstage of described host node is transferred to described journal file the database of described secondary node;
The database backstage of described secondary node is applied to described journal file the database of described secondary node.
Further, the data of described host node being backuped to secondary node also comprises:
When the database of described secondary node just often, adopt method of synchronization transmission journal file between the database of described host node and the database of described secondary node;
When the database response of described secondary node is overtime, adopt asynchronous system transmission journal file between the database of described host node and the database of described secondary node.
Further, described monitor node detects described host node whether fault comprises:
Described monitor node detects the network link situation between described monitor node and described host node and the secondary node respectively;
When described monitor node detects network link between described monitor node and the described host node when unusual, inquire about network link situation between described host node and the secondary node to described secondary node;
When inquiring network link between described host node and the secondary node when unusual, judge described host node fault, otherwise, judge that described host node is normal.
Further, described network link comprises: with the linking of database server, with application server link and/or with the linking of interface server.
Further,, described monitor node is controlled described secondary node and is comprised for described operation system provides service:
Described monitor node sends switching command to described secondary node, is used to control described secondary node and switches to host node;
Described monitor node starts the name server of former secondary node;
Described monitor node is controlled described operation system and is visited former secondary node by the parsing of the name server of described former secondary node.
Further, described operation system is visited former secondary node by the parsing of the name server of described former secondary node and is comprised:
The name server of described former secondary node is mapped to the domain name of application server the Internet protocol address of the application server of former secondary node;
The parsing of the name server by described former secondary node, described operation system is visited the application server of described former secondary node;
And/or the name server of described former secondary node is mapped to the domain name of interface server the Internet protocol address of the interface server of former secondary node;
The parsing of the name server by described former secondary node, described operation system is visited the interface server of described former secondary node.
The present invention also provides a kind of device of realizing operation system protection, is applied to host node and provides service for operation system, and the data of described host node are backuped to secondary node, and this device comprises:
Monitoring means is used to detect whether fault of described host node;
Control unit is used for when described host node fault, and described monitor node is controlled described secondary node and provided service for described operation system.
Further, described monitoring means comprises:
Detection sub-unit is used for detecting respectively the device of described realization operation system protection and the network link situation between described host node and the secondary node;
The inquiry subelement is used for when detecting device that described realization operation system protects and the network link between the described host node when unusual, inquires about network link situation between described host node and the secondary node to described secondary node;
Judgment sub-unit is used for judging described host node fault when inquiring network link between described host node and the secondary node when unusual, otherwise, judge that described host node is normal.
Further, described control unit comprises:
Switch subelement, be used for sending switching command to described secondary node, described switching command is used to control described secondary node and switches to host node;
The promoter unit is used to start standby name server;
Control sub unit is used to control described operation system and visits former secondary node by the parsing of the name server of described former secondary node.
Adopt the method and the device of realization operation system protection provided by the invention, when the host node fault, secondary node switches to host node; take over host node and provide service for operation system; thereby when guaranteeing unexpected the generation, operation system works on, and avoids the user is brought loss.
Description of drawings
Fig. 1 illustrates DB Backup flow chart in the embodiment of the invention;
Fig. 2 illustrates the networking structure figure of the method that realizes the operation system protection in the embodiment of the invention;
Fig. 3 illustrates a kind of data switching sequence figure in the embodiment of the invention;
Fig. 4 illustrates the structural representation of the device of realizing the operation system protection in the embodiment of the invention.
Embodiment
Below in conjunction with accompanying drawing the specific embodiment of the present invention is done and to be elaborated.In order to guarantee the high availability of operation system, the present invention backs up in realtime by the data strange land and controls the protection of name server realization to operation system.
This programme comprises the content of five aspects: the switching of the switching of Database Backup, database, the configuration of network, network, network control and node switching controls module.
DB Backup sees also Fig. 1, the change of the database (hereinafter to be referred as master data base) of host node is transferred to the database (standby database) of secondary node by journal file.Master data base will record journal file to all modifications of database, the master data base background process is responsible for journal file is real-time transmitted to standby database, background process on the standby database is applied to standby database with the journal file that passes over, thereby the data in master/slave data storehouse are consistent.
Database switches when referring to that master data base is unavailable, and standby database switches to master data base and bears the process of operation system operation.When confirming that master data bank system is unavailable, the journal file on the affirmation standby database switches to the master data base pattern with standby database after using and finishing.
The main purpose of network configuration is when host node is unavailable, and operation system can be connected to the former secondary node that switches to host node automatically.The concrete grammar of configuration is 1, operation system is by domain name access application server, database server, interface server.2, answer the name server of operation system host node to be set to primary name server, the name server of secondary node is set to standby name server.Wherein, operation system includes but not limited to application terminal and external system.
When host node is unavailable, network will take place switch.Concrete process is: after 1, the database switching was finished, standby name server was mapped to standby database server internet protocol (Internet Protocol, IP) address with the database domain name of operation system.2, the domain name of application server is mapped to the IP address of standby application server.3, the domain name of interface server is mapped to the IP address of spare interface server.4, from the domain name mapping of trend backup domain name server requests, standby name server does not return the IP address of secondary node because primary name server (host node is unavailable) responds for application terminal and external system.
Network measuring and node switching controls module major function are to detect the state of network linking, are confirming that the map addresses by the control name server reaches the purpose that service is automaticallyed switch under network or the in-problem situation of server.The network measuring module is deployed in A, B, C three ground, whether the link that detects every station server in the network is normal, and the detection module that is deployed in different nodes can be inquired the network linking situation between the other side and any server (server that comprises node server and secondary node) mutually.Node switching controls module major function is under the situation of confirming node or server failure, by the control name server, server domain name is mapped on the server of secondary node, thus the automatic switchover of realization malfunctioning node.
Concrete, see also Fig. 2, realize that the method for operation system protection can comprise:
Database configuration comprises: the database on A ground is arranged to master data base, the database on B ground is arranged to standby database.The Database Backup mode is selected the physics backup mode.Journal file is selected synchronous generating mode at the generating mode of master data base.The data protection pattern is set to maximum available protected mode on master data base, but promptly when active and standby two databases time spent all, the transfer of data between the master/slave data storehouse adopts the method for synchronization.When the standby database response timeout, the transfer of data between the master/slave data storehouse automatically switches to asynchronous system.After standby database recovered normally, transfer of data switched to the method for synchronization again.Journal file is selected real-time application mode in the application mode of standby database; All all embody at standby database synchronously in the change that master data base takes place.Switching mode between main-standby nodes is selected quick switching mode; The 3rd ground C outside A, B two places is provided with monitor node, with monitoring C to A and C to the network linking between B.The link down time threshold that configuration switches.
The database switching comprises, sees also Fig. 3:
301, the node switching controls module among the monitor node C is to the network state inquiry of A meshed network monitoring module to the A node.
302, the node switching controls module among the monitor node C detect and A between network link surpassed default threshold value break period, i.e. not response of monitoring module A (A meshed network monitoring module).
303, whether the network between monitor node C inquiry Node B and the A is normal, and promptly node switching controls module is to the network state of B meshed network monitoring module query node A.
If the network that 304 B respond between B and the A is normal, C only sends warning information, does not send the main-standby nodes switching command.In the present embodiment, B meshed network monitoring module returns the information that whole node A can not arrive.
305, C sends the main-standby nodes switching command to standby database, promptly sends master/slave data storehouse switching command.
306, after the standby database of B node receives instruction, check whether all daily records all use, daily record switches to the master data base mode operation after using and finishing.C detects to switch to former standby database and finishes.
307, after switching was finished, C sent the instruction of domain name configuration modification to the standby name server of B node, the database domain name is mapped as the IP address of former standby database.
Network configuration comprises: application terminal and external interface system are by domain name access database, application server and interface server.A, B two places all are furnished with name server; A is a primary name server, and B is standby name server.The name server on application terminal and external interface system A ground is set to primary name server, and the name server on B ground is set to standby name server.Same domain name, for example the application server domain name is mapped as the application server address on A ground with it on A region name server.On B region name server, it is mapped as the application server address on B ground.
Network handoff scenario one: node A is unavailable or database A is unavailable
1, after database was finished switching, standby name server was mapped to the standby database server ip address with the database domain name of operation system;
2, standby name server is enabled;
3, standby name server is mapped to the domain name of application server the IP address of standby application server;
4, standby name server is mapped to the domain name of interface server the IP address of spare interface server;
5, the application terminal can't be visited owing to primary name server, by standby domain name server parses domain name;
6, by the parsing of standby name server, the application terminal has access to standby application server automatically;
7, by the parsing of standby name server, the external interface system has access to standby interface server automatically.
Network handoff scenario two: the application server of node A is unavailable, and other servers are normal
1, the switching controls node finds that the application server of node A is unavailable;
2, the network monitoring module of switching controls node inquiry Node B, whether the application server A of Node B monitoring module and node A is normal;
3, the Node B monitoring module return with application server A link undesired;
4, the application server of switching controls node affirmation Node B can be used;
5, the switching controls node points to application server domain name on the A region name server IP address of Node B application server;
6, the application terminal will be connected with the application server of Node B by the name server access application server.
Network handoff scenario three: certain interface server of node A is unavailable, and other servers are normal
1, the switching controls node finds that the interface server A1 of node A is unavailable;
2, the network monitoring module of switching controls node inquiry Node B, whether the interface server A1 of Node B monitoring module and node A is normal;
3, the Node B monitoring module return with interface server A1 link undesired;
4, the switching controls node confirms that the Node B interface server B1 corresponding with A1 can use;
5, the switching controls node points to the domain name of interface server 1 on the A region name server IP address of Node B interface server B1;
6, external system will be connected with the interface server B1 of Node B by name server access interface server 1.
Fig. 4 illustrates the structural representation of the device of realizing the operation system protection in the embodiment of the invention.See also Fig. 4, be applied to host node and provide service for operation system, the data of host node are backuped to secondary node, this device comprises:
Monitoring means 401 is used to detect whether fault of host node;
Further, monitoring means 401 can comprise:
Detection sub-unit 401-1 is used for detecting respectively the device of realization operation system protection and the network link situation between host node and the secondary node;
Inquiry subelement 401-2 is used for when detecting the device of realizing the operation system protection and the network link between the host node when unusual, inquires about network link situation between host node and the secondary node to secondary node;
Judgment sub-unit 401-3 is used for judging the host node fault when inquiring network link between host node and the secondary node when unusual, otherwise, judge that host node is normal.
Further, control unit 402 can comprise:
Switch subelement 402-1, be used for sending switching command to secondary node, switching command is used to control secondary node and switches to host node;
Promoter unit 402-2 is used to start standby name server;
Control sub unit 402-3 is used to control operation system and visits former secondary node by the parsing of the name server of former secondary node.
The above only is the specific embodiment of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.
Claims (10)
1. a method that realizes operation system protection is characterized in that host node provides service for operation system, and the data of described host node are backuped to secondary node, and this method comprises:
Monitor node detects whether fault of described host node;
When described host node fault, described monitor node is controlled described secondary node and is provided service for described operation system.
2. method according to claim 1 is characterized in that, the data of described host node is backuped to secondary node comprise:
The database of described host node records journal file with data modification;
The database backstage of described host node is transferred to described journal file the database of described secondary node;
The database backstage of described secondary node is applied to described journal file the database of described secondary node.
3. method according to claim 2 is characterized in that, the data of described host node is backuped to secondary node also comprise:
When the database of described secondary node just often, adopt method of synchronization transmission journal file between the database of described host node and the database of described secondary node;
When the database response of described secondary node is overtime, adopt asynchronous system transmission journal file between the database of described host node and the database of described secondary node.
4. method according to claim 1 is characterized in that, described monitor node detects described host node, and whether fault comprises:
Described monitor node detects the network link situation between described monitor node and described host node and the secondary node respectively;
When described monitor node detects network link between described monitor node and the described host node when unusual, inquire about network link situation between described host node and the secondary node to described secondary node;
When inquiring network link between described host node and the secondary node when unusual, judge described host node fault, otherwise, judge that described host node is normal.
5. method according to claim 4 is characterized in that, described network link comprises: with the linking of database server, with application server link and/or with the linking of interface server.
6. method according to claim 1 is characterized in that, described monitor node is controlled described secondary node and comprised for described operation system provides service:
Described monitor node sends switching command to described secondary node, is used to control described secondary node and switches to host node;
Described monitor node starts the name server of former secondary node;
Described monitor node is controlled described operation system and is visited former secondary node by the parsing of the name server of described former secondary node.
7. method according to claim 6 is characterized in that, described operation system is visited former secondary node by the parsing of the name server of described former secondary node and comprised:
The name server of described former secondary node is mapped to the domain name of application server the Internet protocol address of the application server of former secondary node;
The parsing of the name server by described former secondary node, described operation system is visited the application server of described former secondary node;
And/or the name server of described former secondary node is mapped to the domain name of interface server the Internet protocol address of the interface server of former secondary node;
The parsing of the name server by described former secondary node, described operation system is visited the interface server of described former secondary node.
8. a device of realizing operation system protection is characterized in that, is applied to host node and provides service for operation system, and the data of described host node are backuped to secondary node, and this device comprises:
Monitoring means is used to detect whether fault of described host node;
Control unit is used for when described host node fault, and described monitor node is controlled described secondary node and provided service for described operation system.
9. device according to claim 8 is characterized in that, described monitoring means comprises:
Detection sub-unit is used for detecting respectively the device of described realization operation system protection and the network link situation between described host node and the secondary node;
The inquiry subelement is used for when detecting device that described realization operation system protects and the network link between the described host node when unusual, inquires about network link situation between described host node and the secondary node to described secondary node;
Judgment sub-unit is used for judging described host node fault when inquiring network link between described host node and the secondary node when unusual, otherwise, judge that described host node is normal.
10. device according to claim 8 is characterized in that, described control unit comprises:
Switch subelement, be used for sending switching command to described secondary node, described switching command is used to control described secondary node and switches to host node;
The promoter unit is used to start standby name server;
Control sub unit is used to control described operation system and visits former secondary node by the parsing of the name server of described former secondary node.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910110488A CN101729290A (en) | 2009-11-04 | 2009-11-04 | Method and device for realizing business system protection |
PCT/CN2010/075305 WO2010149117A1 (en) | 2009-11-04 | 2010-07-20 | Method and apparatus for implementing service system protection |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910110488A CN101729290A (en) | 2009-11-04 | 2009-11-04 | Method and device for realizing business system protection |
Publications (1)
Publication Number | Publication Date |
---|---|
CN101729290A true CN101729290A (en) | 2010-06-09 |
Family
ID=42449562
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN200910110488A Pending CN101729290A (en) | 2009-11-04 | 2009-11-04 | Method and device for realizing business system protection |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101729290A (en) |
WO (1) | WO2010149117A1 (en) |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010149117A1 (en) * | 2009-11-04 | 2010-12-29 | 中兴通讯股份有限公司 | Method and apparatus for implementing service system protection |
CN102831038A (en) * | 2011-06-17 | 2012-12-19 | 中兴通讯股份有限公司 | Disaster tolerance method for ENUM-DNS (Telephone Number Mapping-Domain Name System) and ENUM-DNS |
WO2014032532A1 (en) * | 2012-09-03 | 2014-03-06 | 中兴通讯股份有限公司 | Enum-dns disaster recovery method and system in ims network |
CN104346373A (en) * | 2013-07-31 | 2015-02-11 | 华为技术有限公司 | Partition log queue synchronization management method and device |
CN104506353A (en) * | 2014-12-23 | 2015-04-08 | 北京奇虎科技有限公司 | Authentication management method, equipment and system |
CN105338078A (en) * | 2015-10-26 | 2016-02-17 | 北京百度网讯科技有限公司 | Data storage method and device used for storing system |
CN105512343A (en) * | 2016-01-06 | 2016-04-20 | 北京京东尚科信息技术有限公司 | Method and device for simulating network anomaly and testing automatic switching of database faults |
WO2016070530A1 (en) * | 2014-11-04 | 2016-05-12 | 中兴通讯股份有限公司 | Method and system for processing operation of primary and standby device |
WO2016173179A1 (en) * | 2015-04-29 | 2016-11-03 | 中兴通讯股份有限公司 | Method and device for switching primary database and secondary database |
CN106156086A (en) * | 2015-03-31 | 2016-11-23 | 西门子公司 | Hadoop platform system and host node log backup method thereof |
CN106202261A (en) * | 2016-06-29 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | The distributed approach of a kind of data access request and engine |
CN106254100A (en) * | 2016-07-27 | 2016-12-21 | 腾讯科技(深圳)有限公司 | A kind of data disaster tolerance methods, devices and systems |
CN106856489A (en) * | 2015-12-08 | 2017-06-16 | 阿里巴巴集团控股有限公司 | A kind of service node switching method and apparatus of distributed memory system |
CN107480014A (en) * | 2017-07-24 | 2017-12-15 | 北京奇安信科技有限公司 | A kind of High Availabitity equipment switching method and device |
WO2018023994A1 (en) * | 2016-08-05 | 2018-02-08 | 华为技术有限公司 | Disaster-recovery switching method, node, and system |
CN109101196A (en) * | 2018-08-14 | 2018-12-28 | 北京奇虎科技有限公司 | Host node switching method, device, electronic equipment and computer storage medium |
CN110502460A (en) * | 2018-05-16 | 2019-11-26 | 华为技术有限公司 | The method and node of data processing |
CN112990867A (en) * | 2021-03-11 | 2021-06-18 | 北京明略昭辉科技有限公司 | Method, system and equipment for realizing high availability of document platform service |
CN113609107A (en) * | 2021-09-30 | 2021-11-05 | 武汉四通信息服务有限公司 | Database management method and device, electronic equipment and storage medium |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105915366A (en) * | 2016-03-30 | 2016-08-31 | 苏州美天网络科技有限公司 | Efficient backup server system |
CN109005045B (en) * | 2017-06-06 | 2022-01-25 | 北京金山云网络技术有限公司 | Main/standby service system and main node fault recovery method |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7986618B2 (en) * | 2002-06-12 | 2011-07-26 | Cisco Technology, Inc. | Distinguishing between link and node failure to facilitate fast reroute |
US7710865B2 (en) * | 2005-02-25 | 2010-05-04 | Cisco Technology, Inc. | Disaster recovery for active-standby data center using route health and BGP |
CN101060391A (en) * | 2007-05-16 | 2007-10-24 | 华为技术有限公司 | Master and spare server switching method and system and master server and spare server |
CN101145972B (en) * | 2007-10-16 | 2012-09-05 | 中兴通讯股份有限公司 | A disaster tolerance network management system and login method of network management clients |
CN101227333B (en) * | 2008-02-02 | 2010-12-29 | 中兴通讯股份有限公司 | Disaster tolerance network managing system and login method of network managing subscriber end |
CN101309167B (en) * | 2008-06-27 | 2011-04-20 | 华中科技大学 | Disaster allowable system and method based on cluster backup |
CN101729305A (en) * | 2008-10-28 | 2010-06-09 | 华为技术有限公司 | Method and system for automatically restoring fault, and control network element |
CN101465768B (en) * | 2009-01-12 | 2011-11-02 | 上海及第熊软件科技有限公司 | Method and system for implementing website disaster-tolerating and error-tolerating operation |
CN101729290A (en) * | 2009-11-04 | 2010-06-09 | 中兴通讯股份有限公司 | Method and device for realizing business system protection |
-
2009
- 2009-11-04 CN CN200910110488A patent/CN101729290A/en active Pending
-
2010
- 2010-07-20 WO PCT/CN2010/075305 patent/WO2010149117A1/en active Application Filing
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010149117A1 (en) * | 2009-11-04 | 2010-12-29 | 中兴通讯股份有限公司 | Method and apparatus for implementing service system protection |
CN102831038A (en) * | 2011-06-17 | 2012-12-19 | 中兴通讯股份有限公司 | Disaster tolerance method for ENUM-DNS (Telephone Number Mapping-Domain Name System) and ENUM-DNS |
WO2014032532A1 (en) * | 2012-09-03 | 2014-03-06 | 中兴通讯股份有限公司 | Enum-dns disaster recovery method and system in ims network |
CN104346373A (en) * | 2013-07-31 | 2015-02-11 | 华为技术有限公司 | Partition log queue synchronization management method and device |
CN104346373B (en) * | 2013-07-31 | 2017-12-15 | 华为技术有限公司 | Subregion journal queue synchronization management method and equipment |
WO2016070530A1 (en) * | 2014-11-04 | 2016-05-12 | 中兴通讯股份有限公司 | Method and system for processing operation of primary and standby device |
CN105634779A (en) * | 2014-11-04 | 2016-06-01 | 中兴通讯股份有限公司 | Operation processing method and apparatus of primary and secondary devices |
CN105634779B (en) * | 2014-11-04 | 2019-09-03 | 南京中兴软件有限责任公司 | The operation processing method and device of master/slave device |
CN104506353A (en) * | 2014-12-23 | 2015-04-08 | 北京奇虎科技有限公司 | Authentication management method, equipment and system |
CN106156086A (en) * | 2015-03-31 | 2016-11-23 | 西门子公司 | Hadoop platform system and host node log backup method thereof |
WO2016173179A1 (en) * | 2015-04-29 | 2016-11-03 | 中兴通讯股份有限公司 | Method and device for switching primary database and secondary database |
CN105338078A (en) * | 2015-10-26 | 2016-02-17 | 北京百度网讯科技有限公司 | Data storage method and device used for storing system |
CN105338078B (en) * | 2015-10-26 | 2019-01-01 | 北京百度网讯科技有限公司 | Date storage method and device for storage system |
CN106856489A (en) * | 2015-12-08 | 2017-06-16 | 阿里巴巴集团控股有限公司 | A kind of service node switching method and apparatus of distributed memory system |
CN105512343A (en) * | 2016-01-06 | 2016-04-20 | 北京京东尚科信息技术有限公司 | Method and device for simulating network anomaly and testing automatic switching of database faults |
CN106202261A (en) * | 2016-06-29 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | The distributed approach of a kind of data access request and engine |
CN106254100A (en) * | 2016-07-27 | 2016-12-21 | 腾讯科技(深圳)有限公司 | A kind of data disaster tolerance methods, devices and systems |
CN106254100B (en) * | 2016-07-27 | 2019-04-16 | 腾讯科技(深圳)有限公司 | A kind of data disaster tolerance methods, devices and systems |
US10713135B2 (en) | 2016-07-27 | 2020-07-14 | Tencent Technology (Shenzhen) Company Limited | Data disaster recovery method, device and system |
WO2018023994A1 (en) * | 2016-08-05 | 2018-02-08 | 华为技术有限公司 | Disaster-recovery switching method, node, and system |
US10834186B2 (en) | 2016-08-05 | 2020-11-10 | Huawei Technologies Co., Ltd. | Disaster recovery switchover method and system, and node |
CN107480014A (en) * | 2017-07-24 | 2017-12-15 | 北京奇安信科技有限公司 | A kind of High Availabitity equipment switching method and device |
CN110502460A (en) * | 2018-05-16 | 2019-11-26 | 华为技术有限公司 | The method and node of data processing |
CN110502460B (en) * | 2018-05-16 | 2021-03-23 | 华为技术有限公司 | Data processing method and node |
CN109101196A (en) * | 2018-08-14 | 2018-12-28 | 北京奇虎科技有限公司 | Host node switching method, device, electronic equipment and computer storage medium |
CN112990867A (en) * | 2021-03-11 | 2021-06-18 | 北京明略昭辉科技有限公司 | Method, system and equipment for realizing high availability of document platform service |
CN113609107A (en) * | 2021-09-30 | 2021-11-05 | 武汉四通信息服务有限公司 | Database management method and device, electronic equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
WO2010149117A1 (en) | 2010-12-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101729290A (en) | Method and device for realizing business system protection | |
CN106685818B (en) | Message feedback method and device | |
CN102439903B (en) | Method, device and system for realizing disaster-tolerant backup | |
CN101282276B (en) | Method and apparatus for protecting Ethernet tree service | |
CN100459601C (en) | Method for realizing active/standby gateway apparatus in network | |
CN106375342A (en) | Zookeeper-technology-based system cluster method and system | |
CN101431428B (en) | Security monitoring service recovery method and system | |
CN101304346B (en) | Method and apparatus for monitoring link | |
CN106330475A (en) | Method and device for managing main and standby nodes in communication system and high availability cluster | |
EP2482524A1 (en) | Address distribution method, device and system thereof | |
CN101729305A (en) | Method and system for automatically restoring fault, and control network element | |
CN101227333B (en) | Disaster tolerance network managing system and login method of network managing subscriber end | |
CN111371625A (en) | Method for realizing dual-computer hot standby | |
CN101197733A (en) | Automatic detection method and device for network connectivity | |
CN104506372A (en) | Method and system for realizing host-backup server switching | |
CN101145972B (en) | A disaster tolerance network management system and login method of network management clients | |
CN101729559A (en) | Method and system for realizing backup of DHCP server | |
CN101404594B (en) | Hot backup performance test method and apparatus, communication equipment | |
CN101651912B (en) | Data transmission method, device and system used in optical access network | |
CN111601299A (en) | Information association backfill system under 5G framework | |
CN110661651A (en) | SDN controller data management method, system, device and readable storage medium | |
CN102215272B (en) | Method and system for emergency switching | |
CN1855838B (en) | Interface inverting method | |
CN101453395A (en) | Switching method, system and device for uplink mode | |
CN111510336B (en) | Network equipment state management method and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C12 | Rejection of a patent application after its publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20100609 |