Method for a cloud-based meta-file system to virtually unify remote and local files across a range of devices' local file systems
A system and process that establish a singular shared file system among devices in order to create a virtual representation of data on all of the devices via metadata indexing. This virtual representation of data means that the files are not actually stored on all devices and thus, with the exception of a single physical location, they do not need to take up any space (i.e. storage) on any additional device's hard drive. This allows for significant amounts of data to be virtually stored on each device, even if there is no physical storage room available for the data on each device. The system and process do not require data to be stored on a provider server, but instead stores only lightweight metadata, i.e., a small fraction of information about the files, online.
1. A process for operating on files located on multiple devices using a singular file system comprising:
accepting a request to operate on a file at a first device, wherein the file is selected from the singular file system on the first device;
modifying the singular file system on the first device to make local files and virtual files appear indistinguishable to the singular file system, the local files and virtual files sharing a same location on the first device;
intercepting the request by a software client on the first device;
determining by the software client if the file is physically located on the first device or if the file is a virtual file of a corresponding file physically stored on a second device by reviewing file metadata, wherein a visual representation of the singular file system on the first device is identical to a visual representation of the singular file system on the second device; and
if the file is the virtual file of the corresponding file physically located on the second device, requesting by the software client on the first device that a peer-to-peer connection be brokered by a server-based web service between the first device and the second device;
if the peer-to-peer connection is brokered, transferring the corresponding physical file from the second device to the first device; and
performing the operation on the transferred corresponding physical file at the first device.
2. The process according to claim 1 , wherein if the peer-to-peer connection cannot be brokered between the first device and the second device, an alternative connection is established by the server-based web service.
3. The process according to claim 2 , wherein the alternative connection is an HTTP relay.
4. The process according to claim 1 , further comprising updating metadata of the singular file system on the first device and the second device to reflect a change in physical location of the file from the second device to the first device.
5. The process according to claim 1 , wherein an operating system of the first device is unaware of files being virtual or physical and believes that all files are physically stored on the first device within the singular file system.
6. The process according to claim 1 , further comprising:
upon completing the operation, pushing the physical file back to the second device; and
retaining the virtual file at the first device.
7. A non-transitory computer-readable storage medium storing a set of instructions that, when executed by a processor, cause the processor to perform operations, comprising:
accepting a request to operate on a file at a first device, wherein the file is selected from the singular file system on the first device;
modifying the singular file system on the first device to make local files and virtual files appear indistinguishable to the singular file system, the local files and virtual files sharing a same location on the first device;
intercepting the request by a software client on the first device;
determining by the software client if the file is physically located on the first device or if the file is a virtual file of a corresponding file physically stored on a second device by reviewing file metadata, wherein a visual representation of the singular file system on the first device is identical to a visual representation of the singular file system on the second device; and
if the file is the virtual file of the corresponding file physically located on the second device, requesting by the software client on the first device that a peer-to-peer connection be brokered by a server-based web service between the first device and the second device;
if the peer-to-peer connection is brokered, transferring the corresponding physical file from the second device to the first device; and
performing the operation on the transferred corresponding physical file at the first device.
8. A client comprising:
a memory;
at least one processor configured to:
accept a request to operate on a file at a first device, wherein the file is selected from the singular file system on the first device;
modify the singular file system on the first device to make local files and virtual files appear indistinguishable to the singular file system, the local files and virtual files sharing a same location on the first device;
intercept the request by a software client on the first device;
determine by the software client if the file is physically located on the first device or if the file is a virtual file of a corresponding file physically stored on a second device by reviewing file metadata, wherein a visual representation of the singular file system on the first device is identical to a visual representation of the singular file system on the second device; and
if the file is the virtual file of the corresponding file physically located on the second device, request by the software client on the first device that a peer-to-peer connection be brokered by a server-based web service between the first device and the second device;
if the peer-to-peer connection is brokered, transfer the corresponding physical file from the second device to the first device; and
perform the operation on the transferred corresponding physical file at the first device.