CN101763421A - File synchronization method and device - Google Patents
File synchronization method and device Download PDFInfo
- Publication number
- CN101763421A CN101763421A CN200910261682A CN200910261682A CN101763421A CN 101763421 A CN101763421 A CN 101763421A CN 200910261682 A CN200910261682 A CN 200910261682A CN 200910261682 A CN200910261682 A CN 200910261682A CN 101763421 A CN101763421 A CN 101763421A
- Authority
- CN
- China
- Prior art keywords
- file
- incident
- change
- variation
- synchronization
- 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
Abstract
The embodiment of the invention discloses a file synchronization method and a device, wherein the file synchronization method comprises the following steps: monitoring whether a specified file change event occurs or not; merging the file change event according to the matched degree of the file change event when the specified file change event occurs; and executing the file synchronization according to the merged file change event. When the file synchronization method provided by the invention is used, the real-time file synchronization according to the file change can be realized, at the same time, the occupation on a CPU and an IO can be reduced when obtaining the file change information, and system resources are saved.
Description
Technical field
The present invention relates to the file synchronization field, more particularly, relate to file synchronisation method and device under a kind of Linux.
Background technology
In the actual deployment scene of the current anti-tamper product of webpage, generally adopt so a kind of mechanism: the web page files relevant with webpage to be released is published on the backup server, then the web page files of issuing on the backup server is synchronized on user's the Website server.In the prior art, be to know that by the disk file scan mechanism web page files on the backup server changes, and then the webpage of the new issue of discovery.Its implementation procedure is mainly: by periodically scanning the web page files on the disk in the backup server, when by web page files was compared at the timestamp of a last scan period and the timestamp of current scan period, find certain web page files when the timestamp of current scan period changes, be about to this web page files and be synchronized on the Website server from backup server.
By research to prior art, the inventor finds: in the file synchronisation method of prior art, be periodically the file on the backup server to be scanned, can not know in real time that the web page files on the backup server changes, so can't carry out synchronously to real-time to the file on the Website server; Simultaneously,, therefore, when monitored file does not change or have only partial document to change, also can scan, can cause too high CPU and IO to take, waste system resource all monitored files owing to be periodically to scan.
Summary of the invention
For solving the problems of the technologies described above, the invention provides a kind of file synchronisation method and device, the variation to file that system can real-time is carried out synchronously; Make simultaneously and when obtaining the file change event information, reduce CPU and IO takies, conserve system resources.
The embodiment of the invention provides following technical scheme:
A kind of file synchronisation method comprises: whether the file change incident that monitors appointment takes place; When the file change incident of described appointment takes place, described file change incident is merged according to file change event matches degree; Synchronous according to the file change incident execute file after the described merging.
Preferably, whether the file change incident of described supervision appointment comprises: obtain the Monitoring Files of appointment and the file change incident of appointment; Monitor that the file change incident of described appointment takes place the Monitoring Files whether appointment is arranged.
Preferably, describedly comprise synchronously: obtain and the relevant variation file of file change incident after the described merging according to the file synchronization strategy according to the file change incident execute file after the described merging; The notice client-server carries out file synchronization to described variation file; Perhaps, directly obtain and the relevant variation file of file change incident after the described merging; The notice client-server carries out file synchronization to described variation file.
Preferably, describedly obtain the variation file relevant with file change incident after the described merging according to the file synchronization strategy and comprise: the file change incident after being combined according to fileinfo and/or file change event type is screened; Obtain with screen after the relevant variation file of file change incident.
Preferably, described notice client-server carries out file synchronization to described variation file and comprises: after obtaining described variation file, the real-time informing client-server carries out file synchronization to described variation file; Perhaps, after obtaining described variation file, time-delay notice client-server carries out file synchronization to described variation file; Perhaps, after obtaining described variation file, regularly notify client-server that described variation file is carried out file synchronization.
Preferably, the file change incident of described appointment comprises: the accessed incident of file, file is modified incident, file attribute is modified incident, when finishing, operating writing-file closes the descriptor incident, closing can not written document descriptor incident, incident opens file, file is moved out of incident, file is moved into incident, the deleted incident of file, create new file event, file delete self incident, file movement self incident, the close file incident, the move incident, the unloaded incident of file system, incident and file be left in the basket any one or any multiple combination in the incident are overflowed in event queuing.
A kind of file synchronization device comprises: the incident monitor unit is used to monitor whether the file change incident of appointment takes place; The incident merge cells is used for according to file change event matches degree described file change incident being merged when the file change incident of described appointment takes place; The file synchronization unit is used for according to the file change incident execute file after the described merging synchronous.
Preferably, described incident monitor unit comprises: information acquisition unit is used to obtain the Monitoring Files of appointment and the file change incident of appointment; Monitoring executing unit is used to monitor that the file change incident of described appointment takes place the Monitoring Files whether appointment is arranged.
Preferably, described file synchronization unit comprises: the first file acquiring unit is used for obtaining and the relevant variation file of file change incident after the described merging according to the file synchronization strategy; Notification unit is used to notify client-server that described variation file is carried out file synchronization; Perhaps, the second file acquiring unit is used for directly obtaining and the relevant variation file of file change incident after the described merging; Notification unit is used to notify client-server that described variation file is carried out file synchronization.
Preferably, the described first file acquiring unit comprises: the screening unit, and the file change incident after being used for being combined according to fileinfo and/or file change event type is screened; Acquiring unit, be used to obtain with screen after the relevant variation file of file change incident.
Preferably, described notification unit comprises: the real-time informing unit, be used for after obtaining described variation file, and the real-time informing client-server carries out file synchronization to described variation file; Perhaps, the time-delay notification unit is used for after obtaining described variation file, and time-delay notice client-server carries out file synchronization to described variation file; Perhaps, regularly notification unit is used for after obtaining described variation file, regularly notifies client-server that described variation file is carried out file synchronization.
Preferably, the file change incident of described appointment comprises: the accessed incident of file, file is modified incident, file attribute is modified incident, when finishing, operating writing-file closes the descriptor incident, closing can not written document descriptor incident, incident opens file, file is moved out of incident, file is moved into incident, the deleted incident of file, create new file event, file delete self incident, file movement self incident, the close file incident, the move incident, the unloaded incident of file system, incident and/or file be left in the basket any one or any multiple combination in the incident are overflowed in event queuing.
Use the technical scheme that the embodiment of the invention provided, be that the change events of file is monitored, when the user operates file, can report corresponding file change incident to supervisory system, so can be real-time get access to the variation of file according to the file change incident, and can according to the file change incident real-time carry out file synchronously, CPU and IO when also having reduced to obtain file change simultaneously take, and have saved system resource.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the process flow diagram of an embodiment of a kind of file synchronisation method of the present invention;
Fig. 2 is the process flow diagram of another embodiment of a kind of file synchronisation method of the present invention;
Fig. 3 is the system construction drawing of file synchronization among the present invention;
The structural representation of the file synchronization device that Fig. 4 provides for the specific embodiment of the invention.
Embodiment
In the file synchronisation method of prior art, be to adopt disk scanning mechanism periodically the file on the backup server to be scanned, therefore can not know in real time that the web page files on the backup server changes, so can't carry out synchronously to real-time to the file on the Website server; Simultaneously,, therefore, when monitored file does not change or have only partial document to change, also can scan, can cause too high CPU and IO to take, waste system resource all monitored files owing to be periodically to scan.
For this reason, the invention provides a kind of file synchronisation method, comprising:
Whether the file change incident that monitors appointment takes place;
When the file change incident of described appointment takes place, described file change incident is merged according to file change event matches degree;
Synchronous according to the file change incident execute file after the described merging.
Use file synchronisation method provided by the present invention, the variation to file that can real-time is carried out synchronously, can all monitored files not scanned simultaneously, has reduced CPU and IO takies, and has saved system resource.
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that is obtained under the creative work prerequisite.
Embodiment one:
Referring to shown in Figure 1, the process flow diagram of a kind of file synchronisation method that provides for the specific embodiment of the invention, this method specifically may further comprise the steps:
Step S101 monitors whether the file change incident of appointment takes place.
In Linux, operation to All Files realizes by calling the file operation function, a kind of file change event monitoring mechanism is provided among the Linux, it realizes that principle is: add corresponding incident call function in the handling function of file, when the user utilizes the file operation function that file is operated, will call the incident call function in the file operation function automatically, described incident call function can report all file change incidents relevant with user's file operation from the trend supervisory system, therefore, by the Monitoring Files change events whether this monitoring mechanism taking place can monitor any operation of user to web page files in real time.
System can wait for the generation of a series of file change incidents, when the file change incident takes place, the file change incident that system kernel can go the proactive notification supervisory system to go to read to have taken place, and carry out follow-up file synchronization according to the file change incident that has taken place and handle.
Wherein, whether the file change incident of supervision appointment comprises: obtain the Monitoring Files of appointment and the file change incident of appointment; Monitor that the file change incident of described appointment takes place the Monitoring Files whether appointment is arranged.For example, system can monitor whether the Monitoring Files of appointment the file change incident of appointment takes place.And the file change incident of the file of appointment and appointment can be set arbitrarily according to user's user demand, and present embodiment does not limit this.The file change incident of described appointment comprises: the accessed incident of file, file is modified incident, file attribute is modified incident, when finishing, operating writing-file closes the descriptor incident, closing can not written document descriptor incident, incident opens file, file is moved out of incident, file is moved into incident, the deleted incident of file, create new file event, file delete self incident, file movement self incident, the close file incident, the move incident, the unloaded incident of file system, incident and file be left in the basket any one or any multiple combination in the incident are overflowed in event queuing.
When the file change incident is monitored, can set in advance a configuration file, in configuration file, include each file directory and with the corresponding file path of each file directory.Can obtain the file change incident that to monitor according to file directory with the corresponding file path of file directory.When needs were revised the file change incident that is monitored, only need make amendment to the file directory in the configuration file with the corresponding file path of file directory got final product.
Step S102 when the file change incident of described appointment takes place, merges described file change incident according to file change event matches degree.
Generally, a normal file operation for the user, the file operation function that is associated of several successive may call in system, so can monitor the file change incident that is associated of several successive, therefore need described file change incident be merged according to the matching degree of file change incident, described matched rule is meant that the immigration incident of the incident that shifts out of file A for example and file A can merge into the moving event of a file A.
For example, for the operation of file movement, system can detect that file is moved out of incident and file is moved into incident, therefore, the file that monitors can be moved out of incident and file and be moved into incident and merge into a file movement incident; For directory delete operation, system can monitor the different files under this catalogue or the deletion event of sub-directory, so the deletion event that several files of getting access to or sub-directory deletion event can be merged into a composite catalog.
Step S103, synchronous according to the file change incident execute file after the described merging.
Wherein, can directly obtain and the relevant variation file of file change incident after the described merging according to the information of file change incident; The notice client-server carries out file synchronization to described variation file.
In addition, can also obtain and the relevant variation file of file change incident after the described merging according to the file synchronization strategy; The notice client-server carries out file synchronization to described variation file.
Describedly obtain the variation file relevant with file change incident after the described merging according to the file synchronization strategy and comprise: the file change incident after being combined according to the file change event type is screened; Obtain with screen after the relevant variation file of file change incident.For example get rid of to incident of opening file or close file incident synchronously, obtain with screen after the relevant variation file of file change incident.Perhaps, according to fileinfo to the file change incident after merging screen; Obtain with screen after the relevant variation file of file change incident.So that client-server carries out file synchronization to the variation file after screening, described fileinfo can comprise: the summary info of the title of file, the type of file or file etc.
Wherein, notifying client-server that described variation file is carried out file synchronization can comprise:
After obtaining described variation file, the real-time informing client-server carries out file synchronization to described variation file;
Perhaps, after obtaining described variation file, time-delay notice client-server carries out file synchronization to described variation file;
Perhaps, after obtaining described variation file, regularly notify client-server that described variation file is carried out file synchronization.
Described file synchronization specifically can comprise: according to described variation file and this document corresponding file change events, carry out corresponding file operation on client-server; For example: when deletion self incident takes place the file A on the home server, on client-server, carry out corresponding file operation, be about to corresponding file delete.
Described file synchronization specifically can also comprise: carry out this variation file transfer to client-server according to described variation file and this document corresponding file change events; For example: in a catalogue of home server, newly write file B, then answer startup file transmission thread that this document is transferred on the client-server under the corresponding catalogue, can also monitor the transmission course of file simultaneously in real time.
As can be seen from the above-described embodiment, use the file synchronisation method that present embodiment provided, the variation to file that can real-time is carried out synchronously, and the while can not scanned all monitored files, has reduced CPU and IO takies, and has saved system resource.
Embodiment two:
Below in conjunction with a concrete application example, the technical scheme of the inventive method embodiment is described:
See also Fig. 3, Fig. 3 is the system construction drawing of file synchronization among the present invention, as shown in Figure 3, after the user is published to web page files on the backup server, respectively to moving that the file A on the backup server carries out, B deletes to catalogue again, and then the file synchronisation method between backup server and the Website server sees also shown in Figure 2, the process flow diagram of a kind of file synchronisation method that Fig. 2 provides for the specific embodiment of the invention, this method specifically may further comprise the steps:
Step S201 sets in advance the configuration file of monitored object.
In configuration file, need to dispose appointment Monitoring Files and with the file change incident of the corresponding appointment of this Monitoring Files.For example, the user need monitor file A on the backup server and catalogue B, if variation has taken place in the All Files among file A and the catalogue B, promptly realize file between backup server and the Website server synchronously.Then need be provided with by the user in configuration file is All Files among file A and the catalogue B according to the specified Monitoring Files of user's needs.If the user need be in the file A variation that is moved, when catalogue B is deleted, realize the file synchronization between backup server and the Website server device, then need in configuration file, be provided with the corresponding specified file change events of file A be moving event, with the corresponding specified file change events of catalogue B be deletion event.
Certainly, need to prove, above-mentioned situation only is special circumstances of special setting for the back makes things convenient for the synchronous method of description document, in practice, can set the Monitoring Files of appointment and the file change incident of appointment arbitrarily in configuration file according to user's actual demand.
Based on above-mentioned situation, can comprise in the configuration file: the title of file A, path and corresponding moving event, the title of catalogue B, path and corresponding deletion event.In addition, when supervisory system was made amendment to monitored object, modification that can be corresponding was also preserved configuration file; Moving event and the deletion event of file A all can certainly be added in the configuration file.
Step S202 reads configuration file, obtains monitored object.
System can be by reading title, path and the corresponding moving event that configuration file obtains file A, the title of catalogue B, path and corresponding deletion event; Accessed information is imported in the kernel.
Step S203 monitors specifying monitored object.
The monitoring file A incident that whether is moved monitors whether catalogue B deletion event takes place.When the file movement function carries out will calling the corresponding incident call function in the file operation function automatically when mobile to file A, described incident call function can be from the incident that shifts out of trend supervisory system reporting file A and the immigration incident of file A; When the file delete function is deleted catalogue B, will call the corresponding incident call function in the file operation function automatically, if catalogue B is an empty list, then described incident call function can report the deletion event of catalogue B from the trend supervisory system; If comprise different files and sub-directory among the catalogue B, then described incident call function can report file and the deletion event of catalogue and the deletion event of catalogue B among the catalogue B from the trend supervisory system; Above-mentioned file change incident is that strict sequencing is arranged on time of origin.
When the deletion event of the moving event of file A or catalogue B takes place, the file change incident that system kernel can go the proactive notification supervisory system to go to read to have taken place, and carry out follow-up file synchronization according to the file change incident that has taken place and handle.
Step S204 merges described file change incident according to file change event matches degree.
When the deletion event of the moving event of file A or catalogue B took place, system can get access to the incident that shifts out of A and the immigration incident of file A, the deletion event of the file among the catalogue B and the deletion event of sub-directory and catalogue B.
Incident according to systemic presupposition merges matched rule, the immigration incident of the incident that shifts out of file A and file A can be merged into the moving event of file A, the deletion event of the deletion event of file among the catalogue B and sub-directory and catalogue B be merged into the deletion event of catalogue B.
Step S205, synchronous according to the file change incident execute file after the described merging.
After the file synchronization incident is merged, the user can come as required in real time, delay time or timing carry out file synchronization.
The concrete operations of described file synchronization are: according to the move operation of carrying out corresponding file A at the moving event of the file A that takes place on the home server on far-end server; According to the deletion action of on far-end server, carrying out corresponding catalogue B at the deletion event of the catalogue B that takes place on the home server.In addition, if the file change incident that monitors is included in when newly writing file in the home server, then can startup file the transmission thread, with the file transfer that newly writes to the far-end server under the corresponding path.
Certainly, also can optionally the change events or the file of file be carried out synchronously according to the synchronization policy of user preset, as get rid of to certain type file synchronously or get rid of to certain file change incident synchronously.
As can be seen from the above-described embodiment, use the technical scheme that the embodiment of the invention provided, be that the change events of file is monitored, when the user operates file, can report corresponding file change incident to supervisory system, thus can be real-time get access to the variation of file according to the file change incident, and can according to the file change incident real-time carry out file synchronously, CPU and IO when also having reduced to obtain file change simultaneously take, and have saved system resource.
Embodiment three
Correspond to above-mentioned file synchronisation method, the present invention also provides a kind of file synchronization device, referring to shown in Figure 4, structural representation for the file synchronization device that the specific embodiment of the invention provided, comprise: incident monitor unit 401, incident merge cells 402 and file synchronization unit 403, wherein
When the user carries out file operation by the file operation function, incident call function in the file operation function will trigger the file change incident and report incident monitor unit 401, the process that reads the file change incident of described incident monitor unit will be activated, and goes to read the file change incident that is monitored and uses for application program.
Wherein, the file change incident of described appointment comprises: the accessed incident of file, file is modified incident, file attribute is modified incident, when finishing, operating writing-file closes the descriptor incident, closing can not written document descriptor incident, incident opens file, file is moved out of incident, file is moved into incident, the deleted incident of file, create new file event, file delete self incident, file movement self incident, the close file incident, the move incident, the unloaded incident of file system, incident and file be left in the basket any one or any multiple combination in the incident are overflowed in event queuing.
Described incident monitor unit 401 comprises: information acquisition unit 4011 and monitoring executing unit 4012,
Monitoring executing unit 4012 is used for according to information acquisition unit accessed that information monitors that the file change incident of described appointment takes place the Monitoring Files whether appointment is arranged.
Incident merge cells 402 is used for according to file change event matches degree described file change incident being merged when the file change incident of described appointment takes place.
A normal file operation, the file operation function that is associated of several successive may call in system, so monitoring unit 401 can monitor the file change incident that is associated of several successive, so incident merge cells 402 need merge described file change incident according to the matching degree of file change incident.
In the practical application scene, the user can optionally carry out the synchronous of file, so described file synchronization unit 403 comprises: and the first file acquiring unit 4031 and notification unit 4032, wherein,
The first file acquiring unit 4031 is used for obtaining and the relevant variation file of file change incident after the described merging according to the file synchronization strategy.
Wherein, the described first file acquiring unit 4031 comprises:
The screening unit, the file change incident after being used for being combined according to the file change event type is screened; With, acquiring unit, be used to obtain with screen after the relevant variation file of file change incident.
Certainly, the user also can directly carry out file synchronization according to accessed file change incident, so described file synchronization unit 403 comprises:
The second file acquiring unit is used for directly obtaining and the relevant variation file of file change incident after the described merging.
Notification unit is used to notify client-server that described variation file is carried out file synchronization.
The user can also come select File synchronous opportunity according to demand, so described notification unit 4032 comprises:
The real-time informing unit is used for after obtaining described variation file, and the real-time informing client-server carries out file synchronization to described variation file;
Perhaps,
The time-delay notification unit is used for after obtaining described variation file, and time-delay notice client-server carries out file synchronization to described variation file;
Perhaps,
Regularly notification unit is used for after obtaining described variation file, regularly notifies client-server that described variation file is carried out file synchronization.
As can be seen from the above-described embodiment, use the file synchronization device that present embodiment provided, be that the change events of file is monitored, when the user operates file, can report corresponding file change incident to supervisory system, so the variation to file that can real-time is carried out synchronously, the while can not scanned all monitored files, reduce CPU and IO takies, saved system resource.
The above only is the specific embodiment of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.
Claims (12)
1. a file synchronisation method is characterized in that, comprising:
Whether the file change incident that monitors appointment takes place;
When the file change incident of described appointment takes place, described file change incident is merged according to file change event matches degree;
Synchronous according to the file change incident execute file after the described merging.
2. method according to claim 1 is characterized in that, whether the file change incident of described supervision appointment comprises:
Obtain the Monitoring Files of appointment and the file change incident of appointment;
Monitor that the file change incident of described appointment takes place the Monitoring Files whether appointment is arranged.
3. method according to claim 1 is characterized in that, describedly comprises synchronously according to the file change incident execute file after the described merging:
Obtain and the relevant variation file of file change incident after the described merging according to the file synchronization strategy;
The notice client-server carries out file synchronization to described variation file;
Perhaps,
Directly obtain and the relevant variation file of file change incident after the described merging;
The notice client-server carries out file synchronization to described variation file.
4. method according to claim 3 is characterized in that, describedly obtains the variation file relevant with file change incident after the described merging according to the file synchronization strategy and comprises:
File change incident after being combined according to fileinfo and/or file change event type is screened;
Obtain with screen after the relevant variation file of file change incident.
5. method according to claim 3 is characterized in that, described notice client-server carries out file synchronization to described variation file and comprises:
After obtaining described variation file, the real-time informing client-server carries out file synchronization to described variation file;
Perhaps,
After obtaining described variation file, time-delay notice client-server carries out file synchronization to described variation file;
Perhaps,
After obtaining described variation file, regularly notify client-server that described variation file is carried out file synchronization.
6. according to any described method of claim 1-5, it is characterized in that the file change incident of described appointment comprises:
The accessed incident of file, file are modified that incident, file attribute are modified incident, close the descriptor incident when operating writing-file finishes, closing can not written document descriptor incident, the incident that opens file, file are moved out of incident, file is moved into incident, the deleted incident of file, create new file event, file delete self incident, file movement self incident, close file incident, and incident and file be left in the basket any one or any multiple combination in the incident are overflowed in move incident, the unloaded incident of file system, event queuing.
7. a file synchronization device is characterized in that, comprising:
The incident monitor unit is used to monitor whether the file change incident of appointment takes place;
The incident merge cells is used for according to file change event matches degree described file change incident being merged when the file change incident of described appointment takes place;
The file synchronization unit is used for according to the file change incident execute file after the described merging synchronous.
8. device according to claim 7 is characterized in that, described incident monitor unit comprises:
Information acquisition unit is used to obtain the Monitoring Files of appointment and the file change incident of appointment;
Monitoring executing unit is used to monitor that the file change incident of described appointment takes place the Monitoring Files whether appointment is arranged.
9. device according to claim 7 is characterized in that, described file synchronization unit comprises:
The first file acquiring unit is used for obtaining and the relevant variation file of file change incident after the described merging according to the file synchronization strategy;
Notification unit is used to notify client-server that described variation file is carried out file synchronization;
Perhaps,
The second file acquiring unit is used for directly obtaining and the relevant variation file of file change incident after the described merging;
Notification unit is used to notify client-server that described variation file is carried out file synchronization.
10. device according to claim 9 is characterized in that, the described first file acquiring unit comprises:
The screening unit, the file change incident after being used for being combined according to fileinfo and/or file change event type is screened;
Acquiring unit, be used to obtain with screen after the relevant variation file of file change incident.
11. device according to claim 9 is characterized in that, described notification unit comprises:
The real-time informing unit is used for after obtaining described variation file, and the real-time informing client-server carries out file synchronization to described variation file;
Perhaps,
The time-delay notification unit is used for after obtaining described variation file, and time-delay notice client-server carries out file synchronization to described variation file;
Perhaps,
Regularly notification unit is used for after obtaining described variation file, regularly notifies client-server that described variation file is carried out file synchronization.
12., it is characterized in that the file change incident of described appointment comprises according to any described device of claim 7-11:
The accessed incident of file, file are modified that incident, file attribute are modified incident, close the descriptor incident when operating writing-file finishes, closing can not written document descriptor incident, the incident that opens file, file are moved out of incident, file is moved into incident, the deleted incident of file, create new file event, file delete self incident, file movement self incident, close file incident, and incident and/or file be left in the basket any one or any multiple combination in the incident are overflowed in move incident, the unloaded incident of file system, event queuing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910261682A CN101763421A (en) | 2009-12-24 | 2009-12-24 | File synchronization method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910261682A CN101763421A (en) | 2009-12-24 | 2009-12-24 | File synchronization method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101763421A true CN101763421A (en) | 2010-06-30 |
Family
ID=42494585
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910261682A Pending CN101763421A (en) | 2009-12-24 | 2009-12-24 | File synchronization method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101763421A (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102833267A (en) * | 2012-09-14 | 2012-12-19 | 山东中创软件商用中间件股份有限公司 | Method and device for protecting webpage security |
| CN102946410A (en) * | 2012-10-15 | 2013-02-27 | 北京奇虎科技有限公司 | Method and device for network synchronization |
| CN102946411A (en) * | 2012-10-15 | 2013-02-27 | 北京奇虎科技有限公司 | Network synchronization system |
| CN103139263A (en) * | 2011-12-02 | 2013-06-05 | 潘燕辉 | Method of automatically realizing cloud storage |
| CN103473341A (en) * | 2013-09-23 | 2013-12-25 | 网易（杭州）网络有限公司 | Playing list generating method and equipment |
| 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 |
| CN104348914A (en) * | 2014-10-31 | 2015-02-11 | 福建六壬网安股份有限公司 | Tamper-proofing system file synchronizing system and tamper-proofing system file synchronizing method |
| WO2016180265A1 (en) * | 2015-05-13 | 2016-11-17 | 阿里巴巴集团控股有限公司 | Log event processing method and device |
| CN106372526A (en) * | 2016-08-19 | 2017-02-01 | 上海爱数信息技术股份有限公司 | File change monitoring and synchronization method and system |
| CN109446170A (en) * | 2018-09-13 | 2019-03-08 | 北京米文动力科技有限公司 | A kind of profile data synchronous method and equipment |
-
2009
- 2009-12-24 CN CN200910261682A patent/CN101763421A/en active Pending
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103139263A (en) * | 2011-12-02 | 2013-06-05 | 潘燕辉 | Method of automatically realizing cloud storage |
| CN102833267A (en) * | 2012-09-14 | 2012-12-19 | 山东中创软件商用中间件股份有限公司 | Method and device for protecting webpage security |
| CN102946410A (en) * | 2012-10-15 | 2013-02-27 | 北京奇虎科技有限公司 | Method and device for network synchronization |
| CN102946411A (en) * | 2012-10-15 | 2013-02-27 | 北京奇虎科技有限公司 | Network synchronization system |
| CN103473341A (en) * | 2013-09-23 | 2013-12-25 | 网易（杭州）网络有限公司 | Playing list generating method and equipment |
| WO2015085901A1 (en) * | 2013-12-10 | 2015-06-18 | 北京奇虎科技有限公司 | File transmission method and device, and related 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 |
| CN104348914A (en) * | 2014-10-31 | 2015-02-11 | 福建六壬网安股份有限公司 | Tamper-proofing system file synchronizing system and tamper-proofing system file synchronizing method |
| WO2016180265A1 (en) * | 2015-05-13 | 2016-11-17 | 阿里巴巴集团控股有限公司 | Log event processing method and device |
| CN106372526A (en) * | 2016-08-19 | 2017-02-01 | 上海爱数信息技术股份有限公司 | File change monitoring and synchronization method and system |
| CN106372526B (en) * | 2016-08-19 | 2019-08-02 | 上海爱数信息技术股份有限公司 | A kind of monitoring file change and synchronous method and system |
| CN109446170A (en) * | 2018-09-13 | 2019-03-08 | 北京米文动力科技有限公司 | A kind of profile data synchronous method and equipment |
| CN109446170B (en) * | 2018-09-13 | 2024-01-19 | 北京米文动力科技有限公司 | Configuration file data synchronization method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101763421A (en) | File synchronization method and device | |
| CN106713487B (en) | Data synchronization method and device | |
| CN102970158B (en) | Log storage and processing method and log server | |
| CN101729595A (en) | Network backup device and backup method thereof | |
| US8370853B2 (en) | Event notification management | |
| JP2018527683A (en) | Method and apparatus for loading terminal application | |
| CN101833489A (en) | Method for file real-time monitoring and intelligent backup | |
| CN102360410B (en) | User operation discovery method of file system and synchronous system utilizing the same | |
| CN102999400A (en) | Data backup method and device of cloud storage system | |
| CN103218224A (en) | Method and terminal for improving utilization ratio of memory space | |
| CN102831035A (en) | Information backup method and device | |
| CN105760240A (en) | Distributed task processing method and device | |
| CN103780675B (en) | A kind of cloud disc file synchronous method and device | |
| KR20140053998A (en) | Method and device for managing pictures of mobile terminal | |
| CN102968486A (en) | High-reliability file synchronization method based on log change | |
| CN108647317A (en) | Generation method, device and the storage medium and electronic equipment of delta file | |
| CN106126335A (en) | The Media Survey method of terminal unit and terminal unit | |
| CN103577048A (en) | Desktop icon intelligent arranging system and method | |
| CN105005517B (en) | The storage and backup system and method for call center's recording file | |
| CN103150503A (en) | Trojan scanning method and Trojan scanning device | |
| CN102799609A (en) | Data acquisition method based on data monitoring | |
| WO2022100192A1 (en) | Multimedia file processing methods and apparatus, terminal, and network access point device | |
| CN115562744A (en) | Application program loading method and electronic equipment | |
| CN107959791B (en) | Video image acquisition processing method and device, computer equipment and storage medium | |
| JP5504872B2 (en) | Data stream processing system and method, processing node rearrangement apparatus, and program |
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 |
Application publication date: 20100630 |