CN1756108A - Master/backup system data synchronizing method - Google Patents
Master/backup system data synchronizing method Download PDFInfo
- Publication number
- CN1756108A CN1756108A CN 200410080629 CN200410080629A CN1756108A CN 1756108 A CN1756108 A CN 1756108A CN 200410080629 CN200410080629 CN 200410080629 CN 200410080629 A CN200410080629 A CN 200410080629A CN 1756108 A CN1756108 A CN 1756108A
- Authority
- CN
- China
- Prior art keywords
- data
- data block
- main
- synchronization
- synchronizing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Hardware Redundancy (AREA)
- Multi Processors (AREA)
Abstract
Discloses a method for realizing the synchronization between the data of main and back-up systems comprises: the main system divides the data needed synchronization into several data blocks according to characters of said data; the main system judges if the contents of data blocks have changed, and the main system initiates the increment synchronization, or else, the main system initiates the batch synchronization according to the trigger conditions (as the factors which can make the data unconformity as timing synchronization cycle, system reset and the communication abnormal interruption between main and back-up systems); and the batch synchronization and increment synchronization are processed the synchronization according to the priority level of divided data blocks, while the higher priority one is processed first. The invention can reduce the number of unnecessary synchronization data between the main and back-up systems, and via the high priority data being processed first, improve the reliability of system compared to common method.
Description
Technical field
The present invention relates to method of data synchronization, especially relate to the method for data synchronization of leading between usefulness, back-up system.
Background technology
Data communication system requires system to have very high reliability usually, and redundancy is to improve a kind of basic skills of reliability.In the redundant system, the system that is in core status is generally adopted 1+1 backup or N+1 backup, in case when the master who is working broke down with system, back-up system is can very fast adapter main to become main usefulness with the work of system, make whole system can continue operate as normal.In master-slave conversion system, may relate to operations such as more dynamic data and configuration data, realize making main switching can not impact, must relate to main with data synchronization problem between, the back-up system to the normal operation of system with, back-up system.
In order to improve system reliability, adopt activestandby hot backup mechanism to be protected usually for the critical system in the system.Under the normal operating conditions, main in running order with system, the necessary function of the system that finishes, back-up system keeps real time data synchronous to main with system, go wrong can't be competent at a job the time with system when main, back-up system can in time fully be replaced the main system works of using, to improve the reliability of system.
Available technology adopting is compressed with system main the need data in synchronization, is sent to the method that decompresses after the back-up system with sliding window protocol, guarantees that the master uses, the data sync of back-up system.
Can analyze it from prior art has the following disadvantages:
Adopt compression algorithm to strengthen the computational complexity of system, method for synchronous in this scheme needs all data synchronously at every turn simultaneously, no matter need data in synchronization whether in back-up system, to exist, when the mass data in leading usefulness, back-up system is consistent like this, will transmit a lot of unnecessary synchrodatas in periodically synchronous, the master uses, the burden of back-up system communication thereby strengthen; Simultaneously; mainly switch if in synchronizing process, take place with, back-up system; because the method for The data compression transmits; the packed data that causes back-up system to be received may be incomplete; can not carry out correct decompression; at this moment back-up system just can not play the main function with system of protection, thereby reduces the reliability of system.
Summary of the invention
The problem that the present invention solves provides a kind of master/backup system data synchronizing method, and this method is avoided unnecessary synchrodata synchronously; Simultaneously can guarantee availability, the completeness of data in the back-up system to greatest extent, thereby improve the reliability of whole system on the whole.
For addressing the above problem, the invention provides a kind of master/backup system data synchronizing method, this method comprises,
A, main system need data in synchronization be divided into the plurality of data piece;
Whether the content of B, judgment data piece changes, if it is synchronous then to initiate increment; Otherwise, initiate in batches synchronously according to trigger condition.
Wherein, the described process that will need data in synchronization to be divided into the plurality of data piece specifically comprises:
21), according to the size of the arithmetic speed specified data piece of the data characteristic, data category and the system that need synchrodata in the system;
22), the big young pathbreaker according to data block needs data in synchronization to be divided into the plurality of data piece.
Wherein, the synchronous process of described increment specifically comprises: this data block is synchronized to system fully; Finish the increment synchronizing process;
Wherein, the synchronous process of described batch specifically comprises:
31), be equipped with system and upload data block to main system;
32), whether main system judge to be equipped with the corresponding data block contents of data block contents that system transmits and main system consistent, as inconsistent, then this data block is synchronized to system fully, finishes the batch synchronizing process, continuation execution in step B; As unanimity, then finish synchronizing process in batches, continue execution in step B.
Wherein, the described process that will need data in synchronization to be divided into the plurality of data piece also comprises: the check code of choosing respective type according to the arithmetic speed of the size of data block and system for the plurality of data piece.
Wherein, also comprise between described steps A and B: main preparation system is according to its corresponding check sign indicating number of data computation of each data block.
Wherein, the synchronous process of described batch specifically comprises:
41), the check code that will be equipped with after system will calculate reports main system;
42), main system judges whether the check code that the check code receive calculates with oneself is identical, if different, then this data block is synchronized to system fully, finishes synchronizing process in batches, continuation execution in step B; If identical, then finish synchronizing process in batches, continue execution in step B.
Wherein, comprise between described steps A and step B: the importance according to data is carried out prioritization to need data in synchronization piece.
Wherein, in the synchronous process of increment and in step 32) described in be synchronized to this data block fully that the process of system is specially: this data block successively is synchronized to system fully according to the priority order from high to low of data block.
Wherein, in step 42) described in be synchronized to this data block fully that the process of system is specially: data block successively is synchronized to system fully according to the priority order from high to low of data block.
Wherein, described trigger condition comprises: cycle synchronisation, system reset, main preparation system communication abnormality interrupt.
Compared with prior art, the present invention has the following advantages: owing to adopted deblocking, reduced synchrodata amount unnecessary in main usefulness, the back-up system data sync, thereby alleviated active and standby burden with system communication.In addition, by deblocking and by the whether consistent mode of check code judgment data piece, further reduced active and standby with unnecessary synchrodata amount in the system data synchronization process, thereby can further alleviate main burden with, back-up system communication; Simultaneously, by deblocking and with the whether consistent mode of check code checking data piece and the mode of prioritization, make the present invention improve the reliability of system than general fashion.
Description of drawings
Fig. 1 is the flow chart of first embodiment of the invention;
Fig. 2 is the synchronous flow chart of increment in the first embodiment of the invention;
Fig. 3 is a flow chart (not adopting check code) synchronous in batches in the first embodiment of the invention;
Fig. 4 is a flow chart (employing check code) synchronous in batches in the second embodiment of the invention;
Fig. 5 be for main with in the system with data block division and priority assignment and be synchronized to the schematic diagram of back-up system;
Fig. 6 is the synchronous flow chart of increment in the third embodiment of the invention;
Fig. 7 is a flow chart (not adopting check code and synchronous by the data block priority orders) synchronous in batches in the third embodiment of the invention;
Fig. 8 is a flow chart (adopting check code and synchronous by the data block priority orders) synchronous in batches in the fourth embodiment of the invention.
Embodiment
Data sync is meant that back-up system keeps with main in real time with the consistent process of system data in the activestandby hot backup system.In two kinds of situation, a kind of is that a kind of is that increment is synchronous in batches synchronously.
Described batch is meant that synchronously back-up system is to main mode of attempting carrying out data sync with all data of system, be used for abnormal conditions such as main usefulness, back-up system communicating interrupt/system reset, also be used for periodically synchronously, to guarantee back-up system and main with the data sync between system.
Described increment is meant synchronously works as the master with system works just often, and the master because its data changes (causing the main system configuration data to change as user's distribution configuration command), is synchronized to the data block contents that changes the process that is equipped with system with system.
This method discloses a kind of synchronous method of master/backup system data of optimization, and this method adopts the activestandby hot backup protected mode of N+1 (N＞=1).
Below in conjunction with Fig. 1 the first embodiment of the present invention is explained in detail.
In the present invention, execution in step S101 at first, to main with needing data in synchronization to be divided into the plurality of data piece in the system.Concrete operations are: step 1, size according to the composite factor specified data pieces such as arithmetic speed of data characteristic, data category and the system of need synchrodata, for example, every configuration order is fixed length M in the synchronous configuration data when needing in the system, when dividing configuration data blocks, select the size (M*N) of the integral multiple N of M as data block; If the arithmetic speed of CPU is very fast, suitably determine data block big; The classification of data is also referred to as the coupling between data, and during the dividing data piece, the data that coupling is stronger are divided in the same data block, and the more weak data of coupling are divided in the different data blocks.For example the business configuration data are divided into a data block, will protect the class data to be divided into a data block, the maintenance class data are divided into a data block.Step 2 needs data in synchronization to be divided into the plurality of data piece according to the big young pathbreaker of data block; For example, need synchronous configuration data total amount to be: T then can be divided into configuration data (T/ (M*N)+1) individual data block.
After synchrodata was divided into data block, then the least unit of each backup operation was a data block.In a system, data are divided into several data blocks, division can make most retouching operation once only relate to a data block like this, therefore the content that only needs a synchronous data block, and if the data block capacity after dividing is enough little, process that just can acceleration synchronization.
Then, execution in step S102, whether the content of main system judgment data piece changes situations such as (usually cause the main system configuration data to change) user's distribution configuration commands, in this way then execution in step S103 to carry out increment synchronous; If the content of data block does not change, execution in step S104 then, main system is initiated in batches synchronously according to trigger condition (as communicating interrupt, system reset or periodic synchronous etc.).
Describe the synchronous process of increment in detail below in conjunction with Fig. 2.
At first, main system execution in step S201, the content that detects some data block changes, it is synchronous to carry out increment, then main system execution in step S202 obtains carrying out increment data in synchronization block number, execution in step S203 then, the data block that numbering is corresponding is synchronized to system fully, finishes the increment synchronizing process then.
Below in conjunction with Fig. 3 the synchronous process of the present invention's batch is elaborated.
When main system detects when meeting in batches synchronous condition, at first execution in step S301 initiates synch command in batches to being equipped with system; After being equipped with system and receiving this order, execution in step S302 will be equipped with that each data block contents sends main system in the system; Follow execution in step S303, after main system receives the data block that system sends fully, whether the content of judging respective data blocks on these data block contents and the main system is consistent, if unanimity then finish this in batches synchronizing process, otherwise main system execution in step S304 promptly writes down inconsistent data block numbering; Then execution in step S305 is about to the corresponding data block of these data block numberings and is synchronized to system fully, finishes synchronizing process in batches.
Be the second embodiment of the present invention below.
At first main system need data in synchronization be divided into the plurality of data piece, and concrete operations are: step 1, according to the size of the composite factor specified data pieces such as arithmetic speed of data characteristic, data category and the system of need synchrodata; For example, every configuration order is fixed length M in the synchronous configuration data when needing in the system, when dividing configuration data blocks, selects the size (M*N) of the integral multiple N of M as data block; If the arithmetic speed of CPU is changed faster, can suitably determine the size of data block big; Data category is also referred to as the coupling between data, and during the dividing data piece, the data that coupling is stronger are divided in the same data block, and the more weak data of coupling are divided in the different data blocks.For example the business configuration data are divided into a data block, will protect the class data to be divided into a data block, the maintenance class data are divided into a data block.Step 2 needs data in synchronization to be divided into the plurality of data piece according to the big young pathbreaker of data block; For example, need synchronous configuration data total amount to be: T then can be divided into configuration data (T/ (M*N)+1) individual data block.Step 3 is chosen the check code of respective type for the plurality of data piece according to the arithmetic speed of the size of data block and system; For example when the data block size of dividing be 1K, if the speed of CPU is very fast, can select MD5 etc. to can be used for the check code type of digital signature; Otherwise can select in the transmission courses such as CRC-16 through being commonly used to guarantee the check code type of receiving terminal and transmitting terminal data consistency.
Secondly, main with, back-up system its corresponding check sign indicating number of data computation according to each data block.
Then, if change situations such as (usually cause the main system configuration data to change) user's distribution configuration commands has taken place the content of main system judgment data piece, it is synchronous then to carry out increment; If the content of data block does not change, then main system will be initiated in batches synchronously according to trigger condition (as communicating interrupt, system reset or periodic synchronous etc.).
The synchronous process of increment specifically describes as shown in Figure 2 with first embodiment.
Adopt the batch data synchronizing process of check code to be explained in detail below in conjunction with Fig. 4 to the present invention.
When main system detects when meeting in batches synchronous condition, at first execution in step S401 promptly initiates synch command in batches to being equipped with system; After this order was received by system fully, execution in step S402 calculated each data block check code of system fully, and reports main system; Main system receives execution in step S403 behind system's reported verification sign indicating number fully and calculates each data block check code on it; Main system has been calculated on it behind each data block check code, and whether execution in step S404 judges its check code that calculates and be equipped with system's reported verification sign indicating number consistent; As unanimity, then finish this synchronizing process in batches, as inconsistent, execution in step S405, the inconsistent data block numbering of record check code; Execution in step S406 numbers corresponding data block with these and is synchronized to system fully then, finishes this synchronizing process in batches.
Adopt the mode of check code can further reduce data sync amount between main preparation system, but need to increase the amount of calculation of main preparation system, be equivalent in the software design commonly used to exchange spatial strategy for the time.During concrete the application, can be according to the mode that how much determines whether to adopt check code of need synchrodata amount.If need the data in synchronization amount little, this mode is not adopted in suggestion, and adopts a last by way of example.
Be the third embodiment of the present invention below, this is a kind of master/backup system data synchronizing method of more optimizing.
At first the master will need data in synchronization to divide the plurality of data piece with system; Specific operation process is with first
Embodiment.
When needs carry out synchronous the time a plurality of data blocks, need be according to the importance of data block after having divided data block to system's operation, each data block is determined priority, formulate synchronizing sequence, for example: configuration data blocks is being arranged, the protected data piece, under the situation of three kinds of data blocks of service data piece, can the priority location of configuration data is the highest, protection class data priority takes second place, and maintenance class priority is minimum; As shown in Figure 5, be main with in the system data block being divided, and priority assignment and be synchronized to the example of back-up system.The data priority of business configuration is the highest, is labeled as data block A110; Secondly for protection class data, be labeled as data block B120; Secondly be the maintenance class data again, be labeled as data block C130, by that analogy, according to priority A＞B＞C＞D＞E＞... arrange.
Then carry out next step, when situations such as user's distribution configuration command caused the main system configuration data to change, change had taken place in the content that main system is judged data block, so it is synchronous to carry out increment; If the content of data block does not change, then main system will be initiated in batches synchronously according to trigger condition (as communicating interrupt, system reset or periodic synchronous etc.).
Describe the synchronous process of increment in detail below in conjunction with Fig. 6.
At first, main system execution in step S601, the content that detects some data block changes, it is synchronous to carry out increment, and then main system execution in step S602 obtains carrying out increment data in synchronization block number, execution in step S603 then, to successively be synchronized to system fully from high to low according to the priority orders of data block all over the data block of number correspondence, the elder generation that priority is high is synchronous, finishes the increment synchronizing process then.
Below in conjunction with Fig. 7 the synchronous process of the present invention's batch is elaborated.When main system detects when meeting in batches synchronous condition, at first execution in step S701 initiates synch command in batches to being equipped with system; After this order is received by system fully, execution in step S702 will be equipped with system and send each data block contents to main system; Follow execution in step S703, after main system receives the data block that system sends fully, whether the content of judging respective data blocks on these data block contents and the main system is consistent, if unanimity then finish this in batches synchronizing process, otherwise main system execution in step S704 promptly writes down inconsistent data block numbering; Then execution in step S705 is about to the corresponding data block of these data blocks numberings and successively is synchronized to system fully from high to low according to the priority orders of data block, and the elder generation that priority is high is synchronous, finishes synchronizing process in batches then.
Be the fourth embodiment of the present invention below, this is the another kind of master/backup system data synchronizing method of more optimizing.
At first the master will need data in synchronization to divide the plurality of data piece with system; Specific operation process is with second
Embodiment.
Secondly according to the importance of data block to system's operation, a plurality of data block data blocks are determined priority, formulate synchronizing sequence, for example: configuration data blocks is being arranged, the protected data piece, under the situation of three kinds of data blocks of service data piece, can the priority location of configuration data is the highest, protection class data priority takes second place, and maintenance class priority is minimum; As shown in Figure 5, be main to divide with data block in the system, and priority assignment and be synchronized to the example of back-up system.The data priority of business configuration is the highest, is labeled as data block A110; Secondly for protection class data, be labeled as data block B 120; Secondly be the maintenance class data again, be labeled as data block C130, by that analogy, according to priority A＞B＞C＞D＞E＞... arrange.
Then, main with, back-up system its corresponding check sign indicating number of data computation according to each data block.
Change situations such as (cause the main system configuration data to change) usually user's distribution configuration commands has taken place in the content of judging data block as main system, and it is synchronous then to carry out increment, and detailed process is with described in the 3rd embodiment; If the content of data block does not change, then main system will regularly be initiated in batches synchronously according to trigger condition (as communicating interrupt, system reset or periodic synchronous etc.).
Below in conjunction with Fig. 8 batch synchronizing process in the present embodiment is explained in detail.
When main system detects when meeting in batches synchronous condition, at first execution in step S801 promptly initiates synch command in batches to being equipped with system; After this order was received by system fully, execution in step S802 calculated each data block check code of system fully, and reports main system; Main system receives execution in step S803 behind system's reported verification sign indicating number fully and calculates each data block check code on it; Main system has been calculated on it behind each data block check code, and whether execution in step S804 judges its check code that calculates and be equipped with system's reported verification sign indicating number consistent; As unanimity, then finish this synchronizing process in batches, as inconsistent, execution in step S805, the inconsistent data block numbering of record check code; Execution in step S806 then, the data block that these numberings are corresponding successively is synchronized to system fully from high to low according to the priority orders of data block, and the elder generation that priority is high is synchronous, finishes synchronizing process in batches then.
Among the above-mentioned the 3rd and the 4th embodiment, because the master carries out data sync with system's height according to priority, promptly synchronous to the high high priority data of priority, synchronous subsequently to the data that priority is lower, even in synchronizing process, occur accident like this, as, communicating interrupt, unexpected termination synchronously etc., back-up system can use preferentially data in synchronization to finish basic functions, has increased the reliability of system so greatly.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in technical scope disclosed by the invention; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claims.
Claims (10)
1, a kind of master/backup system data synchronizing method is characterized in that, comprising:
A, main system need data in synchronization be divided into the plurality of data piece;
Whether the content of B, judgment data piece changes, if it is synchronous then to initiate increment; Otherwise, initiate in batches synchronously according to trigger condition.
According to the described master/backup system data synchronizing method of claim 1, it is characterized in that 2, the described process that will need data in synchronization to be divided into the plurality of data piece specifically comprises:
21), according to the size of the arithmetic speed specified data piece of the data characteristic, data category and the system that need synchrodata in the system;
22), the big young pathbreaker according to data block needs data in synchronization to be divided into the plurality of data piece.
3, according to the described master/backup system data synchronizing method of claim 2, it is characterized in that,
The synchronous process of described increment specifically comprises: this data block is synchronized to system fully; Finish the increment synchronizing process;
The synchronous process of described batch specifically comprises:
31), be equipped with system and upload data block to main system;
32), whether main system judge to be equipped with the corresponding data block contents of data block contents that system transmits and main system consistent, as inconsistent, then this data block is synchronized to system fully, finishes the batch synchronizing process, continuation execution in step B; As unanimity, then finish synchronizing process in batches, continue execution in step B.
According to the described master/backup system data synchronizing method of claim 2, it is characterized in that 4, the described process that will need data in synchronization to be divided into the plurality of data piece also comprises:
Choose the check code of respective type for the plurality of data piece according to the arithmetic speed of the size of data block and system.
5, according to the described master/backup system data synchronizing method of claim 4, it is characterized in that, between described steps A and B, also comprise:
Main preparation system is according to its corresponding check sign indicating number of data computation of each data block.
According to the described master/backup system data synchronizing method of claim 5, it is characterized in that 6, the synchronous process of described batch specifically comprises:
41), the check code that will be equipped with after system will calculate reports main system;
42), main system judges whether the check code that the check code receive calculates with oneself is identical, if different, then this data block is synchronized to system fully, finishes synchronizing process in batches, continuation execution in step B; If identical, then finish synchronizing process in batches, continue execution in step B.
7, according to each described master/backup system data synchronizing method of claim 1 to 6, it is characterized in that, between described steps A and step B, comprise:
Importance according to data is carried out prioritization to need data in synchronization piece.
8, according to the described master/backup system data synchronizing method of claim 7, it is characterized in that, in the synchronous process of increment and in step 32) described in be synchronized to this data block fully that the process of system is specially: this data block successively is synchronized to system fully according to the priority order from high to low of data block.
9, according to the described master/backup system data synchronizing method of claim 7, it is characterized in that, in step 42) described in be synchronized to this data block fully that the process of system is specially: data block successively is synchronized to system fully according to the priority order from high to low of data block.
10, according to claim 8 or 9 described master/backup system data synchronizing methods, it is characterized in that described trigger condition comprises: cycle synchronisation, system reset, main preparation system communication abnormality interrupt.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410080629 CN1756108A (en) | 2004-09-29 | 2004-09-29 | Master/backup system data synchronizing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410080629 CN1756108A (en) | 2004-09-29 | 2004-09-29 | Master/backup system data synchronizing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1756108A true CN1756108A (en) | 2006-04-05 |
Family
ID=36689105
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200410080629 Pending CN1756108A (en) | 2004-09-29 | 2004-09-29 | Master/backup system data synchronizing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1756108A (en) |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101937435A (en) * | 2009-07-01 | 2011-01-05 | 北京科东电力控制系统有限责任公司 | Online synchronized method of distributed real-time database confronting power system |
| CN101110608B (en) * | 2007-08-23 | 2011-02-09 | 华为技术有限公司 | Method, system and device for data detection of main and spare plate |
| CN102064932A (en) * | 2010-12-30 | 2011-05-18 | 上海顶竹通讯技术有限公司 | Method and device for synchronizing data between different equipment |
| CN103092840A (en) * | 2011-10-28 | 2013-05-08 | 上海邮电设计咨询研究院有限公司 | Method for acquiring self-increment mass data files from multiple sources |
| CN103500130A (en) * | 2013-09-11 | 2014-01-08 | 上海爱数软件有限公司 | Method for backing up dual-computer hot standby data in real time |
| WO2014053089A1 (en) * | 2012-10-01 | 2014-04-10 | Huawei Technologies Co., Ltd. | Controlling data synchronization and backup services |
| CN103905397A (en) * | 2012-12-28 | 2014-07-02 | 腾讯科技（深圳）有限公司 | Data synchronization method and system |
| CN104272649A (en) * | 2011-11-04 | 2015-01-07 | 达索系统加拿大软件股份有限公司 | System and method for data communication over a network |
| CN104299065A (en) * | 2014-07-30 | 2015-01-21 | 国家电网公司 | Dispatching automation host and backup model correctness checking method |
| CN104618434A (en) * | 2014-12-23 | 2015-05-13 | 上海斐讯数据通信技术有限公司 | Synchronization method and system for mPortal system data |
| CN105224418A (en) * | 2015-09-06 | 2016-01-06 | 福建三元达通讯股份有限公司 | A kind of data back up method and device |
| CN105474250A (en) * | 2013-07-12 | 2016-04-06 | 贸易技术国际公司 | Tailored messaging |
| CN106357703A (en) * | 2015-07-13 | 2017-01-25 | 阿里巴巴集团控股有限公司 | Cluster switching method and cluster switching equipment |
| CN106936940A (en) * | 2017-02-10 | 2017-07-07 | 福建三元达网络技术有限公司 | Lease information backup method and system in a kind of Dynamic Host Configuration Protocol server |
| CN108259227A (en) * | 2017-12-22 | 2018-07-06 | 合肥工大高科信息科技股份有限公司 | A kind of method of data synchronization of two-node cluster hot backup interlock system |
| CN105323289B (en) * | 2014-08-01 | 2019-02-05 | 上海博达数据通信有限公司 | One kind being based on distributed method of data synchronization |
| CN110781032A (en) * | 2019-09-26 | 2020-02-11 | 北京大米科技有限公司 | Data transmission method, device, electronic equipment and medium |
| CN110958171A (en) * | 2019-11-29 | 2020-04-03 | 盛科网络（苏州）有限公司 | Data synchronization method and system based on main and standby equipment |
| CN112839067A (en) * | 2019-11-22 | 2021-05-25 | 腾讯科技（深圳）有限公司 | Data synchronization method and device |
| CN113830134A (en) * | 2021-08-25 | 2021-12-24 | 通号城市轨道交通技术有限公司 | Vehicle-mounted ATP (automatic train protection) dual-system switching method and logic unit of vehicle-mounted ATP |
| CN114584574A (en) * | 2022-04-28 | 2022-06-03 | 武汉四通信息服务有限公司 | Data synchronization method and device, computer equipment and storage medium |
-
2004
- 2004-09-29 CN CN 200410080629 patent/CN1756108A/en active Pending
Cited By (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101110608B (en) * | 2007-08-23 | 2011-02-09 | 华为技术有限公司 | Method, system and device for data detection of main and spare plate |
| CN101937435A (en) * | 2009-07-01 | 2011-01-05 | 北京科东电力控制系统有限责任公司 | Online synchronized method of distributed real-time database confronting power system |
| CN102064932A (en) * | 2010-12-30 | 2011-05-18 | 上海顶竹通讯技术有限公司 | Method and device for synchronizing data between different equipment |
| CN103092840B (en) * | 2011-10-28 | 2015-09-16 | 上海邮电设计咨询研究院有限公司 | Multi-source is from increasing massive data files real-time collecting method |
| CN103092840A (en) * | 2011-10-28 | 2013-05-08 | 上海邮电设计咨询研究院有限公司 | Method for acquiring self-increment mass data files from multiple sources |
| CN104272649A (en) * | 2011-11-04 | 2015-01-07 | 达索系统加拿大软件股份有限公司 | System and method for data communication over a network |
| CN103947124A (en) * | 2012-10-01 | 2014-07-23 | 华为技术有限公司 | Controlling data synchronization and backup services |
| WO2014053089A1 (en) * | 2012-10-01 | 2014-04-10 | Huawei Technologies Co., Ltd. | Controlling data synchronization and backup services |
| CN103947124B (en) * | 2012-10-01 | 2016-03-09 | 华为技术有限公司 | Synchronous and the backup services of control data |
| CN103905397A (en) * | 2012-12-28 | 2014-07-02 | 腾讯科技（深圳）有限公司 | Data synchronization method and system |
| WO2014101684A1 (en) * | 2012-12-28 | 2014-07-03 | 腾讯科技（深圳）有限公司 | Data synchronizing method, apparatus and system |
| US9753656B2 (en) | 2012-12-28 | 2017-09-05 | Tencent Technology (Shenzhen) Company Limited | Data synchronization method, apparatus and system |
| CN103905397B (en) * | 2012-12-28 | 2015-05-13 | 腾讯科技（深圳）有限公司 | Data synchronization method and system |
| CN111581551A (en) * | 2013-07-12 | 2020-08-25 | 贸易技术国际公司 | Customized messaging |
| CN105474250A (en) * | 2013-07-12 | 2016-04-06 | 贸易技术国际公司 | Tailored messaging |
| CN105474250B (en) * | 2013-07-12 | 2020-04-24 | 贸易技术国际公司 | Customized messaging |
| CN103500130B (en) * | 2013-09-11 | 2015-07-29 | 上海爱数软件有限公司 | A kind of method that two-node cluster hot backup data are backed up in realtime |
| CN103500130A (en) * | 2013-09-11 | 2014-01-08 | 上海爱数软件有限公司 | Method for backing up dual-computer hot standby data in real time |
| CN104299065A (en) * | 2014-07-30 | 2015-01-21 | 国家电网公司 | Dispatching automation host and backup model correctness checking method |
| CN104299065B (en) * | 2014-07-30 | 2017-08-22 | 国家电网公司 | A kind of method that Correctness of model is verified between dispatching automation main preparation system |
| CN105323289B (en) * | 2014-08-01 | 2019-02-05 | 上海博达数据通信有限公司 | One kind being based on distributed method of data synchronization |
| CN104618434A (en) * | 2014-12-23 | 2015-05-13 | 上海斐讯数据通信技术有限公司 | Synchronization method and system for mPortal system data |
| CN106357703A (en) * | 2015-07-13 | 2017-01-25 | 阿里巴巴集团控股有限公司 | Cluster switching method and cluster switching equipment |
| CN106357703B (en) * | 2015-07-13 | 2020-03-10 | 阿里巴巴集团控股有限公司 | Cluster switching method and device |
| US10609141B2 (en) | 2015-07-13 | 2020-03-31 | Alibaba Group Holding Limited | Methods and apparatuses for cluster switching |
| CN105224418A (en) * | 2015-09-06 | 2016-01-06 | 福建三元达通讯股份有限公司 | A kind of data back up method and device |
| CN106936940A (en) * | 2017-02-10 | 2017-07-07 | 福建三元达网络技术有限公司 | Lease information backup method and system in a kind of Dynamic Host Configuration Protocol server |
| CN106936940B (en) * | 2017-02-10 | 2019-11-08 | 安科讯(福建)科技有限公司 | Lease information backup method and system in a kind of Dynamic Host Configuration Protocol server |
| CN108259227A (en) * | 2017-12-22 | 2018-07-06 | 合肥工大高科信息科技股份有限公司 | A kind of method of data synchronization of two-node cluster hot backup interlock system |
| CN108259227B (en) * | 2017-12-22 | 2021-01-08 | 合肥工大高科信息科技股份有限公司 | Data synchronization method of dual-computer hot standby interlocking system |
| CN110781032A (en) * | 2019-09-26 | 2020-02-11 | 北京大米科技有限公司 | Data transmission method, device, electronic equipment and medium |
| CN112839067A (en) * | 2019-11-22 | 2021-05-25 | 腾讯科技（深圳）有限公司 | Data synchronization method and device |
| CN110958171A (en) * | 2019-11-29 | 2020-04-03 | 盛科网络（苏州）有限公司 | Data synchronization method and system based on main and standby equipment |
| CN113830134A (en) * | 2021-08-25 | 2021-12-24 | 通号城市轨道交通技术有限公司 | Vehicle-mounted ATP (automatic train protection) dual-system switching method and logic unit of vehicle-mounted ATP |
| CN113830134B (en) * | 2021-08-25 | 2024-03-15 | 通号城市轨道交通技术有限公司 | Vehicle-mounted ATP double-system switching method and logic unit of vehicle-mounted ATP |
| CN114584574A (en) * | 2022-04-28 | 2022-06-03 | 武汉四通信息服务有限公司 | Data synchronization method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1756108A (en) | Master/backup system data synchronizing method | |
| CN103262044B (en) | The method of virtual machine failover management and back-up system thereof | |
| CN1195813A (en) | System of reporting errors by hardward element of distributed computer system | |
| CN1190094C (en) | Processor duplex apparatus based on real time operation system in mobile communication system and its method | |
| EP2437178B1 (en) | Method, apparatus, and system for processing memory dump | |
| CN1892612A (en) | Cluster availability management method and system | |
| CN1859022A (en) | Communication device and method for realizing master control board and service board master and slave conversion | |
| CN1495611A (en) | Fault-tderant computer system and its resynchronization method and program | |
| CN1794196A (en) | Securing time for identifying cause of asynchronism in fault-tolerant computer | |
| CN1821913A (en) | Communication system and method based on I2C | |
| CN1881934A (en) | Microprocessor, network system, and communication method | |
| CN1753376A (en) | Biprimary controlled network equipment and its master back-up switching method | |
| CN1159657C (en) | Bus system and its data transmitting method | |
| CN1753377A (en) | Method of avoiding access collision of redundant main station against serial bus ink | |
| CN1852154A (en) | Intelligent net business control device disaster tolerance system | |
| CN1197236A (en) | Method of reporting errors by hardward element of distributed computer system | |
| CN1295903C (en) | A safe system starting method | |
| CN1547330A (en) | A method for multi-port multi-link communication network backup control and apparatus therefor | |
| CN105119949A (en) | Data synchronization method and system based on multistage slice difference distribution statistics | |
| CN101605051B (en) | Method and device for realizing changeover between main and standby services on control panels | |
| CN1302372C (en) | Method of interrupting printing for solving wrong printing in networked printing system | |
| CN1269331C (en) | Method for sanding and receiving data based on synchronous serial interface in digital signal processor | |
| CN101561795A (en) | Method and device for synchronizing data in distribution-type system | |
| CN1777848A (en) | Method, interface and network for the cyclic transmission of Ethernet telegrams | |
| CN105354110A (en) | Cloud server data backup method and apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |