Abstract: A system can receive a request to access a file, and determine that a time when the file was most recently modified is more recent than when the file was most recently scanned for viruses with a latest virus definition. The system can determine that a first data store comprises a first indication that indicates that the file has been respectively modified by respective user input received via respective user accounts of at least one user account since the second time at which the file was most recently scanned. The system can determine that a second data store comprises a second indication that indicates that at least one of the at least one user account is classified as a threat user in accordance with a threat criterion. The system can perform an antivirus scan on the file and permit the access to the file where the scan is clear.

Abstract: A system can mark a file in a computer file storage system as a sensitive file, and determine that an attempt to access the file has been made via a first user account. The system can, based on the attempt to access the file, and on determining that the file is the sensitive file, notify at least one device, associated with a security group, of the attempt to access, wherein the security group comprises at least one user account other than the first user account. The system can, after the notifying, receive access approval data that is associated with at least one of the at least one user account of the security group, wherein the access approval data is indicative of granting the first user account access to the file. The system can, based on receiving the access approval data, enable access to the file via the first user account.

Abstract: A system can maintain a mapping between respective data chunks of a group of data chunks and at least one respective storage drive of a group of storage drives that store the respective data chunks. The system can determine respective input/output performance characteristics of the different input/output performance characteristics based on monitoring respective input/output operations of the at least one respective storage drive. The system can, based on receiving a request to perform an input/output operation on a data chunk of the group of data chunks, select a storage drive of the group of storage drives based on the mapping and based on the respective input/output performance characteristics, to produce a selected storage drive. The system can perform the input/output operation on the data chunk using the selected storage drive.

Abstract: A system can maintain respective numbers of changed bytes for respective backup paths of a file system, which indicate how many bytes have changed since respective most-recent backups of the respective backup paths. The system can, while performing a backup of a backup path of the respective backup paths, for respective tasks of the backup, determine respective amounts of time spent backing up respective files associated with the respective tasks, and respective file sizes of the respective files, determine a mean time to transfer a byte based on the respective amounts of time spent backing up the respective files, and the respective file sizes, determine an estimated time of completing the backup based on the mean time to transfer a byte and the number of changed bytes for the backup path, and store an indication of the estimated time of completing the backup.

Abstract: A system can determine to perform deduplication on a group of directories in a file system. The system can determine respective deduplication ratios of respective directories of the group of directories, wherein the respective deduplication ratios comprise respective ratios of respective logical sizes of the respective directories to respective physical sizes of the respective directories. The system can perform the deduplication on a first subgroup of the group of directories that have respective deduplication ratios that satisfy a deduplication ratio criterion before performing deduplication on a second subgroup of the group of directories that have respective deduplication ratios that do not satisfy the deduplication ratio criterion.

Abstract: A system can maintain respective numbers of changed bytes for respective backup paths of a file system, which indicate how many bytes have changed since respective most-recent backups of the respective backup paths. The system can, while performing a backup of a backup path of the respective backup paths, for respective tasks of the backup, determine respective amounts of time spent backing up respective files associated with the respective tasks, and respective file sizes of the respective files, determine a mean time to transfer a byte based on the respective amounts of time spent backing up the respective files, and the respective file sizes, determine an estimated time of completing the backup based on the mean time to transfer a byte and the number of changed bytes for the backup path, and store an indication of the estimated time of completing the backup.

Abstract: A system can determine to perform deduplication on a group of directories in a file system. The system can determine respective deduplication ratios of respective directories of the group of directories, wherein the respective deduplication ratios comprise respective ratios of respective logical sizes of the respective directories to respective physical sizes of the respective directories. The system can perform the deduplication on a first subgroup of the group of directories that have respective deduplication ratios that satisfy a deduplication ratio criterion before performing deduplication on a second subgroup of the group of directories that have respective deduplication ratios that do not satisfy the deduplication ratio criterion.

Abstract: A system can maintain, in a directory, respective first softlinks of respective first files that have a size within a specified range, and that have been modified subsequent to a respective most-recent virus scan. The system can, in response to determining to perform an antivirus scan on a group of files that comprises the first files, perform a first antivirus scan on the first files based on identifying the first softlinks in the directory, and, after performing the first antivirus scan on the first files, perform a second antivirus scan on second files of the group of files that are not identified with respective second softlinks in the directory.

Abstract: A system can identify a first group of files that are scheduled to be modified by another operation within a next defined amount of time. The system can remove the first group of files from the files of the file system with respect to a deduplication operation to produce a second group of files. The system can perform a sampling phase on the second group of files, wherein the sampling phase identifies a first group of blocks, and wherein the first group of blocks corresponds to duplicate file system blocks. The system can identify a second group of blocks that correspond to the first group of files. The system can remove any blocks from the first group of blocks that have a respective duplicate in the second group of blocks to produce a third group of blocks. The system can perform the deduplication operation on the third group of blocks.

Abstract: A system can create a group of at least one file on a source computer. The system can perform iterations of backing up the group of at least one file to a destination computer. The system can store respective job status indications of respective iterations of the iterations of backing up the group of at least one file. The system can, in response to determining to back up the data, and in response to determining that the job status indications indicate that at least one iteration of the iterations of backing up the group of at least one file was successful, back up the data to the destination computer, or, in response to determining that the job status indications indicate that the at least one iteration of the iterations of backing up the group of at least one file was unsuccessful, refrain from backing up the data.

