Abstract: A facility for managing filesystem object storage quotas (i.e., size limits) in a storage environment is disclosed. The facility enables users to establish, modify, and remove quotas on directories and files within a filesystem. Each quota acts as a soft limit on the size of the associated filesystem object, including any child objects of the filesystem object. The facility improves the speed at which the system can test for and identify violations of quotas established for individual filesystem objects by using aggregation and reconciliation techniques rather than constantly traversing a filesystem in its entirety to test for violations of quotas.

Abstract: Embodiments are directed to traversing a file system to determine file system objects to copy to an object store. In response to visiting a document object in the file system, performing further actions, including: determining a hierarchical file path of the document object that corresponds to a location in the file system based on the file system objects that are ancestor file system objects of the document object; generating an object key for the document object that encodes the hierarchical file path such that each portion of the object key corresponds to an ancestor file system object; copying the document object and the object key to the object store such that the document object may be stored in the object store as an object store object and such that the object store object may be indexed using an unordered index based on the object key; or the like.

Abstract: Embodiments are directed to managing data in a file system over a network. A source file system that includes a plurality of objects may be provided. A replication job that copies each object associated with a source replication snapshot to a target file system may be executed. The replication job may be associated with a job identifier. Recovery point information that includes the job identifier, a source snapshot number that corresponds to the source replication snapshot, a target snapshot number that corresponds to a target replication snapshot may be generated. The recovery point information may be stored on the source file system and a copy of the recovery point information may be stored on the target file system. The recovery point information or the copy of the recovery point information may be employed to recover from errors detected during execution of a next replication job.

Abstract: Embodiments are directed to a replication engine that provides a root node for a file that may be associated with a replication snapshot where the file is comprised of the root node, internal nodes, and data nodes. The replication engine may start at the root node and traverse the file system. If a visited internal node has an epoch value that matches the epoch, the replication engine may continue the traversal by visiting a next unvisited adjacent internal node. If the visited internal node has an epoch value that mismatches the epoch, the replication engine may backtrack to a nearest adjacent internal node that matches the epoch. And, in response to visiting a data node the replication engine may be arranged to determine blocks that are associated with the data node and communicate a copy of the blocks to a target file system.

Abstract: A software and hardware facility persistently maintains metrics on directories at different levels within a tree of a filesystem. The facility hierarchically aggregates attributes of files contained by directories and stores them as metric values in each directory within a tree. The stored values represent summed or otherwise aggregated data from the descendant directories and files. The metric values represent aggregated attributes such as checksums, MIN and/or MAX aggregates, sameness bits, bloom filter aggregates, queryable user tags, moving average aggregates, b-tree aggregates, etc.

Abstract: Embodiments are directed to managing data in a file system that includes storage nodes and storage volumes in a cloud computing environment (CCE). A backup job may be executed to perform further actions, including: providing a backup identifier that is associated with the backup job; determining the storage nodes based on the file system and the CCE; disabling the file system by disabling the storage nodes, wherein each disabled storage node is associated with a shutdown timestamp; determining storage volumes associated with each disabled storage node; and generating storage images that archive a copy of information from the storage volumes; associating the storage images with the backup identifier; confirming that the file system is consistent based on an absence of file system activity occurring subsequent to each shutdown timestamp; and enabling the file system by enabling the storage nodes.

Abstract: Embodiments are direct to managing file systems. Alternate data streams (ADSs) of an object in a file system may be modified based on a request from a client and metrics associated with the ADSs may be modified. Values for reconcile fields associated with the object may be set based on the modified metrics such that the object with the modified ADSs may be included in a reconcile list. And, such that an acknowledgment of the request may be provided to the client. A reconcile engine may determine a parent object of the object. The object may be reconciled and the parent object may be placed on the reconcile list for reconciling in turn.

Abstract: Embodiments are directed to managing data in a file system. A query may be provided to determine characteristics associated with a file system and a sampling model. The sampling model may be employed to determine objects in the file system based on a traversal of the file system. The sampling model may be employed to determine metrics associated with the alternate data streams (ADSs) included in the objects such that each of the objects that includes a separate main data stream and the ADSs may be associated with data blocks and the ADSs may each be associated with other data blocks. The sampling model and the query may be employed to sample the objects to provide partial results such that the sampling may be distributed between the objects based on the sampling model and the metrics. A result to the query may be provided based on the partial results.

Abstract: A software and hardware facility persistently maintains metrics on directories at different levels within a tree of a filesystem. The facility hierarchically aggregates attributes of files contained by directories and stores them as metric values in each directory within a tree. The stored values represent summed or otherwise aggregated data from the descendant directories and files. The metric values represent aggregated attributes such as checksums, MIN and/or MAX aggregates, sameness bits, bloom filter aggregates, queryable user tags, moving average aggregates, b-tree aggregates, etc. The facility provides mechanisms for efficiently sampling activities performed by the filesystem and visually representing these activities.

Abstract: Embodiments are directed to managing file systems over a network. Jobs may be provided to a storage computer in a file system. Control models may be associated with the jobs. Scores may be generated based on the control models. Each job may be associated with a score provided by its associated control model. And, each job that may be behind its corresponding schedule may be associated with a higher score value than each other job that may be either on its corresponding other schedule or ahead of its corresponding other schedule. Commands may be selected for execution based on the commands being associated with a job that may be associated with the higher score value that may be greater than score values associated with other jobs. The jobs may be ranked based on the updated scores. Subsequent commands may be selected and executed based on the ranking of the jobs.

