CN100563233C - Fault-tolerance method during a kind of Common Object Request Broker Architecture is used - Google Patents
Fault-tolerance method during a kind of Common Object Request Broker Architecture is used Download PDFInfo
- Publication number
- CN100563233C CN100563233C CNB2004100548775A CN200410054877A CN100563233C CN 100563233 C CN100563233 C CN 100563233C CN B2004100548775 A CNB2004100548775 A CN B2004100548775A CN 200410054877 A CN200410054877 A CN 200410054877A CN 100563233 C CN100563233 C CN 100563233C
- Authority
- CN
- China
- Prior art keywords
- server
- mentioned
- fault
- client
- request broker
- 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
Fault-tolerance method during a kind of Common Object Request Broker Architecture is used, use the heartbeat signal of one or more softwares periodic between a master server and one or more backup server to carry out fault detect and signalling trouble, simultaneously with the period of state of object in the above-mentioned master server copy in the above-mentioned backup server, switch to above-mentioned backup server by above-mentioned master server when breaking down, it is characterized in that: in above-mentioned master server and backup server, produce and have the identical interoperability object reference (IOR that is used for the addressing purpose, Interoperable Object Reference) object of parameter, above-mentioned object have identical communication end point to be described, identical object reference, identical thesaurus sign.The present invention compares with other CORBA fault-tolerance methods in the prior art, has weak point switching time, do not waste system resource, do not influence the advantage of client simultaneously, and do not need special software, and expense is low.
Description
(1) technical field
The present invention relates to the fault-tolerance method of application layer middleware in a kind of communications field, more particularly, is the fault-tolerance method during a kind of Common Object Request Broker Architecture is used, and is used for OO distributed system.
(2) background technology
In recent years, because the continuous expansion of the Internet network planning mould and computer is soft, the raising at full speed of hardware technology level has brought huge challenge for the implementation of traditional application software system.At first, in enterprise-level application, hardware system integrator is based on the consideration of aspects such as performance, price, service, usually integrated hardware device from different vendor, operating system, database platform and procotol etc. in same system, the isomerism that brings has thus brought serious problems for interoperability, compatibility and the smooth upgrade ability of application software.In addition, along with network-based service is on the increase, the Distributed Application mode of traditional client/server (C/S) pattern more and more demonstrates the limitation at aspects such as operational efficiency, processing complex transaction ability and system upgrade abilities.
In order to solve distributed computing environment (DCE) (DCE, Distributed Computing Environment) different hardware equipment and software systems is interconnected in, strengthen the interoperability of software between network, solve problems such as handling the complex transaction scarce capacity in the traditional distributed computation schema, (the OMG of OMG, Object Management Group) Common Object Request Broker Architecture (CORBA has been proposed, Common Object Request Broker Architecture), to strengthen the interoperability between software systems, make and construct flexibly that distribution application system becomes possibility.
CORBA has made full use of the developing Object-oriented Technique of software engineering now, realizes the integrated of application software under based on network distributed application environment, makes OO software distribute, realize under the isomerous environment reusable, portable and interoperability.More precisely, CORBA is a kind of middleware of OO distributed system.Here said middleware is a kind of independently systems soft ware or service routine, and Distributed Application software is shared resource between different technology by above-mentioned this systems soft ware or service routine.Middleware is positioned on the operating system of client-server, Management Calculation resource and network communication.The core of CORBA middleware is called Object Request Broker (ORB, Object Request Broker).By using ORB, the client can call one on the service object method and need not to know the fabric of client-server, this service object can be in this locality, also can be on the other machines that connects by network.ORB intercepts and captures this and calls to be responsible for simultaneously searching and realize service object and transmit parameter, call method, return final result to it.The client does not also know to provide the service object of service where to be positioned at, and what its programming language and operating system is, does not know object interface other system part in addition yet.Like this, ORB under the isomery distributional environment for the application on the different machines provides interoperability, and seamlessly integrated multiple objective system.After introducing ORB, propose service request to the service object, between distributed objects, set up client-service object's relation by ORB as long as the client follows service object's external interface standard.Fig. 1 has shown the customer service request schematic diagram.
As seen from Figure 1, the client sends request from the service object of client computer on server, and wherein the client is the entity of desire to the request of service object's sending method, and the service object comprises the data resource and the code of this method.In CORBA, the effect of the ORB of Object Request Broker just is to receive the service request that the client sends, the positioning service object, and service object's execution result returned to the client.
Because all computer systems all can be made mistakes, therefore to adopt the fault-tolerance method to solve the problem of makeing mistakes of computer system.Here said fault-tolerance is a system has the ability of opposing to mistakes that reason caused such as, memory overflow out of service by processor fault, network failure, operating system, software design mistakes.
Distributed system is made up of many elements, and these elements generally are striding courses and stride the main frame distribution.In these elements any one may break down at any time, so the CORBA system need adopt fault-tolerance approach equally, makes when certain element lost efficacy owing to fault in the system, and system can not lose efficacy as a whole.In the fault-tolerance method, back mechanism (or claiming redundancy scheme, replicanism) is the basis of various trouble saving mechanism, and the fault-tolerant standard of CORBA also is based upon on the basis of object backup just.Present CORBA standard (Fault Tolerant CORBA, Chapter 25 of Common Object Request BrokerArchitecture (CORBA), v2.5, September calendar year 2001) in to the support of fault-tolerance and not exclusively, therefore provide these fault-tolerances services task some just fall on the application designer head.OMG in the practical application (OMG) has adopted different fault-tolerance methods with different program designers.
First method is the Fault Tolerant CORBA method (Fault Tolerant CORBA, Chapter 25 of CommonObject Request Broker Architecture (CORBA), v2.5, September calendar year 2001) that OMG proposes, as shown in Figure 2.Fig. 2 represents how to occur under the unusual situation in a server S 1 or S2, the service that CORBA provides still can continue.This solution has been added a series of functional modules in Object Request Broker (ORB), for example how to carry out duplicating, how to find fault, how carrying out the notice of fault and how to switch etc. of object between server.Specifically, establishment object requests among the figure " establishment _ object () " (create_object ()) is transmitted to replication manager (Replication Manager) with the request of setting a property " setting _ attribute () " (set_properties ()), replication manager can be distributed to the establishment object requests that is provided with attribute among two server S 1 and the S2, produces two objects that lay respectively among S1, the S2 by their factory (factory 1, factory 2) separately again.These two object type is identical, attribute is identical, and therefore these two objects among described server S 1 and the S2 are backup mutually.Tracer (tracer 1, tracer 2) is housed on server S 1, S2, breaks down, failure message will be reported to signalling trouble device (Fault Notifier) if above-mentioned tracer detects the place server.In addition, on any platform in server S 1, S2 or be positioned on other servers beyond S1, the S2 a central tracer also is housed, when the tracer of S1, S2 can't detect the fault of self owing to reasons such as outages, this central authorities' tracer can detect the fault from server S 1, S2.After the fault that detects server S 1 or S2, also failure message is reported to above-mentioned signalling trouble device.The signalling trouble device can be notified above-mentioned replication manager, and replication manager can determine the service of this server that breaks down is switched on the another one server.The advantage of this method is that the backup between server can real-time fully carrying out, under the situation that a server breaks down, can switch to backup server by master server extremely apace, and it is, therefore little to the influence of client owing to do not need soft, the hardware of client are made amendment.Its shortcoming is on the backup server objects services on any one master server all to be kept backup, thereby makes that cost height, the resource utilization of this method are low.In addition, this method need join among the ORB above-mentioned carrying out object tools between server, find fault, carry out Trouble Report and functional module such as switching, ORB promptly common, standard can not realize above-mentioned functions, need buy the ORB that has particular module when buying ORB, so the buying expenses height.
Second method is for using fault-tolerance method (the The InterceptionApproach to Reliable Distributed CORBA Objects of multicast group communication (multicast group approach), written by P.Narasimhan, L.E.Moser, P.M.Melliar-Smith, Department of Electrical and Computer Engineering, Universityof California, Santa Barbara, CA 93106.The paper was originally published in theProceedings of the Third USENIX Conference on Object-Oriented Technologies andSystems Portland, Oregon, June 1997), above-mentioned multicast is more a kind of communication mode to multiple spot or multiple spot to multiple spot, and promptly a plurality of recipients receive the identical information of a source transmission simultaneously.The fault-tolerance method of employing multicast group communication as shown in Figure 3.Fig. 3 has shown from the request of the application of client through Object Request Broker (ORB) afterwards, form a clean culture (Unicast) message, this message is intercepted and captured by adapter object (Adaptor Objects), send on the two-server through platform (platform comprises operating system and hardware) in the mode of multicast again, wherein one be master server, another is backup server.That is to say that request is copied on the two-server, owing to asked on the server, will cause server to create corresponding service object, server backs up this service object again.The process that sends to after the two-server is similar with the method for above-mentioned first kind of OMG standard, and process such as switch after fault detect, Trouble Report and the discovery fault is arranged equally.The advantage of this method is under the situation that a server breaks down, and also can switch to backup server by master server extremely apace, equally to almost not influence of client.Its shortcoming is that server all backs up the object of asking each time to be created in the method, first kind of above-mentioned OMG method for normalizing then is that the object on the server has experienced several request back backups once, and therefore this multicast group communication method more expends system resource than first method.And this method also needs to buy the ORB that has particular module, buying expenses height.
The third fault-tolerance method is to utilize group of objects service (OGS, Object Group Service), (list of references is with the list of references of above-mentioned second method) as shown in Figure 4.OGS belongs to the part of CORBA among Fig. 4, and its position is positioned at the upper strata of ORB.When making in this way, server S 1 is at first created a group (Group1), quote (reference) above-mentioned group when this server provides service for client tells client, and server S 1 is created the service object and the service object who creates is joined among the group Group1 of above-mentioned establishment then.Server S 1 is told server S 2 with above-mentioned group quote, and promptly server S 2 is used quoting of identical group with server S1.Client uses dynamic call window (DII) to send the call request of client, and server end then uses dynamic framework interface (DSI) to transmit the call request of client.Will express with above-mentioned group quote in the time of the client call request, then can further determine this time to call at server end and cause which object carries out.When the request of client arrives server S 1, some objects of having in corresponding distribution mechanism, the assign group of server S 1 serve for this request.If client asks the required service that provides not change next time, server S 1 still can use the object in the above-mentioned group (Group1) to provide service as client; If client is provided by the required service change that provides next time, server S 1 will be according to as above creating another one group (Group2) in proper order and new service object being joined among the group Group2 of new establishment.Server S 1 periodically backups to the service object on the server S 2.When an object of server S 1 lost efficacy, will use the another one backup object that is positioned on the server S 2 to be this request service automatically.The advantage of this method is after the object on the master server lost efficacy, because quoting of group is constant, therefore can find the object on the server of backup to provide service for client at short notice, and promptly switch speed is fast, and little to the influence of client.Secondly, owing to this method can only back up stable calls, so the resource utilization height.Mainly utilize the OGS service of CORBA high level can cause the change of server-side application so shortcoming is this method, and owing to need to buy OGS software, buying expenses height.The 4th kind of method is to utilize the interception that ORB inside provides among the CORBA (Intercept) mechanism (Object Level FaultTolerance for CORBA-based Distributed Computing, Edited by Dan Tanner, Excerpted froma research report by the Semaphore staff).In the CORBA system, if client is visited an object, can issue ORB to access request, ORB passes to server end with request.Interception mechanism is equivalent to add last layer blocker (Interceptor) respectively at the client and server end, this blocker is directly provided by ORB, when each client sends a request or each server when receiving a request, interception (Intercept) program is triggered in the capital, its step as shown in Figure 5, at first there is a request (step 1) of thinking an object among the access server A (Server Host A) in client (Client Host); This request is sent to server A (step 2); If server A breaks down, can not finish the request of client, then the blocker of server A can return to the message (step 3) of the blocker one " can't serve " of client ORB; The blocker of client ORB can identify this message that " can't serve ", notice is positioned at copy services agency (Replica Service the Agent) (step 4) on the 3rd the server C (Server Host C); The copy services agency starts the recovery service mechanism, informs that the blocker server B (Server Host B) of client can provide service (step 5); Copy services agency while announcement server B is as master server (step 6); Client transmit a request to server B (step 7) then; Object handles on the server B is from the request (step 8) of client; The server B return results is given client (step 9).In the method, the backup procedure of object is arranged equally also, for example can the object on the server A periodically be copied on the server B by the copy services agency.The advantage of this method is only just to move above-mentioned hook procedure when server is made mistakes, just often make owing to not moving this hook procedure that the server expense is little, resource utilization is high at server, and all blocker can be housed on the general ORB software, need not to buy extra software module, so buying expenses is low.Its shortcoming is might search error reason from client, client and make switch speed slow owing to handoff request, and this method has the handling procedure that needs to write blocker on the basis of blocker in client, promptly need to transform client, big to the influence of client.
The 5th kind of method is the application layer fault-tolerance mechanism that provides in PARLAY.Here said Parlay is the open service technique of a kind of next generation network (NGN), the Parlay standard definition be the API (API) of control bottom-layer network resource.In the PARLAY method, all fault detects, back up, duplicate, switch all the CORBA service of in the application program on server end upper strata, finishing, do not relate to bottom.The fault-tolerance method of the application layer that provides among the PARLAY is provided Fig. 6, the figure illustrates the structure of a server end, and CORBA ORB is positioned on the platform among the figure, and the application program that contains application then is positioned at the upper strata of CORBA.Can two-server be arranged the notice client in the configuration of system, one of them is a master server, communicate by master server and client at first, this master server can be given the client sign (ID) that a server-side application distributes, client need be remembered this sign, under the situation that this master server lost efficacy, if client is found server end and was lost efficacy, will get in touch second server and inform original sign, second this sign of discovering server will use this sign to find corresponding object to provide service as client, and quoting of this object informed client, be convenient to client calls next time.This method also can only back up stable calling, so the resource utilization height, and need not to buy extra software and make expense low.Shortcoming be since this service relate to be outside CORBA more the change of the application layer program on upper strata time of make switching long, another problem is to safeguard that owing to client reason, client-side program such as its sign need change.
Above-mentioned CORBA fault-tolerance method respectively has pluses and minuses, and for example method in the OMG CORBA standard and multicast prescription formula are switched very fast but waste system resource; The group of objects method of service is switched soon, does not waste system resource, but can influence client and need to buy special software; Application mode among interception mode and the PARLAY is switched slowly, does not waste system resource, needn't buy special software, but will have influence on client yet.And we in use wish to use a kind of method, and this method not only switched soon, but also do not waste system resource, can not have influence on client simultaneously, also need not to buy special software.
(3) summary of the invention
The purpose of this invention is to provide the fault-tolerance method of a kind of Common Object Request Broker Architecture (CORBA) in using, this method can make when breaking down master server lack to the switching time of backup server; The resource utilization height of system, promptly object needn't all back up, and only stable calling is just backed up; Client does not make an amendment; Need not to buy special software simultaneously.
This invention is realized by following technical scheme: the fault-tolerance method during a kind of Common Object Request Broker Architecture is used, use one or more softwares between a master server and one or more backup server, to carry out fault detect and signalling trouble, simultaneously with the period of state of service object in the above-mentioned master server copy in the above-mentioned backup server, switch to above-mentioned backup server by above-mentioned master server when breaking down, it is characterized in that: generation is created by Common Object Request Broker Architecture in above-mentioned master server and backup server, object with identical interoperability object reference (IOR) parameter that is used for the addressing purpose, above-mentioned object have identical communication end point to be described, identical object reference, identical thesaurus sign.
According to an aspect of the present invention, above-mentioned communication end point is described and is comprised host IP address and predefined port numbers.
According to another aspect of the present invention, above-mentioned object key assignments comprises portable object adapter (POA) number and object identity (Object ID).
According to a further aspect of the invention, above-mentioned thesaurus sign is meant service object's type.
The present invention compares with other CORBA fault-tolerance methods in the prior art, has weak point switching time, do not waste system resource, do not influence the advantage of client simultaneously, and need not to install special software, so expense is low.
(4) description of drawings
To embodiments of the invention, advantage is further described below in conjunction with accompanying drawing, and these explanations are not restrictive.
Fig. 1 is for adopting the customer service request schematic diagram of the ORB of Object Request Broker;
Fig. 2 is the Fault Tolerant CORBA solution that OMG proposes in the prior art;
Fig. 3 is the fault-tolerance method of multicast in the prior art (multileaving) group communication method (multicast group approach);
Fig. 4 is for utilizing the fault-tolerance method of group of objects service (OGS, Object Group Service) in the prior art;
Interception (Intercept) the machine-processed fault-tolerance method of Fig. 5 for utilizing ORB inside to provide in the prior art;
The fault-tolerance method of the application layer that Fig. 6 provides for PARLAY in the prior art;
Fig. 7 is embodiments of the invention, comprises two steps, the situation when last figure is server S 1, S2 operate as normal; Figure below is the situation of server S 1 when making a mistake.Number designation among the figure is represented flow process.
(5) embodiment
Fig. 7 is embodiments of the invention, comprises two steps, the situation when last figure is server S 1, S2 operate as normal; Figure below is the situation of server S 1 when making a mistake.
At first, when server S 1 was created the service object, interoperability object reference at this object of above-mentioned server (Interoperable Object Reference) parameter can be created and return in the CORBA system.
After being provided with more than server S 1, S2 carried out, it seems that from client server S 1 has just had identical logic IP addresses with S2.But, have only that a server really has logic IP addresses, other server only has physical IP address at synchronization.
After two servers were created the service object, client sent request (step 71 among the row of the going up figure of Fig. 7), and the IP address in the interoperability object reference of this request (Interoperable Object Reference) is a logical ip.If this moment, server S 1 had this logical ip, this request just sends to (step 72 among the row of the going up figure of Fig. 7) above the server S 1 so.To server S 2 (step 73 among the row of the going up figure of Fig. 7), backup method can have multiple server S 1, for example backs up by same backup software is housed on server S 1, S2 relevant information back-up.
All moving " heartbeat " (heartbeat) program on server S 1 and the S2, monitor the other side's state by transmitting such as " I live (I ' m alive) " such periodic heartbeat signal, if server S 1 breaks down, can not continue to provide service, server S 2 just can not be received such information in the regular hour so, at this moment server S 2 can be taken over the IP (step 74 among the following row figure of Fig. 7) of server S 1, that is to say that S2 really has logic IP addresses.
In addition, can also come detecting server S1 state by the operational failure manager, this fault manager can be positioned on server S 1 or the server S 2, also can be positioned on the another one server S 3 outside S1, the S2.Fault manager periodically sends " heartbeat " message, the state of detecting server S1.If fault manager finds that server S 1 breaks down, also can determine to allow server S 2 take over the IP of server S 1, just S2 really has logic IP addresses.
The request of client can then arrive server S 2 (step 75 among the following row figure of Fig. 7).Serve (step 76 among the following row figure of Fig. 7) by server S 2 for the request of client.
If under the situation that server S 2 is not also taken over fully, client is just sent request, then can produce of short duration inefficacy, client can carry out retry, promptly send out once request again this moment, resend in the time of request, server S 2 can take over server S 1 fully.
Table 1 is switch speed after server lost efficacy of five kinds of fault-tolerance methods of the present invention and prior art, resource utilization, to the influence of client application, whether need the comparison of several respects such as special software, expense.
The performance of table 1 the present invention and other fault-tolerance methods relatively
As can be seen from Table 1, after technical scheme of the present invention, master server has identical logic IP addresses with backup server, thereby makes when master server breaks down, backup server quick-acting pipe master server soon, so switching time is short.Because the present invention only backs up the resource utilization ratio height to stable calling.The present invention does not simultaneously need soft, the hardware of client are changed, therefore to client without any influence, also need not to buy special software, so expense is low.
Claims (4)
1. the fault-tolerance method during a Common Object Request Broker Architecture is used comprises:
A) use one or more softwares between a master server and one or more backup server, to carry out fault detect and signalling trouble,
B) in above-mentioned master server and backup server, produce by Common Object Request Broker Architecture object that create, that have the identical interoperability object reference parameter that is used for the addressing purpose, above-mentioned object has identical communication end point description, identical object key assignments, identical thesaurus sign
C) simultaneously with the period of state of object in the above-mentioned master server copy in the above-mentioned backup server, and
D) when breaking down, switch to above-mentioned backup server by above-mentioned master server.
2. the fault-tolerance method during a kind of Common Object Request Broker Architecture according to claim 1 is used, above-mentioned communication end point are described and are comprised host IP address and predefined port numbers.
3. the fault-tolerance method during a kind of Common Object Request Broker Architecture according to claim 1 is used, above-mentioned object key assignments comprise portable object adapter number and object identity.
4. the fault-tolerance method during a kind of Common Object Request Broker Architecture according to claim 1 is used, above-mentioned thesaurus sign is meant service object's type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100548775A CN100563233C (en) | 2004-07-31 | 2004-07-31 | Fault-tolerance method during a kind of Common Object Request Broker Architecture is used |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100548775A CN100563233C (en) | 2004-07-31 | 2004-07-31 | Fault-tolerance method during a kind of Common Object Request Broker Architecture is used |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1728697A CN1728697A (en) | 2006-02-01 |
| CN100563233C true CN100563233C (en) | 2009-11-25 |
Family
ID=35927705
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100548775A Expired - Fee Related CN100563233C (en) | 2004-07-31 | 2004-07-31 | Fault-tolerance method during a kind of Common Object Request Broker Architecture is used |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100563233C (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101110776B (en) * | 2007-07-05 | 2011-06-01 | 华为技术有限公司 | Backup method, backup device and backup system for data business |
| CN101459690B (en) * | 2008-12-25 | 2012-05-09 | 哈尔滨工程大学 | Error tolerance method in wireless public object request proxy construction application |
| CN101655812B (en) * | 2009-09-15 | 2012-07-18 | 中兴通讯股份有限公司 | Self-adaptive data backup system and method thereof |
| CN105162856B (en) * | 2012-10-16 | 2019-03-01 | 北京奇虎科技有限公司 | Network application integrated system and method |
| CN104683140A (en) * | 2013-12-02 | 2015-06-03 | 中兴通讯股份有限公司 | Method and device for realizing northbound Coreba (Common Object Request Broker Architecture) interface specification seamless switching |
| CN108093207B (en) * | 2016-11-23 | 2021-03-16 | 杭州海康威视数字技术股份有限公司 | Data storage and acquisition method and device |
| CN106789257B (en) * | 2016-12-23 | 2019-03-05 | 中科星图股份有限公司 | A kind of cloud system server state visual management method |
-
2004
- 2004-07-31 CN CNB2004100548775A patent/CN100563233C/en not_active Expired - Fee Related
Non-Patent Citations (2)
| Title |
|---|
| 容错CORBA系统的设计与实现. 薛文革，李增智，王宇，陆建平.小型微型计算机系统，第23卷第10期. 2002 |
| 容错CORBA系统的设计与实现. 薛文革，李增智，王宇，陆建平.小型微型计算机系统，第23卷第10期. 2002 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1728697A (en) | 2006-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230273937A1 (en) | Conditional master election in distributed databases | |
| JP5102901B2 (en) | Method and system for maintaining data integrity between multiple data servers across a data center | |
| Felber et al. | Experiences, strategies, and challenges in building fault-tolerant CORBA systems | |
| CN102656565B (en) | Failover and recovery for replicated data instances | |
| CN102640108B (en) | The monitoring of replicated data | |
| CN112099918A (en) | Live migration of clusters in containerized environments | |
| US7451215B2 (en) | OPC server redirection manager | |
| JP4464525B2 (en) | Centralized affinity maintenance apparatus and method in a client / server data processing system managed by workload | |
| JP4637842B2 (en) | Fast application notification in clustered computing systems | |
| US7743036B2 (en) | High performance support for XA protocols in a clustered shared database | |
| CN100549960C (en) | The troop method and system of the quick application notification that changes in the computing system | |
| US10922303B1 (en) | Early detection of corrupt data partition exports | |
| CN110392884A (en) | The selfreparing Database Systems of automation and the method for realizing it | |
| US6493715B1 (en) | Delivery of configuration change in a group | |
| US7093163B2 (en) | Processing takeover method in multiple computer system | |
| CN100563233C (en) | Fault-tolerance method during a kind of Common Object Request Broker Architecture is used | |
| CN111800484A (en) | Service anti-destruction replacing method for mobile edge information service system | |
| US20070011328A1 (en) | System and method for application deployment service | |
| CN111158949A (en) | Configuration method, switching method and device of disaster recovery architecture, equipment and storage medium | |
| CN113766004A (en) | Disaster recovery system, method and storage medium based on multi-cloud platform | |
| CA2619778A1 (en) | Method and apparatus for sequencing transactions globally in a distributed database cluster with collision monitoring | |
| Montresor et al. | Enhancing Jini with group communication | |
| JP2001350777A (en) | Distributed database system | |
| CN100397349C (en) | Real composite objects for providing high availability of resources on networked systems | |
| Zhong et al. | A web-based design for the mobile transaction management of a distributed database system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: SIEMENS COMMUNICATION TECHNOLOGY ( BEIJING ) CO., Free format text: FORMER OWNER: SIEMENS (CHINA) AG Effective date: 20061229 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20061229 Address after: 100016 Building No. 14, Jiuxianqiao Road, Chaoyang District, Beijing, 51 Applicant after: Siemens Communication Networks Ltd., Beijing Address before: 100102 No. 7 South Central Road, Chaoyang District, Beijing, China Applicant before: SIEMENS (China) Co., Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20091125 Termination date: 20110731 |