Abstract: Systems and methods for backing up data. A backup operation can identify blocks that have changed since a most recent backup operation. The blocks that have changed since the most recent backup operation are compared with the blocks that are being used. Only the blocks that are both used and have changed are backed up. This can reduce the size of the backup be excluding blocks that may have changed but are no longer used.

Abstract: Check point recovery based on identifying used blocks for block-based backup files is described. At least one data block is identified that is used by a system since a point in time in response to receiving a request to restore the system based on the point in time. At least one data block, corresponding to the identified at least one data block, is recovered from at least one backup file for the system, without reading each data block backed up via the at least one backup file for the system. The system is restored based on the recovered at least one data block.

Abstract: Embodiments are directed to a method of identifying changed files in incremental block based backups, by obtaining changed data blocks of a file from a change block tracking (CBT) driver, wherein the file has an associated master file table (MFT) record and a parent MFT record number used in a file system, and constructing a complete file path of the file by traversing from the changed MFT record to the root directory using respective parent MFT record numbers by iteratively parsing each record by extracting the file name and parent MFT record number and appending the file name to a previous MFT record file name.

Abstract: Embodiments are directed to a method of performing block based backups for large-scale source volumes, by obtaining a total source volume size to determine if the source volume exceeds 64 TB, creating a number of sub-volumes to divide the total source volume into discrete sub-volumes of 64 TB each, and storing in an advanced file type device (AFTD), upon a read operation for a block based backup operation, each block of the source volume into a corresponding sub-volume of the sub-volumes. The method determines a block number and offset of each block and derives the corresponding sub-volume from the offset. Each sub-volume represents an individual saveset of the backup operation, and the container manages the individual saveset for the block based backup operation.

Abstract: Embodiments are directed to a method of performing block based backups for large-scale source volumes, by obtaining a total source volume size to determine if the source volume exceeds 64 TB, creating a number of sub-volumes to divide the total source volume into discrete sub-volumes of 64 TB each, grouping the discrete sub-volumes into a container, and storing, upon a read operation for a block based backup operation, each block of the source volume into a corresponding sub-volume of the sub-volumes. The method determines a block number and offset of each block and derives the corresponding sub-volume from the offset. Each sub-volume represents an individual saveset of the backup operation, and the container manages the individual saveset for the block based backup operation.

Abstract: Systems and methods for backing up data. A backup operation can identify blocks that have changed since a most recent backup operation. The blocks that have changed since the most recent backup operation are compared with the blocks that are being used. Only the blocks that are both used and have changed are backed up. This can reduce the size of the backup be excluding blocks that may have changed but are no longer used.

Abstract: Check point recovery based on identifying changed blocks for block-based backup files is described. At least one data block is identified that changed for a system since a point in time in response to receiving a request to restore the system based on the point in time. At least one data block, corresponding to the identified at least one data block, is recovered from at least one backup file for the system, without reading each data block backed up via the at least one backup file for the system. The system is restored based on the recovered at least one data block.

Abstract: Systems and methods for backing up data. A backup operation can identify blocks that have changed since a most recent backup operation. The blocks that have changed since the most recent backup operation are compared with the blocks that are being used. Only the blocks that are both used and have changed are backed up. This can reduce the size of the backup be excluding blocks that may have changed but are no longer used.

Abstract: Systems and methods for generating synthetic backups and for consolidating a chain of related backups. The chain of related backups is merged on the fly to create a backup stream. A block allocation table (BAT) may be identified for each backup to be consolidated into a synthetic backup, and BAT entries from each backup may be merged or combined to create a new BAT table associated with the synthetic backup. The data included in the related backups may be reformatted on the fly from big endian to little endian or vice versa. The backup stream is stored on a target device or volume.