Abstract: Systems and methods for performing backups including incremental backups are provided. A change log is provided. The change log includes a map file that includes a bit for each inode in a file system. The bits are set on certain file events. The map file allows the files to be included in the next backup to be identified without having to trawl the entire file system. The change log also includes a data file that lists actual changes to the various files in corresponding records that are indexed by the inode number. The change log can enable faster incremental backups in part by eliminating unnecessary disk access requests.

Abstract: Systems and methods for performing backups including incremental backups are provided. A change log is provided. The change log includes a map file that includes a bit for each inode in a file system. The bits are set on certain file events. The map file allows the files to be included in the next backup to be identified without having to trawl the entire file system. The change log also includes a data file that lists actual changes to the various files in corresponding records that are indexed by the inode number. The change log can enable faster incremental backups in part by eliminating unnecessary disk access requests.

Abstract: Systems and method for performing backup. A layered file system is provided that is configured to detect all transactions with a physical file system. Based on an analysis of the transactions, records are selectively entered into a change log. A backup agent is able to generate a backup based on the change log, which reflects data that has changed or that needs to be backed up relative to the previous backup.

Abstract: In general, embodiments of the invention relate to a method for processing input/output (I/O requests). The method includes receiving an I/O request from a virtual machine executing on a host computing device, where the host computing device comprises a filter driver. The method further includes making a first determination that the filter driver is in a backup mode and based on the first determination, making a second determination that the I/O request intersects with a prior filter driver tracking list (FDTL). Further, in response to the second determination, the method includes pausing, by the filter driver, the processing of the I/O request, obtaining, from a primary disk, data associated with the I/O request, after obtaining the data, resuming the processing of the I/O request, where processing the I/O request results in the data on the primary disk being overwritten with new data.

Abstract: In general, embodiments of the invention relate to a method for processing input/output (I/O requests). The method includes receiving an I/O request from a virtual machine executing on a host computing device, where the host computing device comprises a filter driver. The method further includes making a first determination that the filter driver is in a backup mode and based on the first determination, making a second determination that the I/O request intersects with a prior filter driver tracking list (FDTL). Further, in response to the second determination, the method includes pausing, by the filter driver, the processing of the I/O request, obtaining, from a primary disk, data associated with the I/O request, after obtaining the data, resuming the processing of the I/O request, where processing the I/O request results in the data on the primary disk being overwritten with new data.

Abstract: Systems and methods for performing backups including incremental backups are provided. A change log is provided. The change log includes a map file that includes a bit for each inode in a file system. The bits are set on certain file events. The map file allows the files to be included in the next backup to be identified without having to trawl the entire file system. The change log also includes a data file that lists actual changes to the various files in corresponding records that are indexed by the inode number. The change log can enable faster incremental backups in part by eliminating unnecessary disk access requests.

Abstract: Incrementally backing up file system hard links based on change logs is described. A system identifies a unique identifier and a file name associated with a file event in a file system. The system determines whether a change log for the file system lacks an association between the unique identifier and the file name. The system adds the file name to one of a new file name list and a deleted file name list associated with the change log in response to a determination that the change log for the file system lacks the association between the unique identifier and the file name. The system incrementally backs up the file event based on at least one of the new file name list and the deleted file name list.

Abstract: A cloud gateway (GW) device receives a first request for incremental backup from a client device over a LAN, where the first request includes a first file representing a difference between the incremental backup in view of a prior backup. In response, the cloud GW identifies a first base backup previously backed up to a cloud storage server over a WAN. A second request is transmitted to the cloud storage server over the WAN to copy the first base backup into a second base backup. A third request is transmitted to the cloud storage server over the WAN to replace a second file within the second base backup. The third request includes a second backup ID, a descriptor describing the file to be replaced, and content of the file received from the client without modifying the first file.

Abstract: Recording file events in change logs while incrementally backing up file systems is described. A system begins incrementally backing up a file system by reading a current change log. The system identifies a file event associated with the file system while incrementally backing up the file system. The system identifies a unique identifier associated with the file event. The system determines whether the unique identifier associated with the file event is greater than a unique identifier offset associated with reading the current change log. The system records the file event in the current change log in response to a determination that the unique identifier associated with the file event is greater than the unique identifier associated with reading the current change log.

Abstract: A method of reading data from a partitioned directory incident to a serialized process. A first read and an offset value are received. A first data block in a modeled fully partitioned directory is identified based on the offset value and a predetermined number of entries associated with a buffer. It is determined whether the first data block in the fully partitioned directory is present in the actual partitioned directory. Zeros are written in the buffer if the first data block in the fully partitioned directory is not present in the actual partitioned directory otherwise the first data block associated with the actual partitioned directory is written to the buffer. A second data block is similarly read by a second read operation and written. The second data block is associated with a second subdirectory, selected based on a horizontal node traversal at a node level of said first subdirectory.