CN109241004B - Metadata file size recovery method, system, device and readable storage medium - Google Patents
Metadata file size recovery method, system, device and readable storage medium Download PDFInfo
- Publication number
- CN109241004B CN109241004B CN201811125459.9A CN201811125459A CN109241004B CN 109241004 B CN109241004 B CN 109241004B CN 201811125459 A CN201811125459 A CN 201811125459A CN 109241004 B CN109241004 B CN 109241004B
- Authority
- CN
- China
- Prior art keywords
- file
- update
- target
- metadata
- target file
- 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
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000011084 recovery Methods 0.000 title claims description 27
- 238000013523 data management Methods 0.000 claims abstract description 47
- 238000007726 management method Methods 0.000 claims abstract description 32
- 238000004590 computer program Methods 0.000 claims description 10
- 239000000126 substance Substances 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Abstract
The application discloses a method, a system, a device and a computer readable storage medium for recovering the size of a metadata file, which utilizes an event log generated when a client updates a file after a cluster fault of a distributed file management system occurs to judge whether a file updating mark for reflecting the condition that the client does not update the metadata after updating the file exists in the event log so as to know which file cannot be updated in time in the updating process, then utilizes the file updating mark to generate a file size query instruction to be sent to a data management server so as to utilize the data management server to obtain the actual size information of a target file, and then utilizes the data management server to update the metadata file size information of the target file after obtaining the actual size information of the target file, thereby ensuring that the metadata file size information of the target file is consistent with the actual size information of the target file, the file data loss caused by faults is avoided, and the reliability and the stability of the distributed file system are improved.
Description
Technical Field
The present invention relates to the field of distributed file storage, and in particular, to a method, system, apparatus, and computer-readable storage medium for recovering a metadata file size.
Background
In a distributed file system cluster, when a client updates data to a file in the distributed file system cluster, the data updating and metadata updating are generally separated asynchronously for performance consideration, namely, the data is updated to a data management server, the data is considered to be updated successfully after the data is updated, and in the subsequent time, the client updates metadata information such as the size of the file cached in a memory and the like to the metadata management server by using an asynchronous metadata updating method; however, asynchronous updating of metadata may also cause a problem that the size of the file metadata is incorrect while the performance is improved, for example, data is updated to the data management server, but the client has not updated new size information to the metadata management server, and the file metadata information cached by the client is permanently lost due to power failure or downtime of a node where the client is located.
Therefore, in order to improve the stability and reliability of the distributed file system cluster, a metadata file size recovery method is needed.
Disclosure of Invention
In view of the above, the present invention is directed to a method, a system, a device, and a computer readable storage medium for recovering a size of a metadata file, which can recover the size of the metadata file after a failure and improve stability and reliability of a distributed file system cluster. The specific scheme is as follows:
a metadata file size recovery method, comprising:
judging whether a file updating mark exists in the event record log or not;
if the target file exists, generating a file size query instruction by using the file updating mark, and sending the file size query instruction to a data management server so as to enable the data management server to obtain the actual size information of the target file corresponding to the file updating mark;
receiving and utilizing the actual size information of the target file sent by the data management server to update the metadata file size information of the target file;
wherein the file update flag in the event log is generated when the client updates the target file.
Optionally, the process of generating a file size query instruction by using the file update flag and sending the file size query instruction to the data management server includes:
generating the file size query instruction by using the update range section of the target file recorded in the file update mark and the target iNode corresponding to the target file;
sending the file size query instruction to the data management server;
and the update range section of the target file is allocated when the client updates the target file.
Optionally, before the determining whether the file update flag exists in the event log, the method further includes:
receiving an update request of the client to the target file;
generating a file update mark corresponding to the target file by using the update request;
saving the file update mark to the event record log;
and sending the file updating mark to the client to allow the client to update the target file.
Optionally, the process of generating the file update flag corresponding to the target file by using the update request includes:
and generating an updating range section corresponding to the target file by using the updating request.
The invention also discloses a metadata file size recovery system, which comprises:
the mark judging module is used for judging whether a file updating mark exists in the event log;
the size query module is used for generating a file size query instruction by using the file updating mark and sending the file size query instruction to a data management server when the mark judgment module judges that the file updating mark exists, so that the data management server obtains the actual size information of the target file corresponding to the file updating mark;
the size updating module is used for receiving and utilizing the actual size information of the target file sent by the data management server to update the metadata file size information of the target file;
wherein the file update flag in the event log is generated when the client updates the target file.
Optionally, the size query module includes:
the instruction generating unit is used for generating the file size query instruction by utilizing the update range section of the target file recorded in the file update mark and the target iNode corresponding to the target file;
the instruction sending unit is used for sending the file size query instruction to the data management server;
and the update range section of the target file is allocated when the client updates the target file.
Optionally, the method further includes:
a request receiving module, configured to receive an update request of the client for the target file;
a tag generation module, configured to generate, by using the update request, a file update tag corresponding to the target file;
the mark storage module is used for storing the file updating mark into the event record log;
and the mark sending module is used for sending the file updating mark to the client so as to allow the client to update the target file.
Optionally, the tag generating module is specifically configured to generate an update range segment corresponding to the target file by using the update request.
The invention also discloses a device for recovering the size of the metadata file, which comprises:
a memory for storing a computer program;
a processor for executing said computer program to implement a metadata file size recovery method as described above.
The invention also discloses a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the metadata file size recovery method as described above.
In the invention, the method for recovering the size of the metadata file comprises the following steps: judging whether a file updating mark exists in the event record log or not; if the target file exists, generating a file size query instruction by using the file updating mark, and sending the file size query instruction to the data management server so as to enable the data management server to obtain the actual size information of the target file corresponding to the file updating mark; receiving and updating the metadata file size information of the target file by using the actual size information of the target file sent by the data management server; and the file updating mark in the event record log is generated when the client updates the target file.
After cluster failure of the distributed file management system occurs, the invention judges whether a file updating mark for reflecting the condition that metadata is not updated after a client updates a file exists in the event log by utilizing the event log generated when the client updates the file to know which file cannot be updated in time in the updating process, then utilizes the file updating mark to generate a file size query instruction to be sent to the data management server so as to utilize the data management server to obtain the actual size information of a target file, update the metadata file size information of the target file after obtaining the actual size information of the target file, and recover the metadata file size information after failure, thereby ensuring that the metadata file size information of the target file is consistent with the actual size information of the target file, and avoiding file data loss caused by failure, the reliability and the stability of the distributed file system are improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention 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, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a schematic flowchart illustrating a metadata file size recovery method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a metadata file size recovery system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
The embodiment of the invention discloses a method for recovering the size of a metadata file, which is shown in figure 1 and comprises the following steps:
it should be noted that, when a client needs to update data to a target file, for example, when the client writes new data to the target file or deletes old data in the target file, the metadata management server receives an update request from the client to the target file, the metadata management server records the update event in an event log by using the update request, and at the same time, generates a file update flag corresponding to the target file by using the update request, and stores the file update flag in the event log to indicate that the target file is being updated by the client, the metadata management server sends the file update flag to the client to allow the client to update the target file, after the client closes the file, the subsequent client asynchronously updates the file size to the metadata management server by using a background thread, and the metadata management server receives update information sent by the client, and the metadata management server eliminates the file update mark of the target file in the event record log while updating by using the update information, and indicates that the target file is updated by the client.
S11: and judging whether a file updating mark exists in the event record log or not.
Specifically, in the actual application process, if the distributed file management system cluster fails, the event log is entered to search whether a file update flag exists, and if so, the case that the metadata is not updated after the file is updated by the client exists when the failure occurs is indicated.
It can be understood that there may be a case where a plurality of clients respectively update a plurality of different files at the same time, and therefore, a plurality of file update markers belonging to different files may also be recorded in the event log, and the metadata file size recovery procedures adopted for the plurality of file update markers belonging to different files are all the same.
S12: and if so, generating a file size query instruction by using the file updating mark and sending the file size query instruction to the data management server so as to enable the data management server to obtain the actual size information of the target file corresponding to the file updating mark.
Specifically, the file update mark corresponds to the target file, so that the feature information of the target file can be obtained by using the file update mark, and the file size query instruction generated by using the file update mark includes the feature information of the target file, so that the data management server can find the target file by using the feature information of the target file after receiving the file size query instruction, and query the file object of the target file to obtain the actual size information of the target file.
It will be appreciated that if not, this indicates that no client has updated the file during the failure, and therefore no data loss occurs, so no recovery is required and no action is taken.
S13: and receiving and updating the metadata file size information of the target file by using the actual size information of the target file sent by the data management server.
Specifically, the metadata file size information of the target file can be updated by receiving the actual size information of the target file sent by the data management server, so that the metadata file size information of the file can be automatically recovered after the distributed file management system cluster fails, and the loss of data is avoided.
It can be seen that, in the embodiments of the present invention, after a cluster failure occurs in the distributed file management system, an event log generated when a client updates a file is used to determine whether a file update flag for reflecting a situation that metadata is not updated after the client updates the file exists in the event log, so as to know which file is not updated in time in an update process, and then a file size query instruction is generated by using the file update flag and sent to the data management server, so that the data management server is used to obtain actual size information of a target file, and after the actual size information of the target file is obtained, the metadata file size information of the target file is updated, and the metadata file size information can be recovered after the failure, thereby ensuring that the metadata file size information of the target file is consistent with the actual size information of the target file, and avoiding file data loss caused by the failure, the reliability and the stability of the distributed file system are improved.
The embodiment of the invention discloses a specific metadata file size recovery method, and compared with the previous embodiment, the embodiment further describes and optimizes the technical scheme. Specifically, the method comprises the following steps:
in practical application, because files are stored in the data management server in the form of a plurality of file objects, and the number of file objects of the files is huge, when the data management server searches the actual file size of a target file, a large number of file objects of the target file need to be traversed to find the last effective file object, so that the actual file size of the target file is determined, the time consumption is large, the efficiency is low, and therefore, in order to improve the efficiency, an update range section of the target file is recorded in a file update mark.
It should be noted that, before the client needs to update data to the target file, the metadata management server needs to request to allocate an update scope section of the target file to the metadata management server, and the metadata management server generates and allocates an update scope section of the target file to the client by using the update request, for example, when the client needs to write data to the target file, the metadata management server applies for the update scope section of the target file to the metadata management server, the metadata management server allocates an update scope section of 0M to 16M of the target file, which means that the client can write freely in this section of the target file, when the client needs to reduce the target file, the metadata management server can allocate an update scope section of 16M to 32M for the client to reduce the target file, and the client performs an update operation in the update scope section of the target file, following an asynchronous update rule, namely, only data needs to be updated to a data management server, the update is considered to be successful, a subsequent client asynchronously updates the size of a file to a metadata management server through a background thread, when the client finishes using or will finish using an update range section, an operation of synchronously updating metadata is performed once, the metadata management server updates a target file to the correct size and applies for a new update range section to the metadata management server, the metadata management server redistributes the new update range section, for example, when the client writes, the update range section of 0M-16M of the target file is written, the metadata management server redistributes the update range section of 16M-32M of the target file for the client to write, when the client shrinks, the update range section of 16M-32M of the target file is shrunk, the metadata management server reallocates the update range segment of 0M-16M of the target file for client reduction.
Wherein the reduction of the file refers to deleting old data in the file.
Meanwhile, when the client updates the target file, the metadata management server records the update event in the event log and stores the current update range section of the target file, for example, the metadata management server allocates an update range section of 0M to 16M to the target file for the first time, the update range section of the target file recorded in the event log is 0M to 16M, when the metadata management server allocates an update range section of 16M to 32M to the target file for the second time, the update range section of the target file recorded in the event log is 16M to 32M, when the client closes the target file, the client performs a synchronous update operation of the metadata, and simultaneously, after receiving a request for closing the file, the metadata management server updates the size of the file to the correct size, and sets the update range section of the target file in the event log to none, e.g., 0.
Specifically, the process of generating the file size query instruction by using the file update flag and sending the file size query instruction to the data management server in S12 may specifically include S121 and S122:
s121: generating a file size query instruction by using the update range section of the target file recorded in the file update mark and the target iNode corresponding to the target file;
s122: and sending the file size query instruction to a data management server.
Specifically, the file update flag may record a target iNode of the target file as the characteristic information of the target file, the data management server may search the target file using the target iNode, and at the same time, the data management server may reduce the search range of the file object of the target file using the update range section, thereby greatly increasing the query speed, so that, after receiving the target iNode and the update range section including the target file, the data management server may rapidly determine the queried file as the target file using the target iNode, and rapidly reduce the search range among the plurality of file objects of the target file using the update range section, thereby rapidly searching the last valid file object of the target file to obtain the actual size information of the target file, for example, the target file includes 1024 file objects, the update range section defines the last valid file object between the 356 nd file object and the 578 th file object, the query range is reduced from 1024 to 222, and the query speed and the work efficiency are greatly improved.
Correspondingly, the embodiment of the present invention further discloses a metadata file size recovery system, as shown in fig. 2, the system includes:
a mark judging module 11, configured to judge whether a file update mark exists in the event log;
a size query module 12, configured to, when the flag determination module 11 determines that the file update flag exists, generate a file size query instruction by using the file update flag, and send the file size query instruction to the data management server, so that the data management server obtains actual size information of the target file corresponding to the file update flag;
a size updating module 13, configured to receive and update metadata file size information of the target file according to actual size information of the target file sent by the data management server;
and the file updating mark in the event record log is generated when the client updates the target file.
Specifically, the size query module 12 may include an instruction generating unit and an instruction sending unit; wherein the content of the first and second substances,
the instruction generating unit is used for generating a file size query instruction by utilizing the update range section of the target file recorded in the file update mark and the target iNode corresponding to the target file;
the instruction sending unit is used for sending the file size query instruction to the data management server;
the update range section of the target file is allocated when the client updates the target file.
Furthermore, the metadata file size recovery system can also comprise a request receiving module, a mark generating module, a mark storing module, a mark sending module and a mark clearing module; wherein the content of the first and second substances,
the request receiving module is used for receiving an update request of a client to a target file;
the mark generating module is used for generating a file updating mark corresponding to the target file by utilizing the updating request;
the mark storage module is used for storing the file updating mark into the event record log;
and the mark sending module is used for sending the file updating mark to the client so as to allow the client to update the target file.
Specifically, the tag generating module may be specifically configured to generate an update range section corresponding to the target file by using the update request.
In addition, the embodiment of the invention also discloses a device for recovering the size of the metadata file, which comprises:
a memory for storing a computer program;
a processor for executing a computer program to implement a metadata file size recovery method as described above.
For specific contents of the foregoing metadata file size recovery method, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not described herein again.
In addition, the embodiment of the present invention further discloses a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the metadata file size recovery method are implemented.
For specific contents of the foregoing metadata file size recovery method, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not described herein again.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be 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. Also, 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 an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The method, system, apparatus and computer-readable storage medium for restoring metadata file size provided by the present invention are described in detail above, and a specific example is applied in the present document to explain the principle and implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A metadata file size recovery method is applied to a metadata management server and comprises the following steps:
judging whether a file updating mark exists in the event record log or not;
if the target file exists, generating a file size query instruction by using the file updating mark, and sending the file size query instruction to a data management server so as to enable the data management server to obtain the actual size information of the target file corresponding to the file updating mark;
receiving and utilizing the actual size information of the target file sent by the data management server to update the metadata file size information of the target file;
wherein the file update flag in the event log is generated when the client updates the target file.
2. The method for restoring the size of a metadata file according to claim 1, wherein the step of generating a file size query instruction by using the file update flag and sending the file size query instruction to a data management server comprises:
generating the file size query instruction by using the update range section of the target file recorded in the file update mark and the target iNode corresponding to the target file;
sending the file size query instruction to the data management server;
and the update range section of the target file is allocated when the client updates the target file.
3. The metadata file size recovery method according to claim 1 or 2, wherein before determining whether the file update flag exists in the event log, the method further comprises:
receiving an update request of the client to the target file;
generating a file update mark corresponding to the target file by using the update request;
saving the file update mark to the event record log;
and sending the file updating mark to the client to allow the client to update the target file.
4. The method of claim 3, wherein said generating a file update tag corresponding to said target file using said update request comprises:
and generating an updating range section corresponding to the target file by using the updating request.
5. A metadata file size recovery system, applied to a metadata management server, comprising:
the mark judging module is used for judging whether a file updating mark exists in the event log;
the size query module is used for generating a file size query instruction by using the file updating mark and sending the file size query instruction to a data management server when the mark judgment module judges that the file updating mark exists, so that the data management server obtains the actual size information of the target file corresponding to the file updating mark;
the size updating module is used for receiving and utilizing the actual size information of the target file sent by the data management server to update the metadata file size information of the target file;
wherein the file update flag in the event log is generated when the client updates the target file.
6. The metadata file size recovery system of claim 5, wherein the size query module comprises:
the instruction generating unit is used for generating the file size query instruction by utilizing the update range section of the target file recorded in the file update mark and the target iNode corresponding to the target file;
the instruction sending unit is used for sending the file size query instruction to the data management server;
and the update range section of the target file is allocated when the client updates the target file.
7. The metadata file size recovery system according to claim 5 or 6, further comprising:
a request receiving module, configured to receive an update request of the client for the target file;
a tag generation module, configured to generate, by using the update request, a file update tag corresponding to the target file;
the mark storage module is used for storing the file updating mark into the event record log;
and the mark sending module is used for sending the file updating mark to the client so as to allow the client to update the target file.
8. The metadata file size recovery system according to claim 7, wherein the tag generation module is specifically configured to generate, by using the update request, an update range segment corresponding to the target file.
9. A metadata file size recovery apparatus, comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the metadata file size recovery method as claimed in any one of claims 1 to 4.
10. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of a metadata file size recovery method as claimed in any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811125459.9A CN109241004B (en) | 2018-09-26 | 2018-09-26 | Metadata file size recovery method, system, device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811125459.9A CN109241004B (en) | 2018-09-26 | 2018-09-26 | Metadata file size recovery method, system, device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109241004A CN109241004A (en) | 2019-01-18 |
| CN109241004B true CN109241004B (en) | 2022-02-18 |
Family
ID=65056226
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811125459.9A Active CN109241004B (en) | 2018-09-26 | 2018-09-26 | Metadata file size recovery method, system, device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109241004B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110647514B (en) * | 2019-08-23 | 2022-07-08 | 北京浪潮数据技术有限公司 | Metadata updating method and device and metadata server |
| CN110807000B (en) * | 2019-10-25 | 2022-06-10 | 北京达佳互联信息技术有限公司 | File repair method and device, electronic equipment and storage medium |
| CN113672419B (en) * | 2021-08-09 | 2024-01-02 | 中标软件有限公司 | Log record protection method suitable for domestic operating system |
| CN113886352B (en) * | 2021-10-21 | 2024-02-23 | 济南浪潮数据技术有限公司 | Metadata recovery method, device, equipment and medium of distributed file system |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103067418A (en) * | 2011-10-19 | 2013-04-24 | 北大方正集团有限公司 | Method, device and system for reconstructing metadata |
| CN102567445B (en) * | 2011-10-25 | 2014-07-02 | 无锡城市云计算中心有限公司 | Method for guaranteeing consistency of metadata in distributed file system |
| CN102662795A (en) * | 2012-03-20 | 2012-09-12 | 浪潮电子信息产业股份有限公司 | Metadata fault-tolerant recovery method in distributed storage system |
| CN103150394B (en) * | 2013-03-25 | 2014-07-23 | 中国人民解放军国防科学技术大学 | Distributed file system metadata management method facing to high-performance calculation |
| US20160170842A1 (en) * | 2013-07-29 | 2016-06-16 | Hewlett-Packard Development Company, L.P. | Writing to files and file meta-data |
| CN103997517B (en) * | 2014-05-06 | 2017-10-24 | 广州金山网络科技有限公司 | A kind of CDN node file synchronisation method and device |
| US20160019317A1 (en) * | 2014-07-16 | 2016-01-21 | Commvault Systems, Inc. | Volume or virtual machine level backup and generating placeholders for virtual machine files |
| CN106911743B (en) * | 2015-12-23 | 2019-03-26 | 中兴通讯股份有限公司 | Small documents write polymerization, read polymerization and system and client |
| CN107480010A (en) * | 2017-08-21 | 2017-12-15 | 郑州云海信息技术有限公司 | A kind of method and device for recovering metadata |
| CN107506147B (en) * | 2017-08-29 | 2020-05-29 | 郑州云海信息技术有限公司 | Method and system for keeping consistency of metadata |
| CN108563743A (en) * | 2018-04-12 | 2018-09-21 | 郑州云海信息技术有限公司 | A kind of file read/write method, system and equipment and storage medium |
-
2018
- 2018-09-26 CN CN201811125459.9A patent/CN109241004B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109241004A (en) | 2019-01-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109241004B (en) | Metadata file size recovery method, system, device and readable storage medium | |
| US11799959B2 (en) | Data processing method, apparatus, and system | |
| US20230117542A1 (en) | Remote Data Replication Method and System | |
| US8606759B2 (en) | Apparatus, system and method for recovering meta data using fragmentary information | |
| US11269902B2 (en) | Time series data management method, device, and apparatus | |
| CN106776130B (en) | Log recovery method, storage device and storage node | |
| CN109284073B (en) | Data storage method, device, system, server, control node and medium | |
| US20160041885A1 (en) | Data Replicating System, Data Replicating Method, Node Device, Management Device and Computer Readable Medium | |
| CN106445643B (en) | It clones, the method and apparatus of upgrading virtual machine | |
| WO2012076342A1 (en) | Clustered redirect on write filesystem | |
| CN107451013B (en) | Data recovery method, device and system based on distributed system | |
| CN108255638B (en) | Snapshot rollback method and device | |
| CN105574187A (en) | Duplication transaction consistency guaranteeing method and system for heterogeneous databases | |
| CN110647514B (en) | Metadata updating method and device and metadata server | |
| US9146921B1 (en) | Accessing a file system during a file system check | |
| CN110245129B (en) | Distributed global data deduplication method and device | |
| WO2018059239A1 (en) | Method and device for file storage | |
| CN102708166B (en) | Data replication method, data recovery method and data recovery device | |
| CN113687783B (en) | Object aggregation method, system, device and computer storage medium | |
| US10275509B2 (en) | Replica checkpointing without quiescing | |
| WO2019072088A1 (en) | File management method, file management device, electronic equipment and storage medium | |
| CN108271420A (en) | Manage method, file system and the server system of file | |
| CN113886352A (en) | Metadata recovery method, device, equipment and medium for distributed file system | |
| CN113590380A (en) | Database recovery method and system | |
| CN107577433B (en) | Storage medium and file data migration method, device and equipment |
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 |