Managed Directories for Virtual Machines
US-2024385997-A1 · Nov 21, 2024 · US
US10891194B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10891194-B2 |
| Application number | US-201715665930-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 1, 2017 |
| Priority date | Jan 23, 2009 |
| Publication date | Jan 12, 2021 |
| Grant date | Jan 12, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A versioned file system comprises a set of structured data representations. At a first time, an interface creates and exports to a cloud data store a first structured data representation corresponding to a first version of the local file system. The first structured data representation is an XML tree having a root element, one or more directory elements associated with the root element, and one or more file elements associated with a given directory element. Upon a change within the file system, the interface creates and exports a second structured data representation corresponding to a second version of the file system. The second structured data representation differs from the first structured data representation up to and including the root element of the second structured data representation. The interface continues to generate and export the structured data representations to the data store.
Opening claim text (preview).
The invention claimed is: 1. A storage-as-a-service system to provide storage for an enterprise, comprising: a management console to provision and manage a scalable file system across one or more cloud-based storage service providers; one or more file system interfaces associated with the enterprise, wherein at least one file system interface executes either as a virtual machine or on physical hardware and is configured to represent, to the enterprise, a local file system whose data is stored in one or more cloud-based storage service providers; wherein the one or more file system interfaces export their local file system data as a structured data representation, wherein the structured data representation associated with the at least one file system interface comprises a Uniform Resource Identifier (URI)-addressable cloud node that contains information passed by that file system interface about its associated local file system, together with an access control; wherein the structured data representation associated with the at least one file system interface is self-contained in that it includes or points to all data structures and data needed to reconstruct the associated local file system at a point-in-time. 2. The storage-as-a-service system as described in claim 1 , wherein the structured data representation associated with the at least one file system interface comprises one or more tree-based data structures, wherein at least one tree-based data structure starts with a root that represents a current version of the local file system, and that further includes one or more change events that have been generated as a result of modification to the local file system. 3. The storage-as-a-service system as described in claim 1 , wherein, from a tree-walk perspective, a tree-based data structure is a complete version of the local file system at a given point-in-time. 4. The storage-as-a-service system as described in claim 1 , wherein the local file system, a directory and its contents, a given file, or a piece of a file, are restorable from the scalable file system with respect to a given time period. 5. The storage-as-a-service system as described in claim 1 wherein at least one file system interface is located on the physical hardware on-premises in the enterprise. 6. The storage-as-a-service system as described in claim 1 , wherein the structured data representation associated with the at least one file system interface is a logical representation of a combination of a current version of the local file system and one or more prior versions of the local file system. 7. The storage-as-a-service system as described in claim 1 wherein the file system interface is a generic virtual file system interface that supports a set of access protocols. 8. The storage-as-a-service system as described in claim 7 wherein the set of access protocols are one of: NFS and CIFS. 9. The storage-as-a-service system as described in claim 1 wherein local file system data is encrypted prior to being exported and stored in the one or more cloud-based storage service providers. 10. The storage-as-a-service system as described in claim 1 wherein one or more of the file system interfaces are implemented as instances within a cloud computing layer. 11. The storage-as-a-service system as described in claim 1 wherein the scalable file system is a write-once object-based data store.
Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16) · CPC title
Provision of network file services by network file servers, e.g. by using NFS, CIFS (network file access protocols H04L67/1097) · CPC title
Trees · CPC title
Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files · CPC title
Real-time · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.