Microsoft Technology Licensing, LLC

Ernie Pistor

Richard Paul Testardi

Andrea D'Amato

Mohit Kumar Garg

Devidas Joshi

Gautam Gopinadhan

Sebastien Charles

John Renaud

Stephen Wade Wolfe

Suhas Prakash

Cameron Michael Hall

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.

Synchronizing online and offline transfer of data to cloud storage system

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.

Namespace data object name persistence after decoupling of transportable storage device from data server

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.

Clustered coherent cloud read cache without coherency messaging

Growing community of inventors

Brookline, NH, United States of America

Ernie Pistor