Method and system for supporting block-level incremental backups of file system volumes using volume pseudo devices

• US 9,959,278 B1
• Filed: 09/29/2011
• Issued: 05/01/2018
• Est. Priority Date: 09/29/2011
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Khanduja, Vaibhav, Balasubramanian, Shankar
• Primary Examiner(s): Adams, Charles D
• Application Number:
  US13/248,408
• Time in Patent Office: 2,406 Days
• Field of Search: None
• CPC Class Codes: G06F 11/1446 Point-in-time backing up or restoration of persistent data
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1466 to make the backup process non-disruptive
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

A method for performing block-level incremental backups of file system volumes using a pseudo device layer of a volume manager. A driver associated with a snapshot backup program is configured to back up the full pseudo disk upon receipt of a backup request, and not automatically performed upon startup. Incremental backups are performed thereafter using a driver that has been modified to include a monitor that tracks writes during backups. The standard I/O routine of the kernel is overwritten with an I/O routine that tracks write operations. The volume manager is called back to perform the incremental backup operations upon each write operation. The going down routine of the kernel is also overwritten to track any updates to the volume manager. If the volume manager is updated, the data structure is cleared and future backups are performed from a subsequent full backup.

Claims

1. A method comprising:

generating, by a volume manager, a pseudo disk that combines a plurality of physical disks where at least two of the plurality of physical disks have different layouts; and

implementing, by the volume manager, a snapshot backup program to perform an incremental backup of the pseudo disk generated by the volume manager instead of the plurality of physical disks by;

tracking write operations initiated by the volume manager to write to the pseudo disk and volume manager upgrades during an interval of time using a hook mechanism of a driver associated with the snapshot backup program, the hook mechanism of the driver overwriting a standard input/output routine with a tracking input/output routine and overwriting at least one of a going down routine of a kernel or a delete routine of a kernel with a volume manager upgrade tracking routine, the tracking input/output routine intercepting the write operations before data associated with the write operations is written to a snapshot and the volume manager upgrade tracking routine intercepting upgrades of the volume manager;

identifying the blocks of the pseudo disk that are affected by each write operation of the tracked write operations; and

causing the volume manager to be called to perform the incremental backup of the identified blocks by writing the data to the snapshot, the volume manager being called to perform the incremental backup after the snapshot backup program intercepts each of the write operations.

2. The method of claim 1 wherein the snapshot backup program is executed by a UNIX based processing system, and wherein the hook mechanism comprises accessing a strategy entry point of the UNIX kernel.

3. The method of claim 2 wherein the backup of the pseudo disk is a block-level backup performed by the snapshot backup program, the snapshot backup program further performing incremental block-level backups, and further wherein the tracked write operations indicate specific blocks that are updated in a defined period of time.

4. The method of claim 3 wherein the pseudo disk is maintained as an abstract storage device by the volume manager and stores data in a defined format.

5. The method of claim 1, wherein:

the volume manager upgrade tracking routine tracks a version of the volume manager by providing a hook mechanism that detects a self-initiated unloading of the driver associated with the snapshot backup program, and clears data structures associated with the snapshot backup program upon detection of a change in volume manager version prior to the performance of a next full backup operation.

6. The method of claim 5 wherein the hook mechanism that detects the self-initiated unloading of the driver comprises replacing a delete routine of an operating system executed by a processing system executing the snapshot backup program with the driver.

7. A computer program product, comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein, the computer-readable program code adapted to be executed by one or more processors to:

generate, by a volume manager, a pseudo disk that combines a plurality of physical disks where at least two of the plurality of physical disks have different layouts; and

implement, by the volume manager, a snapshot backup program, the snapshot backup program performing an incremental backup of the pseudo disk instead of the plurality of physical disks by;

tracking write operations initiated by the volume manager to write to the pseudo disk and volume manager upgrades during an interval of time using a hook mechanism of a driver associated with the snapshot backup program, the hook mechanism of the driver overwriting a standard input/output routine with a tracking input/output routine and overwriting at least one of a going down routine of a kernel or a delete routine of a kernel with a volume manager upgrade tracking routine, the tracking input/output routine intercepting the write operations before data associated with the write operations is written to a snapshot and the volume manager upgrade tracking routine intercepting upgrades of the volume manager;

identifying the blocks of the pseudo disk that are affected by each write operation of the tracked write operations; and

causing the volume manager to be called to perform the incremental backup of the identified blocks by writing the data to the snapshot, the volume manager being called to perform the incremental backup after the snapshot backup program intercepts each of the write operations.

8. The computer program product of claim 7 wherein the snapshot backup program is executed by a UNIX based processing system, and wherein the hook mechanism comprises accessing a strategy entry point of the UNIX kernel.

9. The computer program product of claim 8 wherein the backup of the pseudo disk is a block-level backup performed by the snapshot backup program, the snapshot backup program further performing incremental block-level backups, and further wherein the tracked write operations indicate specific blocks that are updated in a defined period of time.

10. The computer program product of claim 7, wherein:

the volume manager upgrade tracking routine tracks a version of the volume manager by providing a hook mechanism that detects a self-initiated unloading of the driver associated with the snapshot backup program, and clears data structures associated with the snapshot backup program upon detection of a change in volume manager version prior to the performance of a next full backup operation.

11. The computer program product of claim 10 wherein the hook mechanism that detects the self-initiated unloading of the driver comprises replacing a delete routine of an operating system executed by a processing system executing the snapshot backup program with the driver.

12. A system comprising:

a first processor-based computer component configured to perform a backup of a pseudo disk that combines a plurality of physical disks instead of a backup of the plurality of physical disks, the pseudo disk created by a volume manager, the pseudo disk being read in a sequential order, where at least two of the plurality of physical disks have different layouts;

a second processor-based component configured to track write operations initiated by the volume manager to write to the pseudo disk and volume manager upgrades during an interval of time using a hook mechanism of a driver associated with the snapshot backup program, the hook mechanism of the driver overwriting a standard input/output routine with a tracking input/output routine and overwriting at least one of a going down routine of a kernel or a delete routine of a kernel with a volume manager upgrade tracking routine, the tracking input/output routine intercepting the write operations before data associated with the write operations is written to a snapshot and the volume manager upgrade tracking routine intercepting upgrades of the volume manager, and identify the blocks that are affected by each write operation of the tracked write operations; and

a third processor-based component configured to cause the volume manager to be called to perform the write operations to the snapshot, using the snapshot backup program on the pseudo disk, in response to detecting that each write operation has been initiated by the volume manager, the volume manager being called to perform the incremental backup after the snapshot backup program intercepts each of the write operations.

13. The system of claim 12 wherein the snapshot backup program is executed by a UNIX based processing system, and wherein the hook mechanism is configured to access a strategy entry point of the UNIX kernel.

14. The system of claim 13 wherein the backup of the pseudo disk is a block-level backup performed by the snapshot backup program, the snapshot backup program being further configured to perform incremental block-level backups, wherein the tracked write operations indicate specific blocks that are updated in a defined period of time.

15. The system of claim 14 wherein the pseudo disk is maintained as an abstract storage device by the volume manager and stores data in a defined format.

16. The system of claim 12, wherein the volume manager upgrade tracking routine tracks a version of the volume manager by providing a hook mechanism that detects a self-initiated unloading of the driver associated with the snapshot backup program, and clears data structures associated with the snapshot backup program upon detection of a change in volume manager version prior to the performance of a next full backup operation.

17. The system of claim 16 wherein the hook mechanism that detects the self-initiated unloading of the driver is configured to replace a delete routine of an operating system executed by a processing system executing the snapshot backup program with the driver.