Abstract: Efficient authentication in a file system with multiple security groups is disclosed. A file system (FS) executing on at least one processor device receives, from a first client application of a plurality of client applications, a request to access a first object, the request including a unique object ID that identifies the first object. The FS determines, based on a data structure maintained by the FS and inaccessible to the first client application, that the first client application is associated with a first security group of a plurality of different security groups. The FS determines, based on metadata of the first object, that the first object is associated with the first security group, and grants the first client application access to the first object.

Abstract: A caseless file lookup in a distributed file system is disclosed. A request to store a file in a volume may be received. In response to the request, the type of client system issuing the request may be identified. Based on the type of client system that has been identified, a first hash value or a second hash value may be calculated for the name of the file to generate and assign a hash value to the file. The file may be stored in a storage resource based on the first or second hash value that has been generated for the file.

Abstract: A method and system for storing an object in a distributed storage system are provided. An example system includes an object name identifier that receives a request to save an object having an initial object name within a file system space and determines, based on a set of regular expressions, whether the initial object name is a temporary object name. The example system also includes a converter that, when the initial object name is determined to be a temporary object name, transforms, based on the set of regular expressions, the initial object name into a permanent object name. The example system further includes a selector that applies a function to the permanent object name and selects, based on a result of the function applied to the permanent object name, a server of a plurality of servers. The object is sent to the selected server for storage.

Abstract: A caseless file lookup in a distributed file system is disclosed. A request to store a file in a volume may be received. In response to the request, the type of client system issuing the request may be identified. Based on the type of client system that has been identified, a first hash value or a second hash value may be calculated for the name of the file to generate and assign a hash value to the file. The file may be stored in a storage resource based on the first or second hash value that has been generated for the file.

Abstract: A caseless file lookup in a distributed file system is disclosed. A request to store a file in a volume may be received. In response to the request, the type of client system issuing the request may be identified. Based on the type of client system that has been identified, a first hash value or a second hash value may be calculated for the name of the file to generate and assign a hash value to the file. The file may be stored in a storage resource based on the first or second hash value that has been generated for the file.

Abstract: Efficient authentication in a file system with multiple security groups is disclosed. A file system (FS) executing on at least one processor device receives, from a first client application of a plurality of client applications, a request to access a first object, the request including a unique object ID that identifies the first object. The FS determines, based on a data structure maintained by the FS and inaccessible to the first client application, that the first client application is associated with a first security group of a plurality of different security groups. The FS determines, based on metadata of the first object, that the first object is associated with the first security group, and grants the first client application access to the first object.

Abstract: Embodiments relate to systems and methods for replicating a group of data objects within a storage network. In particular, a module can designate an object in the storage network as an anchor object. The module can further evaluate a replication policy of the anchor object to determine a destination resource on which to replicate a related group of data objects. Further, the module can located the related group of data objects, and define a replication policy on each of the data objects that specifies that each of the data objects follow the anchor object. The module can replicate each of the data objects as well as the anchor object on the destination resource.

Abstract: A processing device identifies a file (or data block) and selects a storage location for the file based on a plurality of data distribution policies. To select the storage location, the processing device applies, at a top distribution layer, a first data distribution policy to select a first storage pool from a plurality of storage pools based on a first storage criterion. The processing device then applies, at a bottom distribution layer, a second data distribution policy associated with the first storage pool to select a first storage node from a plurality of storage nodes in the first storage pool based on a second storage criterion. The processing device stores at least a portion of the file in the first storage node of the first storage pool.

Abstract: Data connections from a remote login session are identified and an identification query may be transmitted by the remote login session to endpoints (e.g., servers) of the data connections. In response to the identification query, identification information may be received from the endpoints. Furthermore, the identification information may be compared with a local identification of a local server that hosts the remote login session. A file created by the remote login session may be stored at an endpoint over a data connection where the local identification matches a portion or all of the identification information of the endpoint of the data connection.

Abstract: Embodiments relate to systems and methods for replicating data from a primary resource to a secondary resource within a storage network based on resource attributes. In particular, a user can specify a policy framework comprising one or more count selections and one or more attributes. A policy generation module can determine candidate resources that match the policy framework, and order the candidate resources based on one or more factors. The policy generation module can generate a replication policy based on the ordered resources and replicate the data according to the replication policy.

