Abstract: Kernel objects for implementing a transaction have a security descriptor applied thereto. The kernel objects include, at least, a transaction object, a resource management object, and an enlistment object. The security descriptor, otherwise known as an access control list, identifies at least one user, an operation to be performed on the kernel object to which the security descriptor is applied, and a right indicating that the identified user is permitted or prohibited to perform the operation.

Abstract: Transactions among kernel objects utilize application program interfaces (APIs) to implement operations on a transaction object and APIs to implement operations on a resource manager object.

Abstract: 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.

Abstract: 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.

Abstract: Kernel objects for implementing a transaction have a security descriptor applied thereto. The kernel objects include, at least, a transaction object, a resource management object, and an enlistment object. The security descriptor, otherwise known as an access control list, identifies at least one user, an operation to be performed on the kernel object to which the security descriptor is applied, and a right indicating that the identified user is permitted or prohibited to perform the operation.

Abstract: 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.

Abstract: Transactions among kernel objects utilize application program interfaces (APIs) to implement operations on a transaction object and APIs to implement operations on a resource manager object.

Abstract: 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.