Abstract: Methods, systems, and devices for data management are described. The described techniques may enable a data management system (DMS) to determine an amount of data to be pulled from a source cluster prior to performing a replication of a source file stored on the source cluster. For example, before copying any data from the source cluster to a target cluster, the DMS may read an index file associated with the source file to determine data blocks that are different from data blocks of a base file stored on the target cluster, which may indicate indices of data blocks of the source file that may be replicated from the source cluster to the target cluster as part of the replication operation. By profiling the data to be copied before copying the data to the target cluster, the DMS may optimize the replication process to reduce latency, among other examples.

Abstract: Methods, systems, and devices for data management are described. A data management system may receive a request to generate backup data for a set of data files from the one or more databases. The data management system may then generate, in response to the request, a file including a set of partitions including respective groups of shard files that correspond to respective groups of data files from among the set of data files. In some examples, a respective group of shard files within a partition of the set of partitions may include a first shard file representative of metadata for the partition and one or more additional shard files representative of the respective group of data files for the partition. The data management system may then distribute the respective groups of shard files to a set of nodes within the distributed backup system.

Abstract: In some examples, a data management and storage (DMS) platform comprises peer DMS nodes in a node cluster, a distributed data store comprising local and cloud storage, and at least one processor configured to perform operations in a method of creating a local consolidated patch file from a patch file chain stored in the cloud storage. Example operations comprise, in a first dry-run phase, creating a patch file image of data blocks in one or more cloud patch files stored in the cloud storage; in a second data-transfer phase, downloading at least some of the data blocks from the cloud patch files identified by the patch file image; and creating and storing, in the local storage, the local consolidated patch file using the downloaded data blocks.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may access a snapshot of a target client object to perform a block-order traversal of a set of files included in the snapshot. The DMS may generate an index file for the set of files based on a metadata associated with the snapshot, the index file including a mapping between a file path for each file and one or more properties of each file. The DMS may then read the set of files included in the snapshot using a sliding window in accordance with the mapping between the file path for each file and the one or more properties of each file, and may determine whether to generate an alert based on reading the set of files included in the snapshot.

Abstract: Methods, systems, and devices for data management are described. The method may include obtaining a first fingerprint of one or more first data blocks obtained from a source data system, where the one or more first data blocks correspond to one or more data objects and are in accordance with a first storage format, obtaining, a second fingerprint of one or more second data blocks as stored in the backup system, where the one or more second data blocks correspond to the one or more data objects and are stored in the backup system in accordance with a second storage format, and comparing, in accordance with a mapping between data objects of the source data system and data blocks in the backup system, the first fingerprint and the second fingerprint to validate whether the one or more data objects are stored correctly at the backup system.

Abstract: Methods, systems, and devices for data management are described. The described techniques may enable a data management system (DMS) to determine an amount of data to be pulled from a source cluster prior to performing a replication of a source file stored on the source cluster. For example, before copying any data from the source cluster to a target cluster, the DMS may read an index file associated with the source file to determine data blocks that are different from data blocks of a base file stored on the target cluster, which may indicate indices of data blocks of the source file that may be replicated from the source cluster to the target cluster as part of the replication operation. By profiling the data to be copied before copying the data to the target cluster, the DMS may optimize the replication process to reduce latency, among other examples.

Abstract: Methods, systems, and devices for data management are described. The described techniques may enable a data management system (DMS) to determine an amount of data to be pulled from a source cluster prior to performing a replication of a source file stored on the source cluster. For example, before copying any data from the source cluster to a target cluster, the DMS may read an index file associated with the source file to determine data blocks that are different from data blocks of a base file stored on the target cluster, which may indicate indices of data blocks of the source file that may be replicated from the source cluster to the target cluster as part of the replication operation. By profiling the data to be copied before copying the data to the target cluster, the DMS may optimize the replication process to reduce latency, among other examples.

Abstract: Methods, systems, and devices for data management are described. A data management system may receive a request to generate backup data for a set of data files from the one or more databases. The data management system may then generate, in response to the request, a file including a set of partitions including respective groups of shard files that correspond to respective groups of data files from among the set of data files. In some examples, a respective group of shard files within a partition of the set of partitions may include a first shard file representative of metadata for the partition and one or more additional shard files representative of the respective group of data files for the partition. The data management system may then distribute the respective groups of shard files to a set of nodes within the distributed backup system.

Abstract: In some examples, a data management and storage (DMS) platform comprises peer DMS nodes in a node cluster, a distributed data store comprising local and cloud storage, and at least one processor configured to perform operations in a method of creating a local consolidated patch file from a patch file chain stored in the cloud storage. Example operations comprise, in a first dry-run phase, creating a patch file image of data blocks in one or more cloud patch files stored in the cloud storage; in a second data-transfer phase, downloading at least some of the data blocks from the cloud patch files identified by the patch file image; and creating and storing, in the local storage, the local consolidated patch file using the downloaded data blocks.

