Abstract: Transportable storage devices are communicatively coupled behind one or more dedicated “edge” data servers to take advantage of the benefits of the data servers and transportable storage devices while limiting their disadvantages. Each edge data server ingests data from one or more client devices and copies the data to one or more of the transportable storage devices for eventual transport to a cloud data center for upload to a cloud storage system. Multiple versions of a segment of data (e.g., of a file or a blob) are maintained at various points in the disclosed system and the disclosed technology ensures that the most recent version is the version ultimately stored on the cloud storage system.

Abstract: Transportable storage devices are communicatively coupled behind one or more dedicated “edge” data servers to take advantage of the benefits of the data servers and transportable storage devices while limiting their disadvantages. Each edge data server ingests data from one or more client devices and copies the data to one or more of the transportable storage devices for eventual transport to a cloud data center for upload to a cloud storage system. Multiple versions of a segment of data (e.g., of a file or a blob) are maintained at various points in the disclosed system and the disclosed technology ensures that the most recent version is the version ultimately stored on the cloud storage system.

Abstract: Transportable storage devices are communicatively coupled behind one or more dedicated “edge” data servers to take advantage of the benefits of the data servers and transportable storage devices while limiting their disadvantages. Each edge data server ingests data from one or more client devices and copies the data to one or more of the transportable storage devices for eventual transport to a cloud data center for upload to a cloud storage system. Multiple versions of a segment of data (e.g., of a file or a blob) are maintained at various points in the disclosed system and the disclosed technology ensures that the most recent version is the version ultimately stored on the cloud storage system.

Abstract: Transportable storage devices are communicatively coupled behind one or more dedicated “edge” data servers to take advantage of the benefits of the data servers and transportable storage devices while limiting their disadvantages. Each edge data server ingests data from one or more client devices and copies the data to one or more of the transportable storage devices for eventual transport to a cloud data center for upload to a cloud storage system. Object identifiers of objects stored on the transportable storage devices are maintained in a namespace of the data servers after decoupling of the transportable storage devices from the data servers so that the object identifiers remain visible to client devices.

Abstract: Described herein is a system and method for performing a clustered coherent cloud read cache without coherency messaging. At a cloud reader agent having a read cache, a request for a particular portion of data is received from a client. The request includes an identifier of the node making the request, a current time on the node making the request, a last stubbed time of the particular portion of data, and/or an identifier of the particular portion of data. When the particular portion of data is stored in the read cache of the cloud reader agent, the cloud reader agent can determine whether the cached particular portion of data is valid based, at least in part, upon the received identifier of the node making the request, the received last stubbed time of the particular portion of data, and/or, a stored time associated with the cached particular portion of data.

Abstract: Methods for performing work operations and management of hierarchical datasets are performed by systems and devices. Changes to portions of information in datasets are made via client devices, and such changes are intercepted by an independently-operating tracker. The tracker flags portions being changed as work needed, along with any other dataset portions from which the portion to be changed depends. A work service independently discovers portion(s) designated as work needed to perform work thereon, while dataset branches/leaves not flagged are ignored in discovery. Upon work completion, any changes made to the portion(s) that underwent the work, or to any depending portions, while the work was performed are identified. Such changes result in aborting the performed work and setting work needed indications for any changed dependents. Work is re-performed for the portion when all portion and dependent portion work completes. Work is then performed for higher-level portions that are flagged.

Abstract: Transportable storage devices are communicatively coupled behind one or more dedicated “edge” data servers to take advantage of the benefits of the data servers and transportable storage devices while limiting their disadvantages. Each edge data server ingests data from one or more client devices and copies the data to one or more of the transportable storage devices for eventual transport to a cloud data center for upload to a cloud storage system. Object identifiers of objects stored on the transportable storage devices are maintained in a namespace of the data servers after decoupling of the transportable storage devices from the data servers so that the object identifiers remain visible to client devices.

