Emc IP Holding Company LLC

Symantec Corporation

Veritas Technologies LLC

Sridhar Surampudi

Pavan Kumar Dattatreya Ati

Ravi Rangapuram

Timothy Michael Naftel

Ravi Kishore Yadav Rangapuram

Rangapuram Ravi Kishore Yadav

Manjunath Jagannatha

Ravi Shankar Panem

Kiran Kumar

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.

Minimizing a footprint of incremental backups

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.

Check point recovery based on identifying used blocks for block-based backup files

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.

Identifying changed files in incremental block-based backups to backup indexes

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.

Block-based backups for large-scale volumes and advanced file type devices

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.

Block-based backups for large-scale volumes

Various techniques, including a method, system and computer program product for restoring encrypted files are disclosed. The method includes accessing a file table record for an encrypted file. The file table record includes an encrypted file stream and extent information identifying a location of one or more portions of the encrypted file in a virtual machine image. In response to accessing the file table record a consecutive data stream is stored. Storing the consecutive data stream includes encapsulating the encrypted file stream and the one or more portions of the encrypted file.

Method and system for restoring encrypted files from a virtual machine image

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.

Check point recovery based on identifying changed blocks for block-based backup files

Embodiments provide granular recovery of virtual machine backups by generating the virtual machine backups comprising virtual disks that are configured as iSCSI targets; exposing, with an iSCSI server, the virtual disks as a logical unit number to an iSCSI client; performing SCSI read operations from the virtual disk using defined application program interfaces (APIs); and mounting a backup save set comprising the virtual disk files as a local disk on a computer where data recover is to be performed. Embodiments also emulate virtual disk storage as an iSCSI target by exposing the virtual disk as a logical unit number to an iSCSI client and mounting a backup save set as a local disk in an iSCSI server executing a backup process defining a granularity for data restore operations.

Growing community of inventors

Rajahmundry, India

Sridhar Surampudi