Abstract: A method for recovering files from a filesystem stored across sparse files in a cloud environment is described. According to the method, a data management system may receive a request to read the files. The data management system may identify one or more target address ranges corresponding to the files indicated via the request. The data management system may read index information for the sparse files in the cloud environment. The index information may indicate respective address ranges for data blocks within the sparse files. The data management system may identify one or more data blocks within one or more sparse files as corresponding to address ranges that overlap with the one or more target address ranges based on the index information. The data management system may transmit, to the cloud environment, one or more read requests for the identified one or more data blocks.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may access a snapshot of a target client object to perform a block-order traversal of a set of files included in the snapshot. The DMS may generate an index file for the set of files based on a metadata associated with the snapshot, the index file including a mapping between a file path for each file and one or more properties of each file. The DMS may then read the set of files included in the snapshot using a sliding window in accordance with the mapping between the file path for each file and the one or more properties of each file, and may determine whether to generate an alert based on reading the set of files included in the snapshot.

Abstract: Methods, systems, and devices for data management are described. The method may include obtaining a first fingerprint of one or more first data blocks obtained from a source data system, where the one or more first data blocks correspond to one or more data objects and are in accordance with a first storage format, obtaining, a second fingerprint of one or more second data blocks as stored in the backup system, where the one or more second data blocks correspond to the one or more data objects and are stored in the backup system in accordance with a second storage format, and comparing, in accordance with a mapping between data objects of the source data system and data blocks in the backup system, the first fingerprint and the second fingerprint to validate whether the one or more data objects are stored correctly at the backup system.

Abstract: A storage system may store one or more snapshots of a computing system to support backup and restoration of data stored at the computing system. The storage system may identify an expiration of a first snapshot indicating a first set of physical storage locations to which first data of the computing system was stored as part of a first backup procedure. The storage system may identify a first subset physical storage locations of the first set as storing a first portion of the first data that is superseded by second data associated with a second snapshot. Based on identifying the first subset, the storage system may delete the first portion of the first data from the first subset of physical storage locations and retain a second portion of the first data at a second subset of physical storage locations.

Abstract: A method for recovering files from a filesystem stored across sparse files in a cloud environment is described. According to the method, a data management system may receive a request to read the files. The data management system may identify one or more target address ranges corresponding to the files indicated via the request. The data management system may read index information for the sparse files in the cloud environment. The index information may indicate respective address ranges for data blocks within the sparse files. The data management system may identify one or more data blocks within one or more sparse files as corresponding to address ranges that overlap with the one or more target address ranges based on the index information. The data management system may transmit, to the cloud environment, one or more read requests for the identified one or more data blocks.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may access a snapshot of a target client object to perform a block-order traversal of a set of files included in the snapshot. The DMS may generate an index file for the set of files based on a metadata associated with the snapshot, the index file including a mapping between a file path for each file and one or more properties of each file. The DMS may then read the set of files included in the snapshot using a sliding window in accordance with the mapping between the file path for each file and the one or more properties of each file, and may determine whether to generate an alert based on reading the set of files included in the snapshot.

Abstract: In some examples, a method comprises: receiving a request to read data within a specified range from a backup file storing at least one base snapshot and at least one incremental snapshot; looking up the specified range in range filters from the backup file, the range filters corresponding to snapshots stored in the backup file and each range filter comprising bits indicating whether data exists at respective ranges within the snapshot corresponding to the respective range filter; and in response to the looking up, reading the requested data from the looked-up range in the backup file.

Abstract: A method of consolidating snapshots includes receiving a request to consolidate a first snapshot with a second snapshot into a third snapshot, the first and second snapshots stored in separate backup files, each backup file organized as a directory where data parts of the first and second snapshots can be hard linked to locations outside of the backup file, comparing the data parts of the first and second snapshots to determine if any second snapshot data part fully overlaps with any first snapshot data part, responsive to determining that a second snapshot data part fully overlaps with a first snapshot data part, hard linking the determined second snapshot data part into the third snapshot, and storing the third snapshot in the backup file.

Abstract: In some examples, a method comprises: receiving a request to read data within a specified range from a backup file storing at least one base snapshot and at least one incremental snapshot; looking up the specified range in range filters from the backup file, the range filters corresponding to snapshots stored in the backup file and each range filter comprising bits indicating whether data exists at respective ranges within the snapshot corresponding to the respective range filter; and in response to the looking up, reading the requested data from the looked-up range in the backup file.

Abstract: In some examples, a data management and storage (DMS) platform, comprises peer DMS nodes in a node cluster, a distributed data store comprising local and cloud storage, and at least one processor configured to perform operations in a method of creating a local consolidated patch file from a patch file chain stored in the cloud storage. The operations include, in a first dry-run phase, creating a logical patch file image of data blocks in one or more cloud patch files stored in the cloud storage; in a second data-transfer phase, downloading at least some of the data blocks from the cloud patch files identified by the logical patch file image, the second data-transfer phase comprising a coalescing operation to construct a set of coalesced reads of the data blocks; and creating and storing, in the local storage, the local consolidated patch file using the downloaded data blocks.

Abstract: In some examples, a data management and storage (DMS) platform comprises peer DMS nodes in a node cluster, a distributed data store comprising local and cloud storage, and at least one processor configured to perform operations in a method of creating a local consolidated patch file from a patch file chain stored in the cloud storage. Example operations comprise, in a first dry-run phase, creating a patch file image of data blocks in one or more cloud patch files stored in the cloud storage; in a second data-transfer phase, downloading at least some of the data blocks from the cloud patch files identified by the patch file image; and creating and storing, in the local storage, the local consolidated patch file using the downloaded data blocks.