Abstract: A transactional block storage system is provided which is capable of supporting a single-phase commit for data writes specifying a protected storage unit. The storage system includes a data storage map that logically links the protected data storage unit to two or more block storage units associated with a layer of the protected data storage unit. The storage system also includes an address abstraction layer which translates write requests to the block storage units and resolves whether those write requests are atomically committed to the storage system in a single phase transaction. The address abstraction layer is further configured to detected when a block storage unit becomes unavailable during a transaction and create a cleaning kit for that block in order to prevent data loss. Additionally, the address abstraction layer facilitates moving, copying, and merging of block storage units without global locking in the storage system.

Abstract: Embodiments are directed to managing data in a file system over a network. A file system that includes a master node and client nodes may be provided. A master quorum value and a client quorum value having the same value may be provided. A profile catalog associated with the master node that includes parameters may be provided. Profile registers associated with the client nodes may be provided. Change actions may be executed on each client node based on change information provided by the master node. In response to errors, access to the file system may be suspended; the master quorum value may be modified to indicate that the file system is out of quorum; recovery actions may be executed; the client quorum value at each client node may be modified to correspond with the master quorum value; and access to the file system may be restored.

Abstract: Embodiments are directed to managing file systems over a network. A core specification that defines characteristics of a portion of a file system and parameters may be provided. The characteristics may include one or more storage device characteristics. And, the parameters may include one or more of a cluster size, or a protection level. File system models may be generated based on the core specification and the parameters. Each file system model may correspond to a file system that conforms to a core specification and specific values for the parameters. A simulation engine may be employed to provide simulation results based on the file system models. Deployment models may be generated based on the simulation results. The deployment models may be employed to provision file systems that conform to the file system performance characteristics associated with its corresponding deployment model.

Abstract: Embodiments are directed to managing data in a file system. A source file system may be mirrored on a target file system by executing one or more replication jobs. A root object of the source file system may be associated with a current read-only identifier corresponds to a current update epoch of the source file system. A replication job that copies objects from the source file system to the target file system may be executed. A write request directed to the source file system may be received. Write objects associated with the write request may be determined The source file system may be traversed upwards from the write objects. A read-only identifier associated with each visited object may be determined based on the read-only identifier matching the current read-only identifier. The write request may be enabled based on the mismatch of the read-only identifier and current read-only identifier.

Abstract: A facility comprising systems and method for automatically triggering the collection of comprehensive monitoring information in a distributed processing system. The facility compares the overall performance of distributed processing system to one or more performance metrics and, in response to determining that one or more performance metrics is not satisfied, triggers one or more of the nodes within the distributed processing system to increase one or more of its monitoring rate or its distribution rate. The facility collects and analyzes the collected information to provide resources that can be used to assess and diagnose failures within the distributed processing system. In this manner, the facility reacts to performance anomalies by triggering nodes within in the system to provide comprehensive performance information over a trigger period for diagnostic purposes.

Abstract: Embodiments are directed to a file system engine that provides a file system with parent objects associated with child objects. The file system engine provides a replication snapshot associated with an epoch of the file system such that each child object modified during the epoch and each associated parent object is associated with the replication snapshot. A root object of a portion of the file system included in the replication snapshot may be provided. A replication engine may traverse the portion of file system starting from the root object such that the parent objects that are not associated with the replication snapshot are omitted from the traversal. The replication engine may determine replication objects based on the traversal such that each replication object was modified during the epoch. Then the replication engine may execute a replication job that copies replication objects to a target file system.

Abstract: Embodiments are directed to managing data in a file system. A pre-fetch engine may receive requests from a client the file system that includes a pre-fetch storage tier and a file storage tier of storage devices. The pre-fetch engine determines a pre-fetch policy based on the requests such that the pre-fetch policy determines which blocks to copy to the pre-fetch storage tier. And, the pre-fetch policy may be associated with a score model that includes score rules where one of the rules may be associated with a client score. The pre-fetch engine may obtain scores associated with the score rules such that the scores are based on previous requests made by the client. In response to scores exceeding a threshold value, the pre-fetch engine may copy the blocks to the pre-fetch storage tier. The pre-fetch engine may update the scores based on the performance of the pre-fetch policy.

Abstract: Managing data in a file system with a verification engine that may obtain a user identifier associated with a user, an object identifier, and a target object. The verification engine may determine target identities associated with two or more file system protocols based on the user identifier. The verification engine may determine permission entries associated with the two or more file system protocols associated and the target object. The verification engine may employ the target identities and the permission entries to directly verify access rights to the target object for the user. Accordingly, the verification engine may provide a report that includes the target identities, the permission entries, or the access rights.

Abstract: Embodiments are directed to file systems. A replication engine may establish a secure communication channel between a source file system and a target file system. The replication engine may: instantiate a replication job associated with rules; determine changes in the source file system; determine characteristics of the replication job that may be based on the changes; compare the to the characteristics and a black-out schedule; execute the replication job to communicate the changes in the source file system to the target file system based on a result of the comparison. Upon completion of the replication job, the replication engine may automatically instantiating a next replication job to copy subsequent changes in the source file system to the target file system.

Abstract: A facility for snapshot space accounting for a storage system, such as a filesystem is disclosed. The facility enables users to quickly and easily determine the amount of storage space that would be released or recovered if a snapshot were to be purged. The facility may work in conjunction with, or as part of, a snapshot service. The facility maintains an expiration data structure and a count data structure and uses these data structures in implementing the disclosed snapshot space accounting techniques. The expiration data structure represents the life cycle of each snapshot element maintained by the facility while the count data structure represents, for pairs of snapshots, the size of the information stored in the snapshot data that expired and that spans the corresponding pair of snapshots.