Abstract: Transportable storage devices are communicatively coupled behind one or more dedicated “edge” data servers to take advantage of the benefits of the data servers and transportable storage devices while limiting their disadvantages. Each edge data server ingests data from one or more client devices and copies the data to one or more of the transportable storage devices for eventual transport to a cloud data center for upload to a cloud storage system. Multiple versions of a segment of data (e.g., of a file or a blob) are maintained at various points in the disclosed system and the disclosed technology ensures that the most recent version is the version ultimately stored on the cloud storage system.

Abstract: Described herein is a system and method for performing a clustered coherent cloud read cache without coherency messaging. At a cloud reader agent having a read cache, a request for a particular portion of data is received from a client. The request includes an identifier of the node making the request, a current time on the node making the request, a last stubbed time of the particular portion of data, and/or an identifier of the particular portion of data. When the particular portion of data is stored in the read cache of the cloud reader agent, the cloud reader agent can determine whether the cached particular portion of data is valid based, at least in part, upon the received identifier of the node making the request, the received last stubbed time of the particular portion of data, and/or, a stored time associated with the cached particular portion of data.

Abstract: Methods for performing work operations and management of hierarchical datasets are performed by systems and devices. Changes to portions of information in datasets are made via client devices, and such changes are intercepted by an independently-operating tracker. The tracker flags portions being changed as work needed, along with any other dataset portions from which the portion to be changed depends. A work service independently discovers portion(s) designated as work needed to perform work thereon, while dataset branches/leaves not flagged are ignored in discovery. Upon work completion, any changes made to the portion(s) that underwent the work, or to any depending portions, while the work was performed are identified. Such changes result in aborting the performed work and setting work needed indications for any changed dependents. Work is re-performed for the portion when all portion and dependent portion work completes. Work is then performed for higher-level portions that are flagged.

Abstract: The efficient backing up of a hierarchical system in cloud blob storage. The hierarchical structure of the system as it existed at a prior instance in time is reconstructed. A change journal that represents changes in the file system that prior instant in time is then used to formulate an updated file system hierarchy as it exists at a second instant in time. An updated injected representation of the file system, and updated file system reversal information is then formulated and provided to cloud blob storage. The injected representation of the file system is a one-to-one function of the content of the file system, in that the reversal information can be used to recover the content of the file system. Injected representations of various nodes in the system hierarchy may also be remotely stored.

Abstract: An incremental synchronous hierarchical system restoration system. A hierarchical system, such as a file system, that has an incompletely populated hierarchy, such as a directory structure, is incrementally restored in response to each of at least some successive hierarchical system commands. For instance, in some embodiments, the hierarchical system restoration may be a just-in-time hierarchical system restoration that restores portions of the hierarchical system hierarchy just in time to provide the visualizations used for each hierarchical system command response. By so doing, the restoration system provides the illusion that the hierarchical system has already been restored since the appropriate visualization and functionality is provided in response to each hierarchical system command, just as a fully populated hierarchical system would. The manner of acquiring and populating file system hierarchies is especially efficient so as to make such restoration possible in substantial real-time.

Abstract: The efficient backing up of a hierarchical system in cloud blob storage. The hierarchical structure of the system as it existed at a prior instance in time is reconstructed. A change journal that represents changes in the file system that prior instant in time is then used to formulate an updated file system hierarchy as it exists at a second instant in time. An updated injected representation of the file system, and updated file system reversal information is then formulated and provided to cloud blob storage. The injected representation of the file system is a one-to-one function of the content of the file system, in that the reversal information can be used to recover the content of the file system. Injected representations of various nodes in the system hierarchy may also be remotely stored.

Abstract: An operating system including a software development environment is programmed into the on-chip flash memory of a system-on-a-chip type microcontroller. The software development environment is configured to reside entirely in the microcontroller's on-chip flash memory and includes an editor, a line-by-line bytecode compiler, a flasher, and an interactive debugger. A user operating a terminal emulator on a host computer connects to the microcontroller chip by means of a serial (USB) connection based on an FTDI protocol, or other serial link, in order to develop a BASIC program for the embedded system. The operating system is configured to permit external I/O pins on the microcontroller chip to be mapped to special “pin variables” for manipulation or examination by the user program, and to manage internal peripherals (timers, UARTs) of the microcontroller chip so as to permit application-level interrupt handling.