CN105404645A - File management method in file server system and file server system - Google Patents
File management method in file server system and file server system Download PDFInfo
- Publication number
- CN105404645A CN105404645A CN201510707012.2A CN201510707012A CN105404645A CN 105404645 A CN105404645 A CN 105404645A CN 201510707012 A CN201510707012 A CN 201510707012A CN 105404645 A CN105404645 A CN 105404645A
- Authority
- CN
- China
- Prior art keywords
- file
- server
- server node
- server system
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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/18—File system types
- G06F16/185—Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof
-
- 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/11—File system administration, e.g. details of archiving or snapshots
- G06F16/113—Details of archiving
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a file management method in a file server system and the file server system. The method comprises the steps that when uploading a file to the file server system, a client uploads a to-be-uploaded file to a server node connected with the client, and the server node receives and stores the file uploaded by the client; the server node obtains information of other server nodes running normally through zookeeper, one or more of the other server nodes running normally are randomly selected to perform backup on the uploaded file, and a file backup list is established and uploaded to an index server; when the client downloads the file, the server node firstly retrieves whether the required file is stored in a local end of the server node or not, and if yes, the file is directly downloaded; and if not, the server node list that backs up the file required by the client is obtained, the server nodes running normally in the server node list are obtained, and one of the server nodes running normally is arbitrarily selected to obtain the required file for downloading.
Description
Technical field
The application relates to computer server technical field, specifically, relates to the file management method in a kind of file server system and system.
Background technology
Along with the development of informationization technology, file effectively manages the project having become many enterprises and institutions and very paid attention to.File management can comprise uploading, back up and downloading of file.File backup refers to as anti-locking system occurs that misoperation or the system failure cause File lose, and all or part of file set is copied to the process of other storage medium from the hard disk of applied host machine or array.File, document or historical record important inside a lot of enterprises and institutions computer, vital to enterprises and institutions user, accidentally lose for the moment, immeasurable loss is caused in capital, light then the arduous painstaking effort accumulated are irrevocably lost, serious meeting affects the normal operation of enterprises and institutions, causes huge loss to work.In order to ensure the normal operation of producing and selling, exploitation, file backup is quite important.Enterprises and institutions have a large amount of files to need to upload onto the server to preserve, and traditional file management system is very low to the efficiency of fragmented file process, therefore, uploading, back up and download and having become more and more user's problems faced of file can how effectively be carried out.
Summary of the invention
In view of this, technical problems to be solved in this application there is provided file management method in a kind of file server system and system, it is by the pattern of large files block management small documents block, not only ensure that the normal operation of file server system, effectively can also improve the uploading of file, back up, the file management efficiency such as download.
In order to solve the problems of the technologies described above, the application has following technical scheme:
A file management method in file server system, is characterized in that, comprising:
When client is to file server system upload file, by connected server node in files passe to be uploaded to described file server system, this server node receives and preserves the file of described client upload;
According to the file backup strategy preset, the server node receiving described client upload file obtains the information of normal other server nodes run by the zookeeper in described file server system, and select at random one or morely to back up described upload file from other server nodes of described normal operation, set up file backup inventory, and this file backup list is uploaded to the index server in described file server system;
When described client is from described file server system download file, first retrieve its this locality with the server node of this client's side link and whether preserve file needed for client, if preserve this file, then directly file needed for client is provided to described client downloads; If do not preserve this file, then first this server node obtains from described index server the server node list that backup has file needed for client, the server node of normal operation in described server node list is obtained again by the zookeeper in described file server system, from the server node of described normal operation, finally choose arbitrarily a server node obtain file needed for client, for described client downloads.
Preferably, wherein, each described server node in described file server system comprises at least one archive large files block, and each archive large files block comprises multiple fileblock small documents block; When described server node receives new file, this file is saved in described fileblock small documents block.
Preferably, wherein individual, each described server node in described file server system comprises a local index, and described server node is retrieved local file by described local index.
Preferably, wherein, the frequency of each described server node in described file server system to download file is from it added up, and according to the download policy preset, the file at least comprising the highest file of download frequency is saved to this server node local.
Preferably, wherein, described file backup inventory comprises: the fileinfo of institute's backup file, and described fileinfo comprises: index mark, file size, the side-play amount of file in archive, checking mark, deletion mark in one or more.
A kind of file server system, is characterized in that, comprise at least one server node, index server, zookeeper and client, wherein,
At least one server node described: in files passe process, receives and preserves the file of described client upload; For in file backup process, file is backed up, set up file backup inventory, and file backup inventory is uploaded to described index server; For in file download process, obtain file needed for client, for described client downloads from local or other server nodes normally run;
Described index server: for receiving the file backup inventory that described server node is uploaded, and provide the server node list of file needed for client to the described server node of filing a request;
Described zookeeper: for providing the server node of normal operation in described file server system to the described server node of filing a request;
Described client: for described file server system upload file, by server node connected in files passe to be uploaded to server system, and for from file server system download file.
Preferably, wherein, each described server node comprises at least one archive large files block, and each archive large files block comprises multiple fileblock small documents block; When described server node receives new file, this file is saved in described fileblock small documents block.
Preferably, wherein, each described server node comprises a local index, and described server node is retrieved local file by described local index.
Preferably, wherein, the file at least comprising the highest file of download frequency, also for adding up the frequency of download file from it, according to the download policy preset, is saved to this server node local by each described server node.
Preferably, wherein, described file backup inventory comprises the fileinfo of institute's backup file, described fileinfo comprise index mark, file size, the side-play amount of file in archive, checking mark, deletion mark in one or more.
Compared with prior art, the method and system described in the application, reaches following effect:
First, in the file management method of file server system provided by the present invention and file server system, the file of client upload can backup in the multiple or whole server node in file server system, in file server system operational process, even if having one or several server node to break down cannot normally run, client also can get required file from other nodes, therefore can not affect file server system to continue externally to provide service, the normal operation of file server system can be ensured.
Second, server node in file server system of the present invention comprises at least one archive large files block, each archive large files block comprises multiple fileblock small documents block, file backup is in each fileblock small documents block, thus achieve a server node and manage multiple large files block, each large files block manages again the network structure of multiple small documents block respectively, ff transfer efficiency between server node is significantly improved, thus effectively improves the file activity of whole system.
3rd, in file server system of the present invention, the memory location of each file can be named according to each server node, without the need to concrete IP address binding, if certain server node occurs abnormal, file server system is finished the work automatically switching to available server node.
4th, in file server system of the present invention, each described server node can also be added up the frequency of download file from it, according to the download policy preset, the file at least comprising the highest file of download frequency is saved to this server node local, client is if any download demand, directly can downloading from server node this locality, without the need to transferring from other server nodes again, effectively improve download efficiency.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide further understanding of the present application, and form a application's part, the schematic description and description of the application, for explaining the application, does not form the improper restriction to the application.In the accompanying drawings:
Fig. 1 is the file management method process flow diagram in described a kind of file server system of the present invention;
Fig. 2 is the structural representation of described file server system of the present invention;
Fig. 3 is a kind of Application Example schematic diagram of described file server system of the present invention.
Embodiment
As employed some vocabulary to censure specific components in the middle of instructions and claim.Those skilled in the art should understand, and hardware manufacturer may call same assembly with different noun.This specification and claims are not used as with the difference of title the mode distinguishing assembly, but are used as the criterion of differentiation with assembly difference functionally." comprising " as mentioned in the middle of instructions and claim is in the whole text an open language, therefore should be construed to " comprise but be not limited to "." roughly " refer to that in receivable error range, those skilled in the art can solve the technical problem within the scope of certain error, reach described technique effect substantially.In addition, " couple " word and comprise directly any and indirectly electric property coupling means at this.Therefore, if describe a first device in literary composition to be coupled to one second device, then represent described first device and directly can be electrically coupled to described second device, or be indirectly electrically coupled to described second device by other devices or the means that couple.Instructions subsequent descriptions is implement the better embodiment of the application, and right described description is for the purpose of the rule that the application is described, and is not used to the scope limiting the application.The protection domain of the application is when being as the criterion depending on the claims person of defining.
Embodiment 1
Specific embodiment for the file management method in file server system a kind of described in the application shown in Figure 1, method described in the present embodiment (see Fig. 1) comprises the following steps:
Step 101, files passe: when client is to file server system upload file, by server node connected in files passe to be uploaded to file server system, this server node receives and preserves the file of described client upload;
Step 102, file backup: according to the file backup strategy preset, the server node receiving client upload file obtains the information of normal other server nodes run by the zookeeper in file server system, and select at random one or morely to back up described upload file from other server nodes of described normal operation, set up file backup inventory, and file backup inventory is uploaded to the index server in file server system;
Step 103, file download: when client is from file server system download file, first retrieve its this locality with the server node of this client's side link and whether preserve file needed for client, if preserve this file, then directly file needed for client is provided to described client downloads; If do not preserve this file, then first this server node obtains from described index server the server node list that backup has file needed for client, the server node of normal operation in described server node list is obtained again by the zookeeper in file server system, from the server node of described normal operation, finally choose arbitrarily a server node obtain file needed for client, for client downloads.
Each described server node in above-mentioned file server system preferably includes at least one archive large files block, and each archive large files block comprises multiple fileblock small documents block; When described server node receives new file, this file is saved in described fileblock small documents block.Thus constitute the pattern of large files block management small documents block, be conducive to improving file activity.
Each described server node in above-mentioned file server system comprises a local index, and server node is retrieved local file preferably by described local index.
The frequency of each described server node in above-mentioned file server system to download file is from it added up, and according to the download policy preset, the file at least comprising the highest file of download frequency is saved to this server node local.When client needs to download this file, directly can downloading from this locality of connected server node, without the need to calling to other nodes again, effectively improve download efficiency.
Above-mentioned file backup inventory comprises the fileinfo of institute's backup file, and it is one or more that this fileinfo preferably includes in fid (index mark), size (file size), offset (side-play amount of file in archive), crc32 (checking mark), md5 (checking mark), deleteflag (delete mark).The memory location of each file can be known by the side-play amount of file in archive, this memory location can be named according to each server node, without the need to concrete IP address binding, if certain server node occurs abnormal, file server system is finished the work automatically switching to available server node.
Embodiment 2
The present invention also provides a kind of file server system, see Fig. 2, it is characterized in that, comprises at least one server node 10, index server 20, zookeeper30 and client 40,
At least one server node 10: in files passe process, receives and preserves the file that described client 40 uploads; For in file backup process, file is backed up, set up file backup inventory, and file backup inventory is uploaded to described index server 20; For in file download process, obtain file needed for client 40 from local or other server nodes 10 normally run, download for described client 40;
Index server 20: for receiving the file backup inventory that described server node 10 is uploaded, and provide server node 10 list of file needed for client 40 to the server node 10 of filing a request;
Zookeeper30: for providing the server node 10 of normal operation in file server system to the server node 10 of filing a request;
Client 40: for file server system upload file, by server node 10 connected in files passe to be uploaded to server system, and for from file server system download file.
Each described server node 10 preferably includes at least one archive large files block, and each archive large files block comprises multiple fileblock small documents block; When described server node 10 receives new file, this file is saved in described fileblock small documents block.Thus constitute the pattern of large files block management small documents block, be conducive to improving file activity.
Each described server node 10 comprises a local index, and described server node 10 is retrieved local file by described local index.
Each described server node 10 is also for adding up the frequency of download file from it, according to the download policy preset, the file at least comprising the highest file of download frequency is saved to this server node 10 local, when client needs to download this file, can directly download from this locality of connected server node 10, without the need to calling to other nodes again, effectively improve download efficiency.
Above-mentioned file backup inventory comprises the fileinfo of institute's backup file, and it is one or more that described fileinfo comprises in fid (index mark), size (file size), offset (side-play amount of file in archive), crc32 (checking mark), md5 (checking mark), deleteflag (delete mark).The memory location of each file can be known by the side-play amount of file in archive, this memory location can be named according to each server node, without the need to concrete IP address binding, if certain server node occurs abnormal, file server system is finished the work automatically switching to available server node.
Embodiment 3
One Application Example of the present invention is below provided:
File server system shown in Figure 3, customer end A connection server node file01, customer end B connection server node file02.User A has made picture file IMG001 (this picture file is not yet uploaded to file server system), and is uploaded onto the server in node file01 by this picture file IMG001.According to the file backup strategy preset, server node file01 can back up the server node of random selecting several other, and after backup, sets up one for the backup list of picture file IMG001, be saved in index server.Suppose server node file01 herein by file backup in server node file03.When user B needs download pictures file IMG001, first server node file02 inquires about self and whether preserves picture file IMG001, if do not preserve, then server node file02 to index server inquiry for the backup list of picture file IMG001, thus know in which server node and preserve picture file IMG001, be server node file01 and file03 herein.Server node file02, again by the server discovery mechanism of zookeeper, learns the state of file01 and file03, if file01 and file03 all normally runs, then random selecting one obtains picture file IMG001 for user B download to it; If file01 and file03 has one normally not run, then automatically select the normal node run to obtain picture file, ensure that user B normally can complete download.
In server node of the present invention, the preservation of file is based on archive file structure.Each server node comprises multiple archive large files block, and archive large files block is similar to compressed file.The long-pending maximal value of archive large files block can set arbitrarily, such as, can be set to 32GB, wherein mark off multiple fileblock small documents block.When server have received a new file, then be kept in a fileblock small documents block, until the file size that in an archive large files block, all fileblock small documents blocks are preserved is greater than 32GB, then server node sets up a new archive large files block, thus achieves the pattern of large files block management small documents block.
Each file is saved in fileblock small documents block and after backing up, necessary fileinfo also can be written in backup list, to inquire about more efficiently and to extract.It is one or more that fileinfo can comprise in fid (index mark), size (file size), offset (side-play amount of file in archive), crc32 (checking mark), md5 (checking mark), deleteflag (delete mark).If user deletes the file oneself uploaded, not representing this file will be deleted in server system, but add a deleteflag in server system this file.If file has been added deleteflag, then the operation such as inquiry, extraction of this file is not responded.By the memory location of each file of the side-play amount of file in archive, this memory location can be named according to each server node, without the need to concrete IP address binding, if certain server node occurs abnormal, file server system is finished the work automatically switching to available server node.
Known by above each embodiment, the beneficial effect that the application exists is:
First, in the file management method of file server system provided by the present invention and file server system, the file of client upload can backup in the multiple or whole server node in file server system, in file server system operational process, even if having one or several server node to break down cannot normally run, client also can get required file from other nodes, therefore can not affect file server system to continue externally to provide service, the normal operation of file server system can be ensured.
Second, server node in file server system of the present invention comprises at least one archive large files block, each archive large files block comprises multiple fileblock small documents block, file backup is in each fileblock small documents block, thus achieve a server node and manage multiple large files block, each large files block manages again the network structure of multiple small documents block respectively, ff transfer efficiency between server node is significantly improved, thus effectively improves the file activity of whole system.
3rd, in file server system of the present invention, the memory location of each file can be named according to each server node, without the need to concrete IP address binding, if certain server node occurs abnormal, file server system is finished the work automatically switching to available server node.
4th, in file server system of the present invention, each described server node can also be added up the frequency of download file from it, according to the download policy preset, the file at least comprising the highest file of download frequency is saved to this server node local, client is if any download demand, directly can downloading from server node this locality, without the need to transferring from other server nodes again, effectively improve download efficiency.
Those skilled in the art should understand, the embodiment of the application can be provided as method, device or computer program.Therefore, the application can adopt the form of complete hardware embodiment, completely software implementation or the embodiment in conjunction with software and hardware aspect.And the application can adopt in one or more form wherein including the upper computer program implemented of computer-usable storage medium (including but not limited to magnetic disk memory, CD-ROM, optical memory etc.) of computer usable program code.
Above-mentioned explanation illustrate and describes some preferred embodiments of the application, but as previously mentioned, be to be understood that the application is not limited to the form disclosed by this paper, should not regard the eliminating to other embodiments as, and can be used for other combinations various, amendment and environment, and can in invention contemplated scope described herein, changed by the technology of above-mentioned instruction or association area or knowledge.And the change that those skilled in the art carry out and change do not depart from the spirit and scope of the application, then all should in the protection domain of the application's claims.
Claims (10)
1. the file management method in file server system, is characterized in that, comprising:
When client is to file server system upload file, by connected server node in files passe to be uploaded to described file server system, this server node receives and preserves the file of described client upload;
According to the file backup strategy preset, the server node receiving described client upload file obtains the information of normal other server nodes run by the zookeeper in described file server system, and select at random one or morely to back up described upload file from other server nodes of described normal operation, set up file backup inventory, and this file backup list is uploaded to the index server in described file server system;
When described client is from described file server system download file, first retrieve its this locality with the server node of this client's side link and whether preserve file needed for client, if preserve this file, then directly file needed for client is provided to described client downloads; If do not preserve this file, then first this server node obtains from described index server the server node list that backup has file needed for client, the server node of normal operation in described server node list is obtained again by the zookeeper in described file server system, from the server node of described normal operation, finally choose arbitrarily a server node obtain file needed for client, for described client downloads.
2. the file management method according to claim 1 in file server system, is characterized in that, comprise further:
Each described server node in described file server system comprises at least one archive large files block, and each archive large files block comprises multiple fileblock small documents block; When described server node receives new file, this file is saved in described fileblock small documents block.
3. the file management method according to claim 1 in file server system, is characterized in that,
Each described server node in described file server system comprises a local index, and described server node is retrieved local file by described local index.
4. the file management method according to claim 1 in file server system, is characterized in that,
The frequency of each described server node in described file server system to download file is from it added up, and according to the download policy preset, the file at least comprising the highest file of download frequency is saved to this server node local.
5., according to the file management method in the arbitrary described file server system of Claims 1 to 4, it is characterized in that,
Described file backup inventory comprises: the fileinfo of institute's backup file, and described fileinfo comprises: index mark, file size, the side-play amount of file in archive, checking mark, deletion mark in one or more.
6. as Claims 1 to 5 arbitrary as described in a file server system, it is characterized in that, comprise at least one server node, index server, zookeeper and client, wherein,
At least one server node described: in files passe process, receives and preserves the file of described client upload; For in file backup process, file is backed up, set up file backup inventory, and file backup inventory is uploaded to described index server; For in file download process, obtain file needed for client, for described client downloads from local or other server nodes normally run;
Described index server: for receiving the file backup inventory that described server node is uploaded, and provide the server node list of file needed for client to the described server node of filing a request;
Described zookeeper: for providing the server node of normal operation in described file server system to the described server node of filing a request;
Described client: for described file server system upload file, by server node connected in files passe to be uploaded to server system, and for from file server system download file.
7. file server system according to claim 6, is characterized in that,
Each described server node comprises at least one archive large files block, and each archive large files block comprises multiple fileblock small documents block; When described server node receives new file, this file is saved in described fileblock small documents block.
8. file server system according to claim 6, is characterized in that,
Each described server node comprises a local index, and described server node is retrieved local file by described local index.
9. file server system according to claim 6, is characterized in that,
The file at least comprising the highest file of download frequency, also for adding up the frequency of download file from it, according to the download policy preset, is saved to this server node local by each described server node.
10., according to the arbitrary described file server system of claim 6 ~ 9, it is characterized in that,
Described file backup inventory comprises the fileinfo of institute's backup file, described fileinfo comprise index mark, file size, the side-play amount of file in archive, checking mark, deletion mark in one or more.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510707012.2A CN105404645A (en) | 2015-10-27 | 2015-10-27 | File management method in file server system and file server system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510707012.2A CN105404645A (en) | 2015-10-27 | 2015-10-27 | File management method in file server system and file server system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105404645A true CN105404645A (en) | 2016-03-16 |
Family
ID=55470135
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510707012.2A Pending CN105404645A (en) | 2015-10-27 | 2015-10-27 | File management method in file server system and file server system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105404645A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108986556A (en) * | 2018-08-22 | 2018-12-11 | 高海龙 | A kind of aircraft remote technology clearance method, apparatus and smart machine |
| CN109561120A (en) * | 2017-09-26 | 2019-04-02 | 杭州海康威视系统技术有限公司 | Small documents backup method, systems and management server |
| CN110661829A (en) * | 2018-06-28 | 2020-01-07 | 杭州海康威视系统技术有限公司 | File downloading method and device, client and computer readable storage medium |
| CN111027578A (en) * | 2018-10-09 | 2020-04-17 | 厦门雅迅网络股份有限公司 | Method and device for preventing loss and replacement of photos |
| CN113010474A (en) * | 2021-03-16 | 2021-06-22 | 中国联合网络通信集团有限公司 | File management method, instant messaging method and storage server |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102710554A (en) * | 2012-06-25 | 2012-10-03 | 深圳中兴网信科技有限公司 | Distributed message system and service status detection method thereof |
| CN103530387A (en) * | 2013-10-22 | 2014-01-22 | 浪潮电子信息产业股份有限公司 | Improved method aimed at small files of HDFS |
| US20140196115A1 (en) * | 2013-01-07 | 2014-07-10 | Zettaset, Inc. | Monitoring of Authorization-Exceeding Activity in Distributed Networks |
| CN104065741A (en) * | 2014-07-04 | 2014-09-24 | 用友软件股份有限公司 | Data collection system and method |
| CN104331428A (en) * | 2014-10-20 | 2015-02-04 | 暨南大学 | Storage and access method of small files and large files |
-
2015
- 2015-10-27 CN CN201510707012.2A patent/CN105404645A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102710554A (en) * | 2012-06-25 | 2012-10-03 | 深圳中兴网信科技有限公司 | Distributed message system and service status detection method thereof |
| US20140196115A1 (en) * | 2013-01-07 | 2014-07-10 | Zettaset, Inc. | Monitoring of Authorization-Exceeding Activity in Distributed Networks |
| CN103530387A (en) * | 2013-10-22 | 2014-01-22 | 浪潮电子信息产业股份有限公司 | Improved method aimed at small files of HDFS |
| CN104065741A (en) * | 2014-07-04 | 2014-09-24 | 用友软件股份有限公司 | Data collection system and method |
| CN104331428A (en) * | 2014-10-20 | 2015-02-04 | 暨南大学 | Storage and access method of small files and large files |
Non-Patent Citations (2)
| Title |
|---|
| 杜勇: "基于HDFS的云数据备份系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
| 胡军杰: "云平台下分布式文件系统评测技术研究", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109561120A (en) * | 2017-09-26 | 2019-04-02 | 杭州海康威视系统技术有限公司 | Small documents backup method, systems and management server |
| CN109561120B (en) * | 2017-09-26 | 2022-03-01 | 杭州海康威视系统技术有限公司 | Small file backup method, system and management server |
| CN110661829A (en) * | 2018-06-28 | 2020-01-07 | 杭州海康威视系统技术有限公司 | File downloading method and device, client and computer readable storage medium |
| CN108986556A (en) * | 2018-08-22 | 2018-12-11 | 高海龙 | A kind of aircraft remote technology clearance method, apparatus and smart machine |
| CN111027578A (en) * | 2018-10-09 | 2020-04-17 | 厦门雅迅网络股份有限公司 | Method and device for preventing loss and replacement of photos |
| CN111027578B (en) * | 2018-10-09 | 2024-01-12 | 厦门雅迅网络股份有限公司 | Method and device for preventing photo from being lost and replaced |
| CN113010474A (en) * | 2021-03-16 | 2021-06-22 | 中国联合网络通信集团有限公司 | File management method, instant messaging method and storage server |
| CN113010474B (en) * | 2021-03-16 | 2023-10-24 | 中国联合网络通信集团有限公司 | File management method, instant messaging method and storage server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106294585B (en) | A kind of storage method under cloud computing platform | |
| US6922761B2 (en) | Method and system for migrating data | |
| CN106250270B (en) | A kind of data back up method under cloud computing platform | |
| JP5260536B2 (en) | Primary cluster fast recovery | |
| CN106156359B (en) | A kind of data synchronization updating method under cloud computing platform | |
| JP5210176B2 (en) | Protection management method for storage system having a plurality of nodes | |
| CN105404645A (en) | File management method in file server system and file server system | |
| US10289859B2 (en) | System and method for secure multi-tenancy in datadomain operating system (DDOS), a purpose built backup appliance (PBBA) operating system | |
| US10187256B2 (en) | Configuration replication across distributed storage systems | |
| JP5868986B2 (en) | Recovery by item | |
| US20130325932A1 (en) | Electronic device and method for storing distributed documents | |
| US7080102B2 (en) | Method and system for migrating data while maintaining hard links | |
| CN102495772A (en) | Characteristic-based terminal program cloud backup and recovery methods | |
| CN104641369A (en) | File server, information system, and control method thereof | |
| US20160139996A1 (en) | Methods for providing unified storage for backup and disaster recovery and devices thereof | |
| US8145864B1 (en) | Discovering data storage for backup | |
| CN105468643A (en) | Distributed file system access method and system | |
| US6952699B2 (en) | Method and system for migrating data while maintaining access to data with use of the same pathname | |
| CN106294842A (en) | A kind of data interactive method, platform and distributed file system | |
| WO2009031158A2 (en) | Method and apparatus for network based data recovery | |
| CN116560904A (en) | NAS data backup disaster recovery method, system, terminal and storage medium | |
| US10620883B1 (en) | Multi-format migration for network attached storage devices and virtual machines | |
| CN103714089A (en) | Method and system of rolling back cloud database | |
| CN111176904A (en) | Method, system, equipment and medium for data backup under private cloud architecture | |
| US10713121B1 (en) | Dynamic migration of a cloud based distributed file system metadata server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160316 |