Microsoft Technology Licensing, LLC

Microsoft Corporation

Andrew James Edwards

Shane Kumar Mainali

Bradley Gene Calder

Ju Wang

Maneesh Sah

Hoi Huu Vo

David Mitford Gillies

Hon Keat W Chan

Aaron William Ogus

Krishnan Varadarajan

Rushi Srinivas Surla

Amitabh Srivastava

Carlos P Gomes

David Allen Goebel

Ronnie Chaiken

Yikang Xu

Ishai Ben Aroya

Ken B Pierce

Jiyang Liu

Mark L Roberts

Ozan Demir

Weiping Zhang

Cheng Huang

Matthew Douglas Hendel

Venkates Paramasivam Balakrishnan

Ivan Brugiolo

Huseyin Simitci

Samer Arafeh

Ioan Oltean

Yue Zuo

Anu Engineer

Ovais Khan

Patrick L McDonald

John A Lefor

Manan Shah

Sivakumar Kalva

Jaidev Haridas

Gideon Andreas Yuval

Jiesheng Wu

Shuvabrata Ganguly

Jegan Devaraju

Michael E Roberson

Gregory A Eigsti

Bruce M Kuramoto

Jean Ghanem

Vinod Grover

Saad Syed

Karthik Raman

Pavel Anatolievich Dournov

Darek Josip Mihocka

Chun Yuan

David Read Tarditi, Jr

Quan Zhang

Mark Ronald Plesko

Zichen Sun

Georgi M Chalakov

Manish Chablani

Satish Narayanasamy

Charles L Mitchell

Corey M Sanders

Sundar P Subramani

Madhav Himanshubhai Pandya

Zhenghao Wang

Julian Burger

Marcus Swenson

Sanjay Bhansali

Dzmitry Suponau

Andrew Edward Ayers

Ronald C Murray

Ho-Yuen Chau

Muhammad Junaid Shahid

Wen-Ke Chen

Akella V S Sastry

Kenneth Bryant Pierce

Pradeep Seela

Maxim Khutornenko

Girish Saini

Krisjan David Fritz

James Jordan Tigani

Kaviyarasan Rajendran

Michael Hauss

Stuart D De Jong

Jianhua Yan

S Craig Schertz

Abhishek Singh Baghel

Ameya Bhagat

Ping-Yao Tseng

Fnu Arunachaleshwar

Shuitao Fan

Aung Maw Oo

Phillip Taron

Jaiden Haridas

Jegan Devanraju

Methods, systems, apparatuses, and computer program products are provided that enable immediate access to data associated with a source blob. The foregoing is achieved by creating a copy-on-read blob based on the source blob and a link blob based on the copy-on-read blob for each virtual machine to be deployed. When creating the copy-on-read blob, the source blob is not copied. Instead, data from the source blob is copied to the copy-on-read blob upon request by a virtual machine. Subsequent requests for that data are retrieved from the copy-on-read blob. Each link blob stores write data provided by its corresponding virtual machine. When a virtual machine requests data, its corresponding link blob is checked for the data. If the data is not stored therein, the copy-on-read blob is checked for the data. If the copy-on-read blob does not store the data, the data is retrieved from the source blob.

Providing instant and distributed access to a source blob via copy-on-read blobs and link blobs

In various embodiments, methods and systems for providing access to file systems are provided. An SFA-based operation having an operation modifier for a file in a file system is received. The SFA-based operation is defined based on a file-representational state transfer (REST) interface. The SFA-REST interface comprises integrated functionality of an SFA protocol and REST protocol. The SFA-based operation is executed using the operation modifier. A REST-based operation for the file in the distributed file storage is received. The REST-based operation is defined based on the SFA-REST interface. The operation modifier is referenced in order to execute the REST-based operation. The REST-based operation based on the SFA-REST interface. A schema can be implemented for accessing the file system. The schema includes tables to store files, the table comprises fields corresponding to elements of a SFA-REST interface. A snapshot component can be implemented to backup file shares in the file system.

File service using a shared file access-rest interface

In various embodiments, methods and systems for implementing a distributed metadata management system in distributed storage systems are provided. A distributed storage system operates based on data storage resources (e.g., extents and streams). The distributed metadata management system is implemented for extent and stream metadata to facilitate the scalability of metadata processing. The distributed storage system implements extent managers and stream managers that independently manage extent and stream metadata, respectively. The extent managers are associated with an extent table that stores extent metadata. The stream managers are associated with streams that store associations with extents. The distributed metadata management system can also utilize a bootstrap layer that leverages components of a legacy distributed storage system to facilitate distributed management of extent and stream metadata. The bootstrap layer is used to store the extent table as a system table and to persist the state of the stream manager as system streams.

Distributed metadata management in a distributed storage system

A distributed file system that includes multiple computing node tiers. Each of at least some of the multiple computing node tiers has multiple computing nodes having like characteristics. The distributed file system also has an executable component in the form of a distribution component that comprises logic that distributes state of file system entities amongst the computing node tiers. The distribution is performed so that latency of file system requests are reduced due to state responsive to many requests being much closer latency wise to the file system requestor(s). Furthermore, the distribution considers durability guarantees of the state, thereby meeting durability guarantees.

