CN101212458A - Database system backup method - Google Patents
Database system backup method Download PDFInfo
- Publication number
- CN101212458A CN101212458A CNA200610161788XA CN200610161788A CN101212458A CN 101212458 A CN101212458 A CN 101212458A CN A200610161788X A CNA200610161788X A CN A200610161788XA CN 200610161788 A CN200610161788 A CN 200610161788A CN 101212458 A CN101212458 A CN 101212458A
- Authority
- CN
- China
- Prior art keywords
- database
- network
- agency
- guest machine
- main computer
- 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.)
- Withdrawn
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a method for backuping a database system, which includes the following steps: originally identical databases are conserved in a plurality of network nodes; the network is connected to a business processing system through a gateway/ a router; the various network nodes execute operation to the identical database of various database embodiments so as to finish data backup through intercepting the database broadcast on network and synchronously operating the database. The method uses Ethernet broadcasting to backup data on multiple nodes, further uses information to confirm mechanism and switch a timer so as to carry out active/standby switching in the database system, thereby finishing the active/standby switching within a definite database operational period with a simple system, in particular to solve business paralysis caused by intermittent disconnection of the database system and program interruption in HLR network elements of mobile communications, thus as much as possible reducing the instability of the system owing to exception of database.
Description
Technical field
The present invention relates to database technology, be specifically related to a kind of database system backup method.
Background technology
The superfluous calamity of the Database Systems of broad sense refers to the loss of data that force majeure such as reducing nature, war causes; The superfluous calamity of the Database Systems of narrow sense, the Database Systems paralysis that bring comprise because the impact that misoperation, hardware damage, peak traffic, outage etc. cause Database Systems etc., this exists under the situation of BUG in Database Systems, more common, this situation is more frequent, and the normal operation of business has been brought immeasurable loss.Whether interrupt by business, be divided into superfluous calamity of data level and the superfluous calamity of application layer again 1..The application layer system that refers to finishes calamity automatically and is equipped with switching, and maximum reduces switching time, makes to use continual operation; The superfluous calamity of data is then inevitably understood interrupting service, data return to Database Systems during this period of time in, Database Systems are inoperable, modal is exactly that the backup that provides of most commercial relational databases recovers, before recovering, database is disabled.
Superfluous calamity Database Systems generally partly constitute by two, and the one, Database Systems are switched, and the 2nd, data are duplicated.The application layer calamity of IBM is equipped with the main High AvailabilityGeographical Cluster/High Availability Cluster Multi-Processing that adopts based on the AIX platform, be called for short the HAGEO/HACMP scheme or based on the Geographically Dispersed ParallelSysplex of S/390, be called for short the GDPS scheme, and the scheme of data level adopts Peer ToPeer Remote Copy or Extend Remote Copy based on disk system, is called for short PPRC or XRC functional software 2..System's switchover policy of Veritas then can be by customization, and at Global Cluster Manager/Veritas Cluster Server, be called for short in the GCM/VCS software and realize that data are duplicated and then adopted VolumeReplicator, be called for short VVR 3. logical volume is copied on a plurality of backup nodes.Data are duplicated, in general can on hardware or software layer, realize, as, disk hardware store level, file system level, operating system grade, database level, SNA network level etc.
Present superfluous calamity scheme still is at the superfluous calamity of data level mostly, for example, the PPRC/XRC functional software of IBM, it is to pass through optical-fibre channel, with the logical volume is unit, the local data synchronous mirror to far-end, can be had synchronously and asynchronous system, and difference is whether main frame is received that standby host is write to finish and just confirmed that data write success behind the signal.
Actually rare at the superfluous calamity of the continual application layer of business, ripe product, (rule of HACMP is equally applicable to HAGEO as the HAGEO/HACMP of IBM, 4. the distance that both support is distinguished to some extent) Clustering, its data copy mode has three kinds: synchronously, mirror image is synchronously with asynchronous, synchronizing process is a linear process substantially, writes far-end earlier and writes this locality again, waits active and standby writing to be over, just declaration is write and is finished, mirror image has adopted the equipment of a state diagram synchronously, writes state diagram earlier, again the handwritten copy domain, this locality has been write and has promptly been declared to write to finish, be responsible for far-end by the backstage and write, in full accord up to far-end and local data, asynchronous mode be allow active and standby between certain data difference, it is synchronous to be converted to mirror image after reaching difference value, to improve performance.
The HAGEO/HACMP handoff procedure is to utilize lan to come the state of monitoring host computer, network and network interface card, this environment is made of two cover networks, the one, the public network of client-access, it is the TCP/IP network, the one, the communication path of alternative TCP/IP can be a RS232 serial ports etc., promptly non-TCP/IP network, it is actually ' heartbeat ' line, is used for monitoring three default class faults specially: network interface card fault, network failure, node failure.In a single day main-standby nodes adds this cluster, each network interface card of node, non-TCP/IP network can constantly send and receive K_A (Keep_Alive) signal, if TCP/IP network that standby host receives and the K_A signal on the non-TCP/IP network are all lost, HACMP can predicate node failure so; If K_A dropout on the TCP/IP network that standby host receives, and the K_A signal on the TCP/IP network exists, HACMP can predicate network failure so; If the K_A signal of a certain network interface card is all lost, then HACMP can predicate the network interface card fault, under the default situations, HACMP only judges this three kinds of situations, some mechanism that other fault can provide in conjunction with AIX basic function and HACMP, as Error Notification Facility, clinfo API etc. monitor and take recovery measures such as switching to fault.
ORACLE Data Guard then provides a disaster recovery solution on the database level, it is that redo daily record with main frame copies on the standby host, recover daily record simultaneously, to reach active and standby machine data unanimity, but having an accident, certain node needs active and standby switching, still need artificial participation, ORACLE RAC allows the backup of N node, but still link between the node by exchanged form, switching still needs the clustermanager module to carry out heartbeat monitor 5., rather than utilizes the information that produces in the business procedure to judge.
Summary of the invention
The technical issues that need to address of the present invention provide a kind of DB Backup method, can utilize business information to back up.
Above-mentioned technical problem of the present invention solves like this, and a kind of DB Backup method is provided, and uses the database manipulation packet to back up at a plurality of network nodes, may further comprise the steps:
1.1) with independent preservation the in original identical a plurality of network nodes of database in the Database Systems local area network (LAN);
1.2) this local area network (LAN) is connected with the transaction processing system that sends the database manipulation packet by gateway/router;
1.3) each network node carries out the same database operation by intercept the database manipulation packet of broadcasting simultaneously in the Database Systems local area network (LAN) to database instance separately.
According to backup method provided by the invention, described database manipulation is read operation, described step 1.3) in only the network node business datum of returning read operation show to the transaction processing system that sends the database manipulation packet.
According to backup method provided by the invention, described database manipulation is a write operation; Described step 1.3) in only a network node return the success of write operation/failure and indicate and give the transaction processing system that sends the database manipulation packet.
According to backup method provided by the invention, a described network node is a main computer, and other network nodes are guest machine.
According to backup method provided by the invention, described guest machine is one or more.
According to backup method provided by the invention, described Database Systems are made of described network node, and described Database Systems local area network (LAN) is is only connected and composed by described network node and network.
According to backup method provided by the invention, it is bus mode that described network connects.
According to backup method provided by the invention, the network interface card of described network node is made as the Promiscuous pattern.
Database system backup method provided by the invention, utilize Ethernet broadcasting characteristics to carry out data backup at multiple network node, further utilize message authentication mechanism and switch timer and carry out the active and standby machine switching of Database Systems, the Database Systems simple structure, and can in the time in an established data operation cycle, finish active and standby switching, reach the effect of the real-time Hot Spare of multimachine, can solve especially in the mobile communication HLR network element, the business paralysis that Database Systems usually cause because hit or some program interrupts etc. are unusual reduces as far as possible because the systematic jitters that database brings unusually.
Description of drawings
Further the present invention is described in detail below in conjunction with the drawings and specific embodiments.
Fig. 1 is the system configuration schematic diagram that redundancy backup of the present invention and changing method are realized.
Fig. 2 is a data back up method logic flow schematic diagram of the present invention.
Fig. 3 is a main/standby switching method logic flow schematic diagram of the present invention.
Embodiment
At first, key of the present invention is described: in the read/write data operating process, the characteristics of utilizing packet to broadcast in Ethernet are carried out Backup Data, and the out-of-service time of Database Systems is limited in the definite time range by mechanism such as switching timer.
Second step illustrated that the present invention used the universe network environment, specifically as shown in Figure 1, comprised 1. Business Processing (application) system 40, and 2. router five 0 and the database local net system 30 that 3. is made up of main computer 10 and guest machine 20 are specific as follows:
1. Business Processing (application) system 40, its produces the read/write operation to Database Systems;
2. router five 0, between transaction processing system and database local net system, also can be switch or HUB hub;
3. database local net system 30, it is " sharing formula " local area network (LAN) that constitutes backstage entire database system, its essence is that a carrier wave detects the shared channel that multichannel is intercepted machine-processed control transmission, link to each other with bus mode by switch, HUB hub or router five 0 between main computer 10 and the guest machine 20, the Various types of data that transaction processing system 40 produces wraps in this channel with the broadcast mode transmission, for the data backup of guest machine 20 provides physical environment;
Database local net system 30 is made up of main computer 10 and guest machine 20, guest machine 20 can be one or more, here only listed a guest machine 20, the network interface card of main computer 10 and guest machine 20 is set to " mixing " Promiscuous pattern, receives the packet on the shared channel local area network (LAN);
By 60 communications of inter-agent communication network, communication network 60 can be that TCP/IP can be RS235 also between main computer agency 101 and guest machine agency 201 and a plurality of guest machine agency 201, between the agency by message authentication in order to active and standby switching.
Wherein, adopt the TCP/IP network to connect between transaction processing system 40 and the database local net system 30 that forms by main computer 10 and guest machine 20; Respectively have an agent process 101 and 201 to be responsible on main computer 10 and the guest machine 20: 1) processing data packets 2) the IP address replaces 3) initiate active and standby switching; Carry out communication by adopting TCP/IP or serial ports RS235 to link between main computer and the guest machine between agency on the main computer and the agency on the guest machine; The guest machine people is for being defined as first guest machine, second guest machine etc.; Active/standby identical with the machine software and hardware configuration.
In the 3rd step, further specify the read-write operation of database local net of the present invention system:
(1) read data operation may further comprise the steps:
1. in the transaction processing system, read data operation (SQL statement character string) after network/transmission/link layer packing, enters the switch buffer memory in the TCP/IP network;
2. switch sends read data operating data bag to the active/standby machine of using by broadcast mode, and the agency on the main computer receives read data operating data bag, and the agency on the guest machine also receives read data operating data bag;
3. active/standby accept read data operating data bag with the agency on the machine after, the switching timer on main computer and the guest machine picks up counting simultaneously;
4. after the database instance on the main computer is handled SQL statement character string in the packet, return to the agency's two class data on the main computer: business datum, success/failure sign (comprises hardware, work as machine, overtime, the SQL grammer, can not find out faults such as data, further sorting processing by the agency differentiates then), processing procedure is the same with main computer on the guest machine, also returns this two classes data, if the guest machine frequency of failure reaches certain number of times, then first guest machine is substituted by former second guest machine, and the like, and alarm;
5. the agency on the main computer returns to transaction processing system with the business datum packing by the TCP/IP network, agency on the guest machine then will be separately the data returned of database all shield (all interceptions, not to transaction processing system return data bag), success/failure sign is returned to agency on the main computer by another set of network, and the agency on the main computer beams back response message to each guest machine then;
6. if the agency on the main computer monitors the database instance failure on the main frame, perhaps the switching timer on the main computer is overtime, and received the successful sign that the agency on first guest machine returns, then initiate to switch by master agent, take over main frame by first guest machine, agency on this guest machine at first initiates to replace main computer IP operation, then the business datum packing is returned to transaction processing system by switch network.This is that agency on the main computer is normal, in the time in a read data operation cycle, is initiated the situation of active and standby switching by the agency on the main computer;
7. if in the 5th step, before the switching timer expired that the agency on the guest machine started in the 4th step arrives, do not receive the response message of the agency on the main computer yet, then initiate active and standby switching by the agency on first guest machine;
8. if first guest machine is initiated active and standby handoff failure, then then initiate active and standby switching by second guest machine, all fail up to guest machine;
(2) data writing operation may further comprise the steps:
1. in the transaction processing system, data writing operation (SQL statement character string) after network/transmission/link layer packing, enters the switch buffer memory in the TCP/IP network;
2. switch sends read data operating data bag to the active/standby machine of using by broadcast mode, and the agency on the main computer receives the data writing operation packet, and the agency on the guest machine also receives the data writing operation packet;
3. active/standby accept the data writing operation packet with the agency on the machine after, the switching timer on main computer and the guest machine picks up counting;
4. after the database instance on the main computer is handled SQL statement character string in the packet, return to the agency's class data only on the main computer: success/failure sign (comprises hardware, work as machine, overtime, the SQL grammer, can not find out faults such as data, further sorting processing by the agency differentiates then), processing procedure is the same with main computer on the guest machine, also return this class data, if the guest machine frequency of failure reaches certain number of times, then first guest machine is substituted by former second guest machine, and the like, and alarm;
5. the agency on the main computer returns to transaction processing system with success/failure sign by the TCP/IP network, guest machine returns to agency on the main computer with success/failure sign by another set of network, and the agency on the main computer beams back response message to each guest machine then;
6. if the agency on the main computer monitors the database instance failure on the main frame, perhaps the switching timer on the main computer is overtime, and received the successful sign that the agency on first guest machine returns, then initiate to switch by master agent, take over main frame by first guest machine, agency on this guest machine at first initiates to replace main computer IP operation, then the business datum packing is returned to transaction processing system by switch network.This is that agency on the main computer is normal, in the time in a read data operation cycle, is initiated the situation of active and standby switching by the agency on the main computer;
7. if in the 5th step, before the switching timer expired that the agency on the guest machine started in the 4th step arrives, do not receive the response message of the agency on the main computer yet, then initiate active and standby switching by the agency on first guest machine;
8. if the agency on first guest machine initiates active and standby handoff failure, then then initiate active and standby switching by the agency on second guest machine, all fail up to guest machine;
Wherein, in the read/write data process, maximum difference is active/standby with return results difference behind the database instance treatment S QL on the machine: if reading data course, then except success/failure sign, return query results in addition, the write data process then can the return results collection, and active/standby different with the processing of machine on this, all the other are identical.
The 4th step illustrated data backup of the present invention/data reproduction process, specifically as shown in Figure 2, may further comprise the steps:
1. transaction processing system 40 is initiated the reading and writing operation, and in the local area network (LAN) of shared channel, packet can be comprised in this local area network (LAN) that all nodes of main computer 10 and guest machine 20 listen to;
2. main computer agency 101 and guest machine agency 201 receive and comprise the packet of carrying out the SQL instruction, start by " switching timer ", and simultaneously, database instance 102 on the main computer and the database instance 202 on the guest machine are also received this packet;
3. 102 pairs of this SQL operations of main computer database instance are finished, and return success/conditional codes such as failure flags, and 101 pairs of these signs of agency are sorted out judgment processing on the main computer, see Table 1:
Table 1
| Fault type | Classification criteria | Processing procedure |
| Logic fault, as: main | Fault can be recovered, no | If be asynchronous mode, |
| The key conflict can not find data, and table is locked ... etc. | Influence database manipulation next time | |
| Software fault, as: database instance is worked as machine, and program exception withdraws from, communication abnormality ... etc. | Fault is irrecoverable, influence database manipulation next time, but do not need manual intervention | " the switching timer " that |
| Hardware fault, as: machine is worked as machine, and network interface card is unusual, Bad Track ... etc. | Fault is irrecoverable, and influence is the database manipulation of section for a long time, needs manual intervention | Hardware fault has had influence on the operation of |
4. 202 pairs of this SQL operations of guest machine database instance are finished, and return success/conditional codes such as failure flags, and 201 pairs of these signs of agency are sorted out judgment processing on the guest machine, see Table 2:
Table 2
| Fault type | Classification criteria | Processing procedure |
| Logic fault, as: the major key conflict, can not find data, table is locked ... etc. | Fault can be recovered, and does not influence database manipulation next time | The |
| Software fault, as: database instance is worked as machine, and program exception withdraws from, communication abnormality ... etc. | Fault is irrecoverable, influence database manipulation next time, but do not need manual intervention | " the switching timer " that |
| Hardware fault, as: machine is worked as machine, and network interface card is unusual, Bad Track ... etc. | Fault is irrecoverable, and influence is the database manipulation of section for a long time, needs manual intervention | Hardware fault has had influence on the operation of |
5. if hardware fault has had influence on and has acted on behalf of 101 operation on the main computer in the 3rd step, can't respond acting on behalf of 201 " end of operation " notification message on the guest machine, will cause that then guest machine agency 201 can not receive response and enters switching flow;
6. if hardware fault has had influence on and has acted on behalf of 201 operation on the guest machine in the 4th step, can't initiate " end of operation " notification message, to cause that then main computer agency 101 can not receive message, and this guest machine will be designated as inefficacy, take over contingent next time switching by next guest machine;
7. the process of data backup is in the 2nd step, finish in the 4th step, agency 201 listens to the IP packet that transaction processing system 40 mails to main computer 10 on the guest machine, and abandons not according under the normal condition, and its partition is handled follow-up supervention to database instance on the guest machine 202;
At last, the active and standby machine handoff procedure of the present invention is described, specifically as shown in Figure 3, may further comprise the steps:
1. database instance 20b finishes this SQL operation on guest machine, send the message of this " end of operation " by agency 201 on the guest machine, act on behalf of after 101 on the notice main computer, if agency 201 is at the response message of not receiving on the main computer agency 101 within the certain hour on the guest machine, then beam back result such as this database manipulation success/failure flags to transaction processing system 40;
2. behind the return results, initiated to switch by agency on the guest machine 201, remaining this guest machine of guest machine of notice is upgraded to main computer, and obtains the affirmation of all normal guest machines, finishes some initial work;
3. on main computer, act on behalf of after the 101 SQL operating data bags that receive from transaction processing system 40, agency 101 starts " switching " timer on the main computer, if main computer is normal, return to main computer agency 101 time the result such as this success/failure flags of operation system, timer can be stopped zero clearing, if overtime, then initiate " switching " flow process " 2 ";
4. notify all guest machines by agency 101 on the main computer, guest machine has just been determined the replacement sequential queue when whole system is initialized, guest machine by queue heads is upgraded to main computer, main computer 10 enters the replacement rear of queue, become guest machine 20, and obtain the affirmation of all normal guest machines, finish some initial work;
5. after agency 201 IP with guest machine replace to the IP of main computer on the guest machine, can receive packet, carry out the SQL operation of database from transaction processing system 40;
6. the process of active and standby switching is finished by acting on behalf of " switching " timer of being managed on interacting message between the agency and the active and standby machine on the active and standby machine, and the former guarantees can carry out active and standby switching under the hardware fault, and the latter guarantees can carry out active and standby switching under the software fault.
Claims (8)
1. a database system backup method is characterized in that, uses the database manipulation packet to back up at a plurality of network nodes, may further comprise the steps:
1.1) with independent preservation the in original identical a plurality of network nodes of database in the Database Systems local area network (LAN);
1.2) this local area network (LAN) is connected with the transaction processing system that sends the database manipulation packet by gateway/router;
1.3) each network node carries out the same database operation by intercept the database manipulation packet of broadcasting simultaneously in the Database Systems local area network (LAN) to database instance separately.
2. according to the described backup method of claim 1, it is characterized in that described database manipulation is read operation, described step 1.3) in only the network node business datum of returning read operation show to the transaction processing system that sends the database manipulation packet.
3. according to the described backup method of claim 1, it is characterized in that described database manipulation is a write operation; Described step 1.3) in only a network node return the success of write operation/failure and indicate and give the transaction processing system that sends the database manipulation packet.
4. according to claim 2 or 3 described backup methods, it is characterized in that a described network node is a main computer, other network nodes are guest machine.
5. according to the described backup method of claim 4, it is characterized in that described guest machine is one or more.
6. according to the described backup method of claim 1, it is characterized in that described Database Systems are made of described network node, described Database Systems local area network (LAN) is is only connected and composed by described network node and network.
7. according to the described backup method of claim 6, it is characterized in that it is bus mode that described network connects.
8. according to the described backup method of claim 1, it is characterized in that the network interface card of described network node is made as the Promiscuous pattern.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA200610161788XA CN101212458A (en) | 2006-12-25 | 2006-12-25 | Database system backup method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA200610161788XA CN101212458A (en) | 2006-12-25 | 2006-12-25 | Database system backup method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101212458A true CN101212458A (en) | 2008-07-02 |
Family
ID=39612129
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA200610161788XA Withdrawn CN101212458A (en) | 2006-12-25 | 2006-12-25 | Database system backup method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101212458A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101917263A (en) * | 2010-08-16 | 2010-12-15 | 深圳市赫迪威信息技术有限公司 | Multi-machine hot standby method and system |
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
| WO2013082759A1 (en) * | 2011-12-06 | 2013-06-13 | 华为技术有限公司 | Data accessing method and system |
| CN103501290A (en) * | 2013-09-18 | 2014-01-08 | 万达信息股份有限公司 | High-reliability service system establishment method based on dynamic-backup virtual machines |
| CN103634411A (en) * | 2013-12-16 | 2014-03-12 | 上海证券交易所 | Real-time market data broadcasting system and real-time market data broadcasting method with state consistency |
| CN103781082A (en) * | 2012-10-17 | 2014-05-07 | 中兴通讯股份有限公司 | Communication method, apparatus and system |
| CN104202255A (en) * | 2014-08-26 | 2014-12-10 | 浪潮(北京)电子信息产业有限公司 | Efficient multi-link data transmission implementation method |
| CN104765889A (en) * | 2015-04-30 | 2015-07-08 | 北京奇虎科技有限公司 | Switching method and device of high-availability frame based on database |
| CN105068886A (en) * | 2015-07-30 | 2015-11-18 | 上海新炬网络信息技术有限公司 | Disaster backup intelligent switching control method based on GoldenGate |
| CN106202075A (en) * | 2015-04-29 | 2016-12-07 | 中兴通讯股份有限公司 | A kind of method and device of data base's active-standby switch |
| CN108415797A (en) * | 2018-03-05 | 2018-08-17 | 山东超越数控电子股份有限公司 | A method of avoid server failure switching according to library loss of data |
| CN108833164A (en) * | 2018-06-14 | 2018-11-16 | 杭州网易再顾科技有限公司 | Server control method, device, electronic equipment and storage medium |
| WO2020119699A1 (en) * | 2018-12-11 | 2020-06-18 | Oppo广东移动通信有限公司 | Resource publishing method and apparatus in internet of things, device, and storage medium |
-
2006
- 2006-12-25 CN CNA200610161788XA patent/CN101212458A/en not_active Withdrawn
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101917263A (en) * | 2010-08-16 | 2010-12-15 | 深圳市赫迪威信息技术有限公司 | Multi-machine hot standby method and system |
| WO2013082759A1 (en) * | 2011-12-06 | 2013-06-13 | 华为技术有限公司 | Data accessing method and system |
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
| CN103781082B (en) * | 2012-10-17 | 2018-07-06 | 中兴通讯股份有限公司 | The means of communication, apparatus and system |
| CN103781082A (en) * | 2012-10-17 | 2014-05-07 | 中兴通讯股份有限公司 | Communication method, apparatus and system |
| CN103501290A (en) * | 2013-09-18 | 2014-01-08 | 万达信息股份有限公司 | High-reliability service system establishment method based on dynamic-backup virtual machines |
| CN103501290B (en) * | 2013-09-18 | 2017-10-24 | 万达信息股份有限公司 | A kind of highly reliable service system construction method based on dynamic backup virtual machine |
| CN103634411A (en) * | 2013-12-16 | 2014-03-12 | 上海证券交易所 | Real-time market data broadcasting system and real-time market data broadcasting method with state consistency |
| CN103634411B (en) * | 2013-12-16 | 2017-06-06 | 上海证券交易所 | A kind of marketing data real time broadcasting system and method with state consistency |
| CN104202255A (en) * | 2014-08-26 | 2014-12-10 | 浪潮(北京)电子信息产业有限公司 | Efficient multi-link data transmission implementation method |
| CN106202075A (en) * | 2015-04-29 | 2016-12-07 | 中兴通讯股份有限公司 | A kind of method and device of data base's active-standby switch |
| CN104765889A (en) * | 2015-04-30 | 2015-07-08 | 北京奇虎科技有限公司 | Switching method and device of high-availability frame based on database |
| CN105068886A (en) * | 2015-07-30 | 2015-11-18 | 上海新炬网络信息技术有限公司 | Disaster backup intelligent switching control method based on GoldenGate |
| CN105068886B (en) * | 2015-07-30 | 2018-03-30 | 上海新炬网络信息技术股份有限公司 | The standby intelligence of calamity based on GoldenGate cuts control method |
| CN108415797A (en) * | 2018-03-05 | 2018-08-17 | 山东超越数控电子股份有限公司 | A method of avoid server failure switching according to library loss of data |
| CN108833164A (en) * | 2018-06-14 | 2018-11-16 | 杭州网易再顾科技有限公司 | Server control method, device, electronic equipment and storage medium |
| CN108833164B (en) * | 2018-06-14 | 2021-10-08 | 杭州网易再顾科技有限公司 | Server control method, device, electronic equipment and storage medium |
| WO2020119699A1 (en) * | 2018-12-11 | 2020-06-18 | Oppo广东移动通信有限公司 | Resource publishing method and apparatus in internet of things, device, and storage medium |
| US11463376B2 (en) | 2018-12-11 | 2022-10-04 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Resource distribution method and apparatus in Internet of Things, device, and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101207512B (en) | Method for switching and redundancy backup of database system | |
| CN101212458A (en) | Database system backup method | |
| CN106341454B (en) | Across computer room distributed data base management system (DDBMS) mostly living and method | |
| EP2281240B1 (en) | Maintaining data integrity in data servers across data centers | |
| CN100354834C (en) | Multi-site remote-copy system | |
| US7428657B2 (en) | Method for rolling back from snapshot with log | |
| CN101212341A (en) | Database system switching method | |
| CN106815097A (en) | Database disaster tolerance system and method | |
| US7945753B2 (en) | Computer system, management method and storage network system | |
| CN106357787A (en) | Storage disaster tolerant control system | |
| CN101145946B (en) | A fault tolerance cluster system and method based on message log | |
| JP2004532442A (en) | Failover processing in a storage system | |
| CN104503965A (en) | High-elasticity high availability and load balancing realization method of PostgreSQL (Structured Query Language) | |
| US7734884B1 (en) | Simultaneous concurrent and cascaded triangular asynchronous replication | |
| CN112511394B (en) | Management and maintenance method of RapidIO bus system | |
| CN109117310A (en) | Realize disaster tolerance system, the method and device of data backup | |
| CN111800484B (en) | Service anti-destruction replacing method for mobile edge information service system | |
| CN103186348B (en) | Storage system and data read-write method thereof | |
| CN109165122B (en) | Method for improving disaster recovery capability of application system same city multi-park deployment realized based on block chain technology | |
| WO2021115043A1 (en) | Distributed database system and data disaster backup drilling method | |
| CN102487332B (en) | Fault processing method, apparatus thereof and system thereof | |
| JPH09186686A (en) | Network management system | |
| CN101448028A (en) | Method for protecting continuous data, device and system thereof | |
| JPH0728667A (en) | Fault-tolerant computer system | |
| KR101513943B1 (en) | Method and system for operating management of real-time replicated database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C04 | Withdrawal of patent application after publication (patent law 2001) | ||
| WW01 | Invention patent application withdrawn after publication |