CN112596956B - File system management method, device and related components - Google Patents
File system management method, device and related components Download PDFInfo
- Publication number
- CN112596956B CN112596956B CN202011583614.9A CN202011583614A CN112596956B CN 112596956 B CN112596956 B CN 112596956B CN 202011583614 A CN202011583614 A CN 202011583614A CN 112596956 B CN112596956 B CN 112596956B
- Authority
- CN
- China
- Prior art keywords
- server
- file
- file system
- commit
- change information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 53
- 230000008859 change Effects 0.000 claims abstract description 97
- 238000000034 method Methods 0.000 claims abstract description 33
- 230000008569 process Effects 0.000 claims abstract description 26
- 238000004590 computer program Methods 0.000 claims description 9
- 238000012795 verification Methods 0.000 claims description 8
- 238000012986 modification Methods 0.000 claims description 6
- 230000004048 modification Effects 0.000 claims description 6
- 238000007792 addition Methods 0.000 claims description 5
- 238000012217 deletion Methods 0.000 claims description 5
- 230000037430 deletion Effects 0.000 claims description 5
- 230000001960 triggered effect Effects 0.000 claims description 3
- 230000006854 communication Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000004883 computer application Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000013515 script Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1453—Management of the data involved in backup or backup restore using de-duplication of the data
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application discloses a file system management method, a file system management device, electronic equipment and a computer readable storage medium, which are applied to a client, wherein the file system management method comprises the steps of inquiring a reference file system state of a server and a current file system state of the client; judging whether the reference file system state and the current file system state have differences or not; if yes, acquiring file change information, and submitting the file change information to a server for backup so that the server can update the state of the reference file system according to the file change information. The method and the device only backup the changed file increment, reduce the backup data volume, occupy small space, shorten the time required by the backup process and improve the backup efficiency.
Description
Technical Field
The present invention relates to the field of computer operating systems, and in particular, to a method and apparatus for managing a file system, and related components.
Background
In the development process of computers, the operating system of the computer is used as a bridge for connecting computer hardware and software, and plays a role in modern computer technology. The operating system of a computer is the basis for all computer applications, which provides a platform and support for computer applications as well as internet applications. The file system is a basic function of an operating system, and the backup function of the existing file system often adopts an integral disk backup scheme, but the integral backup scheme has larger backup data volume, so that the occupied space is large, the time required by the backup process is long, and the efficiency is low.
Therefore, how to provide a solution to the above technical problem is a problem that a person skilled in the art needs to solve at present.
Disclosure of Invention
The purpose of the application is to provide a file system management method, a device, an electronic device and a computer readable storage medium, which only backup the changed file increment, reduce the backup data volume, occupy small space, shorten the time required by the backup process and improve the backup efficiency.
In order to solve the above technical problems, the present application provides a file system management method, applied to a client, the file system management method includes:
inquiring a reference file system state of a server side and a current file system state of the client side;
judging whether the reference file system state and the current file system state have differences or not;
if yes, acquiring file change information, and submitting the file change information to a server for backup, so that the server can update the state of the reference file system according to the file change information.
Preferably, the file change information includes a change file and metadata corresponding to the change file;
the metadata includes file branches, file sizes, commit reasons and commit logs, the commit reasons including additions and/or modifications and/or deletions.
Preferably, after submitting the file change information to a server for backup, the file system management method further includes:
receiving a commit id, wherein the commit id is an independent id returned after the server receives the file change information;
correspondingly, the process of querying the state of the reference file system of the server side comprises the following steps:
querying a file branch and a commit id corresponding to file change information which are stored by the server and last submitted by the client;
and determining a reference file system state according to the file branch and the commit id.
Preferably, the process of submitting the file change information to a server for backup includes:
and sending a submitting signal to the server, and submitting the file change information to the server for backup after receiving the validity verification confirming signal returned by the server.
Preferably, the process of sending the commit signal to the server includes:
and when the submitting condition is met, sending a submitting signal to the server.
Preferably, the process of submitting the file change information to a server for backup includes:
submitting the file change information to a server, and executing a backup operation through the server, wherein the backup operation comprises the steps of storing the change file into an nfs file system and storing the metadata into a database.
Preferably, the file system management method further includes:
requesting the latest commit id of the server from the server;
judging whether the latest commit id of the server and the latest commit id of the server have differences or not;
if yes, analyzing the difference type, and if the difference type meets the pulling condition, pulling the difference file from the server and storing the difference file to the local.
In order to solve the above technical problem, the present application further provides a file system management device, applied to a client, where the file system management device includes:
the query module is used for querying the reference file system state of the server and the current file system state of the client;
the judging module is used for judging whether the reference file system state and the current file system state have differences or not, and if yes, the submitting module is triggered;
the submitting module is used for acquiring file change information and submitting the file change information to a server for backup so that the server can update the state of the reference file system according to the file change information.
In order to solve the above technical problem, the present application further provides an electronic device, including:
a memory for storing a computer program;
a processor for implementing the steps of the file system management method as claimed in any one of the preceding claims when executing the computer program.
To solve the above technical problem, the present application further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the file system management method according to any one of the above.
The file system management method is characterized in that the client analyzes the difference of files, when the files change, the client actively pushes the file change information to the server for backup, and the server updates the reference file system state according to the file change information, so that the next time the client performs file difference analysis. The application also provides a file system management device, electronic equipment and a computer readable storage medium, which have the same beneficial effects as the file system management method.
Drawings
For a clearer description of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described, it being apparent that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a management system according to the present disclosure;
FIG. 2 is a flowchart illustrating steps of a method for managing a file system according to the present application;
fig. 3 is a schematic structural diagram of a file system management apparatus provided in the present application.
Detailed Description
The core of the application is to provide a file system management method, a device, electronic equipment and a computer readable storage medium, which only backup the changed file increment, reduce the backup data volume, occupy small space, shorten the time required by the backup process and improve the backup efficiency.
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of 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 apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
For convenience in understanding a file system management method provided in the present application, a management system to which the file system management method is applicable will be described below, referring to fig. 1, fig. 1 is a schematic structural diagram of a management system provided in the present application, where the management system includes two components, that is, a server and a client, respectively, the number of clients may be plural, only one client is shown in fig. 1, and the server may exist in a cluster manner, that is, the server may have multiple hosts together, and adopts a distributed deployment manner. As a preferred embodiment, the multiple hosts of the server side comprise a master server and slave servers, so that the availability is improved, and the normal operation of the backup operation is ensured.
The server comprises a communication device, a recording device and a storage device, and the client comprises a difference analysis device, an uploading device, a downloading device, a rollback device and a command line tool.
The following description is made for each device at the service end:
the communication device is used for integrating information in the communication process with the client, monitoring a service port and analyzing the information of the client, and meanwhile, in the cluster mode, the communication device performs communication interaction when a plurality of servers interact; the recording device is used for storing basic information submitted by the server side each time, including information such as files submitted each time, file states, submit ids, submit logs and the like; the storage device is used for storing binary files of the server, the binary files are stored in an nfs file system format so that all hosts of the server can share, the storage device cannot record logic information of the files, and each file is only regarded as a common file.
Explanation is made for each device of the client:
the command line tool is an entry for interaction with a user, the command line tool is a series of scripts providing a way for the user to interact with each device, device to device; the input of the difference analysis device is the file state of the server, the state of the current file system is scanned, and the difference between the files is analyzed through the state of the server and the state of the local machine; the uploading device is used for communicating with the communication device of the server and uploading the file change information to the server; the downloading device is used for communicating with the communication device of the server and downloading the difference file to the client; the rollback device is used for operating the local file system after the downloading device finishes downloading the difference file to be downloaded, and synchronizing the file state of the local file system with the server. And all devices of the client communicate with each other, so that interaction with the server is finally realized, and a local file system is managed in a version mode.
The following describes a file system management method provided by the present application with a client as an execution body.
Referring to fig. 2, fig. 2 is a flowchart illustrating steps of a file system management method provided in the present application, where the file system management method includes:
s101: inquiring the reference file system state of the server and the current file system state of the client;
s102: judging whether the reference file system state and the current file system state have differences, if so, executing S103;
it can be understood that the server side is used as a center of version control and is responsible for storing the change log of the file system and the incremental file of the file system, and the client side cannot communicate with the server side under the condition that the user does not call the command line.
Specifically, all commands supported by the client include, but are not limited to, querying a current system state, querying a current branch state of the server, submitting local file change information to the server, pulling a record of the server to the local, newly building a branch of the server, switching the branch of the server, and the like.
Specifically, the purpose of this step is to determine whether the current file system state of the client changes, send an instruction to the server by the client, obtain the reference file system state stored by the server, scan the local file system, obtain the current file system state, determine whether there is a difference between the reference file system state and the current file system state, and if there is a difference, prompt the information corresponding to the difference, so that after the user sees the information, perform the operation of subsequently submitting file change information.
S103: and acquiring file change information, and submitting the file change information to a server for backup so that the server can update the state of the reference file system according to the file change information.
Specifically, when there is a difference between the reference file system state and the current file system state, file change information is obtained, where the file change information is specifically a changed file increment. The change information comprises but is not limited to a change file and metadata corresponding to the change file, wherein the metadata comprises but is not limited to a file branch, a file size, a submission reason and a submission log, the submission reason comprises new addition and/or modification and/or deletion, and the submission log is written in each submission operation and is used for describing the content information submitted at the time so as to trace the file change later. Specifically, when the file change information is submitted to the server for backup, only the changed file increment is backed up, so that the data volume of backup is reduced, the occupied space is small, and the time required by the backup process is shortened. In this embodiment, the command line may be used to submit local file change information to the server.
As a preferred embodiment, the process of submitting the file change information to the server for backup includes:
and sending a submitting signal to the server, and submitting file change information to the server for backup after receiving the validity verification confirming signal returned by the server.
Specifically, when the client finds that the file system state changes, a commit signal is sent to the server, and after the server receives the commit signal, validity verification is performed on the client, where the validity verification includes, but is not limited to, verifying whether the commit signal is legal, verifying whether the client is within a management range of the server, and the like. When the file is judged to be valid, the server side returns a validity verification confirmation signal to the client side, and the client side submits file change information to the server side for backup after receiving the validity verification confirmation signal.
As a preferred embodiment, the process of sending the commit signal to the server includes:
and when the submitting condition is met, sending a submitting signal to the server.
The commit condition here may be the receipt of a user trigger.
As a preferred embodiment, the process of submitting the file change information to the server for backup includes:
and submitting the file change information to a server, and executing a backup operation through the server, wherein the backup operation comprises the steps of storing the change file into an nfs file system and storing metadata into a database.
Specifically, the change file is a binary file, the change file is stored in an nfs system, and a plurality of servers at the server side can share the nfs system, so that the change file does not need to be stored in each server, and metadata is stored in a database, so that subsequent clients can perform operations such as query, pulling and the like.
As a preferred embodiment, after submitting the file change information to the server for backup, the file system management method further includes:
receiving a commit id, wherein the commit id is an independent id returned after the server receives file change information;
correspondingly, the process of inquiring the state of the reference file system of the server side comprises the following steps:
inquiring file branches and commit ids corresponding to file change information which is stored by a server and is recently submitted by a client;
the reference file system state is determined from the file branch and commit id.
Specifically, when the server receives file change information submitted by the client, an independent commit id is issued for the current commit operation, the commit ids can be issued sequentially or randomly, the fact that the commit ids corresponding to each commit operation are different is guaranteed, and the commit ids can be issued according to tree changes, and can be used for subsequent query and pull operations. Correspondingly, when determining whether the file system state is changed, the client can send a query request to the server through the last received commit id, acquire file change information stored by the server and corresponding to the commit id, and determine the reference file system state through the file change information.
The commit id may specifically identify a code for identifying a version of the file system data, where the code is a string of 32-bit numbers and letters.
Therefore, in this embodiment, the difference of the files is analyzed at the client, when the files change, the client actively pushes the file change information to the server for backup, and updates the reference file system state at the server according to the file change information, so that the next time the client performs file difference analysis.
Based on the above embodiments:
as a preferred embodiment, the file system management method further includes:
requesting the latest commit id of the server from the server;
judging whether the latest commit id of the server and the latest commit id of the server have differences or not;
if yes, analyzing the difference type, and if the difference type meets the pulling condition, pulling the difference file from the server and storing the difference file to the local.
Specifically, when the server record needs to be pulled to the local, the client requests the server for the latest commit id, which can be understood that one server may correspond to a plurality of clients, and it is assumed that the server corresponds to the client A, B, C, and the latest commit id of the server may be generated after receiving the file change information of the client a, or generated after receiving the file change information of the client B, or generated after receiving the file change information of the client C. After the latest commit id of the server is obtained, comparing the latest commit id with the latest commit id received by the server, and judging whether a difference exists, if so, analyzing the difference type, wherein the difference type comprises: the client is behind the server, the client is ahead of the server, and the client is equal to the server. If the client is behind the server, the final state is compared with the current state, the corresponding difference file is downloaded to the client, if the client is ahead of the server, error information is prompted, and if the client is consistent with the server, no processing is performed.
As a preferred embodiment, the present application may also create a server branch, and create a new branch to the server based on the current branch. The method also comprises the operation of switching the branches of the server, and the branches of the server can be switched by the client because the server possibly has a plurality of branches, and the branches are submitted and modified according to the new branches after the switching.
In summary, the file system of the operating system can be subjected to versioning management, so that operations such as backup, rollback and the like of the file system are further refined, batch deployment based on the submitted id can be realized, the fineness and accuracy of file system management are improved, and the efficiency of file management is improved.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a file system management apparatus provided in the present application, applied to a client, the file system management apparatus includes:
the query module 1 is used for querying the reference file system state of the server and the current file system state of the client;
the judging module 2 is used for judging whether the reference file system state and the current file system state have differences, and if so, the submitting module 3 is triggered;
and the submitting module 3 is used for acquiring the file change information and submitting the file change information to the server for backup so that the server can update the state of the reference file system according to the file change information.
Therefore, in this embodiment, the difference of the files is analyzed at the client, when the files change, the client actively pushes the file change information to the server for backup, and updates the reference file system state at the server according to the file change information, so that the next time the client performs file difference analysis.
As a preferred embodiment, the file change information includes a change file and metadata corresponding to the change file;
metadata includes file branches, file size, commit reasons, and commit logs, commit reasons including additions and/or modifications and/or deletions.
As a preferred embodiment, the file system management apparatus further includes:
the feedback module is used for receiving the submitting id, wherein the submitting id is an independent id returned after the server receives the file change information;
correspondingly, the process of inquiring the state of the reference file system of the server side comprises the following steps:
inquiring file branches and commit ids corresponding to file change information which is stored by a server and is recently submitted by a client;
the reference file system state is determined from the file branch and commit id.
As a preferred embodiment, the process of submitting the file change information to the server for backup includes:
and sending a submitting signal to the server, and submitting file change information to the server for backup after receiving the validity verification confirming signal returned by the server.
As a preferred embodiment, the process of sending the commit signal to the server includes:
and when the submitting condition is met, sending a submitting signal to the server.
As a preferred embodiment, the process of submitting the file change information to the server for backup includes:
and submitting the file change information to a server, and executing a backup operation through the server, wherein the backup operation comprises the steps of storing the change file into an nfs file system and storing metadata into a database.
As a preferred embodiment, the file system management apparatus further includes:
and the pulling module is used for requesting the latest commit id of the server to the server, judging whether the latest commit id of the server and the latest commit id of the server have differences, if so, analyzing the difference types, and if the difference types meet the pulling conditions, pulling the difference files from the server and storing the difference files to the local.
In another aspect, the present application further provides an electronic device, including:
a memory for storing a computer program;
a processor for implementing the steps of the file system management method as described in any one of the embodiments above when executing a computer program.
For an introduction to an electronic device provided in the present application, reference is made to the foregoing embodiments, and the description is omitted herein.
The electronic equipment has the beneficial effects of the file system management method.
In another aspect, the present application further provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the file system management method as described in any one of the embodiments above.
For an introduction to a computer readable storage medium provided in the present application, reference is made to the above embodiments, and the description thereof is omitted herein.
The computer readable storage medium provided by the application has the beneficial effects of the file system management method.
It should also be noted that in this specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use 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 (7)
1. A file system management method, applied to a client, comprising:
inquiring a reference file system state of a server side and a current file system state of the client side;
judging whether the reference file system state and the current file system state have differences or not;
if yes, acquiring file change information, and submitting the file change information to a server for backup so that the server can update the state of the reference file system according to the file change information;
the file change information comprises a change file and metadata corresponding to the change file;
the metadata comprises file branches, file sizes, commit reasons and commit logs, wherein the commit reasons comprise new additions and/or modifications and/or deletions;
after submitting the file change information to a server for backup, the file system management method further comprises the following steps:
receiving a commit id, wherein the commit id is an independent id returned after the server receives the file change information;
correspondingly, the process of querying the state of the reference file system of the server side comprises the following steps:
querying a file branch and a commit id corresponding to file change information which are stored by the server and last submitted by the client;
determining a reference file system state according to the file branches and the commit id;
the file system management method further comprises the following steps:
requesting the latest commit id of the server from the server;
judging whether the latest commit id of the server and the latest commit id of the server have differences or not;
if yes, analyzing the difference type, and if the difference type meets the pulling condition, pulling the difference file from the server and storing the difference file to the local.
2. The file system management method according to claim 1, wherein the process of submitting the file change information to a server for backup includes:
and sending a submitting signal to the server, and submitting the file change information to the server for backup after receiving the validity verification confirming signal returned by the server.
3. The file system management method according to claim 2, wherein the process of transmitting a commit signal to the server includes:
and when the submitting condition is met, sending a submitting signal to the server.
4. The file system management method according to claim 1, wherein the process of submitting the file change information to a server for backup includes:
submitting the file change information to a server, and executing a backup operation through the server, wherein the backup operation comprises the steps of storing the change file into an nfs file system and storing the metadata into a database.
5. A file system management apparatus, applied to a client, comprising:
the query module is used for querying the reference file system state of the server and the current file system state of the client;
the judging module is used for judging whether the reference file system state and the current file system state have differences or not, and if yes, the submitting module is triggered;
the submitting module is used for acquiring file change information and submitting the file change information to a server for backup so that the server can update the state of the reference file system according to the file change information;
the file change information comprises a change file and metadata corresponding to the change file;
the metadata comprises file branches, file sizes, commit reasons and commit logs, wherein the commit reasons comprise new additions and/or modifications and/or deletions;
the file system management apparatus further includes:
the feedback module is used for receiving a commit id, wherein the commit id is an independent id returned after the server receives the file change information;
correspondingly, the process of querying the state of the reference file system of the server side comprises the following steps:
querying a file branch and a commit id corresponding to file change information which are stored by the server and last submitted by the client;
determining a reference file system state according to the file branches and the commit id;
the file system management apparatus further includes:
and the pulling module is used for requesting the latest commit id of the server to the server, judging whether the latest commit id of the server and the latest commit id of the server have differences, analyzing the difference types if the latest commit id of the server and the latest commit id of the server have differences, and if the difference types meet the pulling conditions, pulling the difference files from the server and storing the difference files to the local.
6. An electronic device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the file system management method according to any of claims 1-4 when executing said computer program.
7. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the file system management method according to any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011583614.9A CN112596956B (en) | 2020-12-28 | 2020-12-28 | File system management method, device and related components |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011583614.9A CN112596956B (en) | 2020-12-28 | 2020-12-28 | File system management method, device and related components |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112596956A CN112596956A (en) | 2021-04-02 |
| CN112596956B true CN112596956B (en) | 2024-02-13 |
Family
ID=75202854
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011583614.9A Active CN112596956B (en) | 2020-12-28 | 2020-12-28 | File system management method, device and related components |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112596956B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114721881B (en) * | 2022-06-09 | 2022-11-04 | 苏州浪潮智能科技有限公司 | Database management method, system, electronic device and storage medium |
| CN117312264B (en) * | 2023-12-01 | 2024-02-20 | 中孚信息股份有限公司 | File synchronization method, system, equipment and medium in virtual disk system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5634052A (en) * | 1994-10-24 | 1997-05-27 | International Business Machines Corporation | System for reducing storage requirements and transmission loads in a backup subsystem in client-server environment by transmitting only delta files from client to server |
| CN104714755A (en) * | 2013-12-13 | 2015-06-17 | 华为技术有限公司 | Snapshoot management method and device |
| CN106487852A (en) * | 2015-08-31 | 2017-03-08 | 阿里巴巴集团控股有限公司 | Realize the synchronous method of client file, device, terminal unit and system |
| CN108763503A (en) * | 2018-05-30 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of knowledge base management system and method based on enterprise's private clound |
| CN109542851A (en) * | 2018-11-30 | 2019-03-29 | 北京金山云网络技术有限公司 | File updating method, apparatus and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110040788A1 (en) * | 2009-08-14 | 2011-02-17 | Ic Manage, Inc. | Coherent File State System Distributed Among Workspace Clients |
-
2020
- 2020-12-28 CN CN202011583614.9A patent/CN112596956B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5634052A (en) * | 1994-10-24 | 1997-05-27 | International Business Machines Corporation | System for reducing storage requirements and transmission loads in a backup subsystem in client-server environment by transmitting only delta files from client to server |
| CN104714755A (en) * | 2013-12-13 | 2015-06-17 | 华为技术有限公司 | Snapshoot management method and device |
| CN106487852A (en) * | 2015-08-31 | 2017-03-08 | 阿里巴巴集团控股有限公司 | Realize the synchronous method of client file, device, terminal unit and system |
| CN108763503A (en) * | 2018-05-30 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of knowledge base management system and method based on enterprise's private clound |
| CN109542851A (en) * | 2018-11-30 | 2019-03-29 | 北京金山云网络技术有限公司 | File updating method, apparatus and system |
Non-Patent Citations (4)
| Title |
|---|
| Using file-aware deduplication to improve capacity in storage systems;Paul Bartus 等;2017 IEEE Colombian Conference on Communications and Computing (COLCOM);全文 * |
| 基于分区操作系统的文件并行访问方法;杨琼;王冬;;航空计算技术(第05期);全文 * |
| 窄带宽网络环境下的快速文件备份方法;黄建强;胡晓勤;李涛;田诗源;;计算机与现代化(第02期);全文 * |
| 远程文件备份与恢复系统的设计与实现;任欣;李涛;胡晓勤;;计算机工程(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112596956A (en) | 2021-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8667031B2 (en) | Reuse of shared metadata across applications via URL protocol | |
| KR101376916B1 (en) | Techniques to perform gradual upgrades | |
| US8250102B2 (en) | Remote storage and management of binary object data | |
| US7624116B2 (en) | System and method for managing objects according to the common information model | |
| US8689179B2 (en) | Transportable refactoring object | |
| US20100205475A1 (en) | Meta-data driven, service-oriented architecture (soa)-enabled, application independent interface gateway | |
| US20100131940A1 (en) | Cloud based source code version control | |
| CN112596956B (en) | File system management method, device and related components | |
| CN107038519B (en) | Method and system for bidirectional data synchronization between systems | |
| CN111356996A (en) | Versioning verification of data transfers between heterogeneous data stores | |
| CN107025108B (en) | Exporting hierarchical data from a Source Code Management (SCM) system to a Product Lifecycle Management (PLM) system | |
| US7529750B2 (en) | Accessing information on a network | |
| US20080133543A1 (en) | System and Method for Dynamic and On-Demand Data Transfer and Synchronization Between Isolated Networks | |
| US8321854B1 (en) | Client with flexible grammar-base syntax | |
| CN113626416A (en) | Data verification method and device, computing equipment and storage medium | |
| CN116070294B (en) | Authority management method, system, device, server and storage medium | |
| US11327746B2 (en) | Reduced processing loads via selective validation specifications | |
| CA2470093A1 (en) | Preparing associated files for storage in a server | |
| CN116501700A (en) | APP formatted file offline storage method, device, equipment and storage medium | |
| KR101762861B1 (en) | Programmable computation system using one or more function modules, method for processing information using one or more function modules and computer program for the same | |
| US7761418B2 (en) | Method and product for sharing logged data objects within a distributed storage system | |
| CN111104125B (en) | Intelligent integrated version management method, device, medium and electronic equipment | |
| US20060190472A1 (en) | System and method for improved exposure of database schema information | |
| US20050108194A1 (en) | System for verifying a state of an environment | |
| US11775356B2 (en) | Method and system for facilitating backwards compatibility of a rest API on an evolving data model |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |