CN104038498A - File synchronization updating method and device - Google Patents
File synchronization updating method and device Download PDFInfo
- Publication number
- CN104038498A CN104038498A CN201410263977.2A CN201410263977A CN104038498A CN 104038498 A CN104038498 A CN 104038498A CN 201410263977 A CN201410263977 A CN 201410263977A CN 104038498 A CN104038498 A CN 104038498A
- Authority
- CN
- China
- Prior art keywords
- file
- under
- path
- files
- blocks
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a file synchronization updating method and a file synchronization updating device. The method comprises the following steps: after a client successfully logins a server, monitoring whether a file/a folder updating event exists in a share path preset in a client configuration file of the client, responding the file/the folder updating event, and triggering the file/folder in a memory path preset in a server configuration file of the server to synchronously update, so as to improve the synchronous updating efficiency of the file on the basis of effectively ensuring the synchronous updating accuracy of the file.
Description
Technical field
The present invention relates to information-based integrated platform technical field, particularly relate to a kind of synchronously renewing file method and device.
Background technology
Along with the demand of enterprise intensification management, the application of information-based integrated platform, is used integrated platform processing business, data, information to be penetrated into enterprise security, to have produced links.Transmission between data, file, share and used by increasing information-based integrated platform, as Real-time Monitoring Data text, picture and text drawing, information paper etc.
In information-based integrated platform, user end to server transfer files is also for the situation that server uses is very common, when after file update in client, realize the renewal of synchronizeing of file and file in this client in server, and in file update process, the accuracy, the raising file update efficiency that ensure file update are one of keys promoting information-based integrated platform stability, high efficiency, to the smooth operation of guarantee information integrated platform, the integrated effect that promotes information-based integrated platform is significant.
Summary of the invention
In view of this, the embodiment of the present invention provides a kind of synchronously renewing file method and device, is ensureing, on the basis of synchronously renewing file accuracy, to improve synchronously renewing file efficiency to realize.
To achieve these goals, the technical scheme that the embodiment of the present invention provides is as follows:
A kind of synchronously renewing file method, comprising:
When after client success logon server, monitor under the shared path setting in advance in the client configuration file of described client whether have more new events of file/file;
Respond more new events of described file/file, trigger the file/file deposited under path setting in advance in the server profile of described server and synchronously upgrade.
Preferably, described synchronous renewal comprises: deleted file/file, transaction file/file, or create file/file.
Preferred:
The process of Delete Folder is: when depositing file in file and this file under path and this file described in deletion and more new events being Delete Folder when described file/file, under described shared path, deleted file presss from both sides identical;
The process of transaction file folder is: according to described file/file upgrade event synchronization deposit described in upgrading file under path and this file with when described file/file more new events be transaction file while pressing from both sides, the file being updated under described shared path is identical;
Creating the process of file is: deposit when creating file and this file under path and more new events being for establishment file when described file/file described, the file being created under described shared path is identical;
The process of deleted file is: when depositing file under path and this file described in deletion and more new events being deleted file when described file/file, under described shared path, deleted file is identical;
The process of transaction file is: when depositing file under path and this file described in deletion and more new events being transaction file when described file/file, the file being updated under described shared path is identical;
According to this position of depositing deleted file under path, described in being uploaded to, deposits under path by the file after upgrading under described shared path;
Creating the process of file is: when described file/file more new events when creating file, according to the position of the file being created under this shared path, described in the file being created is uploaded to, deposit under path under described shared path.
Preferably, the process of depositing under path described in file is uploaded to is:
Whether the size that judges described file is greater than preset value;
In the time being, according to described preset value, described file being divided into and in multiple blocks of files and each described blocks of files, being carried and its unique index value corresponding to position hereof;
Described in blocks of files described in each is uploaded to, deposit under path, to make described server according to receiving the index value carrying in blocks of files, blocks of files described in each is combined into file.
Preferably, adopt multithreading to deposit under path described in blocks of files described in each is uploaded to.
Preferably, in the time that the size of described file is not more than described preset value, the method also comprises:
Described in directly described file being uploaded to, deposit under path.
Preferably, also comprise: verify that by check code whether file/blocks of files of depositing described in being uploaded under path is correct.
Preferably, also comprise: after file/blocks of files is deposited under path described in being uploaded to, judge whether the form of described file/blocks of files meets the call format setting in advance in described server;
When no, be the form that meets described call format by the format conversion of described file/blocks of files;
Described in another existence of file/blocks of files of carrying out after format conversion, deposit under path.
Preferably, set in advance and under the shared path in the client configuration file in described client, whether exist file/file more before new events in monitoring, also comprise:
Judge file under described shared path with described in whether deposit file under path consistent;
According to inconsistent file, the described file of depositing under path is synchronously upgraded.
A kind of synchronously renewing file device, comprising:
Monitoring unit, for when after client success logon server, monitors under the shared path setting in advance in the client configuration file of described client whether have more new events of file/file;
Synchronous updating block, for responding more new events of described file/file, triggers the file/file deposited under path setting in advance in the server profile of described server and synchronously upgrades.
The application provides a kind of synchronously renewing file method and device, by when after client success logon server, monitoring sets in advance under the shared path in the client configuration file of client, whether there is more new events of file/file, and respond more new events of this file/file, file/file of depositing under path that triggering sets in advance in the server profile of server synchronously upgrades, and then effectively ensure on the basis of synchronously renewing file accuracy, improve synchronously renewing file efficiency.
Brief description of the drawings
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, the accompanying drawing the following describes is only some embodiment that record in the present invention, for those of ordinary skill in the art, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
A kind of synchronously renewing file method flow diagram that Fig. 1 provides for the embodiment of the present application one;
A kind of method flow diagram of depositing under path that file is uploaded to that Fig. 2 provides for the embodiment of the present application one;
The structural representation of a kind of synchronously renewing file device that Fig. 3 provides for the embodiment of the present application two.
Embodiment
In order to make those skilled in the art person understand better the technical scheme in the present invention, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiment.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtaining under creative work prerequisite, should belong to the scope of protection of the invention.
Embodiment mono-:
A kind of synchronously renewing file method flow diagram that Fig. 1 provides for the embodiment of the present application one.
As shown in Figure 1, the method comprises:
S101, when after client success logon server, monitor under the shared path setting in advance in the client configuration file of client whether have more new events of file/file.
In the embodiment of the present application, when client is by processes such as authentications, as: input user name and password, after success logon server, preferably, can monitor under the shared path setting in advance in the client configuration file of this client whether have more new events of file/file by this client self assembly.
Below be only the optimal way of the embodiment of the present application, inventor can arrange arbitrarily according to the demand of oneself other listening mode, to realize the monitoring to the file/file under the shared path in the client configuration file of client.
More new events of S102, response file/file, triggers the file/file deposited under path setting in advance in the server profile of server and synchronously upgrades.
In the embodiment of the present application, when listening to file/file more when new events, can respond more new events of this file/file, trigger the file/file deposited under path setting in advance in the server profile of server and synchronously upgrade.
In the embodiment of the present application, preferred, this synchronous renewal comprises: deleted file/file, transaction file/file, or create file/file.
In the embodiment of the present application, preferably, the process of Delete Folder is: when deleting the file deposited in file and this file under path and this file and more new events being Delete Folder when file/file, share deleted file under path and press from both sides identical.
In the embodiment of the present application, preferably, the process of transaction file folder is: according to file/file upgrade event synchronization upgrade the file deposited under path and this file with when file/file more new events be that transaction file is while pressing from both sides, share the file being updated under path identical, as: in the time listening to the name changing of sharing certain file under path, by deposit the title of this file under path change accordingly (by deposit the title of this file under path make into share path under title after this file change identical).
In the embodiment of the present application, preferred, the process that creates file is: under path, create file and this file and more new events is when creating file when file/file depositing, the file being created under shared path is identical.
In the embodiment of the present application, preferred, the process of deleted file is: when deleting the file deposited under path and this file and more new events being deleted file when file/file, under shared path, deleted file is identical.
In the embodiment of the present application, preferred, the process of transaction file is: first, when deleting the file deposited under path and this file and more new events being transaction file when file/file, the file being updated under shared path is identical; Then deposit the position of deleted file under path according to this, the file after upgrading is uploaded to this deposits under path under shared path.
In the embodiment of the present application, preferred, be uploaded to and deposit the position of the file under path, to deposit under path the position of deleted file identical with this.
In the embodiment of the present application, preferred, the process that creates file is: when file/file more new events when creating file, according to the position of the file being created under this shared path, be uploaded to and deposit under path sharing the file being created under path.
In the embodiment of the present application, preferably, be uploaded to and deposit the position of the file under path, corresponding with the position of the file being created under shared path, as: when shared path is D dish, deposits path while being F dish, when created the file of a name by name in the data file by name of D dish time, the file of this name by name is uploaded in the data file of depositing in path F dish.
A kind of method flow diagram of depositing under path that file is uploaded to that Fig. 2 provides for the embodiment of the present application one.
As shown in Figure 2, the method comprises:
S201, judge whether the size of file is greater than preset value.
In the embodiment of the present application, preferred, set in advance preset value, when needs are uploaded to file to deposit path lower time, first, need to judge whether the size of this file is greater than this preset value.
S202, according to preset value, file is divided into and in multiple blocks of files and each blocks of files, is carried and its unique index value corresponding to position hereof.
In the embodiment of the present application, in the time judging the size of file and be greater than preset value, according to this preset value, this file is divided into multiple blocks of files, and, in each blocks of files, carry and its unique index value corresponding to position hereof.Preferably, the size of blocks of files equals this preset value.
In the embodiment of the present application, preferred, this preset value is not a definite value, it is according to the value of current actual conditions real-time change, in the embodiment of the present application, by controlling the size of this preset value, control the current file that is greater than preset value and account for the ratio of general act.
And inventor finds by research, in the embodiment of the present application, control this ratio below 10%, be conducive to improve the efficiency of transmission of file, below be only the optimal way of the embodiment of the present application, inventor can also arrange arbitrarily according to the demand of oneself size of this ratio.
S203, each blocks of files is uploaded to and is deposited under path, to make server according to receiving the index value carrying in blocks of files, each blocks of files is combined into file.
In the embodiment of the present application, when file being divided into after multiple blocks of files, what each blocks of files was uploaded onto the server deposits under path, to make server according to the index value carrying in the blocks of files receiving, each blocks of files is combined into file, and this file is stored in to this deposits under path.
And in the embodiment of the present application, preferred, it is corresponding with the position that file under shared path is updated/creates that file is uploaded to the position of depositing under path.
Further, a kind of file being uploaded in the method for depositing under path providing in the embodiment of the present application, preferred, adopt multithreading that each blocks of files is uploaded to and is deposited under path.
In the embodiment of the present application, set in advance resource pool, this resource pool comprises multiple threads, in the time that needs are uploaded each blocks of files, obtain thread idle in current resource pool, upload a blocks of files by the thread of each free time, and when being transmitted after one time by current each idle thread, this each thread is put back to resource pool, and if now transmitted, again obtain thread idle in current resource pool blocks of files is transmitted.
Further, what provide in the embodiment of the present application is a kind ofly uploaded to file in the method for depositing under path, also comprises: in the time judging the size of file and be not more than preset value, directly this file is uploaded to and is deposited under path.
And in the embodiment of the present application, preferred, when being uploaded to, this file deposits path lower time, also can adopt the mode of multithreading, from current resource pool, obtain a highest idle thread of priority, this file is transmitted.
Further, what provide in the embodiment of the present application is a kind ofly uploaded to file in the method for depositing under path, also comprises: verify that by check code whether be uploaded to file/blocks of files of depositing under path correct.
In the embodiment of the present application, preferably, well known to a person skilled in the art that each file/blocks of files all exists a unique check code corresponding with it, the embodiment of the present application is uploaded previous check code by obtaining file/blocks of files, and upload after check code, and relatively whether both are identical, judge whether file/blocks of files is uploaded correctly.As: the check code before upload with upload check code afterwards when identical, representation file/blocks of files is uploaded correctly; When different, representation file/file is uploaded failure.
Further, a kind of file being uploaded in the method for depositing under path providing in the embodiment of the present application, also comprise: after file/blocks of files is uploaded to and deposits under path, judge whether the form of file/blocks of files meets the call format setting in advance in server; When no, be the form that meets call format by the format conversion of file/blocks of files; File/the blocks of files of carrying out after format conversion is separately deposited under path.
And in the embodiment of the present application, preferably, in server, set in advance check code storehouse, in this check code storehouse, deposit each and carry out the check code of the file/blocks of files after format conversion, and the check code of this file/blocks of files before carrying out format conversion, in the time judging the form of file/blocks of files and not meeting the call format setting in advance in server, first the unique identification of this file/blocks of files will be represented, and the current check code of this file/blocks of files is stored in check code storehouse, and carry out after format conversion in file/blocks of files, the relevant position that the check code of the file/blocks of files after conversion is stored in to check code storehouse is (preferred, this position is the position corresponding with unique identification).
In the embodiment of the present application, preferred, check code is MD5 check code, and above is only the optimal way of the embodiment of the present application, and inventor can also arrange arbitrarily according to the demand of oneself the concrete manifestation form of this check code, be not described in detail at this.
Further, what provide in the embodiment of the present application is a kind ofly uploaded to file in the method for depositing under path, also comprises: in the time that file is made mistakes in upload procedure, send one-level warning message.
In the embodiment of the present application, preferred, this one-level warning message is for ejecting error message prompting frame etc.
Further, what provide in the embodiment of the present application is a kind ofly uploaded to file in the method for depositing under path, also comprises: when in the predetermined interval of sending after warning message, do not detect the mistake in file upload procedure is not processed, send secondary warning message.
In the embodiment of the present application, preferred, the effect of this secondary warning message is identical with the effect of above-mentioned one-level warning message, is all prompting file mistakes in upload procedure.And preferred, this secondary warning message is more prone to be found by those skilled in the art compared with one-level warning message, if this secondary warning message is high sudden strain of a muscle, voice etc.
Further, in a kind of synchronously renewing file method providing in the embodiment of the present application, also comprise: whether set in advance and under the shared path in the client configuration file in client, exist file/file more before new events in monitoring, file under path is shared in judgement and whether deposit file under path consistent; According to inconsistent file, the file of depositing under path is synchronously upgraded.
In the embodiment of the present application, when after client success logon server, whether monitoring sets in advance and under the shared path in the client configuration file of client, exists file/file more before new events, first can judge the file shared under path and whether deposit file under path consistent, when inconsistent, according to all inconsistent files, the file of depositing under path is synchronously upgraded.
The embodiment of the present application provides a kind of synchronously renewing file method, by when after client success logon server, monitoring sets in advance under the shared path in the client configuration file of client, whether there is more new events of file/file, and respond more new events of this file/file, file/file of depositing under path that triggering sets in advance in the server profile of server synchronously upgrades, and then effectively ensure on the basis of synchronously renewing file accuracy, improve synchronously renewing file efficiency.
Embodiment bis-:
The structural representation of a kind of synchronously renewing file device that Fig. 3 provides for the embodiment of the present application two.
As shown in Figure 3, this device comprises: monitoring unit 1 and be connected with this monitoring unit 1 synchronize updating block 2, wherein,
Monitoring unit 1, for when after client success logon server, monitors under the shared path setting in advance in the client configuration file of client whether have more new events of file/file.
Synchronous updating block 2, for more new events of response file/file, triggers the file/file deposited under path setting in advance in the server profile of server and synchronously upgrades.
The embodiment of the present application provides a kind of synchronously renewing file device, comprise monitoring unit and synchronous updating block, monitoring unit passes through when after client success logon server, monitoring sets in advance under the shared path in the client configuration file of client, whether there is more new events of file/file, and respond more new events of this file/file by synchronous updating block, file/file of depositing under path that triggering sets in advance in the server profile of server synchronously upgrades, and then effectively ensure on the basis of synchronously renewing file accuracy, improve synchronously renewing file efficiency.
In the present invention, each embodiment adopts the mode of going forward one by one to describe, and what each embodiment stressed is and the difference of other embodiment, between each embodiment identical similar part mutually referring to.For the disclosed device of embodiment, because it corresponds to the method disclosed in Example, so description is fairly simple, relevant part illustrates referring to method part.
Below be only the preferred embodiment of the present invention, make those skilled in the art can understand or realize the present invention.To be apparent to one skilled in the art to the multiple amendment of these embodiment, General Principle as defined herein can, in the situation that not departing from the spirit or scope of the present invention, realize in other embodiments.Therefore, the present invention will can not be restricted to these embodiment shown in this article, but will meet the widest scope consistent with principle disclosed herein and features of novelty.
Claims (10)
1. a synchronously renewing file method, is characterized in that, comprising:
When after client success logon server, monitor under the shared path setting in advance in the client configuration file of described client whether have more new events of file/file;
Respond more new events of described file/file, trigger the file/file deposited under path setting in advance in the server profile of described server and synchronously upgrade.
2. method according to claim 1, is characterized in that, described synchronous renewal comprises: deleted file/file, transaction file/file, or create file/file.
3. method according to claim 2, is characterized in that:
The process of Delete Folder is: when depositing file in file and this file under path and this file described in deletion and more new events being Delete Folder when described file/file, under described shared path, deleted file presss from both sides identical;
The process of transaction file folder is: according to described file/file upgrade event synchronization deposit described in upgrading file under path and this file with when described file/file more new events be transaction file while pressing from both sides, the file being updated under described shared path is identical;
Creating the process of file is: deposit when creating file and this file under path and more new events being for establishment file when described file/file described, the file being created under described shared path is identical;
The process of deleted file is: when depositing file under path and this file described in deletion and more new events being deleted file when described file/file, under described shared path, deleted file is identical;
The process of transaction file is: when depositing file under path and this file described in deletion and more new events being transaction file when described file/file, the file being updated under described shared path is identical;
According to this position of depositing deleted file under path, described in being uploaded to, deposits under path by the file after upgrading under described shared path;
Creating the process of file is: when described file/file more new events when creating file, according to the position of the file being created under this shared path, described in the file being created is uploaded to, deposit under path under described shared path.
4. method according to claim 3, is characterized in that, the process of depositing under path described in file is uploaded to is:
Whether the size that judges described file is greater than preset value;
In the time being, according to described preset value, described file being divided into and in multiple blocks of files and each described blocks of files, being carried and its unique index value corresponding to position hereof;
Described in blocks of files described in each is uploaded to, deposit under path, to make described server according to receiving the index value carrying in blocks of files, blocks of files described in each is combined into file.
5. method according to claim 4, is characterized in that, described in employing multithreading is uploaded to blocks of files described in each, deposits under path.
6. method according to claim 5, is characterized in that, in the time that the size of described file is not more than described preset value, the method also comprises:
Described in directly described file being uploaded to, deposit under path.
7. method according to claim 6, is characterized in that, also comprises: verify that by check code whether file/blocks of files of depositing described in being uploaded under path is correct.
8. method according to claim 7, is characterized in that, also comprises: after file/blocks of files is deposited under path described in being uploaded to, judge whether the form of described file/blocks of files meets the call format setting in advance in described server;
When no, be the form that meets described call format by the format conversion of described file/blocks of files;
Described in another existence of file/blocks of files of carrying out after format conversion, deposit under path.
9. whether method according to claim 8, is characterized in that, set in advance and under the shared path in the client configuration file in described client, exist file/file more before new events in monitoring, also comprises:
Judge file under described shared path with described in whether deposit file under path consistent;
According to inconsistent file, the described file of depositing under path is synchronously upgraded.
10. a synchronously renewing file device, is characterized in that, comprising:
Monitoring unit, for when after client success logon server, monitors under the shared path setting in advance in the client configuration file of described client whether have more new events of file/file;
Synchronous updating block, for responding more new events of described file/file, triggers the file/file deposited under path setting in advance in the server profile of described server and synchronously upgrades.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410263977.2A CN104038498A (en) | 2014-06-13 | 2014-06-13 | File synchronization updating method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410263977.2A CN104038498A (en) | 2014-06-13 | 2014-06-13 | File synchronization updating method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104038498A true CN104038498A (en) | 2014-09-10 |
Family
ID=51469087
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410263977.2A Pending CN104038498A (en) | 2014-06-13 | 2014-06-13 | File synchronization updating method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104038498A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108093063A (en) * | 2017-12-26 | 2018-05-29 | 中国电信股份有限公司新疆分公司 | Big file multithreading FTP method for uploading |
| CN109391673A (en) * | 2018-04-16 | 2019-02-26 | 深圳思为科技有限公司 | A kind of method, system and the terminal device of management update file |
| CN113096006A (en) * | 2021-04-19 | 2021-07-09 | 上海跃影科技有限公司 | File synchronization method and system applied to holographic scene |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1988535A (en) * | 2005-12-23 | 2007-06-27 | 腾讯科技（深圳）有限公司 | Synchronous method, system for file storage and customer terminal |
| CN101702732A (en) * | 2009-09-23 | 2010-05-05 | 中兴通讯股份有限公司 | Document synchronous method and document synchronous system |
| CN102054036A (en) * | 2010-12-29 | 2011-05-11 | 北京新媒传信科技有限公司 | File synchronizing method and device |
| CN103428242A (en) * | 2012-05-18 | 2013-12-04 | 阿里巴巴集团控股有限公司 | Method, device and system for increment synchronization |
| US20140108505A1 (en) * | 2012-10-15 | 2014-04-17 | Hon Hai Precision Industry Co., Ltd. | File synchronization system and method |
-
2014
- 2014-06-13 CN CN201410263977.2A patent/CN104038498A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1988535A (en) * | 2005-12-23 | 2007-06-27 | 腾讯科技（深圳）有限公司 | Synchronous method, system for file storage and customer terminal |
| CN101702732A (en) * | 2009-09-23 | 2010-05-05 | 中兴通讯股份有限公司 | Document synchronous method and document synchronous system |
| CN102054036A (en) * | 2010-12-29 | 2011-05-11 | 北京新媒传信科技有限公司 | File synchronizing method and device |
| CN103428242A (en) * | 2012-05-18 | 2013-12-04 | 阿里巴巴集团控股有限公司 | Method, device and system for increment synchronization |
| US20140108505A1 (en) * | 2012-10-15 | 2014-04-17 | Hon Hai Precision Industry Co., Ltd. | File synchronization system and method |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108093063A (en) * | 2017-12-26 | 2018-05-29 | 中国电信股份有限公司新疆分公司 | Big file multithreading FTP method for uploading |
| CN109391673A (en) * | 2018-04-16 | 2019-02-26 | 深圳思为科技有限公司 | A kind of method, system and the terminal device of management update file |
| CN109391673B (en) * | 2018-04-16 | 2021-01-05 | 深圳思为科技有限公司 | Method, system and terminal equipment for managing update file |
| CN113096006A (en) * | 2021-04-19 | 2021-07-09 | 上海跃影科技有限公司 | File synchronization method and system applied to holographic scene |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9979784B2 (en) | Method for cloud data backup and recovery | |
| CN101673295B (en) | Data synchronization control method, device and single-point logging-in system | |
| CN105915369B (en) | A kind of configuration information management method and device | |
| CN103516529A (en) | Management method, device and system of configuration files | |
| WO2016107042A1 (en) | Data incremental backup method and apparatus, and nas device | |
| US10671376B2 (en) | Server program hot upgrading method and device | |
| US10311030B1 (en) | Method and system for implementing an automated migration tool | |
| CN112380227B (en) | Data synchronization method, device, equipment and storage medium based on message queue | |
| CN104038498A (en) | File synchronization updating method and device | |
| CN103874113A (en) | Wireless network maintenance method, device and system | |
| US9178860B2 (en) | Out-of-path, content-addressed writes with untrusted clients | |
| CN106201666A (en) | A kind of distributed transaction implementation method | |
| CN115001967A (en) | Data acquisition method and device, electronic equipment and storage medium | |
| CN102932443A (en) | HDFS (hadoop distributed file system) cluster based distributed cloud storage system | |
| CN110324384B (en) | Data pushing method and device | |
| CN103167035A (en) | Method for solving NameNode single-point failure in hadoop distributed file system (HDFS) | |
| CN109165032A (en) | A kind of baseboard management controller BMC setting method, device and storage medium | |
| CN103631680A (en) | Personnel desktop synchronous backup system based on cloud computing | |
| WO2016161680A1 (en) | Traffic data update method, traffic data update system and terminal | |
| CN106933888B (en) | Database configuration management system | |
| CN108153650A (en) | Obtain method, system, device and the storage medium of Cloud Server resource information | |
| CN103118072B (en) | A kind of method and system of database update | |
| KR101951118B1 (en) | Planning software type network license monitoring system, and method thereof | |
| CN103077231B (en) | A kind of method and system of database synchronization | |
| CN112817998A (en) | Method and system for automatically comparing and synchronizing data of hydropower station |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140910 |
|
| RJ01 | Rejection of invention patent application after publication |