CN111538710A - Method and system for real-time data synchronization based on rsync - Google Patents
Method and system for real-time data synchronization based on rsync Download PDFInfo
- Publication number
- CN111538710A CN111538710A CN202010326678.4A CN202010326678A CN111538710A CN 111538710 A CN111538710 A CN 111538710A CN 202010326678 A CN202010326678 A CN 202010326678A CN 111538710 A CN111538710 A CN 111538710A
- Authority
- CN
- China
- Prior art keywords
- event
- file
- file system
- synchronization
- rsync
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000012544 monitoring process Methods 0.000 claims abstract description 54
- 238000012217 deletion Methods 0.000 claims description 30
- 230000037430 deletion Effects 0.000 claims description 30
- 238000012216 screening Methods 0.000 claims description 6
- 230000001360 synchronised effect Effects 0.000 claims description 6
- 230000007717 exclusion Effects 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 1
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Mathematical Physics (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a method and a system for real-time data synchronization based on rsync, wherein the method comprises the following steps: monitoring a file system in real time to obtain monitoring data; setting the data synchronization frequency of the file system according to the acquired command; then judging whether the size of the current file system is smaller than or equal to a set file system threshold value or not according to the data synchronization frequency; if so, executing a full-quantity synchronization mode, otherwise, executing an incremental synchronization mode. The system comprises: the device comprises a monitoring module, a frequency setting module, a judging module, a full-quantity synchronization module and an increment synchronization module. By the method and the device, the resource occupation of the server can be effectively reduced while the timely synchronization from the server side to the client side is ensured, the influence on the bandwidth is avoided, and the overall performance of the server is improved.
Description
Technical Field
The present application relates to the technical field of server data transmission, and in particular, to a method and system for performing real-time data synchronization based on rsync.
Background
In the field of server data transmission, files are often required to be synchronously transmitted in a plurality of hosts, and rsync is a remote data synchronization tool commonly used in operation and maintenance work.
At present, a commonly used method for performing data synchronization based on rsync generally adopts triggered data synchronization combining rsync + inotify. Specifically, real-time data monitoring is achieved by using an inotify mechanism, namely a file system operation monitoring mechanism, and when the inotify monitors that a file system changes, rsync is triggered to perform data synchronization operation at the first time.
However, in the current method for performing data synchronization based on rsync, since the monitoring result of the inotify mechanism triggers the rsync in real time, the rsync is frequently operated, a large amount of system resources are occupied, and bandwidth and overall performance of the server are affected.
Disclosure of Invention
The application provides a method and a system for real-time data synchronization based on rsync, which are used for solving the problems that data synchronization in the prior art occupies a large amount of system resources and affects bandwidth and server performance.
In order to solve the technical problem, the embodiment of the application discloses the following technical scheme:
a method for real-time data synchronization based on rsync, the method comprising:
the method comprises the steps of monitoring a file system in real time to obtain monitoring data, wherein the file system is arranged in a main server, and the monitoring data comprise: the file system comprises the size of the file system, file attributes and an event file, wherein the event file is used for recording events occurring in the file system, and the events comprise: modifying an event, adding an event, deleting an event and moving an event;
setting the data synchronization frequency of the file system according to the acquired command;
judging whether the size of the current file system is smaller than or equal to a set file system threshold value or not according to the data synchronization frequency;
if so, synchronizing the current file system to each web server in real time by using rsync in a full-scale synchronization mode;
if not, the current file system is synchronized to each web server in real time by using the rsync in an incremental synchronization mode.
Optionally, the synchronizing, in a full-volume synchronization manner, the synchronizing, in real time, the current file system to each web server by using rsync includes:
reading an event file in the monitoring data;
if the event in the event file is a deletion event or a movement event, recording a deletion log;
deleting the corresponding file in the web server according to the deletion log;
if the event in the event file is a newly added event or a modified event, excluding the set directory and file;
and performing full directory synchronization operation on the file system excluding the set directory and file.
Optionally, the synchronizing, in an incremental synchronization manner, the current file system to each web server in real time by using rsync includes:
reading an event file in the monitoring data;
if the event in the event file is a deletion event or a movement event, recording a deletion log;
deleting the corresponding file in the web server according to the deletion log;
if the event in the event file is a newly added event or a modified event, screening and eliminating repeated files according to the event file to generate an execution file;
and incrementally synchronizing the file system content corresponding to the executed file to each Web server by using the rsync.
Optionally, the file system comprises: a common magnitude file system and a large magnitude file system.
Optionally, after performing a full-scale directory synchronization operation on the file system excluding the set directory and file, the method further includes:
and deleting the event file in the current file system monitoring data.
Optionally, after incrementally synchronizing the file system content corresponding to the executed file to each Web server by using the rsync, the method further includes:
and deleting the execution file and the event file in the current file system monitoring data.
A system for real-time data synchronization based on rsync, the system comprising:
the monitoring module is used for monitoring a file system in real time to acquire monitoring data, the file system is arranged in the main server, and the monitoring data comprises: the file system comprises the size of the file system, file attributes and an event file, wherein the event file is used for recording events occurring in the file system, and the events comprise: modifying an event, adding an event, deleting an event and moving an event;
the frequency setting module is used for setting the data synchronization frequency of the file system according to the acquired command;
the judging module is used for judging whether the size of the current file system is smaller than or equal to a set file system threshold value or not according to the data synchronization frequency;
the full synchronization module is used for synchronizing the current file system to each web server in real time by using rsync in a full synchronization mode when the size of the current file system is smaller than or equal to a set file system threshold value;
and the incremental synchronization module is used for synchronizing the current file system to each web server in real time by using rsync in an incremental synchronization mode when the size of the current file system is larger than a set file system threshold value.
Optionally, the full-scale synchronization module includes:
the first reading unit is used for reading the event file in the monitoring data;
the first recording unit is used for recording a deletion log when the event in the event file is a deletion event or a movement event;
the first deleting unit is used for deleting the corresponding file in the web server according to the deleting log;
the exclusion unit is used for excluding the set directory and files when the event in the event file is a newly added event or a modified event;
and the full directory synchronization unit is used for executing full directory synchronization operation on the file system excluding the set directories and files.
Optionally, the incremental synchronization module includes:
the second reading unit is used for reading the event file in the monitoring data;
the second recording unit is used for recording a deletion log when the event in the event file is a deletion event or a movement event;
the second deleting unit is used for deleting the corresponding file in the web server according to the deleting log;
the execution file generation unit is used for screening and eliminating repeated files according to the event file to generate an execution file when the event in the event file is a newly added event or a modified event;
and the incremental file synchronization unit is used for synchronizing the file system matched with the execution file to each Web server by using rsync.
Optionally, the system further includes a deleting module, configured to delete a file related to the event file in the current file system monitoring data after the current file system is synchronized to each web server in real time.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
the method comprises the steps of firstly monitoring a file system in real time to obtain monitoring data, secondly setting the data synchronization frequency of the file system according to an obtained command, and then judging whether the size of the current file system is smaller than or equal to a set file system threshold value or not according to the data synchronization frequency, if so, executing a full-scale synchronization mode, and otherwise, executing an incremental synchronization mode. The embodiment monitors the file system in real time, controls the rsync to periodically execute the synchronization operation by adopting a mode of setting the synchronization frequency, can realize the timely synchronization from the server to the client, and can reduce the resource occupation of the server, thereby avoiding influencing the bandwidth and being beneficial to improving the overall performance of the server. The embodiment also adopts different data synchronization modes aiming at different file system sizes, full synchronization is carried out when the file system is small, incremental synchronization is adopted when the file system is large, files with events are extracted, and the data synchronization efficiency is further improved.
The application also provides a system for real-time data synchronization based on rsync, which mainly comprises a monitoring module, a frequency setting module, a judging module, a full-quantity synchronization module and an incremental synchronization module. The frequency setting module can avoid frequent triggering of the rsync, can ensure timely synchronization from a server to a client, and can reduce resource occupation of the server, thereby avoiding influencing bandwidth and being beneficial to improving the overall performance of the server. The size of the file system is judged through the judging module, so that the full-size synchronizing module or the incremental synchronizing module is selected to be started according to the difference of the sizes of the file systems, data synchronization is more targeted, and the efficiency of the data synchronization is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for performing real-time data synchronization based on rsync according to an embodiment of the present application;
FIG. 2 is a flow chart of a full-scale synchronization method;
FIG. 3 is a flow chart of an incremental synchronization method;
fig. 4 is a schematic structural diagram of a system for performing real-time data synchronization based on rsync according to an embodiment of the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For a better understanding of the present application, embodiments of the present application are explained in detail below with reference to the accompanying drawings.
Example one
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a method for performing real-time data synchronization based on rsync according to an embodiment of the present disclosure. As shown in fig. 1, the method for performing real-time data synchronization based on rsync in this embodiment mainly includes the following steps:
s1: and monitoring the file system in real time to obtain monitoring data.
In the data synchronization in this embodiment, a file system in a master server is synchronized to each web server, the master server is a file system server, an rsync server is deployed on the master server, each web server is a slave server, and an rsync client is deployed on the slave server. The file system in this embodiment includes: the method is applicable to both the data transmission of the common magnitude file system and the data transmission of the large magnitude file system, namely, the data transmission of the file system including the constant magnitude level and the data transmission of the file system including the super magnitude level.
The file system of this embodiment is disposed in the main server, and the monitoring data includes: the size of the file system, file attributes, and event files. The event file is used for recording events generated by the file system, and the event file is automatically generated according to the size of the file system and different file attributes. The events include: modify events, add events, delete events, and move events. It should be noted that the event and the file attribute are different, and the file attribute includes different states such as an executable state, a read-only state, and a read-write state.
In specific implementation, a fileMaxSize parameter and an exclude parameter may be defined, where the fileMaxSize parameter is a file size limit value used to obtain the size of the monitored file system, and the exclude is used to specify excluded files and directories. In the embodiment, inotify is adopted to monitor the change of the file system in real time, because one file system change can trigger a plurality of events, the embodiment filters and extracts the occurred events, only extracts modification events, new events, deletion events and movement events, and writes the occurred events into an inotifywatch log, wherein the file is used for counting the access times of the file system and is a file system access time log.
The real-time synchronization method in the embodiment is based on the rsync synchronization transmission tool, utilizes inotify to monitor the main server in real time, judges the events occurring in the file system, can acquire event information in time, and is convenient for executing different data synchronization modes on different events in the next step.
S2: according to the acquired command, a data synchronization frequency of the file system is set.
Specifically, the frequency maxdelay of data synchronization, i.e. the frequency of task execution, may be set in the timer, i.e.: a delay value. The specific data synchronization frequency is determined according to the specific situation of the user file system. The mode of setting the data synchronization frequency can effectively avoid frequent triggering of the rsync, and can ensure the condition of timely realizing data synchronization, thereby greatly saving system resources and improving the overall performance of the server.
S3: and judging whether the size of the current file system is smaller than or equal to a set file system threshold value or not according to the data synchronization frequency.
If the size of the current file system is less than or equal to the set file system threshold, execute step S4: and synchronizing the current file system to each web server in real time by adopting a full-scale synchronization mode.
The method of full-scale synchronization in this embodiment can be seen in fig. 2. As can be seen from fig. 2, the method for full-scale synchronization in this embodiment includes the following steps:
s41: and reading an event file in the monitoring data.
Log, i.e. read event file inotifywatch.
The events recorded by the event file of the embodiment include: modify events, add events, delete events, and move events. According to different events, different steps are respectively executed.
If the event in the event file is a delete event or a move event, execute step S42: and recording the deletion log.
S43: and deleting the corresponding file in the web server according to the deletion log.
The rsync-delete command may be invoked to delete the file corresponding to the client.
If the event in the event file is a new event or a modified event, execute step S44: excluding the set directories and files.
Namely, according to the acquired exception parameter, the set directory file is excluded.
S45: and performing full directory synchronization operation on the file system excluding the set directory and file.
With continued reference to fig. 1, if the size of the current file system is greater than the set file system threshold, step S5 is executed: and synchronizing the current file system to each web server in real time by adopting an incremental synchronization mode.
S51: and reading an event file in the monitoring data.
If the event in the event file is a delete event or a move event, execute step S52: and recording the deletion log.
S53: and deleting the corresponding file in the web server according to the deletion log.
If the event in the event file is a new event or a modified event, execute step S54: and screening and eliminating repeated files according to the event file to generate an execution file.
S55: and incrementally synchronizing the file system content corresponding to the executed file to each Web server by using the rsync.
As can be seen from the above steps S54 and S55, when the event in the event file is a new event or a modified event, the event file in the log file inotifywatch.log is extracted, the duplicate file is filtered out to generate an execution file execute.log, rsync is called, the execute.log is read, and the file in which the event occurs is synchronized.
Further, in the present embodiment, after the step S4 and the step S5, the method further includes a step S6: and deleting files related to the event files in the current file system monitoring data.
The step S6 has different implementations according to different data synchronization modes.
Specifically, after steps S43 and S45, step S46 is performed: and deleting the event file in the current file system monitoring data. Log, the event file inotifywatch is emptied and the next round of the loop is performed.
Log, reading an event file inotifywatch once every time a task is executed, and clearing the event file after the task is finished.
After steps S53 and S55, step S56 is performed: and deleting the execution file and the event file in the current file system monitoring data. Namely: and emptying the event file inotifywatch.log and the execution file execute.log, and performing the next round of circulation.
And when the task is executed once, the event file in the current file system monitoring data is deleted, so that the system resource of the server can be effectively saved, and the overall performance of the server is greatly improved.
Example two
Referring to fig. 4, fig. 4 is a schematic structural diagram of a system for performing real-time data synchronization based on rsync according to an embodiment of the present application. As can be seen from fig. 4, the system for performing real-time data synchronization based on rsync in this embodiment mainly includes: the device comprises a monitoring module, a frequency setting module, a judging module, a full-quantity synchronization module and an increment synchronization module.
Wherein, the monitoring module is used for carrying out real time monitoring to the file system, acquires the monitoring data, and the file system sets up in the main server, and the monitoring data includes: the file system comprises the size, the file attribute and an event file of the file system, wherein the event file is used for recording events occurring in the file system, and the events comprise: modify events, add events, delete events, and move events. And the frequency setting module is used for setting the data synchronization frequency of the file system according to the acquired command. And the judging module is used for judging whether the size of the current file system is less than or equal to a set file system threshold value or not according to the data synchronization frequency. And the full synchronization module is used for synchronizing the current file system to each web server in real time by using rsync in a full synchronization mode when the size of the current file system is smaller than or equal to a set file system threshold value. And the incremental synchronization module is used for synchronizing the current file system to each web server in real time by using rsync in an incremental synchronization mode when the size of the current file system is larger than a set file system threshold value.
Further, the full-scale synchronization module comprises: the device comprises a first reading unit, a first recording unit, a first deleting unit, an excluding unit and a full-scale catalog synchronizing unit. The first reading unit is used for reading an event file in the monitoring data; the first recording unit is used for recording a deletion log when the event in the event file is a deletion event or a movement event; the first deleting unit is used for deleting the corresponding file in the web server according to the deleting log; the exclusion unit is used for excluding the set directory and files according to the acquired exception parameters when the events in the event files are newly added events or modified events; and the full directory synchronization unit is used for executing full directory synchronization operation on the file system excluding the set directories and files.
The incremental synchronization module includes: the device comprises a second reading unit, a second recording unit, a second deleting unit, an execution file generating unit and an incremental file synchronizing unit. The second reading unit is used for reading an event file in the monitoring data; the second recording unit is used for recording a deletion log when the event in the event file is a deletion event or a movement event; the second deleting unit is used for deleting the corresponding file in the web server according to the deleting log; the execution file generation unit is used for screening and eliminating repeated files according to the event file to generate an execution file when the event in the event file is a newly added event or a modified event; and the incremental file synchronization unit is used for incrementally synchronizing the file system content corresponding to the execution file into each Web server by using the rsync.
Further, the system of this embodiment further includes a deleting module, where the deleting module is configured to delete the event file in the current file system monitoring data after synchronizing the current file system to each web server in real time.
For parts of this embodiment that are not described in detail, reference may be made to the first embodiment shown in fig. 1 to fig. 3, and the two embodiments may be referred to each other and are not described again here.
The above description is merely exemplary of the present application and is presented to enable those skilled in the art to understand and practice the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for real-time data synchronization based on rsync, the method comprising:
the method comprises the steps of monitoring a file system in real time to obtain monitoring data, wherein the file system is arranged in a main server, and the monitoring data comprise: the file system comprises the size of the file system, file attributes and an event file, wherein the event file is used for recording events occurring in the file system, and the events comprise: modifying an event, adding an event, deleting an event and moving an event;
setting the data synchronization frequency of the file system according to the acquired command;
judging whether the size of the current file system is smaller than or equal to a set file system threshold value or not according to the data synchronization frequency;
if so, synchronizing the current file system to each web server in real time by using rsync in a full-scale synchronization mode;
if not, the current file system is synchronized to each web server in real time by using the rsync in an incremental synchronization mode.
2. The method of claim 1, wherein the synchronizing the current file system to each web server in real time by using the rsync in a full-scale synchronization manner comprises:
reading an event file in the monitoring data;
if the event in the event file is a deletion event or a movement event, recording a deletion log;
deleting the corresponding file in the web server according to the deletion log;
if the event in the event file is a newly added event or a modified event, excluding the set directory and file;
and performing full directory synchronization operation on the file system excluding the set directory and file.
3. The method of claim 1, wherein the synchronizing the current file system to each web server in real time by using the rsync in an incremental synchronization manner comprises:
reading an event file in the monitoring data;
if the event in the event file is a deletion event or a movement event, recording a deletion log;
deleting the corresponding file in the web server according to the deletion log;
if the event in the event file is a newly added event or a modified event, screening and eliminating repeated files according to the event file to generate an execution file;
and incrementally synchronizing the file system content corresponding to the executed file to each Web server by using the rsync.
4. The method of claim 1, wherein the file system comprises: a common magnitude file system and a large magnitude file system.
5. The method of claim 2, wherein after performing a full directory synchronization operation on the file system excluding the set directories and files, the method further comprises:
and deleting the event file in the current file system monitoring data.
6. The method of claim 3, wherein after the rsync is used to incrementally synchronize the file system content corresponding to the executed file to each Web server, the method further comprises:
and deleting the execution file and the event file in the current file system monitoring data.
7. A system for real-time data synchronization based on rsync, the system comprising:
the monitoring module is used for monitoring a file system in real time to acquire monitoring data, the file system is arranged in the main server, and the monitoring data comprises: the file system comprises the size of the file system, file attributes and an event file, wherein the event file is used for recording events occurring in the file system, and the events comprise: modifying an event, adding an event, deleting an event and moving an event;
the frequency setting module is used for setting the data synchronization frequency of the file system according to the acquired command;
the judging module is used for judging whether the size of the current file system is smaller than or equal to a set file system threshold value or not according to the data synchronization frequency;
the full synchronization module is used for synchronizing the current file system to each web server in real time by using rsync in a full synchronization mode when the size of the current file system is smaller than or equal to a set file system threshold value;
and the incremental synchronization module is used for synchronizing the current file system to each web server in real time by using rsync in an incremental synchronization mode when the size of the current file system is larger than a set file system threshold value.
8. The system of claim 7, wherein the full-scale synchronization module comprises:
the first reading unit is used for reading the event file in the monitoring data;
the first recording unit is used for recording a deletion log when the event in the event file is a deletion event or a movement event;
the first deleting unit is used for deleting the corresponding file in the web server according to the deleting log;
the exclusion unit is used for excluding the set directory and files when the event in the event file is a newly added event or a modified event;
and the full directory synchronization unit is used for executing full directory synchronization operation on the file system excluding the set directories and files.
9. The system of claim 7, wherein the incremental synchronization module comprises:
the second reading unit is used for reading the event file in the monitoring data;
the second recording unit is used for recording a deletion log when the event in the event file is a deletion event or a movement event;
the second deleting unit is used for deleting the corresponding file in the web server according to the deleting log;
the execution file generation unit is used for screening and eliminating repeated files according to the event file to generate an execution file when the event in the event file is a newly added event or a modified event;
and the incremental file synchronization unit is used for incrementally synchronizing the file system content corresponding to the execution file into each Web server by using the rsync.
10. The system for rsync-based real-time data synchronization according to any one of claims 7-9, wherein the system further comprises a deletion module, configured to delete a file related to the event file in the current file system monitoring data after the current file system is synchronized in real time to each web server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010326678.4A CN111538710A (en) | 2020-04-23 | 2020-04-23 | Method and system for real-time data synchronization based on rsync |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010326678.4A CN111538710A (en) | 2020-04-23 | 2020-04-23 | Method and system for real-time data synchronization based on rsync |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111538710A true CN111538710A (en) | 2020-08-14 |
Family
ID=71978969
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010326678.4A Withdrawn CN111538710A (en) | 2020-04-23 | 2020-04-23 | Method and system for real-time data synchronization based on rsync |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111538710A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112416878A (en) * | 2020-11-09 | 2021-02-26 | 山西云时代技术有限公司 | File synchronization management method based on cloud platform |
| CN112667374A (en) * | 2020-12-21 | 2021-04-16 | 苏州浪潮智能科技有限公司 | Thread synchronization method, system and medium |
| CN115348272A (en) * | 2022-08-15 | 2022-11-15 | 四川虹美智能科技有限公司 | Automatic synchronization method and device for server output |
| CN117009309A (en) * | 2023-05-31 | 2023-11-07 | 合芯科技(苏州)有限公司 | File real-time synchronization method and device based on rsync |
| CN118152418A (en) * | 2024-05-09 | 2024-06-07 | 麒麟软件有限公司 | Index database dynamic updating method and system based on inotify |
-
2020
- 2020-04-23 CN CN202010326678.4A patent/CN111538710A/en not_active Withdrawn
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112416878A (en) * | 2020-11-09 | 2021-02-26 | 山西云时代技术有限公司 | File synchronization management method based on cloud platform |
| CN112667374A (en) * | 2020-12-21 | 2021-04-16 | 苏州浪潮智能科技有限公司 | Thread synchronization method, system and medium |
| CN112667374B (en) * | 2020-12-21 | 2023-01-10 | 苏州浪潮智能科技有限公司 | Thread synchronization method, system and medium |
| CN115348272A (en) * | 2022-08-15 | 2022-11-15 | 四川虹美智能科技有限公司 | Automatic synchronization method and device for server output |
| CN117009309A (en) * | 2023-05-31 | 2023-11-07 | 合芯科技(苏州)有限公司 | File real-time synchronization method and device based on rsync |
| CN117009309B (en) * | 2023-05-31 | 2024-05-07 | 合芯科技(苏州)有限公司 | File real-time synchronization method and device based on rsync |
| CN118152418A (en) * | 2024-05-09 | 2024-06-07 | 麒麟软件有限公司 | Index database dynamic updating method and system based on inotify |
| CN118152418B (en) * | 2024-05-09 | 2024-08-13 | 麒麟软件有限公司 | Index database dynamic updating method and system based on inotify |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111538710A (en) | Method and system for real-time data synchronization based on rsync | |
| JP4594928B2 (en) | Flashback database | |
| JP6385336B2 (en) | Telemetry system for cloud synchronization system | |
| JP5731656B2 (en) | Method and computer program for automated and self-adjusting data backup operations | |
| CN106528574A (en) | Data synchronization method and device | |
| CN105389230A (en) | Continuous data protection system and method combining with snapshot technology | |
| CN104750573B (en) | The global coherency backup-and-restore method of distributed data system back end | |
| US20110282843A1 (en) | Method and system for data backup and replication | |
| US11947429B2 (en) | Data disaster recovery method and site | |
| JP2007140700A (en) | Computer system, management computer, storage system and backup management method | |
| CN112597249B (en) | Synchronous distribution storage method and system for service data | |
| CN106339278A (en) | Data backup and recovery method of network file system | |
| CN112667374B (en) | Thread synchronization method, system and medium | |
| CN110990432A (en) | Device and method for synchronizing distributed cache clusters across machine rooms | |
| CN112015593B (en) | Disaster recovery backup method for Kubernetes cluster and related components | |
| WO2012149719A1 (en) | Method and system for establishing checkpoint | |
| CN109684338A (en) | A kind of data-updating method of storage system | |
| CN110188068A (en) | A kind of volume grade backup method and device guaranteeing file system data consistency | |
| WO2013113220A1 (en) | Method and device for backup and recovery of network management configuration data | |
| CN103973486B (en) | A kind of Log Administration System based on B/S structures | |
| US11042454B1 (en) | Restoration of a data source | |
| CN114880167A (en) | Data backup and recovery method, server, distributed system and storage medium | |
| CN111045865A (en) | Real-time synchronization method and system based on block replication | |
| CN114328009A (en) | Unified disaster recovery backup method and device for heterogeneous database based on virtualization and snapshot | |
| CN117520056A (en) | Hbase data backup method, hbase data backup system, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200814 |
|
| WW01 | Invention patent application withdrawn after publication |