CN100592298C - File synchronisation method and device - Google Patents
File synchronisation method and device Download PDFInfo
- Publication number
- CN100592298C CN100592298C CN200810098124A CN200810098124A CN100592298C CN 100592298 C CN100592298 C CN 100592298C CN 200810098124 A CN200810098124 A CN 200810098124A CN 200810098124 A CN200810098124 A CN 200810098124A CN 100592298 C CN100592298 C CN 100592298C
- Authority
- CN
- China
- Prior art keywords
- file
- event queue
- change events
- untreated
- incident
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a data simultaneous technique, discloses a file synchronous method, which comprises: monitoring a file directory, and recording the change event of a change when a file in thefile directory changes; determining files to be synchronized; and synchronizing the files to be synchronized to an objective computer. The invention also discloses a file synchronous device, comprising a monitoring unit, a record unit, an analytical unit and a synchronous unit. By using the invention, the real-time performance and reliability of file synchronization can be ensured.
Description
Technical field
The present invention relates to data synchronization technology, be specifically related to a kind of file synchronisation method and device.
Background technology
In the multiple applied environment of information processing, data sync all has demand widely.Along with the raising of IT application in enterprises degree, consider the safety of data, the file synchronization on the main frame need be backed up to other main frame; In distributed system, essence data files need be synchronized on each main frame that is in the distributed system.The key that satisfies synchronisation requirement is to solve following point: to real-time, reliability, the high efficiency of file synchronization, to guarantee the safe and reliable of data.
At present file synchronization is adopted regularly synchronously usually, mainly contains following dual mode:
1, regularly needs synchronous catalogue to carry out full scan one time, each file that scans is arrived the purpose machine verify, whether be newly-increased or made modification to determine this document, if, then file synchronization is arrived the purpose machine for increasing or made modification newly to the source machine.
2, timing needs synchronous catalogue carry out full scan one time to the source machine, and the file after each scanning is carried out synchronous operation earlier, then this machine backup directory is arrived in the file conversion after synchronous.During each later on scanning, all be to handle newly-increased file.
Above-mentioned these two kinds equal deleted files synchronously of the methods of synchronization regularly; And, can not accomplish in real time that synchronously reliability is relatively poor.
Summary of the invention
The embodiment of the invention provides a kind of file synchronisation method and device, to guarantee the real-time and the reliability of file synchronization.
A kind of file synchronisation method that the embodiment of the invention provides comprises:
The monitoring file directory when file in monitoring described file directory changes, records event queue with the change events of this variation; If described event queue is full or the incident file that is untreated, then described change events is write the described incident file that is untreated;
When described event queue is non-NULL, resolve the change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described event queue; After described event queue is sky, change events in the described incident file that is untreated is loaded into described event queue, and resolve change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described incident file that is untreated;
The file synchronization that described needs are synchronous is to the purpose machine.
A kind of file synchronization device that the embodiment of the invention provides comprises:
Monitoring unit is used to monitor file directory;
Record cell is used for when file that described monitoring unit monitors described file directory changes, and the change events of this variation is recorded event queue; If described event queue is full or the incident file that is untreated, then described change events is write the described incident file that is untreated;
Resolution unit is used for determining the file that needs are synchronous according to the change events of described recording unit records; When described event queue is non-NULL, resolve the change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described event queue; After described event queue is sky, change events in the described incident file that is untreated is loaded into described event queue, and resolve change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described incident file that is untreated;
Lock unit is used for the file synchronization that described needs are synchronous to the purpose machine.The technical scheme that provides by the above embodiment of the invention as can be seen, the embodiment of the invention is monitored file directory in real time by monitor mode, when having monitored file when changing, the record change events; Determine the file that needs are synchronous according to described change events; The file synchronization that described needs are synchronous is to the purpose machine.Therefore, the file that changes can be synchronized on the purpose machine immediately, guarantee the real-time and the reliability of file synchronization.
Description of drawings
Fig. 1 is the realization flow figure of a kind of embodiment of file synchronisation method of the present invention;
Fig. 2 is the realization flow figure of record change events among the inventive method embodiment;
Fig. 3 is the realization flow figure that resolves change events among the inventive method embodiment;
Fig. 4 is the process flow diagram that carries out file directory scanning in the embodiment of the invention;
Fig. 5 is the sequential chart of the another kind of embodiment of file synchronisation method of the present invention;
Fig. 6 is the structured flowchart of embodiment of the invention file synchronization device.
Embodiment
In order to make those skilled in the art person understand the scheme of the embodiment of the invention better, the embodiment of the invention is described in further detail below in conjunction with drawings and embodiments.
In order to guarantee the real-time of file synchronization, the file that changes can be synchronized on the purpose machine immediately, and the embodiment of the invention adopts real-time monitor mode, when having monitored file when changing, write down change events, and determine the file that needs are synchronous according to described change events.
As shown in Figure 1, be the realization flow of a kind of embodiment of file synchronisation method of the present invention, mainly may further comprise the steps:
In the present embodiment, can utilize the interface of operating system, adopt the file change event notification mechanism, monitor the variation of file in the file directory in real time.Such as, under (SuSE) Linux OS, the INOTIFY file change monitoring mechanism that can use operating system to provide is monitored the file change in the file directory in real time; Under Windows operating system, can utilize system interface ReadDirectoryChangesW, monitor the file change in the file directory in real time.Because the use of operating system interface, the very first time after can the file modification in catalogue obtains the file change notice, thus can realize mass file synchronously in real time.In the example of the present invention, also can adopt the variation of file in other means or the self-defining means monitoring file directory.
In embodiments of the present invention, in order to guarantee the reliability of file synchronization, the change events that file can be changed is write the formation of appointment, such as event queue, when change events is too many, and, also change events can be write the incident file that is untreated as behind the queue full, do not lost to guarantee described change events.
When the existing incident file that is untreated is untreated, when also having the operating system notification event to take place, can handle the already present incident file that is untreated earlier, notification event is continued to write this incident file that is untreated, thereby the order that guarantees the file synchronization operation is carried out.To be described in detail in the back this.
Correspondingly, can at first from described event queue, read change events, this change events is resolved, need determine synchronous file.If described event queue is empty, the incident file that then will be untreated reads in described event queue, then, reads change events from described event queue, and this change events is resolved, and need to determine synchronous file.
The means of carrying out file synchronization can have multiple, and for example FTP (File Transfer Protocol, file transfer protocol (FTP)) transmission mode or utilize the socket mode realizes the transmission of synchronous documents.
As seen, the embodiment of the invention writes down the change events that the file in the described file directory changes by the monitoring file directory, such as adopting operating system file change notification mechanism, can guarantee synchronous carrying out in real time, write the incident file mode, can guarantee synchronous reliability.
Flow process to record change events in the embodiment of the invention and parsing change events is elaborated below.
In embodiments of the present invention, described change events can be recorded event queue, if described event queue is full or the incident file that is untreated, then described change events can be write the described incident file that is untreated, the described incident file that is untreated can have one or more, can not lose to guarantee all changes incident.Be untreated during incident file as a plurality of, can rank to the incident file that respectively is untreated, can access preferential synchronous processing to guarantee the file that changes earlier by document queue.
As shown in Figure 2, be the realization flow of record change events in the embodiment of the invention, mainly may further comprise the steps:
Step 201 utilizes operating system interface to obtain the file change incident.
Such as, under (SuSE) Linux OS, the INOTIFY file change monitoring mechanism that uses operating system to provide obtains the file change incident; Under Windows operating system, utilize system interface ReadDirectoryChangesW, obtain the file change incident.
Step 202, the incident file that judged whether to be untreated exists; If then execution in step 203; Otherwise, execution in step 205.
Step 203 judges whether not write the full incident file that is untreated; If then execution in step 204; Otherwise, execution in step 207.
Step 204 writes the incident file that is untreated with change events, and this flow process finishes.
Step 205, whether the decision event formation is full; If then execution in step 203; Otherwise, execution in step 206.
Step 206, with the formation of change events writing events, this flow process finishes.
Step 207, the newly-built incident file that is untreated, and this incident file name that is untreated put into document queue.This flow process finishes.
Correspondingly, when the processing variation incident, promptly resolve when change events is definite to need synchronous file, can carry out according to following process: when event queue is non-NULL, resolve the change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described event queue; After event queue is sky, the change events in the incident file that is untreated is loaded into event queue, and resolves the change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described incident file that is untreated; After change events in the described incident file that is untreated is loaded into described event queue, delete the described incident file that is untreated.
Need to prove, be untreated during incident file, can load the incident file that respectively is untreated successively to described event queue, can access preferential synchronous processing to guarantee the file that changes earlier according to the order in the document queue as a plurality of.
As shown in Figure 3, be the realization flow of resolving change events in the embodiment of the invention, mainly may further comprise the steps:
Utilize the mode of record change events shown in Figure 2 and the mode of parsing change events shown in Figure 3, can guarantee real-time property of synchronizing and reliability.
In order further to improve synchronous high efficiency, can also when the startup file synchronous task, carry out directory scan (as full directory scan) to the source machine, obtain the modification time of file in the described catalogue; If described file modifying time ratio record last time file synchronization supervision time new, then with described file synchronization to the purpose machine; Described file synchronization behind the purpose machine, is write down the checkpoint time of this file synchronization.
In addition, can also scan file directory for the first time, and when not having pending change events, the status information of record catalogue this moment is to the checkpoint message file, and after this setting is a checkpoint every certain hour, when arriving the checkpoint and not having pending being untreated during incident file, upgrade the checkpoint message file.According to the directory state information that in checkpoint message file write down determine the operation of each file this catalogue under when scanning next time, thereby determine whether this document needs synchronously.The use of checkpoint message file can be accelerated the speed of follow up scan file directory, reduces network interaction, thereby guarantees the efficient operation of file directory scanning.
As shown in Figure 4, be the process flow diagram that carries out file directory scanning in the embodiment of the invention, mainly may further comprise the steps:
Step 401 judges whether the checkpoint message file exists; If then execution in step 402; Otherwise, execution in step 403;
Step 402 reads the checkpoint message file, to obtain nearest checkpoint information; Execution in step 404 then;
Step 405 judges whether stack is empty; If then execution in step 406; Otherwise, execution in step 407;
Step 406 finishes scanning process, and this flow process finishes.
Step 407 ejects stack top element, as current file directory to be scanned;
Step 408 is opened file directory to be scanned;
Step 409 judges whether file is arranged under this document catalogue; If then execution in step 410; Otherwise, execution in step 405;
Step 410 is obtained a file under this document catalogue;
Step 411 judges whether this document is catalogue; If then execution in step 412; Otherwise, execution in step 413;
Step 413 compares fileinfo and checkpoint information, and whether decision needs to carry out file synchronization; If then execution in step 414; Otherwise, execution in step 409;
Step 414 is carried out file synchronization, and this flow process finishes.
Utilize this scanning flow process, can further guarantee the reliability of file synchronization.
When using operating system interface monitoring file directory, if be used for that the synchronization program of execute file synchronous task breaks down (when operation termination that takes place such as program exception or program restart) or by the people for stopping, the file change incident that produces so just catch less than, cause losing of change events.For addressing this problem, further guarantee synchronous reliability, can when restarting synchronization program, carry out directory scan (as full directory scan), to guarantee the file change after obtain synchronization program stops to the source machine.
That is to say, in the embodiment of the invention, can be when the startup file synchronous task, start directory scan thread and catalogue monitoring thread simultaneously, the directory scan thread guarantee the catalogue monitoring thread break down or stop after change information obtain synchronously, the real-time file change information of catalogue monitoring thread assurance obtains synchronously.Design can guarantee the real-time and the reliability of file synchronization better like this.
As shown in Figure 5, be the sequential chart of another kind of embodiment of the invention file synchronisation method, may further comprise the steps:
Step 501 starts the scanning thread when the startup file synchronous task;
Step 502 starts monitoring thread;
Step 503, whether the scanning document catalogue has file to change to check;
Step 504 if there is file to change, then changes file synchronously;
Step 505 is monitored file directory in real time;
Step 506, monitor change events after, described change events is recorded event queue;
Step 507 if event queue is full or the incident file that is untreated, then writes change events the described incident file that is untreated;
Step 508 reads the change events in the event queue, need to determine synchronous file;
Step 509 if the event queue sky then reads the change events in the incident file that is untreated, needs synchronous file;
Certainly, as previously described, reading when being untreated incident file, if a plurality of incident files that are untreated are arranged, can read successively according to the order in the document queue, and the change events in the incident file that will be untreated is loaded into event queue, resolves the change events in the described event queue then successively, needs synchronous file in the change events of determining to write down in the described incident file that is untreated.In addition, after the change events in the described incident file that is untreated is loaded into described event queue, also need to delete this incident file that is untreated.
Step 510, with the file synchronization that changes to the purpose machine.
Need to prove that in embodiments of the present invention, the described event queue of incident file in synchronized process that be untreated produces when full, when the new change events that produces is not handled at the existing incident file that is untreated, continues to write this incident file that is untreated.After this incident file that is untreated is loaded into event queue, delete this incident file that is untreated.When synchronized process has just started, need the existing incident file that is untreated of deletion, delete the incident file that is untreated when synchronized process normally withdraws from, the change events in this incident file that is untreated can be finished by the scan procedure after synchronization program starts next time.
Synchronized process can have a plurality of incident files that are untreated, and handles for convenience, and it is identical to set the change events bar number that writes down in each incident file that is untreated, and equals the size of event queue in the synchronized process.The size of event queue can be specified when synchronization program starts.
Can comprise following information in the described incident file: the mode of operation of filename, file, file type etc., concrete form can be as shown in table 1 below:
Table 1
Mention in the above, can scan file directory, and when not having pending change events, the record status information of catalogue at this moment arrives the checkpoint message file for the first time.According to the directory state information that in checkpoint message file write down determine the operation of each file this catalogue under when scanning next time, thereby determine whether this document needs synchronously.
Need to prove that single synchronized process has only a checkpoint message file, this checkpoint message file is set up in the time of can not finding in default path when synchronized process starts.
The information and the form that comprise in the message file of described checkpoint can be as shown in table 2 below:
Table 2
Checkpoint information can regularly be upgraded, and after timing arrives, if directory scan finishes, and when not having pending incident, upgrades described checkpoint information.
In the message file of checkpoint, can keep the historical checkpoint information of respective number according to the appointment of user when starting synchronized process.The user can specify which the checkpoint information of use when starting synchronized process.If the checkpoint information number that needs to keep is N, up-to-date checkpoint information position hereof is P (P is since 0 counting), checkpoint information take up space is the M byte, suppose that checkpoint message file sign accounts for the LA byte, need to keep checkpoint information number and account for the LB byte, information position hereof, up-to-date checkpoint accounts for the LC byte.
When synchronized process started, if do not specify which the checkpoint information of use, the position LOC1 of the checkpoint information that then will read was:
LOC1=LA+LB+LC+P*M (formula 1)
The position LOC2 that writes down next checkpoint information is:
LOC2=LA+LB+LC+ ((P+1) %N) * M (formula 2)
Obtain old checkpoint information according to LOC1, carry out file scan.According to LOC2 new checkpoint information is set, if LOC2 has had checkpoint information, old information will be capped.
When new checkpoint information was set, the position that needs to revise up-to-date checkpoint information was:
P＝(P+1)％N。
Use i checkpoint if specify, then the position of checkpoint information is:
LOC3＝LA+LB+LC+(P+i)％N。
Utilize the file synchronisation method of the embodiment of the invention, can guarantee the real-time, reliable and efficient of file synchronization.
Need to prove, one of ordinary skill in the art will appreciate that all or part of step that realizes in the foregoing description method is to instruct relevant hardware to finish by program, described program can be stored in the computer read/write memory medium, described storage medium, as: ROM/RAM, magnetic disc, CD etc.
The embodiment of the invention also provides a kind of file synchronization device, as shown in Figure 6, it is the structured flowchart of this document synchronous device, mainly comprise monitoring unit 61, record cell 62, resolution unit 63 and lock unit 64, reliability for further file synchronization can also comprise scanning element 65, comparing unit 66 and checkpoint time updating block 67.Wherein:
Monitoring unit 61 is used to monitor file directory; Record cell 62 is used for having monitored file when changing when monitoring unit 61, writes down the change events of this variation; Resolution unit 63 is used for determining the file that needs are synchronous according to the change events of record cell 62 records; Lock unit 64 is used for the file synchronization that described needs are synchronous to the purpose machine.Scanning element 65 is used for when the startup file synchronous task source machine being carried out directory scan, obtains the modification time of file in the described catalogue; Comparing unit 65 be used for more described file modifying time and record last time file synchronization the checkpoint time, if described file modifying time ratio record last time file synchronization the checkpoint time new, then notify lock unit 64 with described file synchronization to the purpose machine; Checkpoint time updating block 66 be used for comparing unit 65 with described file synchronization behind the purpose machine, write down the checkpoint time of this file synchronization.
Wherein, record cell 62 can comprise following subelement (not shown): the write queue subelement is used for described change events is recorded event queue; The written document subelement is used for when described event queue has expired or has been untreated incident file described change events being write the described incident file that is untreated.
Correspondingly, resolution unit 63 can comprise following subelement (not shown): subelement is resolved in formation, be used for when described event queue is non-NULL, resolving the change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described event queue; The document analysis subelement, be used for after described event queue is sky, change events in the described incident file that is untreated is loaded into described event queue, and resolve change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described incident file that is untreated; The file delete subelement is used for deleting the described incident file that is untreated after the change events of the described incident file that is untreated is loaded into described event queue.
Utilize the device of the embodiment of the invention to realize that the detailed process and the front of file synchronization are similar to the description in the inventive method, do not repeat them here.
More than the embodiment of the invention is described in detail, used embodiment herein the present invention set forth, the explanation of above embodiment just is used for help understanding device and method of the present invention; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, the part that all can change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention.
Claims (8)
1, a kind of file synchronisation method is characterized in that, comprising:
The monitoring file directory when file in monitoring described file directory changes, records event queue with the change events of this variation; If described event queue is full or the incident file that is untreated, then described change events is write the described incident file that is untreated;
When described event queue is non-NULL, resolve the change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described event queue; After described event queue is sky, change events in the described incident file that is untreated is loaded into described event queue, and resolve change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described incident file that is untreated;
The file synchronization that described needs are synchronous is to the purpose machine.
2, method according to claim 1 is characterized in that, described method also comprises:
When the startup file synchronous task, the source machine is carried out directory scan, obtain the modification time of file in the described catalogue;
If described file modifying time ratio record last time file synchronization supervision time new, then with described file synchronization to the purpose machine;
Described file synchronization behind the purpose machine, is write down the checkpoint time of this file synchronization.
3, method according to claim 1 and 2 is characterized in that, described method also comprises:
After change events in the described incident file that is untreated is loaded into described event queue, delete the described incident file that is untreated.
4, method according to claim 1 is characterized in that, describedly will need synchronous file synchronization to comprise to the purpose machine:
Utilize file transfer protocol (FTP) or socket mode will need synchronous file synchronization to the purpose machine.
5, method according to claim 1 is characterized in that, utilizes the file change event notification mechanism of operating system to monitor described file directory in real time.
6, a kind of file synchronization device is characterized in that, comprising:
Monitoring unit is used to monitor file directory;
Record cell is used for when file that described monitoring unit monitors described file directory changes, and the change events of this variation is recorded event queue; If described event queue is full or the incident file that is untreated, then described change events is write the described incident file that is untreated; Resolution unit is used for determining the file that needs are synchronous according to the change events of described recording unit records; When described event queue is non-NULL, resolve the change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described event queue; After described event queue is sky, change events in the described incident file that is untreated is loaded into described event queue, and resolve change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described incident file that is untreated;
Lock unit is used for the file synchronization that described needs are synchronous to the purpose machine.
7, device according to claim 6 is characterized in that, also comprises:
Scanning element is used for when the startup file synchronous task source machine being carried out directory scan, obtains the modification time of file in the described catalogue;
Comparing unit, be used for more described file modifying time and record last time file synchronization the checkpoint time, if described file modifying time ratio record last time file synchronization the checkpoint time new, then notify described lock unit with described file synchronization to the purpose machine;
Checkpoint time updating block, be used for described comparing unit with described file synchronization behind the purpose machine, write down the checkpoint time of this file synchronization.
8, according to claim 6 or 7 described devices, it is characterized in that described resolution unit comprises:
Subelement is resolved in formation, is used for resolving the change events in the described event queue successively when described event queue is non-NULL, needs synchronous file in the change events of determining to write down in the described event queue;
The document analysis subelement, be used for after described event queue is sky, change events in the described incident file that is untreated is loaded into described event queue, and resolve change events in the described event queue successively, need synchronous file in the change events of determining to write down in the described incident file that is untreated;
Described resolution unit also comprises:
The file delete subelement is used for deleting the described incident file that is untreated after the change events of the described incident file that is untreated is loaded into described event queue.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810098124A CN100592298C (en) | 2008-05-13 | 2008-05-13 | File synchronisation method and device |
| PCT/CN2008/073693 WO2009137977A1 (en) | 2008-05-13 | 2008-12-24 | File synchronization method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810098124A CN100592298C (en) | 2008-05-13 | 2008-05-13 | File synchronisation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101281543A CN101281543A (en) | 2008-10-08 |
| CN100592298C true CN100592298C (en) | 2010-02-24 |
Family
ID=40014011
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810098124A Active CN100592298C (en) | 2008-05-13 | 2008-05-13 | File synchronisation method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN100592298C (en) |
| WO (1) | WO2009137977A1 (en) |
Families Citing this family (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100592298C (en) * | 2008-05-13 | 2010-02-24 | 华为技术有限公司 | File synchronisation method and device |
| CN102567341B (en) * | 2010-12-09 | 2016-02-17 | 腾讯科技（深圳）有限公司 | A kind of method and system realizing Directory Synchronization inside and outside software |
| CN102739706A (en) * | 2011-04-07 | 2012-10-17 | 腾讯科技（深圳）有限公司 | Method and system for carrying out data synchronization |
| CN102609532B (en) * | 2012-02-15 | 2014-07-23 | 大唐移动通信设备有限公司 | Method and device for monitoring file directory |
| CN102915338A (en) * | 2012-09-18 | 2013-02-06 | 浪潮(北京)电子信息产业有限公司 | Data synchronization method of distributed file systems and file systems |
| CN103258018B (en) * | 2013-04-27 | 2016-08-10 | 北京金和软件股份有限公司 | The file synchronisation method of file change in a kind of accurate monitored directory file |
| CN105577841B (en) * | 2013-07-12 | 2018-11-16 | 北京金山云网络技术有限公司 | A kind of method, apparatus of file synchronization, client, server end and equipment |
| CN103336925B (en) * | 2013-07-29 | 2016-10-05 | 腾讯科技（深圳）有限公司 | A kind of method and apparatus scanning acceleration |
| CN104348859B (en) * | 2013-07-30 | 2019-05-07 | 深圳市腾讯计算机系统有限公司 | File synchronisation method, device, server, terminal and system |
| CN106850818B (en) * | 2013-11-08 | 2020-02-18 | 北京奇虎科技有限公司 | Data real-time synchronization method and system |
| CN103747029A (en) * | 2013-12-10 | 2014-04-23 | 北京奇虎科技有限公司 | File transmission method, device and system |
| CN103902663A (en) * | 2014-03-10 | 2014-07-02 | 联想(北京)有限公司 | File synchronization method and device |
| CN104133739B (en) * | 2014-07-28 | 2017-09-05 | 珠海市君天电子科技有限公司 | A kind of method and device of automated back-up file |
| CN104994177B (en) * | 2015-08-06 | 2019-01-25 | 上海爱数信息技术股份有限公司 | Synchronous method, terminal device and the Dropbox system of Dropbox system |
| CN105426386A (en) * | 2015-10-23 | 2016-03-23 | 小米科技有限责任公司 | File synchronization method and apparatus, and terminal device |
| CN106610996B (en) * | 2015-10-23 | 2022-03-11 | 北京奇虎科技有限公司 | Hot dictionary switching method and device |
| CN106372526B (en) * | 2016-08-19 | 2019-08-02 | 上海爱数信息技术股份有限公司 | A kind of monitoring file change and synchronous method and system |
| CN106572280B (en) * | 2016-10-12 | 2019-09-06 | 曙光信息产业(北京)有限公司 | Scan the method and system of file |
| CN109446170B (en) * | 2018-09-13 | 2024-01-19 | 北京米文动力科技有限公司 | Configuration file data synchronization method and device |
| CN109783463A (en) * | 2018-12-13 | 2019-05-21 | 杭州数梦工场科技有限公司 | File synchronisation method, device and computer readable storage medium |
| CN111488317A (en) * | 2020-04-16 | 2020-08-04 | 北京雷石天地电子技术有限公司 | File synchronization method and device based on file change content |
| CN111488318A (en) * | 2020-04-16 | 2020-08-04 | 北京雷石天地电子技术有限公司 | File synchronization method and device based on multistage feedback queue |
| CN111651414A (en) * | 2020-04-17 | 2020-09-11 | 福建天泉教育科技有限公司 | Method for monitoring document opening and storage medium |
| CN111526198B (en) * | 2020-04-24 | 2023-06-13 | 深圳融安网络科技有限公司 | Data synchronization method and device of server and computer readable storage medium |
| CN114185749A (en) * | 2021-12-15 | 2022-03-15 | 南京欧珀软件科技有限公司 | Monitoring method and device and electronic equipment |
| CN117009309A (en) * | 2023-05-31 | 2023-11-07 | 合芯科技(苏州)有限公司 | File real-time synchronization method and device based on rsync |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7363330B1 (en) * | 1999-06-07 | 2008-04-22 | Symantec Corporation | Work monitor with file synchronization |
| CN1197013C (en) * | 2001-02-02 | 2005-04-13 | 英业达股份有限公司 | Fault-tolerant method by means of synchronous directory |
| CN1249597C (en) * | 2002-09-03 | 2006-04-05 | 鸿富锦精密工业（深圳）有限公司 | Synchronous system in distributed files and method |
| CN100592298C (en) * | 2008-05-13 | 2010-02-24 | 华为技术有限公司 | File synchronisation method and device |
-
2008
- 2008-05-13 CN CN200810098124A patent/CN100592298C/en active Active
- 2008-12-24 WO PCT/CN2008/073693 patent/WO2009137977A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| WO2009137977A1 (en) | 2009-11-19 |
| CN101281543A (en) | 2008-10-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100592298C (en) | File synchronisation method and device | |
| US6981177B2 (en) | Method and system for disaster recovery | |
| US8370304B2 (en) | Restore of full system backup and incremental backups using multiple simultaneous device streams | |
| US20030208511A1 (en) | Database replication system | |
| US7437601B1 (en) | Method and system for re-synchronizing an asynchronous mirror without data loss | |
| US6728735B1 (en) | Restartable dump that produces a consistent filesystem on tapes | |
| WO2018049983A1 (en) | Data synchronization method and system, and synchronization acquisition method and device | |
| JP4224126B1 (en) | Database management server device, database management system, database management method, and database management program | |
| JP5647624B2 (en) | Multi-server application synchronization method, program, and system without interrupting I / O | |
| WO2014059804A1 (en) | Method and system for data synchronization | |
| WO2015101084A1 (en) | Method, server and system for data recovery | |
| WO2008119292A1 (en) | Method, device and system for realizing backup of stored data | |
| US20110282843A1 (en) | Method and system for data backup and replication | |
| CN110188000A (en) | Application disaster recovery method and system based on virtualization and iSCSI or FC | |
| JP2003536157A (en) | Data storage systems and processes | |
| CN105159795A (en) | Data synchronization method, apparatus and system | |
| CN105376277A (en) | Data synchronization method and device | |
| US20120278429A1 (en) | Cluster system, synchronization controlling method, server, and synchronization controlling program | |
| US20220335011A1 (en) | System and Method for Eliminating Full Rescan Synchronizations on Service Restarts | |
| CN110187998A (en) | The application disaster tolerance system and method stored based on virtual platform and ceph | |
| CN110188068A (en) | A kind of volume grade backup method and device guaranteeing file system data consistency | |
| CN101216794A (en) | Improved Server-Less backup method, memory apparatus and backup server | |
| US10671567B2 (en) | System and method for optimized lock detection | |
| US9817834B1 (en) | Techniques for performing an incremental backup | |
| US20090132534A1 (en) | Remote replication synchronizing/accessing system and method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |