Data revision control in large-scale data analytic systems
US-2024104067-A1 · Mar 28, 2024 · US
US11726967B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11726967-B2 |
| Application number | US-202117146020-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 11, 2021 |
| Priority date | Jul 7, 2015 |
| Publication date | Aug 15, 2023 |
| Grant date | Aug 15, 2023 |
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 storage system (VFS) and method for operating and using the same is disclosed. In an aspect, a mechanism is provided wherein a first VFS interface unit coupling the VFS to a local data storage system is replaced with a second VFS interface unit in a coordinated procedure for taking the first unit offline, making a reliable snapshot of its data and cache structure in the VFS, and loading the same data and cache structure into the second VFS interface brought online. The first and second VFS interfaces transfer the necessary data to achieve the switch through respective side-loading daemons running in each interface. Clients in the local data storage system experience minimal interruption of services in the VFS.
Opening claim text (preview).
What is claimed is: 1. A method operative in a cloud storage-based versioned file system (VFS), comprising: taking a first VFS interface offline so that it no longer accepts new data or requests for data from a local data storage system while maintaining the first VFS interface powered and running a first daemon; while the first VFS interface is offline but powered and running the first daemon, bringing a second VFS interface online so that it is powered and running a second daemon; with the first VFS interface still offline, placing the first and second daemons in data communication with one another; with the first VFS interface still offline and the second VFS interface online, receiving at the second VFS interface, through the second daemon, a copy of data from the first VFS interface, the copy of data being provided through the first daemon as in a data transfer process, whereby the first VFS interface is upgraded to the second VFS interface without performance degradation; and while the data transfer process between the first and second daemons is on-going, and responsive to receipt of a request for information at the second VFS interface, retrieving the information from the second VFS interface, and returning the information in response to the request, thereby avoiding retrieval of the information from the cloud storage-based VFS. 2. The method of claim 1 , wherein receiving said copy of the data comprises secure transmission of said data from the first daemon to the second daemon. 3. The method of claim 1 , further comprising taking a third VFS interface online, and using a third VFS interface, coupling said third VFS interface to the first VFS interface so that both the second and third VFS interfaces replace said first VFS interface in servicing the local data storage system. 4. The method of claim 1 , further comprising receiving at the second VFS interface, from the first VFS interface, a copy of a cached data. 5. The method of claim 1 , further comprising receiving at the second VFS interface, from the first VFS interface, a copy of a directory structure. 6. The method of claim 1 , further comprising taking the second VFS interface online by providing the second VFS interface with a reachable network address. 7. The method of claim 6 , further comprising providing the second VFS interface with a reachable network address by assigning to the second VFS interface a same network address as was previously used by the first VFS interface. 8. The method of claim 6 , further comprising providing the second VFS interface with a reachable network address by assigning to the second VFS interface a different network address than was previously used by the first VFS interface. 9. The method of claim 1 , said steps representing a process for decommissioning at least one VFS interface, including the first VFS interface, and commissioning at least one VFS interface, including the second VFS interface. 10. A network accessible data storage architecture, comprising: a network-connected versioned file system (VFS); a first VFS interface, coupled to the VFS, servicing one or more requests from a local data storage system when the first VFS interface is online and addressable by the local data storage system, the first VFS interface including a first daemon, and a data set stored in the first VFS interface; and a second VFS interface, coupled to the VFS, servicing one or more requests from the local data storage system when the second VFS interface is online and addressable by the local data storage system, the second VFS interface including a second daemon receiving from the first daemon a copy of the data set in a data transfer process, whereby the first VFS interface is upgraded to the second VFS interface without performance degradation; wherein the network accessible data storage architecture is services the one or more requests from the local data storage system, initially from said first VFS interface while the first VFS interface is online and addressable by the local data storage system, then from the second VFS interface after the second VFS interface is populated by the data set through the respective second and first daemons of the second and first VFS interfaces; wherein as the data transfer process is on-going, at least one request is serviced from the local data storage system through the second VFS interface obtaining information from the first VFS interface, thereby avoiding retrieval of the information from the VFS. 11. The architecture of claim 10 , further comprising a cloud interface between said VFS and each of the first and second VFS interfaces. 12. The architecture of claim 10 wherein the information is obtained from the first VFS interface upon a cache miss at the second VFS interface. 13. The architecture of claim 10 further including decommissioning the first VFS interface following completion of the data transfer process.
Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files · CPC title
implemented as replicated file system · CPC title
Management specifically adapted to replicated file systems · CPC title
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] · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.