Microsoft Technology Licensing, LLC

Jacob Lacouture

Surendra Verma

Brian D Andrew

Jonathan M Cargille

Jon Cargille

Balan Sethu Raman

Sameet Harishanker Agarwal

Shishir P Pardikar

Pradeep Madhavarapu

Pradeep Jnana Madhavarapu

A system and method supporting multiple independent transactional resource managers on a single logical volume, in which each resource manager is a unit of storage management. Each resource manager independently maintains metadata associated with a collection of files that are contained within the scope of a resource manager, such as the files within a subdirectory corresponding to the resource manager. A general architecture allows databases or other entities to integrate with a transactional file system volume via the resource managers, whereby each database has its files independently associated with a transactional resource manager such that database operations do not affect other operations on the volume. Having independent resource managers allows different levels of performance, reliability, feature availability, and manageability to be specified within a single volume. Functions to create, start, and shut down a resource manager are also provided, along with other functions that facilitate resource manager usage.

Method and system for supporting multiple independent transactional resource managers on a single logical volume

A system to perform transacted remote file operations over a network includes a client and a server. The client and server each include a transaction manager (TM) and a file system (FS). The client also includes a redirector (RDR), while the server includes a server application (SRV). The RDR receives a request for a remote transacted file operation. In response, the RDR retrieves the transaction from the request. The RDR may use the TM to marshall the transaction for transmission to the server. The RDR sends the transaction to the server over the network. The SRV component receives the transaction, which the TM and FS of the server then use to perform the file operation. The server then returns the file operation result to the client via the network.

Method and system for transacted file operations over a network

An external request to perform a file operation within a resource manager is received. The resource manager selects a resource manager file identifier that is to be an attribute of a file associated with the file operation. The file operation and the resource manager file identifier are logged in a log entry of a log. Subsequent to logging the log entry, the log entry is accessed during a forward pass through the log, for example, during a roll-forward recovery. If it is determined that the resource manager file identifier in the log entry is assigned to the file, the first log entry is not processed. On the other hand, if it is determined that the resource manager file identifier in the log entry is not assigned to the file, the resource manager file identifier is selected to be assigned to a file when the first log entry is processed.

Identifying files within a namespace

The location of appropriate undo data necessary for reversing an effect of an operation performed at a computer system is identified during a forward pass through a log. A cycle count can be used to determine if appropriate undo data is stored in an object or is stored in auxiliary storage. If appropriate undo data is stored in an object and the undo data would be potentially lost by processing a redo log entry to modify the contents of the object, the appropriate undo data is copied to auxiliary storage. In some embodiments, a secondary computer system receives log entries from a primary computer system. The secondary computer system can identify undo data necessary to reverse an effect of an operation performed at the secondary computer system from received log entries. Identified undo data can be copied auxiliary storage at the secondary computer system.

Growing community of inventors

Redmond, WA, United States of America

Jacob Lacouture