Abstract: Embodiments relate to searching a cloud-based file storage system using a set of expandable probes. Platforms and techniques are provided to search for a file whose location in cloud storage resources is recorded in a consistent hash ring structure. In a hash ring, a file name can generate a hash output corresponding to a position around a circle. The closest clockwise node to that location can contain the file itself, or a link to another location containing or leading to the file. When a link has become obsolete and no longer points to the file, it may be necessary to search for that file. Embodiments perform a graduated search for the missing file, starting one node from the original node, then trying two adjacent nodes, then four adjacent nodes and so forth in expanding fashion, until the file is found or the hash structure is exhausted.

Abstract: Data connections from a remote login session are identified and an identification query may be transmitted by the remote login session to endpoints (e.g., servers) of the data connections. In response to the identification query, identification information may be received from the endpoints. Furthermore, the identification information may be compared with a local identification of a local server that hosts the remote login session. A file created by the remote login session may be stored at an endpoint over a data connection where the local identification matches a portion or all of the identification information of the endpoint of the data connection.

Abstract: A caseless file lookup in a distributed file system is disclosed. A request to store a file in a volume may be received. In response to the request, the type of client system issuing the request may be identified. Based on the type of client system that has been identified, a first hash value or a second hash value may be calculated for the name of the file to generate and assign a hash value to the file. The file may be stored in a storage resource based on the first or second hash value that has been generated for the file.

Abstract: A processing device identifies a file (or data block) and selects a storage location for the file based on a plurality of data distribution policies. To select the storage location, the processing device applies, at a top distribution layer, a first data distribution policy to select a first storage pool from a plurality of storage pools based on a first storage criterion. The processing device then applies, at a bottom distribution layer, a second data distribution policy associated with the first storage pool to select a first storage node from a plurality of storage nodes in the first storage pool based on a second storage criterion. The processing device stores at least a portion of the file in the first storage node of the first storage pool.

Abstract: Embodiments relate to systems and methods for a cloud-based directory system based on hashed values of parent and child storage locations. Platforms and techniques are provided to store a data object to cloud storage resources in two or more locations recorded in a consistent hash structure. A file management tool can store one copy of the data object to a location corresponding to the hashed value of the file path or name, and a second copy to a location corresponding to the hashed value of the parent directory of the data object. All files sharing a common parent directory or other location therefore have at least one copy stored to the same location, in common with the parent. Directory-wide read, write, and/or search operations can therefore be performed more efficiently, since the constituent files of a directory or other location can be accessed from one location rather than distributed locations.

Abstract: A method and system for storing an object in a distributed storage system are provided. An example system includes an object name identifier that receives a request to save an object having an initial object name within a file system space and determines, based on a set of regular expressions, whether the initial object name is a temporary object name. The example system also includes a converter that, when the initial object name is determined to be a temporary object name, transforms, based on the set of regular expressions, the initial object name into a permanent object name. The example system further includes a selector that applies a function to the permanent object name and selects, based on a result of the function applied to the permanent object name, a server of a plurality of servers. The object is sent to the selected server for storage.

Abstract: Embodiments relate to systems and methods for dynamically replicating data from a primary resource to a secondary resource within a storage network. In particular, a user can select parameters that specify a policy framework. A policy management module can determine one or more attributes associated with resources of the storage network, and enter the one or more attributes into the policy framework to determine a replication policy. The one or more attributes can be determined at any point before or during a replication. The policy management module can then replicate the data according to the replication policy.

Abstract: Embodiments relate to systems and methods for monitoring files in cloud-based networks. In particular, a file managing module can manage the access and retrieval of files stored in cloud-based networks on a distributed basis. In embodiments, the file managing module can receive a file access request from a requesting entity. The file managing module can use the file access request to determine a storage location mapped to a hash structure. Generation numbers associated with the both the storage location and the actual file at the storage location can be compared to determine whether the file has been unexpectedly modified or relocated. The file managing module can sync any discrepancy between the generation numbers and retrieve the file for the requesting entity.

Abstract: Embodiments relate to systems and methods for replicating data from a primary resource to a secondary resource within a storage network based on resource attributes. In particular, a user can specify a policy framework comprising one or more count selections and one or more attributes. A policy generation module can determine candidate resources that match the policy framework, and order the candidate resources based on one or more factors. The policy generation module can generate a replication policy based on the ordered resources and replicate the data according to the replication policy.

Abstract: Embodiments relate to systems and methods for replicating a group of data objects within a storage network. In particular, a module can designate an object in the storage network as an anchor object. The module can further evaluate a replication policy of the anchor object to determine a destination resource on which to replicate a related group of data objects. Further, the module can located the related group of data objects, and define a replication policy on each of the data objects that specifies that each of the data objects follow the anchor object. The module can replicate each of the data objects as well as the anchor object on the destination resource.