Abstract: Described is a system for leveraging incremental backup metadata of a deduplication storage system to perform an efficient data restore. The system may reference metadata stored as part of incremental backup infrastructure to determine only the changes to the data that occurred subsequent to the restore point. As a result, the system may reduce data read processing by retrieving only the changed data from the deduplication storage system. Moreover, the system may reduce the required bandwidth for the restore by providing only the changed data to a target device of the restore. Data retained by the client system such as the current version of the data may then be overwritten with the reduced set of data to complete the restore. As a result, the system may perform an efficient restore by reducing read accesses and bandwidth requirements, and thus, improve overall restore performance.

Abstract: Corruption detection in backups is disclosed. Backups that are received into a backup environment are stored in corresponding lineages. A detection engine is configured to perform corruption detection operations on the most recent backups in each of the lineages based on a sample frequency. Corruption detection operations may also be performed randomly and based on unexpected or unusual changes in backup metadata.

Abstract: Embodiments for providing file immutability for cloud storage data in a deduplicating filesystem and using a new filesystem that is spawned to receive redirected live data, after which the old filesystem is expired. Data objects are stored in the cloud by defining a protection duration from a first date to a fixed future date, and applying a retention lock to one or more data objects stored in cloud storage during the protection duration, the retention lock preventing unauthorized deletion, modification or movement of the data. A renew threshold date is defined within the protection duration, and a new filesystem is spawned on this date. All new data is redirected to the new filesystem and locked for the protection duration, and the first file system is destroyed.

Abstract: Embodiments for providing file immutability for cloud storage data in a deduplicating filesystem and using a new filesystem that is spawned to receive redirected live data, after which the old filesystem is expired. Data objects are stored in the cloud by defining a protection duration from a first date to a fixed future date and a selection period to select a subset of data objects to be protected during the protection period. A retention lock is applied to the subset of data objects stored in cloud storage during the protection duration, the retention lock preventing unauthorized deletion, modification or movement of the data. A cloud bucket is created for storing the subset of data objects and a new filesystem is spawned for attachment to the cloud bucket. Upon expiration of the selection period, the retention locks are expired and the new filesystem is destroyed.

Abstract: Embodiments for providing file immutability for cloud storage data in a deduplicating filesystem and using a new filesystem that is spawned to receive redirected live data, after which the old filesystem is expired. Data objects are stored in the cloud by defining a protection duration from a first date to a fixed future date and a selection period to select a subset of data objects to be protected during the protection period. A retention lock is applied to files that meet a set selection criteria, as determined by a matching or filter process. The selection criteria can include one or more of time-based selection, filetype selection, or tag-based selection.

Abstract: A method for providing data immutability using a deduplication filesystem for data objects stored in the cloud by defining a protection duration from a first date to a fixed future date, and applying a retention lock to one or more data objects stored in cloud storage during the protection duration, the retention lock preventing deletion, modification or movement of the data objects by an unauthorized entity. The method defines a renew threshold date within the protection duration, and performs a garbage collection (GC) operation at the renew threshold date to permanently delete dead data objects and carry forward live data objects, and extends the retention lock on remaining live data objects and subsequently written data objects upon completion of the GC operation.

Abstract: Embodiments for processing fastcopy overwrite backup workloads (FCOW) as virtual synthetic backups, by detecting whether or not a backup workload comprises an FCOW workload in which a base file is fastcopied to a target file, wherein portions of the base file are overwritten through overwrites by new data in the target file by a deduplication backup process.

Abstract: A self-healing method of recovering files using a cyber recovery vault for deduplication filesystems. Data to be backed up from a production system to a backup system in a datacenter is also copied to a cyber security vault coupled to the data center through an air gapped connection. A copy process makes a point-in-time (PIT) copy of the portion of data to a namespace in the vault, and retention locks the copied portion in the vault. An automated process detects a missing segment error, such as due to a bad index lookup in the data to be backed up. The self-healing process provides the missing segment from the PIT copy in the cyber security vault. For any missing fingerprints the process adds the data in new containers and the references in the index, providing an indirection that allows for just writing a new container with the missing L0 references and updating the index.

Abstract: During a current backup of a file system of a client, a determination is that a file in the current backup includes first data regions found in a file from a previous backup, and second data regions that are new. A virtual synthetic file is generated by writing the second data regions, and synthesizing the first data regions by referencing the file from the previous backup. A request received to restore the particular file includes identifications of other files still present at client. A determination is that the particular file corresponds to the virtual synthetic file and that the other files still present at client include the file from the previous backup. The second data regions are read to send to client. A complete version of the particular file is assembled at client using the file from the previous backup, still present at client, and the second data regions.

Abstract: Methods of cloning data backup across namespaces are disclosed. One or more source files are cloned from a first namespace to a second namespace, as one or more destination files. When the cloning of the source file(s) is performed, a data structure including source file information and destination file information is generated. A source synthetic file is cloned from the first namespace to the second namespace, as a destination synthetic file, where the source synthetic file uses the source file(s) as one or more base files on the first namespace. When the cloning of the source synthetic file is performed, the data structure is looked up to obtain the source file information and the destination file information. Based on the source file information and the destination file information, synthetic information of the destination synthetic file is updated to use the destination file(s) as one or more base files on the second namespace.

