CN108243208A - A kind of method of data synchronization and device - Google Patents
A kind of method of data synchronization and device Download PDFInfo
- Publication number
- CN108243208A CN108243208A CN201611209618.4A CN201611209618A CN108243208A CN 108243208 A CN108243208 A CN 108243208A CN 201611209618 A CN201611209618 A CN 201611209618A CN 108243208 A CN108243208 A CN 108243208A
- Authority
- CN
- China
- Prior art keywords
- data
- synchronized
- time
- newer
- timestamp
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Abstract
The invention discloses a kind of method of data synchronization and devices, obtain data to be synchronized, include the first identity ID for identifying the data to be synchronized in the data to be synchronized, determine that there is no the first ID in the 2nd ID set, ID in the 2nd ID set is successfully completed synchronous data for identifying, and synchronizes the data to be synchronized.How to realize that data synchronize when can solve the problem of that multiple data centers provide application access to the user jointly in the prior art by the present invention between multiple data centers.
Description
Technical field
The present invention relates to Internet technical fields, and in particular to a kind of method of data synchronization and device.
Background technology
With becoming increasingly popular for network service, the type of network application is more and more, by network application accessing network equipment
Caused user data visit capacity is increasing.At present, network data is usually stored entirely in a data center, the data
Center often data access amount is excessive or hardware, computer room, network etc. due to and break down, individual data center occurs
Failure can lead to happening for service disruption, therefore provide the system reliability ratio of data service for application by individual data center
It is relatively low.
With the extension of current business scale and the increase of data center's disaster tolerance demand, the data that individual data center provides
Service cannot undertake the demand of various applications.Therefore need the demand of multiple various applications of data center's shared.
When multiple data centers provide application access to the user jointly, need to ensure the consistency of data.To ensure each number
According to data consistency in center, need to carry out the synchronized update of data between each data center, there is presently no one kind to be directed to
The method that data synchronize is realized between multiple data centers for providing application access to the user jointly.
Invention content
The object of the present invention is to provide a kind of method of data synchronization and device, to solve multiple data centers in the prior art
The problem of data synchronization is carried out when providing application access to the user jointly, between multiple data centers.
The purpose of the present invention is what is be achieved through the following technical solutions：
In a first aspect, a kind of method of data synchronization is provided, in this method, by data sending terminal to be synchronized (i.e. in data
The heart) determine data to be synchronized, and create for data to be synchronized described in unique mark the first identity (Identity,
ID), the first ID is added to the data to be synchronized, and the data to be synchronized added with the first ID are sent
To data receiver to be synchronized (i.e. data center).Data receiver to be synchronized acquisition includes number to be synchronized described in unique mark
According to the data to be synchronized of the first ID, there is no in the case of the first ID in the 2nd ID set is determined, described in write-in
Data to be synchronized.
Wherein, the ID in the 2nd ID set is successfully completed synchronous data for identifying.
In the embodiment of the present invention, the data to be synchronized for including the first ID are sent to same step number by data sending terminal to be synchronized
According to receiving terminal, ID ratios during data receiver to be synchronized is gathered by the ID for including the data to be synchronized got and the 2nd ID
Compared with, in the case where the first ID is not present in determining the 2nd ID set, the write-in data to be synchronized.By write-in and
Data to be synchronized different ID through successful synchronization data avoid and are repeatedly written the identical data to be synchronized of ID, that is, avoid
Identical data to be synchronized are repeatedly written, solve the data synchronization problems between multiple data centers, and are avoided multiple
During carrying out data synchronization updating between data center, data update is reliable caused by being repeatedly written data to be synchronized
The problem of property is relatively low.
Preferably, having time stamp is further included in the data to be synchronized, it is described to determine that there is no described in the 2nd ID set
After first ID, further include：
Determine the timestamp institute that the timestamp that the data to be synchronized include characterizes the time, includes with initial data
The sequencing of time is characterized, according to preset synchronization policy and the sequencing, it is institute that determining, which needs synchronous data,
Data to be synchronized are stated, and the first ID is added in the 2nd ID set.
Wherein, the data with existing before the initial data is write-in data to be synchronized, the preset synchronization policy are used
Timestamp select to characterize the data that the time is first or posterior data are as needs synchronization in instruction.
If preferably, according to preset synchronization policy and the sequencing, it is not institute that determining, which needs synchronous data,
State data to be synchronized, then it will be in the data storage to data collision set to be synchronized.
Second aspect, provides a kind of method of data synchronization, and in this method, data receiver to be synchronized determines number to be synchronized
According to, including：
Determine database journal, the database journal includes newer data occur and newer data occur
Renewal time；According to the renewal time that newer data occur in the database journal, the newer data of generation are created
Timestamp；Newer data and the timestamp that newer data occur occurs by described, is determined as data to be synchronized.
The third aspect provides a kind of data synchronization unit, including：
Acquiring unit for obtaining data to be synchronized, includes to treat described in unique mark in the data to be synchronized
First ID of synchrodata；
Processing unit, for determining that there is no the data packets to be synchronized that the acquiring unit obtains in the 2nd ID set
The first ID included, wherein, the ID in the 2nd ID set is successfully completed synchronous data for identifying；
Synchronization unit, for determining that there is no the institutes that the acquiring unit obtains in the 2nd ID set in the processing unit
In the case of stating the first ID that data to be synchronized include, the data to be synchronized that the acquiring unit obtains are written.
Preferably, having time stamp is further included in the data to be synchronized that the acquiring unit obtains；
The processing unit is additionally operable to：
There is no after the first ID in the 2nd ID set is determined, the time that the data to be synchronized include is determined
Stamp characterizes the time, the sequencing for the time that the timestamp included with initial data is characterized；According to preset synchronous plan
Slightly and the sequencing, the data for determining needs synchronization are the data to be synchronized, and the first ID are added to institute
It states in the 2nd ID set.
Wherein, the data with existing before the initial data is write-in data to be synchronized, the preset synchronization policy are used
Timestamp select to characterize the data that the time is first or posterior data are as needs synchronization in instruction.
Preferably, the processing unit is additionally operable to：
If according to preset synchronization policy and the sequencing, it is same to determine that the synchronous data of needs are not treated for described in
Step data, then will be in the data storage to data collision set to be synchronized.
Fourth aspect provides a kind of data synchronization unit, including：
Determination unit, for determining data to be synchronized；
Creating unit, for creating the first body of the data to be synchronized determined for determination unit described in unique mark
Part mark ID；
The first ID that the creating unit creates is added to the data to be synchronized by adding device；
Transmitting element, for sending the data to be synchronized after the adding device adds the first ID.
Preferably, the determination unit specifically determines data to be synchronized in the following way：
Determine database journal, the database journal includes newer data occur and newer data occur
Renewal time；
According to the renewal time that newer data occur in the database journal, the newer data of generation are created
Timestamp；
Newer data and the timestamp that newer data occur occurs by described, is determined as data to be synchronized.
Description of the drawings
Fig. 1 realizes flow chart for a kind of method of data synchronization provided in an embodiment of the present invention；
Fig. 2 is a kind of method flow diagram for determining data to be synchronized provided in an embodiment of the present invention；
Fig. 3 realizes flow chart for another method of data synchronization provided in an embodiment of the present invention；
Fig. 4 realizes flow chart for another method of data synchronization provided in an embodiment of the present invention；
Fig. 5 realizes flow chart for another method of data synchronization provided in an embodiment of the present invention；
Fig. 6 realizes flow chart for a kind of data synchronous interaction provided in an embodiment of the present invention；
Fig. 7 is a kind of data synchronization unit schematic diagram provided in an embodiment of the present invention；
Fig. 8 is another data synchronization unit schematic diagram provided in an embodiment of the present invention.
Specific embodiment
Below in conjunction with the attached drawing in the embodiment of the present invention, the technical solution in the embodiment of the present invention is retouched in detail
It states, it is clear that described embodiment is only part of the embodiment of the present invention, is not whole embodiments.
In order to solve the problems, such as that data synchronize between multiple data centers, the embodiment of the present invention provides a kind of data and synchronizes
Method.
Below in conjunction with the accompanying drawings, a kind of method of data synchronization specific embodiment provided in an embodiment of the present invention is carried out detailed
Explanation.
Fig. 1 show a kind of method of data synchronization provided in an embodiment of the present invention and realizes flow chart, as shown in Figure 1, including：
S101：Determine data to be synchronized.
In the embodiment of the present invention, when the data in a data center update, newer data occur by described
It is determined as data to be synchronized.
In the embodiment of the present invention, mode shown in Fig. 2 specifically can be used and determine data to be synchronized, as shown in Fig. 2, including：
S201：Determine database journal, the database journal includes newer data occur and occur newer
The renewal time of data.
In the embodiment of the present invention, database journal is the database journal that carries of database, database day in data center
Will includes newer data information occurs in database, for example, newer data occur and newer data occur more
The new time.
S202：According to the renewal time that newer data occur in the database journal, it is newer to create the generation
The timestamp of data.
S203：Newer data and the timestamp that newer data occur occurs by described, is determined as to be synchronized
Data.
In the embodiment of the present invention, newer each data will occur in database journal and occurred more according to described
The timestamp that the renewal time of new each data creates, is determined as data to be synchronized.
S102：Create the first ID for data to be synchronized described in unique mark.
It is data to be synchronized to identify the newer data of generation, according to certain algorithm in the embodiment of the present invention
One group of ID is created, no repetition ID, every ID are for data to be synchronized described in unique mark in this group of ID, in this way, other data
Center receive include the first ID data can determine whether the data be data to be synchronized.
S103：First ID is added to the data to be synchronized.
S104：Send the data to be synchronized added with the first ID.
S105：Obtain data to be synchronized.
S106：Determine that there is no the first ID in the 2nd ID set.
In the embodiment of the present invention, multiple data centers can treat together during synchrodata according to successful synchronization
First ID of step data creates a 2nd ID set, i.e. the 2nd ID set includes data to be synchronized of successful synchronization
ID.When a data center gets a data to be synchronized, judge in the 2nd ID set with the presence or absence of the number to be synchronized
According to the first ID, if the 2nd ID set in there are the first ID, be not written into the corresponding data to be synchronized of the first ID.If
The first ID is not present in 2nd ID set, it may be determined that the corresponding data to be synchronized of the first ID are also failed same
Step, then be written the corresponding data to be synchronized of the first ID.
S107：The data to be synchronized are written.
In the embodiment of the present invention, the corresponding data to be synchronized of the first ID being not present in the 2nd ID set is determined are also
After failed write-in, the data to be synchronized are written.When through the above scheme, subsequently to carry out data synchronization, weight is avoided
It makes carbon copies into the data for including the first ID.
In the embodiment of the present invention, sent to same data center with Liang Ge data centers treated for same data below
It is illustrated for synchrodata.When occurring the data update for same data there are two data center A and B, in data
The time that heart A is updated the data is first, the time that data center B is updated the data rear, at this point, data center A and data center B are equal
This is synchronized to data center C to update the data, due to the number to be synchronized of the data center C data center A got and data center B
According to including the first ID it is different, therefore data center C will include the data update number to be synchronized of the first ID of difference according to the two
According to.Data center C only needs newest data to be synchronized synchronization time in practical application, therefore in the embodiment of the present invention, it is described to treat
Having time stamp is further included in synchrodata, the timestamp is used for judging the time that data to be synchronized occur, by comparing the time
Stamp characterizes the priority of time and can determine newest data to be synchronized.
In the embodiment of the present invention, before the data to be synchronized are written, also determine what the data to be synchronized included
The timestamp that the time and initial data that timestamp is characterized include characterizes the sequencing of time, suitable according to the priority
Sequence and preset synchronization policy, and then determine to need whether synchronous data are the data to be synchronized.Wherein, it is described preset
Synchronization policy, which is used to indicate, selects that timestamp characterizes that the time is first or posterior data are as needing synchronous data.Wherein,
Preset synchronization policy can specifically be set according to practical situations, and the embodiment of the present invention is not especially limited, below with default
Synchronization policy be used to indicate select timestamp characterize time posterior data as the data instance finally synchronously completed into
Row explanation.
Fig. 3 show another method of data synchronization provided in an embodiment of the present invention and realizes flow chart, as shown in figure 3, its
In middle S301, S302, S303, S304, S305, S306 and S310 and Fig. 1 S101, S102, S103, S104, S105, S106 and
S107 is identical, the difference lies in, determine that the timestamp that includes of the data to be synchronized characterizes the time in S307, it is and original
The timestamp that data include characterizes the sequencing of time.According to preset synchronization policy and the priority in S308
Sequentially, it is the data to be synchronized that determining, which needs synchronous data,.The first ID is added to the 2nd ID collection in S309
In conjunction.Through the above scheme, when have for the same data to be synchronized updated the data need write-in when, can avoid write-in conflict
Generation, and be ensured of using timestamp and characterize time newest data to be synchronized as the data finally synchronously completed.
It in the embodiment of the present invention, is written after the data to be synchronized, passes through the first ID that will complete write-in
In gathering added to the 2nd ID, indicate that the data to be synchronized successfully complete write-in, during subsequently to carry out data synchronization,
When receiving the data to be synchronized including identical first ID, avoid being repeatedly written the data for including the first ID.
It is above-mentioned to be described in detail according to preset synchronization policy and the sequencing in the embodiment of the present invention, it determines
Synchronous data are needed for the operation after the data to be synchronized, if being described more detail below according to preset synchronization policy,
And the sequencing, when determining to need synchronous data for the data to be synchronized, how to handle the number to be synchronized
According to.
Fig. 4 show another method of data synchronization provided in an embodiment of the present invention and realizes flow chart, as shown in figure 4, its
In, S301, S302, S303, S304, S305 in S401, S402, S403, S404, S405, S406, S407 and S409 and Fig. 3,
S306, S307 are identical with S310, the difference lies in, if according to preset synchronization policy and the sequencing in S408,
It is not the data to be synchronized that determining, which needs synchronous data, then will be in the data storage to data collision set to be synchronized.
It is stored by the data to be synchronized that will do not need to be synchronous into data collision set, convenient for being received later to identical data
Update when, carry out data collision inspection.
In the embodiment of the present invention, when needing, the data to be synchronized for synchronizing processing are more, and data center has little time to handle
In the case of, loss of data to be synchronized may be caused, and then lead to failure of data synchronization, on during progress data synchronization
The occurrence of stating, therefore data sending terminal to be synchronized is cached after data to be synchronized are determined, data receiver to be synchronized
After data to be synchronized are got, also the data to be synchronized are cached.
Fig. 5 show another method of data synchronization provided in an embodiment of the present invention and realizes flow chart, as shown in figure 5, its
In, S501, S502, S503, S505, S506, S508, S509, S510 and S511 respectively with S401, S402 in Fig. 4, S403,
S404, S405, S406, S407, S408 are identical with S409, and the difference lies in cache data to be synchronized in S504 and S507.It is logical
Cross and cache the data to be synchronized, avoid in the case where data center has little time processing, caused by loss of data to be synchronized
Problem.
In the embodiment of the present invention, it is same data will to be carried out with Liang Ge data centers, for the interactive process of synchrodata below
Step explanation, i.e., one of data center connect as data sending terminal to be synchronized, another data center as data to be synchronized
Receiving end.
Fig. 6 show a kind of data synchronous interaction provided in an embodiment of the present invention and realizes flow chart, as shown in fig. 6, in Fig. 6
Data center A is the data center that data update occurs, and data center A determines to include timestamp by analytical database daily record
With the data to be synchronized of ID (being the first ID), by the data buffer storage to be synchronized and it is sent to data center B.Data center B
It obtains the data to be synchronized and caches, judge to whether there is the first ID of the data to be synchronized in the 2nd ID set, if the
There are the first ID in two ID set, then are not written into the corresponding data to be synchronized of the first ID.If in the 2nd ID set not
There are the first ID, and determine time that the timestamp that includes of data to be synchronized is characterized when initial data includes
Between after stamp characterize the time, data center B is written data to be synchronized, and by including the 2nd ID of the first ID additions gather.
Wherein, data center B if it is determined that time for being characterized of the timestamp that data to be synchronized include when initial data includes
Between before stamp characterizes the time, then the data to be synchronized are stored into data collision set, so that data center's A energy
Enough carry out that data collision is counter investigates and prosecutes reason.
A kind of data synchronization unit in the embodiment of the present invention is also provided, the composition and use of the device is described more fully below
On the way.
Fig. 7 show a kind of data synchronization unit schematic diagram provided in an embodiment of the present invention, as shown in fig. 7, the device packet
Acquiring unit 101, processing unit 102 and synchronization unit 103 are included, wherein：
Acquiring unit 101 for obtaining data to be synchronized, includes in the data to be synchronized for described in unique mark
First identity ID of data to be synchronized；
Processing unit 102, for determining that there is no the described to be synchronized of the acquiring unit 101 acquisition in the 2nd ID set
The first ID that data include, wherein, the ID in the 2nd ID set is successfully completed synchronous data for identifying；
Synchronization unit 103, for determining that the acquiring unit is not present in the 2nd ID set in the processing unit 102
In the case of the first ID that 101 data to be synchronized obtained include, the number to be synchronized that the acquiring unit 101 obtains is written
According to.
In the embodiment of the present invention, having time stamp is further included in the data to be synchronized that the acquiring unit 101 obtains；
The processing unit 102 is additionally operable to：
There is no after the first ID in the 2nd ID set is determined, the time that the data to be synchronized include is determined
Stamp characterizes the time, the sequencing for the time that the timestamp included with initial data is characterized；According to preset synchronous plan
Slightly and the sequencing, the data for determining needs synchronization are the data to be synchronized, the first ID are added to described
In 2nd ID set.
Wherein, the data with existing before the initial data is write-in data to be synchronized, the preset synchronization policy are used
Timestamp select to characterize the data that the time is first or posterior data are as needs synchronization in instruction.
In the embodiment of the present invention, the processing unit 102 is additionally operable to：
If according to preset synchronization policy and the sequencing, it is same to determine that the synchronous data of needs are not treated for described in
Step data, then will be in the data storage to data collision set to be synchronized.
Another data synchronization unit in the embodiment of the present invention is also provided, the composition and use of the device is described more fully below
On the way.
Fig. 8 show another data synchronization unit schematic diagram provided in an embodiment of the present invention, as shown in figure 8, the device
Including determination unit 201, creating unit 202, adding device 203 and transmitting element 204, wherein：
Determination unit 201, for determining data to be synchronized；
Creating unit 202, for creating the data to be synchronized determined for determination unit 201 described in unique mark
First ID；
The first ID that the creating unit 202 creates is added to the data to be synchronized by adding device 203；
Transmitting element 204, for sending the number to be synchronized after the adding device 203 adds the first ID
According to.
In the embodiment of the present invention, the determination unit 201 is specific to determine data to be synchronized in the following way：
Determine database journal, the database journal includes newer data occur and newer data occur
Renewal time；
According to the renewal time that newer data occur in the database journal, the newer data of generation are created
Timestamp；
Newer data and the timestamp that newer data occur occurs by described, is determined as data to be synchronized.
In the embodiment of the present invention, the data to be synchronized for including the first ID are sent to same step number by data sending terminal to be synchronized
According to receiving terminal, data receiver to be synchronized in determining the 2nd ID set in the case where being not present the first ID, described in write-in
Data to be synchronized.By the way that the to be synchronized data different from the ID of successful synchronization data are written, avoid and be repeatedly written ID phases
Same data to be synchronized, that is, avoid repetition and synchronize identical data to be synchronized, solve the number between multiple data centers
It is to be synchronized due to repeating to synchronize according to stationary problem, and during avoiding and carrying out data synchronization updating between multiple data centers
The problem of reliability of data update caused by data is relatively low.
Obviously, various changes and modifications can be made to the invention without departing from essence of the invention by those skilled in the art
God and range.In this way, if these modifications and changes of the present invention belongs to the range of the claims in the present invention and its equivalent technologies
Within, then the present invention is also intended to include these modifications and variations.
Claims (10)
1. a kind of method of data synchronization, which is characterized in that including：
Data to be synchronized are obtained, are included in the data to be synchronized for the first identity of data to be synchronized described in unique mark
Identify ID；
It is same to determine that the ID in gathering in the 2nd ID set there is no the first ID, the 2nd ID is successfully completed for mark
The data of step；
The data to be synchronized are written.
2. the method as described in claim 1, which is characterized in that having time stamp is further included in the data to be synchronized；
It is described to determine that the method further includes there is no after the first ID in the 2nd ID set：
Determine that the timestamp that the data to be synchronized include characterizes the time, the timestamp included with initial data is characterized
The sequencing of time；
The initial data is the data with existing before data to be synchronized are written；
According to preset synchronization policy and the sequencing, it is the data to be synchronized that determining, which needs synchronous data,；
First ID is added in the 2nd ID set；
Wherein, the preset synchronization policy, which is used to indicate, selects that timestamp characterizes that the time is first or posterior data are as needing
The data to be synchronized.
3. method as claimed in claim 2, which is characterized in that the method further includes：
If according to preset synchronization policy and the sequencing, it is not the number to be synchronized that determining, which needs synchronous data,
According to then will be in the data to be synchronized storage to data collision set.
4. a kind of method of data synchronization, which is characterized in that including：
Determine data to be synchronized；
Create the first identity ID for data to be synchronized described in unique mark；
First ID is added to the data to be synchronized；
Send the data to be synchronized added with the first ID.
5. method as claimed in claim 4, which is characterized in that it is described to determine data to be synchronized, including：
Determine database journal, the database journal includes newer data occur and the update of newer data occurs
Time；
According to the renewal time that newer data occur in the database journal, the time that newer data occur is created
Stamp；
Newer data and the timestamp that newer data occur occurs by described, is determined as data to be synchronized.
6. a kind of data synchronization unit, which is characterized in that including：
Acquiring unit for obtaining data to be synchronized, includes in the data to be synchronized for be synchronized described in unique mark
First identity ID of data；
Processing unit, for determining what is included in the 2nd ID set there is no the data to be synchronized that the acquiring unit obtains
First ID, wherein, the ID in the 2nd ID set is successfully completed synchronous data for identifying；
Synchronization unit, for there is no treated described in acquiring unit acquisition in the processing unit determines that the 2nd ID gathers
In the case of the first ID that synchrodata includes, the data to be synchronized that the acquiring unit obtains are written.
7. device as claimed in claim 6, which is characterized in that also wrapped in the data to be synchronized that the acquiring unit obtains
Include having time stamp；
The processing unit is additionally operable to：
There is no after the first ID in the 2nd ID set is determined, the timestamp institute that the data to be synchronized include is determined
Characterize time, the sequencing for the time that the timestamp included with initial data is characterized；
The initial data is the data with existing before data to be synchronized are written；
According to preset synchronization policy and the sequencing, it is the data to be synchronized that determining, which needs synchronous data,；
First ID is added in the 2nd ID set；
Wherein, the preset synchronization policy, which is used to indicate, selects that timestamp characterizes that the time is first or posterior data are as needing
The data to be synchronized.
8. device as claimed in claim 7, which is characterized in that the processing unit is additionally operable to：
If according to preset synchronization policy and the sequencing, it is not the number to be synchronized that determining, which needs synchronous data,
According to then will be in the data to be synchronized storage to data collision set.
9. a kind of data synchronization unit, which is characterized in that including：
Determination unit, for determining data to be synchronized；
Creating unit, for creating the first identity mark of the data to be synchronized determined for determination unit described in unique mark
Know ID；
The first ID that the creating unit creates is added to the data to be synchronized by adding device；
Transmitting element, for sending the data to be synchronized after the adding device adds the first ID.
10. device as claimed in claim 9, which is characterized in that the determination unit determines number to be synchronized in the following way
According to：
Determine database journal, the database journal includes newer data occur and the update of newer data occurs
Time；
According to the renewal time that newer data occur in the database journal, the time that newer data occur is created
Stamp；
Newer data and the timestamp that newer data occur occurs by described, is determined as data to be synchronized.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611209618.4A CN108243208A (en) | 2016-12-23 | 2016-12-23 | A kind of method of data synchronization and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611209618.4A CN108243208A (en) | 2016-12-23 | 2016-12-23 | A kind of method of data synchronization and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108243208A true CN108243208A (en) | 2018-07-03 |
Family
ID=62704472
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611209618.4A Pending CN108243208A (en) | 2016-12-23 | 2016-12-23 | A kind of method of data synchronization and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108243208A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558458A (en) * | 2018-12-30 | 2019-04-02 | 贝壳技术有限公司 | Method of data synchronization, configuration platform, transaction platform and data synchronous system |
| CN113259470A (en) * | 2021-06-03 | 2021-08-13 | 长视科技股份有限公司 | Data synchronization method and data synchronization system |
| WO2023246316A1 (en) * | 2022-06-24 | 2023-12-28 | 中兴通讯股份有限公司 | Information processing method and apparatus, storage medium and program product |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101127640A (en) * | 2007-09-10 | 2008-02-20 | 中兴通讯股份有限公司 | A method for improving data synchronization efficiency via the incremental mode |
| CN102098342A (en) * | 2011-01-31 | 2011-06-15 | 华为技术有限公司 | Transaction level-based data synchronizing method, device thereof and system thereof |
| CN103139259A (en) * | 2011-11-30 | 2013-06-05 | 百度在线网络技术（北京）有限公司 | Method and server of achieving low-flux synchronous message logging |
| CN103678494A (en) * | 2013-11-15 | 2014-03-26 | 北京奇虎科技有限公司 | Method and device for client side and server side data synchronization |
| CN104580522A (en) * | 2015-01-30 | 2015-04-29 | 宁波凯智信息科技有限公司 | Client-server data synchronization method and system |
| CN104598610A (en) * | 2015-01-29 | 2015-05-06 | 无锡江南计算技术研究所 | Step-by-step database data distribution uploading and synchronizing method |
| US20160088082A1 (en) * | 2014-09-19 | 2016-03-24 | Netapp, Inc. | Techniques for coordinating parallel performance and cancellation of commands in a storage cluster system |
| CN106254094A (en) * | 2016-07-19 | 2016-12-21 | 中国银联股份有限公司 | A kind of method of data synchronization and system |
-
2016
- 2016-12-23 CN CN201611209618.4A patent/CN108243208A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101127640A (en) * | 2007-09-10 | 2008-02-20 | 中兴通讯股份有限公司 | A method for improving data synchronization efficiency via the incremental mode |
| CN102098342A (en) * | 2011-01-31 | 2011-06-15 | 华为技术有限公司 | Transaction level-based data synchronizing method, device thereof and system thereof |
| CN103139259A (en) * | 2011-11-30 | 2013-06-05 | 百度在线网络技术（北京）有限公司 | Method and server of achieving low-flux synchronous message logging |
| CN103678494A (en) * | 2013-11-15 | 2014-03-26 | 北京奇虎科技有限公司 | Method and device for client side and server side data synchronization |
| US20160088082A1 (en) * | 2014-09-19 | 2016-03-24 | Netapp, Inc. | Techniques for coordinating parallel performance and cancellation of commands in a storage cluster system |
| CN104598610A (en) * | 2015-01-29 | 2015-05-06 | 无锡江南计算技术研究所 | Step-by-step database data distribution uploading and synchronizing method |
| CN104580522A (en) * | 2015-01-30 | 2015-04-29 | 宁波凯智信息科技有限公司 | Client-server data synchronization method and system |
| CN106254094A (en) * | 2016-07-19 | 2016-12-21 | 中国银联股份有限公司 | A kind of method of data synchronization and system |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558458A (en) * | 2018-12-30 | 2019-04-02 | 贝壳技术有限公司 | Method of data synchronization, configuration platform, transaction platform and data synchronous system |
| CN109558458B (en) * | 2018-12-30 | 2021-08-03 | 贝壳找房(北京)科技有限公司 | Data synchronization method, configuration platform, transaction platform and data synchronization system |
| CN113259470A (en) * | 2021-06-03 | 2021-08-13 | 长视科技股份有限公司 | Data synchronization method and data synchronization system |
| WO2023246316A1 (en) * | 2022-06-24 | 2023-12-28 | 中兴通讯股份有限公司 | Information processing method and apparatus, storage medium and program product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107295080B (en) | Data storage method applied to distributed server cluster and server | |
| CN103207867B (en) | It handles the method for data block, initiate the method and node of recovery operation | |
| CN103530362B (en) | A kind of computer data reading/writing method for many copies distributed system | |
| CN107919971B (en) | Method, apparatus and system for audio/video communication connection disaster tolerance | |
| CN105930121B (en) | The person's handwriting synchronous method and system of multi-client | |
| US10021182B2 (en) | Method and apparatus for data synchronization | |
| CN106411629B (en) | Method and equipment for monitoring state of CDN node | |
| CN108243208A (en) | A kind of method of data synchronization and device | |
| CN104168335B (en) | A kind of method of data synchronization and device | |
| US9762667B2 (en) | Distributed server election with imperfect clock synchronization | |
| CN111193792A (en) | Message transmission method and device, electronic equipment and storage medium | |
| CN105959078A (en) | Cluster time synchronization method, cluster and time synchronization system | |
| CN103780621B (en) | A kind of remote table sharing method and system | |
| CN105812492B (en) | A kind of method of data synchronization and system | |
| CN105339906B (en) | The method for controlling the data write-in to permanent storage appliance | |
| US20130120652A1 (en) | Method and apparatus for evaluating time delay of mobile video service | |
| EP2690560A2 (en) | Method of benchmarking the behaviour of a replacement information system with the old system | |
| CN106992905A (en) | Long-distance service method and system after network link failure | |
| CN106055494A (en) | Data aggregator and data management method | |
| CN113259989B (en) | Data retransmission method and device and electronic equipment | |
| CN109257403A (en) | Date storage method and equipment, distributed memory system | |
| CN107707590A (en) | System, the method and device of data transfer | |
| US10514850B2 (en) | Information processing system, server device, Information processing method, and computer program product | |
| CN108628901A (en) | A kind of data-updating method and device | |
| CN114020503A (en) | Optimization method, system and device for transparent fault switching of distributed file system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20180703 |
|
| WD01 | Invention patent application deemed withdrawn after publication |