Abstract: Examples described herein are generally directed towards file share access, and more specifically towards a mechanism to connect file shares at the protocol level in a distributed file server environment. In operation, a first FSVM hosting a first file share may receive a request by a client to access a location in a name space. The first FSVM may determine the location is at a second file share linked to the first file share. The first FSVM may provide access to the second file share to the client. In some examples, the first file share and the second file share may be linked at the directory level.

Abstract: Examples described herein are generally directed towards file server access controls, and more specifically towards a mechanism to create consistent access control lists for local users across different file servers in a distributed file server environment. In operation, a local user system SID (e.g., external SID) may be generated for a first user of a first file server. A global ID based on attributes associated with the user of the first file server may also be generated. The global ID for the user may be stored in metadata associated with an access control list (ACL) for a file accessible through the first file server. Data, including the file may be migrated to a second file server. Based on receiving an access request at the second file server associated with the user based on the external ID, the external ID for the user may be translated into the global ID, and used to determine access to the file.

Abstract: A file server manager disclosed herein accesses information regarding a selected share of a source distributed file server for replication, where the selected share stores at least a portion of a namespace of storage items and is hosted by a first file server virtual machine of the source distributed file server. The file server manager accesses a mapping between virtual machines of the source distributed file server and virtual machines of the destination distributed file server and replicates the selected share to a second file server virtual machine of the destination distributed file server based on the mapping. The file server manager directs a request to read a first storage item to the destination distributed file server and directs a request to write to a second storage item to the source distributed file server while the destination distributed file server services the request to read the first storage item.

Abstract: An example file server manager disclosed herein receives a registration for a distributed file server, where the distributed file server is hosted in a virtualization environment and includes a cluster of file server virtual machines configured to provide access to a file system. The file server manager further synchronizes metadata with the distributed file server, the metadata including identification of each of the file server virtual machines of the cluster of file server virtual machines, the metadata including information regarding the file system and receiving a management request for the distributed file server. The file server manager further formats the management request for the virtualization environment based on the metadata and utilizing information from the registration to access the distributed file server with the formatted management request.

Abstract: An example file server manager updates a selected share of a destination distributed file server based on a snapshot of at least a portion of a selected share of a source distributed file server. The selected share of the destination distributed file server is updated while the source distributed file server serves client requests for storage items of the selected share of the source distributed file server. The file server manager receives a request to failover from the source distributed file server to the destination distributed file server and configures the destination distributed file server to service read and write requests for storage items of the selected share of the destination distributed file server. The file server manager further redirects client requests for storage items of the selected share of the source distributed file server to the destination distributed file server by updating active directory information.

Abstract: Examples of a virtualized file server that persistently stores file system event data records are described. The virtualized file server may include an audit framework with a connector publisher that is configured to publish the event data records and other information for consumption by other services using a message system. The event data records may include data related to various operations on the file system executed by the VFS. The VFS may persistently store event data records according to a data retention policy and/or until an event data record is consumed by one or more particular services.

Abstract: This disclosure relates to scope-based lock management for shared resources of a distributed computing system. A scope-based lock manager may grant a request for a lock of a shared resource of the distributed computing system, where the lock request includes a scope of the lock and a target having the scope. The target may define entities able to access the shared resource when locked. The scope and target of the lock are stored at a lock database including scopes and targets associated with additional locks of additional shared resources of the distributed computing system. The scope based lock manager may determine when a computing node of the distributed computing system has failed and remove the lock from the lock database responsive to a determination that the target of the lock is hosted on the computing node.

Abstract: Examples described herein include virtualized environments including a virtualized file server. Examples of file server virtual machine managers are described which may setup and/or configure file server virtual machines in accordance with a target number of connections and/or a target throughput for the virtualized file server. The virtualized file server may be scaled up, scaled down, scaled in, and/or scaled out.

Abstract: Examples of file analytics systems are described that may obtain metadata data and events data from a virtualized file server. The file analytics systems may detect one or more events from the events data matching a criteria indicating malicious activity. The file analytics systems may further identify one or more files of the virtualized file server affected by the detected malicious activity and recover a share of the distributed file server including the one or more affected files by replacing the one or more affected files with stored versions of the one or more affected files from a snapshot of the share taken prior to the detected malicious activity.

Abstract: Examples described herein include virtualized environments including a virtualized file server. Examples of file server virtual machine managers are described which may setup and/or configure file server virtual machines in accordance with a target number of connections and/or a target throughput for the virtualized file server. The virtualized file server may be scaled up, scaled down, scaled in, and/or scaled out.

Abstract: Examples of distributed database systems are described. Multiple computing nodes may be utilized to provide a distributed database system. Each of the multiple computing nodes may cache a portion of the distributed database. The cache may be utilized to service write requests. A computing node servicing a write request may provide a callback to other computing nodes hosting the distributed database. The local cache may be updated responsive to the write request and callbacks issued to the other computing nodes to allow for updates of other local caches. In this manner, a local cache may be updated prior to updating the distributed database as a whole in some examples. While callbacks may be used to update cached data on other nodes, the computing node servicing the write request may not need to receive a callback prior to updating the local cache.

Abstract: Examples described herein include virtualized environments including a virtualized file server. Examples of file server virtual machine managers are described which may setup and/or configure file server virtual machines in accordance with a target number of connections and/or a target throughput for the virtualized file server. The virtualized file server may be scaled up, scaled down, scaled in, and/or scaled out.

Abstract: A state management system preserves a state for a cluster of file servers in a cluster file system in the presence of load balancing, failover, and fail-back events. The system provides a file and record locking solution for a clustered network attached storage system running on top of a cluster file system. The system employs a lock ownership scheme in which ownership identifiers are guaranteed to be unique across clustered servers and across various protocols the clustered servers may be exporting. The system supports multi-protocol clustered NAS gateways, NAS gateway server failover and fail-back, and load-balancing architectures. The system further eliminates a need for a lock migration protocol, resulting in improved efficiency and simplicity.