Abstract: A system can maintain a record of first files that have been accessed via at least one of a group of priority user accounts, wherein the record is maintained as a least recently used structure, and wherein the first files belong to a group of files. The system can, in response to determining that the group of files is to be backed up, traverse the record of files from a head of the least recently used structure, and, for respective first files of the record of first files, create respective backup tasks for the respective first files. The system can, after backing up the respective first files, perform a backup of second files of the group of files that are omitted from the record of first files.

Abstract: A system can maintain, in a directory, respective first softlinks of respective first files that have a size within a specified range, and that have been modified subsequent to a respective most-recent virus scan. The system can, in response to determining to perform an antivirus scan on a group of files that comprises the first files, perform a first antivirus scan on the first files based on identifying the first softlinks in the directory, and, after performing the first antivirus scan on the first files, perform a second antivirus scan on second files of the group of files that are not identified with respective second softlinks in the directory.

Abstract: A system can maintain a record of first files that have been accessed via at least one of a group of priority user accounts, wherein the record is maintained as a least recently used structure, and wherein the first files belong to a group of files. The system can, in response to determining that the group of files is to be backed up, traverse the record of files from a head of the least recently used structure, and, for respective first files of the record of first files, create respective backup tasks for the respective first files. The system can, after backing up the respective first files, perform a backup of second files of the group of files that are omitted from the record of first files.

Abstract: A system can determine that a node a storage cluster has failed, wherein respective data protection levels are maintained for respective files. The system can traverse the respective files, comprising, in response to determining that a data protection level for a file is degraded and that the file is a priority file, adding an identifier of the file to a priority table for restoration of data protection, or, in response to determining that the data protection level for the file of the respective files is degraded and that the file is not the priority file, adding the identifier of the file to a non-priority table for the restoration of data protection. The system can, after traversing the files, restore respective first data protection levels of respective first files represented by the priority table, and then restore respective second data protection levels of respective second files represented by the non-priority table.

Abstract: A system can maintain respective extended attributes for respective files in a file system, wherein the respective extended attributes comprise respective first-in-first-out (FIFO) queues of user identities that have been determined to have modified the respective files. The system can receive an indication to perform a delete operation on a first portion of the file system, wherein the indication is indicative of a first user identity for which files are to be preserved. The system can, in response to receiving the indication, evaluate the respective files, comprising in response to determining that the first user identity is omitted from a FIFO queue of the respective FIFO queues, delete a file of the respective files that corresponds to the FIFO queue; and in response to determining that the first user identity is identified in the FIFO queue, refrain from deleting the file.

Abstract: A system can create a group of at least one file on a source computer. The system can perform iterations of backing up the group of at least one file to a destination computer. The system can store respective job status indications of respective iterations of the iterations of backing up the group of at least one file. The system can, in response to determining to back up the data, and in response to determining that the job status indications indicate that at least one iteration of the iterations of backing up the group of at least one file was successful, back up the data to the destination computer, or, in response to determining that the job status indications indicate that the at least one iteration of the iterations of backing up the group of at least one file was unsuccessful, refrain from backing up the data.

Abstract: A system can maintain respective extended attributes for respective files in a file system, wherein the respective extended attributes comprise respective first-in-first-out (FIFO) queues of user identities that have been determined to have modified the respective files. The system can receive an indication to perform a delete operation on a first portion of the file system, wherein the indication is indicative of a first user identity for which files are to be preserved. The system can, in response to receiving the indication, evaluate the respective files, comprising in response to determining that the first user identity is omitted from a FIFO queue of the respective FIFO queues, delete a file of the respective files that corresponds to the FIFO queue; and in response to determining that the first user identity is identified in the FIFO queue, refrain from deleting the file.

Abstract: A system can determine that an integrity of a data backup is to undergo a validation process, wherein the data backup is located at a target location, and wherein the data backup comprises a backup of source data at a source location. The system can identify a subset of files of the source data to validate in the data backup, wherein the subset of files is determined prior to performing the determining that the integrity of the data backup is to undergo the validation process. The system can, as part of validation of the subset of files according to the validation process, validate respective first hashes of respective files of the subset of files relative to respective second hashes of respective corresponding second files of the data backup, to produce a validation result. The system can store the validation result.

Abstract: A system can to perform a replication of data from first computing equipment to second computing equipment, the data being stored as part of a path in a file system. The system can, from a replication policy for the replication, a priority sub-path of the path. The system can add a first set of files to a transfer queue comprising tree-walking the priority sub-path. The system can, after adding the first set of files, adding a second set of files to the transfer queue comprising tree-walking a portion of the path that is different from the priority sub-path. The system can replicate files in the transfer queue from the first computing equipment to the second computing equipment.

Abstract: A system can determine to perform a replication of data from first computing equipment to second computing equipment, the data being stored as part of a path in a file system. The system can determine that a change log of file operations on files in the path identifies a file operation on a file that is made by a user account that has priority for replications. The system can replicate the file. The system can, after processing the change log for file operations made by first user accounts that have priority for replications, replicating other files in the path associated with second user accounts that do not have priority for replications.