WO2014015782A1 - 分布式文件***、文件访问方法以及客户端 - Google Patents
分布式文件***、文件访问方法以及客户端 Download PDFInfo
- Publication number
- WO2014015782A1 WO2014015782A1 PCT/CN2013/079855 CN2013079855W WO2014015782A1 WO 2014015782 A1 WO2014015782 A1 WO 2014015782A1 CN 2013079855 W CN2013079855 W CN 2013079855W WO 2014015782 A1 WO2014015782 A1 WO 2014015782A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- file
- server
- meta
- access
- information
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 18
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
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/182—Distributed file systems
- G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
- G06F16/183—Provision of network file services by network file servers, e.g. by using NFS, CIFS
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2094—Redundant storage or storage space
-
- 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/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- 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/13—File access structures, e.g. distributed indices
- G06F16/134—Distributed indices
-
- 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/182—Distributed file systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Definitions
- This application relates to data storage technologies, and more particularly to distributed file systems, file access methods, and clients. Background of the invention
- the representative distributed file system in the industry is Google's distributed file system, called GFS (Global File System).
- GFS Global File System
- the GFS consists mainly of a Master Server and a number of Chunk Servers.
- the Master Server is mainly responsible for storing the file directory and the meta information of each file in the file directory.
- the meta information mainly includes: the size of the file, the number of data blocks into which the file is divided, the Chunk Server in which the data block into which the file is divided, and the like.
- Chunk Server is mainly responsible for storing the data blocks into which the files are divided.
- a file is divided into multiple data blocks according to a certain size. Each data block is called a Chunk, and these data blocks are distributed and stored in different Chunk Servers.
- the embodiment of the present application provides a distributed file system, a file access method, and a client, so as to increase the number of files in a single cluster and the concurrent access amount of files.
- a distributed file system including:
- the master server is used to store the file directory and the routing information of the Meta Server associated with each file in the file directory.
- the stored routing information is found in the stored routing information.
- the routing information of the Meta Server associated with the file is provided to the client, so that the client accesses the Meta Server by using the routing information provided by the Master Server;
- Meta Server which is used to store the meta information of the associated file, the number of Meta Servers is greater than or equal to 1; when receiving the access of the client, providing the meta information of the file that the client needs to access to the client, so that the client can utilize
- the meta information provided by the Meta Server accesses the files that need to be accessed from the Node Server.
- the node server is used to store backups of data blocks and/or data blocks into which files are divided.
- the number of Node Servers is greater than or equal to 1.
- a file access method including:
- a client applied to file access including:
- a first access unit configured to access a file directory stored by the master server, and obtain, from the master server, routing information of the meta information server Meta Server associated with the file that the client needs to access;
- a second access unit configured to access the Meta Server by using the routing information obtained by the first access unit, and obtain meta information of the file that the client needs to access from the Meta Server;
- the third access unit is configured to use the acquired meta information to access the file that needs to be accessed from the multiple node server Node Server.
- the file directory and the file meta information are separately stored, that is, the client only accesses the file directory of the Master Server and the routing information of the Meta Server associated with each file in the file directory. And go to the Meta Server to access the meta-information of the specific file, which provides a higher number of visits per second (QPS) than a single Master Server that provides both file directory access and file meta-information access. It is possible to provide a higher number of concurrent accesses.
- the master server only stores file directories, which ensures that the distributed file system in the embodiment of the present invention stores more files.
- FIG. 1 is a schematic structural diagram of a distributed file system according to an embodiment of the present invention.
- FIG. 2 is a schematic flowchart of a file access method according to an embodiment of the present invention.
- FIG. 3 is a schematic structural diagram of a client according to an embodiment of the present disclosure.
- FIG. 4 is a schematic structural diagram of a client according to another embodiment of the present invention. Mode for carrying out the invention
- the distributed file system provided by the embodiment of the present invention has the structure shown in FIG. 1, and includes: a master server, at least one meta information server ( Meta Server), and at least one node server (Node Server).
- Meta Server meta information server
- Node Server node server
- the number of the Meta Server and the Node Server may be set according to the cluster size, which is not specifically limited in the embodiment of the present invention.
- the distributed system provided by the embodiment of the present invention The three-layer architecture is adopted, wherein the upper layer is the master server, the middle layer is at least one meta server, and the lower layer is at least one Node server. Based on this, the distributed system provided by the embodiment of the present invention may be referred to as a three-layer architecture. Distributed file system.
- the number of Meta Servers and Node Servers may be set according to the cluster size.
- the distributed system provided by the embodiment of the present invention may also be referred to as an extended distributed file system, which is called XFS (extensible file system).
- the storage of the file meta-information is much larger than the storage of the file directory.
- the file directory and the file meta-information are separately stored in the embodiment of the present invention.
- Server stores, and the file meta information is stored in Meta Server.
- the storage in the Master Server is also associated with each file in the file directory. Meta Server routing information.
- Master Server used to store the file directory, and the routing information of the Meta Server associated with each file in the file directory;
- each Meta Server is configured to store meta information of a file associated with the file, where the meta information of the file includes at least: a length of the file, a number of data blocks into which the file is divided, and each data block into which the file is divided, and
- the meta information of the file may further include: a file creation time, a file creator, and summary information of each data block into which the file is divided.
- the embodiment of the present invention is not specifically limited.
- Each Node Server is used to store backups of data blocks and/or other data blocks. Wherein, each Node Server can store only one or more of the same file divided into A data block, but it is forbidden to simultaneously store a certain data block into which the same file is divided and a backup of the data block. That is, a block of data cannot be stored on the same Node Server as its backup.
- the file 1 for the file in the file directory stored by the Master Server (referred to as file 1), if the file 1 is divided into 5 data blocks, in order to improve the fault tolerance of the system.
- the five data blocks and their backups may be dispersed in different manners according to the characteristics of the backup of the Node Server storage data block and the data block described above.
- how the file 1 is divided into data blocks can be based on the existing division manner, and the present invention will not repeat them.
- multiple backups of one data block may exist.
- the embodiment of the present invention does not store the multiple backups in the same
- the Node Server is distributed on different Node Servers, that is, all backups of the same data block are not stored in the same Node Server.
- backups of different data blocks into which the same file is divided are not stored in the same Node Server based on fault tolerance considerations.
- the Master Server finds the file that the client needs to access in the stored file directory, and finds the stored routing information.
- the routing information of the Meta Server associated with the file is provided to the client, so that the client accesses the Meta Server by using the routing information provided by the Master Server; and when the Meta Server receives the access of the client, providing the client needs
- the meta information of the accessed file is sent to the client, so that the client accesses the file that needs to be accessed by using the meta information provided by the Meta Server.
- the client's file access can be completed. It can be seen that the client only accesses the file directory of the Master Server and the route of the Meta Server associated with each file in the file directory. Information, and go to Meta Server to access the meta-information of specific files, which provides a higher number of visits per second (QPS) than a single Master Server that provides both file directory access and file meta-information access. It is also possible to provide a higher number of concurrent accesses.
- the master server only stores the file directory, which can expand the file directory stored by the master server, and ensure that the distributed file system provided by the embodiment of the present invention stores more files.
- the Master Server since the Master Server only stores the file directory and the routing information of the Meta Server associated with each file in the file directory, the meta information of the file is not stored, which is compared to a single Master Server.
- the number of files in the cluster is no longer limited due to the limited memory of a single Master Server. Instead, the number of files can be flexibly expanded, and the number of Meta Servers and Node Servers can be flexibly expanded accordingly. .
- each Meta Server of the extension is similar to the original Meta Server function of the distributed file system. For example, if the currently extended Meta Server is recorded as Server 1 and Server 2, Server1 is For example, the principle of Server2 is similar, Bay' J,
- the Server1 can store the meta information of the file associated with it, wherein the file associated with Server1 can be a file existing in the file directory of the Master Server, and the file associated with Server1 exists in the file directory of the Master Server.
- the server 1 stores the meta information of the file 1, wherein the server 1 stores the meta information of the file 1, and can provide a backup for the Meta Server that has stored the meta information of the file 1 to improve the system. Fault tolerance.
- the file associated with the Server1 may also be a file that does not exist in the file directory of the Master Server, but a file that needs to be expanded according to requirements.
- Serverl stores the meta information of the file that needs to be expanded.
- the Master Server is also used to add a force to the file directory and the extended Meta Server.
- the Node Server which is extended according to requirements in the embodiment of the present invention, it is similar to the existing Node Server function of the distributed file system, and is used for storing backups of data blocks and/or data blocks into which files are divided.
- the extended data block of each Node Server may be a data block or a data block that is divided into a file that exists in the file directory of the Master Server, or may be a data block or data that is divided into a newly extended file.
- Block backup how to store data blocks in detail, can be set according to the current actual situation, and will not be described here.
- the Master Server only stores the file directory and the routing information of the Meta Server associated with each file in the file directory, and the file directory and the Meta Server associated with each file in the file directory.
- the storage space occupied by the routing information is not large, especially when the name of the file in the file directory is short, such as a short number or character encoding, which ensures that the Master Server stores more file directories and files associated with the files in the file directory.
- the routing information of the linked Meta Server expands the cluster size.
- the file directory on the Master Server and the routing information of the Meta Server associated with each file in the file directory may be stored to other quick accesses.
- the storage space of the distributed system is much larger than that of the Master Server. This ensures that more file directories are stored, and more Meta Server routing information associated with each file in the file directory. The concurrent access capability of the entire cluster will be Further improvement.
- Meta Servers since the number of Meta Servers is not unique, if one or more Meta Servers fail, and other normal Meta Servers are not affected, some files can still be read and written, and the fault tolerance is stronger. .
- FIG. 2 is a flowchart of a file access method according to an embodiment of the present invention.
- the process shown in Figure 2 can be performed by the client.
- the method includes the following steps: Step 201: Access a file directory stored by the Master Server, and obtain a Meta Server associated with the file to be accessed from the Master Server. Routing information;
- Step 202 Access the Meta Server by using the obtained routing information, and obtain meta information of the file to be accessed from the Meta Server.
- the meta information of the file includes at least: a length of the file, a number of data blocks into which the file is divided, each data block into which the file is divided, and a Node where the backup of each data block is located. Server.
- Step 203 Access the file to be accessed from the plurality of Node Servers by using the obtained meta information.
- the client only accesses the file directory and the Meta Server routing information associated with each file in the file directory, and goes to Meta Server to access the meta information of the specific file, which is compared to a single
- the Master Server provides both higher file access times (QPS) and higher concurrent access in terms of file directory access and access to file meta information.
- FIG. 3 is a structural diagram of a client according to an embodiment of the present invention.
- the client includes:
- a first access unit configured to access a file directory stored by the Master Server, and obtain, from the Master Server, routing information of a Meta Server associated with a file that the client needs to access;
- a second access unit configured to access by using routing information acquired by the first access unit Meta Server, and obtain meta information of the files that the client needs to access from the Meta Server.
- the meta information of the file includes at least: a length of the file, a number of data blocks into which the file is divided, each data block into which the file is divided, and a Node Server where the backup of each data block is located;
- the third access unit is configured to access the file that needs to be accessed from the plurality of Node Servers by using the meta information obtained by the second access unit.
- FIG. 4 is a schematic structural diagram of a client according to another embodiment of the present invention.
- the client includes at least: a memory and a processor in communication with the memory, wherein the memory includes first access instructions, second access instructions, and third access instructions executable by the processor.
- the first access instruction is used to access a file directory stored by the master server, and obtain, from the master server, routing information of the meta information server Meta Server associated with the file that the client needs to access;
- a second access instruction configured to access the Meta Server by using the routing information obtained by the first access instruction, and obtain, from the Meta Server, meta information of a file that the client needs to access;
- a third access instruction configured to access the file to be accessed from the plurality of node servers Node Server by using the meta information obtained by the second access instruction.
- the meta information of the file includes at least: a length of the file, a number of data blocks into which the file is divided, each data block into which the file is divided, and a Node Server where the backup of each data block is located.
- the file directory and the file meta information are separately stored, that is, the client only accesses the file directory of the Master Server and the routing information of the Meta Server associated with each file in the file directory. , and go to the Meta Server access
- the meta-information of the file which provides a higher QPS and provides a higher amount of concurrent access than a single Master Server that provides both file directory access and file meta-information access.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2015523398A JP2015528957A (ja) | 2012-07-26 | 2013-07-23 | 分散ファイルシステム、ファイルアクセス方法及びクライアントデバイス |
US14/414,501 US20150169623A1 (en) | 2012-07-26 | 2013-07-23 | Distributed File System, File Access Method and Client Device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210261331.1A CN103581229B (zh) | 2012-07-26 | 2012-07-26 | 分布式文件***、文件访问方法以及客户端 |
CN201210261331.1 | 2012-07-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014015782A1 true WO2014015782A1 (zh) | 2014-01-30 |
Family
ID=49996586
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/079855 WO2014015782A1 (zh) | 2012-07-26 | 2013-07-23 | 分布式文件***、文件访问方法以及客户端 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20150169623A1 (zh) |
JP (1) | JP2015528957A (zh) |
CN (1) | CN103581229B (zh) |
WO (1) | WO2014015782A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10691478B2 (en) | 2016-08-15 | 2020-06-23 | Fujitsu Limited | Migrating virtual machine across datacenters by transferring data chunks and metadata |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105635196B (zh) * | 2014-10-27 | 2019-08-09 | 中国电信股份有限公司 | 一种获取文件数据的方法、***和应用服务器 |
CN104462335B (zh) * | 2014-12-03 | 2017-12-29 | 北京和利时***工程有限公司 | 一种访问数据的方法和服务器代理 |
CN106470163B (zh) * | 2015-08-17 | 2020-07-07 | 腾讯科技(北京)有限公司 | 一种信息处理方法、装置和*** |
CN108804711B (zh) * | 2018-06-27 | 2022-12-06 | 郑州云海信息技术有限公司 | 一种数据处理的方法、装置和计算机可读存储介质 |
CN109756573B (zh) * | 2019-01-15 | 2022-02-08 | 苏州链读文化传媒有限公司 | 一种基于区块链的文件*** |
US11768954B2 (en) | 2020-06-16 | 2023-09-26 | Capital One Services, Llc | System, method and computer-accessible medium for capturing data changes |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7487228B1 (en) * | 2003-01-30 | 2009-02-03 | Red Hat, Inc. | Metadata structures and related locking techniques to improve performance and scalability in a cluster file system |
WO2010005460A1 (en) * | 2008-07-11 | 2010-01-14 | Avere Systems, Inc. | Media aware distributed data layout |
CN101997823A (zh) * | 2009-08-17 | 2011-03-30 | 联想(北京)有限公司 | 一种分布式文件***及其数据访问方法 |
CN101576915B (zh) * | 2009-06-18 | 2011-06-08 | 北京大学 | 一种分布式b+树索引***及构建方法 |
CN102420854A (zh) * | 2011-11-14 | 2012-04-18 | 西安电子科技大学 | 面向云存储的分布式文件*** |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9413825B2 (en) * | 2007-10-31 | 2016-08-09 | Emc Corporation | Managing file objects in a data storage system |
US8346824B1 (en) * | 2008-05-21 | 2013-01-01 | Translattice, Inc. | Data distribution system |
WO2010036889A1 (en) * | 2008-09-25 | 2010-04-01 | Bakbone Software, Inc. | Remote backup and restore |
US9239843B2 (en) * | 2009-12-15 | 2016-01-19 | Symantec Corporation | Scalable de-duplication for storage systems |
US8468135B2 (en) * | 2010-04-14 | 2013-06-18 | International Business Machines Corporation | Optimizing data transmission bandwidth consumption over a wide area network |
US9128626B2 (en) * | 2010-10-01 | 2015-09-08 | Peter Chacko | Distributed virtual storage cloud architecture and a method thereof |
CN102158546B (zh) * | 2011-02-28 | 2013-05-08 | 中国科学院计算技术研究所 | 一种集群文件***及其文件服务方法 |
CN102307221A (zh) * | 2011-03-25 | 2012-01-04 | 国云科技股份有限公司 | 一种云存储***及其实现方法 |
US8533231B2 (en) * | 2011-08-12 | 2013-09-10 | Nexenta Systems, Inc. | Cloud storage system with distributed metadata |
JP5174255B2 (ja) * | 2012-02-28 | 2013-04-03 | 株式会社インテック | ストレージサービス提供装置、システム、サービス提供方法、及びサービス提供プログラム |
-
2012
- 2012-07-26 CN CN201210261331.1A patent/CN103581229B/zh active Active
-
2013
- 2013-07-23 JP JP2015523398A patent/JP2015528957A/ja active Pending
- 2013-07-23 US US14/414,501 patent/US20150169623A1/en not_active Abandoned
- 2013-07-23 WO PCT/CN2013/079855 patent/WO2014015782A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7487228B1 (en) * | 2003-01-30 | 2009-02-03 | Red Hat, Inc. | Metadata structures and related locking techniques to improve performance and scalability in a cluster file system |
WO2010005460A1 (en) * | 2008-07-11 | 2010-01-14 | Avere Systems, Inc. | Media aware distributed data layout |
CN101576915B (zh) * | 2009-06-18 | 2011-06-08 | 北京大学 | 一种分布式b+树索引***及构建方法 |
CN101997823A (zh) * | 2009-08-17 | 2011-03-30 | 联想(北京)有限公司 | 一种分布式文件***及其数据访问方法 |
CN102420854A (zh) * | 2011-11-14 | 2012-04-18 | 西安电子科技大学 | 面向云存储的分布式文件*** |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10691478B2 (en) | 2016-08-15 | 2020-06-23 | Fujitsu Limited | Migrating virtual machine across datacenters by transferring data chunks and metadata |
Also Published As
Publication number | Publication date |
---|---|
JP2015528957A (ja) | 2015-10-01 |
US20150169623A1 (en) | 2015-06-18 |
CN103581229B (zh) | 2018-06-15 |
CN103581229A (zh) | 2014-02-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11809726B2 (en) | Distributed storage method and device | |
CN107547653B (zh) | 一种分布式文件存储*** | |
JP6538780B2 (ja) | 分散型データベースシステムのシステム全体のチェックポイント回避 | |
WO2014015782A1 (zh) | 分布式文件***、文件访问方法以及客户端 | |
US20220284046A1 (en) | Application Programming Interface-based Writing of Data to a Directory of a File Structure Layer of a Data Storage System | |
US8694564B2 (en) | Method and system for providing on-demand services through a virtual file system at a computing device | |
US8301654B2 (en) | Geographical distributed storage system based on hierarchical peer to peer architecture | |
US10031933B2 (en) | Peer to peer ownership negotiation | |
US10210167B1 (en) | Multi-level page caching for distributed object store | |
US9031906B2 (en) | Method of managing data in asymmetric cluster file system | |
US20130218934A1 (en) | Method for directory entries split and merge in distributed file system | |
US11080253B1 (en) | Dynamic splitting of contentious index data pages | |
JP2009533759A (ja) | 分散データを再構築するためのシステム | |
CN109302448B (zh) | 一种数据处理方法及装置 | |
US7533133B1 (en) | Externally managed file versions | |
WO2014107901A1 (zh) | 数据存储方法、数据库存储节点故障处理方法及装置 | |
US11334456B1 (en) | Space efficient data protection | |
WO2018000618A1 (zh) | 对象文件的追加、截断方法及服务器 | |
US10684786B2 (en) | Methods for performing global deduplication on data blocks and devices thereof | |
JP5890452B2 (ja) | クラスタシステムのサーバ装置およびそのプログラム | |
JP2012508411A (ja) | デジタルデータ集合の仮想ストレージ方法および仮想ストレージシステム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13823833 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14414501 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2015523398 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 24/06/2015) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13823833 Country of ref document: EP Kind code of ref document: A1 |