Abstract: Methods of cloning data backup across namespaces are disclosed. In response to receiving a file replication request, one or more source files are cloned from a first namespace to a second namespace, as one or more destination files. A first attribute indicating that the source file(s) have been cloned to the second namespace as the destination file(s) is created. A source synthetic file is cloned from the first namespace to the second namespace, as a destination synthetic file, where synthetic information of the destination synthetic file points to the source file(s) as one or more base file. A second attribute indicating that the source synthetic file has been cloned to the second namespace as the destination synthetic file is created. Based on the first and second attributes, the synthetic information of the destination synthetic file is updated or propagated to use the destination file(s) as one or more base files on the second namespace.

Abstract: A request is received to restore a file at a deduplicated storage system to a client. The file resides at the storage system as a synthetic file based on a base file at the storage system. The request includes an indication that the base file is also present at the client. Metadata generated during a backup of the file to the storage system is reviewed. The metadata includes references to data determined to be in the base file at the storage system, and references to other data determined to not be in the base file at the storage system. The other data determined to not be in the base file is read from the storage system and transmitted to the client. Upon receipt, the client assembles the requested file using the base file present at the client and the other data determined to not be in the base file.

Abstract: This disclosure provides system, methods, and media for identifying inadvertent compression or encryption in data streams from a client that land on a deduplication storage system. When one or more such abnormalities are detected, an alert message is generated to alert the administrator of the deduplication storage system so that corrective actions can be taken to prevent undesired consequences. According to an exemplary method, machine learning techniques are used to plot and smoothen global compression ratios and local compression ratios of historical backups from a client over a period of time. Then, a second derivative of each data point on the smoothened curves is taken and compared with a predetermined threshold to detect whether that the slope of the data point exceeds a threshold. A data point whose slope exceeds the threshold can be determined to be a data point corresponding to a backup that includes compression and/encryption.

Abstract: Replication of a filesystem or a mount point or share may replicate all data that it consists of irrespective of where the data is stored. Replication protects data irrespective of location. One method is to replicate the filesystem namespace as is while skipping the data outside of the appliance/machine so that replication cost and time are reasonable. The data outside of the machine, like cloud/tape data is protected differently. One example method includes a data protection operation configured to replication a namespace associated with multiple data tiers. During replication, data from one of the tiers is skipped while all of the namespace metadata is replicated. The recovery restores the namespace metadata and the data that was replicated from the other tier. This may be performed in connection with cyber security, for example when replicating multi-tier data to a vault.

Abstract: Replication of a filesystem or a mount point or share may replicate all data that it consists of irrespective of where the data is stored. Replication protects data irrespective of location. One method is to replicate the filesystem namespace as is while skipping the data outside of the appliance/machine so that replication cost and time are reasonable. The data outside of the machine, like cloud/tape data is protected differently. One example method includes a data protection operation configured to replication a namespace associated with multiple data tiers. During replication, data from one of the tiers is skipped while all of the namespace metadata is replicated. The recovery restores the namespace metadata and the data that was replicated from the other tier. This may be performed in connection with cyber security, for example when replicating multi-tier data to a vault.

Abstract: A request is received to restore a file at a deduplicated storage system to a client. The file resides at the storage system as a synthetic file based on a base file at the storage system. The request includes an indication that the base file is also present at the client. Metadata generated during a backup of the file to the storage system is reviewed. The metadata includes references to data determined to be in the base file at the storage system, and references to other data determined to not be in the base file at the storage system. The other data determined to not be in the base file is read from the storage system and transmitted to the client. Upon receipt, the client assembles the requested file using the base file present at the client and the other data determined to not be in the base file.

Abstract: Described is a system for leveraging incremental backup metadata of a deduplication storage system to perform an efficient data restore. The system may reference metadata stored as part of incremental backup infrastructure to determine only the changes to the data that occurred subsequent to the restore point. As a result, the system may reduce data read processing by retrieving only the changed data from the deduplication storage system. Moreover, the system may reduce the required bandwidth for the restore by providing only the changed data to a target device of the restore. Data retained by the client system such as the current version of the data may then be overwritten with the reduced set of data to complete the restore. As a result, the system may perform an efficient restore by reducing read accesses and bandwidth requirements, and thus, improve overall restore performance.

Abstract: Embodiments of an instant recall process and system for long-term data stored on a cloud storage tier. Embodiments include saving a content handle of a file in a cloud storage tier as an extended attribute in a single file system namespace; moving the file from the cloud storage tier to an active storage tier for data processing; recalling the file from the active storage tier to the cloud storage tier upon completion of the data processing; using the content handle from hidden metadata for a working copy of the file; and saving a hash of a segment reference as part of the extended attribute.

Abstract: A data management device includes a persistent storage and a processor. The persistent storage includes an object storage. The processor segments a file into file segments. The processor generates meta-data of the file segments. The processor stores a portion of the file segments in a data object of the object storage. The processor stores a portion of the meta-data of the file segments in a meta-data object of the object storage.

Abstract: Replication of a filesystem or a mount point or share may replicate all data that it consists of irrespective of where the data is stored. Replication protects data irrespective of location. One method is to replicate the filesystem namespace as is while skipping the data outside of the appliance/machine so that replication cost and time are reasonable. The data outside of the machine, like cloud/tape data is protected differently. One example method includes a data protection operation configured to replication a namespace associated with multiple data tiers. During replication, data from one of the tiers is skipped while all of the namespace metadata is replicated. The recovery restores the namespace metadata and the data that was replicated from the other tier. This may be performed in connection with cyber security, for example when replicating multi-tier data to a vault.