CN105245361A - Data high availability system for Linux system, method and device - Google Patents
Data high availability system for Linux system, method and device Download PDFInfo
- Publication number
- CN105245361A CN105245361A CN201510573929.8A CN201510573929A CN105245361A CN 105245361 A CN105245361 A CN 105245361A CN 201510573929 A CN201510573929 A CN 201510573929A CN 105245361 A CN105245361 A CN 105245361A
- Authority
- CN
- China
- Prior art keywords
- middleware
- server node
- current use
- distributed file
- node
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Abstract
The embodiment of the invention provides a data high availability system for a Linux system, a method and a device. The system comprises a distributed file system, fault transfer equipment, at least two pieces of middleware and clients, wherein the distributed file system comprises at least two server nodes, and the server nodes are bound by a network card; one end of the fault transfer equipment is connected with all server nodes and the other end is connected with all pieces of middleware for monitoring whether fault happens to currently-used server nodes and currently-used middleware and switching failed server nodes and failed middleware; each piece of middleware is connected with all clients; and the clients perform data interaction with the server nodes in the distributed file system via the middleware and the fault transfer equipment. As the distributed file system and multiple pieces of middleware are adopted, as long as one normal server node and one normal piece of middleware exist, data interaction can be carried out, data high availability is ensured, and continuity of upper service can be further ensured.
Description
Technical field
The present invention relates to technical field of data transmission in linux system, particularly relate to a kind of data high-availability system, method and apparatus for linux system.
Background technology
At present, in minicomputer and other similar Linux system, client computer is carried out data interaction with memory device by single middleware and individual server node usually, when in data exchange process, when middleware and/or server node break down, this data exchange process cannot be proceeded, the high availability of data cannot be ensured, the continuity of upper-layer service cannot be ensured further.
Summary of the invention
In view of this, the embodiment of the present invention provides a kind of data high-availability system, method and apparatus for linux system, usually come to carry out data interaction with memory device by single middleware and individual server node to solve client computer in prior art, when in data exchange process, when middleware and/or server node break down, this data exchange process cannot be proceeded, the high availability of data cannot be ensured, the successional problem of upper-layer service cannot be ensured further.
For achieving the above object, the embodiment of the present invention provides following technical scheme:
For a data high-availability system for linux system, comprising: distributed file system, failover apparatus, at least 2 middlewares and client computer; Wherein,
Described distributed file system comprises at least 2 server nodes, adopts network card binding pattern between each described server node;
Described failover apparatus one end is connected with all described server nodes, the other end is connected with all described middlewares, for monitoring current use server node and whether current use middleware breaks down, when monitoring current use server node fault, in Servers-all node, select another server node as current use server node, when monitoring current use middleware fault, in all middlewares, select another middleware as current use middleware;
Each described middleware is all connected with all described client computer;
Described client computer carries out data interaction by described server node in described middleware and described failover apparatus and described distributed file system.
Wherein, described distributed file system also comprises memory device, and the equal carry of all described memory devices, on each described server node, realizes data interaction between described memory device and described server node.
Wherein, described memory device is by data interaction between optical fiber switch and described server node.
For a data high availability method for linux system, based on the above-mentioned data high-availability system for linux system, comprising:
Determine current use server node and current use middleware;
Monitor described current use server node whether to break down, if occur, then in Servers-all node, select another server node as current use server node;
Monitor described current use middleware whether to break down, if occur, in all middlewares, then select another middleware as current use middleware, ensure that client computer is mutual by use server node normal data current in current use middleware and failover apparatus and distributed file system.
Wherein, also comprise before determining current use server node and current use middleware:
Determine the catalogue of distributed file system carry;
Configure all middlewares, by all described middleware carries under described catalogue.
Wherein, also comprise before determining current use server node and current use middleware:
For Servers-all Joint Enterprise one public ip address;
For all described server node configuration floating IP address.
Wherein, in Servers-all node, select another server node as current use server node according to described floating IP address.
For a data high-availability device for linux system, comprising: determination module, the first monitoring modular and the second monitoring modular; Wherein,
Described determination module, for determining current use server node and current use middleware;
Whether described first monitoring modular, break down for monitoring described current use server node, if occur, then in Servers-all node, selects another server node as current use server node;
Described second monitoring modular, whether break down for monitoring described current use middleware, if occur, in all middlewares, then select another middleware as current use middleware, ensure that client computer is mutual by use server node normal data current in current use middleware and failover apparatus and distributed file system.
Wherein, the described data high-availability device for linux system also comprises: the first configuration module, for determining the catalogue of distributed file system carry, configures all middlewares, by all described middleware carries under described catalogue.
Wherein, the described data high-availability device for linux system also comprises: the second configuration module, for being Servers-all Joint Enterprise one public ip address, and is all described server node configuration floating IP address.
Based on technique scheme, the data high-availability system for linux system that the embodiment of the present invention provides, method and apparatus, wherein system is by distributed file system, failover apparatus, at least 2 middlewares and client computer composition, wherein, distributed file system comprises at least 2 server nodes, network card binding pattern is adopted between each server node, failover apparatus one end is connected with Servers-all node, the other end is connected with all middlewares, for monitoring current use server node and whether current use middleware breaks down, when monitoring current use server node fault, in Servers-all node, select another server node as current use server node, when monitoring current use middleware fault, in all middlewares, select another middleware as current use middleware, each middleware is all connected with all described client computer, client computer carries out data interaction by server node described in middleware and failover apparatus and distributed file system.Gather distributed file system, by data scatter in each server node, use multiple middleware simultaneously, when failover apparatus monitoring current using server node to break down time, another server node and client computer is used to proceed data interaction, when failover apparatus monitoring current using middleware to break down time, another middleware is used to make client computer and distributed point of office system proceed data interaction, as long as namely there is a normal server node and there is a normal middleware, client computer can continue to carry out data interaction with distributed file system, ensure that data high availability, further ensure the continuity of upper-layer service.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only embodiments of the invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to the accompanying drawing provided.
The system block diagram of the data high-availability system for linux system that Fig. 1 provides for the embodiment of the present invention;
The flow chart of the data high availability method for linux system that Fig. 2 provides for the embodiment of the present invention;
The method flow diagram for configuring middleware in the data high availability method of linux system that Fig. 3 provides for the embodiment of the present invention;
The method flow diagram for configuration server node in the data high availability method of linux system that Fig. 4 provides for the embodiment of the present invention;
The system block diagram of the data high-availability device for linux system that Fig. 5 provides for the embodiment of the present invention;
Another system block diagram of the data high-availability device for linux system that Fig. 6 provides for the embodiment of the present invention;
The another system block diagram of the data high-availability device for linux system that Fig. 7 provides for the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
The system block diagram of the data high-availability system for linux system that Fig. 1 provides for the embodiment of the present invention, gather distributed file system, by data scatter in each server node, use multiple middleware simultaneously, when failover apparatus monitoring current using server node to break down time, another server node and client computer is used to proceed data interaction, when failover apparatus monitoring current using middleware to break down time, another middleware is used to make client computer and distributed point of office system proceed data interaction, as long as namely there is a normal server node and there is a normal middleware, client computer can continue to carry out data interaction with distributed file system, ensure that data high availability, further ensure the continuity of upper-layer service, with reference to Fig. 1, this data high-availability system being used for linux system can comprise: distributed file system 10, failover apparatus 20, at least 2 middlewares 30 and client computer 40.Wherein,
Distributed file system 10 comprises at least 2 server nodes 11, network card binding pattern is adopted between each server node 11, namely the physical network card of each server node is bound into a Microsoft Loopback Adapter, to provide load balancing or redundancy, increase bandwidth, when the network interface card that breaks down arbitrary in Servers-all node 11 is unavailable, all can not has influence on other server nodes 11 and normally work.
Use distributed file system, except data high availability can be ensure that, further ensure outside the continuity of upper-layer service, compare local file system, without the need to when fault switches again, carry data disk again, also will be reduced in the time of Server switching when fault occurs greatly.
Optionally, distributed file system 10 can also comprise memory device 12, the equal carry of all memory devices 12 is on each server node 11, to realize data interaction between memory device 12 and server node 11, that is, each server node 11 all hangs over whole memory devices 12, ensure that in each server node 11, data are all identical, no matter to carry out data interaction all as broad as long for client computer 40 and which server node 11 in distributed file system 10.
Optionally, memory device 12 can by between optical fiber switch and server node 11 carry out data interaction.Optionally, the optical fiber switch of use can be FC optical fiber switch.
One end of failover apparatus 200 is connected with Servers-all node 11 in distributed file system 10, and the other end is connected with all middlewares 30.
When client computer and distributed point of office system carry out data interaction, example client computer 40 reads the data message in distributed point of office system 10, or client computer 40 when writing data message in distributed point of office system 10, current use server node (i.e. the current server node used in data exchange process) can be monitored and whether current use middleware (i.e. the current middleware used in data exchange process) breaks down by failover apparatus 200.
If failover apparatus 200 monitors current use server node fault, then in Servers-all node, select another server node except the server node of this fault, the server node this selected, as current use server node, proceeds data interaction with the current use server node after this replacement.
If failover apparatus 200 monitors current use middleware fault, then select in all middlewares except another middleware of middleware of this fault is as current use middleware, the middleware this selected, as current use middleware, proceeds data interaction with the current use middleware after this replacement.
Failover apparatus 200, except the failed equipment handoff functionality provided, also for upper-layer service provides unified interface IP address, reduces application complexity.
Each middleware 300 is all connected with All Clients 400, client computer 40 carries out data interaction by middleware 30 and failover apparatus 20 with distributed file system 10, concrete, client computer 40 carries out data interaction by a middleware 30 and a failover apparatus 20 with a server node 11 in distributed file system 10.
Optionally, in all middlewares 300, all can comprising same database, when including same database in all middlewares 300, the high availability of this database can be realized.
Optionally, can by middleware 300 and distributed file system 100 carry in same catalogue
Based on technique scheme, the data high-availability system for linux system that the embodiment of the present invention provides, by distributed file system, failover apparatus, at least 2 middlewares and client computer composition, wherein, distributed file system comprises at least 2 server nodes, network card binding pattern is adopted between each server node, failover apparatus one end is connected with Servers-all node, the other end is connected with all middlewares, for monitoring current use server node and whether current use middleware breaks down, when monitoring current use server node fault, in Servers-all node, select another server node as current use server node, when monitoring current use middleware fault, in all middlewares, select another middleware as current use middleware, each middleware is all connected with all described client computer, client computer carries out data interaction by server node described in middleware and failover apparatus and distributed file system.Gather distributed file system, by data scatter in each server node, use multiple middleware simultaneously, when failover apparatus monitoring current using server node to break down time, another server node and client computer is used to proceed data interaction, when failover apparatus monitoring current using middleware to break down time, another middleware is used to make client computer and distributed point of office system proceed data interaction, as long as namely there is a normal server node and there is a normal middleware, client computer can continue to carry out data interaction with distributed file system, ensure that data high availability, further ensure the continuity of upper-layer service.
Be introduced the data high availability method for linux system that the embodiment of the present invention provides below, the data high availability method for linux system described below is based on the above-described data high-availability system for linux system.
The flow chart of the data high availability method for linux system that Fig. 2 provides for the embodiment of the present invention, with reference to Fig. 2, this data high availability method being used for linux system can comprise:
Step S100: determine current use server node and current use middleware;
Current use server node, when referring to that the server node of client computer and distributed point of office system carries out data interaction by middleware and failover apparatus, the current server node used.
Current use middleware, when referring to that client computer and distributed point of office system carry out data interaction by middleware and failover apparatus, the current middleware used.
Optionally, before determining current use server node and current use middleware, the catalogue of distributed file system carry can also be determined, all middlewares are configured, by equal for all middlewares carry under this catalogue, by middleware and distributed file system carry in same catalogue.
Optionally, before determining current use server node and current use middleware, it can also be first Servers-all Joint Enterprise one public ip address, and be Servers-all Joint Enterprise one floating IP address, when monitoring current use server node and breaking down, another server node can be selected in Servers-all node as current use server node according to this floating IP address.
Step S110: monitor described current use server node and whether break down, if occur, then selects another server node as current use server node in Servers-all node;
After determining current use server node, the current use server node determined this can be carried out Real-Time Monitoring, when monitoring this current use server node and breaking down, another server node except the server node of this fault will be selected immediately in Servers-all node, the server node this selected, as current use server node, proceeds data interaction with the current use server node after this replacement.
If monitor this another server node selected also to break down, then will continue in Servers-all node, select another server node except the server node of known fault as current use middleware, another server node this selected, as current use server node, proceeds data interaction.
By that analogy, as long as the current use server node server node that is fault always, then the server node of this fault is replaced, until current use server node is normal server node.
Step S120: monitor described current use middleware and whether break down, if occur, then selects another middleware as current use middleware in all middlewares.
After determining current use middleware, the current use middleware determined this is carried out Real-Time Monitoring by failover apparatus, when monitoring this current use middleware and breaking down, will select except another middleware of middleware of this fault is as current use middleware immediately in all middlewares, the middleware this selected, as current use middleware, proceeds data interaction with the current use middleware after this replacement.
Same, if monitor this another middleware selected also to break down, then failover apparatus will continue in all middlewares, select another middleware except the middleware of known fault as current use middleware, another middleware this selected, as current use middleware, proceeds data interaction.
By that analogy, as long as the current use middleware middleware that is fault always, then the middleware of this fault is replaced, until current use middleware is normal middleware.
Wherein, between step S210 and step S220, there is no logical order relation, can first perform step S210 and perform step S220 again, can first perform step S220 yet and perform step S210 again, under the prerequisite of conditions permit, also can perform step S210 and step S220 simultaneously.
By step S200, step S210 and step S220, can ensure that current use server node is normal server node at any time, and current use middleware is normal middleware, ensure that client computer carries out normal data by current use server node in current use middleware and failover apparatus and distributed file system mutual.
Optionally, Fig. 3 shows the method flow diagram for configuring middleware in the data high availability method of linux system that the embodiment of the present invention provides, and with reference to Fig. 3, the method for this configuration middleware can comprise:
S200: the catalogue determining distributed file system carry;
If by all middlewares and distributed file system carry under same catalogue, then the catalogue first determining distributed file system carry need be needed.
S210: configure all middlewares, by all described middleware carries under described catalogue.
After the catalogue determining distributed file system carry, then can be configured all middlewares, under just all middlewares are deployed in the catalogue of distributed file system carry.
Optionally, Fig. 4 shows the method flow diagram for configuration server node in the data high availability method of linux system that the embodiment of the present invention provides, and with reference to Fig. 4, the method for this configuration server node can comprise:
S300: be Servers-all Joint Enterprise one public ip address;
S310: be all described server node configuration floating IP address.
Optionally, another server node can be selected in Servers-all node as current use server node by the floating IP address of this setting.
When current use server node is for server node 1, this floating IP address points to this server node 1, when this server node 1 breaks down, this floating IP address will automatically switch to another station server node, on such as server node 2, this floating IP address points to this server node 2, and this server node 2 will as current use server node.
Optionally, when middleware use proxy server and server node carry out communication data mutual time, the IP address of the proxy server of middleware can be set to this floating IP address, why, current use middleware all normally can carry out data interaction with this current use server node to make no matter current use server node.
The data high availability method for linux system that the embodiment of the present invention provides, when monitor current using server node to break down time, another server node and client computer is used to proceed data interaction, when failover apparatus monitoring current using middleware to break down time, another middleware is used to make client computer and distributed point of office system proceed data interaction, as long as there is a normal server node and there is a normal middleware, client computer can continue to carry out data interaction with distributed file system, ensure that data high availability, further ensure the continuity of upper-layer service.
Be introduced the data high-availability device for linux system that the embodiment of the present invention provides below, the data high-availability device for linux system described below can mutual corresponding reference with the above-described data high availability method for linux system.
The system block diagram of the data high-availability device for linux system that Fig. 5 provides for the embodiment of the present invention, with reference to Fig. 5, this data high-availability device being used for linux system can comprise: determination module 100, first monitoring modular 200 and the second monitoring modular 300.Wherein,
Determination module 100, for determining current use server node and current use middleware;
Whether the first monitoring modular 200, break down for monitoring described current use server node, if occur, then in Servers-all node, selects another server node as current use server node;
Second monitoring modular 300, whether break down for monitoring described current use middleware, if occur, in all middlewares, then select another middleware as current use middleware, ensure that client computer is mutual by use server node normal data current in current use middleware and failover apparatus and distributed file system.
Optionally, Fig. 6 shows another system block diagram of the data high-availability device for linux system that the embodiment of the present invention provides, and with reference to Fig. 6, this data high-availability device being used for linux system can also comprise: the first configuration module 400.
First configuration module 400, for determining the catalogue of distributed file system carry, configures all middlewares, by all described middleware carries under described catalogue.
Optionally, Fig. 7 shows the another system block diagram of the data high-availability device for linux system that the embodiment of the present invention provides, and with reference to Fig. 7, this data high-availability device being used for linux system can also comprise: the second configuration module 500.
Second configuration module 500 for being Servers-all Joint Enterprise one public ip address, and is all described server node configuration floating IP address.
The data high-availability device for linux system that the embodiment of the present invention provides, when monitor current using server node to break down time, another server node and client computer is used to proceed data interaction, when failover apparatus monitoring current using middleware to break down time, another middleware is used to make client computer and distributed point of office system proceed data interaction, as long as there is a normal server node and there is a normal middleware, client computer can continue to carry out data interaction with distributed file system, ensure that data high availability, further ensure the continuity of upper-layer service.
In this specification, each embodiment adopts the mode of going forward one by one to describe, and what each embodiment stressed is the difference with other embodiments, between each embodiment identical similar portion mutually see.For device disclosed in embodiment, because it corresponds to the method disclosed in Example, so description is fairly simple, relevant part illustrates see method part.
To the above-mentioned explanation of the disclosed embodiments, professional and technical personnel in the field are realized or uses the present invention.To be apparent for those skilled in the art to the multiple amendment of these embodiments, General Principle as defined herein can without departing from the spirit or scope of the present invention, realize in other embodiments.Therefore, the present invention can not be restricted to these embodiments shown in this article, but will meet the widest scope consistent with principle disclosed herein and features of novelty.
Claims (10)
1. for a data high-availability system for linux system, it is characterized in that, comprising: distributed file system, failover apparatus, at least 2 middlewares and client computer; Wherein,
Described distributed file system comprises at least 2 server nodes, adopts network card binding pattern between each described server node;
Described failover apparatus one end is connected with all described server nodes, the other end is connected with all described middlewares, for monitoring current use server node and whether current use middleware breaks down, when monitoring current use server node fault, in Servers-all node, select another server node as current use server node, when monitoring current use middleware fault, in all middlewares, select another middleware as current use middleware;
Each described middleware is all connected with all described client computer;
Described client computer carries out data interaction by described server node in described middleware and described failover apparatus and described distributed file system.
2. the data high-availability system for linux system according to claim 1, it is characterized in that, described distributed file system also comprises memory device, the equal carry of all described memory devices, on each described server node, realizes data interaction between described memory device and described server node.
3. the data high-availability system for linux system according to claim 2, it is characterized in that, described memory device is by data interaction between optical fiber switch and described server node.
4. for a data high availability method for linux system, it is characterized in that, based on the data high-availability system for linux system according to claim 1, comprising:
Determine current use server node and current use middleware;
Monitor described current use server node whether to break down, if occur, then in Servers-all node, select another server node as current use server node;
Monitor described current use middleware whether to break down, if occur, in all middlewares, then select another middleware as current use middleware, ensure that client computer is mutual by use server node normal data current in current use middleware and failover apparatus and distributed file system.
5. the data high availability method for linux system according to claim 4, is characterized in that, also comprises before determining current use server node and current use middleware:
Determine the catalogue of distributed file system carry;
Configure all middlewares, by all described middleware carries under described catalogue.
6. the data high availability method for linux system according to claim 4, is characterized in that, also comprises before determining current use server node and current use middleware:
For Servers-all Joint Enterprise one public ip address;
For all described server node configuration floating IP address.
7. the data high availability method for linux system according to claim 6, is characterized in that, selects another server node as current use server node according to described floating IP address in Servers-all node.
8. for a data high-availability device for linux system, it is characterized in that, comprising: determination module, the first monitoring modular and the second monitoring modular; Wherein,
Described determination module, for determining current use server node and current use middleware;
Whether described first monitoring modular, break down for monitoring described current use server node, if occur, then in Servers-all node, selects another server node as current use server node;
Described second monitoring modular, whether break down for monitoring described current use middleware, if occur, in all middlewares, then select another middleware as current use middleware, ensure that client computer is mutual by use server node normal data current in current use middleware and failover apparatus and distributed file system.
9. the data high-availability device for linux system according to claim 8, it is characterized in that, also comprise: the first configuration module, for determining the catalogue of distributed file system carry, configure all middlewares, by all described middleware carries under described catalogue.
10. the data high-availability device for linux system according to claim 8, is characterized in that, also comprise: the second configuration module, for being Servers-all Joint Enterprise one public ip address, and is all described server node configuration floating IP address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510573929.8A CN105245361A (en) | 2015-09-10 | 2015-09-10 | Data high availability system for Linux system, method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510573929.8A CN105245361A (en) | 2015-09-10 | 2015-09-10 | Data high availability system for Linux system, method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105245361A true CN105245361A (en) | 2016-01-13 |
Family
ID=55042872
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510573929.8A Pending CN105245361A (en) | 2015-09-10 | 2015-09-10 | Data high availability system for Linux system, method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105245361A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106897175A (en) * | 2017-02-19 | 2017-06-27 | 郑州云海信息技术有限公司 | Heat replaces the method and device of NC nodes |
| CN107592215A (en) * | 2017-08-31 | 2018-01-16 | 郑州云海信息技术有限公司 | A kind of method for managing message-oriented middleware |
| CN108170545A (en) * | 2018-01-08 | 2018-06-15 | 北京奇艺世纪科技有限公司 | A kind of method for message transmission and device based on message-oriented middleware |
| CN108650297A (en) * | 2018-04-09 | 2018-10-12 | 天津中兴智联科技有限公司 | A kind of realization method and system of Internet of things middleware high availability |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070106745A1 (en) * | 2003-09-30 | 2007-05-10 | Sony Corporation | Content acquisition method |
| CN101217558A (en) * | 2007-12-26 | 2008-07-09 | 中国移动通信集团湖北有限公司 | An operation middleware service load balancing method |
| CN102655460A (en) * | 2012-01-05 | 2012-09-05 | 中国工商银行股份有限公司 | Redundancy backup method and system of production server |
| US20130056258A1 (en) * | 2010-05-14 | 2013-03-07 | 3M Innovative Properties Company | Electromagnetic shielding adhesive tape |
-
2015
- 2015-09-10 CN CN201510573929.8A patent/CN105245361A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070106745A1 (en) * | 2003-09-30 | 2007-05-10 | Sony Corporation | Content acquisition method |
| CN101217558A (en) * | 2007-12-26 | 2008-07-09 | 中国移动通信集团湖北有限公司 | An operation middleware service load balancing method |
| US20130056258A1 (en) * | 2010-05-14 | 2013-03-07 | 3M Innovative Properties Company | Electromagnetic shielding adhesive tape |
| CN102655460A (en) * | 2012-01-05 | 2012-09-05 | 中国工商银行股份有限公司 | Redundancy backup method and system of production server |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106897175A (en) * | 2017-02-19 | 2017-06-27 | 郑州云海信息技术有限公司 | Heat replaces the method and device of NC nodes |
| CN107592215A (en) * | 2017-08-31 | 2018-01-16 | 郑州云海信息技术有限公司 | A kind of method for managing message-oriented middleware |
| CN108170545A (en) * | 2018-01-08 | 2018-06-15 | 北京奇艺世纪科技有限公司 | A kind of method for message transmission and device based on message-oriented middleware |
| CN108650297A (en) * | 2018-04-09 | 2018-10-12 | 天津中兴智联科技有限公司 | A kind of realization method and system of Internet of things middleware high availability |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6112249A (en) | Non-disruptively rerouting network communications from a secondary network path to a primary path | |
| CN108965123B (en) | Link switching method and network communication system | |
| EP3016316B1 (en) | Network control method and apparatus | |
| CN109743370B (en) | SD-WAN-based hybrid cloud connection method and system | |
| US10027574B2 (en) | Redundant pathways for network elements | |
| JP2005521334A (en) | Network management system | |
| WO2015101168A1 (en) | Failure recovery method and controller | |
| CN104486128B (en) | A kind of system and method for realizing redundancy heartbeat between dual controller node | |
| EP2732598B1 (en) | Method to enhance high availability in a secure telecommunications network, and telecommunications network comprising a plurality of remote nodes | |
| CN105245361A (en) | Data high availability system for Linux system, method and device | |
| CN104038376A (en) | Method and device for managing real servers and LVS clustering system | |
| CN110324375B (en) | Information backup method and related equipment | |
| US20140219080A1 (en) | Method and apparatus for interworking protection switching | |
| CN101145972B (en) | A disaster tolerance network management system and login method of network management clients | |
| EP3618350A1 (en) | Protection switching method, device and system | |
| CN108667640B (en) | Communication method and device, and network access system | |
| CN106664247B (en) | Communication device, communication system, and communication method | |
| KR20180122513A (en) | Method and framework for traffic engineering in network hypervisor of sdn-based network virtualization platform | |
| CN109104319B (en) | Data storage device and method | |
| CN106534758B (en) | Conference backup method and device | |
| US10673717B1 (en) | Monitoring networked devices | |
| EP2953299B1 (en) | Protection switching method, system and node | |
| CN106130783B (en) | Port fault processing method and device | |
| CN114422335A (en) | Communication method, communication device, server and storage medium | |
| CN114615190A (en) | Rerouting method, communication device, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160113 |