Microsoft Technology Licensing, LLC

Diaa E Fathalla

David Matthew Kruse

Mathew George

James T Pinkerton

Thomas Ewan Jolly

Ali Ediz Turkoglu

Sai Sudhir Anantha Padmanaban

Prashanth Prahalad

Thomas E Jolly

Implementing a high availability mode. A distributed computing environment includes a plurality of nodes. Each of the nodes has an instance of a particular storage service. One or more of the instances have one or more cluster shared filesystems coupled to them. A method includes monitoring arrivals and departures of cluster shared file systems. The method further includes identifying the arrival of one or more clustered shared file systems previously attached to a different instance of the storage service on a different node and being accessible by following one or more namespace partitions located in that clustered shared file system. As a result, the method further includes connecting the instance of the storage service to the one or more arriving clustered shared file systems and exposing the one or more namespace partitions located in that clustered shared file system.

Multi-level high availability model for an object storage service

Described are embodiments for providing unique identifiers for files or objects across servers in a server cluster. Embodiments include generating a unique identifier that includes at least three portions. The first portion includes a node identifier which identifies the particular server in a cluster which created the unique identifier. The second portion includes a major sequence number that is incremented when a server is rebooted or otherwise taken off-line and then brought back online. Additionally, the major sequence number is incremented when all of the minor sequence numbers, which are included in a third portion of the unique identifier, have been used. The minor sequence numbers in the third portion are incremented for every unique file or object requested.

Cluster unique identifier

An application instance identifier is employed with various systems and methods in order to provide a requestor with continuous access to a resource when operating in a client clustered environment. A requestor residing on a first client may attempt to access a resource. The first client sends a request to access the resource. The request may be associated with an application instance identifier that identifies the requestor. At some point, the first client fails and the requestor is associated with a second client via a failover mechanism. The second client sends a second request to access the resource on behalf of the requestor. The second request is associated with the requestor's application instance identifier. The application instance identifier is used to identify the second request as belonging to the same requestor as the first request, thereby granting the second request to access the resource while avoiding a conflict situation.

Clustered client failover

A hybrid environment may be used for addressing application compatibility between a host operating system and one or more application(s) optimized to run on a different ('guest') version of the host operating system. A thunking wrapper consisting of a native thunking layer, a service thunking layer, and a subsystem thunking layer provides translation between the guest application and the host operating system for a seamless interface. Multiple thunking wrappers may be included to support application compatibility between multiple guest operating systems and the host operating system.

Application compatibility using a hybrid environment

A method for testing a software shim is provided, in which a skeleton executable file is altered so that it mimics the executable file for which the shim is intended. The alterations made to the skeleton executable file may include one or more of the following: changing the file name, padding the file and changing the calculated checksum of the file.

Method for testing a software shim

An application program interface (API) replay tool and method is disclosed for modeling and testing APIs. The replay tool receives as input a set of API calls and associated context information and resources. A set of components are called to map variables and a context into the replay tool environment. An API builder translates the original API call (including mapping memory references of parameters) into a sequence of assembly code instructions, constituting the replayed API call, which is placed in an execution buffer. The execution buffer is thereafter executed in a replay environment including a set of resources extracted from a source binary file associated with the replayed API. Thereafter, the operating system, or other suitable consumer of API calls, executes the call in the context recreated by the API replay tool prior to passing the call.

Growing community of inventors

Redmond, WA, United States of America

Diaa E Fathalla