Patents by Inventor Roopesh C. Battepati
Roopesh C. Battepati has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Patent number: 11775476Abstract: Examples described herein generally relate to maintaining a snapshot of a multitier distributed file system. A snapshot directory volume of a directory volume can be created at least in part by copying, to the snapshot directory volume, metadata of the directory volume. Based on a file access request, it can be determined whether the file has not been snapshotted. If not, a snapshot file record of the file, and associated with the snapshot directory volume.Type: GrantFiled: December 20, 2021Date of Patent: October 3, 2023Assignee: MICROSOFT TECHNOLOGY LICENSING, LLCInventors: Mathew George, David Matthew Kruse, Vladimir Petter, Roopesh C Battepati, Henry Gabryjelski
-
Patent number: 11570255Abstract: Systems and methods are disclosed for clients and servers operating in a scaled cluster environment. Efficiencies are introduced to the process of connecting a client to a clustered environment by providing the client with the ability to attempt a connection with multiple servers in parallel. Servers operating the in the clustered environment are also capable of providing persistent storage of file handles and other state information. Ownership of the state information and persistent handles may be transferred between servers, thereby providing clients with the opportunity to move from one server to another while maintaining access to resources in the clustered environment.Type: GrantFiled: March 2, 2020Date of Patent: January 31, 2023Assignee: Microsoft Technology Licensing, LLCInventors: David M. Kruse, Daniel E. Lovinger, Thomas E. Jolly, James T. Pinkerton, Mathew George, Roopesh C. Battepati, Mingdong Shang
-
Publication number: 20220114141Abstract: Examples described herein generally relate to maintaining a snapshot of a multitier distributed file system. A snapshot directory volume of a directory volume can be created at least in part by copying, to the snapshot directory volume, metadata of the directory volume. Based on a file access request, it can be determined whether the file has not been snapshotted. If not, a snapshot file record of the file, and associated with the snapshot directory volume.Type: ApplicationFiled: December 20, 2021Publication date: April 14, 2022Inventors: Mathew GEORGE, David Matthew KRUSE, Vladimir PETTER, Roopesh C BATTEPATI, Henry GABRYJELSKI
-
Patent number: 11204892Abstract: Examples described herein generally relate to maintaining a snapshot of a multitier distributed file system. A snapshot directory volume of a directory volume can be created at least in part by copying, to the snapshot directory volume, metadata of the directory volume. Based on a file access request, it can be determined whether the file has not been snapshotted. If not, a snapshot file record of the file, and associated with the snapshot directory volume.Type: GrantFiled: March 21, 2019Date of Patent: December 21, 2021Assignee: Microsoft Technology Licensing, LLCInventors: Mathew George, David Matthew Kruse, Vladimir Petter, Roopesh C Battepati, Henry Gabryjelski
-
Publication number: 20200301880Abstract: Examples described herein generally relate to maintaining a snapshot of a multitier distributed file system. A snapshot directory volume of a directory volume can be created at least in part by copying, to the snapshot directory volume, metadata of the directory volume. Based on a file access request, it can be determined whether the file has not been snapshotted. If not, a snapshot file record of the file, and associated with the snapshot directory volume.Type: ApplicationFiled: March 21, 2019Publication date: September 24, 2020Inventors: Mathew GEORGE, David Matthew KRUSE, Vladimir PETTER, Roopesh C. BATTEPATI, Henry GABRYJELSKI
-
Publication number: 20200204633Abstract: Systems and methods are disclosed for clients and servers operating in a scaled cluster environment. Efficiencies are introduced to the process of connecting a client to a clustered environment by providing the client with the ability to attempt a connection with multiple servers in parallel. Servers operating the in the clustered environment are also capable of providing persistent storage of file handles and other state information. Ownership of the state information and persistent handles may be transferred between servers, thereby providing clients with the opportunity to move from one server to another while maintaining access to resources in the clustered environment.Type: ApplicationFiled: March 2, 2020Publication date: June 25, 2020Applicant: Microsoft Technology Licensing, LLCInventors: David M. KRUSE, Daniel E. LOVINGER, Thomas E. JOLLY, James T. PINKERTON, Mathew GEORGE, Roopesh C. BATTEPATI, Mingdong SHANG
-
Patent number: 10630781Abstract: Systems and methods are disclosed for clients and servers operating in a scaled cluster environment. Efficiencies are introduced to the process of connecting a client to a clustered environment by providing the client with the ability to attempt a connection with multiple servers in parallel. Servers operating the in the clustered environment are also capable of providing persistent storage of file handles and other state information. Ownership of the state information and persistent handles may be transferred between servers, thereby providing clients with the opportunity to move from one server to another while maintaining access to resources in the clustered environment.Type: GrantFiled: August 25, 2015Date of Patent: April 21, 2020Assignee: Microsoft Technology Licensing, LLCInventors: David M. Kruse, Daniel E. Lovinger, Thomas E. Jolly, James T. Pinkerton, Mathew George, Roopesh C. Battepati, Mingdong Shang
-
Patent number: 9462039Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.Type: GrantFiled: September 2, 2014Date of Patent: October 4, 2016Assignee: Microsoft Technology Licensing, LLCInventors: Mathew George, David M. Kruse, James T. Pinkerton, Roopesh C. Battepati, Tom Jolly, Paul R. Swan, Mingdong Shang, Daniel Edward Lovinger
-
Publication number: 20150365482Abstract: Systems and methods are disclosed for clients and servers operating in a scaled cluster environment. Efficiencies are introduced to the process of connecting a client to a clustered environment by providing the client with the ability to attempt a connection with multiple servers in parallel. Servers operating the in the clustered environment are also capable of providing persistent storage of file handles and other state information. Ownership of the state information and persistent handles may be transferred between servers, thereby providing clients with the opportunity to move from one server to another while maintaining access to resources in the clustered environment.Type: ApplicationFiled: August 25, 2015Publication date: December 17, 2015Applicant: MICROSOFT TECHNOLOGY LICENSING, LLCInventors: David M. Kruse, Daniel E. Lovinger, Thomas E. Jolly, James T. Pinkerton, Mathew George, Roopesh C. Battepati, Mingdong Shang
-
Publication number: 20140372521Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.Type: ApplicationFiled: September 2, 2014Publication date: December 18, 2014Applicant: Microsoft CorporationInventors: Mathew George, David M. Kruse, James T. Pinkerton, Roopesh C. Battepati, Tom Jolly, Paul R. Swan, Mingdong Shang, Daniel Edward Lovinger
-
Patent number: 8856582Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.Type: GrantFiled: June 30, 2011Date of Patent: October 7, 2014Assignee: Microsoft CorporationInventors: Mathew George, David M. Kruse, James T. Pinkerton, Roopesh C. Battepati, Tom Jolly, Paul R. Swan, Mingdong Shang, Daniel Edward Lovinger
-
Patent number: 8631277Abstract: A connection state system is described herein that allows a client to resume a connection with a server or a different replacement server by remotely storing client state information in association with a resume key. The system provides a resume key filter operating at the server that facilitates the storing of volatile server state information. The state information can include information such as oplocks, leases granted to a client, and in-flight operations on a file handle. The resume key filter driver sits above the file system, which allows multiple file access protocols to use the filter. Upon a failover event, such as a server going down or losing connectivity to a client, the system can bring up another server or the same server and reestablish state for file handles held by various clients using the resume key filter.Type: GrantFiled: December 10, 2010Date of Patent: January 14, 2014Assignee: Microsoft CorporationInventors: Paul R. Swan, Mathew George, David M. Kruse, Roopesh C. Battepati, Michael C. Johnson
-
Publication number: 20130067095Abstract: Systems and methods are disclosed for clients and servers operating in a scaled cluster environment. Efficiencies are introduced to the process of connecting a client to a clustered environment by providing the client with the ability to attempt a connection with multiple servers in parallel. Servers operating the in the clustered environment are also capable of providing persistent storage of file handles and other state information. Ownership of the state information and persistent handles may be transferred between servers, thereby providing clients with the opportunity to move from one server to another while maintaining access to resources in the clustered environment.Type: ApplicationFiled: September 9, 2011Publication date: March 14, 2013Applicant: Microsoft CorporationInventors: David M. Kruse, Daniel E. Lovinger, Thomas E. Jolly, James T. Pinkerton, Mathew George, Roopesh C. Battepati, Mingdong Shang
-
Publication number: 20130007518Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.Type: ApplicationFiled: June 30, 2011Publication date: January 3, 2013Applicant: Microsoft CorporationInventors: Mathew George, David M. Kruse, James T. Pinkerton, Roopesh C. Battepati, Tom Jolly, Paul R. Swan, Mingdong Shang, Daniel Edward Lovinger
-
Patent number: 8214641Abstract: Aspects of the subject matter described herein relate to providing file access in a multi-protocol environment. In aspects, a file server is operable to receive requests formatted according to two or more file access protocols. If a request is formatted according to a first file access protocol, the file server applies access rights associated with the file to an account associated with a requester to determine whether to grant access. If the request is formatted according to the second file access protocol, the file server may first attempt to find an account for the requester. If an account is not found, the file server may then grant access based on access rights associated with the file as applied to information in the request without consulting an account on the file server.Type: GrantFiled: August 23, 2007Date of Patent: July 3, 2012Assignee: Microsoft CorporationInventors: Scott A Field, Paul J Leach, Roopesh C Battepati, Michael C Johnson
-
Publication number: 20120151249Abstract: A connection state system is described herein that allows a client to resume a connection with a server or a different replacement server by remotely storing client state information in association with a resume key. The system provides a resume key filter operating at the server that facilitates the storing of volatile server state information. The state information can include information such as oplocks, leases granted to a client, and in-flight operations on a file handle. The resume key filter driver sits above the file system, which allows multiple file access protocols to use the filter. Upon a failover event, such as a server going down or losing connectivity to a client, the system can bring up another server or the same server and reestablish state for file handles held by various clients using the resume key filter.Type: ApplicationFiled: December 10, 2010Publication date: June 14, 2012Applicant: Microsoft CorporationInventors: Paul R. Swan, Mathew George, David M. Kruse, Roopesh C. Battepati, Michael C. Johnson
-
Patent number: 8180812Abstract: Aspects of the subject matter described herein relate to configuring file shares. In aspects, a template is created that includes policies to apply to one or more shares. The template may derive or otherwise obtain policies from other templates and may also refer to other templates. The template may include opaque data to pass to a subsystem that configures a share with a policy corresponding to the data. After the template is created, the template may then be applied to one or more shares to configure the shares according to policies included in the template. When the template or any template upon which the template depends or to which the template refers is changed, shares associated with the template may also be automatically changed as appropriate.Type: GrantFiled: May 8, 2009Date of Patent: May 15, 2012Assignee: Microsoft CorporationInventors: Roopesh C. Battepati, Michael C. Johnson
-
Publication number: 20100293197Abstract: Aspects of the subject matter described herein relate to directory oplocks. In aspects, a file system filter is inserted in a filter stack between requesters of directory oplocks and a file system that stores file system objects. The file system filter receives requests for directory oplocks and subsequently monitors for requests to access file system objects that are inconsistent with the directory oplocks. To provide directory oplock mechanisms, the file system filter may use alternate data streams if provided by the file system or may independently maintain information usable to maintain and release directory oplocks. A directory oplock may affect ancestors and descendants of the directory depending on constraints imposed by the oplock.Type: ApplicationFiled: May 14, 2009Publication date: November 18, 2010Applicant: Microsoft CorporationInventors: Roopesh C. Battepati, Michael C. Johnson, Jeffrey K. Biseda, James T. Pinkerton, David Matthew Kruse
-
Publication number: 20100287221Abstract: Aspects of the subject matter described herein relate to configuring file shares. In aspects, a template is created that includes policies to apply to one or more shares. The template may derive or otherwise obtain policies from other templates and may also refer to other templates. The template may include opaque data to pass to a subsystem that configures a share with a policy corresponding to the data. After the template is created, the template may then be applied to one or more shares to configure the shares according to policies included in the template. When the template or any template upon which the template depends or to which the template refers is changed, shares associated with the template may also be automatically changed as appropriate.Type: ApplicationFiled: May 8, 2009Publication date: November 11, 2010Applicant: Microsoft CorporationInventors: Roopesh C. Battepati, Michael C. Johnson
-
Publication number: 20090055921Abstract: Aspects of the subject matter described herein relate to providing file access in a multi-protocol environment. In aspects, a file server is operable to receive requests formatted according to two or more file access protocols. If a request is formatted according to a first file access protocol, the file server applies access rights associated with the file to an account associated with a requester to determine whether to grant access. If the request is formatted according to the second file access protocol, the file server may first attempt to find an account for the requester. If an account is not found, the file server may then grant access based on access rights associated with the file as applied to information in the request without consulting an account on the file server.Type: ApplicationFiled: August 23, 2007Publication date: February 26, 2009Applicant: MICROSOFT CORPORATIONInventors: Scott A. Field, Paul J. Leach, Roopesh C. Battepati, Michael C. Johnson