Microsoft Technology Licensing, LLC

Jason Daniel Shay

Ivelin Lyubenov Zheglov

Spencer Alan Bishop

Michael S Murstein

Marian Trandafir

Ran Kalach

James Robert Benton

Cristian Teodorescu

Kashif Hasan

Fenghua Yuan

Tanu Mutreja

Jose J Figueroa-Morales

Gunjan Jain

Diaa Eldin Mohamed Hazem Fathalla

Surender Kumar

James Benton

Michael Murstein

Non-limiting examples of the present disclosure describe implementation of an exemplary synchronization protocol to identify file data for synchronization as well as negotiate how to achieve data transport for synchronization of the file data. In one example, a request for synchronization of data is received from a processing device. In response to receiving the request, a response is generated. The response may comprise: identification of file data for synchronization, instructions for accessing the file data and instructions indicating a data transport protocol to utilize to obtain the file data. The response may be transmitted to the processing device, for example, to enable the processing device to synchronize file data. Other examples are also described.

Synchronizing file data between computer systems

A storage system for transactional data storage includes a key/value store comprising a first plurality of rows and a second plurality of rows, each of the first plurality of rows including a first key associated with a respective row of a database and a transaction state associated with the respective row, and each of the second plurality of rows including a second key associated with a respective row of the database and a data version of the respective row. The storage system is configured to provide a transaction state to and receive an updated transaction state from a plurality of different systems, each comprising a database engine to perform transactional database operations on the key/value store.

Transactional database layer above a distributed key/value store

Disclosed herein is a system and method to synchronize files from a hosted file system where the client endpoint devices have direct access to the files stored on a hosted file store. When the client desires to synchronize with the files stored on the hosted file store the process identifies a sync role that can process the request. The particular sync role does not need to maintain state with the client device or the file store. The state necessary for the processing of the synchronization process is maintained separate from the sync role such that any sync role in the system can pick up the requests and process the requests. Once the role has been selected the synchronization process proceeds as normal. As state is not maintained by the sync role multiple roles can process the request or two roles can handle different portions of the process.

Hosted file sync with stateless sync nodes

A first server computing device, including a processor configured to receive, from a first application instance, a first access request for a file. The first access request may include a first modification privilege request and a modification privilege sharing request. The processor may determine that the file is not locked for editing and grant the first application instance access to the file with modification privileges indicated by the first modification privilege request and without modification privilege sharing permissions indicated by the modification privilege sharing request. The processor may set the file to be locked for editing. The processor may receive, from a second application instance, a second access request including a second modification privilege request. The processor may determine that the file is locked for editing and deny the second application instance access to the file.

Setting modification privileges for application instances

A system hosts a file system representing a replica of file systems hosted on a plurality of nodes, each node storing data on a first storage medium. The system stores data on a second storage medium that is slower than the first storage medium. The system stores on the second storage medium a file received from one of the nodes when the file remains un-accessed by the nodes for a predetermined period of time. The first storage medium on the plurality of nodes stores a pointer to the file and not the data content of the file stored on the second storage medium. The system provides the file from the second storage medium to the first storage medium on one of the nodes while providing the plurality of nodes read and write access to the file stored on the second storage medium using the pointer on the first storage medium.

Reliable hierarchical storage management with data synchronization

A computing system is configured to be coupled to a remote storage system. The remote storage system comprises a key/value store. The computing system is configured to perform transactions on data stored at the remote storage system. The system includes a database client. The database client includes an interface configured to allow a user to request database operations using the database client. The system further includes a database engine coupled to the database client. The database engine is configured to receive requests for database operations from the database client. The database engine is further configured to obtain and operate on transaction state stored as one or more key/value pairs in the key/value store at the remote storage system from the remote storage system. The database engine is configured to transactionally perform data operations, using the transaction state, on one or more data key/value pairs in the key/value store.

Embodiments described herein are directed to enabling a user to modify data stored locally during a data migration process in which the user's data is being transferred to the cloud. For instance, a synchronization service requests the user's device (e.g., a client-based server) to provide a hash value for each data object maintained thereby (including modified data objects) and compares the hash values to hash values generated for the data uploaded to the cloud. If a hash value provided by the server does not match any of the hash values generated for the uploaded data, this means that the data object associated with the unmatched hash value has been modified since the initiation of the data transfer process. The synchronization service receives the modified data object from the server and uploads it to the cloud, thereby synchronizing the data uploaded to the cloud with the data locally-maintained by the server.

Synchronizing in-use source data and an unmodified migrated copy thereof

Disclosed herein is a system and method that can be used to synchronize files from a hosted file system where the client endpoint devices have direct access to the files stored on a hosted file store/system. When the client synchronizes with the files stored on the hosted file store the synchronization process identifies the files that need to be synchronized with the client and prepares batches of files to be synced. During the process of synchronization the files are not locked from other user's being able to use the files. If the file is modified by another endpoint during the file synchronization process the file will not be synchronized with the client device during the particular synchronization process. In this way synchronization becomes possible with the hosted service without impacting the performance of other devices that use and access the data in the hosted file store.

Growing community of inventors

Seattle, WA, United States of America

Jason Daniel Shay