File system with distributed entity state

A system receives a request to store data at a first layer of servers in a cluster, configured to authenticate and authorize the request. The system compresses the data upon authenticating and authorizing the request and encrypts the compressed data at the first layer of servers when encryption is enabled. The system sends the request and the encrypted data to a second layer of servers in the cluster, configured to store data structures used to manage data storage in a third layer of servers in the cluster, and to distribute the request and the encrypted data to the third layer of servers using the data structures. The system stores the encrypted data in the third layer of servers. Encrypting the data at the first layer of servers reduces latency associated with transferring the data between the first, second, and third layers of servers.

Fully managed account level blob data encryption in a distributed storage environment

A cloud storage system includes a processor and a non-transitory computer-readable medium to store blob table management instructions for execution by the processor. The blob table management instructions are configured to manage a plurality of storage requests for a blob stored in a storage stamp as snapshots in a blob table and selectively create a user snapshot of at least one of the snapshots in the blob table. When automatic snapshots are enabled, the blob table management instructions are configured to receive a first request to overwrite the blob. If the first request does not further specify a key of the one of the snapshots in the blob table, the blob table management instructions are configured to add a new snapshot to the blob table and maintain storage of a prior snapshot of the blob for a maximum period.

Distributed data storage system with automatic snapshots, user snapshots and soft delete

In various embodiments, methods and systems for implementing hash-based partitioning in distributed computing systems are provided. At a high level, a distributed computing system having an underlying range-based partitioning architecture for storage may be configured as a hash-based partitioning system, for example, a hybrid range-hash table storage. An operations engine of the hash-based partitioning system receives a tenant request to provision input/output operations per second (IOPS). The tenant request comprises a requested number of IOPS. Based on the tenant request, a provisioning operation to provision IOPS in a hybrid range-hash table storage with hash-based partitioning is determined. The provisioning operation is selected from one of the following: a table creation provisioning operation, an IOPS increase provisioning operation, and an IOPS decrease provisioning operation. The selected provisioning operation is executed for a corresponding table. A user request for data is processed using the table associated with the requested number of IOPS.

Hash-based partitioning system

Techniques for implementing zone redundant computing services in distributed computing systems are described herein. In one embodiment, a computing device is configured to query a database in a first availability zone for a list of computing services corresponding to a user account and provided by servers in a second availability zone different than the first availability zone. The computing device can then selects one or more computing services provided by the servers in the second availability zone from the queried list of computing services and transmit an instruction to the servers in the second availability zone for performing the requested data operation.

Zone redundant computing services using multiple local services in distributed computing systems

In various embodiments, methods and systems for implementing garbage collection in distributed storage systems are provided. The distributed storage system operates based on independent management of metadata of extent and stream data storage resources. A hybrid garbage collection system based on reference counting garbage collection operations and mark-and-sweep garbage collection operations is implemented. An extent lifetime table that tracks reference weights and mark sequences for extents is initialized and updated based on indications from extent managers and stream managers, respectively. Upon determining that an extent is to be handed-off from weighted reference counting garbage collection operations to mark-and-sweep garbage collection operations, a reference weight field for the extent is voided and a mark sequence field of the extent is updated. The mark sequence field is updated with a latest global sequence number. The mark-and-sweep garbage collection operations are utilized to reclaim the extent when the extent is no longer referenced.

Hybrid garbage collection in a distributed storage system

A system receives data of one or more types from one or more sources having distinct identities for storing the data in a distributed storage system. The system stores metadata associated with storing the data in data structures in the distributed storage system. The system selects a portion of the data and a portion of the metadata associated with storing the data in the distributed storage system. The system compresses the selected portions of the data and the metadata, encrypts the compressed data and metadata using a single key or using a separate key for each data type, and stores the encrypted compressed data and metadata in the distributed storage system. The system also encrypts unencrypted metadata and associated data during defragmentation procedure.

Encrypting object index in a distributed storage environment

A system stores data in data units in a cluster in a cloud computing system, the data stored in the data units being encrypted or unencrypted depending on whether encryption is enabled or disabled when storing data in the data units. The system identifies one or more data units to defragment and defragments the identified data units by writing the data from the identified data units to one or more new data units and by releasing the identified data units for storing new data. The system encrypts unencrypted data from the identified data units when writing the data from the identified data units to the one or more new data units.

Encrypting existing live unencrypted data using age-based garbage collection

Cloud computing platforms having computer-readable media that perform methods for facilitating communications with storage. A request having a first-interface format to access storage is intercepted. The first interface format of the request supports access to a virtual hard drive (VHD). The request is translated to a blob request having a blob interface format. The blob interface format of the blob request supports access to a plurality of blobs of data in a blob store. The blob request is communicated to a blob interface such that the blob request is executed in managing the plurality of blobs.

Methods and systems for facilitating communications with storage

Growing community of inventors

Bellevue, WA, United States of America

Andrew James Edwards