Abstract: An archival job is assessed to calculate loss of data reduction efficiency due to block-level data deduplication. Archivable data, or individual storage objects or data structures therein, are moved to archival storage contingent upon satisfaction of a predetermined condition related to data reduction efficiency. Archivable data, or individual storage objects or data structures therein, that fail to satisfy the predetermined condition are maintained in primary storage. The loss of data reduction efficiency and the predetermined condition may be expressed as a percentage of maximum possible data reduction that would result in the absence of data deduplication.

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 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 a backup of data stored on a source computer, wherein the backup is stored on a remote computer. The system can maintain, on the source computer, a file catalog, wherein the file catalog comprises a local path for a first file on the source computer, a remote backup location for the first file on the remote computer, and a first hash of the first file. The system can determine that a copy of the first file at the local path on the source computer is corrupted. The system can identify whether a second hash of a second file on the source computer matches the first hash of the first file. The system can, in response to determining that the second hash matches the first hash, repair first data of the first file with second data of the second file, and repair first metadata of the first file with second metadata from the remote backup location for the first file on the remote computer.

Abstract: A system can receive a request that is associated with a user account to perform an operation on the system. The system can evaluate the request based on a security breach policy to produce a security result. The system can, in response to determining that the security result indicates that there is a possible security breach, determine not to perform the operation, and perform a mitigating action regarding the possible security breach. The system can, in response to the security result indicating that the possible security breach does not exist, perform the operation.

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.

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 maintain information indicative of prohibited computer operations, wherein the information is accessible to respective computing clusters of a group of computing clusters, and wherein the information is stored separately from the group of computing clusters. The system can obtain, by a service of a first computing cluster of the group of computing clusters, the information. The system can, in response to receiving, at the first computing cluster, a request to perform an operation on a first computer of the first computing cluster, in response to determining, based on the information, that the operation is prohibited, prevent the operation from occurring; and, in response to determining, based on the information, that the operation is not prohibited, permit the operation to occur.

Abstract: An archival job is assessed to calculate loss of data reduction efficiency due to block-level data deduplication. Archivable data, or individual storage objects or data structures therein, are moved to archival storage contingent upon satisfaction of a predetermined condition related to data reduction efficiency. Archivable data, or individual storage objects or data structures therein, that fail to satisfy the predetermined condition are maintained in primary storage. The loss of data reduction efficiency and the predetermined condition may be expressed as a percentage of maximum possible data reduction that would result in the absence of data deduplication.

Abstract: A system can maintain information indicative of prohibited computer operations, wherein the information is accessible to respective computing clusters of a group of computing clusters, and wherein the information is stored separately from the group of computing clusters. The system can obtain, by a service of a first computing cluster of the group of computing clusters, the information. The system can, in response to receiving, at the first computing cluster, a request to perform an operation on a first computer of the first computing cluster, in response to determining, based on the information, that the operation is prohibited, prevent the operation from occurring; and, in response to determining, based on the information, that the operation is not prohibited, permit the operation to occur.

Abstract: A system can determine to perform a replication of data from first computing equipment to second computing equipment, wherein the data is stored within a path in a file system of the first computing equipment. The system can determine the path from a replication policy for the replication. The system can, while tree-walking the path, in response to determining that a first file is marked for priority replication, adding the first file to a priority queue, and in response to determining that a second file lacks a marking for priority replication, adding the second file to a normal queue. The system can, in response to determine that the priority queue contains files, replicating the files from the priority queue instead of replicating other files from the normal queue.

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.

Abstract: A system can determine to perform a replication of data from first computing equipment to second computing equipment, wherein the data is stored within a path in a file system of the first computing equipment. The system can determine the path from a replication policy for the replication. The system can, while tree-walking the path, in response to determining that a first file is marked for priority replication, adding the first file to a priority queue, and in response to determining that a second file lacks a marking for priority replication, adding the second file to a normal queue. The system can, in response to determine that the priority queue contains files, replicating the files from the priority queue instead of replicating other files from the normal queue.

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: Techniques are provided for identifying and deleting idle remote sessions in a distributed file system. In an example, a server that serves a plurality of server message block (SMB) sessions analyzes those sessions to determine which sessions are idle. Of the idle sessions, the server can determine which possess a lock on a computer file. Where another, active session is waiting for that resource, the server can terminate the idle session and release the lock so that the active session acquires access to the requested computer file.

Abstract: Techniques are provided for predicting and deleting idle remote sessions in a distributed file system. In an example, a server that serves a plurality of server message block (SMB) sessions analyzes with linear regression techniques those sessions to determine which sessions will become idle. In some examples, the server can then proactively close a SMB session that it predicts that an administrator would choose to close after a given idle period of time, or recommend to an administrator that the SMB session can be closed.